Approval processes provided out-of-the-box for BMC Change Management
BMC Change Management ships with default approval processes designed out-of-the-box for global use. These best practice approval processes are already defined for you by default. These processes specify which status occurs next if a request is approved or rejected, or if no approvers are defined.
Preconfigured approval processes for BMC Change Management
Approval Process (phase)
In the Initiate stage, the out-of-the-box behavior for change requests is that when their Status moves out of Draft status into Request For Authorization status, the Review approval phase starts.
Business Approval - No Impact
The Change Ad Hoc approval process is used in the No Impact Business Approval phase with the Change Manager logon as the first approver. By default, this Ad Hoc approval process applies only to changes with a Class setting of No Impact. No approver mapping is required to be configured for this phase.
The Review & Authorize stage focuses on risk assessment and impact analysis. The Business Approval Phase starts when the change request is placed in Request for Change status. The Business Approval phase requires that the business case for the change be approved before it can move forward.
In the Plan & Schedule stage, the out-of-the-box behavior for change requests is that the Implementation Approval phase starts when their Status moves into Scheduled For Approval status. At this phase, the system notifies you that the change must be approved before it can be implemented.
Close Down Approval
In the Implement stage, the out-of-the-box behavior for change requests is that the Close Down approval phase starts when their Status moves into Completed status (with a status reason of Final Review Required). At this phase, the system notifies you that the request must be approved before it can be closed down.
The read-only Next or Current Approval Phase field displays what approval phase the change is in during its life cycle. The Approvers tab also displays the following important information:
- Approval status
- Signatures of groups and individuals who must approve the change request
- Alternate approvers
Approvals can be generated automatically, based on information captured on the change request. They can also be generated manually on an ad hoc basis.
Change form — Approvers tab
If needed, the application administrator can configure the change request approval workflow according to your organization's business model. This determines which change requests require approval and what kind of approval process they undergo.