The Change State dialog changes the state of files, folders, and custom objects. Multiple instances of any of those entity types can be acted on at one time. However, the Change State dialog does not support more than one entity type at a time. For example, the user cannot change state on a file and folder at the same time.
You can change the lifecycle for a file in the Vault stand-alone client or change the state of a file in the Vault add-in for Inventor and AutoCAD as well as the stand-alone client.
The Change State command allows users to modify the lifecycle state for a file or group of files. Changing the lifecycle state of a file enforces certain lifecycle behaviors configured by the Vault administrator in the Vault client. Examples of states include Work in Progress, Released, and Obsolete.
The relationship grid displays project data that was selected when the Change State command was chosen. The lifecycle definition and the lifecycle state is shown for each object listed in the grid and can be modified individually. Along the top of the dialog, the lifecycle definition filter drop-down, the lifecycle state drop-down, and the browse button are used for making bulk changes.
Choosing a lifecycle definition from the filter allows the user to make bulk state changes to all data that belongs to that lifecycle definition. Browse to another lifecycle definition to change the lifecycle definition that is assigned to the data in the grid. Only lifecycle definitions that are assigned to the category will be available in this dialog. The lifecycle state drop-down allows the user to change the state on more than one object at a time.
By default, all data in the relationship grid is checked by default and, as a rule, only the data that is checked is affected by the settings in this dialog. Any data that is unchecked ignores the changes that were set in the Change State dialog. See the Lifecycle Definition Filter and New Lifecycle State section for more information on these features.
Changes to data made in this dialog are shown in bold text. This allows the user to easily see what data is going to change based on the settings of this dialog.
To change the lifecycle state of a file, choose the lifecycle state drop-down and select the desired state. The per file lifecycle state drop-down lists all available states within the given lifecycle definition (for which a transition from the current state to the listed state is an allowed transition).
To change the lifecycle definition of a file, click on the "..." button in the lifecycle definition drop-down in the grid. A dialog display in which you can choose a new lifecycle definition for the file. The lifecycle definitions displayed in this dialog are all the lifecycle definitions assigned to the category to which that file belongs. When the user selects a new lifecycle definition and clicks OK, the selected file lists the new definition and its state is changed to the default state of the selected lifecycle definition.
This workflow is identical for project folders and custom objects as well.
The lifecycle definition filter drop-down contains all of the lifecycle definitions that exist for the project data listed within the relationship grid. This filter is used in conjunction with the lifecycle state drop-down. The two fields are used to update all data within a given lifecycle definition to a new lifecycle state. If the user wants to change all of the project data in a given lifecycle definition to a new lifecycle state, here's the workflow:
For example, if you want to change all files in the grid that are in the Basic Release Process to the Work in Progress state, choose Basic Release Process in the Lifecycle Definition Filter drop-down. At this point, no changes have been made to states within the grid. Next, choose Work in Progress from the lifecycle state drop-down. All files in the grid that have the Basic Release Process are changed to the Work in Progress state.
You can change the lifecycle definition of all of the project data in the file grid by clicking the "..." button to select a new lifecycle definition. The lifecycle definitions listed in select a Change Lifecycle Definition dialog are only those lifecycles which would be applied to every file in the file grid. That is, the dialog lists the intersection of lifecycle definitions that would be available for each file in the object grid. A lifecycle definition is considered available if that lifecycle is assigned to the same category as the object.
Once you select a lifecycle definition and click OK, all files within the grid are listed with the chosen lifecycle definition. Their states are also changed to the default state of the new lifecycle definition (unless the project data was already set to the chosen lifecycle definition).
The relationship grid has three views: Folder View, List View, and Design View
Folder View
List View
Design View
You can select which relationships are included in the grid display by configuring the preferences in the Settings dialog. Access the Settings dialog by clicking the Settings icon on the Change State dialog.
In the Settings dialog, you can choose whether dependents, attachments, or library files are included in the relationship grid for the selected data. You can also control whether parents are displayed as well and if other related documentation is also listed.
Settings dialog for Custom Objects
There is an option to include links to the Custom Object definition type. Only links to that custom object definition type can be included in the grid display.
You can also quickly select whether to include file dependents or parents for the selected files by clicking their respective icons.
As indicated in the previous section, links to entities can be included in the Change State operation. This allows a user to change the state of data that is linked into their project or custom object. For example, if a user has a Vault project configured that contains links to other folders, he or she can change the state of the folder, include sub-folders using the include dependents, and include any linked files by checking that box in the Settings dialog.
Links to data of other entity types cannot be included in the Change State event.
You can change the lifecycle definition assigned to Vault data directly from the existing one to a new lifecycle definition in one step, using the Change State command.
The Change State command is used to change the status of a Vault data and its related files by reassigning the lifecycle state. The Change State command can be accessed from three places:
Multiple Objects
Multiple files, folders, or custom objects can be selected for the Change State command. When multiple Vault objects are selected, Autodesk Vault examines the status of each object in the set. If any of the selected objects are not eligible for a state change, the Change State command appears unavailable on both the Actions menu and the context-sensitive menu.
Change a Lifecycle State
You can modify the lifecycle state for a file or group of files to enforce certain lifecycle behaviors (e.g., Work in Progress, Released, Obsolete). Behaviors for a particular state can be altered by an administrator in the Autodesk Vault Client.
Change a File's State
The Change State command allows users to modify a file or group of files' lifecycle state to enforce certain process behaviors. Examples of states include, Work in Progress, Quick Change, and Obsolete.
The Change State dialog box is displayed.
The Change State command allows users to modify a file or group of files to enforce certain behaviors. Examples of states include, Work in Progress, Quick Change, and Obsolete.
Modify a file to enforce certain behaviors with the Change State command. Examples of states include, Work in Progress, Quick Change, and Obsolete.
The Change State dialog box is displayed. The current lifecycle of the open file and lifecycle definition name are displayed at the top of the dialog.