Re: [rules-users] Rule is firing on those objects for which that hasalready fired

Thanks for the reply. This really helped me to think a bit more. the "exists" statement is described which has almost the functionality which you want. inside the "exists" body. In my scenario, I need to know what are the data points that have violated the rule condition. So, "exists" will not help here. in which objects trigger the rule. If so, I can imagine, that you don't want to know only one portion of your rule is correct. Yes, you are right... the behavior of the rule is correct. What I missed was, I need to include a condition more ...so that rule only considers those data points which has been inserted after last successful rule execution [i.e after those data points which caused the rule to get violated last time]. if you can safely assume that they "have done their work". I.e. if you know, that these objects should needs these objects, retract them in the rhs of your rule. I can not do this as, there are couple of rules in same RuleBase who may need those data points. "processed" by the rule, e.g with your ruleID, and to test everytime in the lhs if the object of interest is not Yes, this will solve the problem. Rule will only consider those objects which have not participated in the rule violation. In my scenario, All data points inserted in Working Memory have timestamp associated with those. Rule need not consider all data points which have not participated in the rule violation (i.e not marked as processed) each time I call fireAllRules(). Only datapoints inserted after last rule violation need to be considered. I can think of another solution: For every rule I can maintain a object which will contain the time stamp value of last data points that have violated that rule. So in next executions rule will only consider those objects which have greater timestamp values then the last violated data point. As sample, rule "sample_rule" when $p4: DataObject(id == 4, stringValue == "230007014", $newTime4 : timeStamp) and ( not ProcessedObject(rule== "sample_rule") or ( $po4: ProcessedObject(rule== "sample_rule") and eval ( $newTime4.after( $po4.getLatestTimestamp(4) ) ) ) ) and $p14: DataObject(id == 14, stringValue == "230007004", $newTime14 : timeStamp) and (not ProcessedObject(rule== "sample_rule") or ( $po14: ProcessedObject(rule== "sample_rule") and eval ( $newTime14.after( $po14.getLatestTimestamp(14) ) ) ) ) and $p10: DataObject(id == 10, stringValue == "230007005", $newTime10 : timeStamp) and (not ProcessedObject(rule== "sample_rule") or ( $po10: ProcessedObject(rule== "sample_rule") and eval ( $newTime10.after( $po14.getLatestTimestamp(10) ) ) ) ) then String ruleID = "sample_rule"; RuleOutput ruleOutput = RuleEngineHelper.getRuleOutput(ruleSetOutput, ruleID); ruleOutput.addDataObject($p4); ruleOutput.addDataObject($p14); ruleOutput.addDataObject($p10); ProcessedObject po = ruleOutput.getProcessedObject(); insert(po); end [ Here ProcessedObject will have the timestamp of last data points that has violated that rule. There will be another rule which will ensure per rule only one ProcessedObject exists in Working Memory. Not sure if I can avoid the 2nd Rule. Please provide your suggestions] Do you see any problem with this solution ? Any opportunity to further tune the rule mentioned above ? Feedback/Suggestions are welcome. Regards Siddhartha Alexander Claus wrote: -- View this message in context: http://www.nabble.com/Re%3A-Rule-is-firing-on-those-objects-for-which-tha... Sent from the drools - user mailing list archive at Nabble.com.