sendCIsAddedToIncident
A Workflow Engine function that sends a request to the corresponding outbound integration workflow to add a list of CIs to the incident for the named service. By default, the action expects a list of CIs in the newCIs workflowContext key. You can use the optional CIs argument to override the default.
This function is available as a feature of the Add-ons v2.2 download and later.
This function is available for alert and Situation workflows.
Back to Workflow Engine Functions Reference.
Arguments
Workflow Engine function sendCIsAddedToIncident takes the following arguments:
Name | Required | Type | Description |
|---|---|---|---|
| yes | string | The name of the incident integration; has the value alertops. |
| no | string | An instance name for integrations supporting multiple instances. Defaults to the first instance |
| no | string | A list of CIs. Example: "node1", "node2" |
| no | object | A JavaScript object that passes any additional arguments as context to the workflow and adds them to the existing workflow context. |
Example
Within a Situation Delta workflow, this action can be proceeded by a haveSituationCIsChanged function. The haveSituationCIsChanged function returns true when the CIs in a situation have changed, and it populates the newCIs workflowContext key with a list of CIs added to the situation.
If the forwarding behavior on the haveSituationCIsChanged function is set to “Stop This Workflow”, the subsequent sendCIsAddedToIncident function only runs when the CIs in the situation have changed. It then takes the list of new CIs added from the workflowContext, so the CIs argument can be omitted.