This content has been marked as final. Show 2 replies
hmm... while debugging to see if I could develop a workaround, I learned something....
<end-state name="e2" end-complete-process='true' />
in the end-state 'inside' the fork works as expected.... at least for my simple unit test. I'll make some more extended test and file a jira issue for documenting this...
Shouldn't this behaviour be the default btw?
oeps... sorry... wrong forum