Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-13572

TaskFilter with Or Query including candidateUser and candidateGroup throws Exception

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.16.0, 7.15.6, 7.16.0-alpha5
    • None
    • None
    • None

      Environment (Required on creation):

      Tested on 7.16.0-alpha1

      Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

      The engine throws an exception when a user creates a filter through Tasklist containing "candidateUser" and "candidateGroup" in an Or query.

      Steps to reproduce (Required on creation):

      1. Open Tasklist
      2. Click "create filter"
      3. add criteria "candidateUser" and "candidateGroup" and select match ANY
      4. Click "save"

      Observed Behavior (Required on creation):

      Tasklist shows an error message but no filters making it impossible to interact with other filters.
      The engine log shows an exception message containing: {{ Invalid query usage: cannot set both candidateGroup and candidateUser}}.

      Expected behavior (Required on creation):

      Root Cause (Required on prioritization):

      The filter is saved correctly as both criteria are allowed together in or queries.
      When loading the filter list again the JsonTaskQueryConverter converts the OR query JSON String to a TaskQueryImpl object without setting the isOrQueryActive flag. This causes the check to fail.

      Solution Ideas (Optional):

      isOrQueryActive should be true when creating the Or Query from the JSON string

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              miklas.boskamp Miklas Boskamp
              Tobias Metzke-Bernstein Tobias Metzke-Bernstein
              Miklas Boskamp Miklas Boskamp
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: