[
https://issues.jboss.org/browse/DROOLS-1225?page=com.atlassian.jira.plugi...
]
Osamu Kuniyasu commented on DROOLS-1225:
----------------------------------------
Unexpected DRL generation from a Decision Table Excel file was realized.
When we have multiple RuleTable(s) in one Excel Sheet (means one RuleSet),
Each RuleTable starts from salience={SequentialMaxPriority}.
With this, the order of rule firing is jumping between RuleTable(s) in same Excel Sheet.
Can we have rules' saliences counting down from the top to the bottom in same Excel
Sheet even it has multiple RuleTable(s)?
Add options to specify the salience range of rules in a Decision
Table Sheet
----------------------------------------------------------------------------
Key: DROOLS-1225
URL:
https://issues.jboss.org/browse/DROOLS-1225
Project: Drools
Issue Type: Feature Request
Components: decision tables
Affects Versions: 6.4.0.Final
Environment: any
Reporter: Osamu Kuniyasu
Assignee: Mario Fusco
Priority: Major
Fix For: 7.0.0.Final
When we set Sequential=true in RuleSet properties.
The salience of the generated rules are started from 65518 and down one by one.
When we mix several Decision Table Sheets and DRL rules in a Ruleflow-Group
(Agenda-Group), We could not make these rules' salience order, because each Decision
Table Sheet has fixed to start from 65518.
A (limited) workaround is to have separated Ruleflow-Groups,
But this way does not solve the situation to back to the higher priority rules as
it's previous Ruleflow-Group.
To solve The request is that add two options into RuleSet properties. like,
SequentialMaxPriority 10000
SequentialMinPriority 1000
By this optional properties, we can control the range of the salience of rules in the
Decision Table Sheet. and it is possible safely to mix multiple Decision Table Sheets in a
Ruleflow-Group.
The SequentialMaxPriority is used to set the start value of the salience instead of
65518.
The SequentialMinPriority is used to check if this minimum salience value is not violated
in the Decision Table Compiler. (if it's violated, compilation error occurs.)
Best Regards,
Osamu Kuniyasu
--
This message was sent by Atlassian Jira
(v7.12.1#712002)