Uploaded image for project: 'JBoss BRMS Platform'
  1. JBoss BRMS Platform
  2. RHBRMS-2752

Unexpected results in GDST when using enumerations with commas

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 6.4.1.GA
    • Business Central
    • 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" ) )

        1. 1-DataObject.png
          1-DataObject.png
          31 kB
        2. 2-Enumeration.png
          2-Enumeration.png
          21 kB
        3. 3-GDST-column.png
          3-GDST-column.png
          70 kB
        4. 4-GDST-dropdownsOK.png
          4-GDST-dropdownsOK.png
          36 kB
        5. 5-GDST-sourceNOT_OK.png
          5-GDST-sourceNOT_OK.png
          32 kB

            trikkola Toni Rikkola
            rhn-support-mputz Martin Weiler (Inactive)
            Archiver:
            rhn-support-ceverson Clark Everson
            Jozef Marko Jozef Marko (Inactive)
            Jozef Marko Jozef Marko (Inactive)

              Created:
              Updated:
              Resolved:
              Archived: