Red Hat Bugzilla – Bug 804989
Designer doesn't allow sequence flow from boundary compensation event
Last modified: 2012-11-09 00:14:38 EST
Created attachment 571366 [details] Screenshot of the sample process Description of problem: Only association is allowed as an edge going from boundary compensation event. According to BPMN 2.0 specification it should be possible to drag a sequence flow from such event node. Version-Release number of selected component (if applicable): BRMS-5.3.0-ER4 How reproducible: Every time Steps to Reproduce: 1. add an activity to the pane 2. add boundary throw compensation event 3. drag the activity from menu to the right of the node Actual results: activity is connected using 'association flow' Expected results: activity is connected using 'sequence flow' Additional info: other (supported) boundary events allow sequence flow correctly
I think this is the case for the throwing event which cannot be a boundary event. For catching event only a compensation associations are possible (see screenshot).
Created attachment 572785 [details] from bpmn2 docs
Then make it work. If you create such process, it can't be saved nor BPMN2 can be viewed. And if you handwrite it, the jbpm engine does not compile such a jbpm. However if you substitute it wit sequence flow, it works like a charm (not in designer, in jbpm engine)
After talking to Kris about this, we decided to remove the intermediate compensation events from the Designer stencil set until the runtime has proper support for them. At that point we can revisit and fix any outstanding bugs. This has been committed to designer master and the 2.1.x branch.
Update status to ON_QA. Please verify them against ER6.
The possibility of intermediate catch events is disabled, but we want it fixed in the future. Therefore marking it ASSIGNED and removing target milestone.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The jBPM runtime, and by extension the process designer, do not support sequence flow from boundary compensation events.