Skip to main content
Feedback

A worked example of using Integration data actions with Flow

This topic provides an example of how you can use Integration Flow Service Data Actions to retrieve and work with data in Flow.

In this example, a Flow is built in the Flow canvas that allows users to save, query, load, and delete data to and from a simple database in Integration.

Before you begin

Before working through this example, ensure you are familiar with the following:

Integration setup

Integration is set up as follows:

  • A PostgreSQL database table is set up to act as the target data system for the processes to interact with.

  • A Flow Service component is set up, and a Flow Service Data Action added to it.

  • The JSON Profile for the Data Action consists of a single level 'Contact' Object.

  • You create and assign a process for each type of request, using a Flow Services Server listener process Start step. The Flow Service Operations are set as a 'Data Action' Service Type, with the relevant Data Action Operation selected (Load, Save, Delete).

  • Deploy all elements to a cloud attachment.

Flow setup

Flow is set up as follows:

  • You install and configure a Boomi Integration Service connector to connect to the Flow Service component in Integration.

  • Flow automatically creates a 'Contact' type from the Integration profile once you install the service. You associate this type and its properties/binding with values to allow data to be passed to and from Flow.

  • You create a main 'Contact' Object value to store and work with data of this type.

A Flow is built in the Flow canvas to allow users to save, query, load, and delete data to and from the database:

Example Flow

The Flow is laid out in four main sections:

When the user runs the Flow in a web browser, the landing page displays:

Example Flow

On this Page