From f036298d3e1575afef7e0864ac6a8ed80aad57e2 Mon Sep 17 00:00:00 2001 From: Christina Ausley Date: Mon, 10 Mar 2025 13:00:07 -0400 Subject: [PATCH] update multi instance docs --- .../modeler/bpmn/multi-instance/multi-instance.md | 11 +++++------ .../modeler/bpmn/multi-instance/multi-instance.md | 13 ++++++------- .../modeler/bpmn/multi-instance/multi-instance.md | 11 +++++------ 3 files changed, 16 insertions(+), 19 deletions(-) diff --git a/docs/components/modeler/bpmn/multi-instance/multi-instance.md b/docs/components/modeler/bpmn/multi-instance/multi-instance.md index acc0429530a..e1ae297faf5 100644 --- a/docs/components/modeler/bpmn/multi-instance/multi-instance.md +++ b/docs/components/modeler/bpmn/multi-instance/multi-instance.md @@ -6,12 +6,7 @@ description: "Learn about multi-instance activities like service tasks and recei A multi-instance activity is executed multiple times - once for each element of a given collection (like a _foreach_ loop in a programming language). -The following activities can be marked as multi-instance: - -- [Service tasks](../service-tasks/service-tasks.md) -- [Receive tasks](../receive-tasks/receive-tasks.md) -- [Embedded subprocesses](../embedded-subprocesses/embedded-subprocesses.md) -- [Call activities](../call-activities/call-activities.md) +We support the multi-instance marker for all [supported activities](/components/modeler/bpmn/bpmn-coverage.md), such as service tasks, receive tasks, embedded subprocceses, and call activities. For example: ![multi-instance](assets/multi-instance-example.png) @@ -19,6 +14,10 @@ On the execution level, a multi-instance activity has two parts: a multi-instanc When the activity is entered, the multi-instance body is activated and one instance for every element of the `inputCollection` is created (sequentially or in parallel). When all instances are completed, the body is completed and the activity is left. +:::note +Events with a `JobWorker` implementation, such as intermediate throw events, do not support this marker. +::: + ## Sequential vs. parallel A multi-instance activity is executed either sequentially or in parallel (default). In the BPMN, a sequential multi-instance activity is displayed with three horizontal lines at the bottom. A parallel multi-instance activity is represented by three vertical lines. diff --git a/versioned_docs/version-8.6/components/modeler/bpmn/multi-instance/multi-instance.md b/versioned_docs/version-8.6/components/modeler/bpmn/multi-instance/multi-instance.md index 6817a484f57..e1ae297faf5 100644 --- a/versioned_docs/version-8.6/components/modeler/bpmn/multi-instance/multi-instance.md +++ b/versioned_docs/version-8.6/components/modeler/bpmn/multi-instance/multi-instance.md @@ -1,17 +1,12 @@ --- id: multi-instance title: "Multi-instance" -description: "A multi-instance activity is executed multiple times - once for each element of a given collection." +description: "Learn about multi-instance activities like service tasks and receive tasks. These can be executed multiple times - once for each element of a given collection." --- A multi-instance activity is executed multiple times - once for each element of a given collection (like a _foreach_ loop in a programming language). -The following activities can be marked as multi-instance: - -- [Service tasks](../service-tasks/service-tasks.md) -- [Receive tasks](../receive-tasks/receive-tasks.md) -- [Embedded subprocesses](../embedded-subprocesses/embedded-subprocesses.md) -- [Call activities](../call-activities/call-activities.md) +We support the multi-instance marker for all [supported activities](/components/modeler/bpmn/bpmn-coverage.md), such as service tasks, receive tasks, embedded subprocceses, and call activities. For example: ![multi-instance](assets/multi-instance-example.png) @@ -19,6 +14,10 @@ On the execution level, a multi-instance activity has two parts: a multi-instanc When the activity is entered, the multi-instance body is activated and one instance for every element of the `inputCollection` is created (sequentially or in parallel). When all instances are completed, the body is completed and the activity is left. +:::note +Events with a `JobWorker` implementation, such as intermediate throw events, do not support this marker. +::: + ## Sequential vs. parallel A multi-instance activity is executed either sequentially or in parallel (default). In the BPMN, a sequential multi-instance activity is displayed with three horizontal lines at the bottom. A parallel multi-instance activity is represented by three vertical lines. diff --git a/versioned_docs/version-8.7/components/modeler/bpmn/multi-instance/multi-instance.md b/versioned_docs/version-8.7/components/modeler/bpmn/multi-instance/multi-instance.md index acc0429530a..e1ae297faf5 100644 --- a/versioned_docs/version-8.7/components/modeler/bpmn/multi-instance/multi-instance.md +++ b/versioned_docs/version-8.7/components/modeler/bpmn/multi-instance/multi-instance.md @@ -6,12 +6,7 @@ description: "Learn about multi-instance activities like service tasks and recei A multi-instance activity is executed multiple times - once for each element of a given collection (like a _foreach_ loop in a programming language). -The following activities can be marked as multi-instance: - -- [Service tasks](../service-tasks/service-tasks.md) -- [Receive tasks](../receive-tasks/receive-tasks.md) -- [Embedded subprocesses](../embedded-subprocesses/embedded-subprocesses.md) -- [Call activities](../call-activities/call-activities.md) +We support the multi-instance marker for all [supported activities](/components/modeler/bpmn/bpmn-coverage.md), such as service tasks, receive tasks, embedded subprocceses, and call activities. For example: ![multi-instance](assets/multi-instance-example.png) @@ -19,6 +14,10 @@ On the execution level, a multi-instance activity has two parts: a multi-instanc When the activity is entered, the multi-instance body is activated and one instance for every element of the `inputCollection` is created (sequentially or in parallel). When all instances are completed, the body is completed and the activity is left. +:::note +Events with a `JobWorker` implementation, such as intermediate throw events, do not support this marker. +::: + ## Sequential vs. parallel A multi-instance activity is executed either sequentially or in parallel (default). In the BPMN, a sequential multi-instance activity is displayed with three horizontal lines at the bottom. A parallel multi-instance activity is represented by three vertical lines.