MKS Implementer 2006 Administration Guide

Chapter 5: MKS Integrity Integration
208
Manage States and State-based Capabilities
Throughout the product development lifecycle, issues submitted in MKS Integrity follow a
workflow. You can customize the workflow and the stage the issue is in. These stages are
states in MKS Integrity. For example, your process may include resource allocation, research,
coding, quality assurance testing, and production. Or your process can be more elaborate.
Further, each issue type can follow a unique workflow.
State Usage Within Implementer
In Implementer, promotion path entries are used to designate the different development
locations. They also correlate to states in MKS Integrity, and define the default mapping
between Implementer environments and the state of issues for members in those
environments.
Implementer has three default promotion paths: *TST, *QAC1, and *PRD. You can create
additional *QAC paths as needed, for example, *QAC2, *QAC3, *QAC4. Promotion path
entries are defined in the MKS Integrity State setup, option 47 from the Implementer Menu.
NOTE For details on MKS Integrity state setup in Implementer, see “State Setup in
Implementer” on page 232.
Implementer State-based Capabilities
In MKS Integrity, you assign Implementer capabilities to the states used during Implementermanaged
development. State-based capabilities correlate to the Implementer promotion path.
They define the Implementer functions (check out, promotion, and rejection) that are allowed
or not allowed for members while an issue is in a defined state.
The following state based capabilities (state transitions) are created in MKS Integrity after
you run F8=Configure MKS Integrity from Implementer’s MKS Integrity State Setup panel
(as described on page 233). The capabilities are based on the default path entries in
Implementer.
allows checkout to a development environment in Implementer
allows promotion to QAC environment number 1 as defined in the development path in
Implementer
allows rejection of changes from a quality assurance environment back to a development
environment in Implementer
allows promotions to a production environment in Implementer
The following example shows the state based capabilities that apply to the following
workflow:
Submitted > Checkout > QA1 > QA2 > In Production