| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
What is an Actionflow?
An Actionflow is a diagram that represents a sequence of actions and data flows.
Example Actionflow
Actionflows...
- control the interactions users have with your application and its data, e.g. opening a new screen to edit data
- belong to an application or package and can be reused in multiple locations within your application but with different inputs, e.g. address cleansing/finder
- are composed of individual actions (represented as nodes) that each perform a specific task, e.g. opening a screen or saving data
- have input and output connections to screens, buttons or tables
- are designed to be composable, e.g. can be combined and are data agnostic
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 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)