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.

Creating an emergency change request


An emergency change is implemented when there is an incident that requires a change. Depending on how your application administrator has configured the Change Management application, emergency change requests bypass the normal approval process. When you create an Emergency change the new approval process phase will be used, bypassing the normal change states. For example, if emergency requests are configured to bypass the Review approval stage, the change is not held up waiting for approvals, but is automatically approved. The request skips to the next stage in its lifecycle. You can also relate problem records to the emergency change. 

As a manual step, make sure that an open incident refers to this change request.

Before you begin

Your application administrator must configure the approval process that bypasses the normal approval process for emergency change requests. For more information, see Setting-up-an-emergency-change-process-that-bypasses-the-approval-process.

To create an emergency change request

  1. Create a new change request as described in Creating-a-change-request-at-the-Initiate-stage.
  2. Select Emergency from the Class field.

    The following message is displayed:
    Make sure an open incident references this change. (ARWARN 1440110)

  3. Enter the required information for the change record, and then click Save.
  4. Add the related incident or problem requests in the Relationship tab of the record.

 

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