User Guide - MKS

Why Use Change Packages?
Change packages provide the following advantages:
Why Use Change Packages?
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.
Since a change package is stored with each new revision, there is a link
between every change in the repository to the related changes made
by the author. If Integrity Manager is enabled, there is also a link back
to the issue that provides the context for why the particular change
was made.
Using change packages with the track locks feature, managers are able
to monitor work in progress.
Groups of changes can be reviewed as a unit.
TIP
You can expand the capabilities of change packages with Integrity Manager to
take advantage of workflow and process management through the use of
issues. The change packages can then be associated with issues. Enabling the
Integrity Manager integration also permits multiple change packages for each
issue. For more information, see “The Integrity Manager Integration” on
page 339.
201