In Unifi, we throw events for Transaction State changes. Like standard ServiceNow Script Actions, Event Actions respond to those events. Unlike Script Actions, however (where there is a simple one-to-one relationship between the event and the action), Event Actions provide an added level of abstraction in that they offer functionality that enables you to triage the events and make decisions about how you deal with them according to the conditions you configure.

Their primary use case would be in dealing with Transaction errors. For example, you may choose to create an incident after receiving five errors in fifteen minutes, or when a specific error code occurs. The available configuration options make their use case extremely flexible, so you could decide, for example, to auto-close previously opened incidents when the Transaction is complete.

Execution Flow

The Event Action executes under the following conditions:

1. Run Conditions. These stipulate the conditions which cause the Event Action to fire. They specify which Integration* and which Event* the Event Action is responding to (*both Integration & Event are mandatory). They can even be dependent on the status of the integration and apply to specific messages.

2. Triage Conditions. Triage conditions determine whether or not we take any action i.e. the conditions that must apply for the Action script to run.

3. Action. This is where you will find the Action script, which is the actual script that will run.

Details Fields

The Details fields that can be configured for the Event Action record are as follows:

Run Conditions Fields

The Run Conditions fields that can be configured for the Event Action record are as follows:

Triage Conditions Fields

The Triage Conditions fields that can be configured for the Event Action record are as follows:

Action Fields

The Action fields that can be configured for the Event Action record are as follows:

Example script:

var incident,
    integration,
    summary;
​
​
integration = current.getDisplayValue('integration');
summary = 'Issue with integration ' + integration + ': error - ' + (current.error || current.process_error);
​
incident = new GlideRecord('incident');
incident.addQuery('short_description', '=', summary);
incident.query();
​
​
if (!incident.next()) {
  incident.newRecord();
  incident.short_description = summary;
  incident.impact = 3;
  incident.urgency = 3;
  incident.assignment_group = ''; // Your integration team here;
} else {
  // Increase impact and urgency each time the event action is called
  incident.impact = (+incident.impact - 1) < 1 ? 1 : +incident.impact - 1;
  incident.urgency = (+incident.urgency - 1) < 1 ? 1 : +incident.urgency - 1;
}
​
incident.work_notes = 'Integration ' + integration + ' has encountered an' + 
  ' error ' + current.error + ' and has triggered the event action ' + 
  action.getDisplayValue();
incident.update();

In the above example code, we query the incident table for records that match (using short_description as a unique identifier). If one isn’t found, we create a new one and set some values. Otherwise we increment the impact and urgency. Finally, we add a work note to the incident.