Hi, Edson, I was going through your rule sniplets and I couldn't understand very well one thing: ------------- when $a : Account( $number : number -> ( number % 10 < 5 ), number < 9000 ) not Account( number == ( $number + 1000 ) ) then ------------- The 'number' variable refers to the 'fact' in the working memory, correct? Basically it means I have only one particular number to compare ALL accounts (from the data sheet) with? If so, it's not what I actually need to achieve. I need to compare all accounts with 'each other', all of them coming from the same data sheet. So, I guess it has to be an iteration through all the facts, comparing each fact with every other one. Or is the sniplet above does exactly that? Ie, iterating through all the facts? In other words, I'd be initializing working memory ONLY with the facts below: for (Iterator it = accountsFromDataSheet.iterator(); it.hasNext(); ) { Account account = (Account)it.next(); workingMemory.assertObject(account); } After which the rules must operate on the facts loaded... Thanks. Vlad -----Original Message----- From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Edson Tirelli Sent: 02 February 2007 11:13 To: Rules Users List Subject: Re: [rules-users] advice is needed: rule based processing ofinter connected facts Hi Vlad, This is a case where you can apply business rules with good results. In the end, it all depends on how you model your Business Objects, but lets get some examples: My understanding is that you are validating your accounting plan, so you may have an Account object in your model. So, if you want to report inconsistencies, you can do something like: rule "missing accounts" when $a : Account( $number : number -> ( number % 10 < 5 ), number < 9000 ) not Account( number == ( $number + 1000 ) ) then // $a does not have a matching primary account end Please, note that the "formulas" I used above may not be the best way to do it... they are only a possible representation of what you said. Here, it seems you are refering to a set of transactions, so you might have a set of transaction objects to represent the transaction in your sample. So, a possible representation would be: rule "transaction consistency" when Transaction( $id : id ) $credits: Double( ) from accumulate( TransactionEntry( id == $id, operation == "credit", $amount : amount ), init( double balance = 0 ), action( balance += $amount ), result( new Double( balance ) ) ); $debits: Double( ) from accumulate( TransactionEntry( id == $id, operation == "debit", $amount : amount ), init( double balance = 0 ), action( balance -= $amount ), result( new Double( balance ) ) ); eval( ! $credits.equals( $debits ) ) then // inconsistency for transaction $id end Again, this is not the only way or the best way... it is just an example. Also, for the above examples, I used syntax/features of the jbrules 3.1 version. Hope it helps. []s Edson Olenin, Vladimir (MOH) wrote: of 400 the -- Edson Tirelli Software Engineer - JBoss Rules Core Developer Office: +55 11 3124-6000 Mobile: +55 11 9218-4151 JBoss, a division of Red Hat @ www.jboss.com _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users