I've been using the following from a script node outside of an adhoc subprocess to activate a human task node inside the adhoc subprocess where the task name is "AddNoteTask".
I've moved that script node to a flow inside the adhoc subprocess and now it doesn't activate the "AddNoteTask" human task node when it is executed.
Does kcontext refer to a different context when the script task is inside a sub process? How can I get this to work?
I'm using JBPM 6.0.0.CR5
I mixed up the node name and task name. I was signalling with the task name of the human task node I wanted to activate. Changed it to the node name and it works as expected now.
To answer my other question, kcontext does point to a different context when inside the ad hoc sub process but kcontext.getProcessInstance() returns the same instance.