User Guide - Mks.com

Chapter 8: Viewing and Editing Projects, Sandboxes, and Members
284
Former subprojects that are still in the sandbox view appear as
subprojects in the snapshot.
Source Integrity always uses the actual name of the member working
file for the snapshot.
You cannot take a snapshot of a sparse sandbox.
The Snapshot Sandbox command is performed on the entire sandbox,
independently of the filter used to display the contents of a sandbox.
Differencing can be performed between a project revision created by a
snapshot and another project revision (including revisions created by
a snapshot) in the project history, but the revision cannot be
differenced with the sandbox contents.
In order to specify an existing development path when taking a
sandbox snapshot, you must use the CLI. For more information, see
The Source Integrity Enterprise Edition CLI Reference Guide.
Members of a sandbox need to be associated with a corresponding
archive on the Integrity Server.
When recursing into subsandboxes, the snapshot represents exactly
the same directory structure and files of your sandbox. All subproject
elements become the same type and shared subprojects of different
types become shared subprojects of the same type.
When you snapshot a sandbox recursively that contains
subsandboxes, for those subsandboxes the snapshot creates a
branched project revision based on the revision of the subproject
captured in the last checkpoint of the master project (if one exists), not
the current revision of the subproject in your sandbox. Member
revisions are unaffected.
When you snapshot a sandbox non-recursively the subproject
elements refer to the exact type they were in the sandbox at the time
the snapshot is performed, so configured subprojects remain
configured. For more information, see “Configuring a Subproject” on
page 131.
The following is the recommended scenario for when to take a sandbox
snapshot in a development environment:
1 You are in a situation where you are working in a regular sandbox, but
should be working in a variant sandbox.
2 Instead of checking in your changes to the main development path,
check in (or merge in) your changes on a branch.
3 Snapshot the sandbox.
u s e r g u i d e