With Systemwalker Runbook Automation Studio, you can define exception handling behavior as follows:
Error Actions can be used to handle specific errors and to determine the behavior of a process instance in case an error occurs. If you do not define any error handling, a process instance will go into error state as soon as an exception is thrown, irrespective of when the error occurs, for example the sending of an email was unsuccessful.
Error Actions can be defined on different levels:
On Process Definition level:
These Error Actions are executed in case of any error, independent of the activity in which an error occurs and independent of the severity of an error. Error Action Sets defined on process definition level will be executed immediately before the process instance will go into error state. Note that such Error Actions cannot influence the behavior of the process instance. Error Actions on process definition level may, for example, be used for sending a notification email or for writing additional information into a log file. Refer to section 11.8.1 Using Error Actions on Process Definition Level for details.
On Java Action level:
An Error Action Set on this level is executed when an error occurs during the execution of a "regular" Java Action. Error Actions can be defined for all types of Java Actions, except for an Error or Compensation Action. Assigning Error Actions to Java Actions is described in section 11.1.7 Dealing With Errors in Java Actions.
OnSuspend, OnResume, and OnAbort Actions (On*Actions) can be used to deal with the situations when an Administrator suspends, resumes or aborts the execution of a process instance. For example, you can use these Actions to send a notification email. Refer to section 11.8.2 Using OnSuspend, OnResume, and OnAbort Actions for details.
