Create trigger rules for major incidents

Create trigger rules to define the conditions under which a trigger action is executed. You can create major incident trigger rules to define the conditions under which an incident is automatically considered as a major incident candidate.

Before you begin

Role required: incident_manager or admin

About this task

Major incident trigger rules are evaluated asynchronously each time an incident is created or updated provided the following conditions are met:

The incident record doesn't have the Parent Incident populated, which means that the current incident isn't a child incident.
The major incident isn't proposed or accepted.
The incident is active.

Note: The base system major incident trigger rules are inactive by default.

Procedure

Navigate to All > Major Incidents > Administration > Major Incident Trigger Rules.

Note: If the UI16 module link redirection feature is enabled in Service Operations Workspace (SOW) and the UI16 module supports the redirect configuration, navigating through UI16 paths automatically redirects you to the equivalent list or record pages in SOW instead of displaying the UI16 forms or lists. For more information, see Redirect UI16 module links to Service Operations Workspace.
Select New.
On the form, fill in the fields.

Field	Description
Name	Unique name of the trigger rule.
Table	Table on which the trigger rule executes.
Application	Application scope of the trigger rule. The trigger rule is available for all applications or for scoped applications.
Execution Order	The rule with lowest execution order is triggered first. In the following example, the rule with order = 100 is executed first.Example: If business criticality of business service is 1-most critical or 2-somewhat critical, Order = 100. If the number of child incidents is greater than 20, then Order = 200. For a P1 incident, Order = 300. Note: If any of the existing trigger rule conditions are met, the incident is considered to be a major incident candidate. Verification of the remaining rules isn’t required. Otherwise, all the rules are verified based on the execution order.
Action to take	Action taken on the incident when the trigger rule is executed. The possible values are the following:- Propose Major Incident: Incident is proposed as a major incident candidate when the trigger rule is executed. After it’s approved, the incident is promoted to a major incident. - Promote Major Incident: Incident is promoted directly to a major incident when the trigger rule is executed. - Note: The Create major incident from candidate (sn_major_inc_mgmt.com.snc.incident .min.major_incident_creation) system property creates different behaviors depending on which options are selected. When the system property is set to Create new, the following behaviors occur in relation to the Action to take values: Propose Major Incident: The incident is proposed as a major incident candidate. After it’s approved, a new major incident is created and the incident is marked as its child. Promote Major Incident: A new incident is created and promoted to a major incident. The existing incident is marked as its child. When the system property is set to Promote, the following behaviors occur in relation to the Action to take values: Propose Major Incident: The incident is proposed as a major incident candidate. After it’s approved, a new major incident is created and the incident is marked as its child. Promote Major Incident: The existing incident is promoted to a major incident.
Active	Option to activate the trigger rule.
Conditions	Conditions that must be met to execute the trigger rule.

Select Submit.

Parent Topic:Managing major incidents