MKS Implementer 2006 Administration Guide

Chapter 5: MKS Integrity Integration
240
7 In the When rejected from this env field, specify the MKS Integrity state to assign to an
item rejected from this environment.
NAME Specify a valid MKS Integrity state name to override the global
value if defined. Valid for *QAC environments only. The name is
case sensitive.
*DEFAULT Assigns the default global value defined in MKS Integrity State
Setup. If the default is not set, no updates occur. This is the default
value for all environment types.
The state is set as follows: If rejecting from this environment and it
is the first *QAC environment on the path (the path used to
promote from the current location), assigns the *QAC1 default
state. If rejecting from this environment and it is the second *QAC
environment on the path (the path used to promote from the
current location), assigns the *QAC2 default state. This cycle
continues for each *QAC environment.
*NONE No updates occur.
8 Press ENTER to update the environment information. The Work with Environments
panel displays.
IMPORTANT The following setup tasks are required to promote Implementer
requests from within MKS Integrity. If you do not intend to use this alternate
promotion feature, go to “Converting From DesignTracker to MKS Integrity” on
page 243.
Updating Issues Based on Promotion Status
The Update MKS Integrity (IUPDCI) command allows you to change the state of an issue
based on the promotion status of objects in a change package. This process keeps
MKS Integrity synchronous with the development cycle by triggering an issue state change
based on promotion activity. For example, you may want to set the state to “Failed QA”
when a move to QA fails. This is an optional feature.
The IUPDCI command is invoked as an Implementer “After Move-OK” special command for
each environment you want to trigger the state change.
After connecting to the source iSeries and retrieving a list of all issues associated with the
promotion request, the mass update of issues to the specified state occurs. The state change
occurs only after all objects contained in the change package have reached the new location
(QA or production). All issues in the change package must be promotable to the given state.
MKS Integrity allows for an unlimited (and possibly recursive) number of relationships. The
IUPDCI command uses a commit/rollback processing architecture, whereby the status
update occurs only when all issues associated with the specified promotion request are at a
state that allows the update. If any one of the issues do not update, then no issues update.