User Guide - Mks.com

Chapter 6: Member Operations
Pending
Operations
204
Deferred Drop
When resynchronizing a member associated with a deferred drop,
where the working file is modified, Source Integrity asks you if you
want to overwrite the existing working file.
Deferred Rename
When resynchronizing a member associated with a deferred rename,
Source Integrity asks you if you want to overwrite the existing
working file. If the new working file is missing, Source Integrity
resynchronizes it. The working file with the old name is then deleted
from the sandbox.
Deferred Checkin
When resynchronizing a member associated with a deferred check in,
Source Integrity asks you if you want to overwrite the existing
working file.
Deferred Update Revision
When resynchronizing a member associated with a deferred update
revision, Source Integrity asks you if you want to overwrite the
existing working file.
Deferred Import
When resynchronizing a member associated with a deferred import,
Source Integrity asks you if you want to delete the existing working
file.
For additional information on resyncing members, see “Resyncing
Members” on page 197
If change package reviews are mandatory, then pending operations are
created when deferred operations are submitted either individually, or as
part of a change package (see “Submitting Deferred Operations” on
page 202 and “Submitting Change Packages” on page 238). Pending
operations correspond to pending entries in the associated change
package.
Pending operations are operations whose proposed changes reside on the
server, but have not been committed to the repository.
The changes are committed to the repository once the change package is
accepted upon review (see “Change Package Review Process” on
page 240). Pending operations can create pending revisions and members
(see “Working With Pending Revisions” on page 335).
u s e r g u i d e