I was presented with an issue a few weeks ago where the PDF that ws automatically created by the Job Processor on a Lifecycle State change did not have the same Revision number that the IDW had.

This was probably due to the fact that the user running the Job Processor and creating the PDF did not have adequate permissions to modify at the Released state in a particular lifecycle. When this happens these are the steps you need to take to make sure that everything is in sync and working properly from the Vault admin side.

First check to see which user has been assigned to run the Jobs in the Job Processor. In the below, you will see that the administrator user has been assisgned. You can also create a user named Job Processor to better keep track of the Job Processor user as you might have many different users utilising the Vault.

Once you have identiied the user make sure that they have the correct permissions at the lifecycle state that the job processor is trying to make modifications. (to create the PDF) For the creation of the PDF’s automatically from Vault you need to look at the Design Representation Process Lifecycle.

This Lifecycle controls the PDF’s at a certain stage and the user that is running the Job Processor would need to have download and modify permissions for the Release Lifecycle as per the below image.

Once these permission have been assisgned, if the PDF and IDW had different revision numbers, you can manually create the PDF and the Revision numbers would be the same.

Still looking for answers? Start a discussion with other professionals in your industry!