Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue

What is an
Insert excerpt
_actionflow_icon
_actionflow_icon
nopaneltrue
 Actionflow?

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

Each Actionflow belongs

Actionflows...

  • control the interactions users have with your application and its data.
  • belong to an application and
is reusable
  • can be reused in multiple locations within that application
. Actionflows 
  • and with different inputs
  • are composed of individual actions (nodes)
that are wired together, and 
  • that each perform a specific action, such as opening a screen or saving data
  • have input and output connections to screens, buttons or tables
.
Actionflows
  • are designed to be resilient to name changes in screens, components, tables and attributes
.

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

  • 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 Actionflow, e.g. just the UID