From b15e9660ff8c8e0f9c10bfe42c72d76e7124c80f Mon Sep 17 00:00:00 2001 From: Dima Fedorenko Date: Wed, 2 Sep 2026 14:30:13 +0200 Subject: [PATCH] Adjust Boundary Events documentation after recent changes in conflict detection there --- .../modeling/application-logic/workflows/boundary-events.md | 6 ------ .../application-logic/workflows/workflow-versioning.md | 2 -- 2 files changed, 8 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 9872e5b29ca..c94773f7a99 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 @@ -109,12 +109,6 @@ Boundary events are re-created upon interrupting behavior change because in-plac Converting an already-triggered non-interrupting boundary event to interrupting in place violates this rule: the parent activity remains in progress, resulting in an interrupting boundary event whose parent is never aborted. Conversely, converting an already-triggered interrupting boundary event to non-interrupting in place leaves it active on an already-aborted parent activity, contradicting the rule that a non-interrupting boundary event must not abort its parent. -#### Implications of Changing the Boundary Event Type - -When you change the type of an ongoing **non-interrupting** boundary event (for example, from Timer to Notification), this causes a partially resolvable [Current Activity Moved out of Path](/refguide/workflow-versioning/#current-activity-moved-out-of-path) conflict. Affected workflow instances cannot be continued. This does not apply to interrupting boundary events. - -For more information on how to handle such conflicts, see [Workaround for Non-resolvable and Partially Resolvable Conflicts](/refguide/workflow-versioning/#workaround-for-non-resolvable-and-partially-resolvable-conflicts). - ### Rearranging Boundary Events You can rearrange boundary events in the following ways: diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-versioning.md b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-versioning.md index 9da04a7f105..2dc1c17016e 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-versioning.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-versioning.md @@ -157,8 +157,6 @@ If a currently running workflow instance is executing an activity that is moved Conversely, moving an activity from a parent path into a nested scope, such as a boundary event path or a sub-process, can also prevent the workflow from progressing. In these scenarios, the Workflow Engine cannot guarantee the integrity of the execution flow. This can result in the workflow instance remaining stuck in the **In Progress** state indefinitely, preventing it from ever reaching a completed state. -This conflict can also occur when you change the type of an ongoing non-interrupting boundary event. For more information, see [Changing Boundary Event Type](/refguide/workflow-boundary-events/#changing-boundary-event-type). - You can do one of the following: * The workflow can be aborted, for example, by using the **DefaultWorkflowAdmin** page in the Workflow Commons.