Quicklinker question

[OpenIT Solutions]

Hi,

In my MDG i have replaced legacy Quicklinker CSV with <<stereotyped relationships>> and all is now ok. Except for one small point.

In a few cases i want my users to use the quicklinker to form (suggested) relationships between two elements. However when dragging the quicklinker from the same source element to empty space, i do not want the quicklinker to (suggest) the target as a new element type. I could do this with the quicklinker csv (ie column N Create Element is blank). How can i do the same with <<stereotyped relationships>> or other meta model techniques ??

Thanks,

Jon.

[Paolo F Cantoni]

Hi,

In my MDG i have replaced legacy Quicklinker CSV with <<stereotyped relationships>> and all is now ok. Except for one small point.

In a few cases, i want my users to use the QuickLinker to form (suggested) relationships between two elements. However, when dragging the QuickLinker from the same source element to empty space, I do not want the QuickLinker to (suggest) the target as a new element type. I could do this with the QuickLinker csv (ie column N Create Element is blank). How can I do the same with <<stereotyped relationships>> or other meta model techniques ??

Thanks,

Jon.

Good question Jon,
Hadn't really thought about it, but I can see it would be useful in our case also.  Hopefully, we'll get an answer. Have you also put in a support request?


Paolo

[Eve]

There are two techniques, but neither offer the option of a single row.

The first, if the target element isn't in the current toolbox it won't be suggested as a new type. All the relationships will still work if the element is already on the diagram.

The second, is that the connector type can be marked as common. Unfortunately, that hasn't made it to the published user guide.

Metamodel Constraints and the Quick Linker

Rule Filtering
The metamodel constraints primarily define what connections are valid. The quicklinker is built from these valid relationships and is then filtered in a number of ways in order to present the relevant relationships to the user.

Item	Detail
Toolbox Filtering	By default for all new diagrams the elements and relationships offered by the quicklinker are restricted to match the types available in the toolbox. This can be changed by the user on a diagram by selecting the Complete view for the diagram or unchecking the Filter to Toolbox option within the quicklinker menu.
Common Relationships	Relationships defined with the _IsCommon property will not be offered as suggestions when a new element also needs to be created. The following UML relationships include this behavior when they are used with a metarelationship: Abtraction Dependency InformationFlow Realization Usage

Edit: I've also added _IsCommon to Special Attributes.

[qwerty]

You can't. I think. IIRC Eve answered that way to a similiar question I asked. If you define something it will also be in the drag-to-blank. Though I had a case where this only partially was true. Alas, I'm still struggling with this feature. E.g. I recently used a "wrong" metaclass with stange results. I guess it will take a year before I can call myself an expert in this area.

q.

P.S. seems I was cross-posting. Take Eve's answer for granted.

[OpenIT Solutions]

Hi,

Thanks for feedback everyone. The _IsCommon attribute worked for me.

Regards,

Jon.

[qwerty]

Edit: I've also added _IsCommon to Special Attributes.

But obviously this change itself has not made it to the public.

q.

[Eve]

Edit: I've also added _IsCommon to Special Attributes.

But obviously this change itself has not made it to the public.

q.

It will be included in the next update.I don't control when that is.