Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

This topic is for application designers who want to configure user interaction for their application.


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 stream item actions.

Actionflows

Use actionflows in applications created in version 9.0 and later.
Actionflows are diagrams that represent a sequence of action steps. Actionflows:

  • belong to an application

  • are reusable

  • are made up of specific 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.

See Actionflows.

Stream-item-actions

Use stream-item-actions in applications created in versions 8.3 and earlier.
Stream-item-actions are individual action steps that transform table data. Stream-item-actions:

  • belong to a table (previously called a stream)

  • use table and attribute names

  • are run in sequence to update data and interact with screens.

  • can have rules or context parameters to determine when a stream-item-action runs.

Stream actions and stream item actions.

Stream Actions Stream-item-actions

Example Action

The following animation shows a user interacting with a Contacts application to: 

  1. Select a contact record.
  2. Edit the DOB field.
  3. Save the change.
Updating a contact in a Contacts application

What Next?

See also

  • No labels