Bug 1007245

Summary:	jBPM Designer allows to set condition expression on sequence flow going out from parallel gateway
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Radovan Synek <rsynek>
Component:	jBPM Designer	Assignee:	Tihomir Surdilovic <tsurdilo>
Status:	CLOSED EOL	QA Contact:	Radovan Synek <rsynek>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0.0	CC:	kverlaen, lpetrovi
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 19:11:12 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:

Description Radovan Synek 2013-09-12 08:05:06 UTC

Description of problem:
Parallel gateway (split) should pass token all outgoing connections without any condition evaluation (BPMN2 spec). But designer allows to set conditions on these connections - which is wrong, conditions do make sense only on connections going out from inclusive/exclusive/complex gateway. 

Multiple connections from activity should behave as parallel gateway - so again, user shouldn't be able to place any conditions on them. As I am thinking about it, even single connection going out from activity shouldn't have any condition - engine has to ignore it.

Disabling properties "Condition Expression" and "Condition Expression Language" in cases stated above would be for the best.