This was my own bad. The splitnode constraint does use the working memory.
The problem was the rules in the previous RuleSetNode weren't firing
correctly. The Process API in general seems to work well and is good for our
purposes.
--
View this message in context:
http://drools.46999.n3.nabble.com/Process-RulesetNode-and-SplitNode-worki...
Sent from the Drools: User forum mailing list archive at
Nabble.com.