This documentation supports the 9.1 version of Change Management.

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

Setting up approval process configuration records for your company

This procedure describes how to configure approval processes for your company. This procedure is applicable for both BMC Change Management and Release Management.


For BMC Change Management this release consolidates process records for Impacted Areas (IAs) and Configuration Items (CI). To configure approval mappings for CI and/or IA, for each record on the Approval Process Configuration form, you must select the CI-IA process, such as Change Level CI-IA - Review.

To set up approval process configuration records for your company

  1. From the Application Administration Console, click the Custom Configuration tab.
  2. Select Foundation > Advanced Options > Approval Process Configuration, and then click Open.
    The Approval Process Configuration form appears in New mode.

    Approval Process Configuration form — Change form

    Click the following figure to expand it.

  3. Enter information in the following fields:

    Field Name

    Action and description

    Form Name

    Select a form name.

    This is the form from where requests will be generated. For BMC Remedy ITSM, there are two forms: CHG:Infrastructure Change and RMS:Release. You use these form to set up approvals for change and release requests. The different forms displayed in the list depend on which ITSM applications are installed on your system.


    Select the company (designated as the Change Manager support company on the Assignment tab in the change request) that will be using this approval configuration record.

    The Company field lets you control access within BMC Change Management. You can create a process flow for Calbro Services and a completely different flow for XYZ Company. If you select Global, the approval process applies to all companies.

    Note: BMC Remedy ITSM supports multitenancy, which means that you can configure different approval configuration records for different companies.


    Select a status for the approval configuration record.

    The status must be set to Enabled for the approval configuration record to execute.

    Select the appropriate status: Proposed, Offline, Obsolete, Archived, or Delete. Select Delete if the approval configuration record should not be available in BMC Remedy ITSM.


    Enter a description of this approval configuration record.

    Phase Name

    Indicate at which phase of the request this approval configuration record should be executed by entering text in this field.

    The phase name identifies the mapping of approval process to the company and is associated with the company for which this approval is being defined.

    Note: You can have multiple records for the same phase, as long as the Phase Name combined with the Form Name, Company, Process Name, Sort Order and Status is unique.

    For more information, see Configuring additional No Impact processes (optional).

    Process Name

    Select the process that should be used for this approval configuration record from the list of processes you configured. This process name was created in the Approval Server. Selecting a process automatically fills the Process Type field.

    For more information, see

    Process Type

    A pre-configured corresponding process type appears when you select the process name. For more information, see Approval process types.

    Impacts Approval Status

    Select Yes or No to indicate whether this approval configuration record impacts the following:

    • The Approval Status area in the change or release request,
    • The approval status displayed when you select a change record on the Change Management console or a release record on the Release Management console

      This setting specifies whether this approval mapping affects the overall approval status field on the change request and on the Change Management console.

    Default Process Name

    Select a fallback process from the menu list. This setting is applicable only for Release Management.

    This setting is optional and is limited to out of the box processes. You should not set it, unless you specifically need it.

    This field only applies if the Process Name field has a Release Level CI type of approval process selected, and no CIs are related to the release request. This feature provides a fallback mechanism to the basic approval process to look for criteria to establish approvers.

    If no CIs are related to the release request, the fallback approval process is used to establish approvers. 

    If you select Release Level CI - Review in the Process Name field, and Release Level - Review in the Default Process Name field, when a release reaches the Review phase and has no related CIs, it uses the Release Level - Review process instead of the Release Level CI - Review process.

    By contrast, if you cleared the Default Process Name, when a release reaches the Review phase and there are no related Configuration Item records, the release would not have any fallback processes to use. The release would then move ahead to the No Approvers status, as configured for the Approval phase.

    Auto Approve?

    Selecting Yes means that no approvers can be mapped to this process on the Approval Mapping form. It defines an auto approval for this phase. By default, this field is empty. If an approver is mapped to the selected phase, you cannot save the value to Yes.

    It is also applicable for Change Ad Hoc and Change Management Chain approval.

    Note: For an example of how you can use this flag, see Bypassing the approval process for emergency changes.

    In earlier releases, this field was labeled System Approval Flag.

    Max Approval Levels

    This field is displayed when you select the Change Management or Release Management Chain process. 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 specify 3 but only 2 levels of approvers are available, the approval transition is done after the second level of approval is completed.

    Sort Order

    If you have defined multiple approval configuration records for the same starting criteria (the combination of Form Name, Company, and the Begin status field), you can use this field to determine which records will be found first. However, each record must have a different sort order.

    The Sort Order field has a ascending order set for it. As a result, you can set a lower value for the sort order to guarantee that a specific record is found first.

    Note: When you upgrade from an existing BMC Remedy ITSM to the current version, the sort order field for existing approval processes are updated. If any qualifications were defined, the sort order is set to 10, otherwise it is set to 100.

    For example, two of the configuration records start with the same criteria, but the Change Timing/Class values are different.

    Depending on your database, for example, on Oracle, to guarantee that the Business Approval - No Impact is found before the Business Approval, use the following values for the Sort Order:

    • Set the Sort Order of the Business Approval - No Impact record to 10.
    • Set the Sort Order of the Business Approval record to 20.

  4. Click the Status Flow tab to set up the approval cycle for the specific change or release request.
    You can use this tab to customize an alternative process flow. For BMC Remedy ITSM applications, the states displayed in the Status menu depend on the Form Name selected. If you are configuring the approval cycle for a change request, then the states that appear in the Status menu lists are derived from the Status field of the change request.

    For BMC Change Management, an additional Change Process Flow list is displayed because users can define custom process flows. This list displays the standard process and custom processes created for BMC Change Management. The contents in the status fields - Begin, Approved, Rejected, and No approvers fields for BMC Change Management are displayed based on the Change process selected. This is a mandatory field.


    A change moves to the Implementation in Progress status from the Scheduled status when a task user moves the first task to the Work in Progress status. Since this transition is based on task status, the following restrictions have been included for Approval Process Configuration:

    • Begin status field cannot be set to Scheduled or Implementation in Progress.
    • Approved status field cannot be set to Implementation in Progress.

    For example, change requests start in the Draft status. The Begin field of the Status menu lists indicates the default state that starts the approval process; for change requests, this is Request for Authorization. When the change request is submitted and moved to the next stage, the Status changes to Request For Authorization in the Beginfield and the approval process starts.

    • If the change request is approved, its Status changes to Request For Change in the Approved column of the Status menu lists.
    • If the change request is rejected, its Status changes to Rejected in the Rejected column of the Status menu lists.
    • If there are no approvers defined for the change, its Status changes to Request For Change in the No Approvers column of the Status menu lists.
  5. To create a status flow, follow these steps:


    For more details on these approval process states, see Approval states on the Status Flow tab.

    1. Define a status and a status reason (optional) for the Begin state.
      This field specifies which status starts the approval process.
    2. Define a status and a status reason (optional) for the Approved state.
      If the change request is approved, the Approval Server changes the status and status reason values on the relevant form to the values you configure here.
    3. Define a status and a status reason (optional) for the Rejected state.
      If the change request is rejected, the Approval Server changes the status and status reason values on the relevant form to the values you configure here.
    4. Define a status and a status reason (optional) for the No Approvers state.
      If the Approval Server does not find any approvers, the Approval Server changes the status and status reason values on the relevant form to the values you configure here.
  6. Click the Additional Qualifications tab.

    Approval Process Configuration form — Additional Qualifications tab

    Click the following figure to expand it.

  7. To create additional qualifications in the approval process, select additional fields from the change request (or release request) to qualify the approval process for a particular approval phase. For example, the default Business Approval - No Impact process is triggered by the No Impact setting in the Change Timing/Class field on the change request, as shown in the figure above.
    You can include other fields to qualify which approval process to use for a particular request. For BMC Change Management, you can select any combination of change type, change timing, and timing. For Release Management, you can select any combination of release type, deployment type, and business justification, as shown in the following figure.

    Additional Qualifications tab — Release Management

    Click the following figure to expand it.

  8. Click Save.
    If this is the first process configuration record you created for the company, you are prompted that the system created additional process configuration records for all your approval phases (if you created additional approval definition phases). These new configuration record are based on the global settings. You can modify these new records as needed.


The Default Process Name field is no longer provided for BMC Change Management on the configuration form. This value was used to define a default approval process that would be used to identify approvers if no approvers were identified for an approval process. This option is no longer required because the different levels of change approval processes are now consolidated into a single level. For example, Change Level-CI - Review and Change Level- IA - Review have been consolidated into Change Level CI-IA - Review.

Related topics

How approvals work with change requests
Working requests through the approval phases
Default global approval processes for BMC Change Management
Default global approval processes for Release Management
Change request state transitions - Draft to Closed
Configuring additional No Impact processes (optional)
Approval mappings
Approval process types

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