docs(update): incidentIdIn can not be applied in OR queries

related to: camunda/camunda-bpm-platform/issues/4632
camunda · Oct 4, 2024 · 922d568 · 922d568
1 parent c1ba386
commit 922d568
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/content/user-guide/process-engine/process-engine-api.md b/content/user-guide/process-engine/process-engine-api.md
@@ -178,7 +178,7 @@ OR queries enable building queries in which filter criteria are linked together
 {{< note title="Heads-up!" class="info" >}}
   - This functionality is only available for task and process instance queries (runtime & history).
   - The following methods cannot be applied to an OR query: orderBy...(), initializeFormKeys(),
-  withCandidateGroups(), withoutCandidateGroups(), withCandidateUsers(), withoutCandidateUsers().
+  withCandidateGroups(), withoutCandidateGroups(), withCandidateUsers(), withoutCandidateUsers(), incidentIdIn().
 {{< /note >}}
 
 After calling `or()`, a chain of several filter criteria could follow. Each filter criterion is linked together