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

« Previous Version 12 Next »



Execution Blocks

Execution blocks include Actions and optionally include Conditions, which are additional requirements that need to be met in order to run the Actions. Execution Blocks are executed in descending order within the Execution Plan. You can visually distinguish blocks by their IF, ELSE IF, or ELSE EXECUTE statements. Whether or not the Actions within an Execution Block will run is dependent upon any connected Conditions, if they are included. Execution Blocks are necessary for Execution Plans to be saved; you must have at least one Execution Block. 

Execution Groups

Execution Groups are collections of Execution Blocks that are run in the order that they appear in the Execution Plan. When an Execution Plan reaches the bottom of the first Execution Group, it will move on to the next group (if more than one group exists). Execution Groups run every time associated Triggers are met for the Execution Plan.

Organizing Execution Groups

Execution Groups may be re-ordered at any time by dragging the group tabs into the desired order. Group tabs may also be renamed with custom names.


The following scenarios present logic errors that prevent Execution Plans from functioning properly.

  1. Using the same result field in multiple groups within an Execution Plan.
  2. Using the same result field twice in the same Execution Block.
  3. Using the same result field among multiple Execution Plans in the same project.

  • No labels