What is a Wait Action?

Action Setup

• Input Connection Points

• : A single input connection

• point containing no mappings and no ability to create mappings

• Output Attributes

• : 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

• • Always generate a single output record regardless of the number of input records (including 0)

• Output Connection Points

• : 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

For more on Loops, see 3.08 Loop Action Configuration.

Creating Wait Actions

1. Click and drag the 

   Insert excerpt
   _action_wait _action_wait nopanel true

    icon in the toolbar onto the canvas
2. Enter a name for the Wait action, then select Create Action
3. Connect the 

   Insert excerpt
   _input _input nopanel true

    node or other action node to the 

   Insert excerpt
   _action_wait _action_wait nopanel true

    action's input connection point 
   1. The Mappings window will open but no attributes can be mapped into the Wait action
4. Connect the 

   Insert excerpt
   _output _output nopanel true

    node or other action node to the 

   Insert excerpt
   _action_wait _action_wait nopanel true

    action's output connection point 
   1. The Mappings window will open where the count attribute can be mapped out

Example Uses

The 

• 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 

  Insert excerpt
  _action_gateway _action_gateway nopanel true

  actions, 

  Insert excerpt
  _action_for_each _action_for_each nopanel true

  actions or 

  Insert excerpt
  _action_view _action_view nopanel true

   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