update docs -> less verbose

camunda · Sep 20, 2024 · 86488bb · 86488bb
1 parent 7fb55ec
commit 86488bb
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 6 deletions.
diff --git a/engine-rest/engine-rest-openapi/src/main/templates/lib/commons/history-process-instance.ftl b/engine-rest/engine-rest-openapi/src/main/templates/lib/commons/history-process-instance.ftl
@@ -234,10 +234,7 @@
   "activityIdIn": {
     "type": "array",
     "itemType": "string",
-    "desc": "Restrict to instances that have an active activity or failing activity with one of given ids. It works
-             similarly to the activityIdIn filter in the runtime query. Difference is activities that follow
-             an asyncAfter activity or themselves are asyncBefore or boundary activities are not considered active until
-             the scheduler picked them up for execution. ${listTypeDescription}"
+    "desc": "Restrict to instances that have an active activity or failing activity with one of the given ids. ${listTypeDescription}"
   },
 
   "executedActivityIdIn": {

diff --git a/engine/src/main/java/org/camunda/bpm/engine/history/HistoricProcessInstanceQuery.java b/engine/src/main/java/org/camunda/bpm/engine/history/HistoricProcessInstanceQuery.java
@@ -437,8 +437,6 @@ public interface HistoricProcessInstanceQuery extends Query<HistoricProcessInsta
 
   /**
    * Only select historic process instances that have active activities or failing activities with given ids.
-   * Activities that follow an asyncAfter activity or themselves are asyncBefore or boundary activities are not
-   * considered active until the scheduler picked them up for execution.
    */
   HistoricProcessInstanceQuery activityIdIn(String... ids);