Takes the message to be displayed as input, can either be one created by the user or pulled from another source. If this Action runs it will stop the current Workflow, vetoing any work already done in the Workflow and popping up the message. When vetoing a Database Event any changes to a Biskit will be rolled back including stopping the Biskit from being created or updated.

 

veto

 

Properties Available for Child Actions To Use

There are no additional properties available for use in any child or descendant action beyond the standard set.