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 Version History

« Previous Version 4 Next »

What are Phases?

Actionflows process data one record at a time. However, sometimes you may want to process all records up to a point, before moving onto the next process.  Phases allow this to happen by acting as an internal break in the Actionflow. 

Phases are useful to check all data coming out of one Actionflow before starting another Actionflow, or where one phase reads records into the Actionflow and checks them one at a time. Once all records have been checked, the Actionflow can then move to the next phase, where records are updated. Phase nodes are particularly useful if the Actionflow requires the user to make a choice as part of the Actionflow.  

Creating Gateway Actions

  1. Click and drag a  Start Phase icon in the toolbar onto the canvas
  2. Click the  Add Phase option that appears
    1. Enter a name and optional description for the Phase, then select Create Action
  3. The Phase action will show on the canvas and a new phase will be added next to the Processing Phase 

Example Setup

This is an example of a  Phase being used to initiate a separate Actionflow after a successful sync to a CRM system .

Worked Example

For a worked example of setting up a phase, see 1.13 Confirmation Message Configuration. The Shop Data (available from the Learning Centre) can be used following these steps.

If you are completing this chapter as part of the Actionflow course and using a training instance, the data and screens have already been pre-loaded into the Actionflow Intermediate Application. For this example, set up a confirmation phase on the Actionflow on the Delete button on the Shop Staff screen.

1.02 Actionflow Principles

  • No labels