Description of problem: It seems that taskId_min and taskId_max use reverse condition. Version-Release number of selected component (if applicable): 6.2.0 ER5 Steps to Reproduce: 1. Run some processes with tasks. 2. Try to get tasks using taskId_min and taskId_max parameters. Actual results: You get taskId_min behaves like taskId_max should behave and vice versa. Expected results: Correct behavior according to the name of the parameter.
Good catch, Tomas, thanks! PR submitted: https://github.com/droolsjbpm/droolsjbpm-integration/pull/223
Fixed in master. Commits: master: https://github.com/droolsjbpm/droolsjbpm-integration/commit/d8039747
Fixed. Commits: 6.3.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/44257bcc master: (see above)
Verified on BPMS 6.2.0 CR1