Properties not being populated

[niels_halferkamps]

I'm having some serious issues with Vault pro not being able to do stuff that seems absolutely basic. 

I'm using vault pro and I've set up a change order workflow. I've made a custom property that says "Checked by" with a dropdown box where the ECO submitter can select a reviewer.

 As soon as the ECO is approved and completed i want Vault to GRAB THAT VALUE, and insert it into my Part/DWG property "checked by"..  That way my PDF will have its datablock populated as soon as i change the state to released and a PDF is created.

Can anyone help me with this?

[bassengineer12]

Vault does not have the ability to "auto populate" on a state change or any other trigger for that matter.  The user will have to change the value of the UDP.  You can setup a lifecycle transition that will prevent the transition if "UDP DOES NOT EQUAL YOUR VALUE."  If you do this, on the next "cycle" through the transition(s) you will have to "reset" this UDP to "blank/null" or other value. 

Here is a crude example, assume there are only 3 lifecycle states : WIP - REVIEW - RELEASED.  From REVIEW to RELEASED - on the CRITERIA tab I would have "CHECKED BY is NOT EMPTY"....then WIP to REVIEW, "CHECKED BY is EMPTY".  So that the next time through the transitions, CHECKED BY needs to be populated again.

[niels_halferkamps]

Thanks for the reply. Is there also no way to mass-change that value? I don't really want to edit properties for 100 drawings seperately.

[ihayesjr]

For clarity, Vault does not map Change Order properties to File properties. 

After a state change, you can trigger a property synchronization via the Job Processor. As an example, this can synchronize the new state's name and revision to a file property.

You can select multiple files in Vault and select Edit Properties from the Properties grid to change multiple files simultaneously.

[ProductivCADUser]

May I ask a quick question:
By quote: "....then WIP to REVIEW, "CHECKED BY is EMPTY".  So that the next time through the transitions, CHECKED BY needs to be populated again."

1. This basically means that the status change WIP to REVVIEW cannot be carried out if the value is not empty?
2. As far as I understand, Vault cannot “automatically” delete the value either. Specifically, the user must set the value “manually” to empty.
Vault does not offer an “out-of-the-box” solution to change custom properties during state changes?

[bassengineer12]

1. This basically means that the status change WIP to REVVIEW cannot be carried out if the value is not empty? Correct.  The user will see an error like "Some properties do not match etc..etc..."
2. As far as I understand, Vault cannot “automatically” delete the value either. Specifically, the user must set the value “manually” to empty.
Vault does not offer an “out-of-the-box” solution to change custom properties during state changes? No Vault cannot delete or populate any property values.  In this example, the user must change the property value during the WIP state before making the transition.