MDG Issue_13.5 & 14

[Aariyeh]

Hello,

I have customized a mdg technology extending archimate. However when try importing the technology in EA 13.5 its working fine. At the same time when i import the same technology in EA14. I can detect my mdg in resoruce and even the toolbox is visible.
But the quick linkers which I assigned is not working and the My element profiles getting varied from 13.5. Have attached the bot the images.Can some help me to figure it out.

EA13.5 : https://imgur.com/TtRe48p
EA14:   https://imgur.com/l8fFhyl


Thanks,
Aariyeh

[qwerty]

It looks like in 13.5 you did not have the profile properly imported. The stereotype should be listed like it's in the V14 picture. Doesn't your dropdown in V13.5 list the profile?

q.

[Paolo F Cantoni]

Hi Aariyeh,

It may be that your "Objective" stereotype in v14 is being "hijacked" by another MDG.  Check the t_xref stereotypes entry for the element.

We deliberately "encrypt" our stereotypes so that they don't clash with any other MDG, but we made a mistake on one.  We found our ABB (Architecture Building Block) was being hijacked by the TOGAF MDG, even though we had not enabled the MDG.  We renamed the stereotype and now all is fine.

As I understand it, in v14, ALL the "visible" MDGs are loaded into EA, but only the ones you enable are supposed to be activated.  We've found that functionality less than optimal as of v14.1.  Eventually, they'll sort it out.

HTH,
Paolo

[peterc]

Sparx have changed the way the quicklinker works in EA14. I originally reported a bug as my MDG worked in 13.5 but not 14.0. It seems that they believe it to be an improvement, apparently also including fixing a bug where a quicklinker could be applied when not intended (but to me seemed to work as it allowed my definition to be applied when that bug was present!). Sometimes my quicklinker definitions are applied and other times not.

With their help I did find that by specifying stereotypes (source and target) and/or diagram types to which the quicklinker applied increased the chance of the quicklinker being applied. If I remember rightly, I was told that by specifying the diagram type to which the quicklinker applies then that overrides something (sorry a bit vague) and it is used. That obviously only works if you expect the quicklinker to work on a (small) subset of diagram types.

There are some quicklinker definitions that I still have not managed to get to work on my MDG.

Sparx suggested using Metamodels - but while this helps limit the toolbox, it doesn't help me add preferences to the quicklinker.

Sparx can probably comment better than me!