TThis This page provides details of the properties for the phase node. These are part of actionflows.

Overview

Image Removed

Actionflows process data one record at a time. However, sometimes you may want to process all records up to one point, before moving on to the next process. For example, you may first want to check all the data before starting to process the first record. One way to do this is to have separate actionflows, so that all the data is processed by one actionflow, saved to a table and then the table is used at the start of the next actionflow. The other way is to use Image Added

Use a 

Phase nodes act as an internal break in the actionflow. For example, you can have one phase in which records are read into the actionflow and checked one at a time. Once all records have been validated, the actionflow can then move to the next phase, where records are updated. Phase nodes are particularly useful if there the actionflow requires the user to make a choice as part of the actionflow. 

Example

Configuring a Validation Phase

A user wants to check some company fields before saving them in an actionflow. The simplest way to do this is to add a new phase before the existing processing phase. The new phase will contain all the logic to check the fields, and only pass on validated fields to the next phase.

Image Removed

Use the following steps:

• to add validation to the fields
• to check that a company name has been provided
• to check that the phone number only contains numbers.

Expression:

do(
	//set error message variable to use in the validation

	$errorMessage = [],

	//check the company name is populated

	if(in.CompanyName == _NULL, 

		$errorMessage = addElement($errorMessage, "Please provide a name")
	),

	if(contains(in.Number, [abc]),

		$errorMessage = addElement($errorMessage, "Phone number should not contain any letter")
	),

	if(countElements($errorMessage) > 0,

		do(
			error(listToString($errorMessage, ", ")),

			false
		),

		true
	)
)	

In the wire properties → Basic Settings → Expression, add:

in.ValidRecord

This ensures only valid records pass to the next phase.

The completed validation phase of the actionflow looks like this:

Image Removed

Configuring a Confirmation Phase

A confirmation phase is useful if the user must:

A confirmation phase usually opens a pop-up window. The following steps assume this screen has already been designed.

To add a confirmation phase:

Sarah todo: add video once working in product. At the moment, adding a phase is just adding a node called Processing Phase. It's not prompting for a phase type or for a name.

 to split your actionflow into phases that process all records up to one point, before moving on to the next phase; see Using Actionflow Phases.

Insert excerpt
_property_tabs _property_tabs name basic-h nopanel true

Basic Settings