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 Release Management)

The Inherent Group menu lets you select a group specified on the Release form to be the Approval group (for example, Release Coordinator Group). The Functional Role menu lets you select a functional role for the approval (for example, Release Coordinator).

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.

With version 9.1.04 or 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

Inherit group

Functional role

Approvers generated

Release Coordinator Group

Not selected

Members of Release Manager Support group on release request with Release Approver functional role

Release Coordinator Group

Release Approver

Members of Release Manager Support group on release request with Release Approver functional role

Release Coordinator Group

Release Coordinator

Members of Release Manager Support group on release request with Release Manager functional role

Release Request Group

Not selected

Members of Release Requester Support Group on release request with Release Approver functional role.

Release Request Group

Release Approver

Members of Release Requester Support Group on release request with Release Approver functional role

Release Request Group

Release Coordinator

Members of Release Requester Support Group on release request with Release Coordinator functional role

Note

The Release Requester Support Group fields are hidden on the Best Practice view.

To create support group mappings

  1. From the Application Administration Console, click the Custom Configuration tab.
  2. From the Application Settings list, select Release Management> Approval> Approval Mappings, and then click Open.
  3. In the Approval For field, select Inherent Group/Role.
    The Approval Mappings form redisplays, so that the fields to configure a group mapping appear.
  4. In the Approval Indicator field, select which form this approver mapping will affect, for example, Release.
  5. In the Inherent Group field, select a release management group.
  6. In the Functional Role field, select one of the BMC Remedy ITSM functional roles defined for release management (for example, Release Coordinator).
    Make sure that you select an inherent group that includes people with the functional role.
  7. In the Phase Name field, select which approval phase needs mapping in the application (for example, Planning).

    Note

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

  8. Enter remaining mappings as needed.
  9. Save the approver mapping.

If you disabled the individual approver mappings and you did not modify the default approval configuration settings, whenever a release request is moved to the Planning phase, the release request cannot be moved forward until this inherent group/role approves the request.

Related topic

Release Management approval mappings

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

Comments