[jboss-jira] [JBoss JIRA] (DROOLS-4361) Salience assignment behaviour is different when SequentialMaxPriority is set

Hiroko Miura (Jira) issues at jboss.org
Wed Jul 24 05:08:00 EDT 2019


Hiroko Miura created DROOLS-4361:
------------------------------------

             Summary: Salience assignment behaviour is different when SequentialMaxPriority is set
                 Key: DROOLS-4361
                 URL: https://issues.jboss.org/browse/DROOLS-4361
             Project: Drools
          Issue Type: Bug
          Components: decision tables
            Reporter: Hiroko Miura
            Assignee: Mario Fusco


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.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jboss-jira mailing list