This page is for application designers who want to create actionflows to add functionality to an application screen. For actionflow concepts, see Understanding Actionflows.
Actionflows can use data displayed on screens. This data can be manipulated within an actionflow and can be saved onto tables. Examples of data sources that can be used are:
- Forms
The form fields displayed on the screen can be mapped into an actionflow to be manipulated/saved - Grids
Selected, edited, dragged, dropped and all displayed (page) records can be mapped into an actionflow. - Card components
Selected, edited, dragged, dropped and all displayed (page) records can be mapped into an actionflow.
Screens can display multiple data sources. Users must connect the desired data source to the input connection point of the actionflow, so that that data can be used within the actionflow. To connect data
- Click connect
- Select the data
What if I don't need to use any data?
What's next?
Terminology changes in progress As part of the redesign of PhixFlow, we are changing the following terms: dashboard → screen
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action
stream action → table-action
driver class → database driver