duplicate tagged values extending non-uml profile

[ken.norcross]

I don't know why but I am getting duplicate tagged values when creating a profile that extends a non-uml element.

The xml for the profile element is pretty plain and simple:

<Stereotype name="Report" notes="" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0" generalizes="BPMN2.0::DataObject" baseStereotypes="BPMN2.0::DataObject"/>


I have reduced my test case to as simple as possible. New EAP file, new MDG model from the wizard, a single stereotpye as defined above, a single toolbox with one item, create the MDG xml using the wizard, import the technology, create an instance, and I get doubled tags.

The tags being duplicated are the BPMN2.0 tags. They show up under the BPMN2.0 category, and then again under the plain "Tagged Values".

I have given up trying to fix this, and have written a script to remove the extra tags.

Is this a bug or am I doing something wrong? I have reduced it to such a simple case I can't see anything wrong.

[qwerty]

How could you create the above except manually? I was not able to define it with EA's profile tools.

q.

[KP]

Do you have a Project Template Package defined?

P.S.

(the smiley face is a ":" and a "D")

When you post your message, check the option to disable smilies ;)

[ken.norcross]

No project template package, brand new empty EAP file.

Smilies disabled, thanks :)

[ken.norcross]

How could you create the above except manually? I was not able to define it with EA's profile tools.

q.

I follow the steps here:

http://www.sparxsystems.com/enterprise_architect_user_guide/10/extending_uml_models/non_uml_metatypes.html

In step 4, pick BPMN2.0::DataObject on the stereotypes tab

In step 5, name the new stereotype "Report"

Continue with adding the Generalize relationship, save the profile, etc.

[qwerty]

Thanks! I tried your example and it worked without issue. Maybe it's a cross-over with BMPN2.0 and 1.1 or 1.0?

q.
[edit] I used a different name than Report and that worked. With Report I see the same issue as you.

P.S. I deleted the default "report" stereotype in Settings/UML Types/Stereotypes and the issue was gone.

[ken.norcross]

Thanks! I tried your example and it worked without issue. Maybe it's a cross-over with BMPN2.0 and 1.1 or 1.0?

q.
[edit] I used a different name than Report and that worked. With Report I see the same issue as you.

P.S. I deleted the default "report" stereotype in Settings/UML Types/Stereotypes and the issue was gone.

Thanks for the hints for a possible workaround This has been driving me a little crazy. I have BPMN 1.0 and 1.1 turned off.

I will try some combinations and see. In my profile I am extending BPMN Process, Activity, DataObject (twice), StartEvent, and EndEvent. I see the problem on all of them.

[edit] - in my test profile I have limited it to one single stereotype as described in the first post, in my true profile I will need to extend many BPMN stereotypes, and in that profile I see the problem in all cases

[ken.norcross]

q.
[edit] I used a different name than Report and that worked. With Report I see the same issue as you.

As I said this has been driving me crazy, because I swear sometimes I do not get the effect and sometimes I do. Just when I think I have the magic configuration in a test profile, and start rebuilding my real profile, the issues comes back. I have to be very careful and keep track of everything that varies.

I tried your suggestion and changed the stereotype name to MyReport.

Where do you look to see the tagged values?

Now I realize if I look in the popup Properties dialog that you get when you double click an element the duplicate tags are there.

If you look in the dockable Tagged Values window that you get from the View menu, the duplicates are not there.

If I run a script to dump all the tagged values I can see that they are duplicated.

[qwerty]

There's an option: in the Tagged Values window click the icon with the checkmarks. That allows to turn on showing duplicates. It's also somewhere in the global options - well, it's EA.

q.

[ken.norcross]

Duplicate tags option didn't make any difference to my models.

I now realize in my home installation I am at build 1006, and my work installation is at build 1004. My build 1006 behaves better, no duplicate tags, so I am going to upgrade work to 1008 and see what difference that makes. I see in the notes for 1006 they fixed something related to migrating stereotypes that creates duplicate tags, so hopefully this is the issue.

[ken.norcross]

Upgrading to V10.0.1008 has fixed the duplicate tags problem for me, thanks folks, I should have checked this first.