This documentation supports the 9.1 version of Change Management.

To view the latest version, select the version from the Product version menu.

Creating inherent group mappings (for BMC Change Management)

The Inherent Group menu lets you select a group specified on the Change form to be the Approval group, for example, Change Manager Group. The Functional Role menu lets you select a functional role for the approval, for example, Infrastructure Change Manager. These roles create individual approval entries for all people who have that functional role.

  • You can use the Inherent Group and Functional Role menus combined to limit the individual approval entries to the Inherent Group.
  • You can select an Inherent Group without a Functional Role; however, you cannot select a Functional Role without an Inherent Group.

With version 9.1.04 and later, a change request is auto approved if you have configured an Inherent Group/Role mapping and the members of the group do not have the required functional role. 

The following table shows the results of approvers that are generated based on the Inherent Group and Functional Role combinations chosen.

Approvers generated depending on the Inherent Group and Functional Role combinations chosen

Inherent group

Functional role

Approvers generated

Change Assigned Group

No functional role selected

Members of Change Coordinator Support group on change request with Infrastructure Change Approver functional role

Change Assigned Group

Infrastructure Change Approver

Members of Change Coordinator Support group on change request with Infrastructure Change Approver functional role

Change Assigned Group

Infrastructure Change Coordinator

Members of Change Coordinator Support group on change request with Infrastructure Change Coordinator functional role

Change Assigned Group

Infrastructure Change Manager

Members of Change Coordinator Support group on change request with Infrastructure Change Manager functional role

Change Manager Group

No functional role selected

Members of Change Manager Group on change request with Infrastructure Change Approver functional role

Change Manager Group

Infrastructure Change Approver

Members of Change Manager Group on change request with Infrastructure Change Approver functional role

Change Manager Group

Infrastructure Change Coordinator

Members of Change Manager Group on change request with Infrastructure Change Coordinator functional role

Change Manager Group

Infrastructure Change Manager

Members of Change Manager Group on change request with Infrastructure Change Manager functional role

Change Implementer Group

No functional role selected

Members of Change Implementer Group on change request with Infrastructure Change Approver functional role

Change Implementer Group

Infrastructure Change Approver

Members of Change Implementer Group on change request with Infrastructure Change Approver functional role

Change Implementer Group

Infrastructure Change Coordinator

Members of Change Implementer Group on change request with Infrastructure Change Coordinator functional role

Change Implementer Group

Infrastructure Change Manager

Members of Change Implementer Group on change request with Infrastructure Change Manager functional role

Change Requester Group

No functional role selected

Members of Change Requester Support Group on change request with Infrastructure Change Approver functional role

Change Requester Group

Infrastructure Change Approver

Members of Change Requester Support Group on change request with Infrastructure Change Approver functional role

Change Requester Group

Infrastructure Change Coordinator

Members of Change Requester Support Group on change request with Infrastructure Change Coordinator functional role

Change Requester Group

Infrastructure Change Manager

Members of Change Requester Support Group on change request with Infrastructure Change Manager functional role

Note

The Change Requester Group fields are not displayed in the Best Practice view. However, when the change request is created, the values of these fields are autopopulated with details of the user creating a change request and approval signatures are generated.

To create support group mappings

  1. From the Application Administration Console, select Change Management> Approval> Approval Mappings, and then click Open.
  2. In the Approval For field, select Inherent Group/Role.
    The Approval Mappings form redisplays, so that the fields to configure a group mapping appear.

    Inherent Group/Role fields displayed in Approval Mappings form

    Click the following figure to expand it.

  3. In the Inherent Group field, select a change management group (for example, Change Manager Group).
  4. In the Functional Role field, select one of the BMC Remedy ITSM functional roles defined for change management (for example, Infrastructure Change Manager).
    Make sure that you select an inherent group that includes people with the functional role.
    For this example, the Change Manager Group includes Mary Mann. Only this individual at Calbro Services has the functional role of Infrastructure Change Manager.
  5. In the Approval Indicator field, select which form this approver mapping will affect, for example, Change.
  6. In the Phase Name field, select which approval phase needs mapping in the application, for example, Review.

    Note

    When you select a phase name, the Phase Company field is automatically populated.

  7. Save the approver mapping.
    If you disabled the individual approver mappings and you did not modify the default approval configuration settings, whenever a change request is moved to the Review phase, the change request cannot be moved from the Request For Authorization status until this inherent group/role approves the request.

    Note

    Do not create any other mappings for now. For example, let the Level field setting remain as zero for now.

  8. To test the relationship between change requests and the Approval Server, continue with the following steps:
    To simplify the example, open two instances of the web client, and then log on to your development server with your sample users.
    1. As Ian Plyment, create a change request.
    2. Use the Process Flow Status wizard to move the change request from the Draft status to the next stage.
      If Ian tries to approve his own request, he is prompted that he currently does not have access permissions to approvals.
    3. Click the Approvers tab in the change request.
      If you have correctly created your approver mappings, the name of the individuals from the Change Manager inherent group that you mapped in steps 1 to 6 appears in the list of approvers, as shown in the following figure.

      List of approvers in the Change Manager inherent group

      Click the following figure to expand it.

    4. Log on to your server as Mary Mann, open the Approval Console, and then approve the change request.
      Based on the If Multiple Approvers setting in the Approval Server, either one or all members of the inherent group must approve the request for it to move forward.
    5. Go back to the window where Ian Plyment is logged in, and then refresh the change request.
      The Approvers table is now empty and the change request has moved to Request For Change status.

      Note

      If you wanted to create a multiple-level inherent group approver mapping, you could create another inherent group approver mapping for another inherent group and set the Level setting to one (1). In this case, both inherent groups must approve the change request before it can move to the next stage. After the first inherent group approves the change (level 0), the second level of approvers (level 1) must approve the request before it can be moved to the next stage.

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

Comments