Bug 1238345
| Summary: | [ENG] (6.1.z) REST Query Operation minor bugs: "workItemId" support and task query params support when querying process instances | |||
|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Marco Rietveld <mrietvel> | |
| Component: | Business Central | Assignee: | Shelly McGowan <smcgowan> | |
| Status: | CLOSED EOL | QA Contact: | Lukáš Petrovický <lpetrovi> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 6.1.0 | CC: | alazarot, kverlaen, smcgowan | |
| Target Milestone: | CR1 | |||
| Target Release: | 6.1.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1238351 (view as bug list) | Environment: | ||
| Last Closed: | 2020-03-27 19:42:26 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1238351, 1249860 | |||
Documentation about the "workItemId" can be found here: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html/Development_Guide/chap-Remote_API.html#Parameter_Table When this bug is resolved, rows referencing the "workItemId" parameter in tables in the REST Query API section, should be removed from those tables. Fixed. Commits: 6.2.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/c9d0e3c1 https://github.com/droolsjbpm/droolsjbpm-integration/commit/a1b82089 Verified on BPMS 6.1.3 CR1 |
Description of problem: There are 2 minor bugs that I discovered when extending testing for the REST Query API. 1. Using the "workItemId" parameter for task or process instance queries, results in an exception. 2. The use of task query parameters does not trigger a 400 response when used with the /rest/query/runtime/process operation, and instead triggers an exception. The solutions/fixes to these problems are: 1. Removing support for the "workItemId" parameter. Adding support for this parameter is non-trivial, and I believe that the parameter is hardly used. 2. Modifying the code to return a HTTP 400 code when task query parameters are used when querying process instances (/rest/query/runtime/process). Version-Release number of selected component (if applicable): 6.1.1 How reproducible: Always Steps to Reproduce: [1/workItemId] 1. Do a query (task or proc inst) with the "workItemId" parameter [2/task query params] 1. Do a proc instance query API REST request using a task query param ("taskId", "potentialOwner", etc.). Actual results: An exception is thrown. Expected results: [1/workItemId] 1. A HTTP 400 code is returned with the message "workItemId" is not supported [2/task query params] 1. a HTTP 400 code is returned with the message that the given query is not supported. Additional info: This bug is meant for product 6.1/community 6.2.