Error Extension Points
Error extensions allow the customisation of what should happen if an unexpected error occurs during flow processing. They provide a hook into handling the thrown exception, and provide the developer with an option to implement a handling routine.
Error extensions are provided by implementing the 'FlowErrorExtensions' interface, and then supplying that to your domain via the extension provider. Please refer to the add extensions section for more details.
The functionality available on the error extensions interface is:
| MethodName | Description | Default Functionality |
|---|---|---|
shouldRaiseEventOnError |
Specifies whether the flow should raise a special 'Unexpected Error' event when an unexpected error occurs during processing and then use that event to transition to the special 'In Error' state. When a flow reaches the 'In Error' state, it can then be moved on by supplying the resume, abort or force complete functionality available on the model domain. |
Turned off, no events raised. |
handle |
Allows the implementation of any custom flow error handling that you wish to provide. A common use case for this functionality would be if you were integrating your flow with IPF’s Human Task Manager (HTM). For example, if an unexpected error occurs during processing, you can define a custom error handler to transition the flow to the error state and raise a HTM task. From here, the operator would have the ability to retry the transaction or to abort/force complete the transaction. More details on this implementation can be found here. |
No additional handling. |
The default error extensions are provided by the 'DefaultFlowErrorHandler' implementation.