<div style="font-family:arial,helvetica,sans-serif;font-size:12pt">Thank you,<br> That sounds like a good idea if we could automatically fix the data or the rules were more fatal instead of warn/error level, but in our case it will require some human intervention and I don't think we will want to stop everything until it gets fixed. I will keep this in mind if we run into any real critical errors though.<br><br>Wendy<br><div><br></div><div style="font-family:arial, helvetica, sans-serif;font-size:12pt"><br><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Edson Tirelli-4 [via Drools] <<a href="/user/SendEmail.jtp?type=node&node=3137120&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>><br><b><span style="font-weight: bold;">To:</span></b> wendy
<<a href="/user/SendEmail.jtp?type=node&node=3137120&i=1" target="_top" rel="nofollow" link="external">[hidden email]</a>><br><b><span style="font-weight: bold;">Sent:</span></b> Sat, July 2, 2011 1:34:42 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [rules-users] Common Practices for warning or debug rules/messages<br></font><br>
<div><br></div> Hi, I think this is the best use case for agenda-groups + auto-focus... i.e., you add your rules to your kbase, and the rules remain there and will not fire, unless an extraordinary condition is detected, in which case the auto-focus will trigger, "pausing" the execution of the other rules to do whatever is necessary to handle the extraordinary condition. After it is fixed, the processing resumes with the regular rules.<div>
<br></div><div> Not sure if that is what you are looking for, but hope it helps.<br><div><br></div><div> Edson<br><br><div class="gmail_quote">2011/6/29 wendy <span dir="ltr"><<a rel="nofollow" target="_top" link="external">[hidden email]</a>></span><br>
<blockquote style="border-left:2px solid #CCCCCC;padding:0 1em;" class="gmail_quote">Hi,<br>
I'm working on a system that has a large number of rules and we are<br>
getting to the point where we think it would be useful to have some 'debug'<br>
or 'warning' type rules (for lack of a better word). The warning rules<br>
would be rules that would signal to us that something is wrong with the<br>
underlying data and would require someone to go in and fix something. I was<br>
wondering if there are some standard practice as to how to write, maintain,<br>
format... these rules. I can think of a couple of ways to do this but I<br>
would like the communities opinion. We would also like the ability to turn<br>
on/off these debug or warning rules easily while the rest of the system<br>
keeps on processing.<br>
<br>
Thank you,<br>
Wendy<br>
<font color="#888888"><br>
<br>
<br>
--<br><span>
View this message in context: <a target="_blank" href="http://drools.46999.n3.nabble.com/Common-Practices-for-warning-or-debug-rules-messages-tp3124178p3124178.html" rel="nofollow" link="external">http://drools.46999.n3.nabble.com/Common-Practices-for-warning-or-debug-rules-messages-tp3124178p3124178.html</a></span><br>
Sent from the Drools: User forum mailing list archive at <a target="_blank" href="http://Nabble.com" rel="nofollow" link="external">Nabble.com</a>.<br>
_______________________________________________<br>
rules-users mailing list<br>
<a rel="nofollow" target="_top" link="external">[hidden email]</a><br>
<a rel="nofollow" target="_blank" href="https://lists.jboss.org/mailman/listinfo/rules-users" link="external">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br> Edson Tirelli<br> JBoss Drools Core Development<br> JBoss by Red Hat @ <a rel="nofollow" target="_blank" href="http://www.jboss.com" link="external">www.jboss.com</a><br>
</div></div>
<br>_______________________________________________
<br>rules-users mailing list
<br><a rel="nofollow" target="_top" link="external">[hidden email]</a>
<br><a rel="nofollow" target="_blank" href="https://lists.jboss.org/mailman/listinfo/rules-users" link="external">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
<br>
<br>
<hr color="#cccccc" noshade="noshade" size="1">
<div style="color:#444;font:12px tahoma, geneva, helvetica, arial, sans-serif;">
<div style="font-weight:bold;">If you reply to this email, your message will be added to the discussion below:</div><span>
<a target="_blank" href="http://drools.46999.n3.nabble.com/Common-Practices-for-warning-or-debug-rules-messages-tp3124178p3132693.html" rel="nofollow" link="external">http://drools.46999.n3.nabble.com/Common-Practices-for-warning-or-debug-rules-messages-tp3124178p3132693.html</a>
</span></div>
<div style="color:#666;font:11px tahoma, geneva, helvetica, arial, sans-serif;margin-top:.4em;">
To unsubscribe from Common Practices for warning or debug rules/messages, <a rel="nofollow" target="_blank" href="" link="external">click here</a>.
</div></div></div>
</div>
<br/><hr align="left" width="300" />
View this message in context: <a href="http://drools.46999.n3.nabble.com/Common-Practices-for-warning-or-debug-rules-messages-tp3124178p3137120.html">Re: [rules-users] Common Practices for warning or debug rules/messages</a><br/>
Sent from the <a href="http://drools.46999.n3.nabble.com/Drools-User-forum-f47000.html">Drools: User forum mailing list archive</a> at Nabble.com.<br/>