Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
transformations:breakpoint [2021/11/16 17:48] – update graphic craigt | transformations:breakpoint [2022/01/31 14:57] – Update to 5.1.2 modes. craigt |
---|
\\ | \\ |
=====Description===== | =====Description===== |
This action stops project execution without producing an error. This action only works in EasyMorph Desktop. | 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 not executed in EasyMorph Desktop. |
| |
\\ | \\ |
=====Use cases===== | =====Use cases===== |
//Breakpoint// is useful for debugging workflows by inserting them between actions to create "step-by-step" workflows and moving through one chain of actions at a time. | //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). | |
| |
{{ transformations:breakpoint_small.png?580 }} | |
| |
\\ | \\ |
=====Action settings===== | =====Action settings===== |
^ Setting ^ Description ^ | ^ Setting ^ Description ^ |
|Current state|The present state of the action. Options: //Break// (active; project execution stops at the Breakpoint) or //Continue// (inactive; project bypasses the Breakpoint).| | |Current state|This displays the current state of the action. Options: //Break// (active; project execution will stop 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).| | |Mode|Refer to the table below for details about each Breakpoint mode.| |
|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.| | |
| |
\\ | \\ |
====Change state settings==== | ====Mode settings==== |
^ Setting ^ Description ^ | ^ Setting ^ Description ^ |
|Never|The action keeps the currently configured state ("Break" or "Continue").| | |Break, continue on manual run|The workflow will stop. This action, and all downstream actions, must be run manually.| |
|Alternate on each run|The state toggles from "Break" to "Continue", or "Continue" to "Break", on each subsequent run of the workflow.| | |Constant breakpoint state|Set the Breakpoint state whenever the project is opened. Options: //Break// or //Continue//. In this mode, you can also set the //Current state//.| |
|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).| | |Break on condition|The workflow stops if the selected condition is met. Options: //Break if table is empty//, //Break if table is NOT empty//,\\ //Break if the condition is true for EVERY row//, and //Break if the condition is true for ANY row//.\\ \\ 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//.| |
| |
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//. | |
| |
| |
\\ | \\ |