Red Hat Bugzilla – Bug 1288171
RuntimeDataServiceImpl. getProcessInstanceHistory returning incorrect active nodes for tasks inside ad-hoc subprocesses
Last modified: 2016-03-29 10:23:29 EDT
Description of problem:
Example process with user tasks inside ad-hoc subprocess. When starting process instance and viewing the process view, the active tasks are not highlighted. What is highlighted is the ad-hoc process itself. (example here: http://imgur.com/F1xgjTl)
jBPM Designer is getting passed the ID of the ad-hoc subprocess instead of the task inside the subprocess.
The console code should be getting node info from getProcessInstanceHistory in RuntimeDataServiceImpl and there seems to be some issue there with the executed queries
Steps to Reproduce:
1. In workbench create sample process (bpmn2 attached)
3. Start process instance
4. View Process View
The "active" node is the ad-hoc subprocess
The "active" node should be the task inside subprocess
Created attachment 1101880 [details]
sample bpmn2 process
added test case to illustrate it does work as expected, so moving to modified to double check - main thing here is that ad hoc subprocess does not activate any tasks in it so these must be explicitly signaled to be active
Works as Maciej described. If the problem is not connected with not signalling the task inside the ad hoc subprocess, feel free to reopen the issues.
@Maciej Thanks for enhancing the test coverage.