I wasn't clear enough. My point applies to BOTH sequential and parallel streams. Each clone knows the predecessor clone, but NOT which version it was cloned from!
Say I have versions 1 to 5 in the model and the diagram I am using to clone has #2. When I say clone to a new version it will place #5 on the diagram.
Now it doesn't know it came from #2 - so it can't revert to #2. I'm not sure that reverting to #4 is what you're after.
I'm still not in complete agreement, but I think I see the problem here.
When you clone an element in a diagram, EA only replaces the predecessor with the clone
in that diagram. I was unaware of this. This means that in a derived version of a model, you can have some diagrams with the clone and some with the predecessor (or not even "the" but "a" predecessor, chaining all the way back to the original).
This is insane.
If when cloning, the predecessor were replaced in all diagrams in the version of the model where the cloning takes place, and new relationships were created accordingly, the situation where both a clone and a predecessor are shown within the same model version could not arise. (At least, not without deliberately breaking the model.) And thus, reverting becomes possible.
Serious discussion! but just wondering how about a baseline of the source and the target packages before cloning, and use that to revert back? ideally automated, but in absence of which can it be a manual effort?
Only if the baseline functionality becomes time-aware.
At present, even with the best possible setup for baselines and TAM to coexist (a package which holds the baselines and only contains the original model package and its TAM clones, with no TAM clones existing outside that package), you can't use the baseline comparison function to see that one element is a clone of another. You only see a new element (the clone), with a new connector to a changed element (the predecessor).
The restore from baseline function would probably also need to understand what a TAM-clone is, and there would certainly need to be a specific "revert" or "un-clone" menu item.
Again, my basic point is that TAM is not integrated with other EA functions, and it shows.
Y'know, the more I look at this the more this whole thing looks like a concept demo that was deemed good enough for a trade show which somehow got shipped with no consideration for the fact that EA elements exist independently of diagrams -- one of EA's core features.
/Uffe
