| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Iframe | ||||||
|---|---|---|---|---|---|---|
|
Actions make PhixFlow applications interactive, converting a static screen into a user interface. Simple individual actions can be combined to provide complex functionality. This enables the application user to interact with the screens, screen components and data.
Actions can be configured using either actionflows or recordtable-actions.
Actionflows
Use
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Actionflows are diagrams that represent a sequence of action steps. Actionflows:
belong to an application
are reusable
are made up of individual actions (actionflow nodes) that are wired together
- have input and output connections to screens, buttons or tables
are designed to be resilient to name changes in screens, components, tables and attributes.
Learn how to configure user interactions with Actionflows.
Table-actions
Use
in applications created in versions 8.3 and earlier.Insert excerpt HELP82:_stream_action HELP82:_stream_action nopanel true
Table-actions:
belong to a table (previously called a stream)
use table and attribute names
- are made up of a list of record-actions that run in sequence to update data and interact with screens.
can have rules or context parameters to determine when a record-action runs.
Learn how to configure user interactions with Stream Actions.
Example Action
The adjacent animation shows a user interacting with a Contacts application to:
- Select a contact record.
- Edit the DOB field.
- Save the change.
Updating a contact in a Contacts application
