Space banner


This documentation supports the 19.08 version of Change Management.

To view an earlier version, select the version from the Product version menu.

Approval process types

This topic describes the approval process types that are provided by Change Management and the Release Management module.

For detailed information about defining the approval processes and rules, see  Defining an approval process  and  Defining approval rules  in the Remedy AR System documentation.

Related topics

Default global approval processes for BMC Change Management
Setting up approval process configuration records for your company

Approval process types

Change Management and the Release Management module provide the following approval process types:



Ad Hoc

Provides routing authority to each approver without requiring the administrator to create approver mappings for every individual or group. The Ad Hoc approval process is used in the No Impact Business Approval phase with the Change Manager as the approver.


Associates individual approvers, or groups of approvers, with impacted areas or configuration items (CIs), or other additional qualifications.


Uses the Requested For manager as the approver. If you configure an approval process that includes the Change Management Chain process, it uses the Requested For manager as the approver. If the Requested For fields are not filled in (on the Change form under the Requester tab), the approval server bypasses the Change Management Chain process.

If you configure an approval process that includes the Release Management Chain process, the approval process uses the manager of the Release Requester (on the General tab of the Release form) as the approver.

Important: Rule-based approvals are not included by default in Change Management.

For example, in the Change Management Chain process, if Joe Unser in HR wanted to upgrade the operating system on his computer and created a change request that required the Change Management Chain approval process, the change request would be sent to Joe's manager for approval. Joe's manager is not a member of the IT organization, and, therefore, might not be aware of additional issues surrounding Joe's request. This process is workflow-driven, triggered from the manager data that is stored in the People form.

Change Management Chain approval process

If you select the Change Management Chain process, the Max Approval Levels field appears in the Approval Process Configuration form, as shown in the preceding figure. You can specify how deep you want to go in the management chain. For example, if you enter 1, the chain extends only to Joe's manager. If you enter 2, the manager of Joe's manager must approve the upgrade, and so on. However, if you mention 3 levels, and only 2 levels of approvers are available, the approval chain is treated as completed.


For Change Management, you are allowed only one record per company with the process type of Parent-Child. If an administrator attempts to create a second approval phase with the Change Management Chain (Parent-Child) process type selected, the following error message is displayed: Only one 'Approval Phase' for '$Company$' can be set to use the 'Parent-Child' 'Process Type'.

In addition, you should use a unique approval process for each phase. Otherwise your approvals do not work as expected.

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