Purging

Learn about purging file versions in Vault.

As files in the vault are worked on over time, versions are created, taking up room in the vault. The versions range from the initial draft version, to versions representing work in progress to the final version. Using the Purge Wizard, you can manage the version history in a vault. Versions that are no longer needed can be purged from the vault, creating a more compact vault database and improving the overall performance of the vault.

The Purge Wizard allows you to specify criteria for removing versions from a vault. You specify the conditions that must be met in order for a file version to be kept in the vault. Versions that do not meet the specified criteria are then removed from the vault.

Purging rules can combine and apply to files. For instance, if there is no change in the lifecycle state but changed Revisions only, then the first version of the revision can be purged if the "Last" option is set for that state under the Control preferences. See Edit Lifecycle State Control for configuring your purge preferences for files assigned to a lifecycle definition to help manage Vault file retention.

Basic rules of purging:

• The latest version in a revision can't be purged (this revision is never removed). To remove a file and all its versions from a vault, use Delete.

• File versions that are labeled can't be purged.

• Files that are currently checked out can have their older versions purged.

• Children with a dependent parent version cannot be purged until the parent version has been purged.

• The Administrator role has a further restriction, and a version can't be purged if a parent exists and is not part of the existing action set.

• For Autodesk Vault Professional:

  • File versions linked to items in Vault Professional cannot be purged. To remove a version linked to an item, the item must first be deleted from the item master.
  • File versions marked as Controlled by the lifecycle definition may not be purged.
  • Files are purged based on revision and lifecycle rules. Configure the Version Selection Criteria section in the Purge dialog to purge files that are not controlled by a lifecycle.
  • Files without a revision scheme are considered a "null" revision and are not purgeable when configured with a lifecycle. To purge based on lifecycle control rules, a revision scheme must be assigned to the lifecycle, and the target of the purge must utilize the revision scheme.
  • Files are purged based on the state transition action. If the Purge action is enabled under the lifecycle state transition action, the corresponding state change will trigger a purge for the changed files.