Recent Posts

Pages: 1 ... 4 5 [6] 7 8 ... 10
51
General Board / Re: Stereotype, tagged values, and Integer types
« Last post by SteveC on September 20, 2018, 06:17:47 am »
It's important to note that you are defining a tagged value for the entire installation. If there is another tagged value with that name in your configuration, you may or may not get the results you expect.

If a tagged value of "Score" has already been defined in your configuration and your MDG also defines a tagged value named "Score" then you will have a name collision and "Score" may not do what you expect.
52
Is there any way to when opening a template, does EA already access a specific folder of the projetc browser?
Some short cut to it.
To avoid getting browsing to the folder I work on daily?
53
General Board / Re: Updating Diagram.StyleEx attribute
« Last post by Geert Bellekens on September 19, 2018, 11:11:32 pm »
As far as I can see there is nothing to update at all.
Unless there is code we aren't seeing here.
You might want to do a reload of the diagram however to make the changes visible.

Geert
54
General Board / Re: Updating Diagram.StyleEx attribute
« Last post by qwerty on September 19, 2018, 10:57:37 pm »
The culprit is
Code: [Select]
Repository.Execute("UPDATE t_diagram set ...");
theDiagram.Update();

The Update undoes the previous Execute. Swap both and you should be done.

q.
55
Automation Interface, Add-Ins and Tools / Re: EA Integration without Add In
« Last post by rwittmann on September 19, 2018, 10:31:07 pm »
It will also work if you have a user logged in all the time. Automated task schedule can then access your model through the com module.
56
General Board / Re: Updating Diagram.StyleEx attribute
« Last post by rwittmann on September 19, 2018, 10:21:12 pm »
Thanks, Geert!
You are right!

The following does not work. The Update() methods seem to revert the SQL update:
Code: [Select]
!INC Local Scripts.EAConstants-JScript

OnProjectBrowserScript();

function OnProjectBrowserScript()
{
// Get the type of element selected in the Project Browser
var treeSelectedType = Repository.GetTreeSelectedItemType();

if (treeSelectedType == otDiagram)
{
var theDiagram as EA.Diagram;
var package as EA.Package;
var diaId;
var name;
theDiagram = Repository.GetTreeSelectedObject();
diaId = theDiagram.DiagramID;
package = Repository.GetPackageByID(theDiagram.PackageID);
Repository.Execute("UPDATE t_diagram set StyleEx='ExcludeRTF=0;DocAll=0;HideQuals=0;AttPkg=1;ShowTests=0;ShowMaint=0;SuppressFOC=1;MatrixActive=0;SwimlanesActive=1;KanbanActive=0;MatrixLineWidth=1;MatrixLineClr=0;MatrixLocked=0;TConnectorNotation=UML 2.1;TExplicitNavigability=0;AdvancedElementProps=1;AdvancedFeatureProps=1;AdvancedConnectorProps=1;m_bElementClassifier=1;ProfileData=;MDGDgm=Extended::Requirements;STBLDgm=;ShowNotes=1;VisibleAttributeDetail=0;ShowOpRetType=1;SuppressBrackets=0;SuppConnectorLabels=0;PrintPageHeadFoot=0;ShowAsList=0;SuppressedCompartments=;Theme=:119;SaveTag=5AB66EC4;' where Diagram_ID=" + diaId + ";");
theDiagram.Update();
package.Update();
return;
}
else
{
// Error message
Session.Prompt( "This script does not support items of this type.", promptOK );
}
}

It works if I replace the Update() methods with
Code: [Select]

Repository.SaveAllDiagrams();

Thanks again!
Rene

57
Automation Interface, Add-Ins and Tools / Re: EA Integration without Add In
« Last post by OpenIT Solutions on September 19, 2018, 09:24:44 pm »
Hi,

Another option could be to get your client to install Pro Cloud Server and then use the web services interface provided. I've not looked at the interface yet - but I understand its limited, but could meet your requirement. See here:

http://www.sparxsystems.com/products/procloudserver/#oslc

Regards,

Jon.
58
General Board / RTF Documentation - Element filtering
« Last post by hismaimai2000 on September 19, 2018, 08:53:38 pm »
Hi Forum. I want to create an RTF that only reports on elements that have operations. I have tried all sorts of filters in various fragments and cannot seem to get an approach that works. Any assistance would be greatly appreciated. Kind regards,
59
General Board / Re: Updating Diagram.StyleEx attribute
« Last post by Geert Bellekens on September 19, 2018, 08:22:38 pm »
Result: extended style is not updated (even though diagram is updated through script and package is reloaded and even EA is restartet).

Can't be sure without seeing your script code, but saving the diagram in the script might very well undo the previous setting of the StyleEx field.

If you post the actual script we might be able the spot the problem.

Geert
60
General Board / Re: Updating Diagram.StyleEx attribute
« Last post by rwittmann on September 19, 2018, 08:12:41 pm »
Yes, Geert, you are absolutely right:

I'll try to describe my sequence a bit more detailed:
I have a python script running which generates requirement diagrams containing various elements
The generation works, the diagrams are created, containing the elements.

Now I run a different script (from inside EA), in which I try to modify the displayed compartments (I want to have the notes of each element shown).
I've read that I have to achieve this by changing the extended style via a SQL query.
So I read out the extended style from another diagram where the notes are shown.
Now I execute the script on a diagram where the extended style only contains the info on the extended diagram style (MDGDgm=Extended::Requirements;).
Result: extended style is not updated (even though diagram is updated through script and package is reloaded and even EA is restartet).

Now, I execute the script on a diagram where I just open the diagram properties, don't change anything, just close the properties with the "OK" button.
Result of the properties action: extended style is changed, notes are not shown by default.
Result of the script execution: extended style is changed to show the notes, diagram displays the notes of each element as well...
Pages: 1 ... 4 5 [6] 7 8 ... 10