User Guide - MKS

Deferring Member Operations
Deferring Member Operations
For certain operations in Source Integrity, you can defer the completion of
the command until a later time. The defer option allows you to see the
effect of the operation in your sandbox without affecting the project. The
deferral of operations is provided as a selectable option in two ways:
through the graphical user interface and in the command line interface as
the --defer option.
You can apply the defer option to the following operations:
adding a project member
dropping a project member
checking in a member
renaming a member
TIP
You can also apply the Deferred Items filter to display any members that are
associated with deferred operations. For more information on using the
Deferred Items filter, see “Using Filters” on page 83.
A deferred member is a member that is associated with any deferred
operation (add, drop, check in, rename). A deferred member appears in the
sandbox, but the deferred operation is not shown in the project until the
deferred operation is submitted.
Deferred operations are visible only from the client-side sandbox and are
seen in the project only when they have been submitted. It is important to
note that deferred operations can be added to a change package and then
submitted as a group of changes, but the deferred operations do not appear
on the Integrity Server until they have been submitted to the project. For
more information, see “Submitting Change Packages” on page 221.
With the exception of deferred rename and check in operations,
Source Integrity supports only single deferred operations on a member. If
you try to perform multiple deferred operations on a single member,
Source Integrity reports an error.
NOTE
Once you have specified a deferred operation on a member, Source Integrity
does not allow any further operations that would cause that member to be
modified.
189