The automation workflow includes variables or tokens that you can use in process definitions as dynamic values. The variables are easily accessed through the process definition design canvas properties.

Variables are contextual to the process, and have the following types:

  • string
  • date
  • objects
  • boolean

Variable values come from the following:

  • alerts
  • incidents
  • resources
  • JSON
  • scripts
  • integrations

Variables example

The following example shows you how to access available variables in the design canvas properties. You will start with an alert StartEvent named Alert Start that takes an alert as input and has an appended User Task named My User Task.

Process Definition Start

Add a dynamic Subject to the task using the alert subject.

  1. In the Subject field, enter a $, and the Alert_Start event is displayed in a list below the Subject field, select Alert_Event.

    Process Definition Select Step 1
  2. In the Subject field, after $Alert_Start, enter a period . and alert is displayed in a list below the Subject field, select alert.

    Process Definition Select Step 2
  3. In the Subject field, after $Alert_Start.alert, enter a period . and the alert variables are displayed in a list below the Subject field. Enter s in the list to filter the attributes starting with s and select subject.

    Process Definition Select Step 3

    The user task will now use the subject of the input alert as the task subject.

    Process Definition Select Step 4

The following example shows how variables can be used to dynamically populate task properties in the Subject, Description, and Priority fields.

Process Definition Variables

In addition to alert, incident, and resource properties, you can also use variables to pass the output of one task to another task including script output and JSON fields.

Available variables

The following table list the available process automation variables. The variables can be string, date, objects, or boolean values.

TypeProcess Automation Variables
Alertsubject
description
metric
component
repeatCount
priority
isAvailabililtyAlert
monitorName
templateName
alertType
eventType
objectId
objectName
objectType
ipAddress
currentState
previousState
status
statusHistory
resource
incident
incidentId
inferenceId
resourceMaintenanceWindowId
isInferenceAlert
clientId
clientName
spUniqueId
partnerId
partnerName
elapsedTime
alertCriticalWarningDuration
source
triggeredTime
externalAlertId
comments
snoozeDuration
createdBy
createdTime
updatedBy
updatedTime
id
tenantUniqueId
uuid
IncidentbusinessImpact
urgency
escalationPolicyId
subject
description
priority
category
subCategory
reason
requester
assignedTo
assigneeGroup
cc
dueDate
impact
status
externalTicketId
clientUniqueId
mspUniqueId
createdBy
createdTime
updatedBy
updatedTime
id
tenantUniqueId
uuid
ResourcealiasName
hostName
serialNumber
agentInstalled
ipAddress
firstManagedTime
updatedDate
osName
mspUniqueId
uuid
macAddress
createdDate
clientUniqueId
name
model
state
make
alternateIpAddress
assetManagedTime
JSONJSON fields can be used as variables.
ScriptOutput
Status
IntegrationIntegration events output can be configured as variables.