In the past, what I've done is have a generic function, which logs which rule + facts fired. In my case, the business user writes/edits rules through a custom rule editor. I wrote a rule compiler to compile the business rules to executable JESS rules. When I generate the rule, every action calls the function and passes in all the facts.
you might be able to do it with jess events http://www.jessrules.com/jess/docs/71/api/jess/JessEvent.html peter On Tue, Jul 8, 2008 at 11:32 AM, Greenblatt, Alan <[EMAIL PROTECTED]> wrote: > You're absolutely right. In my case though, I wanted a general purpose user > function that could act on all of the facts which contributed to the firing > of the rule. I want to be able to create an audit trail of why various > rules fired. I didn't want the rule writer to have to worry about passing > the appropriate parameters. > > - Alan -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
