This documentation supports the 9.1 version of Change Management.

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

BMC Change Management approval mappings

This topic describes how to include additional approval mappings for BMC Change 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. 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.

Additional mappings for BMC Change Management

  1. The Impacted Area/CI tab is used to map approvers to the change's impacted areas or CIs.

    Approver Mappings form-Impacted Area/CI tab

    Click the following figure to expand it.


    The Company, Region, Site Group, and Site fields in the Impacted Area/CI tab apply also to basic approval processes. These fields correspond to the Change Location fields in the Requester tab in a change request.

    Note

    You can also map approvers to the CIs associated with the change if you customize an approval process configuration record that uses the CI processes.

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

    How CIs are selected

    Select on

    Action

    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.

  2. The Categorization tab is used to map approvers to services specified in the change and product categorizations of the change. The fields in the Categorization tab apply to the Impacted Areas and basic approval processes.

    Approver Mappings form-Categorization tab

    Click the following figure to expand it.

  3. The Role tab is used to map approvers based on the support groups defined within the change. The fields in the Role tab apply to the Impacted Areas and basic approval processes.

    Approver Mappings form-Role tab

    Click the following figure to expand it.

    Note

    If your mapping includes Change Implementer values and your user creates a new change request with tasks added, the Change Implementer information is cleared from the change request and the approval mapping no longer meets the criteria. If you plan to add tasks to change requests, you should create two mappings-one mapping when a change implementer is assigned (no tasks are included in the change request), and a second mapping when tasks are included (the Change Implementer fields in the mapping should be blank).

  4. The Advanced Criteria tab is used to map approvers based on specific criteria. The fields in the Advanced Criteria tab apply to the Impacted Areas and basic approval processes.

    Approver Mappings form-Advanced Criteria tab

    Click the following figure to expand it.


    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. These are courtesy notifications that do not require the recipient to 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.

    Note

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

    For example, if you select Approve if Risk <= Risk Level 2, the Notify if Risk < field is automatically set to Risk Level 3. The support staff person is required to approve all normal changes that have a Risk Level of 3 or greater. In addition, he or she is notified of similar changes with a Risk Level of 1 or 2. The following table explains these interactions in more detail.

    Interactions between change risk levels and approver mappings

    Change risk level

    Approval signatures generated

    Non-approval notifications generated

    Approval mapping where Approve if Risk <= is empty and Notify if Risk < Risk Level 1

    1

    Yes

    No

    2

    Yes

    No

    3

    Yes

    No

    4

    Yes

    No

    5

    Yes

    No

    Approval mapping where Approve if Risk <= Risk Level 1 and Notify if Risk < Risk Level 2

    1

    No

    Yes

    2

    Yes

    No

    3

    Yes

    No

    4

    Yes

    No

    5

    Yes

    No

    Approval mapping where Approve if Risk <= Risk Level 2 and Notify if Risk < Risk Level 3

    1

    No

    Yes

    2

    No

    Yes

    3

    Yes

    No

    4

    Yes

    No

    5

    Yes

    No

    Approval mapping where Approve if Risk <= Risk Level 3 and Notify if Risk < Risk Level 4

    1

    No

    Yes

    2

    No

    Yes

    3

    No

    Yes

    4

    Yes

    No

    5

    Yes

    No

    Approval mapping where Approve if Risk <= Risk Level 4 and Notify if Risk < Risk Level 5

    1

    No

    Yes

    2

    No

    Yes

    3

    No

    Yes

    4

    No

    Yes

    5

    Yes

    No

    Approval mapping where Approve if Risk <= Risk Level 5 and Notify if Risk < is empty

    1

    No

    Yes

    2

    No

    Yes

    3

    No

    Yes

    4

    No

    Yes

    5

    No

    Yes

  5. Click Save.

In conclusion, approver mapping records are joined with Change IA join records, Change CI join records, or change requests to provide data for approval processing rules. The Approval Server uses various join forms to select approvers for specified processes.

Note

Approval mapping records are specifically for the Change Level processes. The Change Ad Hoc process does not use the Approver Lookup record, nor does the Change Request Management Chain process.

Related topics

You use the Approver Mappings form to set up individuals and groups as approvers for each approval phase of change 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

Comments