nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Bug in TaskQuery.taskCandidateOrAssigned?

xman-berlin

Hi all,

after a discussion (http://forums.activiti.org/content/howto-get-both-assigned-tasks-and-tasks-where-use-candidate-one-call) about getting both assigned tasks and tasks being candidates in one call, I would like to discuss whether or not the function is buggy.

Here's the scenario:

Start process with a simple task.
user1 and user2 are candidates of the task.
user1 claims the task.
user1 queries tasks by TaskQuery.taskCandidateOrAssigned: returns task1. -> OK
user2 queries tasks by TaskQuery.taskCandidateOrAssigned: returns task1. -> FAIL.

I thought that claiming a task removes it from tasklist of other candidates. To prove the failure, I tried to claim the task by user2 but this works as expected -> Activiti throws ActivitiTaskAlreadyClaimedException.

This is the SQL query which is used to retrieve the task list.

 <when test="bothCandidateAndAssigned">
          <if test="userIdForCandidateAndAssignee != null">
            and (RES.ASSIGNEE_ = #{userIdForCandidateAndAssignee} or (RES.ASSIGNEE_ is null and I.USER_ID_ = #{userIdForCandidateAndAssignee} or I.GROUP_ID_ IN (select g.GROUP_ID_ from ACT_ID_MEMBERSHIP g where g.USER_ID_ = #{userIdForCandidateAndAssignee} ) ) )
          </if>
        </when>‍‍‍‍‍

I think, the query is missing the limitation to "RES.ASSIGNEE_ is null" when testing the user groups, e.g.:

 <when test="bothCandidateAndAssigned">
          <if test="userIdForCandidateAndAssignee != null">
            and (RES.ASSIGNEE_ = #{userIdForCandidateAndAssignee} or (RES.ASSIGNEE_ is null and I.USER_ID_ = #{userIdForCandidateAndAssignee} or  (RES.ASSIGNEE_ is null and I.GROUP_ID_ IN (select g.GROUP_ID_ from ACT_ID_MEMBERSHIP g where g.USER_ID_ = #{userIdForCandidateAndAssignee} ) ) ) )
          </if>
        </when>‍‍‍‍‍

If I am right, I'd like to file a bug report. Where's the right place?

Thanks,
Best regards,
Torsten

Find more posts tagged with

Comments

martin_grofcik

I attached jUnit test patch. I think it can be done by intention too.

Bug_in_TaskQuery_taskCandidateOrAssigned.patch_.txt.zip

xman-berlin

Hi Martin,

what do you mean with "it can be done by intention too". Do you think this is a bug or not?

I still consider this a bug because the query should return tasks that can be claimed by candidates or are already claimed by the assignee.

Thanks,
Torsten

martin_grofcik

Hi Thorsten,

I think it is not a bug. (Let somebody from activiti core team to decide).
Regards
Martin

jbarrez

This is not a bug. Activiti never does security checks on queries - this is for every query the case, not only for tasks. This should be done in the layer above.
This is intentional, in that we do not want to force any company in a model they don't want.

andrei_akatsyeu

Hi,
I 've a question.

user1 is assignee on task1
user2 is candidate on task1
user3 is membership of group1 and group1 is candidate on task1
taskService.createTaskQuery().taskCandidateOrAssigned("user1") return task1
taskService.createTaskQuery().taskCandidateOrAssigned("user2") return empty list
taskService.createTaskQuery().taskCandidateOrAssigned("user3") return task1

I think point six is like a bug.
Should "taskService.createTaskQuery().taskCandidateOrAssigned("user3")" statement return empty list in this situation?

This is the SQL query which is used to retrieve the task list. <code lang="sql">
<when test="bothCandidateAndAssigned">
          <if test="userIdForCandidateAndAssignee != null">
            and (RES.ASSIGNEE_ = #{userIdForCandidateAndAssignee} or (RES.ASSIGNEE_ is null and I.USER_ID_ = #{userIdForCandidateAndAssignee} or I.GROUP_ID_ IN (select g.GROUP_ID_ from ACT_ID_MEMBERSHIP g where g.USER_ID_ = #{userIdForCandidateAndAssignee} ) ) )
          </if>
        </when>
</code>I think, the query is missing the limitation to "RES.ASSIGNEE_ is null" when testing the user groups, e.g.:<code lang="sql">
<when test="bothCandidateAndAssigned">
          <if test="userIdForCandidateAndAssignee != null">
            and (RES.ASSIGNEE_ = #{userIdForCandidateAndAssignee} or (RES.ASSIGNEE_ is null and I.USER_ID_ = #{userIdForCandidateAndAssignee} or (RES.ASSIGNEE_ is null and I.GROUP_ID_ IN (select g.GROUP_ID_ from ACT_ID_MEMBERSHIP g where g.USER_ID_ = #{userIdForCandidateAndAssignee} ) ) ) )
          </if>
        </when>
</code>

trademak

You are correct, fixed it. Could you please retest it?

Best regards,