Difference between revisions of "Start of Task Node"

From PresenceWiki
Jump to: navigation, search
(Dis-ambiguity)
(No difference)

Revision as of 09:50, 17 October 2012

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.

Dis-ambiguity

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:

http://www.international-presence.com/wikidocs/images/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:

http://www.international-presence.com/wikidocs/images/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 |Switch Node
Fork Execution | Join Forked Threads | Start Synch Block | End Synch Block | Event Notification Nodes



Task Elements | Resources