User Guide - MKS

Viewing Which
Sandbox
Locked a
Member
Creating Variant
Sandboxes and
Development
Paths
Working With Sandboxes
You can also open a sandbox from the Registered Sandboxes dialog box.
With the Registered Sandboxes dialog box open, select the sandbox you
want to open, and click Open, or select Open from the shortcut menu. The
sandbox appears in a sandbox window.
You can view which sandbox locked a member from the Member History
view, Locks view, Project view and Sandbox view, by setting the view
preferences to display the information. For more information, see “View
Preferences” on page 59.
While a regular sandbox is based on the current state of the project, a
variant sandbox is based on a previously checkpointed revision of the
project. When you create a variant sandbox, you choose a checkpoint
(snapshot) of your project and use it as the starting point for a new branch
of development. Source Integrity allows you to do this by defining a new
development path.
NOTE
You must define the development path before creating the variant sandbox.
A development path is an identifier given to a new branch of software
development. Changes made through the new development path are kept
separate from the main development trunk unless you choose to merge
them later.
Source Integrity allows multiple developers to point to the same
development path, each using their own variant sandbox. In the variant
sandbox, you can see the current state of the project along that
development path and the changes made by other developers using it.
139