User Guide - MKS

Chapter 6: Member Operations
Locking a
Member
186
3 To resynchronize the member, click Yes (for multiple members, click
Yes to All).
The selected member is updated.
If the working file of the member you are resyncing has been
modified, Source Integrity asks you to confirm that you want to merge
your modifications into the working file. For more information on
merging on a resyncing, see “Automatic Merging on Resync” on
page 320.
Locking a member prevents more than one user from simultaneously
making changes to the same revision. When a revision is locked, no one
other than the locker can check in changes to that revision.
Normally you lock a member during a check out. Sometimes, however,
you may have made changes to a working file that was not checked out in
your name first. In this case, you can set a lock without overriding your
changes.
In the graphical user interface, a locked member is denoted with a padlock
symbol ( ), along with the locker’s name, and the date and time the
member was locked.
The person who has a revision locked is referred to as the locker.
NOTE
Locking a member does not affect the working file in any way. Source Integrity
does not make the working file writable if it was read-only, and does not verify
that it corresponds to the revision being locked. Make sure the working file
corresponds to the revision you want to lock.
To lock a member in the graphical user interface and Web interface
1 With a Project or Sandbox window open, select one or more members
to lock.
2 Do one of the following:
Select Member > Lock.
Click .
If your administrator has enabled the integration with
Integrity Manager and set the option for IMTrackLocksEnabled,
Source Integrity opens the Lock Revision dialog box.
u s e r g u i d e