| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
What is an
Actionflow| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Use 
Actionflows in s are used in applications created in version 9.0 and laterbeyond.
An Actionflow is a diagram that represents a sequence of action steps and data flows.
Each Actionflow belongs to an application and is reusable within that application. Actionflows are made up composed of individual actions (nodes) that are wired together, and have input and output connections to screens, buttons or tables.
Actionflows are designed to be resilient to name changes in screens, components, tables and attributes.
Why are Actionflows used in PhixFlow?
Actionflows make PhixFlow applications interactive. They convert a static screen into a user interface, combining simple individual actions into complex functionality.
This enables the application user to interact with the screens, screen components and data.
The /number/ principles of an Actionflow
Include:
- Actionflows to that insert a new record records do not need any data to run them and can be ON therefore should have an Input Connection of On Click
- Actionflows to edit an existing record do need data to run them Actionflows requiring data to run them should always be given and therefore should have an Input Connection using a Datasource
- Always map in the minimum amount of data possible to run the Actionflow, e.g. just the UID