Uploaded image for project: 'Red Hat Decision Manager'
  1. Red Hat Decision Manager
  2. RHDM-1781

Editing data object guided decision table fails

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.12.0.GA
    • 7.10.0.GA
    • None
    • None
      • RHPAM 7.10
    • False
    • False
    • Release Notes
    • ER1
    • +
    • Undefined
    • Workaround Exists
    • Hide

      Undeploy/deploy project makes it work as expected

      Show
      Undeploy/deploy project makes it work as expected
    • Hide
      • Import the "productList" project via unzipped 02983362-reproducer
      • Deploy to kie-server
      • Execute send-request.sh (changed only user/password)
        -> returns the correct response
      • Go to "Data Object" editor for "productList"
      • Remove "orders" field
      • Press "Save"
      • Deploy to kie-server
      • Execute send-request.sh again
        -> returns the correct response
      • Add "orders" field as String[List]
      • Press "Save"
      • Deploy to kie-server
      • Execute send-request.sh again
        -> returns the score = null response (It means that rules are not fired)
      Show
      Import the "productList" project via unzipped 02983362-reproducer Deploy to kie-server Execute send-request.sh (changed only user/password) -> returns the correct response Go to "Data Object" editor for "productList" Remove "orders" field Press "Save" Deploy to kie-server Execute send-request.sh again -> returns the correct response Add "orders" field as String [List] Press "Save" Deploy to kie-server Execute send-request.sh again -> returns the score = null response (It means that rules are not fired)
    • 2021 Week 28-30 (from Jul 12)

    Description

      After several editions of data objects, rules in gdst are not triggered.

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-6492 2nd incremental update causes misfiring of a rule with 'from'

          • 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

              rhn-support-tkobayas Toshiya Kobayashi
              afanjula@redhat.com Alberto Fanjul Alonso
              Paolo Bizzarri Paolo Bizzarri
              Paolo Bizzarri Paolo Bizzarri
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: