| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Excerpt | ||
|---|---|---|
| ||
What is an Actionflow? |
An Actionflow is |
a diagram |
that represents a sequence of actions and data flows |
Example Actionflow
Actionflows...
controlwithin 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 |
| Excerpt | ||
|---|---|---|
| ||
Example ActionflowFor this example Actionflow, the user clicks a button to trigger the Actionflow that saves a new record containing the text "New".
|
| Excerpt | ||
|---|---|---|
| ||
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. |
The Principles of Actionflows
- All Actionflows require an input, this can be data or an input action (user interaction or scheduled task/task plan)
- To use data within an action node it must be mapped into an input parameter for that node
- Action nodes return data to the Actionflow as Output Attributes
- Actionflows only require minimal data to be mapped in for it to run, e.g. just the primary key, because we can look the data up using a unique identifier (UID)
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. |
| Excerpt | ||
|---|---|---|
| ||
Actionflow Simplified OverviewThe 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.
|
How to Create Actionflows
On a screen, any component that has an
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
On a screen, click a component to display its properties. Components that can have Actionflows are:
- buttons
- grid views
- card/containers
- areas
- form fields
Create via Buttons
Right click on a button and select Add Actionflow.
Create via Event Handler
In the component properties →
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
- Event Type: select an event type
- Action Method: select Actionflow
Insert excerpt _save _save nopanel true - Actionflow: click
Insert excerpt _add _add nopanel true 
Create via Action Settings
Add via an action directly.
- Action Method: select Actionflow
- Actionflow: click
Insert excerpt _add _add nopanel true 
