On 31 March 2011 07:58, Benson Fung <benson.redhat(a)gmail.com&gt; wrote: > Hi, > > If there are 10 rules in the drools rulebase, and right now I would > like to execute one of the particular rule. Is there any approach/way > to execute particular rule programmatically? No. The right hand side of a rule (code between "then" and "end") is executed whenever there is a set of fact objects in Working Memory satisfying the condition. If you insert such a set of facts and call fireAllRules(), then it will happen. > I don't think > agenda-group or activation-group can do that, right? Or is it > possible to create an agenda programmatically ? > No to both. -W > > Thanks > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Agreed, But if you really do want to you can setup an agenda filter so that only the activation for the rule you care about is fired – but I don’t think there are many valid cases where this is needed/desirable/appropriate. Thomas *From:* rules-users-bounces(a)lists.jboss.org [mailto: rules-users-bounces(a)lists.jboss.org] *On Behalf Of *Michael Anstis *Sent:* 31 March 2011 10:08 *To:* Rules Users List *Subject:* Re: [rules-users] execute particular rules programmatically and dynamically Why would you want to execute a single rule? The logic you'd write to determine which rule to fire should itself be part of the rules: So, for example, if you want to validate facts of type "Smurf" then write a rule that matches on "Smurf". When you insert a "Smurf" only the rules that match on this will become candidates for execution when you call fireAllRules. Perhaps use of a stateless session would simplify things so you need not worry about other facts in WM "polluting" the results you expect to see? More and more questions are posted here asking how to make individual rules execute; IMO the solution is to change your thinking about how Rules Engines work. If you give your use-case we might be able to advise a better approach. With kind regards, Mike 2011/3/31 Wolfgang Laun <wolfgang.laun(a)gmail.com&gt; On 31 March 2011 07:58, Benson Fung <benson.redhat(a)gmail.com&gt; wrote: Hi, If there are 10 rules in the drools rulebase, and right now I would like to execute one of the particular rule. Is there any approach/way to execute particular rule programmatically? No. The right hand side of a rule (code between "then" and "end") is executed whenever there is a set of fact objects in Working Memory satisfying the condition. If you insert such a set of facts and call fireAllRules(), then it will happen. I don't think agenda-group or activation-group can do that, right? Or is it possible to create an agenda programmatically ? No to both. -W Thanks _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users ------------------------------ ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster(a)nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ************************************************************************************** _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Why would you want to execute a single rule? The logic you'd write to determine which rule to fire should itself be part of the rules: So, for example, if you want to validate facts of type "Smurf" then write a rule that matches on "Smurf". When you insert a "Smurf" only the rules that match on this will become candidates for execution when you call fireAllRules. Perhaps use of a stateless session would simplify things so you need not worry about other facts in WM "polluting" the results you expect to see? More and more questions are posted here asking how to make individual rules execute; IMO the solution is to change your thinking about how Rules Engines work. If you give your use-case we might be able to advise a better approach. With kind regards, Mike 2011/3/31 Wolfgang Laun <wolfgang.laun(a)gmail.com&gt; > > > On 31 March 2011 07:58, Benson Fung <benson.redhat(a)gmail.com&gt; wrote: >> >> Hi, >> >> If there are 10 rules in the drools rulebase, and right now I would >> like to execute one of the particular rule.  Is there any approach/way >> to execute particular rule programmatically? > > No. The right hand side of a rule (code between "then" and "end") is > executed whenever there is a set of fact objects in Working Memory > satisfying the condition. If you insert such a set of facts and call > fireAllRules(), then it will happen. > > >> >>  I don't think >> agenda-group or activation-group can do that, right?  Or is it >> possible to create an agenda programmatically ? > > No to both. > -W > >> >> Thanks >> _______________________________________________ >> rules-users mailing list >> rules-users(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/rules-users > > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

