-
Bug Report
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
7.6.0
-
None
In the doc (https://docs.camunda.org/manual/7.5/reference/rest/history/task/get-task-query-count/) it says:
Valid operator values are: eq - equal to; neq - not equal to; gt - greater than; gteq - greater than or equal to; lt - lower than; lteq - lower than or equal to; like.
key and value may not contain underscore or comma characters.
But when I try to filter with the LIKE operator, it returns: "Invalid variable comperator specified: like" Looking at the source code (https://github.com/camunda/camunda-bpm-platform/blob/master/engine-rest/engine-rest/src/main/java/org/camunda/bpm/engine/rest/dto/history/HistoricTaskInstanceQueryDto.java#L551), it seems as only the EQUALS operator is implemented here. It's different (https://github.com/camunda/camunda-bpm-platform/blob/master/engine-rest/engine-rest/src/main/java/org/camunda/bpm/engine/rest/dto/task/TaskQueryDto.java#L1205) for the current instances.
Hi,
Thanks for reaching out to us with this.
You mention that you're using version 7.6.2. This implies that you're an enterprise customer and can make use of our product support. However, you used a throwaway email address to create your account, so we can't determine if that is indeed the case. A short question: was this issue meant to be raised in our support project?
The difference between the Support project and the Camunda BPM project is that when raising issues in the Camunda BPM project, they are not subject to the agreed SLAs and they can be viewed by all users. In contrast, issues raised in the Support project can only be seen by your authorized support contacts and us. You can find more information in our documentation.
If you intended to raise a support issue, please let us know your company and we'll move this issue to the support project.
Thank you and best regards,
Mat