User Guide - Mks.com

Locking Multiple Revisions
Locking Multiple Revisions
Locking a revision ensures that no one else can modify that revision. In
some cases locking more than one revision in a member history at the same
time is required.
Cases where you may require multiple locking include:
You are working on both the main branch of development (where new
development is occurring) and in a variant sandbox (where fixes are
occurring)
You are working in two variant sandboxes and need to modify a
different revision in the same member history in each sandbox
You are sharing the member history across many projects and need to
modify a different revision in the same member history in each
particular project
Locking multiple revisions triggers variant branching when necessary. For
example, if you are working in a variant sandbox that does not already
have its own branch, Source Integrity prompts you to create the branch.
Source Integrity then moves the variant and the variant member revision
to that branch. For information on working with variant sandboxes, see
“Creating Variant Sandboxes and Development Paths” on page 146.
NOTE
Your administrator must explicitly set the locking policy to allow locking
multiple revisions. See your administrator to find out if your system is
configured for multiple locking.
Multiple Lock Procedures
There are several ways to lock multiple revisions. The following sections
outline the procedures you can use.
To lock multiple revisions in the graphical user interface
From the Member History view:
Follow the procedure for Locking a Revision (see “Locking Revisions”
on page 324). Repeat to lock other revisions.
Follow the procedure for Checking Out a Member (see “Checking Out
a Member” on page 178) by specifying the revision number (Member
History view via the Sandbox view only). Repeat to check out and lock
other revisions.
327