This page is for application designers who want to create actionflows to add functionality to an application screen. For actionflow concepts, see Understanding Actionflows.

Using data from the starting screen in an actionflow

Actionflows can use data displayed on screens. This data can be manipulated within an actionflow and can be saved onto tables. Examples of data sources that can be used are:

• Forms
  The form fields displayed on the screen can be mapped into an actionflow to be manipulated/saved
• Grids
  Selected, edited, dragged, dropped and all displayed (page) records can be mapped into an actionflow.
• Card components
  Selected, edited, dragged, dropped and all displayed (page) records can be mapped into an actionflow.
  

Screens can display multiple data sources. Users must connect the desired data source to the input connection point of the actionflow, so that that data can be used within the actionflow. To connect data

1. Click connect
   
2. Select the data to be used in the actionflow
   
3. Map required attributes
    
   Mapped attributes are now available to be used within the actionflow.

What if I don't need to use any data?

It is likely that an actionflow does not require any data from the screen it is being initiated from. In this instance the event is used as the input for the actionflow. Connecting to the event (e.g. On-Click, Double-Click) means that the actionflow will run regardless of any data supplied.

Actionflow interface

In the above examples, the data or event, are being connected (and mapped) to connection points on the interface of the actionflow. The interface separates the contents of the actionflow from the specific actionflow instance that is being built. Creating attributes on the connection points on the interface means that we can reuse the actionflow in different contexts, all the user has to do is re-map the attributes from their new data to the connection points for it to work in a second instance.

Inside the actionflow, nodes must start by being connected from the interface connection point. For more information, see below.

What's next?

Using Actionflow Nodes

Wiring Actionflows