Recent Posts

Pages: [1] 2 3 ... 10
1
Bugs and Issues / SQL Server Reverse on views: truncated definition
« Last post by Guillaume on April 20, 2018, 11:19:28 pm »
Hi,

I got the result of an EA reverse engineering run on a SQL Server DB that contains views. When the view definition (query) is longer than 4000 characters, the resulting definition in EA (viewdef tag memo) is truncated at this position.
I found a post on this issue here: http://www.sparxsystems.com/forums/smf/index.php/topic,10962.msg148710/topicseen.html#msg148710

Is there a way to resolve this in SQL Server, ODBC configuration or else?

Thanks
2
Suggestions and Requests / Enterprise architect as SAAS
« Last post by Sigera on April 20, 2018, 10:08:22 pm »
Hello,

Does Sparx offer to host the complete software in their own cloud ? Or we need to go through an external partner to step up the whole environment in a public cloud like azure or AWS ?

Thanks in advance.
3
Bugs and Issues / CallOperationActions in project browser
« Last post by Uffe on April 20, 2018, 10:04:54 pm »
Hi all,


A CallBehaviourAction is displayed with its classifier in the project browser on the form action_name : classifier_name.
A CallOperationAction, on the other hand, doesn't display its operation.

Shouldn't it?

Something like action_name : element_name::operation_name, where element is the interface, class, component or whatever that holds the operation?


/Uffe
4
General Board / Re: Where are user passwords stored?
« Last post by qwerty on April 20, 2018, 10:02:50 pm »
Well, not really. There is no real need for that. It's just that EA adds a few API calls which only get relevant in specific areas. And my book is  a general approach to EA's API which has not changed. Anyhow, every now and then I try to update the API description in the book with my own experience on their usage (which quite often is not that positive).

q.
5
If you create a stereotype for Action and assign it a shape script which prints the Classifier or Classifier.Name property, the expected behaviour for a CallOperationAction is that the name of the operation (when set) is printed. It is not.

When you set the action's operation, the name of that operation is printed -- but only until the diagram is closed. When next it is opened, nothing is printed although you can still Find the operation from the action.

It appears that classifiers defined by the GUID string and not the integer ID aren't handled correctly by the shape script engine.

/Uffe
6
Bugs and Issues / Bug report: Shape script not applied to action-subtype stereotype
« Last post by Uffe on April 20, 2018, 09:54:52 pm »
If you create a stereotype for CallOperationAction on the fly, then assign it a shape script in Configure -- UML Types, and then create a CallOperationAction in an activity diagram and give it that stereotype, the shape script is not executed.

If you modify the stereotype to apply to Action, it is executed correctly on the same CallOperationAction.


/Uffe
7
General Board / Re: Where are user passwords stored?
« Last post by steen.jensen@sll.se on April 20, 2018, 08:22:10 pm »
To Qwerty
Is your book about Scripting in EA updatet to EA v 13.x ?

Regards
Steen Jensen
8
Automation Interface, Add-Ins and Tools / Re: Scripts submenus
« Last post by Guillaume on April 20, 2018, 07:20:11 pm »
Hi Aaron,

The easiest solution would involve using the existing groups in EA.

If you create Diagram Package Groups Group1, Group2, etc. then having an option in EA to treat groups as sub menus would solve the issue
So a right click on a diagram or package would display...
Group1
   Script 1
   Script 2
Group2
   Script 3
   Script 4

Instead of having a flat list ...
Script 1
Script 2
Script 3
Script 4

This issue is impacting quite a lot of users who have many scripts now.
9
General Board / Re: need help for report template setup
« Last post by jimbox on April 20, 2018, 07:06:37 pm »
I just gone through your post and it is understandable. But I cannot find any solution for it because I am a beginner to this system. I hope you will get the required data from those who have known this for years.
10
Oh, and I found that if you've got the situation I had above, then select the non-cloned package in the cloned diagram and hit Clone Element as New Version, the old package is replaced by the new one in the diagram, and subsequently, the Clone Element menu item is greyed out.
As per my previous comments in the other TAM posts, I suspect it's working correctly.  Since the requirement for the initial clone of the diagram is to NOT clone any vertex, it is incumbent upon the user to determine which vertices to clone (including folders).
I'm not convinced. The way it works, the package has been cloned, but the original is shown in the cloned diagram.
Why would you want that?

Only reason I can see is that the cloned package doesn't contain any elements so you need the original in order to show package contents. But that only makes sense in the first generation anyway, so this is still more bug than feature in my book.

Still, if you're aware of it you can fix it immediately after parthenogenesis.1

/U


1 That's "creating a clone", children.
Pages: [1] 2 3 ... 10