Bug 1007245 - jBPM Designer allows to set condition expression on sequence flow going out from parallel gateway
jBPM Designer allows to set condition expression on sequence flow going out f...
Status: ASSIGNED
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: jBPM Designer (Show other bugs)
6.0.0
Unspecified Unspecified
low Severity medium
: ---
: ---
Assigned To: Tihomir Surdilovic
Radovan Synek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-12 04:05 EDT by Radovan Synek
Modified: 2016-01-08 16:49 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Radovan Synek 2013-09-12 04:05:06 EDT
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.

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