You can assign the session clock to a global and access it from LHS conditions and inline accumulate functions. However, be aware that the value obtained from the session clock during LHS evaluations is anything between one WM operation and rule evaluation starts and another WM operation and the activation is created or recreated. This is particularly true with accumulate, where insertions and retractions result in partial re-evaluations so that different evaluations of the "action" or "reverse" part are bound to obtain different values. Depending on what you want to achieve, a more consistent notion of "now" can be obtained by inserting a fact containing the current time (obtained from the session clock), evaluating whatsoever against this value, and advancing this "clock" in a predictable way. -W On 24/05/2012, radai rosenblatt <radai.rosenblatt(a)gmail.com&gt; wrote:

On 24/05/2012, radai rosenblatt <radai.rosenblatt(a)gmail.com&gt; wrote: Don't know what you mean by that. No, because the clock will change, but the rules engine will not be instructed about these changes, so some "frozen" value will be used in some evaluations; some other "frozen" value in others... -W