| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
What is an Actionflow?
Use 
Actionflows in applications created in version 9.0 and later.
An Actionflow is a diagram that represents a sequence of action steps.
Each Actionflow belongs to an application and is reusable within that application. They Actionflows are made up 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.
How 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.
Actions can be configured using either actionflows or table-actions.
The /number/ principles of an Actionflow
Include:
- Actionflows to insert a new record do not need data to run them and can be ON Click
- Actionflows to edit an existing record do need data to run them
- Actionflows requiring data to run them should always be given the minimum amount of data possible, e.g. just the UID