Use > Change Management > Change Management configuration > Configuring approvals in Change Management

Configuring approvals in Change Management

Change Management requires approvals to be complete before the change request can move to the next logical phase. In some cases, approvals can be defined based on associated Service Level Agreements (SLA), so that managers and sponsors associated with the SLA will be listed as approvers for some phases.

After the approvals are complete, you can move the request to any desired phase by setting a condition in the condition editor of a transition. You can set the transition condition to move the change request to another phase or remain in the current phase by setting the statuses to “Denied” and “Pending” respectively. For example, you can set the following conditions for the transitions in the “ECAB Approval” phase to move the change request to different phases.

Condition

Action Performed

Set the following condition in the transition from  the “ECAB Approval” phase to the “Build and Test” phase

Approval Status in CurrentRecord= 
approved AND Build Test Required in 
CurrentRecord= true 

Change request moves from the “ECAB Approval” phase to the next phase, “Build and Test”.

Set the following condition in the transition from “ECAB Approval” to “Implementation”

Approval Status in CurrentRecord= 
approved AND Build Test Required in 
CurrentRecord= false

Change request moves from the “ ECAB Approval” phase to “Implementation”.

Set the following condition in the transition from “ECAB Approval” to “Risk and Impact Analysis”.

Approval Status in CurrentRecord= denied 

Change request moves from the “ECAB Approval” phase to the previous phase, “Risk and Impact Analysis”.

A change request may require other approvals:

  • Change requests with an impact of 3 (Major Impact) also require approval by an IT director.
  • Change requests with an impact other than 1 (Minor Impact) must be approved by a member of the Change Advisory Board (CAB).