Orchestration activities throw exceptions whenever exceptional or abnormal conditions occur. A Catch activity can be added to the Exception Handlers node of the event handler to provide the actions that should be taken for the identified exception.
ClearPath ePortal Exceptions
UserException
ArithmeticException
AssignMessageException
ConnectFailedException
ConnectorException
NullReferenceException
ReceiveTimeoutException
InputDataOverflowException
InvalidCastException
InvalidFormatException
OutOfRangeException
UnorchestratedMessageException
MessageFormatException
UnrecognizedMessageException
Refer to Orchestration Exceptions for a complete list of exceptions.
Refer to Orchestration Toolbox Selections for information about what exceptions are thrown by activity.
Handling Exceptions in an Event Handler
A Catch activity can be for a specific exception, such as ReceiveTimeoutException, or for all exceptions that might be thrown by using the Exception exception.
Drag the Catch activity from the Toolbox to the Exception Handlers node of the appropriate event handler.
In the Properties window, select an exception from the ExceptionName list.
If the exception can have multiple exception codes or multiple sub codes, or both, do the following to determine the exact exception that was thrown:
Drag an appropriate Structured Activity under the Catch activity.
In the Properties window, select the Condition property.
In the Edit Condition dialog box, describe that condition to be met.
Add the activities appropriate for handling the exception under the Catch activity.
Creating Custom Exceptions
Throwing an Exception Using Pre-defined Exceptions
A Throw activity can be created if an exception must be thrown that is not thrown by an activity.
Drag the Throw activity from the Toolbox to the Start node of the appropriate event handler.
In the Properties window, do the following:
Select the pre-defined exception from the ExceptionName list.
Set the Message, ExceptionCode, and ExceptionSubCode properties to appropriate values.
The Catch activity can investigate these properties.
Throwing a Custom Exception
If the exceptions thrown by orchestration activities are not sufficient, a custom exception can be created.
Drag the Throw activity from the Toolbox to the Start node of the appropriate event handler.
In the Properties window, do the following:
Select UserException from the ExceptionName list.
Set the Message, ExceptionCode, and ExceptionSubCode properties to values for the orchestration.
The Catch activity can investigate these properties.