Creation of element on package browser using Template Package fails

[Roman Liebsch]

The template feature is a nice feature to prepare project specific templates for special elements but it could be improved.

Okay obviously it is intended to be used for "Display Options" acc. to SPARX:

When you are creating a new element, the system checks for that element type in the Templates Package and, if it finds that element type, will copy the template element as defined. The definition includes any default display options of the template element,...

but it is really coping the whole content like attribute, notes, tags and their "default" content, even for <memo> etc. of our own stereotypes of our toolbox.
That is what the users like to use as I cannot setup some of them via the toolbox.

So far so good, now let's come to my use cases:

• UC1: If I drag the stereotype from the toolbox on a diagram, everything is working fine and I get a real copy.
• UC2: Doing via Add Element... EA does not copy the content, I think as the trigger is different and not started from a diagram. I would appreciate to act as UC1.
• UC3: Now it comes really strange, if I drag a stereotype (extension of metaclass Requirement) from the toolbox on a package, then EA creates for that stereotype 2 stereotypes - the chosen one and another of same metaclass and even copies the content of the other one. And that is really not a feature and makes us trouble. It seems that is only the case if I use the metaclass Requirement; for Class EA acts like UC2.

Can someone confirm or has an idea what I am doing wrong?

Roman

[Geert Bellekens]

Hi Roman,

I've read something similar earlier this week, so it seems like that is indeed an existing problem.

Remember to send in an official bug report as well if you ever want this to be fixed.

Geert