Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: Somebody on December 31, 2020, 02:00:28 am

Title: MDG: Stereotyped Port --metaconstraint 'umlRole = type'-> Interface for drop as
Post by: Somebody on December 31, 2020, 02:00:28 am
I tried the following:
from: https://sparxsystems.com/enterprise_architect_user_guide/14.0/modeling_tools/metaconstraint.html (https://sparxsystems.com/enterprise_architect_user_guide/14.0/modeling_tools/metaconstraint.html)
(https://live.staticflickr.com/65535/50778154513_186bc85e85_z.jpg)
it worked for most of the stereotyped metaclasses as expected, but not for a stereotyped port. Let me call my stereotyped Port "MyPort" it appears in the 'Drop as:' drop down list of my stereotyped Interface "MyInterface", but if i select "MyPort" and usually should be created as a Port on a element i droped it to, it is neather fixed to the edge of that element nor visable..
In the ProfileDiagramm it looks like:
https://live.staticflickr.com/65535/50778566593_0ff860054b_c.jpg (https://live.staticflickr.com/65535/50778566593_0ff860054b_c.jpg)
In the "work-project":
https://live.staticflickr.com/65535/50778538368_e2528d2d57_b.jpg (https://live.staticflickr.com/65535/50778538368_e2528d2d57_b.jpg)
https://live.staticflickr.com/65535/50779415802_e372341c83_b.jpg (https://live.staticflickr.com/65535/50779415802_e372341c83_b.jpg)
I don't know if it's a bug or not supposed to - or if i miss something, anyone a clue ?
I'am using 14.1.1427 (Build: 1427) Corporate Edition

Thanks in advance
Title: Re: MDG: Stereotyped Port --metaconstraint 'umlRole = type'-> Interface for drop as
Post by: Somebody on January 21, 2021, 06:32:34 am
If someone ever has the same Problem, you should "update" your EA Version, I spent a lot of time searching for the Problem..
Not only for this umlRole but also, for instance for the ownedPort it did not work as expected. But it does perfectly with the new Version:
15.2.1557

I downloaded the trial to test it, should have done this earlier..
If such Problems are known a note in the corresponding Version of documentation would be appreciated.