+++ This bug was initially created as a clone of Bug #1301816 +++

Description of problem:
In GDT, if operation 'is contained in the (comma separated) list' is selected, Editor is not displayed (White page is shown).

Here is example of problematic source DRL.

rule "Row 1 gudedDT1"
dialect "mvel"
when
f1 : Claim( product in ( "EAP" ) )
then
end

//from row number: 2
rule "Row 2 gudedDT1"
dialect "mvel"
when
f1 : Claim( product in ( "BRMS" ) )
then
end

Version-Release number of selected component (if applicable):
6.2.0/6.1.0

How reproducible:

Steps to Reproduce:

1. Create fact: Claim (product: String, solution: String)

2. Create enumeration like the following

'Claim.product' : ['EAP','BRMS']
'Claim.solution' : ['1','2']

3. create new guided decition table by checking 'Use Wizard'

• Option "Use Wizard": checked
• Option "Extended entry, values defined in table body": checked
• Screen "Imports": leave default
• Screen "Add Fact Patterns": choose "Claim"
• Screen "Add Constraints":
• choose "Claim > product"
• column header: "Product"
• operator: "is contained in the (comma separated) list"
• calculation type: "Literal value"
• default value: "Choose..."
• Screen "Add Actions to update Facts":
• choose "Claim > solution"
• column header: "Solution"
• default value: "Choose..."
• Click "Finish"

Actual results:

Editor is not displayed in Editor tab(White page is shown)

Expected results:

Editor is displayed

Additional info:

— Additional comment from JBoss Product and Program Management on 2016-01-25 22:40:19 EST —

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

— Additional comment from Hiroko Miura on 2016-01-25 22:44:53 EST —

I found similar bug but it have been fixed already.

https://bugzilla.redhat.com/show_bug.cgi?id=1076375

Here is comment from customer who reported this issue in attached Case.

This issue is a show-stopper as it may lead to a go/no-go decision for a project since the business users want to be able to use enumeration-based list of values in their decision tables.

— Additional comment from on 2016-01-26 06:43:02 EST —

kie-wb-common
-------------
(master) https://github.com/droolsjbpm/kie-wb-common/pull/210

(6.4.x) https://github.com/droolsjbpm/kie-wb-common/pull/211

— Additional comment from on 2016-01-27 08:32:56 EST —

kie-wb-common
-------------
(master) https://github.com/droolsjbpm/kie-wb-common/commit/de93e3ff0

(6.4.x) https://github.com/droolsjbpm/kie-wb-common/commit/f4e9f1fae

— Additional comment from Radovan Synek on 2016-02-02 07:48:04 EST —

This BZ hasn't been approved nor modified for 6.2.1 patch (fixes are on master and 6.4.x branches only).

— Additional comment from Alessandro Lazarotti on 2016-02-02 13:46:57 EST —

This is not a cumulative patch BZ so no roll up flag is supposed to be added here, I will remove it and keep only the 6.3.0.

Hiroko, if customer would like to see it fixed before 6.3.0 you must:

1) Clone it
2) Add to cloned BZ as subject prefix:
[GSS](6.2.z) GDT: Editor is ...
3) Add to cloned BZ the flag
brms-rollup-2-6.2.x

Never add more than one roll up flag. As 6.2.1 is almost released you should add only the brms-rollup-2-6.2.x.