Duplicate Tagged Values

[pH]

Hi,

There is a horrible bug in EA with respect to tagged values. When a tagged value is added using the script to an element (requirement in my case) with the same name, it actually maintains the newly added plus the previous one with that name. When I get the enumerator for tagged value and loop through I get count as 8 but in the tagged values browser or under requirements I see only 4 because those 4 were duplicated.

Thanks,
pH

[pH]

This can be reproduced using UI itself. Just add 2 tagged values with the same name. EA simply maintains the both. YOu delete once. You still see the duplicate one!!

I think this should be fixed in EA to not to have duplicate tagged values

Thanks,
pH

[pH]

Hi,

I noticed that there is an option to view the duplicate tagged values. Looks like EA is designed like that. But not sure under what circumstances some body needs multiple tagged values with the same name

Thanks.
pH

[beginner]

EAUI is the answer.

b.

[Eve]

The reason I most often use duplicate tagged values is to attribute (or assign) an element to multiple people.  That's just an example though.

[beginner]

Yes, Simon. But all people I know would have chosen a multi-select-list for that purpose. A quite common GUI element. RefGUIDList is something along that line.

b.

[Geert Bellekens]

I must admit that I too use duplicate tagged values  

I'll explain... We use tagged values to maintain the relation between state machine transitions, and the operations that trigger those transitions.
(I tried to use the "real" triggers, but that was way too much overhead for a simple traceability feature)
At first I used the RefGUIDList thing to select all the operations that trigger a transition, but I found it just not user friendly. Once you have selected two operations, and you want to add a third it is way too easy to replace the previous selection with the new operation.

That is the reason we decided to use multiple tagged values with the same name, each one representing only one operation.

I know it is agains UML rules, but with the current state of affairs in EA I don't see an alternative.

Geert

[beginner]

I'd rather like to see a more elegant implementation of the RefGUIDList. The current is very clumsy (as Geert says: Not User Friendly). It would be nice to see a multi-select list which could be configured from stereotyped elements (from a namespace, package, package-tree, etc.), subsets of those, lists of fixed values and any combination.

b.

[Geert Bellekens]

I agree, but in the meantime please don't elimitate the possibility of having multiple tagged values with the same name.

Geert

[Eve]

Another thing is that I quite like the visual side of multiple tagged values essentially showing as a list.  Especially when showing them on a diagram.

Geert, there's no chance of multiple tagged values being eliminated because of the impact it would have on users who have used that feature.

Note: I'm not saying that usability of multiple values within a single tagged value couldn't be improved.

[beginner]

Note: I'm not saying that usability of multiple values within a single tagged value couldn't be improved.

Sure. It's just that over time you get used to strange situations so you think it's normality. We once used that CCC from Paolo. Up til now I'd say that EA is consistently inconsistent ;-)

b.

[Paolo F Cantoni]

Note: I'm not saying that usability of multiple values within a single tagged value couldn't be improved.

Sure. It's just that over time you get used to strange situations so you think it's normality.

Yes, we're like the reptile being slowly warmed to boiling point...

We once used that CCC from Paolo. Up til now I'd say that EA is consistently inconsistent ;-)

b.

I guess that's worse than being inconsistently inconsistent!  

Paolo