User Guide - MKS

Chapter 11: The Integrity Manager Integration
342
4 View the change package in the Change Package window (see
“Viewing Change Package Details and Entries” on page 211). All
operations you do to address the issue will appear in this window.
5 As part of your development process, identify the members that are
affected by the issue. Add the members to the change package during
one of the following operations:
Check Out
Rename
Lock
Add Member
Drop Member
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 window.
6 When all of the development to address the issue is completed, submit
the change Package (see “Submitting Change Packages” on page 221).
All of the deferred operations are submitted
Any locked members are converted to deferred check in operations,
then checked in.
Although you can submit operations individually, or check in a
member without deferring it, submitting all of your operations at one
time ensures that no operations miss the development build.
7 Close the change package to signify that the work to address the issue
has been completed. 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 207 or “Finding Change Packages Using a Query”
on page 347).
8 In Integrity Manager, advance the issue through the workflow. At this
point, the verification phase begins. If it’s determined that more work
needs to be performed to address the issue, the technician moves the
u s e r g u i d e