Maybe you can have a workaround and pass the processInstanceKey as a variable?
Thanks for the reply.
I had that in mind too but I was wondering if there is an way to access the super process.
Is it an intended behavior of jBPM to block the access? If so, why?
At least there should be a method getSuperProcessId() so I can access the super process using the ExecutionService.
don't think it is intended. just not implemented
Do you think you can setup a test case? Can you add a log statement to your assignment handler and check what value you are getting for this?
That's how I'm getting the key right now and it works fine, but it's an ugly cast.
I would like to have a getSuperProcessExecution() on the OpenExecution interface.
OpenExecution has a method getSubProcessInstance() but no method to access the super ProcessInstance, that's basically the issue here.
What was I thinking! I read multiple posts and then got back to this, so lost context, didn't see that you already had the solution for the timebeing. And yes, that should become part of the API, although I think we should clearly specify that in the JIRA.
your right the issue is kind of loosely described, I commented the issue.