Bug 1006321

Summary: Wrong validation results for Ad-Hoc Subprocess
Product: [Retired] JBoss BPMS Platform 6 Reporter: Sona Mala <smala>
Component: jBPM DesignerAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED CURRENTRELEASE QA Contact: Sona Mala <smala>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: kverlaen
Target Milestone: ER5   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:07:27 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 - process with ad-hoc subprocess none

Description Sona Mala 2013-09-10 12:38:54 UTC
Created attachment 795986 [details]
Screenshot - process with ad-hoc subprocess

Description of problem:
Validation for Ad-Hoc Subprocess failed if subprocess contains separated tasks which are not connected by sequence flow.

Look at the attached screenshot.


Version-Release number of selected component (if applicable):
6.0.0 BPMS ER2


Steps to Reproduce:
1. Create a new process
2. Start -> AdHoc -> End
3. Add tasks into AdHoc subprocess
4. validate

Actual results:
See the attached screenshot.
Validation shows issues - "Node has no outgoing/incomming connections".

Expected results:
This process should be valid. No issue for inner tasks.

Additional info:
Look at BPMN Specification - Figure 10.36, page 181

Comment 1 Tihomir Surdilovic 2013-09-30 16:16:53 UTC
fixed for ad-hoc processes too. fix in master and 6.0.x designer branches.

Comment 2 Marek Baluch 2013-11-27 10:12:10 UTC
Verified on ER5.