This topic covers details on rule actions to create or update a case.
The Create a New Case Action panel provides all fields necessary to set case attributes. The following example shows that creation of the case is based on the On First Event
trigger for this rule:
When you use a rule to create a case, you are required to give the case a name. It is possible that your organization has customized the Case resource so that additional fields are mandatory. If so, note that the rule will not check for the additional mandatory fields, and the rule will not fail if you do not set those mandatory fields with this rule action. You should therefore remember that after the rule creates the case, the case owner is responsible for editing and setting the other mandatory fields.
Note: After the rule action creates the case:
Created By
field displays the rule's URI.<rule_name>
and also provides the rule's URI. To apply the Create New Case rule action:
Required: Provide a name for the case.
You can name a case in conjunction with an existing field value from an event. For example, you want your action to create a new case called Suspicious Login Attempts based on a value in the event field, Attacker Address. For this scenario, your case name’s format will be Suspicious Login Attempts $attackerAddress.
Specify a case group and owner.
Optionally choose Include Base Events in Case. This means that when the rule action is triggered, both correlation events and the correlated base events that triggered the rule will be added to the case’s Events tab.
Specify the case’s attributes when the rule is triggered. For information on case attributes, refer to Creating or Editing a Case.
For multi-line text fields, the value specified in this rule action will be appended to the existing values, but only if the new value being appended is unique. For example, your multi-line Attacker Address field has these IP addresses:
192.0.2.0 192.0.2.9 192.0.2.24
If the rule action is to set the field with Attacker Address = 192.0.2.9
, this value will not be appended because the value is already in the field.
The Add To Existing Case Action panel provides all fields necessary to change case attributes. The panel does not fetch current values of the existing case. Instead, the default selection is Keep existing value. Remember that you are defining the rule to keep or change certain case attributes when the action is triggered, whatever the case attributes are at that time.
To apply the Add To Existing Case rule action:
Specify a case by choosing one of two options:
Select an existing case. Use the Case drop-down menu to navigate the Cases resource tree and select the case.
Caution: Make sure the case is not locked when the rule triggers; otherwise, the rule fails. However, even if the rule fails, correlation events are still added to the case because the addition of events does not alter the case resource itself.
Select Calculate case name dynamically to specify a case defined in another rule action.
This setting does not require an existing case. If the case does not yet exist, the case is created when the rule is triggered.
For the dynamic case name, specify the name based on the same case name you provided in the other rule action that creates the case. An example of a dynamic case name is one that includes a variable. In the example, GetMonth
is a variable name, and so the dynamic name entry is Suspicious Login Attempts $GetMonth. If your variable name has spaces, replace the spaces with the underscore character. For example, if your variable is Get Month
, then your case name is Suspicious Login Attempts $Get_Month
.
Optionally choose Include Base Events in Case. This means both correlation events and the correlated base events that triggered the rule will be added to the case’s Events tab.
Specify the case’s updated attributes when the rule is triggered, or keep the existing values. For information on case attributes, refer to Creating or Editing a Case.
For multi-line text fields, the value specified in this rule action will be appended to the existing values, but only if the new value being appended is unique. For example, your multi-line Attacker Address field has these IP addresses:
192.0.2.0 192.0.2.9 192.0.2.24
If the rule action is to set the field with Attacker Address = 192.0.2.9
, this value will not be appended because the value is already in the field.
The Create Ticket in ServiceNow® ITSM panel provides all fields necessary to create a ticket. The following example shows that creation of the case is based on the On First Event
trigger for this rule:
To apply the Create Ticket in ServiceNow® ITSM rule action:
$name
. All expressions common to the Action editor map to their expected values.(Optional) Modify the remaining fields as appropriate, and then click OK.