User Guide - MKS

Chapter 6: Member Operations
Check In Dialog Box Options
Advanced Specifies the following advanced check in options:
Renaming a
Member
180
Author is the author name applied to the revision. If necessary, enter a name.
The user name specified in the Add Members command configuration appears
by default.
Update Member Revision Even on Branch causes Source Integrity to update the
member revision upon check in, even when the locked revision is on a different
branch.
In the Web interface only, select from one of the following options:
Select Yes to update the member revision.
Select No to not update the member revision.
Select Confirm to be asked for confirmation of the action to be taken.
Unexpand Keywords replaces literal values with keywords in the new revision.
Retain Working File (graphical user interface only) causes Source Integrity to
check in the working file and immediately resynchronize it. If this option is
cleared, the working file is deleted after it is checked in.
Revision Number specifies the revision number you want to assign to the
revision. By default, Source Integrity creates the next logical revision number, for
example, 1.1 to 1.2. Optionally, you can enter a revision number.
Force Creation of New Branch causes Source Integrity to create a branch off of
the revision you are checking in.
Save Working File Timestamp (graphical user interface only) sets the timestamp
of the revision in the history to the timestamp of the working file, rather than the
time of check in.
You can rename individual members while working from a Project or
Sandbox window. When you rename a member, member attributes are
copied from the old member name to the new member name.
The member’s archive remains the same, and points to the old member
name so that change packages, member histories, and project histories
continue to work.
You can defer the renaming of a member by selecting Defer Rename or
the si rename --defer command. For more information deferred
operations, see “Deferring Member Operations” on page 189.
NOTE
Because renaming a member effects a change on other users on the same
development path, the member you want to rename must not be locked by any
other user.
Renaming a locked revision in a variant project moves the lock to the duplicate
revision, even if the lock was generated in the master project.
u s e r g u i d e