We would like to model a generic error handling for BPMN errors. Each of our tasks can throw BPMN error with different error code and error message. Then we would like to have generic boundary error event, which catches all BPMN errors (without filled errorCode).
Our boundary event successfully catches all error code. Unfortunately we haven’t found a way how to access the BPMN error context in error handling.
How can we get the error code and error message that we caught in error handling? We try to avoid having numerous specific boundary error events, so we can keep the error handling generic.
No this is not implemented yet.
The workaround for now would be to override the default error boundary event behaviour class. If it’s needed by more users then we can definitely raise the priority of this. It would already help to create a Github issue so we can discuss it a bit more and track progress.
Just for my own understanding, do you think it is tricky the implementation which enables the error context to pass through the boundary event or is there another motivation to avoid the bpmn error propagation?
I am more than interested to see this feature implemented. It would really make error handling a lot easier.
So, I’m wondering if I can create a github issue and offer my contribution by implementing it as @joram proposed?