Note that rules are evaluated globally. That means that, if you have
multiple instances of a process running in the same session and a rule
constraint becomes valid for one instance, it will be valid for all.
You might want to use a simple code constraint in your split here (and
let that refer to a variable containing your TicketBean).
If you want to make sure that a constraint is linked to only that ticket
bean that your process instance is managing, make sure to bind your
constraint your rule to that process instance. Check out
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/t...
for more info on how to access a process variable from inside a constraint.
Kris
Quoting Anderson vasconcelos <anderson.vass(a)gmail.com>:
Hi
I Have a flow as folow: Start -> First_HumanTask -> Split -> [Join
->
Second_HumanTask] or [End].
When i Create one instance of my flow, this runs fine. But when i
have many
instances of my flow (Size of StatefulKnowledgeSession > 1), and
finish the
First_HumanTask the flow stoped. (Not Create de Second_HumanTask, and
not
throws error)
In my split node i check a fact passed to flow as: TicketBean( status
==
TicketStatus.IN_PROGRESS)
Whats wrong?
Thanks
Disclaimer:
http://www.kuleuven.be/cwis/email_disclaimer.htm