-
Bug Report
-
Resolution: Fixed
-
L2 - Critical
-
7.2.0, 7.3.0
-
Windows 10 + tomcat server 7 + Camunda 7.3
Ubuntu 14.04 + tomcat + Camunda 7.2
From the documentation: "Only include tasks that the given user is involved in. A user is involved in a task if an identity link exists between task and user (e.g. the user is the assignee)."
If user is only assignee or owner (or both) of a task, API search does not return this task with parameter involvedUser, although the identity link exists. If I add another identity link of different type than owner or assignee, then the task is returned.
AT:
- When involvedUser is used, filter the query also by task assignee and owner
- Create indexes on those columns
- Validate that it is already correct in the history query (in this case we persist identity links for assignees and owners)
This is the controller panel for Smart Panels app
[CAM-4441] API: Task - Get Tasks: involvedUser not working properly
Hello.
I call "http://localhost:8081/engine-rest/task/?assignee=admin"
and I get
[{
"id": "02825139-e489-4a98-bb78-51886fe9000c",
"name": "test 2",
"assignee": "admin",
......
"owner": "admin",
......
}]
Then I call "http://localhost:8081/engine-rest/task/02825139-e489-4a98-bb78-51886fe9000c/identity-links"
and I get
[{
"userId": "admin",
"groupId": null,
"type": "assignee"
}, {
"userId": "admin",
"groupId": null,
"type": "owner"
}]
So, you see, that Identity links for this task exist.
That means, when I call "http://localhost:8081/engine-rest/task/?involvedUser=admin" , it should return me the same task list as with the first call, but I get only an empty array:
[ ]
Hi Tomas,
if this issue is very urgent from your side, you can speed things up by submitting a pull request, that solves this issue.
Cheers
Robert
Hi,
in version 7.9 this bug still exists. The problem is the following code:
Class: org.camunda.bpm.engine.impl.cmd.AddIdentityLinkCmd (line 71)
public Void execute(CommandContext commandContext) { ensureNotNull("taskId", taskId); TaskManager taskManager = commandContext.getTaskManager(); task = taskManager.findTaskById(taskId); EnsureUtil.ensureNotNull("Cannot find task with id " + taskId, "task", task); checkAddIdentityLink(task, commandContext); if (IdentityLinkType.ASSIGNEE.equals(type)) { task.setAssignee(userId); } else if (IdentityLinkType.OWNER.equals(type)) { task.setOwner(userId); } else { task.addIdentityLink(userId, groupId, type); } return null; }
When you set an assignee to the task it will never create an identity link. And the involved user query is querying the identity links and ignores the assignee value
Please solve this problem in one of the next releases.
Cheers,
Christian
It is not a bug, it is only a misunderstanding on documentation, by default includeAssignedTasks is established on false, so involvedUser or candidateXX, is not going to work as both of you expected, just add includeAssignedTasks=true to query string.
http://localhost:8081/engine-rest/task/?involvedUser=admin&includeAssignedTasks=true
Hi.
I have the same problem here.
The "involvedUser" not working properly (I get only an empty array "[]", when I use: /task/?involvedUser=admin)
When I try the @Juan Parra solution (includeAssignedTasks=true), I have this error:
{
"type": "ProcessEngineException",
"message": "Invalid query usage: candidateUser, candidateGroup, candidateGroupIn, withCandidateGroups, withoutCandidateGroups, withCandidateUsers, withoutCandidateUsers has to be called before 'includeAssignedTasks'."
}
Can you help us?
Thanks for reporting.
Can you provide a failing testcase on this and/or the query you are executing?
Cheers
Robert