Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Configuring approver mappings in BMC Change Management

This topic describes how to configure the approval process assignments and approver mappings in BMC Change Management, to complete the integration with BMC Cloud Lifecycle Management. You configure approver mappaing after you have completed the BMC Cloud Lifecycle Management configuration tasks and have created the Cloud Provider company.

This topic includes the following sections:

Before you begin

  • The cloud administrator must have Infrastructure Change Config and Infrastructure Change Master permissions to update requests in BMC Change Management.
  • For the permissions to take effect, the BMC Remedy Enterprise Action Request Server host system, where BMC Remedy ITSM and BMC Change Management are installed, must have BMC Change Management licenses added to it.

To configure the approval process assignments

  1. On the Application Administration Console, select the Custom Configuration tab and then select Change Management > Advanced Options > Rules.

  2. On the Change Configuration Rules form, specify the assignment roles for the Assignment Engine Integration. 

    Note

    The approver mapping configuration is specific to the company. You can assign approvals to a specific group or to individuals based on different criteria, such as urgency or risk level.

    The round robin assignment selects the individual who is next in turn on a rotating basis.
    changeconfigurationrules_assignmentengine.png

  3. On the Application Administration Console, on the Custom Configuration tab, select Change Management > Approval > Approval Mappings. 

    Note

    The approver mapping configuration is specific to the company. You can assign approvals to a specific group or to individuals based on different criteria, such as urgency or risk level.

  4. On the Approver Mappings form, define the first and last name of the approver for the specified cloud change approval process. Click Enter to obtain the associated approver ID. Fill in the mapping details for the Impacted Area and the Configuration Item.
    change_approvermappings.png
  5. Under Additional Mappings, click the Advanced Criteria tab, and select the value for the Class field. In this example, the class is Standard.
    change_approvermappings_advancedcriteria.PNG

    With the above set up complete, you can create the requestable offering with one of the change policies, as described in Assigning-a-change-policy-to-a-service-offering. The mapping of the Change Class field for each change policy when the service offering instance is provisioned is shown below:
    • Change Approval Required = Standard
    • Pre Authorized Change = No-Impact
    • Audit Only Change = Latent

Your integration is complete after you complete the approver mappings.

In some cases, this procedure is a one-time configuration task. However, in cases where customer tenants are managing changes, then you would need to perform this task whenever a new tenant is onboarded.

Where to go next

Assigning-a-change-policy-to-a-service-offering

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*