This documentation supports the 21.05 version of BMC Helix ITSM: Change Management. To view an earlier version, select the version from the product version menu.

Configuring additional mappings for Release Management

You can include additional approval mappings for Release Management. Select the criteria that should be met to map an approver to the approval phase, in addition to the information selected in Configuring approval mappings for change and release management. The approver is mapped to the approval phase if all the defined criteria are met.

Before you begin

Make sure you have completed the configuration described under Configuring approval mappings for change and release management.


The Approval Mappings form and its fields for Release Management are slightly different than for Change Management. Follow these instructions carefully.

Additional mappings for Release Management

  1. Open the Approval Mappings form.

  2. Use the CI tab to map approvers to the CIs associated with the release. 

    When you map approvers to CIs, you must specify how the CI is selected.

    Select on


    CI Type

    If you select on CI Type, you must select a specific CI type from the menu, for example, CI Type > System > Computer System.

    CI Name

    If you select on CI Name, you must enter a specific CI Name.

    To retrieve a list of CIs, place your cursor in the CI Name field and then press Enter. The CI Relationship Search window appears. Perform a search for a CI and then click Select. The CI Name+ and CI ID fields are then populated.

    The CompanyRegionSite Group, and Site fields in the CI tab apply also to basic approval processes. These fields correspond to the Release Location fields in the General tab in a release request.

  3. Use the Categorization tab to map approvers to services specified in the operational and product categorizations of the release. You can specify a company and a business justification (for example, Upgrade). 

  4. Use the Role tab to map approvers based on the support groups defined within the release. The fields in the Role tab apply to basic approval processes. 

  5. Use the Advanced Criteria tab to map approvers based on specific criteria. The fields in the Advanced Criteria tab apply to basic approval processes. 


    Risk Level 1 is the lowest and Risk Level 5 is the highest risk.

    The Approve if Risk and Notify if Risk fields work in conjunction with each other. You can use the Notify if Risk field to set up notification-only approvals based on risk level. Notification-only approvals are used to only notify a recipient and the recipient doesn't need to approve them or perform any action. You can also use the Approve if Risk <= field to set up approvals based on risk level. If no values are specified, the approval is generated for any risk level.

  6. Click Save.


    Approval mapping records are specifically for the Release Level processes.

Use the Approver Mappings form to set up individuals and groups as approvers for each approval phase of release requests, based on the approval process defined in the Approval Process Configuration form (such as configuration item).

Was this page helpful? Yes No Submitting... Thank you