Exception handler scripts are basically Java code, that is invoked if an exception or error occurred during the execution of a process flow. There are three types of Exception handler scripts:

Service exception
Process Flow exception
Invalid data exception

These scripts can be created at the global level (for all the activities in the process flow) or at the activity level (for a specific activity). If an exception or error occurred during the execution of a process flow, the activity level exception handler script is invoked first. If an activity level exception handler script is not created for that activity, then only global level exception handler script is invoked.

These exception handlers scripts are invoked at different stages of the process flow that are defined below.

Exception	Description
Service exception	This exception handler script is invoked when an error related service (activity) occur. For example, File not found, Stream closed, and so on.
Process Flow exception	This exception handler script is invoked when an error occurs at process flow level. The exception can only be declared at the global level. For example, JMX not found, Repository not found, and so on.
Invalid data exception	This exception handler script is invoked when an error related to the processing of data occurs, for example, incorrect record format.

You can create the exception handler script either using the Script or Custom APIs. If you are creating the exception handler using a script then you need to define the Java code. If you are creating the exception handler using custom APIs then first you need to create a class with method(s) and put them in the .../<AdeptiaInstallFolder>/ServerKernel/customClasses/<ClassPackage> folder where <ClassPackage> is the package where you have defined the Java class. For example, if you have defined the Java class in the org.custom package then first create the org/custom folder in the .../<AdeptiaInstallFolder>/ServerKernel/customClasses folder and put the class in the custom folder. Ensure that:

- The class must implement PluginExecutor interface.
```
public class <class_name> implements PluginExecutor
```
- The method should accept only one parameter and that must have an object of ExecutionEvent.
```
public boolean <method_name>(ExecutionEvent event) throws Exception
```
- The method must be public.

Creating Global Exception Handler Script

Follow the steps to create a global exception handler script:

In Web Process Designer, click View Process Flow Properties icon and select EXCEPTION SCRIPTS tab.
Select the required exception handler option, for example, Service.

Select the interpreter type.

Interpreter Type

Description

Script

In this option, you need to define the Java code for the execution of the process flow. Using this option will decrease the execution performance of the process flow.

Custom API

It is recommended to use this option. Using this option will increase the execution performance of the process flow. In this option, you need to select the class and its method for the execution of the process flow. The process flow will be executed on the basis of the code implemented in the selected method.

Click Done.

Creating Activity Exception Handler Script

Follow the steps to create an Activity Exception Handler Script:

In Graph Canvas area, select the activity and click Options from Context pad.
Select Service Exception option form the list to open Service Exception Script window.

On the Service Exception Script window, select the interpreter type.

Interpreter Type	Description
Script	In this option, you need to define the Java code for the execution of the process flow. Using this option will decrease the execution performance of the process flow.
Custom API	It is recommended to use this option. Using this option will increase the execution performance of the process flow. In this option, you need to select the class and its method for the execution of the process flow. The process flow will be executed on the basis of the code implemented in the selected method.

You can use <CTRL>+<Space Bar> to view pre-defined template of Java Code that can be used while creating Java Condition. You can select any of them and edit it according to your requirement.

Click Done.

Handling Invalid Data Exception

Invalid data exception handler script is invoked when an error related to the processing of data occurs, for example, incorrect record format. Connect displays the exception handler on the Option menu of context pad at the activity level.

Select Invalid Data Exception option form the list to open Invalid Data Exception Script window.

On the Invalid Data Exception Script window, select the interpreter type.

Interpreter Type	Description
Script	In this option, you need to define the Java code for the execution of the process flow. Using this option will decrease the execution performance of the process flow.
Custom API	It is recommended to use this option. Using this option will increase the execution performance of the process flow. In this option, you need to select the class and its method for the execution of the process flow. The process flow will be executed on the basis of the code implemented in the selected method.

Click Done.

You may be interested in...

What's new

Best practices

Training guides

Frequently asked questions

Adeptia Connect APIs

Adeptia security report

Browser not supported