Re: [rules-users] can drools support complex rules (resetting of Accumulate?)

Hi, Temporal Reasoning with Accumulate - (like 3- rule "Customer login from more than 5 locations in the last one month") What if I want to reset my count for accumulate within the time specified sliding window.So that I can have the RHS triggered for every 10times the event occurs in the same window. For Example: when $customer : Customer( $id : id ) Number( intValue > 10 ) from accumulate( CustomerLogin( loginStatus=="Failed", customerId == $id,$cusId:customerId) over window:time( 30s ), count( $ cusId) ) then // do something as the customer had abnormal number of failed violations in last 30 secs. end Right now am doing something similar, but using a manual approach -of explicitly counting. Any Light on this? Regards Rishi ---------------------------------------------------------------------- Message: 1 Date: Tue, 19 May 2009 11:17:41 -0400 From: Edson Tirelli <tirelli(a)post.com&gt; Subject: Re: [rules-users] can drools support complex rules To: Rules Users List <rules-users(a)lists.jboss.org&gt; Message-ID: <e6dd5ba30905190817q33d15b9er5efee64bc74cdb0e(a)mail.gmail.com&gt; Content-Type: text/plain; charset="windows-1252" Your question is funny. First you ask if Drools is capable of managing complex rules and then you mention examples of extremely simple rules? :) Drools is FOL complete and so can represent any well formed First Order Logic expression. Anyway, I will use this message to advertise some of the temporal reasoning features that we have on Drools 5 for the benefit of anyone interested. There are several ways of authoring such rules, depending on how you model your problem domain. One possible way of doing them is: #1: rule "If a customer login within 5 minutes from two different locations, mark the user invalid." when $l1 : CustomerLogin( ) $l2 : CustomerLogin( userId == l1.$id, location != $l1.id, timestamp after[0s, 5m] $l1.timestamp ) then // mark user as invalid end In the previous example I assumed both login objects would be in working memory, but you can easily query for the previous login in an external datasource, pulling the data from the previous login on-demand for the reasoning cycle. #2: rule "If the customer location is not on a list of valid locations, mark the user invalid" when $l : CustomerLogin( location not memberOf $validLocations ) then // mark the user invalid end In the above rule, I assume the valid locations list is a global list, but you can as easily model locations as being facts on your working memory or a service end point that you can call to validate the location. #3: rule "Customer login from more than 5 locations in the last one month" when $customer : Customer( $id : id ) $locations : Set( size > 5 ) from accumulate( CustomerLogin( customerId == $id, $loc : location ) over window:time( 30d ), collectSet( $loc ) ) then // do something as the customer logged in from more than 5 locations in the last 30 days end In the previous rule I decided to use sliding windows, just to show how that feature can be used to simplify rules, but again, there are several ways of doing it. I strongly recommend you read Drools manual. http://www.jboss.org/drools/documentation.html Cheers, Edson 2009/5/19 Bhushan Bhangale <bhushan_bhangale(a)kaleconsultants.com&gt; the mark the user to user one 3777<http://www.plaxo.com/click_to_call?lang=en&src=jj_signature&a... 1+%280%29206+608+3777&amp;Email=bhushan_bhangale(a)kaleconsultants.com&gt; sole Any message message, assumed for Information in Company verification is -- Edson Tirelli JBoss Drools Core Development JBoss, a division of Red Hat @ www.jboss.com