How are IDs created? Will repository elements always be unique?

[Yost67]

Hi all,

I'm new to the coArchi plugin and we are experimenting with multi-user use of Archi. We experienced that if multiple people are changing the same diagram at the same time, the conflict resolution during Publishing wants us to choose one complete diagram version. All the changes in the other diagram version(s) are discarded. Even if they would not impact the changes made in the chosen diagram version (Eg, if 2 people add a different component to the same diagram, only one of those components survives the Publish)...

So we are now considering a work instruction that advices every user to start modeling on their own diagrams, and have sessions together with other authors to combine multiple diagrams into one overview diagram. While discussing this, we were wondering how IDs for repository elements are generated, and if this might result in conflicts during Publish/Merge operations. So if we are all creating Application Components in our own diagrams, will all these components have separate IDs when we are Publishing the diagrams to the shared repository? Or might locally created components share IDs with other locally created components (of the same type)?

Thanks for responding.

[Jean-Baptiste Sarrodie]

Hi,

we were wondering how IDs for repository elements are generated,

Ids are GUID and thus will be unique across models.

We experienced that if multiple people are changing the same diagram at the same time, the conflict resolution during Publishing wants us to choose one complete diagram version. All the changes in the other diagram version(s) are discarded. Even if they would not impact the changes made in the chosen diagram version (Eg, if 2 people add a different component to the same diagram, only one of those components survives the Publish)...

Yes, that's by design. Views are considered atomic objects in this context.

Regards,

JB

[Yost67]

Thanks for the quick reply!