When users send an assembly or drawing for review (Change status to "For Review"), there is no option in Vault to prevent its children from being modified. The only option is to make sure that all dependant/children are set to "For Review" as well, but this creates a loophole in the system (Users will never follow manual routines)!
This has caused problems for our customers, as components have been modified while the parent assembly/drawing have been sent for review. Files can be in a "For Review" state for several weeks, so a lot of changes can be performed during this time. As this is not a released state, there is no history in Vault - not good.
In the transition configuration (e.g. from "Work in Progress" -> "For Review"), there should be a configuration option like "Check that dependant child files also transition to this state".
Have anyone else come up with an alternative solution, while we wait for Autodesk to close this loophole?
I assume we are talking about document lifecycles here?
This should be possible now - you need to assign "In Review" as a released state and you can then enforce children as being in a released state as well in transition rules.
If we define "In Review" as a released state, it is possible to release/approve an assembly or drawing with its children still in a "For Review" state. This is not acceptable.
I will look at adding a request on the wishlist to modify transition rules, perhaps adding a separate condition specifically for state dependencies.
Would a flexible conditional rule like - "Check that dependent child files are <state name>" suffice here, meaning users could specify a lifecycle state rather than simply "Released"?
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.