Stores the current copy of the project and associated files in the Vault database.
Checking in a project creates a copy of the project in the Vault database. Any further changes to the project that are checked in, will generate a new version of the project and the changes will be recorded in the history of the project. If no changes were made to a project that is checked back in, the version history for that project is not incremented. This allows earlier checked-in versions of the project to be recovered if required.
To store the project, select Check In from the Vault tab.
If the project does not already exist in Vault, the Select Vault Location dialog opens. Select a Vault database folder or click New Folder to create a folder in the vault. Click OK.
If the project already exists within the
Vault working folder, the
Check In dialog opens. In this dialog the user can do the following:
- Select the Keep files checked out check-box. This saves the project in the database but the project remains checked out, allowing further modifications and analyses.
- Select the Close file and delete working copy check-box. This deletes the working copy of the project once it is checked in to Vault. You are notified if there are restrictions on a file that prevent it from being deleted.
- Add a check in comment.
Note:
- Once a project has been checked into Vault, renaming the project within Vault will break the file associations. The project can not then be opened.
- The Check In feature is disabled while an analysis is running.