Exception Handler
The exception handler node catches checked exceptions. It starts a new embedded subflow with an input variable that contains details of the exception that was thrown somewhere in the main flow. One such handler is defined per exception type, which allows to handle all related error states correctly and in one centralized place.
One flow can contains multiple exception handlers. If flow has more then one handler then the handler that handles raised exception type will be called.
Example:
Exception A extends B, which extends pdk.ex.Exception.
Exception C extends pdk.ex.Exception.
The flow has 3 handlers for different types of exceptions.
A. handle A exception
B. handle B exception
E. handle pdk.ex.Exception
Cases:
1. Exception A was raised - handler A was executed.
2. Exception C was raised - handler E was executed (there is no handler for the
C structure, but C extends pdk.ex.Exception, which can be handled by E).
Properties
Common Properties
Name - refers to the unique identifier or label assigned to a node within a flow.
input Text
must consist of letters (A-Z or a-z), digits (0-9), underscores (_), or dollar signs ($). However, a class name cannot start with a digit and dollar sign ($)
Unique per flow
Mandatory
Min length: 1
Max length: 255
Description - provides a textual description or additional information about a node within a flow. Unlike the name property, which serves as a unique identifier or label for the node, the description property offers supplementary details that help to clarify the purpose, functionality, or behavior of the node.
Input Text
Max length: 5000
Exception Handler-Specific Properties
Multiple conditions are allowed to be added.
Each condition contains two settings:
Exception - exception type or its children to be handled.
Mandatory
Result
A new variable with the exception type defined as an input parameter.
Connections
This node has no incoming and one outgoing connection
in
0
0
out
1
1
Last updated