User Guide - Mks.com

Creating a Change Package
4 As part of your development process, identify the members that are
affected by the issue. Associate the members with the change package
(see “Operations That Add Entries to a Change Package” on
page 215).
NOTE
You can only add change package lock entries to a change package through a
check out and member lock if lock tracking is enabled. For more information on
lock tracking, see your administrator.
The operations are listed in the Change Package view.
5 When all of the development to address the issue is completed, submit
the change Package (see “Submitting Change Packages” on page 238).
Any locked members are converted to deferred check in operations,
then checked in.
All of the deferred operations are submitted.
Creating a Change Package
Although you can submit operations individually, or check in a
member without deferring it, submitting all of your operations at one
time ensures that changes are submitted as a group.
If reviews are mandatory, the review process begins here. Do not
continue with the following step. For more information, see “CP
Review Workflow” on page 242.
6 Close the change package when the work to address the issue is
completed. The change package is moved to the Closed state, and the
change package disappears from the Manage Change Packages
window.
To find the change package and view its entries, see “Finding Change
Packages” on page 222).
You can create a change package from Source Integrity views and when
performing member operations.
You can also create change packages from Integrity Manager. For more
information, see the Integrity Manager User Guide.
217