Top
Systemwalker Runbook Automation Studio User's Guide
Systemwalker

11.8.2 Using OnSuspend, OnResume, and OnAbort Actions

OnSuspend, OnResume, and OnAbort Actions (On*Actions) are executed just before a process instance changes its state due to the fact that an administrator has issued the command to suspend, resume or abort the execution of a process instance.

Note

On*Actions are not related to exceptions or error cases. They are regular Java Actions that are executed when the command for a state transition has been invoked. Apart from this special use, they are treated like regular Java Actions.

On* Actions can be defined for individual activities (for example individual nodes) or for process definitions. Assume you define, for example, an OnSuspend Java Action both for a node and for a process definition. If this node is active when an Administrator issues the command to suspend the process instance, the Java Actions are executed in the following order:

  1. The OnSuspend Java Action of the Node is executed.

  2. The OnSuspend Java Action of the process definition is executed.

Similar to all other Java Actions, On* Action Sets can contain a number of other Java Actions.

To define On* Actions:

  1. Click the empty space in the Process Definition editor or select the node to which you want to assign the Java Action, to display the Properties view for the process definition or the node respectively.

  2. In the Properties view, select the Exception Handling tab.

    The Exception Handling dialog is displayed. If you have not defined any On* Actions before, an empty folder is displayed for each of the three actions, for example:

    Figure 11.38 Displaying On* Actions

  3. Select the tab for the On* Action you want to create, and click Add.

    The Action Type List dialog is displayed.

  4. Proceed with defining a Java Action as an Error Action. Refer to section 11.1 Using Java Actions for details.

  5. Click OK.