User Guide - Mks.com

Operations That Add Entries to a Change Package
Only the creator of a change package or a change package
administrator can close a change package.
Once a change package is closed, it can only reopened by a
change package administrator.
Operations That Add Entries to a
Change Package
Why Use Change Packages?
The following member operations add entries to a change package:
“Checking Out a Member” on page 178
“Renaming a Member” on page 194
“Locking a Member” on page 198
“Adding Members to a Project” on page 157
“Adding Members From Archive to a Project” on page 166
“Dropping Members From a Project” on page 172
“Checking In a Member” on page 186
“Updating a Member’s Revision” on page 293
“Importing Members” on page 169
“Apply CP Procedures” on page 398
Change packages provide the following advantages:
Change packages allow related changes to be grouped as a logical
unit.
Change packages allow work in progress to be submitted to the
repository (server) all at once (using submit change package), which
prevents users from partially submitting related work in progress.
Change packages provide a way to apply related changes to a project
or sandbox in one operation.
Using change packages, users are able to resync the changes required
to address a specific issue without resyncing the entire project.
215