The following Java Action Sets can be distinguished:
Init Actions and Process Owner Actions are executed upon process initialization. These Java Actions initialize User Defined Attribute data before the first activity is performed.
Commit Actions are executed upon process completion. They can be used to clean up or analyze the data of an entire process instance.
A Prologue Action is evaluated before an activity starts. This Java Action can therefore be used to set up or initialize values associated with a specific node before it does its work.
An Epilogue Action is executed after a node finishes its task and before the process instance moves on to another node. This Java Action can therefore be used to clean up or analyze values associated with the node after the intended work is finished.
A Role Action is evaluated after resolving a role and before assigning a task. This Java Action is therefore used to dynamically compute a list of assignees for a task in conjunction with a Role.
Timer Actions are executed when a timer expires or a due date is reached.
An Error Action can be used for handling specific error situations in the execution of a process. Error Actions can be defined for entire process definitions, for individual nodes and for other Java Actions, i.e. when you want to react on errors occurring during the execution of another Java Action.
A Compensation Action can be defined for another Java Action that accesses a system outside of Systemwalker Runbook Automation, e.g. an external database. Compensation Actions are useful to ensure a consistent state of all systems involved in a transaction for cleaning up and rolling back transactions, e.g. to delete a newly added row in an external database.
A special type of action can be activated as soon as an Administrator issues the command to abort, suspend or resume the processing of a process instance. Such actions are stored in either of the following Action Sets:
onAbort Action
onResume Action
onSuspend Action
These Java Actions are to be performed before the state of a process instance is changed. They can be defined for individual activities, i.e. for individual nodes in a process definition, or for an entire process definition.
