Skip to main content
Feedback

Using Flow Service component Data Actions with Flow

This type of Flow Service Operation is used to integrate with the database steps in Flow that are used to handle all Create, Read, Update, Delete (CRUD) operations for a particular variety of record, using a single type in a flow.

Database load steps, Database save steps, and Database delete steps allow Flow to integrate with your Flow Service Data Actions and their associated processes.

Data actions are useful if you intend to send/retrieve the same kinds of records through multiple processes, as using a Message Action will automatically create a Request and Response type in the flow for any asscoiated processes. Using database steps also allows you to display data from a service directly in a flow page, using certain page components, such as a Combobox, Radio, or Table component.

For a worked example of how you can use Data Actions with Flow, see A worked example of using Data Actions with Flow.

Flow Service Data Actions are mapped to Flow as follows:

Flow Service Data Actions

  • The JSON Profile you assign to the Data Action is used by the Flow Service to automatically create a corresponding type in Flow. Step 1

  • Either the Get Process or the Query Process will be initiated by a Database Load step in Flow, depending on the filter options specified in the step Data Action (see below). Step 2

  • The Save Process will be initiated by a Database Save step in Flow. Step 3

  • The Delete Process will be initiated by a Database Delete step in Flow. Step 4

When is a Get Process or Query Process used?

A Database Load step Data Action can initiate either a Get Process or a Query Process, depending on the filter options specified.

  • If a filter based on a unique identifier is specified for the Data Action in the Database Load step, the Get Process will be initiated. Only a single record is returned, and a unique identifier must be used.

    Get Process

  • If no filter or filter by ‘where’ is specified for the Data Action in the Database Load step, the Query Process will be initiated. Multiple records can be returned with a Query, typically by populating a List value with the query results. These results can then be surfaced by loading this data directly from the service into a table component.

    Query Process

Data Action profiles and Flow types

A Data Action profile always creates a single type in Flow; this type handles both Objects and Lists through the same single level JSON profile Object.

Data Action Profile and type

  • This is different to Flow Service Message Actions that do not always create a type in Flow, and also creates types that are specific to the Request or Response of a single particular process. See Integration Profiles and Flow Types.

  • Profiles should typically be configured as a ‘flat’ JSON Object profile.

On this Page