ive temporaily fixed this by adding a session scoped varaible rather than a conversational scoped one...
i dont like this ... but it works.
By "session scoped", do you mean "token-scoped" by adding variables to the process definition, or are you referring to something outside of JBPM?
If you mean "token-scoped", AFAIK this is the standard way to pass data from node to node. I'm curious - why don't you like it?
im using SEAM, SESSION scope is one of the contexts that you can work in and is also made available to the process definition...placing my variab in the session scope meant that it was available to the node imediatly following the descision node... as long as the session is not destroyed durring the decision im OK .... but i hate this method... and is esentially a hack..
Ill give that a look mate
nice one estaub