Provide an option to synchronize properties directly on the Vault Client after a lifecycle state change, instead of relying only on a queued Sync Properties Job.
In many lifecycle configurations, a Sync Properties Job is triggered as part of state change transitions.
We currently experience problems when files are transitioned back to an editable state.
After the state change is completed, users can immediately start opening and checking out the affected files. However, the Sync Properties jobs may still be waiting for or being processed by the Job Processor.
This is especially problematic for large assemblies, where many Sync Properties jobs may need to be processed. If the user checks out files before the corresponding jobs have finished, the Sync Properties jobs can fail and the properties are not synchronized as intended.
Suggested Behavior
Provide an option within the lifecycle transition configuration such as:
Synchronize Properties on Client after State Change
When enabled:
- The lifecycle state change is performed.
- Property synchronization for the affected files is executed directly from the client. (Only for 'to Edit State'. With client-side property synchronization, the synchronization is performed in the context of the current user. Therefore, the user must have the required write permissions in the target state for all files that need to be synchronized.)
- The client waits until the required property synchronization has completed.
- Only after synchronization is finished does the user regain control and can start opening or checking out the affected files.
This would ensure that property synchronization is completed before the user can continue working with the transitioned files.
For large assemblies, the client should also provide appropriate progress information while the synchronization is running.
