Designing and maintaining flows
A flow is an event-driven connection between two applications. A triggering event in the source application of a flow causes an action to be performed in a target application. End users and administrators can use the Flow Designer feature in BMC Helix Integration Studio to design flows.
- In a Remedy ITSM to JIRA flow, a new or updated incident in BMC Remedy IT Service Management triggers the creation and assignment of a corresponding ticket in Atlassian JIRA.
- In a Slack to Gmail flow, a new message in a specific Slack channel triggers an email to be sent out to a certain audience.
Types of flows
There are two types of flows: personal flows and catalog flows.
A personal flow is intended for a user's personal use and can not be accessed by anybody else using BMC Helix Integration Studio, including admin users. You can modify an existing catalog flow to create a personal flow. Conversely, you can share a personal flow by publishing it as a catalog flow. This publishing will create a separate catalog template (copy of your flow), your personal flow itself will not be available to others.
A catalog flow is intended for company-wide access. It is effectively a flow template that other users can adapt for their needs. Only admin users can create, update, and delete catalog flows. End users can use catalog flows, provided the flows have not been restricted by an admin user.
See Finding existing flows for instructions to look up existing personal and catalog flows for your user account.
Before you begin
Ensure that you can access BMC Helix Integration Studio (see Access and installation). No prior technical knowledge is required to design flows, but you should be familiar with the source and target applications as a user.
Process of designing flows
If you need to design a flow, perform the sequence of steps represented in the following illustration:
You can design a new flow on the My Flows page:
You can perform the following additional actions with the designed flow: