Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
This action is available in PhixFlow version 11.2+.
What is a Wait Action?
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
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)
- does not pass through any of the attributes it has received.
Considerations
When a
action is used inside of a Insert excerpt _action_wait _action_wait nopanel true
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
For more on Loops, see 3.08 Loop Action Configuration.
Creating Wait Actions
- Click and drag the
icon in the toolbar onto the canvasInsert excerpt _action_wait _action_wait nopanel true - Enter a name for the Wait action, then select Create Action
- Connect the
node or other action node to theInsert excerpt _input _input nopanel true
action's input connection point The Mappings window will open but no attributes can be mapped into the Wait actionInsert excerpt _action_wait _action_wait nopanel true - Connect the
node or other action node to theInsert excerpt _output _output nopanel true
action's output connection pointInsert excerpt _action_wait _action_wait nopanel true - The Mappings window will open where the count attribute can be mapped out
Example Uses
The
action is useful in a number of use cases. Insert excerpt _action_wait _action_wait nopanel true
- 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 where connectors receive no records - eg , e.g.
actions,Insert excerpt _action_gateway _action_gateway nopanel true
actions orInsert excerpt _action_for_each _action_for_each nopanel true
actions returning no response records, or no records in a driving gridInsert excerpt _action_view _action_view nopanel true With parallel paths+funnel - outputting a final trigger record after all the others have been processed (e.g. connectors and a
action - where you need to output a final record after all other actions have completed, such as, to trigger the end of the a transaction, or to write out a final end record.Insert excerpt _action_converge _action_converge nopanel true
For
action Insert excerpt _action_wait _action_wait nopanel true
, see Wait Node Properties. Insert excerpt _property_settings _property_settings nopanel true
HTML Comment | ||
---|---|---|
| ||
|
Tip |
---|
If you are completing this chapter as part of the Actionflow course and using a training instance, the data and screens have already been pre-loaded into the Actionflow Intermediate Application. For these example, we'll be working on the Shop Stock screen. |
Weekly Timesheet Reminder Email
In this example, we'll set up an Actionflow that retrieves the email address for specific staff members and sends them an email to remind them to fill in their timesheets. We'll then add this Actionflow to a Task Plan and specify the frequency (weekly) and day (Friday) that we want the email to be sent on.
Create Actionflow
On the Actionflow homepage, create a new ActionflowName: Timesheet Email