Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Uffe

Pages: [1] 2 3 ... 21
Hi everybody,

The quick linker definition format allows you to specify "captions" or menu item labels, in columns K and L.

It would be useful to be able to use macros which resolve to the source/target element names, eg #SRCNAME#.
The macros should honour the "Use Alias if Available" option in the diagram.



Hi all,

It would be useful to be able to force EA to open a particular page of the property dialog by default for a stereotyped element.

Is there a special attribute that can be set, or some other way to achieve this?

I'm thinking in particular of the custom tagged value page that EA creates. When you're designing stereotypes which are essentially just placeholders for a specific set of tagged values, having that page opened automatically on double-click would be a small but valuable time saver.



Suggestions and Requests / "New Project" in EA 14
« on: May 04, 2018, 06:15:48 pm »
Hi all,

The "New Project" function opens a dialog where you can select file type:
  • Enterprise Architect Project (*.eapx)
  • Enterprise Architect Project (*.eap)
  • Enterprise Architect Project (*.feap)
.eapx is new, the two others were in 13 as well.

The problem with this is that there's no explanation of what the different choices entail. A better list would be
  • Enterprise Architect Project / JET 4 (*.eapx)
  • Enterprise Architect Project / JET 3 (*.eap)
  • Enterprise Architect Project / Firebird (*.feap)

The "New Project" menu item should also be reworked so that it contains a submenu with items for the three file types. If you click the "New Project" item, the current dialog should be displayed, but if you point without clicking, the submenu should be expanded.


Bugs and Issues / Formatting on v14 Recent Features page
« on: May 03, 2018, 01:36:55 am »

I'm looking at the long list of features, fixes and tweaks in v14, and the formatting is off in some places which makes the page hard to read. Under 1400 "Execuable Statemachines" (sic) there's a bunch of stuff that's got nothing to do with state machines, and in that section as well as others (BPSim for one), all the bullets have been placed on the top level rather than the intended indented ones. I'm sure there are other similar issues on that page.

Completely boring, I know, but it would really be helpful if this could be fixed.


Bugs and Issues / RefGUIDList tag: field too small
« on: April 27, 2018, 11:29:25 pm »
Hi all,

I'm working with a profile where I've got a tagged value connector from one stereotype to another, with the target role multiplicity set to 0..*.
This is the equivalent of creating a RefGUIDList tagged value type.

The problem is that, after I've generated the MDG Technology, if I select more than six elements I get an error dialog saying

DAO.Field [3163]
The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data.

This is obviously because a GUID is 38 characters, which means a list of six GUIDs requires 233 characters, and with a maximum of 255 characters in the field another list entry won't fit.

The 255-character tagged value limit can be normally worked around with a <memo> value. So here's the question: is there a way of combining <memo> and RefGUIDList?

I tried creating a tagged value with the same name as an attribute in my stereotype, but that didn't work. I also tried manually editing the profile XML data to force the contents of a <memo> tagged value type into the RefGUIDList tag definition, but no luck.

Anyone else?


General Board / Choosing a tool
« on: April 26, 2018, 06:54:23 pm »
Hi all,

This is a tangent from Ian's thread concerning EA vs Aris for process modelling.

I realize that 'it depends' is the most logical answer, but, like most clients, they haven't decided exactly how they are going to do their process modelling.
And I think this is a reasonable approach.
But before you scream 'that's no way to choose a modelling tool', given that they have realized they WILL need a tool, then surely the smart thing is to tailor their approach to (1) their own requirements, but also (2) the capabilities of a tool.

It seems like a solution -> Requirement approach, but don't we need some measure of this? No point crafting a wonderful modelling approach, then finding there is no tool to which can do it without huge modification. And when maybe a small change to the modelling approach would make it fit disproportionately better with one or other tool.

I couldn't agree more with this, and in general universally if you refuse to allow the chosen platform to drive requirements you will end up with a complete mess that combines weak least-common-denominator fulfillment of functional requirements with the massive bloat of "platform independence."

It doesn't matter if you're designing a system, devising a method or picking a tool, if you put those blinkers on (horizontal blinkers, I guess, preventing you from looking down) you'll end up spending an enormous effort on shoehorning which, ultimately, is non-productive work.

