Understanding Sheet Sets and Vault

 Sheet Set Manager (SSM) integration allows you to check in sheet set data into vault, and utilizing Vault existing capabilities.

Once you start working on a Sheet Set in vault environment, there are some changes to how certain Sheet Set commands work.

Resave All Sheets

When you work on a sheet set with vault, youa re working in a collaborative environment. When you resave all sheets, you will notice some differences when:

• Working in a shared sandbox environment, you can Resave All as long as none of the sheets/files involved is currently checked out by other users. The Resave All command will be aborted if there are files that cannot be checked out and, therefore, saved. A file may not be available for check out if it is currently checked out to another user or if vault constraints restrict access to the file.
• Working in a non-shared sandbox environment, you can Resave All even if some of the files are checked out by other users. You will get a list of files that are not available for saving when the sheet set command is completed.

Remove Sheet or Sheet Subset

When you remove a sheet or subset from a vaulted sheet set, its equivalent vaulted copy will NOT be removed automatically. As a result, if you were to re-use the same sheet or sheet subset name, you will be informed that the files already exist in the Vault.

If the removed sheet or sheet subset files are expired or redundant, you may remove them via Vault Client.

Note: Historical references from sheets or sheet set files are lost when they are removed with Vault Client.

Move, Rename, and Copy Design in the Vault Client

Move, Rename, and Copy Design changes made in the Vault Client are ignored when you open the edited sheet set in SSM.