]
Michael Anstis moved GUVNOR-2855 to DROOLS-1824:
------------------------------------------------
Project: Drools (was: Guvnor)
Key: DROOLS-1824 (was: GUVNOR-2855)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Component/s: Guided Decision Table Editor
(was: Guided Decision Table)
Guided Decision Table V&V - Make the V&V pick up salience
& activation-group
----------------------------------------------------------------------------
Key: DROOLS-1824
URL:
https://issues.jboss.org/browse/DROOLS-1824
Project: Drools
Issue Type: Enhancement
Components: Guided Decision Table Editor
Reporter: Toni Rikkola
Assignee: Toni Rikkola
Either the one set in the table or the ones added with code generation based on Hit
Policy.
Made the ticket, but not sure if salience changes anything with what we resolve at the
moment. It does affect loop detection, but we do not handle that at the moment
* If two rules are subsumptant. The order of the rows does not matter, they are still
subsumptant
* If two rules are in conflict. The order does not matter.
Saliance with activation-group however does change things.
* If a rule's LHS with a higher priority subsumes a rule with a lower priority. The
lower row never fires.
* We do not care about conflicting rows in activation-group
Due to PHREAK, we always have top to down salience or a salience set by the user.