Adding, modifying, or copying transitions

You can add, modify, or copy a lifecycle transition. However, you must create states before creating transitions.

Before you begin

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.

About this task

There are three types of transitions: regular, copy (duplicate), and submission.

To modify transitions, click Edit buttons instead of Add buttons.

Procedure

  • To add, modify, or copy transitions:

    1. Display the CR Process dialog box.
    2. In the Lifecycles list, click a lifecycle.
    3. Under Lifecycles, click the Transitions tab.
    4. Optionally, add a regular transition.

      A regular transition is a submit, a transition between states, or a transition for creating a parent-child CR relationship.

      Note: Some options, specifically Copy Relation, are applicable only to copy transitions. For more information about defining lifecycles for child CRs, see Rational® Change Customization Reference, Release 5.2, which is the most recent version of this document.
      1. On the Transition tab, click Add.
      2. In the Add Transition subdialog box, type the label and description for the transition.

        Typically, customizers label the first transition Submit and label child CR COPY transitions Create.

      3. In the From State list box, click the starting state of the transition.

        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.

      4. If you are defining a transition for creating a child CR, in the To Lifecycle list, click the lifecycle to which to transition. Or accept Default Lifecycle (the current lifecycle).
      5. In the To State list box, click the ending state of the transition.

        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.

      6. If you are defining a child CR COPY transition, in the Copy Relation list, click the relation that associates the child CR with the parent CR.

        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.

      7. Optionally, select the Requires dialog check box.

        Select this option to require that users input specific information (which you define) before the transition can occur.

      8. To show the transition in a dialog, select the Show transition in the interface check box. Transitions not shown in the interface are available from the API.

        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.

      9. Click Update.
    5. Optionally, add a copy (duplicate) transition.

      A copy transition is a transition for creating a duplicate of a CR without creating a parent-child CR relationship.

      1. On the Transition tab, click Add.
      2. In the Add Transition subdialog box, type the Label and Description of the transition.

        Typically, customizers label the copy transition Copy.

      3. In the From State list box, click COPY.
      4. In the To State list, select a state (for example, entered).
      5. In the Copy Relation list box, select NONE.

        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.

      6. Click Update.
    6. In the Transitions list, click a transition.

      Click START_HERE to create a Change Request Submission dialog box.

    7. Define or modify the transition dialog box for the new or modified transition.

      For steps, see Defining a Change Request Submission or Transition dialog box.

    8. Add privilege-based security rules for the transition.
      1. Next to Privilege, click Add.
      2. In the Add Privilege Security subdialog box, in the Privilege Name field, type a privilege name or select an existing privilege from the adjacent list box.
      3. Click Update.
    9. Optionally, add attribute-based security rules for the transition.

      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.

      1. Next to Attribute, click Add.
      2. In the Add Attribute Security subdialog box, in the Name field, type an attribute name, or select an existing attribute from the adjacent list box.
      3. In the Privilege Name box, type the name. If you specify both the privilege and the attribute, both rules are used.
      4. Click Update.
    10. Optionally, add branch-based security rules for the transition.
      1. Next to Branch, click Add.
      2. In the Add Branch Security subdialog box, in the Name field, type an attribute name, or select an existing attribute from the adjacent list box.
      3. Select the appropriate operator, either equal or does not equal.
      4. Type the value the attribute must equal (or not equal) for the transition to occur.
      5. To apply privilege security, in the Privilege Name box, type a privilege name or select an existing privilege from the adjacent list box.
      6. Click Update.
    11. On the CR Process subbutton bar, click Save As.
    12. Click Save.

    Feedback