Problem with TaskQuery when using custom GroupEntityManager and UserEntityManager

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.

xman-berlin

Hi folks,

I'm facing an issue when I try to perform a task query using "taskCandidateOrAssigned" but using a custom GroupEntityManager. The problem is that the iBatis-query for groups is using actititi internal tables (ACT_ID_MEMBERSHIP) ignoring the configured custom GroupEntityManager (see Task.xml / commonSelectTaskByQueryCriteriaSql / bothCandidateAndAssigned).

I already saw that it is recommended to provide a custom TaskManager as well, but this would mean I'd have to reimplement the whole task query concept just because I need to provide a custom user-group-mapping.

A quick-and-dirty solution would be that in case of using "bothCandidateAndAssigned" the "TaskQuery.taskCandidateGroupIn" attribute (candidateGroups) would be used for the query, e.g.

        <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 
            <foreach item="group" index="index" collection="candidateGroups" 
                     open="(" separator="," close=")">
              #{group}
            </foreach>
) )
          </if>
        </when>
‍‍‍‍‍‍‍‍‍‍‍‍

Any other recommendation how I can solve this issue?

Thanks,
Torsten

jbarrez

Hmmm this seems to me to be more of a bug, as the query basically doesnt work using custom identity management.
Would you be able to create a jira issue for this?