Quicklinker definition not working

[qwerty]

Yes, I see. Will fiddle around with that...

q.

[Eve]

Just a guess.

If you're inheriting from the original Archimate_BusinessActor, the quicklink definitions defined by the archimate technology will also apply to yours.

All of the rows for BusinessActor have 'Exclusive to ST Filter + No inherit from metatype' set to true. Unless I'm mistaken this also has the effect that no entries without that property set will be considered at all. Potentially including your sub-type. If that's the case, setting it to true in your definitions may allow it to work.

[qwerty]

The Business Actor menu already has an entry "Composed of" from Archimate and that will be used. I renamed your menu to "My Composed of" and it appeared below in the menu.

q.

[Paolo F Cantoni]

The Business Actor menu already has an entry "Composed of" from Archimate and that will be used. I renamed your menu to "My Composed of" and it appeared below in the menu.

q.

So does that mean we've gotten to the bottom of the issue?

In other words, can we describe the problem and the solution - or is it still "in play"?

As I said, I'm keenly interested in the problem (and its solution) before I redevelop my QL.

Paolo

[Guillaume]

Fantastic, it works.

Here are the rules to follow:
- use a different name for the Groups (e.g. Business Actor Bis instead of Business Actor) - column Q
- use a different name both for "New Link Caption" and "New Link & Element Caption" (e.g. is Composed Of instead of Composed Of) - columns K and L

My final request would be to hide the inherited ArchiMate 2 QL definitions. I'm not sure if this is feasible.

[qwerty]

My final request would be to hide the inherited ArchiMate 2 QL definitions. I'm not sure if this is feasible.

I have not found a way to do that. Feature request (though I see little chances for that since it will involve a structure change of the QL table)?

q.

[Paolo F Cantoni]

Fantastic, it works.

Here are the rules to follow:
- use a different name for the Groups (e.g. Business Actor Bis instead of Business Actor) - column Q
- use a different name both for "New Link Caption" and "New Link & Element Caption" (e.g. is Composed Of instead of Composed Of) - columns K and L

My final request would be to hide the inherited ArchiMate 2 QL definitions. I'm not sure if this is feasible.

Thanks for that Guillaume,
Just to "close the circle"; what was the conceptual problem you were trying to solve - just creating your version of the Business Actor or was it more complex than that?

Paolo

[Glassboy]

Thanks for that Guillaume,
Just to "close the circle"; what was the conceptual problem you were trying to solve - just creating your version of the Business Actor or was it more complex than that?

I presume he like others is is trying to either improve on the UMLised Archimate or further UMLise it to make it more usable, by extending it with abstract metatypes.

You run into the same issues when prototyping TOGs suggested enhancements to Archimate. (eg https://www2.opengroup.org/ogsys/catalog/W150)

The real solution would be for Sparx to "open source" the Archimate 2 MDG and allow people to fork it.

[qwerty]

+1 (also for a couple of other things like the help wiki). But chances to see that within the next 10 years are about -1.

q.

[Guillaume]

I sent a query to Sparx regarding the QL issue. I'll update this thread when I get an update.

Paolo, I started looking into this as I have a client who would like to use the original Open Group Archimate colour code (yellow/blue/green on the behaviour/active/passive instead of biz/app/tech), as seen in Mastering Archimate book.
I'm nearly there and plan to share it once completed so users have the alternative option.

[Paolo F Cantoni]

Thanks for that Guillaume,
Just to "close the circle"; what was the conceptual problem you were trying to solve - just creating your version of the Business Actor or was it more complex than that?

I presume he like others is is trying to either improve on the UMLised Archimate or further UMLise it to make it more usable, by extending it with abstract metatypes.

You run into the same issues when prototyping TOGs suggested enhancements to Archimate. (eg https://www2.opengroup.org/ogsys/catalog/W150)

The real solution would be for Sparx to "open source" the ArchiMate 2 MDG and allow people to fork it.

Well I hope Guillaume confirms one way or the other.  (So we don't make any presumptions     - It's a joke, )

We decided to abandon extending the supplied ArchiMate and just replaced it.  We disable the supplied ArchiMate MDGs by renaming their extensions and hook up to our MDG instead.

Our need for consistency and rendering were such that we go off on a tangent.  As each new release of the supplied MDGs comes out we compare and contrast with the previous version to see if anything should be promoted to ours.

Paolo

[Glassboy]

We decided to abandon extending the supplied ArchiMate and just replaced it.  We disable the supplied ArchiMate MDGs by renaming their extensions and hook up to our MDG instead.

Which is why having it in a shared repository and being able to fork it would be more useful :-)