Skip to main content
Feedback

Using the Flow service component with Flow

A Flow Service component is set up in Integration to build and manage the connection to Flow.

You use this component to implement the callback logic required to continue Flow progression once the integration process completes. It manages timeouts by returning wait responses to Flow while a process executes.

The Flow Service component is specifically used by Flow for:

  • Defining the Path to Service

  • Mapping Boomi Flow Service Operations to actions/steps

Defining the path to service

You use the Path to Service field on the General tab of the Flow Service to define the path to the connector on a basic runtime.

The connector URI used by the Boomi Flow Integration Service in Flow uses this Path to Service value.

Flow Service Path to Service

Mapping Flow service operations to actions/steps

You will need to configure the Flow Service to match your operation/action requirements.

The Boomi Flow Service Operation that you have selected in your process Flow Services Server Start step defines what type of operation is going to be performed in your Flow. For example, it defines whether the process supports a Message Action, a File Resource, or a Data Action, and what JSON Request/Response profiles you should use for exchanging data.

Service Operations

Message actions

Flow Service Message Actions are used to map to message actions in a message step in Flow. A message step can be added to a Flow in order to send and receive message requests between Flow and the Integration Flow Service. A Flow uses message actions to define the interface of inputs/outputs when calling against your Flow Service Message Actions. This allows you to map values in a Flow to the inputs and outputs specified by your Flow Service.

For more information, refer to Message Actions tab in Flow Service components.

File resources

Flow Service File Resources are used to map to either of the two page layout components available in Flow for interacting with files. The File Upload component allows you to upload a file, which can then be consumed by a process. The Files component allows you to both upload a file, and list files for download from an outside system.

For more information, refer to File Resources tab in Flow Service components.

Data actions

You use Flow Service Data Actions to integrate with the database steps in Flow. These steps handle all Create, Read, Update, Delete (CRUD) operations for a particular variety of record, using a single type in a Flow. There are three types of database step that you can add to a Flow (Load, Save, and Delete) to integrate with your Flow Service Data Actions and their associated processes.

For more information, refer to Data Actions tab in Flow Service components.

Page components

Table, Combobox and Radio page components can also be populated with data using the connector. For example, data can be loaded directly from the Flow Service (or via a list value) into a Table component on a page in order to display data to Flow users.

For more information, refer to General tab in Flow Service components.

On this Page