Bug 1262105
| Summary: | [GSS][6.1.z]Task query /query/task endpoint returns all the tasks for the authenticated user and ignores potentialOwner parameter | ||
|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | William Antônio <wsiqueir> |
| Component: | Business Central | Assignee: | Marco Rietveld <mrietvel> |
| Status: | CLOSED WONTFIX | QA Contact: | Lukáš Petrovický <lpetrovi> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1.0 | CC: | kverlaen, lpetrovi, mrietvel, smcgowan |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
Cause:
The results of the REST /query/task or /task/query (operational synonyms) operations do not contain the potential owners information.
Consequence:
Even though the field (or XML/JSON element) is empty or null, this does not mean the task in question does not have potential owners. On the contrary, the problem is that the field has not being filled.
The database query and server side logic are processing the query correctly: however, the results are lacking the potential owner information.
Workaround (if any):
Retrieve the enter Task instance in order to view the potential owners information via the ../rest/task/{taskId} operation.
|
Story Points: | --- |
| Clone Of: | 1262036 | Environment: | |
| Last Closed: | 2015-09-29 14:16:10 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: | 1262036 | ||
| Bug Blocks: | 1259382 | ||
|
Description
William Antônio
2015-09-10 19:56:45 UTC
When the TaskSummary was first created by Mauricio, he added a "potentialOwners" field that he then used a second query to fill. Years later, I used the TaskSummary, unaware that he had used a hack (that we were also no longer using) to fill that field. The problem here is not that the wrong tasks are retrieved: the problem is that the field in the TaskSummary info returned to the client is not filled. The bug has been set to CLOSED/WONTFIX because the problem is not that the query does not work, but that incomplete/incorrect results (namely an empty potentialOwners field) is being returned. However, adding the potential owners information to the result would make the operation at _least_ 2x as slow, because a second database query would have to be done in order to retrieve that information. The ideal situation would be to remove the potentialOwners field/element from the result, however this might break the API for users who are looking at the XML or JSON results, as opposed to serializing the result into a Java objects. As a result, we are doing the following: 1. adding @Deprecated and other comments to the code to show that the field is never stored. 2. Requesting that documentation be added that explains that the potentialOwners field will not be filled when a TaskSummary JAXB/JSON instance is returned from the REST API. In 7.0, we will be removing the potentialOwners field. Added a commit with @Deprecated: https://github.com/droolsjbpm/droolsjbpm-integration/commit/9f2c9078 |