2. AsyncFlow Control

Configure the AsyncFlow Control

Praise Magidi avatar
Written by Praise Magidi
Updated over a week ago

In this article, each Ops Portal view section will be discussed in detail, covering the selections, settings, and options of the AsyncFlow control.

The AsyncFlow control creates a view that can monitor all flows in Asynchronous Mode which implies that the flow will run but no data is returned to the flow. Typical uses will be to monitor and test flows that synchronize data or send data by email.

This article describes how to:

Watch the tutorial video below to learn how to create the AsyncFlow View using the Synatic Operations Portal.

Creating a new AsyncFlow View

Go to the Operations Portal menu and select the Operations Portal Tutorial.

  1. Adjacent to the Views tab, click ⨁ to add a new View.

3. Give the View a name and a meaningful description.

The Control type

Click on the Control field and select the AsyncFlow control to display the data captured in the selected Flow. The AsyncFlow control window for this View opens and lets you edit the relevant values and options as described below.

The Flow

Each View created requires that a Synatic Flow is selected. You may create a new Flow by clicking ⨁ or alternatively, you can select the Flow you want to use from the selection list.

Input Schema

The Input Schema is used only in cases where a Synatic Flow has been configured to capture input data before it can execute. The input data might relate to fields in an attached database to search for or filter the output data. Alternatively, the input value may be used in a calculation.

We'll use the Input Schema designer to build an input form to capture and pass data to the selected flow.

  • The Schema Viewer and Raw Schema tabs are used to view the data only.

  • The Designer tab is used to add input fields to capture the required data.

  • You click + to add data objects.

  • The "string" option is used to select the appropriate data type from the selection list.

  • The Required checkbox is selected to ensure that the value is entered at runtime. The flow will not continue if the value is not entered.


The following options must be set or selected to define the output display and available functionality:

  • Allow File Upload - This option instructs the view to request a JSON file if the assigned Flow requires input data from a data file.

  • Mini View - Select this option to minimize the View's output display.

  • Show Runs - Select this option to display a list of previous runs executed by the assigned Flow.

  • Allow Events - Select this option to display the View RunEvents button and when clicked will show Events associated with Flow executed runs.

  • Allow Records - Select this option to allow you to view associated records in the View's output display.

Save the View

When you have completed the View's configuration, click the Save View button.

Test the View

It is always advisable to test each view you create in Synatic's Ops Portal.

1. Select the Ops Portal option in the Account menu to open the Operations Portal. This is also the method used by the operations personnel to process these views.

2. Select and run the view you created from the list of available views.

3. The Execute Flow button must be clicked to execute the Flow assigned to the View unless the Execute Automatically option (available in some Controls) is selected.

  • Input Parameters. Enter any input parameter values, if configured and required by the View.

  • The RunID value is also shown.

  • The Flow assigned to the View is shown.

  • The Total Records Completed by the Flow are also shown.

  • The View RunEvents button is available to display any events associated with the flow.

The Flow Canvas displays the flow that was executed and the following information is shown:

  • An info panel showing dates and times.

  • Each step object in the flow shows the number of records that were:
    (C) Completed - These are successfully completed records.
    (E) Error - These are records that are in error.
    (O) Other - These are line items in the data file representing skipped records, headers, and footers.

  • You can also click on each step object to display the records processed if configured to display.

Useful Tutorials

Revisit the Getting Started page for a refresher.

Learn more in the Operations Portal tutorials.

Did this answer your question?