Transaction Control Nodes

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

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

Transaction Control Nodes

Transaction Control Nodes provide a mechanism to roll back database transactions following an error or unexpected conditions, or to commit outstanding transactions following successful completion of other criteria.

Typically these will be combined with an Error Handler, as with the example Task below:

Transaction nodes.png

This Task schematic describes how to handle the following situation:

  1. "Update Table 1" succeeds
  2. "Update Table 2" succeeds
  3. "Update Table 3" fails

In this instance we want to rollback the updates performed by "Update Table 1" and "Update Table 2", which is performed by the Rollback Node after catching the error generated by "Update Table 3". Similarly, if "Update Table 2" fails, updates performed by "Update Table 1" will be rolled back. Only if all three SQL statements succeed will the changes be committed.

Note: Commit and Rollback nodes will only take effect if "Commit transactions later in Task" is selected under "Transaction Options" on the SQL Editor.


See Also

Task Elements : Data Accesss Task Elements : Transaction Control Nodes

SQL Statement Nodes | Object Monitor Nodes | XML Query Nodes | Mail Scanner Nodes
Web Services Nodes | LDAP Query Nodes | JSON Node | Flat File Parser | Data Table Nodes | Variable Nodes
Transaction Control Nodes | Context XML Nodes


Task Elements | Resources