Sparx Systems Forum
Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: Paolo F Cantoni on November 03, 2015, 11:29:18 am
-
The ArchiMate QuickLinker specifications includes the value "<none>" for the New Link Type column. Anyone know what it means? Are there any other Extrinsic Values that could be useful?
Paolo
-
It's how you tell the quicklinker not to inherit the default menu when there isn't an overriding menu. (You would normally put TRUE in the "Exclusive to stereotype" column, but if there are no possible connections between stereotypes then you don't have that option.)
-
It's how you tell the quicklinker not to inherit the default menu when there isn't an overriding menu. (You would normally put TRUE in the "Exclusive to stereotype" column, but if there are no possible connections between stereotypes then you don't have that option.)
Thanks KP,
Are there any other "specials". For example, I think it would be good to be able to specify that :
Class , stereotype: <any>, Class, Stereotype: <Same>, Aggregation, , Aggregates
To imply you can aggregate stereotype tot he same stereotype.
Paolo
-
Oh please no. I'm already struggling with describing the current capabilities. It would be so much easier if that were programmable conditions in a common language rather than this crude table format.
q.
-
We don't have that specific example, but we have introduced a few new ones with EA 12.1 Beta, e.g. specify the name or classifier of the (unstereotyped) source and/or target element. They use the previously unused "Complexity" field and are documented in the help.
-
We don't have that specific example, but we have introduced a few new ones with EA 12.1 Beta, e.g. specify the name or classifier of the (unstereotyped) source and/or target element. They use the previously unused "Complexity" field and are documented in the help.
Thanks,
I'll check out the help.
-
Oh please no. I'm already struggling with describing the current capabilities. It would be so much easier if that were programmable conditions in a common language rather than this crude table format.
q.
Indeed, but any improvement is better than no improvement...
Paolo
-
We don't have that specific example, but we have introduced a few new ones with EA 12.1 Beta, e.g. specify the name or classifier of the (unstereotyped) source and/or target element. They use the previously unused "Complexity" field and are documented in the help.
Thanks,
I'll check out the help.
Will the examples be extended to show the use of the new complexity column? I see what the definition says, but I'm not sure I can visualise the outcomes.
Paolo