MDG - Stereotyped port tagged values not available at the beginning

[Guillaume]

I have stereotyped classes and ports with tagged values defined in my MDG.
When I create the class from the toolbox, it works fine i.e. I can see its tagged values.
However when I create the stereotyped port on the class, its tagged values are not visible from the Properties view so users cannot straight away populate them.
It's only when I save the diagram or if I click somewhere else, come back, click somewhere else and come back again that the tagged values show up.

It seems to be a bug (EA build 1555) unless there's a way to force it?

[Paolo F Cantoni]

I have stereotyped classes and ports with tagged values defined in my MDG.
When I create the class from the toolbox, it works fine i.e. I can see its tagged values.
However when I create the stereotyped port on the class, its tagged values are not visible from the Properties view so users cannot straight away populate them.
It's only when I save the diagram or if I click somewhere else, come back, click somewhere else and come back again that the tagged values show up.

It seems to be a bug (EA build 1555) unless there's a way to force it?

Hi Guillaume,
This bug - where things don't update correctly seems to be all over v15!  I've just got used to it.  Sometimes, you have to save and reload the diagram to see what you expected.

I suspect they've changed a synchronisation component in the background and are still clearing up the unintended consequences.

Paolo

[Geert Bellekens]

I have seen the same issue with attributes.

Geert

[Guillaume]

The help section talks about the Model Validation and I also previously tried the attributes metaconstraints, only to find they are relevant for Sparx EA Model Validation feature.
However I would find it useful to enforce such constraints so users are restricted and prevented from creating specific stereotyped ports under components or classes, stereotyped attributes under classes, etc.

Again according to the online help (https://sparxsystems.com/enterprise_architect_user_guide/15.2/modeling/metamodelconstraints.html), I don't think this is the case.

As a side note, I also find that the purpose of some metaconstraints is not very clear e.g. supplier, class, activity...