Creating flows with multiple actions
As the BMC Helix Integration Studio administrator or end user, you can create flows with multiple actions. Such flows include a trigger and a series of actions that occur due to this trigger. Instead of creating separate flows for different purposes, you can create a single flow with multiple actions and receive a chain of results after a single flow run.
For example, you can create the following flow: if a new ticket is created in Atlassian JIRA (trigger), create the same ticket in Remedy ITSM (action 1), update the Atlassian JIRA issue with the Remedy ITSM incident number (action 2), and then send an email notification with information from both the JIRA issue and Remedy incident (action 3).
Example: Multiple-action flow for simple tasks
The following illustration shows an example of a flow with simple logic, where the actions in Connector 2 and Connector 3 occur sequentially after a triggering event in Connector 1:
As the result of such a flow run, you receive the same notifications in Slack and Gmail about the triggering event in Salesforce.
Example: Multiple-action flow for complex tasks
The following illustration shows an example of a flow with complex logic:
As the result of such a flow run, you receive the following notifications:
- Notification in Slack about Salesforce user profile change.
- Notification in Gmail that includes Salesforce user profile change information and the title of the Slack channel where the first notification is located.
You can create simple or complex flows with multiple actions by mapping the corresponding fields according to your needs.
Before you begin
Review how to create a simple flow with one trigger and one action.
To create a flow with multiple actions
- Go to Flow Designer.
- Choose the source application, and click Next.
- Choose the trigger, and click Next.
- Choose the target application, and click Next.
- Choose the action, and click Next.
Map the fields, and click Next.
For flows with multiple actions, you can see the origin of a mapped field in a label. Fields that come from the source application are marked with the Source label, while fields that come from the target application are marked with the Target label.
See an example of labeling in the following illustration:
Click Add Action, and repeat steps 4–6 to add other actions.
The following animation shows an example of creating a flow with two actions (Incoming Email > Basecamp > Gmail):
You can create a flow with a maximum of five actions.
- Provide the Summary values, and click Done.
The flow with multiple actions is created. Proceed with activating your flow.
Support for flows with long-running actions
BMC Helix Integration Studio supports flows with long-running actions. You might need to create such a flow according to your business need and based on the performance of a third-party system.
For example, you might need to create an approval flow that requires human intervention for approving business requests.
Execution of a flow with long-running actions might take a considerable period of time (up to a week). All action details are displayed in the flow timeline.