Java Actions are assigned to so-called Action Sets. Action Sets are associated with particular points of time within process execution:
Init Actions: When the process instance starts
Process Instance Owner Actions: When a process instance starts
Role Actions: When Systemwalker Runbook Automation determines who to assign the activity to
Prologue Actions: Before an activity is activated
Timer Actions: When a timer expires or a due date is reached
Epilogue Actions: When an activity is completed
Commit Actions: When the process instance ends
OnSuspend Actions: When a process instance is suspended
OnResume Actions: When a process instance is resumed
OnAbort Actions: When a process instance is aborted
Error Actions: When a Java Action throws an exception.
Compensation Actions: When an error occurs in a Java Action that accesses an external system.
As a default, each Action Set runs as a single transaction. If any action in the set fails, the database transaction for the entire set is rolled back. However, if Java Actions access resources that are not guarded by the transaction, such as an email server, then those effects cannot be rolled back.
To change transaction settings:
Select the node to display the Properties view for the node. The General tab contains the Commit Transaction after completion check box
If the Action Sets of the node are not to run as a single transaction, clear the Commit Transaction after completion check box.
Note
If you wish to make Java Actions run in separate transactions, simply move them to different sets in different nodes. Ensure that the Commit Transaction after completion check box is selected for that node.
