User Guide - Mks.com

Chapter 6: Member Operations
Submitting
Deferred
Operations
202
You can simultaneously defer rename and check in operations on a single
member. When these deferred operations are submitted, Source Integrity
first performs the check in operation followed by the rename operation.
The sequence for performing these operations is set by default and is not
configurable.
If change package reviews are mandatory, ensure that the deferred option
is enabled in command dialog boxes, or Source Integrity creates pending
entries (and if necessary pending revisions) at the time the command
operation is completed rather than when the associated change package is
submitted. For more information, see “Change Package Review Process”
on page 240.
IMPORTANT
When adding multiple deferred operations on the same member to a change
package, only combinations of deferred check in and deferred rename
are possible.
To submit, or complete, a deferred operation, you use the Member > Submit
command. Submitting the operation completes the command and makes it
visible in the associated project.
If change package reviews are mandatory, when you submit deferred
operations using the Member > Submit command, pending entries (and if
necessary pending revisions) are created. You must still submit the
associated change package for review before the changes are committed to
the repository. For more information, see “Submitting Change Packages”
on page 238 and “Change Package Review Process” on page 240.
To submit a deferred operation in the graphical user interface
1 From a Sandbox view, select the member with the deferred operation
you want to submit (for example, a deferred check in, add, drop, or
rename operation).
2 From the menu bar, select Member > Submit.
The Submit dialog box opens.
u s e r g u i d e