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 tenant administrators can use the Flow Designer options in BMC Helix Integration Studio to design and maintain their flows.
The following are the examples of the common flows that can be created in BMC Helix Integration Studio:
- Remedy ITSM to Atlassian 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.
- Slack to Gmail flow: a new message in a specific Slack channel triggers an email to be sent out to a certain audience.
No prior technical knowledge is required to design and maintain flows, but you should be familiar with the source and target applications as a user.
Types of flows
There are two types of flows available for end users and tenant administrators: personal flows and catalog flows.
A personal flow is intended for a user's personal use and cannot be accessed by anybody else using BMC Helix Integration Studio, including tenant administrators. 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 creates a separate catalog template (copy of your flow), and your personal flow itself is not 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 tenant administrators can create, update, and delete catalog flows. End users can use catalog flows, provided the flows have not been restricted by a tenant administrator.
See Finding existing flows for instructions to look up existing personal and catalog flows for your user account.
Working with flows
As a tenant administrator or an end user, you can design and maintain your flows by using Flow Designer on the My Flows page:
The following table provides information about the available options for designing and maintaining flows:
Create a new flow for your personal use. Copy and adapt a similar personal flow to spend less effort on designing a new flow manually.
|Adding or copying flows|
|Create a flow that consists of more than one action to complete complex business tasks.||Creating flows with multiple actions|
Change the status of your flow or initiate a personal flow on demand for testing purposes.
As a tenant administrator, enable or disable a catalog flow for end users.
|Activating or enabling flows|
Use an existing catalog flow as a template for your personal flow to avoid creating a new flow manually.
Publish your personal flow to the catalog, so that other users in your company can use it as a template for their personal flows.
|Publishing or using flows|
|Edit your existing personal flow to change some of its options. Delete your personal flow if it no longer serves your business purposes.||Updating or deleting flows|
|Upgrade your personal flow that was initially created from a catalog flow to incorporate enhancements (if a newer version of the catalog flow is available).||Upgrading flows|
|Apply transformations to mapped fields to establish complex relations between a source and a target application and make your flow deliver the transformed data.||Transforming mapped fields|