What is

an Actionflow?

Insert excerpt
_actionflow_icon _actionflow_icon nopanel true

An Actionflow is a diagram that represents a sequence of action steps actions and data flows.

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 that application and with different inputs, e.g. address cleansing/finder
• are composed of individual actions (nodes) that each perform a specific actiontask, such as opening a screen or saving data
• have input and output connections to screens, buttons or tables

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

• All Actionflows that insert new records do not need any data to run them and therefore should have an Input Connection of On Click
• Actionflows to edit an existing record do need data to run them and therefore should have an Input Connection using a Datasource
• Always map in the minimum amount of data possible to run the Actionflowrequire 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 to run, e.g. just the primary key. This is because we can look the data up using a unique identifier (UID)