Hi all,
I am creating my first profile using the MDG helpers. After reading all I could find, and some trial and error, I have the basics working, but I am running into some quirks extending non-uml elements.
As part of my profile I am extending some BPMN2.0 elements, for example BPMN2.0::Activity.
The first issue is the look/drawing of the extended element. BPMN2.0 Activities will decorate the basic shape depending on the value of the "taskType"tagged value defined in BPMN2.0 for Activities. For example if the value of "taskType" is set to "Service", the shape will be decorated with a set of small gears in the upper left corner of the shape.
I have tried no shape script, and I have tried a simple shape script that just calls:
shape main{
DrawParentShape();
}
But all I ever get is the basic shape with no decorations. (I see in the shape script help files that they actually have a section for drawing what they call "decorations". I do not know if the BPMN2.0 profile adds the extra shapes as "decorations", I am just loosely using the term here).
The second issue may be somehow related to the above (assuming some script may not be finding the tag it is looking for), and that is that the BPMN2.0 tagged values are normally presented in a structured way, grouped into different categories in the tag value editor windows. For my stereotypes that extend the BPMN2.0 types, the BPMN2.0 tags get flattened into a single "BPMN2.0" grouping, and in addition they all appear twice in the tag value editors. Once under a "BPMN2.0" grouping all flattened, and then all repeated again in the regular "tagged values" grouping.
This is not just some visual duplication, there actually are two complete sets of tags in the element. I can change the values independently, and using a script I have to dump all tag values for an element I can see that there actually are duplicated tags.
Anyone have success in extending non-uml profiles?
