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

[GSS] (6.4.z) 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

Details

    • Bug
    • Resolution: Done
    • Major
    • 6.4.10
    • 6.4.1.GA
    • Business Central
    • None

    Description

      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" ) )

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. RHBRMS-2752 Unexpected results in GDST when using enumerations with commas

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-2263 Unexpected results in GDST when using enumerations with commas

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. RHBRMS-2752 Unexpected results in GDST when using enumerations with commas

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. RHDM-493 Complex enumerations are not selected when multivalue cell is edited

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-551 Complex enumerations are not selected when multivalue cell is edited

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. RHDM-25 Use of "contains" operator does not add values from enumeration with quotes in Guided Rules etc.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved:
                Archived:

                PagerDuty