Problem with "feature" full qualified tagged value

[gwieser]

hi, can't believe nobody ran into this problem so far as  i couldn't find any postings here regarding this topic.

from 7.1 onwards, EA treats tagged values that come from stereotypes in a profile totally different: the real UML name of the tagged value consists of profile name::stereotype name::tagged value name. this is, hmm, interesting and maybe a good solution to make tagged values unique somehow across different profiles. unfortunately, there is obviously no migration path. if you have a project with a DSL/profile already in use, then upgrade to 7.1 and once click "synchronize" in the resource pane, EA will create new tagged values with the new full qualified name and WILL NOT MIGRATE the old value. You will have the old "simple" tagged value with the value you once have entered, plus the new full qualified tagged value with no value at all. which leaves EA 7.1 completely useless for users of (changing) profiles...

we contacted sparx about that, so far they simply confirmed that this is not working as expected....anyone having an idea or at least seen the same behaviour?

br,
günther

[«Midnight»]

Hi Günther,

EA 7.1 appears to be the first version that was sensitive to different 'paths' for tagged values. I've seen a few other issues related to this, which either have been or are being (appear to be) solved at Sparx. The corrections seem to come out in new builds (so far) and not be delayed to future versions of EA.

Thanks for reporting this one.

David

[basalt]

Hi.
I just downloaded and installed build 831 of EA, and the problem with full qualified tagged values will still be there.
So I am not able to upgrade from 7.0 to 7.1

kr
george

[«Midnight»]

Yep, just noticed that myself.

Depending on when you contacted Sparx, build 831 might have been frozen pending release. Perhaps we'll see progress in 832...

David

[basalt]

Hi «Midnight»
thanks for checking this build too, so I will wait for the next one.

kind regards
basalt

[grossh]

Hi,
build 832 is out and the release notes mention this problem to be fixed.

I've just given it a short try and it seems to work.
All tagged values will be replaced by their fully qualified names, but the data remains intact.
The only weird thing I've found: If you are using tagged value associations within your profile, you will only get a drill down to select the referenced element, if the tagged value options are set to display only short names. Otherwise the data displayed is a GUID and no drilldown is present.

Harald

[«Midnight»]

Hi Harald,

Thanks for checking - and thanks again for posting back.

Please submit a bug report on the association thing. This sounds like a flaw to me. Given the nature of the problem I suspect it slipped through testing.

Hopefully Sparx can address this for build 833.

David

[Eve]

The only weird thing I've found: If you are using tagged value associations within your profile, you will only get a drill down to select the referenced element, if the tagged value options are set to display only short names. Otherwise the data displayed is a GUID and no drilldown is present.

Yes, I noticed this myself when looking at the synchonise tagged values issue, and passed on the the relevant developers.  However, it's probably also worth you submitting a bug report.

[basalt]

Hi all.
A new version is out, and I tried to reproduce the problem with the "Problem with "feature" full qualified tagged value" in version 7.1 build 832 an it will be still there, also I reported a bug with a .eap file where Sparx can simple retest it but no reply and no fix still now. So the version 7.1 is still a version which cannot be used by us.

kr
george

[«Midnight»]

Thanks for the update George.

The next build should be out sometime this month, so check every few days. The subsequent build - we might have missed the cut for the next one - should be out in October sometime.

Please let us know if the problem gets resolved then.

David

PS: What's the problem with EAP files?

[basalt]

Hi Dave.
Thx for the reply, i will check also the next build.
I sent a EAP file within the bug report to Sparx to provide a project which points to the problem of FullQualified Tagged Values. So the EAP will only be an example.

kr
george

[«Midnight»]

Thanks George,

I see what you mean now. The EAP file will definitely help them test. It seems that replicating the problem on their side is not the issue, since Simon can do that, but having a valid test case from 'the wild' should help them ensure the solution works.

David

[basalt]

Hi all

A new version --- a new retest of duplicate tagged values.
Tested version = 7.1.0 833.

After sync tagged values with profile, no duplicates are there anymore, so the sync work. BUT only if you use right click on stereotype in Resource profile and select "Sync Tagged Values and Constraints...".
Do NOT select and drag and drop the stereotype to attribute, is this will be done, duplicates will be still there.

kr
basalt

[«Midnight»]

The drag and drop problem is probably worth another bug report. They are getting closer, but if we don't tell them about these things they cannot resolve them.

[basalt]

thx for the info, i have post a bug report.
kr
basalt