Bug 996959

Summary: Guided Decision Table: null operator
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: manstis
Status: CLOSED CURRENTRELEASE QA Contact: Radovan Synek <rsynek>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: lpetrovi
Target Milestone: ER4   
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:15:58 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
null operator none

Description Zuzana Krejčová 2013-08-14 11:16:58 UTC
Created attachment 786505 [details]
null operator

Description of problem:
It is possible to add a condition column without an operator. 

You can either do it the "right" way and select the operator "(no operator)". This makes it look like no operator was chosen yet. Or you can do it the wrong way and not select any operator at all. Either way, if you then click Apply changes, alert pops up saying that "Operator has not been selected". If you accept that, column is added.

The column added the right way is on the right in the screenshot and really has no operator in the table header.
The column added the wrong way is on the left and unfortunately has operator null.


Version-Release number of selected component (if applicable):
kie-wb 6.0 CR1


Expected results:
The wrong way to go about it isn't possible at all or results in the same as the right way.


Additional info:
In the source code, both columns behave the same:
1.	|	//from row number: 1
2.	|	rule "Row 1 gdt"
3.	|	    dialect "mvel"
4.	|	    when
5.	|	        f : Fact( )
6.	|	        f2 : Fact( )
7.	|	    then
8.	|	end

Comment 5 Radovan Synek 2013-10-22 13:55:58 UTC
Verified on BPMS-6.0.0.ER4