| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
What is an Actionflow?
An Actionflow is a diagram that represents a sequence of actions and data flows within an application. It controls the interactions users have with an application and its data, e.g. opening a new screen to edit data.
Actionflows are composed of individual actions nodes that each perform a specific task, e.g. opening a screen or saving data, and have input and output connections to screens, buttons, tables or other Actionflows.
Actionflows belong to an application or package, and are represented by the 
icon.
Example Actionflow
For this example Actionflow, the user clicks a button to trigger the Actionflow that saves a new record containing the text "New".
| Tip |
|---|
All images in this course can be clicked on to make them larger. |
Why are Actionflows used in PhixFlow?
Actionflows make PhixFlow applications interactive. They convert a static screen into a user interface by combining individual actions into advanced functionality. This enables an application user to interact with the screens and data.
Actionflows are composable and reusable across an application but with different inputs connected, making Actionflows "data agnostic" and flexible, and ultimately saving time and effort.
Actionflow Simplified Overview
The following diagram illustrates a simplified view of an Actionflow that is being used by two different applications.
The Actionflow is set up to take in a value, Area Code, and return an value, Normalised Area Code, in the form of an Output value. The Contact App maps a Postcode onto the Area Code, this is then processed by the Actionflow to produce a Normalised Area Code, and the Actionflow returns a normalised version of the Postcode. The Logistics App also uses the Actionflow, which is a different instance, and this time a Zip Code is mapped in.
The returned Output can be used by the applications, for example, mapping the output onto a form field on a screen to display it.
Action
