What is an Actionflow?
- A diagrams that represent a sequence of actions and data flows within an application
- control the interactions users have with an 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"
- are represented by the
icon
COMPOSABLE DEFINITION: Composable architecture is a microservices approach to building your tech stack, combining a constellation of different reusable technologies to create one unified system that can communicate via APIs. This breaks down complex ecosystems into more manageable chunks for better oversight, flexibility, and adaptability
Example Actionflow
This is an example Actionflow where a user clicks to save data.
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 and data.
Reusability ...
Add infographics - AG to provide updated diagram
The Principles of Actionflows (put in own page)
- 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)