Recent Posts

Pages: 1 2 [3] 4 5 ... 10
Bugs and Issues / Actions in toolboxes
« Last post by Uffe 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.

You can look at the port instance's classifier and extract the name for your sorting.


P.S. The classifier is stored in t_object.PDATA3 as guid (should be MiscData[2])
General Board / Aris vs EA for Process Modelling
« Last post by Ian Mitchell on April 24, 2018, 08:35:09 pm »
I have a client who is looking for some help evaluating Aris & EA for process modelling.
All of us, I'm sure, have a natural preference, but does anyone have any recent experience of these two? If it helps, my client is willing to pay money for someone with this experience.
Bugs and Issues / Re: SIPOCs often require same element twice (or more) on diagram
« Last post by Uffe on April 24, 2018, 07:54:53 pm »
Well the each-element-no-more-than-once-in-each-diagram thing appears to be pretty fundamental in EA, and I don't think we're going to see that change anytime soon.

Virtualized connectors is a workaround that's been provided to get around this limitation for certain use cases. If you're not in one of those use cases, it won't work for you and you're relegated to EA's core functionality: when diagrams get unwieldy due to the once-per-diagram limitation, work with separate diagrams or instances of elements.

And as I always advise my clients, basing a method of working or a tool adaptation on something other than the core functionality of that tool is precarious at best. You're taking on risk that way, and reality has a tendency to bite.

Workarounds are also not compatible with our model validation addin that uses a clean language metamodel as configuration data.
We don't want workarounds (e.g. creating instances)

We need clean and direct traceability between elements as we are generating lots of excel reports and governance charts.

General Board / Re: Show activity numbering in diagram?
« Last post by Mahalo on April 24, 2018, 07:20:36 pm »
Could you please provide details/a screenshot of the "package settings"?
Could not find this at first try.

Thanks!   ;)
Bugs and Issues / Re: SIPOCs often require same element twice (or more) on diagram
« Last post by Uffe on April 24, 2018, 07:06:34 pm »
In brief: no.

But you can usually achieve the desired result using instances or activity parameters.

Bugs and Issues / SIPOCs often require same element twice (or more) on diagram
« Last post by adepreter on April 24, 2018, 07:01:05 pm »
Any date about when we shall have a solution for this? (besides the weird and buggy “virtual connectors”).,39241.msg242691.html#msg242691

Users complain they cannot create SIPOcs because of this.
Pages: 1 2 [3] 4 5 ... 10