Re: [rules-users] Preventing re-evaluation on modification of 'output' fact

Have you considered making the reasons for being suspicious objects in their own right and inserting them independently? Let's say: SuspectedFraudReason (abstract parent class) TransactionsTooOften (extends SuspectedFraudReason) TransactionsTooHigh (extends SuspectedFraudReason) then indicate the reasons by inserting a new instance of an object, rather than modifying your results object. If you have rules that depend on other indicators of fraud, then they only get evaluated when that particular class of SuspectedFraudReason is inserted, rather than every time you modify the results object. At the end, you can use a query() to collect all the reasons. -- View this message in context: http://drools.46999.n3.nabble.com/Preventing-re-evaluation-on-modificatio... Sent from the Drools: User forum mailing list archive at Nabble.com.