Tagged Vaules from Profile (distinguished)

[thomas.kilian]

When you create a tag from a profile (preferably with enumeration) (e.g. called profileEnumTag) then this tag is "there" when you add the according element. And it is automatically supplied with the defined drop down. Now: when you add a tag profileEnumTag manually then you get a second one without the enumeration constraint. If you use Fully Qualified Tags then you can see that they are different. So far so good. But...

1) When you delete profileEnumTag (the one coming from the profile) then you can NOT recreate it. You only can add the manually defined tag without the enum constraint. There should be a way to re-create the profile defined tag.

2) When you loop through TaggedValues in automation EA does not yield the Fully Qualified name. This is really bad especially since the Synch Tagged Values duplicates tags. There needs to be a way to distinguish between (wrong) manually/duplicated tags and those coming from the profile.

3) Similarly to 1) there needs to be a way to re-create a tag with the profile constraints from automation.

At least 2) is a bug. The other two are missing functionality. I'll send a bug report.

[«Midnight»]

Thanks.

This one sounds nasty, at least as far as downstream problems are concerned.

[KP]

1. You will need to export your tagged value type definition with your profile, and that means creating an MDG Technology.

2. This looks like an oversight - the FQ name needs to be made available in automation.

3. The answer to 1 might help here (I haven't tried it). Otherwise setting TaggedValue.Notes to "Type=Enum;Values=one,two,three;Default=one;" (or whatever the real values are) might do the trick.

[thomas.kilian]

Neil,
I tried 3. and it "somehow" worked. First I never would have expected that you could put that in the Notes since that always looked like an extension to the limited Value field. However, EA seemed to interpret the contents and placed the default value in the Value. But no drop down appeared. Conclusion: It does not work.

When you're at construction here: I would expect that these data need to be places in another attribute. I would call it Behaviour or the like. That would give the possibility to create Tags like in the tags editor.

[peter.zrnko]

Have you tried to use Synchronize Tags and Constraints ?

This isn't an answer to your question but it could help a little bit.

[thomas.kilian]

You can't do that with automation. Also if you create a profile tag manually the sync doesn't rectify the tag behaviour. It creates another one

[«Midnight»]

You can't do that with automation. Also if you create a profile tag manually the sync doesn't rectify the tag behaviour. It creates another one

AFAIK the second behavior is known to to Sparx and a solution is in the works, for some unspecified but near-term time.

The first however is a real issue. Not just for itself - it is sufficient to be a bit of a show-stopper around here - but as an 'introducer' for a whole  family of issues. The API has not kept up with new features in several areas.

As new features are beginning to make use of EA's extensibility functions, limitations in the API that once were annoying have become severe restrictions.

Of course this problem is completely solvable, but only by Sparx. IMHO waiting for another major release is simply not a go. But that's just my opinion, of course...

[KP]

This will synchronize a single stereotype's tagged values from an add-in:

Code: [Select]

Repository.CustomCommand("Repository","SynchProfile","Profile=MyProfile;Stereotype=MyStereotype;")

[«Midnight»]

Except that the call is completely undocumented, and previous experience reported in this forum has indicated it does not always work as expected.

Perhaps some additional information would help...