Update merged objects

Hello Mr Günzburger,

you were told correctly. The answer is as simple as can be: Repeat the merge from the master database to the copies. Each ARIS object possesses a technical GUID (128 bit hexadecimal string), which never changes in its life-time. Not even, when you change its name or merge it to another database, where its copy might start a life of its own.

So with the new merge you have to specify "source overwrites target" and every object will be updated.

Issue: If some objects in your master database are discontinued (deleted, obsolete, not to be used any more), how would you propagate that to the copies? If you delete the master, the copies will continue their lives, just they don't receive any updates.

Solution: Don't delete roles in the master copy. Instead use an attribute of your choice to mark them "deprecated". This will be propagated to the copies upon merge.You might use a template to place an occurrence of this attribute everywhere the role occurs and anyone using the object will see it is deprecated and should be replaced. I suggest a nice big red "X" attribute symbol placed across the object symbol.

Regards, M. Zschuckelt

Thank you Mr. Zschuckelt for your explanation. We will try to implement what you propose.

regards

B. Günzburger