Recent Posts

Pages: 1 ... 8 9 [10]
Automation Interface, Add-Ins and Tools / MDG- Updated stereotypes
« Last post by SparxUser19 on April 19, 2018, 02:07:13 am »

How do I get rid of the leftover stereotypes that continue to exist as part of the various versions I went through, before finalizing my MDG technology. The old stereotypes are conflicting with similarly named stereotypes that are part of my final MDG technology.

Thank you in advance!
Bugs and Issues / Re: Auto numbering doesn’t work for imported requirements
« Last post by SparxUser19 on April 19, 2018, 02:03:02 am »
Thanks. That is what I ended up doing!  :)
General Board / Re: Stereotype, tagged values, and Integer types
« Last post by Martin Merkel on April 19, 2018, 02:00:53 am »
Hi Phil,
had tried this, and to some extend it worked (when adding it as an UML tagged value type). I had problems though to use that as part of an UML profile.
Thanks, Martin
General Board / Re: Stereotype, tagged values, and Integer types
« Last post by philchudley on April 19, 2018, 12:57:19 am »
Hi Martin

There is indeed a tagged value type that suits your needs, define it as follows:


There is an optional default defined as

Default= 0;

Hope this helps

General Board / Stereotype, tagged values, and Integer types
« Last post by Martin Merkel on April 18, 2018, 11:45:48 pm »
in the help on Add an Enumeration to a Stereotype there is a description on how to define an enumerated tagged value, and later use this in an UML profile. Is there as similar possibility to restrict a stereotype attribute to a certain Integer value range, for example from 0 to 127?
Thanks, Martin
Bugs and Issues / Re: Automatic EA database schema "upgrades" / "downgrades"
« Last post by mtamme on April 18, 2018, 11:19:13 pm »
Hi Geert,

we just recognized the issue since we check the 'Version' property before we execute some SQL scripts via the EA Automation Interface. With this check we just want to ensure compatibility with the current EA database schema. Since we only checked for version 4.01, which is (what we experienced) the default for EA 9.3 till 13.5 we had a problem when suddenly version 7.0 appeared in the usys-system table. But after a while version 7.0 disappeared and version 4.01 was back again.

We didn't experience any problems right now, except that our compatibility check failed. My main question is, if there are some other changes going on inside the database during these "upgrades" / "downgrades" which we are not aware of or is there generally another way to check compatibility with the EA database schema?

Where would that oder be important? I guess in the toolbox? If so (IIRC) EA does not offer an ordering from the MDG export (since IIRC I tried that once and could not figure it out).


In the toolbox you define the order yourself. (attribute order)
I don't see where the order in the MDG file would be relevant either.

But maybe it uses the project browser order when generating the profile xml file from a package?

To be clear,

You have

- A regular UML profile with "real" stereotypes
- Multiple toolbox definitions that use some of these stereotypes.

That is perfectly fine and won't be a problem. You can even use standard UML elements or stereotypes from other MDG's in your toolbox.

Hello all,

I have a profile file containing several toolbox profiles (each with an own diagram). The toolboxes share identical stereotypes and they will be used in the same model. When applying the toolbox elements in the actual model, do I encounter any issues in the long run? (since I have applied identical elements from different toolboxes in the same model)

You will somehow have to navigate to the actual activity to see the description.

The EA Navigator could help with that.

Pages: 1 ... 8 9 [10]