Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 852114

Summary: Boundary Events on Reusable Subprocess not possible in jBPM Designer
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Tihomir Surdilovic <tsurdilo>
Component: jBPM 5Assignee: Kris Verlaenen <kverlaen>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.1CC: kverlaen
Target Milestone: ER4   
Target Release: BRMS 5.3.1 GA   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When setting boundary events on reusable subprocesses in the process designer caused a validation occurred stating that there was no incoming connections. In JBoss Enterprise BRMS 5.3.1, it is no longer possible to set boundary events on reusable subprocesses.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:20:39 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
Repository with process none

Description Tihomir Surdilovic 2012-08-27 16:12:59 UTC 
Try to put a Boundary Event on a Reusable SubProcess directly and with this web designer version 2.2 Final it don't think it is possible.
A way to get around this issue :
You must first put the Boundary Event on a Basic Task first and then Morph the Basic Task to a Reusable Subprocess so that it works.
Comment 1 Sona Mala 2012-10-01 08:09:24 UTC 
For BRMS 5.3.1 ER1 and designer 2.3.1-DEV:
 - I can add Catching Intermediate Event to Reusable SubProcess as Boundary Event
   (drag event and drop it into subprocess when green rectangle appears in subprocess)
 - Problems are:
    - Validate that process.
      -> Error: node has not incomming connection
    - Build a package of process:
      -> Error: unable to parse xml : Exception class java.lang.ClassCastException : org.jbpm.workflow.core.node.SubProcessNode cannot be cast to org.jbpm.workflow.core.node.CompositeContextNode

Repository is attached.
Comment 2 Sona Mala 2012-10-01 08:12:10 UTC 
Created attachment 619647 [details]
Repository with process
Comment 3 Sona Mala 2012-10-01 08:13:20 UTC 
Same problems (validation and build package) are for Basic Task.
Comment 4 Tihomir Surdilovic 2012-10-02 20:48:34 UTC 
This is fixed in the community already. Since there is no blocker flag for 5.3.1 I have not moved the fix to the prod branch yet. Please add blocker flag if this is a blocker for 5.3.1.

Thanks.
Comment 5 Lukáš Petrovický 2012-10-17 08:18:26 UTC 
Setting to "future" and MODIFIED, so that we pick it up in later versions.
Comment 6 Lukáš Petrovický 2012-10-18 13:18:35 UTC 
*** Bug 864794 has been marked as a duplicate of this bug. ***
Comment 7 Lukáš Petrovický 2012-10-18 13:20:10 UTC 
(In reply to comment #5)
> Setting to "future" and MODIFIED, so that we pick it up in later versions.

My bad, I had missed the fact that this issue is an approved blocker. Feel free to commit, of course.
Comment 8 Tihomir Surdilovic 2012-10-18 14:56:57 UTC 
Fix committed to 2.3.x Designer branch.

Boundary events on Reusable subprocesses (call activities) is _not_ supported in BRMS 5.3.1. Support for this is available in the community only and should be available in the next BRMS version. 

Fixes include:

1) No longer able to set boundary events on Reusable Subprocess
2) Visual validation should no longer report missing incoming connection errors on boundary events.

Let me know if there is anything else.
Comment 9 Zuzana Krejčová 2012-11-15 13:37:42 UTC 
What works: 
- boundary events can no longer be added to reusable sub-process nodes directly. 
- missing incoming connection errors are fixed. If the event is connected as a boundary event to an activity, this validation error does not occur.

But:
The workaround mentioned in comment 1 can still be used though. Boundary events can be added to the so called basic task, the problem is they cause the same problems as the reusable sub-process. Building a package with process that contains such nodes results in the above mentioned ClassCastException.
If it were a quick fix, it might have been a good idea to remove the support for boundary events on these basic tasks as well.

The fix for the validation issue is definitely nice to have. But as it is now, I propose to revisit this again in a future release with the rest of the boundary events issues. It still needs more work and we simply don't have time for it now. This bug probably should not have been proposed for 5.3.1 anyway, considering the original description.

I'm resetting the 5.3.1 and blocker flag to reflect this.
Comment 16 Red Hat Bugzilla 2025-02-10 03:20:39 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.