Bug 1007245 - jBPM Designer allows to set condition expression on sequence flow going out from parallel gateway
Summary: jBPM Designer allows to set condition expression on sequence flow going out f...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-12 08:05 UTC by Radovan Synek
Modified: 2020-03-27 19:11 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:11:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.