If you split up your rules across many rule files, you can selectively execute specific rule files. Very simple but it works :-) Jevon On Thu, Mar 31, 2011 at 6:58 PM, Benson Fung <benson.redhat(a)gmail.com&gt; wrote: > Hi, > > If there are 10 rules in the drools rulebase, and right now I would > like to execute one of the particular rule.  Is there any approach/way > to execute particular rule programmatically?  I don't think > agenda-group or activation-group can do that, right?  Or is it > possible to create an agenda programmatically ? > > Thanks > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Hi, Here is the scenario : If there are 2 edit boxes and 2 dropdown list at the frontend like. dropdown(minIssrdAge1) editbox(age1) dropdown(minIssrdAge2) editbox(age2) everytime when I lost focus the editbox(age1 or age2), the editbox(age1 or age2) value will be validated against the following rules. i.e. minIssrdAge1 and age1 will be validated together if lost focus the editbox age1. minIssrdAge2 and age2 will be validated together if lost focus the editbox age2 Rule1 is mandatory because both editbox are required field. However, editbox(age1) is only valid within the 0 and 100. and editbox(age2) is only valid within 0 and 600. In other words, editbox(age1) have to be validated against Rule1 + Rule2. However, editbox(age2) have to validated against Rule1 + Rule3. My question, how to design the rule attribute or at the java program side so that different editbox can be validated against different rule. Please help. I can't find any solution by now. rule "Rule1" salience 1 dialect "mvel" when ad : ApplicationData( age == "" || ( == null )) then ad.setReturnMsg( "\n age should not be null or empty" ); end rule "Rule2" dialect "mvel" when ad : ApplicationData( $age : age != null , age != "" , minIssrdAge == "Years" ) eval(Integer.parseInt($age) < 0) or eval(Integer.parseInt($age) > 100) then ad.setReturnMsg( "\nage is out of the range(i.e. < 0 and > 100)" ); end rule "Rule3" dialect "mvel" when ad : ApplicationData( $age : age != null , age != "" , minIssrdAge == "Years" ) eval(Integer.parseInt($age) < 0) or eval(Integer.parseInt($age) > 600) then ad.setReturnMsg( "\nage is out of the range(i.e. < 0 and > 600)" ); end _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Here's a quick (and probably sub-optimal way) ;) When you copy values from the UI to Facts for validation you also include the context of the validation. I've also removed the inline evals you were using. rule "Rule1"   salience 1   dialect "mvel"     when       ApplicationContext( context == "*" )       ad : ApplicationData( age == "" || (  == null ))     then       ad.setReturnMsg( "\n age should not be null or empty" ); end rule "Rule2"   dialect "mvel"     when       ApplicationContext( context == "screen1.panel1.ed" )       ad : ApplicationData( $age : age != null , age != "" , age < 0 || > 100, minIssrdAge == "Years" )     then       ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 and > 100)" ); end rule "Rule3"    dialect "mvel"      when        ad : ApplicationData( $age : age != null , age != "" , age <0 || > 600, minIssrdAge == "Years" )      then        ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 and > 600)" ); end On 13 April 2011 17:19, Benson Fung <benson.redhat(a)gmail.com&gt; wrote: > > Hi, > > Here is the scenario : > > If there are 2 edit boxes and 2 dropdown list at the frontend like. > > > dropdown(minIssrdAge1)   editbox(age1) > dropdown(minIssrdAge2)   editbox(age2) > > everytime when I lost focus the editbox(age1 or age2),  the > editbox(age1 or age2) value will be validated against the following > rules. > i.e.  minIssrdAge1 and age1 will be validated together if lost focus > the editbox age1. >       minIssrdAge2 and age2 will be validated together if lost focus > the editbox age2 > > Rule1 is mandatory because both editbox are required field. > However, editbox(age1) is only valid within the 0 and 100.  and > editbox(age2) is only valid within 0 and 600. > > In other words, editbox(age1) have to be validated against Rule1 + > Rule2.  However, editbox(age2) have to validated against Rule1 + > Rule3. > > My question, how to design the rule attribute or at the java program > side so that different editbox can be validated against different > rule. > > Please help.  I can't find any solution by now. > > rule "Rule1" >        salience 1 >        dialect "mvel" >        when >                ad : ApplicationData( age == "" || (  == null )) >        then >                ad.setReturnMsg( "\n age should not be null or empty" ); > end > > > rule "Rule2" >        dialect "mvel" >        when >                ad : ApplicationData( $age : age != null , age != "" , > minIssrdAge > == "Years" ) >                eval(Integer.parseInt($age) < 0) or > eval(Integer.parseInt($age) > 100) >        then >                ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 and > > 100)" ); > end > > rule "Rule3" >        dialect "mvel" >        when >                ad : ApplicationData( $age : age != null , age != "" , > minIssrdAge > == "Years" ) >                eval(Integer.parseInt($age) < 0) or > eval(Integer.parseInt($age) > 600) >        then >                ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 and > > 600)" ); > end > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Sure, whenever you copy values from your UI to your model for validation you also enter a fact representing the "context" of the values. Using your example you have two edit boxes on one screen and your rule simply checks for the value of a single edit box; in this case the context differentiates the two. Walking your example: (1) When editbox 1 looses focus you copy the value from the dropdown and edit box 1 into your model, plus you enter a "context" fact stating that these values relate to that part of the UI (say "screen1.panel1.editbox1"). You then insert these facts into WM and call fireAllRules. The rules check the "context" and only execute if the values are for the (rule) applicable context. (2) Editbox 2 works in a similar way, but has a different context ((say "screen1.panel1.editbox2"). Have a look at Plugtree - I believe they're quite well customed to writing UIs backed with rules; salaboy or esteban (or IRC #drools) might be able to offer more practical advice. With kind regards, Mike On 13 April 2011 17:48, Benson Fung <benson.redhat(a)gmail.com&gt; wrote: > > Hi Michael, > > Can you elaborate more for the uses of the ApplicationContext?  I > can't follow its uses. > > > Thanks > Benson > > 2011/4/14 Michael Anstis <michael.anstis(a)gmail.com&gt;: > > Here's a quick (and probably sub-optimal way) ;) > > > > When you copy values from the UI to Facts for validation you also > > include > > the context of the validation. > > > > I've also removed the inline evals you were using. > > > > rule "Rule1" > >   salience 1 > >   dialect "mvel" > >     when > >       ApplicationContext( context == "*" ) > >       ad : ApplicationData( age == "" || (  == null )) > >     then > >       ad.setReturnMsg( "\n age should not be null or empty" ); > > end > > > > rule "Rule2" > >   dialect "mvel" > >     when > >       ApplicationContext( context == "screen1.panel1.ed" ) > >       ad : ApplicationData( $age : age != null , age != "" , age < 0 || > > > > > 100, minIssrdAge == "Years" ) > >     then > >       ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 and > 100)" > > ); > > end > > > > rule "Rule3" > >    dialect "mvel" > >      when > >        ad : ApplicationData( $age : age != null , age != "" , age <0 || > > > > > 600, minIssrdAge == "Years" ) > >      then > >        ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 and > 600)" > > ); > > end > > > > On 13 April 2011 17:19, Benson Fung <benson.redhat(a)gmail.com&gt; wrote: > >> > >> Hi, > >> > >> Here is the scenario : > >> > >> If there are 2 edit boxes and 2 dropdown list at the frontend like. > >> > >> > >> dropdown(minIssrdAge1)   editbox(age1) > >> dropdown(minIssrdAge2)   editbox(age2) > >> > >> everytime when I lost focus the editbox(age1 or age2),  the > >> editbox(age1 or age2) value will be validated against the following > >> rules. > >> i.e.  minIssrdAge1 and age1 will be validated together if lost focus > >> the editbox age1. > >>       minIssrdAge2 and age2 will be validated together if lost focus > >> the editbox age2 > >> > >> Rule1 is mandatory because both editbox are required field. > >> However, editbox(age1) is only valid within the 0 and 100.  and > >> editbox(age2) is only valid within 0 and 600. > >> > >> In other words, editbox(age1) have to be validated against Rule1 + > >> Rule2.  However, editbox(age2) have to validated against Rule1 + > >> Rule3. > >> > >> My question, how to design the rule attribute or at the java program > >> side so that different editbox can be validated against different > >> rule. > >> > >> Please help.  I can't find any solution by now. > >> > >> rule "Rule1" > >>        salience 1 > >>        dialect "mvel" > >>        when > >>                ad : ApplicationData( age == "" || (  == null )) > >>        then > >>                ad.setReturnMsg( "\n age should not be null or empty" ); > >> end > >> > >> > >> rule "Rule2" > >>        dialect "mvel" > >>        when > >>                ad : ApplicationData( $age : age != null , age != "" , > >> minIssrdAge > >> == "Years" ) > >>                eval(Integer.parseInt($age) < 0) or > >> eval(Integer.parseInt($age) > 100) > >>        then > >>                ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 > >> and > > >> 100)" ); > >> end > >> > >> rule "Rule3" > >>        dialect "mvel" > >>        when > >>                ad : ApplicationData( $age : age != null , age != "" , > >> minIssrdAge > >> == "Years" ) > >>                eval(Integer.parseInt($age) < 0) or > >> eval(Integer.parseInt($age) > 600) > >>        then > >>                ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 > >> and > > >> 600)" ); > >> end > >> _______________________________________________ > >> rules-users mailing list > >> rules-users(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/rules-users > > > > > > _______________________________________________ > > rules-users mailing list > > rules-users(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/rules-users > > > > > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

In my example Rule 1 was shared between "screen1.panel1.editbox1" and "screen1.panel1.editbox2":- rule "Rule1"   salience 1   dialect "mvel"     when       ApplicationContext( context in ("screen1.panel1.editbox1", "screen1.panel1.editbox2") )       ad : ApplicationData( age == "" || (  == null ))     then       ad.setReturnMsg( "\n age should not be null or empty" ); end This is an approach and may not be the best available; I was trying to demonstrate how your problem can be solved without having to worry about explicitly executing individual rules.For example, depending on what UI technology you are using (Swing, JSF) you could subclass the UI components and use these as facts - but such close coupling between UI and Rules may be undesirable. With kind regards, Mike On 14 April 2011 03:52, Benson Fung <benson.redhat(a)gmail.com&gt; wrote: > > Good, Michael. > > 'context' is used to distinguish which part of the UI which will be > validated, right?  The customer will ask if they have 10000 rules in > the rulebase.  And some of them are redundant, so they want to make > some of the rules share with several part of UI, e.g.  editbox 6, > editbox 7 and editbox 8 these 3 boxes' value range is within 0 and > 600.  Therefore, Rule3 can be shared for these 3 editbox validation, > right?  However, for the context variable approach, it seems Rule3 > cannot be shared for another editbox with same value range validation. >  So these could be a key for the BRMS/Drools. > > > Benson > > 2011/4/14 Michael Anstis <michael.anstis(a)gmail.com&gt;: > > Sure, whenever you copy values from your UI to your model for validation > > you > > also enter a fact representing the "context" of the values. > > > > Using your example you have two edit boxes on one screen and your rule > > simply checks for the value of a single edit box; in this case the > > context > > differentiates the two. > > > > Walking your example: > > > > (1) When editbox 1 looses focus you copy the value from the dropdown and > > edit box 1 into your model, plus you enter a "context" fact stating that > > these values relate to that part of the UI (say > > "screen1.panel1.editbox1"). > > You then insert these facts into WM and call fireAllRules. The rules > > check > > the "context" and only execute if the values are for the (rule) > > applicable > > context. (2) Editbox 2 works in a similar way, but has a different > > context > > ((say "screen1.panel1.editbox2"). > > > > Have a look at Plugtree - I believe they're quite well customed to > > writing > > UIs backed with rules; salaboy or esteban (or IRC #drools) might be able > > to > > offer more practical advice. > > > > With kind regards, > > > > Mike > > > > > > > > On 13 April 2011 17:48, Benson Fung <benson.redhat(a)gmail.com&gt; wrote: > >> > >> Hi Michael, > >> > >> Can you elaborate more for the uses of the ApplicationContext?  I > >> can't follow its uses. > >> > >> > >> Thanks > >> Benson > >> > >> 2011/4/14 Michael Anstis <michael.anstis(a)gmail.com&gt;: > >> > Here's a quick (and probably sub-optimal way) ;) > >> > > >> > When you copy values from the UI to Facts for validation you also > >> > include > >> > the context of the validation. > >> > > >> > I've also removed the inline evals you were using. > >> > > >> > rule "Rule1" > >> >   salience 1 > >> >   dialect "mvel" > >> >     when > >> >       ApplicationContext( context == "*" ) > >> >       ad : ApplicationData( age == "" || (  == null )) > >> >     then > >> >       ad.setReturnMsg( "\n age should not be null or empty" ); > >> > end > >> > > >> > rule "Rule2" > >> >   dialect "mvel" > >> >     when > >> >       ApplicationContext( context == "screen1.panel1.ed" ) > >> >       ad : ApplicationData( $age : age != null , age != "" , age < 0 > >> > || > >> > > > >> > 100, minIssrdAge == "Years" ) > >> >     then > >> >       ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 and > > >> > 100)" > >> > ); > >> > end > >> > > >> > rule "Rule3" > >> >    dialect "mvel" > >> >      when > >> >        ad : ApplicationData( $age : age != null , age != "" , age <0 > >> > || > >> > > > >> > 600, minIssrdAge == "Years" ) > >> >      then > >> >        ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 and > > >> > 600)" > >> > ); > >> > end > >> > > >> > On 13 April 2011 17:19, Benson Fung <benson.redhat(a)gmail.com&gt; wrote: > >> >> > >> >> Hi, > >> >> > >> >> Here is the scenario : > >> >> > >> >> If there are 2 edit boxes and 2 dropdown list at the frontend like. > >> >> > >> >> > >> >> dropdown(minIssrdAge1)   editbox(age1) > >> >> dropdown(minIssrdAge2)   editbox(age2) > >> >> > >> >> everytime when I lost focus the editbox(age1 or age2),  the > >> >> editbox(age1 or age2) value will be validated against the following > >> >> rules. > >> >> i.e.  minIssrdAge1 and age1 will be validated together if lost focus > >> >> the editbox age1. > >> >>       minIssrdAge2 and age2 will be validated together if lost focus > >> >> the editbox age2 > >> >> > >> >> Rule1 is mandatory because both editbox are required field. > >> >> However, editbox(age1) is only valid within the 0 and 100.  and > >> >> editbox(age2) is only valid within 0 and 600. > >> >> > >> >> In other words, editbox(age1) have to be validated against Rule1 + > >> >> Rule2.  However, editbox(age2) have to validated against Rule1 + > >> >> Rule3. > >> >> > >> >> My question, how to design the rule attribute or at the java program > >> >> side so that different editbox can be validated against different > >> >> rule. > >> >> > >> >> Please help.  I can't find any solution by now. > >> >> > >> >> rule "Rule1" > >> >>        salience 1 > >> >>        dialect "mvel" > >> >>        when > >> >>                ad : ApplicationData( age == "" || (  == null )) > >> >>        then > >> >>                ad.setReturnMsg( "\n age should not be null or empty" > >> >> ); > >> >> end > >> >> > >> >> > >> >> rule "Rule2" > >> >>        dialect "mvel" > >> >>        when > >> >>                ad : ApplicationData( $age : age != null , age != "" > >> >> , > >> >> minIssrdAge > >> >> == "Years" ) > >> >>                eval(Integer.parseInt($age) < 0) or > >> >> eval(Integer.parseInt($age) > 100) > >> >>        then > >> >>                ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 > >> >> and > > >> >> 100)" ); > >> >> end > >> >> > >> >> rule "Rule3" > >> >>        dialect "mvel" > >> >>        when > >> >>                ad : ApplicationData( $age : age != null , age != "" > >> >> , > >> >> minIssrdAge > >> >> == "Years" ) > >> >>                eval(Integer.parseInt($age) < 0) or > >> >> eval(Integer.parseInt($age) > 600) > >> >>        then > >> >>                ad.setReturnMsg( "\nage is out of the range(i.e.  < 0 > >> >> and > > >> >> 600)" ); > >> >> end > >> >> _______________________________________________ > >> >> rules-users mailing list > >> >> rules-users(a)lists.jboss.org > >> >> https://lists.jboss.org/mailman/listinfo/rules-users > >> > > >> > > >> > _______________________________________________ > >> > rules-users mailing list > >> > rules-users(a)lists.jboss.org > >> > https://lists.jboss.org/mailman/listinfo/rules-users > >> > > >> > > >> > >> _______________________________________________ > >> rules-users mailing list > >> rules-users(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/rules-users > > > > > > _______________________________________________ > > rules-users mailing list > > rules-users(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/rules-users > > > > > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Hi Wolfgang, Please see the following scenario.