Understanding the platform (tool, middleware, operating system, programming language...) and its capabilities, and making sure your solution fits on top of it, is Right not Wrong.


Bugs and Issues / ActivityParameter _instanceType not honoured
« on: April 25, 2018, 07:12:11 pm »
Hi all,

If you create two stereotypes, one of ActivityParameter and one of ActionPin, and specify that the parameter stereotype should be instantiated to the pin stereotype using the _instanceType attribute in the ActivityParameter metaclass, that specification is not honoured when EA creates an action pin during instantiation of an activity with parameters.

AFAIK there is no other way to instantiate an activity parameter. You can't drag-and-drop one onto an empty diagram area, nor onto an action.



Bugs and Issues / Language in activity parameters and action pins
« on: April 25, 2018, 06:58:30 pm »
Hi all,

When you create an activity parameter in a diagram, the parameter's Language property is set to the project's default regardless of the corresponding properties in the diagram and the activity.

If you create the parameter in the Structural Elements dialog, the behaviour is the same.

The behaviour is also the same for action pins in actions, both when created from the toolbox and in the Structural Elements dialog.

When an action pin is created as the result of instantiating an activity with paremeters, the pin is likewise given the project default Language.

When an activity parameter is created, its Language should be set to the same as its parent activity's.
When a pin is created manually, its Language should be set to the same as its parent action's.
When a pin is created as an instance of a parameter, its Language should be set to the same as the corresponding parameter's.



Bugs and Issues / Actions in toolboxes
« on: April 24, 2018, 09:05:52 pm »
Hi all,

If you specify a toolbox which includes the following attribute definition

Name: UML::CallBehaviorAction
Initial Value: CB Action

... the resulting toolbox creates CallBehaviorActions correctly, but the icon is incorrect. Instead of the standard action icon, the stereotype icon (from the Profile toolbox) is displayed.

If instead you define the toolbox attribute as

Name: UML::CallBehaviorAction(UML::Action)
Initial Value: CB Action

... the correct icon is displayed.

Also, while the user guide page on elements used in toolboxes omits CallOperationAction (but includes CallBehaviorAction), you can in fact specify a CallOperationAction in your toolbox, and it works as expected.

Both reported.


Bugs and Issues / CallOperation actions, action pins and exceptions
« on: April 23, 2018, 09:34:26 pm »
Hi all,

If I create a CallOperation, regardless of whether I've assigned an operation to it, I can't create my own action pins for it. That's OK, the intent is that CallOperation actions should be linked to operations, and the "Synchronize with Parameters" function in the properties dialog (in the Call tab) allows me to create pins for the operation's parameters.

But what if I want to create a pin for an exception?

An operation's parameters cannot be exceptions. There's no exception property to select. What you can do is add "raised exceptions" to the operation in the properties dialog, Redefines tab.

An action pin, on the other hand, can be an exception. There's an "Exception" property on a pin, and selecting it causes the pin to be displayed differently in diagrams (with an added triangle).

See where I'm going?

I can't manually add pins to a CallOperation action.
The CallOperation action's "Synchronize with Parameters" only creates action pins for the operation's parameters, not for its raised exceptions.
Pins can be exceptions, but operation parameters can't.


How do I represent visually the call to an operation which throws exceptions?


Hi all,

The default display of a CallOperation action looks a bit like this:

Or, if the action's name is the same as the operation's (which it is by default):

I've been testing a bunch of parameters in a custom shape script, but I can't seem to get at the interface name: neither the classifier.* nor the  propertytype.* properties give me what I need. (Classifier shows the operation name, but only until I close the diagram; when I reopen it, it's blank.)

Is there a hidden property that contains the "classifier" operation's parent element?


Bugs and Issues / CallOperationActions in project browser
« 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?


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.


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.


Bugs and Issues / Time-aware models: revert clone
« on: April 19, 2018, 10:14:14 pm »
Hi boys & girls,

I can't find a function to revert a cloned element in a diagram, in other words destroy the cloned element and replace it in the diagram with the original.

Isn't there one?


Pages: [1] 2 3 ... 21