Ok tell us the result when you've re-ordered your priorities.
I suspect that what you will likely see is that the consequeces for the
Assign Task and Audit Task will run over and over again forever. This is
because the modifyObject() call will cause the re-evaluation of the
conditions of rules
From the look of it.
If that last rule you defined is activated it will fire first and set the
status to suspend, so no other rule is fired.
If not you will likely have the rules firing in the following sequence
RouteTask, AssignTask, AuditTask, AssignTask, AuditTask, AssignTask,
AuditTask...
may have another more efficient suggestion however.
On 3/7/06, Lionel Port [EMAIL PROTECTED] wrote:
When you use the fireAllRules(AgendaFilter) method on the WorkingMemory
does
it clear the Agenda when its done or can you fire different rules in
the
working memory at different points
On 3/8/06, Lionel Port [EMAIL PROTECTED] wrote:
Michael was not saying to modify the facts in the consequence. Instead, he
was saying that you it would be _possible_ iterate through the facts after
the rules had fired and modify them.
You could do something like:
memory.fireAllRules
When you use the fireAllRules(AgendaFilter) method on the WorkingMemory does
it clear the Agenda when its done or can you fire different rules in the
working memory at different points in time without modifying the facts in
between.
The rules I have can be broken into two distinct rulesets that
