Bug 804989

Summary: Designer doesn't allow sequence flow from boundary compensation event
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Tomas Schlosser <tschloss>
Component: jBPM 5Assignee: Kris Verlaenen <kverlaen>
Status: CLOSED UPSTREAM QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.0.GA   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The jBPM runtime, and by extension the Process Designer, do not support sequence flow from boundary compensation events.
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:19:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of the sample process
none
from bpmn2 docs none

Description Tomas Schlosser 2012-03-20 11:46:18 UTC
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

Comment 1 Tihomir Surdilovic 2012-03-26 15:53:07 UTC
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).

Comment 2 Tihomir Surdilovic 2012-03-26 15:53:51 UTC
Created attachment 572785 [details]
from bpmn2 docs

Comment 3 Tomas Schlosser 2012-03-28 06:17:15 UTC
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)

Comment 4 Tihomir Surdilovic 2012-03-28 12:46:27 UTC
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.

Comment 5 Ryan Zhang 2012-04-23 07:40:16 UTC
Update status to ON_QA. Please verify them against ER6.

Comment 7 Tomas Schlosser 2012-05-02 14:31:53 UTC
The possibility of intermediate catch events is disabled, but we want it fixed in the future. Therefore marking it ASSIGNED and removing target milestone.

Comment 8 lcarlon 2012-06-13 02:26:37 UTC
    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.

Comment 16 Red Hat Bugzilla 2025-02-10 03:19:21 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.