Configure transition criteria for an object in a certain lifecycle state to move to a new lifecycle state. You can also determine actions that are automatically triggered by the state change.
Note: This feature is available in Autodesk Vault Workgroup and Professional.
When an object moves from one lifecycle state to the next, it is called a transition. For example, when a file in Work-in-Progress state is changed to a Released state, that is a state transition.
For each state transition in a lifecycle, you can configure the:
- Transition Criteria–Configure the property criteria that determines when a state transition can occur. For example, administrators can make it so that a file cannot transition to the next state without the Initial Approver property having a value.
- Actions that occur when the transition is made–Configure which events automatically take place when a successful transition occurs. For example, if a file moves to a new state, an automatic revision bump occurs.
- Access control permissions– Determine the groups or users that can execute a transition.
- Release Restrictions– From the Transitions tab on the Lifecycle Definition dialog, you can see the available transitions between each state and edit the settings for each transition.
Configure Transition Criteria
Use transition criteria to determine when a transition occurs. The transition will not happen until the criteria is met.
Add Transition Criteria
- In the Transition dialog box, select the
Criteria
tab. On the Criteria tab, define the criteria under which the transition can occur:
- If desired, filter which properties are displayed based on a certain entity class. For example, configure it so that only File Properties are shown in the Property drop-down.
- In the Property box, select the property.
- In the Condition box, select the condition.
- When appropriate, select a value from the Value box. Not all criterion definitions require an entry to the Value box.
- Click
Add.
The rule is added to the list in the text box below the Add button.
Tip: Use the Property Compliance property to ensure that all properties are in compliance before the transition can take place. This is an excellent rule to incorporate when configuring a transition from non-released state to a released state.
Remove or Replace Transition Criteria
- On the Transitions tab, select the transition that you want to modify and click
Edit.
- On the Transition dialog box, select the Criteria tab, and then do one of the following:
- Select the defined criterion from the text box, and click
Remove.
- Select the defined criterion from the text box, select new criteria from the Property, Condition, and Value boxes and click
Replace.
Boolean Operators (case insensitive)
You can use the following boolean operators when defining the transition criteria value.
and
|
Criteria includes x AND y.
|
or
|
Criteria includes either x OR y.
|
not
|
Criteria includes documents that do NOT have x.
|
Edit Transition Actions
Transition actions are events that occur when the transition is successful. If any error occurs during the transition to the next state, the action will not take place.
Access the Transitions tab
- In the
Transitions dialog box, click the
Actions tab.
- Select an entity class in the Filter drop-down to show only the actions available for that entity class (e.g., select Folders to only see actions available for folder state transitions).
Bump Revision
- If you want a revision bump to occur when the transition occurs, select one of these actions:
- Bump primary revision
- Bump secondary revision
- Bump tertiary revision
Note: Use-the drop-down arrow beside Bump Primary Revision to choose secondary or tertiary revision levels.
Or clear the check box to exclude the action for this transition.
Synchronize Properties
- If you want to synchronize properties with the Job Server, select one of these actions:
Or clear the check box to exclude the action for this transition.
Release Restrictions
The administrator can choose to restrict the transition to the release state of Vault objects based on the state of the dependent children, content, and linked data. Any data that is not in a released (consumable) state causes a restriction and prevents the transition of the select object(s).
Check that dependent child files are released
|
Verifies that state dependent children are in a released state.
|
Check that dependent child folders are released
|
Verifies that the sub-folders of a project folder are in a released state.
|
Check that contained files are released
|
Verifies that all files contained in a project folder are in a released state.
|
Check that linked files are released
|
Verifies that all linked files in a project folder or custom object are in a released state.
|
Check that linked folders are released
|
Verifies that all linked folders in a project folder or custom object are in a released state.
|
Check that linked custom objects are released
|
Verifies that all linked custom objects in a project or custom object are in a released state.
|
Check that linked items are released
|
Verifies that all linked items in a project folder or custom object are in a released state.
|
Check that children are not obsolete
|
Verifies that children objects are not in an obsolete state. The parent will not be released if any child items are obsolete.
|
Check that child items are released
|
Verifies that children items are in a released state.
|
Check that child items have been released
|
Verify that child items have a historically released revision.
|
Check that associated item file links are up to date
|
Verifies that all associated item file links are current.
Click the ellipses (...) button to specify only certain item file links:
- Primary File Links
- Secondary File Links
- Standard Component Links
- Primary Subcomponent File Links
- Secondary Subcomponent File Links
- Design Documents
|
Check that associated item file links are released
|
Verifies that all associated item file links are in a released state.
Click the ellipses (...) button to specify only certain item file links:
- Primary File Links
- Secondary File Links
- Standard Component Links
- Primary Subcomponent File Links
- Secondary Subcomponent File Links
- Design Documents
|
Create a Custom Job
Associate a custom job with a lifecycle transition. Two steps are necessary to create a custom job. First, an administrator adds a custom job to a lifecycle. Second, a programmer creates the job.
More information:
Create a Custom Job
Edit Transition Security
Determine who can make an transition occur by configuring Transition Security. Anyone with Modify access can invoke the Change State command on the object.
Tip: There is currently no command to retire a state. However, you can manually retire a state by denying everyone permission to perform a transition. This prevents files in other states from transitioning into that state. However, files can still transition out of the blocked state into a new one.
Manage Transition Restrictions
- In the Transitions dialog box, click the
Security
tab.
- When the
No restrictions on the transition
check box is selected, no security options can be defined for the transition. To add transition restrictions, clear the No restrictions on the transition check box if it is selected. Click
Add.
Add Members
Members or groups must be made available, and then added to the Current Members list to enable transition permission.
- In the Add Members dialog box, select members or groups from the
Select Members From
list to be added to the Available Members list.
- In the
Available Members
list, select members or groups to be added to the Current Members list, and then click
Add.
Remove Members
- In the Add Members dialog box, select members or groups in the Current Members list, and then click
Remove.
Modify Permissions on Existing Members
Important: Users must have Modify permission at the object-based security level to perform a change state.
- In the Add Members dialog, select the permission next to the member for whom you want to Allow or Deny access and select the new permission from the drop-down list.