Category: Workflow / Internal
This action stops project execution without producing an error. This action only works in EasyMorph Desktop and only in the current module. It's ignored in called/iterated modules or when executed not in EasyMorph Desktop.
Breakpoint is useful for debugging heavy workflows by inserting them between actions to prevent downstream calculations and/or move through one chain of actions at a time.
Alternating workflow branches can be created for comparing the outcomes of two different process paths (see the illustration below).
|Current state||The present state of the action. Options: Break (active; project execution stops at the Breakpoint) or Continue (inactive; project bypasses the Breakpoint).|
|State on project opening||The default state of the action when the project is opened. Options: Break (active; project execution stops at the Breakpoint) or Continue (inactive; project bypasses the Breakpoint).|
|Change state||Select when this action's state toggles from "Break" to "Continue", or "Conintue" to "Break". Options:Never, Alternate on each run, or On condition. See below for details.|
|Never||The action keeps the currently configured state ("Break" or "Continue").|
|Alternate on each run||The state toggles from "Break" to "Continue", or "Continue" to "Break", on each subsequent run of the workflow.|
|On condition||Halt the workflow execution when a specific condition is met prior to reaching the Breakpoint. Options: Halt if table is empty, Halt if table is NOT empty, Halt if the condition is true for EVERY row (enter an expression to evaluate) or Halt if the condition is true for ANY row (enter an expression to evaluate).|
For either of the "condition" options, select how EasyMorph will react if the condition refers to a field, but the table has no rows (e.g. data) at the time of the Breakpoint. Options: Break anyway or Do NOT break.