doesNotHaveStatus
A Workflow Engine function that returns true when the in-scope alert or Situation is not in any of the specified states.
This function is available as a feature of the Add-ons v1.4 download and later.
This function is available for alert, enrichment, and Situation workflows.
Back to Workflow Engine Functions Reference.
Arguments
Workflow Engine function doesNotHaveStatus takes the following arguments:
Name | Required | Type | Description |
|---|---|---|---|
| Yes | Object | The states to check for. Choose from:
Not all states are available to both alerts and Situations. For example, you cannot set an alert to Dormant. |
Example
The following example demonstrates typical use of Workflow Engine function doesNotHaveStatus.
You want to check if an alert is neither Opened, Acknowledged, or Closed before performing subsequent actions in your workflow. Set the following:
states: [ “Opened”, “Acknowledged” , “Closed” ]Forwarding behavior: Stop this workflow. This ensures that if the alert is in any of the specified states, subsequent actions in this workflow do not execute.
The UI translates your settings to the following JSON:
states : [ “Owned”, “Acknowledged” , “Closed” ]
If the alert is not in any of these states, the function returns true and the alert is forwarded to the next action in the workflow.
If the alert is in any of these states, the function returns false and the forwarding behaviour prevents subsequent actions in the workflow from executing.