This documentation supports the 22.1 version of BMC Helix ITSM: Change Management.To view an earlier version, select the version from the Product version menu.

Submitting change requests through the approval phases

In the approval stage, the approver needs to approve, reject, or hold the change request. When an approval is required, you cannot move the request to the next stage unless you first receive an approval or a rejection. When a request requires an approval, its approvers are notified. Notifications are sent according to the method specified in the approver's record in the User form.

The Approval Process Configuration form is used to configure the sequence when a request is approved or rejected, or to configure how the system should respond if no approvers are available. When you have finished planning the request, and have supplied all the information that the approvers require to review the request, you can submit the request to the approval process.

Related topic

Setting-up-approval-process-configuration-records-for-your-company


To submit the request to the approval phase

  1. Open the change request or release request.

  2. Proceed through the states of your request.

    Tip

    When you reach a crucial state and perform an important action (for example, adding dates in the Scheduled status), refresh the request to make sure you are viewing the correct step in the workflow.

    Approving change requests.jpg


  3. When you reach an approval phase, in the Approvals section, click Approve or Reject.
    The Approve and Reject options are enabled only if you are a valid approver or an alternate approver for the selected approval record. As a change manager or a change coordinator (or a release coordinator or release assignee), you can perform these actions for standard approvals if you are the approver or an alternate approver.
    • If the change is configured for the change level approval process, all the approvers on the first level are notified that they must review the request.
    • If the change is configured for the change management chain (parent-child) approval process, the manager of the Requester For user is notified.
    • If the change is configured for the ad hoc approval process, the change manager is notified.

    • The signature of the last approver completes the approval process, and automatically moves the change request to the next status.
      The administrator can configure the approval process to require a justification when you approve or reject a request. For more information, see Form to create and modify approval processes.

      Important

      From the Mid Tier screens of a change request, you can enter the justification only when you Reject. To enter a justification when you Approve a change request, use Approval Central, or Progressive Web App (PWA) screens.

  4. Click Save.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*