Hello everyone,
I've got a scenario which doesnt seem to make sense. In Vault Pro 2014 (SP1, Update 2), my Engineering category has two lifecycles: Flexible Release and Buzzsaw Release, and the default lifecycle is Flexible Release. I also have rules setup so that when files are checked-in, they go to the Engineering category.
The Flexible Release is the same release cycle out of the box, and is set-up to "Sync Properties and Update View via Job Server" on transition to Release.
The Buzzsaw Release is setup so that there is an "autodesk.vault.projectsync.share" job on transition to Release (created by the Lifecycle Event Editor).
When a new file is checked in, I do a Change State, use the picker to change the lifecycle to Buzzsaw Release, and choose the Released state. The file does go to the Released state, but the autodesk.vault.projectsync.share isnt triggered, as evidenced by the Job Queue.
When I transition the file back to WIP, then Release it again, then the autodesk.vault.projectsync.share job is triggered.
I would have expected the autodesk.vault.projectsync.share to have triggered the first time around, but apparently it doesnt. Does this sound right?
Thanks and BR,
Carlos