From 00c11c298691fb6e788c1ef2cae613ee10d18756 Mon Sep 17 00:00:00 2001 From: Dmytro Kostiuk Date: Thu, 26 Jun 2025 16:55:00 +0200 Subject: [PATCH 1/5] Document scheduling of added boundary events --- .../modeling/application-logic/workflows/boundary-events.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md b/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md index f6035e2967e..d28c5b15298 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md @@ -60,6 +60,10 @@ To add a boundary event to the [above-listed activities](#supported-activities), To configure the properties of a boundary event, double-click the event to open its properties dialog box. For more information on how to configure the properties of a timer boundary event, see [Boundary Properties](/refguide/timer/#boundary-properties). +#### Adding Boundary Event to Ongoing Activity + +When a boundary event is added to an activity, any workflow instances currently executing that activity will schedule the new boundary event accordingly. The only exception occurs when an ongoing boundary event is first removed, the workflow is redeployed, and then the removal is reverted. In this case, the boundary event will not be rescheduled. + #### Implications of Changing the Boundary Event Type For an existing boundary event, when you change its type from non-interrupting to interrupting or vice versa, you will be presented with a warning dialog. For example, when you change a boundary event from non-interrupting to interrupting, you will see the following warning dialog: @@ -68,7 +72,7 @@ For an existing boundary event, when you change its type from non-interrupting t After you confirm the change: -* The boundary event is re-created as the specified type. +* The boundary event is re-created with the specified type. The new boundary event will be scheduled after redeploy of the workflow, as soon as it becomes in progress. * The workflow will become incompatible if the changed boundary event has already been executed. The workflow becomes incompatible for the following reasons: * If the changed boundary event was non-interrupting, you will get the [Non-interrupting Boundary Event Path Removed](/refguide/workflow-versioning/#non-interrupting-boundary-event-path-removed) conflict. * If the changed boundary event was interrupting, you will get the [Current Activity Removed](/refguide/workflow-versioning/#current-activity-removed) conflict. From a8f52655c16b24c17cfe8fc15bc478a063e5b836 Mon Sep 17 00:00:00 2001 From: Dmytro Kostiuk Date: Tue, 1 Jul 2025 10:44:25 +0200 Subject: [PATCH 2/5] Document external jumps for Interrupting Boundary Events --- .../modeling/application-logic/workflows/boundary-events.md | 2 +- .../refguide/modeling/application-logic/workflows/jump-to.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md b/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md index d28c5b15298..dbcf8ca66ef 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md @@ -118,7 +118,7 @@ When there are multiple boundary events attached to an activity and an interrupt Boundary events come with a specific set of rules for jumps. These rules are applicable to both types of jumps - [Jumping to other activities in design time](/refguide/jump-activity/) and [Jumping in running workflow instances](/refguide/jump-to/). The rules are as follows: * Jump inside a boundary event: not possible -* Jump outside a boundary event: not possible (a future plan is to make it possible to jump outside interrupting boundary events but only to the parent or grandparent path) +* Jump outside a boundary event: not possible, except when jumping from an interrupting boundary event to its parent or grandparent path, which is possible * Jump within a boundary event: possible ## Boundary Event Variables diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/jump-to.md b/content/en/docs/refguide/modeling/application-logic/workflows/jump-to.md index 0417693a6ec..6e3847753e0 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/jump-to.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/jump-to.md @@ -42,7 +42,7 @@ After setting the objects, changes can be applied by calling a microflow contain ## Jumping to Other Activities in Parallel Splits or in Boundary Event Paths -Jumping to other activities has a limitation in parallel splits and in boundary event paths: it is not possible to jump into or out of a current parallel split or boundary event path. However, it is possible to jump to other activities within a current parallel split or boundary event path, including the end of the path. Activities in other parallel splits or boundary event paths, as well as activities outside the current path, are not available in the **System.WorkflowCurrentActivity_ApplicableTargets** association. +Jumping to other activities has a limitation in parallel splits and in boundary event paths: it is not possible to jump into or out of a current parallel split or boundary event path. However, it is possible to jump to other activities within a current parallel split or boundary event path, including the end of the path. Also, it is possible to jump from an interrupting boundary event to its parent or grandparent path, since they are considered part of the same path. Activities in other parallel splits or boundary event paths, as well as activities outside the current path, are not available in the **System.WorkflowCurrentActivity_ApplicableTargets** association. For more information about jumping rules in a boundary event path, see the [Jump Rules](/refguide/workflow-boundary-events/#jump-rules) section in *Boundary Events*. From d3f290e4be962dd3ca91c9508923918c6258091c Mon Sep 17 00:00:00 2001 From: Yiyun Liao Date: Tue, 8 Jul 2025 15:31:28 +0200 Subject: [PATCH 3/5] Minimal language review --- .../application-logic/workflows/boundary-events.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md b/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md index dbcf8ca66ef..6150404420b 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md @@ -60,9 +60,9 @@ To add a boundary event to the [above-listed activities](#supported-activities), To configure the properties of a boundary event, double-click the event to open its properties dialog box. For more information on how to configure the properties of a timer boundary event, see [Boundary Properties](/refguide/timer/#boundary-properties). -#### Adding Boundary Event to Ongoing Activity +#### Adding a Boundary Event to an Ongoing Activity -When a boundary event is added to an activity, any workflow instances currently executing that activity will schedule the new boundary event accordingly. The only exception occurs when an ongoing boundary event is first removed, the workflow is redeployed, and then the removal is reverted. In this case, the boundary event will not be rescheduled. +When a boundary event is added to an ongoing activity, any workflow instances currently executing that activity will schedule the new boundary event accordingly. The only exception occurs when an ongoing boundary event is removed, the workflow is redeployed, and then the removal is reverted. In this case, the boundary event will not be rescheduled. #### Implications of Changing the Boundary Event Type @@ -72,7 +72,7 @@ For an existing boundary event, when you change its type from non-interrupting t After you confirm the change: -* The boundary event is re-created with the specified type. The new boundary event will be scheduled after redeploy of the workflow, as soon as it becomes in progress. +* The boundary event is re-created with the specified type. The new boundary event will be scheduled after the workflow is redeployed and becomes in progress. * The workflow will become incompatible if the changed boundary event has already been executed. The workflow becomes incompatible for the following reasons: * If the changed boundary event was non-interrupting, you will get the [Non-interrupting Boundary Event Path Removed](/refguide/workflow-versioning/#non-interrupting-boundary-event-path-removed) conflict. * If the changed boundary event was interrupting, you will get the [Current Activity Removed](/refguide/workflow-versioning/#current-activity-removed) conflict. @@ -118,7 +118,7 @@ When there are multiple boundary events attached to an activity and an interrupt Boundary events come with a specific set of rules for jumps. These rules are applicable to both types of jumps - [Jumping to other activities in design time](/refguide/jump-activity/) and [Jumping in running workflow instances](/refguide/jump-to/). The rules are as follows: * Jump inside a boundary event: not possible -* Jump outside a boundary event: not possible, except when jumping from an interrupting boundary event to its parent or grandparent path, which is possible +* Jump outside a boundary event: only possible when jumping from an interrupting boundary event path to its parent or grandparent path * Jump within a boundary event: possible ## Boundary Event Variables From 2ed08fbbfb35f2487722a88e59c23c14b90bde6a Mon Sep 17 00:00:00 2001 From: Yiyun Liao <110980413+Yiyun333@users.noreply.github.com> Date: Tue, 8 Jul 2025 17:52:21 +0200 Subject: [PATCH 4/5] Language review --- .../modeling/application-logic/workflows/boundary-events.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md b/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md index 6150404420b..cf7ecc577bc 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md @@ -62,7 +62,7 @@ To configure the properties of a boundary event, double-click the event to open #### Adding a Boundary Event to an Ongoing Activity -When a boundary event is added to an ongoing activity, any workflow instances currently executing that activity will schedule the new boundary event accordingly. The only exception occurs when an ongoing boundary event is removed, the workflow is redeployed, and then the removal is reverted. In this case, the boundary event will not be rescheduled. +When a boundary event is added to an ongoing activity, any workflow instances currently executing that activity will schedule the new boundary event accordingly. The only exception occurs when an ongoing boundary event is removed from the ongoing activity, the workflow is redeployed, and then the removal is reverted. In this case, the re-added boundary event will not be scheduled. #### Implications of Changing the Boundary Event Type From f60140987e09b16f476e33222de09b547bcb4de0 Mon Sep 17 00:00:00 2001 From: Yiyun Liao <110980413+Yiyun333@users.noreply.github.com> Date: Wed, 9 Jul 2025 09:27:09 +0200 Subject: [PATCH 5/5] Small language adjustment in Update jump-to.md --- .../refguide/modeling/application-logic/workflows/jump-to.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/jump-to.md b/content/en/docs/refguide/modeling/application-logic/workflows/jump-to.md index 6e3847753e0..c7ff2b50824 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/jump-to.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/jump-to.md @@ -42,11 +42,11 @@ After setting the objects, changes can be applied by calling a microflow contain ## Jumping to Other Activities in Parallel Splits or in Boundary Event Paths -Jumping to other activities has a limitation in parallel splits and in boundary event paths: it is not possible to jump into or out of a current parallel split or boundary event path. However, it is possible to jump to other activities within a current parallel split or boundary event path, including the end of the path. Also, it is possible to jump from an interrupting boundary event to its parent or grandparent path, since they are considered part of the same path. Activities in other parallel splits or boundary event paths, as well as activities outside the current path, are not available in the **System.WorkflowCurrentActivity_ApplicableTargets** association. +Jumping to other activities has a limitation in parallel splits and in boundary event paths: it is not possible to jump into or out of a current parallel split or boundary event path. However, it is possible to jump to other activities within a current parallel split or boundary event path, including the end of the path. Also, it is possible to jump from an interrupting boundary event path to its parent or grandparent path, since they are considered part of the same path. Activities in other parallel splits or boundary event paths, as well as activities outside the current path, are not available in the **System.WorkflowCurrentActivity_ApplicableTargets** association. For more information about jumping rules in a boundary event path, see the [Jump Rules](/refguide/workflow-boundary-events/#jump-rules) section in *Boundary Events*. ## Read More * [Generate Jump-To Options](/refguide/generate-jump-to-options/) -* [Apply Jump-To Option](/refguide/apply-jump-to-option/) \ No newline at end of file +* [Apply Jump-To Option](/refguide/apply-jump-to-option/)