You can use script actions to create server-side scripts that perform a variety of tasks, such as modifying a configuration item (CI), or managing failed login attempts. Script actions are triggered by events only.

Configuration

To create a new script action, navigate to System Policy > Events > Script Actions and click New.

Table 1. Script actions
FieldDescription
Name Unique name for your script action.
Application Application that contains the script.
Event name Event to use for this script. If you do not find an event for your script action that suits your purpose, you can create a new one.
Active Check box that enables or disables the script action. Select true) to enable the script action.
Execution order Order in which the script will be executed.
Condition script Statement for a condition under which this script should execute. The system only parses the script field if the condition evaluates to true. If you decide to include the condition statement in the script, leave this field blank.
Script Script that runs when the condition you define evaluates to true. Two additional objects are available in this script:
  • event: a GlideRecord- the sysevent that caused this to be invoked. If you want this first parameter on the event, use event.parm1 or event.parm2 for the second parameter. For the date/time of the event, use event.sys_created_on. To get the user ID that created the event (if there was a user associated), use event.user_id.
  • current: a GlideRecord- the event scheduled on behalf of (incident for example).

Sample of a script action that creates an email notification for Workflow activity:

Figure 1. Script action workflow
Script action workflow notification