Updating a shared repository from an offline copy

[Guillaume]

Hi,

I have a shared EA repository on a DB available via the PCS with the EA Security enabled.
A number of users work remotely and complained it was slow via the VPN so they took a local copy of the EA repository so they can work offline and carry updates locally, before submitting these changes to the shared repository.
This requires some governance and I wonder if the following is sustainable:
- With the shared EA repository opened, the user creates a lock on the package branch to update (no one else can edit it from then)
- A project transfer is carried out to generate a local copy of the full EA repository in a QEA file (SQLite)
- The user opens the local file and locks all packages but the one to update to make sure no modification is carried in other packages
- The user carries the changes locally
- Once the updates are done, the user exports (XEA or XMI) the package matching the locked branch
- The user opens the shared repository and runs an XMI or XEA import on the locked/edited package (XEA should be used as it's quicker but I'm not sure if there's any difference in terms of model update/merge).
- Once the import is over, the user can remove the lock

Any feedback is welcomed.
Thanks

[Eve]

Personally I wouldn't trust my users to follow that process correctly.

That's what the version control integration is designed to do.

Version control the entire branch - https://sparxsystems.com/enterprise_architect_user_guide/17.1/modeling_fundamentals/applyingvctobranches.html
Create the copies of the model that you need.

From that point the package is locked until someone checks it out either on the shared model or their private model. The process for a change on the local model is then:

- Get All Latest on the private model
- Check out the package
- Do the work
- Check in the package changes
- Run a GetLatest on the shared model

Users in the shared model follow the same process without the first and last steps.