Configuring additional mappings for Change Management
You can include additional approval mappings for Change Management.
Before you begin
Make sure you have completed the configuration described under Configuring-approval-mappings-for-change-and-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.
To configure additional mappings for Change Management
The Impacted Area/CI tab is used to map approvers to the change's impacted areas or CIs.
This field corresponds to the impacted areas selected on the change request. By default, the change location is considered one of the impacted areas. Additional impacted areas can be added to the change request as required.
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.
If you map approvers to CIs, you must specify how the CI is selected.
Select on
Action
CI Type
Select a specific CI type from the menu, for example, CI Type > System > Computer System.
CI Name
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 is displayed. Perform a search for a CI and then click Select. The CI Name+ and CI ID fields are then populated.
The Categorization tab is used to map approvers to services specified in the change and product categorizations of the change request. The fields in the Categorization tab apply to the Impacted Areas and the basic approval processes. This field corresponds to the categorization data on the change request.
The Role tab is used to map approvers based on the support groups defined within the change request. The fields in the Role tab apply to the Impacted Areas and basic approval processes.
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 and provide additional attributes that can be used to match the ones on the change request. The most common attribute that you can use is Class; that is, Change Class (Normal, Standard, Emergency, and so on).
The Approve if Risk and Notify if Risk fields work in conjunction with each other. If you select one of these fields, it will set the other field automatically. These fields are used to determine whether an actual approval request will be generated or just a notification (for example, FYI) will be set to the approvers. 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.
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, the user is notified of similar changes with a Risk Level of 1 or 2. The following table explains these interactions in more detail.
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
- 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.