-
Bug
-
Resolution: Done
-
Major
-
6.4.1.GA
-
None
When using enumerations where the values itself contain a comma, the rules generated by a GDST are unexpected, as the "contains in" operator splits those values in the enumerations. Example enumeration:
fact: person field: city context: ['paris','london','new york,boston']
Note: see the 'new york, boston' sample.
The code generated will be:
rule "Row 1 personGDT" dialect "mvel" when p : person( city in ( "new york", "boston" ) ) then end
Basically "paris" and "new york,boston" will be treated by the DSL parser as 3 strings in the DRL generation and will produce someting simiular to
p : person( city in ( "paris", "new york", "boston" ) )
But what the customer expects is the following
p : person( city in ( "paris", "new york,boston" ) )
- clones
-
RHBRMS-2752 Unexpected results in GDST when using enumerations with commas
- Closed
- is cloned by
-
DROOLS-2263 Unexpected results in GDST when using enumerations with commas
- Closed
- is duplicated by
-
RHBRMS-2752 Unexpected results in GDST when using enumerations with commas
- Closed
- is related to
-
RHDM-493 Complex enumerations are not selected when multivalue cell is edited
- Closed
-
RHPAM-551 Complex enumerations are not selected when multivalue cell is edited
- Closed
- relates to
-
RHDM-25 Use of "contains" operator does not add values from enumeration with quotes in Guided Rules etc.
- Closed