How does the quick link configuration work?

[Arnoud_B]

I try to get the quick link capability of SparxEA to work in the MDG I am constructing but I am missing something important as whatever I do nothing changes (and as usual SparxEA does not give any hint of what I do wrong).

So what do I do?

In my MDG I created two elements that 'generalise' the ArchiMate MDG elements:
ArchiStib_StandardHardware 'generalising' ArchiMate3::ArchiMate_Device
ArchiStib_PatternSolutionBuildingBlock 'generalising' ArchiMate3::ArchiMate_TechnologyCollaboration
- first image in: https://imgur.com/a/eSazZJ0

Then I add a quicklink configuration as I want the quicklink only to show a "Realization" relation between the two.
Quicklink configuration below!

However if I deploy my MDG I still get the same list as the parent possibilities and my quicklink configuration does not seem to do anything.
- Image in the link above but the second image.
So I most probably did something completely wrong but I cannot find my mistake.


Quicklink configuration:
Class,ArchiStib_PatternSolutionBuildingBlock,,,,Class,ArchiStib_StandardHardware,Realization,,to,,Realization to,TRUE,TRUE,TRUE,TRUE,,0,,,,,
Class,ArchiStib_StandardHardware,,,,Class,ArchiStib_PatternSolutionBuildingBlock,Realization,,from,,Realization from,TRUE,TRUE,TRUE,TRUE,,0,,,TRUE,,
Class,ArchiStib_PatternSolutionBuildingBlock,Class,ArchiStib_StandardHardware,,,,Realization,,to,Realization to,,TRUE,,TRUE,TRUE,,0,,,,,
Class,ArchiStib_StandardHardware,Class,ArchiStib_PatternSolutionBuildingBlock,,,,Realization,,from,Realization from,,TRUE,,TRUE,TRUE,,0,,,TRUE,,

[Geert Bellekens]

Don't try to use the old QL definitions, that will only result in a lot of headache. This is legacy by now.

You can do this a lot easier with metaconstraints and stereotyped relations and stuff like that.

Geert

[Paolo F Cantoni]

Don't try to use the old QL definitions, that will only result in a lot of headaches. This is legacy by now.

You can do this a lot easier with metaconstraints and stereotyped relations and stuff like that.

Geert

Wot 'e sed!

Paolo

[Arnoud_B]

Hi Geert,

You can do this a lot easier with metaconstraints and stereotyped relations and stuff like that.

Could you give me a hint which part of the documentation to read, I fill my evenings with searching for "stuff like that" the documentation of EA is not that bad once you found what you are looking for but just browsing around does not really help.
What do I need to do to get rid of all other relationships in the 'arrow' pop-up in the diagram except Realisation?

[Geert Bellekens]

Here somewhere I guess: https://sparxsystems.com/enterprise_architect_user_guide/15.2/modeling/metamodelconstraints.html

Geert

[qwerty]

Plan a good span of time on learning that. Once you did it you can do much more (though I still struggle with lots of pitfalls there) than with the QL CSV. The latter is just a dumb thing where you only can loose time and hairs (by pulling them out).

q.

[Arnoud_B]

Thanks guys!
I'll read the page carefully and experiment. I am mostly impressed with the tricks SparxEA can do but it is not at all self explanatory at times. Or my programming skills got rusty as I am doing Architecture in PowerPoint for too long ;-) Probably both!

[qwerty]

I'd say it's mainly the first :-(

q.

[Arnoud_B]

Thanks querty for blaming SparxEA and not me ;-)

I spend a morning experimenting and I succeeded in adding a connector type to my quicklinker.
As (nearly) always there were some 'you have to know it' where the documentation was not really 100% correct. Or at least not for my situation.
I needed to use the full name of the connector type so ArchiMate3::ArchiMate_Access otherwise no luck
And a nice one you have to set the "stereotype" tag on the stereotyped relationship tags which is only visible on the properties pop-up and NOT on the dependency tags which is the only thing visible in the properties window ...

So now I can add things to my quicklinker but I wanted to remove things from the quicklinker, the quicklinker has all kind of entries because my new Stereotype Generalizes an ArchiMate3 Stereotype. If I remove the generalization my quicklink menu only shows the one I configured but if I reintroduce the generalization they comeback. I succeeded to remove the UML connector types with the _HideUmlLinks=true attribute but that does not seem to work (which is logical seeing its name) for the inherited connectors from the ArchiMate3 stereotype.

Any idea's how to keep inheriting an ArchiMate stereotype but not inherit it's quicklinker menu entries?

[qwerty]

Unfortunately the _hide-way is the only one. Means once you turned the inheritance off you need to redefine anything you need yourself. Sucks, I know...

q.