Defining configuration templates

Defining a configuration template tells Change Management for Rational® DOORS® how to locate the change management server. It also defines how the installed change request process maps to the concepts used in the change management feature.

About this task

For help in defining your configuration templates, see the customization guide for your change management system.

Procedure

  1. On the main menu, select Change Management > Define Configuration Templates > Create. The Configuration Template - DOORS window opens and displays the Step 1 Configure Rational Change Management Server tab.
  2. In the Template Name field, type the template name.
  3. Select the method of authentication, either basic access authentication or Open Authorization (OAuth).
  4. Based on your authentication method, perform one of the following steps:
    • Basic access authentication
      1. In the URL for Change Management server field, type your server URL.

        For example: http://server:port/change/oslc

        Another valid option is https.

      2. Click Connect.

        Your change management login dialog box opens. Log on to your system to return to the Configuration Template - DOORS window.

    • OAuth
      1. Before creating a configuration template, ensure that you added the correct Collaboration Link, using the Remote Services tab on the DOORS Database Properties window.
      2. Under Rational Change Management Server Configuration, select the applicable service provider, and then click Next.

        The change management service provider log opens.

      3. Log on to the change management service provider to return to the Configuration Template - DOORS window.
  5. Complete all applicable fields in the Configuration Template - DOORS window.
  6. Click Next to display the Step 2 Requirements Change Management tab.
  7. In the Values section, complete all fields to set the values for the various states that are applicable to your change management process.

    Ensure that you use the name for each state as defined in the process or schema rather than the label.

  8. Based on the change management system that you are using, perform one of the steps:
    • If you are using Rational Change, go to the next step.
    • If you are using Rational ClearQuest:
      1. In Apply Action Attribute, check For ClearQuest.
      2. Type the name of the ClearQuest action that moves the record to the Applied state.
      3. Type the name of the ClearQuest action that moves the record to the Review state in Review Action Attribute.
      4. Go to the next step.
    • If you are using Rational Team Concert:
      1. Check For Rational Team Concert.
      2. Type the name of the Rational Team Concert action that moves the work item to the Applied state in your process in Apply Action Attribute.
      3. Type the name of the action that moves the work item to the Review state in Review Action Attribute.
      4. If you are using one of the delivered process templates, in the State Attribute field, typertc_cm:state. Or type the name of the attribute that contains the state if you created your own process.
      5. Go to the next step.
  9. In the RCR Submit Form field, select the applicable submit form in your change management process that is used for requirement change requests.
  10. In the Conflicting Proposal Behavior field, select one of the following options:
    • Take no action
    • Warn user of conflict: when users make changes that will cause a conflict, a warning message is displayed. The user can make or cancel the change.
    • Prevent modification: users cannot make changes that will cause conflicts.
    Note: Selecting any setting other than Take No Action causes a slight delay when you open the modules to edit them.
  11. Select the Show RCR Recording Report option to show the RCR Recording report.
  12. To enable the Reject button on the Rational DOORS Web Access Requirement Change Management page, in DWA, select Enable Reject button.
  13. Click Next to display the Step 3 Requirements Implementation tab.
  14. For all fields, select those options that are applicable to your change management process that is used for implementation requests.
  15. Click Next to display the Step 4 Requirements Gathering tab.
  16. In the Default Query String field, type the Open Services for Lifecycle Collaboration (OSLC) style query string to be used during requirements gathering.

    Skip this step if you are not using the requirements gathering feature.

  17. Click Next to display the Step 5 Finish tab.
  18. In Template Summary, review the selections you created, and then perform one of the following steps:
    • If the information is correct, click Finish to save your configuration template.
    • If you need to correct the information, click Back to return to the correct tab. Then, make the necessary corrections.

Feedback