ProjectSync "released" or "obsolet" Vault-data will be updated by JobProcessor from BIM

[christoph.lenzJVEK3]

By using ProjectSync for BIM360 Docs and Vault, the JobProcessor updates the files in Vault, if a new version has been uploaded to BIM. 

In case Vault-Data become released or obsolet, it should be necessary that the upload in BIM will be locked for these files! The problem is that the JobProcessor User needs all permissions (change, delete..). Therefore a new version in BIM results in a new version in Vault which is not allowed!

The only way to solve this problem out of the box would be a second JobProcessor with less permissions. This second JobProcessor would do the ProjectSync Jobs only, not more. But this results in inkonsistent data between Vault and BIM! The Vault user will see the right data and the BIM users the wrong "new" data.

There is no back-synchronization of the old and correclty Vault-File!

The ideas are:

- Improve the ProjectSync-Function of the JobProcessor. Check the state in Vault, deny new upload of inorrect files, make a back-synchronization to BIM

- Create a Job which can be used in state change so that the BIM-File will be locked by JobProcessor user!

- Make sure that the BIM-API will be updated to get access to be "lock-function". Then we would be able to build an own Job for idea no. 2. 

- Deliver the API of DesktopConnector so that we can build an own Job for idea no. 2.

@bastian.estner @Holger.Kloecker @AnJanson @antje.wiesner @johannes.dazertGZR3H 

[ihayesjr]

@christoph.lenzJVEK3 

Thank you for posting the idea. I do understand the request but because the two systems, Vault and BIM, do not have the same security and user management backend, it would be difficult to set security in BIM-based on the security in Vault. Project Sync only handles file transfers between the two locations. Metadata is not possible. 

[christoph.lenzJVEK3]

@ihayesjr 

Tanks for your answer. I do understand the technical difficulties and differences.

Nethertheless we would like to solve this requirement for our customers. Due to that we could create custom jobs which "lock" the data in BIM360 Docs by JobProcessor user. These jobs could be included in status changes. In the result the jobprocessor user would "lock" and "unlock" the data in BIM360. Indeed the BIM360 Docs API for BIM360 Docs doesn't contain any information about the "lock"-function. If your colleagues of BIM360 Docs were able to update the API, we will be able to build a custom service.

@Klaus.Loerincz @Markus.Koechl @klaus.katterbauer