1 of 1 people found this helpful
Not that I know of.
The following things happen in sequence when transition happens from one activity to another
1. End event fires for the source node
2. Destination activity is set on the execution
3. Start event is fired on the destination node
4. execute method of destination activity behaviour is called
For a task node, the task is saved in db at step 4, and you expecting the id in step 3. Hence problem.
There is a bug logged already: https://jira.jboss.org/jira/browse/JBPM-2644
I'll wait for the bug fixing, meanwhile
in your opinion exists a workaround for this behaviour?
How can i get the current task id?