Bug 1006321 - Wrong validation results for Ad-Hoc Subprocess
Summary: Wrong validation results for Ad-Hoc Subprocess
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER5
: 6.0.0
Assignee: Tihomir Surdilovic
QA Contact: Sona Mala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-10 12:38 UTC by Sona Mala
Modified: 2014-08-06 20:07 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:07:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot - process with ad-hoc subprocess (64.42 KB, image/png)
2013-09-10 12:38 UTC, Sona Mala
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.