Skip to content

Adjust Boundary Events documentation after recent changes in conflict detection there #11857

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dfedorenko wants to merge 1 commit into
base: development
Choose a base branch
from
Open

Adjust Boundary Events documentation after recent changes in conflict detection there #11857

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
2 changes: 0 additions & 2 deletions ...nt/en/docs/refguide/modeling/application-logic/workflows/workflow-versioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down