flowable-engine
flowable-engine copied to clipboard
Boundary Error Event properties import issue
Issue: After bpmn diagram import to modeler UI Boundary Error Event properties are dropped
Cause: Json converter implemented in that way so that if error code is not set, then all properties are ignored
Details: Modeler export works fine and exports all properties regardless if error code is set or not. Workflow application works in the same way and regardless if error code is set or not, it uses all set properties. Issue occurs only on diagram import to modeler UI. There are two scenarios how to use boundary error event based on BpmnError code:
- Add error code for boundary error event and flowable based on that will do navigation. For that solution multiple boundary error events are needed and this makes diagram hard to read. Negative side - all possible error codes need to have boundary event added
- Do not add boundary error event error code, but store BpmnError error code as variable and based on that design decisions using gateways.
Solution:
Json converted updated to match export and flowable behavior
Unit tests: NA Documentation: NA