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
Show More