Thank you very much for your detailed explanations. It helps a lot to
understand how Launch was designed and how to work with it more
effectively. Regarding the Google approach I guess their idea was that
the GTM user does not even need to know about branching and merging. It
is more like a WYSIWIG approach. If you select a workspace everything
you see, is just specific to the chosen workspace. I can imagine that
one can discuss many advantages and disadvantages when it comes to
finding out what...
Let me try to describe an example I currently confronted with.At the
moment being in the interface the rules and data elements lists show the
latest revision of each item belonging to Library A. There are Rule 1
(Revision 27) and Rule 2 (Revision 13). Same would apply to Data
Elements. Now I want to make changes to Library B that builds upon
previous revisions. My current workflow is the following:Navigate to
PublishingOpen Library BIdentifying Rule 1 (Revision 13) and Rule 2
Thanks for the explanation and the hint regarding revision comparision.
But that means if I (or two persons) work simultaneously on different
versions of a rule each one will and needs to create new revisions. In
the end this means that e.g. revision 1,2 are from V1 and revision 3,4
are from V2 and revision 5 from V1 again and revisions 1 to 5 do not
reflect a step by step evolution of the element. And currently working
on V1 I need to remember that revision 2 (and not 3 or 4) is the last
Yes, I want to make changes based on a previous revision not from the
latest. If I have different libraries that have changes of e.g. the same
rule I would see those as different branches of the rule. At the end
maybe one of those will be discarded or I chose to merge them.
I just saw that parts of this idea eventually reflect what i published
here: Make old revisions of elements editable in different development
libraries thebenrobb can you tell if what you are currently developing
will serve my needs or if my idea is still valid?
If I have different libraries I would like to be able to edit the
revisions of rules, data elements etc. in all libraries. Unfortunately
only the latest revision can be edited. And the latest revision is
always the same that is edited though the interface.Two options would be
could:"Set as latest revision" from the library interfaceSwitching the
Working Library shows the Revisions of the library in the interfaceWhen
editing e.g. a rule again saving would create a new latest revision.