This documentation supports the 9.1 version of Change Management.

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

Handling approvals for emergency change requests

Depending on how the application administrator has configured the application, change requests that have been designated as emergencies can be allowed to bypass the approval process even if they normally require approval. In this case, the emergency change request is not held up waiting for approvals. For more information, see Creating emergency change requests.

Following are possible configurations for handling approvals for emergency change requests:

  • The application administrator can configure emergency change requests to bypass the normal change states and approval process. To configure a new approval process for emergency changes, the application administrator must create a new approval process for your company. As a result, when a change manager or change coordinator creates a change and selects Emergency in the Class (Timing) field, the new approval process phase is then used. For more information, see Bypassing the approval process for emergency changes.
  • The change manager or the change coordinator can choose to add approvers to the process. The Approval Status field is set to Approval Required.
    • If the change manager assigns approvers, the approval process proceeds as usual.
    • If the change manager does not assign approvers, the Approval Status is set to Approved, and the change request can be implemented.
  • If the change request is designated as an emergency and your organization uses the Change Management Chain approval process, the manager of the Requested For user (in the Requester tab) is the first approver in the management chain. If the Requested For fields are empty, the emergency approval process is bypassed. Change managers can add more approvers if appropriate. They cannot delete approvers.
Was this page helpful? Yes No Submitting... Thank you