User Guide - MKS

Locking Multiple Revisions
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 139.
NOTE
Your administrator must explicitly set the locking policy to allow locking
multiple revisions. See your administrator to find out if your system has been
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 window:
Follow the procedure for Locking a Revision (see “Locking Revisions”
on page 294). Repeat to lock other revisions.
Follow the procedure for Checking Out a Member (see “Checking Out
a Member” on page 163) by specifying the revision number (Member
History window via the Sandbox window only). Repeat to check out
and lock other revisions.
From the Sandbox window, follow the procedure for Checking Out a
Member (see “Checking Out a Member” on page 163) by specifying the
revision number. Repeat to check out and lock other revisions.
To lock multiple revisions in the Web interface
From the Member History window:
Follow the procedure for Locking a Revision (see “Locking Revisions”
on page 294). Repeat to lock other revisions.
Follow the procedure for Checking Out a Member (see “Checking Out
a Member” on page 163) by specifying the revision number. Repeat to
check out and lock other revisions.
297