Job processor property synchronization issue - "Initial Release Date" in AutoCAD

[johnsolu]

Our system is set up such that transitioning an AutoCAD drawing to the Released lifecycle state will cause a job processor property update. The "initial release date" property used to successfully populate the AutoCAD block that it is mapped to during this automated process. This suddenly and unexpectedly stopped happening.

Now when a drawing is promoted to released, the date is not populated. I know that it is still linked to the AutoCAD block because if I try to change it on a subsequent revision, it shows a property compliance error and Vault will change it if you launch Synchronize Properties manually.

This is causing some big headaches and I have no idea what changed. I know that 2018.2 is installed now, which may have been the point where things went south, but I can't be sure it coincided with that. Any help is greatly appreciated!

[Jason.Courtemanche]

Hi @johnsolu,

It was nice talking with you, just to recap we fixed the issue by adding the deleted role to the job processor user on the release state.

Also made sure that the properties mapping was set to create.

Regards,

Jason

[johnsolu]

Thanks for the help, it gets us by for now, but here's something new to puzzle over:

I couldn't remember why I needed to have all the create boxes for the property mappings set to "no", but now I do. If the drawing file does not contain that property, it sets off an equivalence error message as shown below. You don't see an "title-B-size.APPDATE" error in the list because it was the block used for that drawing file.

So what we do know is that if the "Initial Release Date" in the drawing is blank, then vault will not update that property when synchronizing unless it is set to "Yes" under the "create" heading for that property... but the side effect is that if it's a different block, it can't create the property in a file without the block so Vault has a panic.

Any ideas?

[johnsolu]

I should add that my workaround is to not enforce property compliance to change the lifecycle state, so it does function if I have the "create" set to "no" on the property mapping unless someone wipes the release date placeholder out from the drawing file completely.

[johnsolu]

This issue still persists and I have more insight as far as what is happening. When Vault notices that there is a property noncompliance for initial release date (as indicated by the tag and the exclamation point icon next to the file in the vault window) BEFORE the state is changed to released, the date will populate in the dwg and in the PDF  (through the job processor synchronize properties before publishing PDF). If there is no placeholder (that is, nothing in the "date" field in the drawing title block, a dash, or a MM/DD/YY placeholder), then Vault does not see any property noncompliance. Upon release, the properties are not updated and therefore, the date is not added to the drawing and PDF upon the job processor synchronizing properties.

Is there any way to get the vault and/or the Vault job processor to add the date upon release regardless of whether or not the property is compliant at the time immediately before it is released?

[johnsolu]

I'm still trying to figure out how to address this. The temporary workaround is becoming somewhat permanent, but no less annoying.