What is a Wait Action?

 Wait actions hold any records passed into them until all previous action nodes have finished processing. The Wait action then outputs a count attribute containing the sum of all records it has received. 

Action Setup

Input Connection Points

 Wait actions have a single input connection point containing no mappings and no ability to create mappings.

Output Attributes

 Wait actions have a pre-configured count output attribute which automatically calculates the sum of all records it has received, once all previous action nodes have completed their processing.

 Wait actions always generate a single output record regardless of the number of input records (including 0). 

Output Connection Points

 Wait actions can have any number of output connection point(s) which can be used to pass the count attribute to other action(s).

 Loop Considerations

When a  Wait action is used inside of a  Loop, it generates a single output record for each iteration of the loop regardless of the number of input records (including 0), once all action nodes in the iteration have completed their processing.

For more on Loops, see 3.08 Loop Action Configuration.

Creating Wait Actions

1. Click and drag the  Wait icon in the toolbar onto the canvas
2. Enter a name for the Wait action, then select Create Action
3. Connect the  input node or other action node to the  Wait action's input connection point 
   1. The Mappings window will open but no attributes can be mapped into the Wait action
4. Connect the  output node or other action node to the  Wait action's output connection point 
   1. The Mappings window will open where the count attribute can be mapped out

Example Uses

The  Wait action is useful in a number of use cases.

• Where multiple records require complex processing and only once this has finished, a separate single process is required 

• Handling special case logic for when paths receive no records - eg  Gateway actions,  For Each actions or   View actions returning no response records, or no records in a driving grid

• With parallel paths+funnel - outputting a final trigger record after all the others have been processed (e.g. to trigger the end of the transaction, or write out a final end record.  

For  Wait action  Properties, see Wait Node Properties.