Variable Scopes

Each variable exists and has a value assigned to it within a single scope. A scope is the environment, or set of conditions, within which the variable and its value are relevant.

• Runtime Scope: The variable is persistent over a single execution of the runbook An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook..

• Incident Scope: The variable is persistent over the lifecycle of an incident A collection of one or more related triggers. Relationships that cause triggers to be combined into incidents include application, location, operating system, or a trigger by itself. associated with a runbook An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook.. Some values are initialized before runbooks run. Successive runs of runbooks will be able to use the value of variables set in a previous run.

• Subflow Scope: The variable is persistent within a subflow A reusable automation chunk that performs frequently used functions, such as opening a ticket in an external system, and can be used to implement integrations with third-party systems. execution and is used to pass data between the subflow and its parent (calling) runbook. In a subflow scope, you are limited to subflow variables.

The scope is prepended to each variable name automatically whenever the variable is displayed or used outside the Variable Definition Editor. (The prefix is not shown within the Variable Definition Editor, since the variable is edited in a tab for that scope.)