Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-4360

Salience assignment behaviour is different when SequentialMaxPriority is set

    Details

    • Sprint:
      2019 Week 29-31
    • Story Points:
      2
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mfusco Mario Fusco
                  Reporter:
                  mfusco Mario Fusco
                  Tester:
                  Tibor Zimanyi
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: