What is a Wait Action?

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

In PhixFlow v12.1+, the Wait action does pass through the last received record, in addition to the count attribute, once it has finished processing all input records.

For the full list of Wait action  Properties, see Wait Action Properties.

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 contains a count of the number of records received, produced once all previous actions have completed their processing
  • Always generates an 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)
  • does not pass through any of the attributes it has received (PhixFlow v12 and older)

Considerations

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

For more on Loops, see 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 action or other action to the  Wait action's input connection point 
4. Connect the  output action or other action 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. For example, new records must be saved before continuing and View Action is used post Wait Action to then continue processing.

• Handling special case logic for where connectors receive no records, e.g.  Gateway actions,  For Each actions or   View actions returning no response records, or no records in a grid

• With parallel connectors and a  Converge action - where you need to output a final record after all other actions have completed, such as, to trigger the end of a transaction, or to write out a final end record

For  Wait action  Properties, see Wait Action Properties.