Re: [rules-users] Local Variable

Just to add another option: A variable to set in one and to use in another consequence can also be a static field in some Java class, with (or without - huh!) setter and getter. However, no matter which technique one chooses, setting such a variable in rule A and using its value in rule B creates two dependencies: - the temporal dependency that rule A must execute before rule B - the logical dependency that an execution of rule A with some specific set of facts must "match" the execution of rule B; in other words, one needs to make sure that there is no confusion among multiple executions of rule A and rule B. Only a dynamically created object, inserted logically or not, has a chance to handle these dependencies, with fields in addition to the "value" to be passed on identifying the context, i.e., one or more facts participating in the firing of A. Anything else is playing with fire. -W On 05/10/2012, Davide Sottara <dsotty(a)gmail.com&gt; wrote: