Start of Task Node

From PresenceWiki
Revision as of 07:46, 20 August 2015 by Rob (Talk | contribs)

(diff) ←Older revision | view current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Start of Task Node

This is used to indicate the first Node that should be executed in case of ambiguity. No Nodes can connect into a Start Node. When executing a Start Node does nothing other than create a low priority log entry.


The main function of a Start Node, as well as providing people who view the Task with an idea of where it starts, is to tell Presence where to start running the Task. For example consider the following Task:

Eek no start node.png

Should Presence run the XML Query first, or the SQL Query? It is unclear, and Presence may start with either Node. To avoid confusion, a well placed Start of Task Node will sort things out:

Task with start node.png

This will now run as follows:

  • Start of Task
  • Read Shipping Note
  • XML Document Writer
  • Send Email
  • Query Stock Information
  • CSV Writer
  • End of Task

See Also

Task Elements > Flow Control Task Elements > Start of Task Node

Schedule Nodes | Decision Point Nodes | Start of Task | End of Task | Error Handler
Throw Exception | Passive Node | Log Entry | Sleep For n Seconds | While Node | Loop Node | Exit Loop Node | |Switch Node
Fork Execution | Join Forked Threads | Start Synch Block | End Synch Block | Event Notification Nodes

Task Elements | Resources