This page is for application designers who want to configure user interactions with data, such as delete or update. It has the reference information about actionflows and their nodes.
Todo-Fiona: page in draft
Overview
For concepts see Understanding Actionflows
This page outlines an overview of how to create actionflows.
Creating an Actionflow
Any Phixflow component with an tab can have an actionflow added to it.
To create an actionflow:
- In a screen, click a component to display its properties. Components that can have actions are:
- buttons
- grid view
- card/container
- areas
- form fields
- There are 3 ways to add actionflows. In the component properties → ActionflowSettings:
- Adding via an event handler
- click Add New
- Event Type select an event type
- Action Method select Actionflow
- Apply
- Actionflow, click Add New
- Adding via an action directly
- Action Method select Actionflow
- Actionflow, click Add New.
- Quick add for buttons
- Right click on a button and select Add actionflow
- Right click on a button and select Add actionflow
- Adding via an event handler
- PhixFlow opens the actionflow canvas.
- Drag actions from the toolbar onto the central canvas
- Wire the actionflow and connect
- instance inputs
- action nodes
- instance outputs (optional)
For more detail on actionflow nodes and wiring, see below.
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