You must already have created the relation attribute before defining the transition.
You can save the CR process only if you have already defined the first state and transition for CR submission.
There are three types of transitions: regular, copy (duplicate), and submission.
To modify transitions, click Edit buttons instead of Add buttons.
To add, modify, or copy transitions:
A regular transition is a submit, a transition between states, or a transition for creating a parent-child CR relationship.
Typically, customizers label the first transition Submit and label child CR COPY transitions Create.
If you are defining a Submit transition, click START_HERE. If you are defining a child CR COPY transition for creating a child CR, click COPY. For any other type of transition, click one of the states you defined previously.
If you are defining a Submit or child CR COPY transition, in To State, select a state (for example, entered). For any other type of transition, click one of the states you defined previously.
The child CR COPY transition name is COPYrelation_name2to_state. When you include the relation_name attribute in a customized dialog box definition, users see a Create and Show UI control on the dialog box.
Select this option to require that users input specific information (which you define) before the transition can occur.
To designate a primary transition, select the Primary Transition check box. A primary transition is the typical path through the lifecycle from a given state. After a primary transition is selected, it is shown first and in bold in lists of transitions for a CR.
You cannot designate a primary transition without selecting Show transition in the interface.
If you used earlier releases of IBM® Rational Change or relied on naming schemes to order transition links, you might see a change in behavior. Sorting of the links is now based on the primary transition properties and the label. Only one primary transition per "From State" can be specified. There is no general ranking of transitions.
A copy transition is a transition for creating a duplicate of a CR without creating a parent-child CR relationship.
Typically, customizers label the copy transition Copy.
This COPY transition copies the current CR to a new CR without creating a parent-child relationship. The COPY transition name is COPY_NONE2to_state. When you include the NONE attribute in a CR Information dialog box definition, users see a Copy UI control on the dialog box.
Click START_HERE to create a Change Request Submission dialog box.
For steps, see Defining a Change Request Submission or Transition dialog box.
Use this subdialog box to allow transitions only when an attribute of the change request object has a specified value (equals), or when it has a value that is not equal to the specified attribute.
For example, if the change_type attribute can be set to either defect or enhancement and you have (one-step) fix_defect and make_enhancement transitions, define the following branching security rules:
For transition name fix_defect: Set Name to change_type and Value to defect.
For transition name make_enhancement: Set Name to change_type and Value to enhancement.