MKS Implementer 2006 Administration Guide

Field Description
User Profile Setup
MKS Integrity State Detail Field Descriptions
Implementer and MKS Integrity Integration
Issue state when rejected Issue state to set when an item in this promotion path location is
rejected. Must be a valid state in MKS Integrity.
Applies to *QAC path entries only. If this value is left blank, the issue
state remains unchanged when rejected.
For each Implementer user that uses the integration, you must define an MKS Integrity user
profile and specify whether the user has authority to activate MKS Integrity emergency
mode. In addition, each user that performs an Implementer check out or promotion for items
associated with an MKS Integrity issue must have a valid user profile in Implementer and a
valid user ID in MKS Integrity.
The user’s profile can be the same for both products or it can be different. By default,
Implementer uses the iSeries user profile, which may or may not be the same as the
MKS Integrity user ID. If the MKS Integrity user ID is different from the iSeries user profile,
you can optionally define the appropriate MKS Integrity user ID to Implementer. This allows
all integrations with MKS Integrity for a user to consistently use the value specified. There is
no requirement that the password be the same.
MKS Integrity Emergency Mode Authority
In the event MKS Integrity temporarily cannot be contacted to perform the integrations,
Implementer provides a facility that allows the check out and promotion functions to
continue uninterrupted. This is accomplished by activating Implementer’s emergency update
mode.
For example, let’s say you have changes on an active request that must be promoted
immediately to correct a level check problem in production, but a communication failure
between Implementer and MKS Integrity has caused the promotion to fail. By activating the
emergency update mode, you can continue with all required development activities, while
storing the issue updates for subsequent posting once the communications are re-established.
IMPORTANT When emergency update mode is active, Implementer is unable to
validate MKS Integrity information. Thus, any issue number is accepted in check
out, including invalid numbers, and every promotion is allowed even if the
workflow or capabilities normally prohibit it. For this reason, operating in
emergency mode is not intended as a normal disconnected mode—rather it is for
emergency purposes only, such as when a production environment is down and
must be updated to be active again.
Users must be authorized to control the emergency update mode; for security reasons, no
users are authorized by default. Typically, emergency mode authority is given to select
development managers and senior developers. Once authorized, the user activates and
235