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

Salience assignment behaviour is different when SequentialMaxPriority is set

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.5.0.GA
    • None
    • BRE
    • 2
    • CR1
    • -
    • 2019 Week 29-31

    Description

      In Spreadsheet decision tables, RuleSet property SequentialMaxPriority and SequentialMinPriority are for controlling the salience number range of Rules generated from Decision Tables.

      https://access.redhat.com/documentation/en-us/red_hat_decision_manager/7.4/html/designing_a_decision_service_using_spreadsheet_decision_tables/decision-tables-defining-proc#decision-tables-rule-set-entries-ref

      By setting Sequential=true without SequentialMaxPriority and SequentialMinPriority, the salience starts with 65535 and it's decremented one by one through all rules across multiple RuleTables.

      On the other hand, by setting Sequential=true WITH SequentialMaxPriority,
      every RuleTables starts with value specified by SequentialMaxPriority as salience.
      i.e. first rule of each RuleTebles has same salience if there are multiple RuleTables.

      In other words, when SequentialMaxPriority is set, start value of salience is reset per RuleTables, but this is unexpected.

      Attachments

        Issue Links

          Activity

            People

              mfusco@redhat.com Mario Fusco
              rhn-support-hmiura Hiroko Miura
              Daniel Rosa Daniel Rosa
              Daniel Rosa Daniel Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: