Skip to content

Commit b5dbdc4

Browse files
committed
Add Support for Multiple Workflow Endpoints
1 parent cd80860 commit b5dbdc4

2 files changed

Lines changed: 9 additions & 5 deletions

File tree

  • content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements
  • static/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/end-event.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,18 @@ weight: 50
66

77
## Introduction
88

9-
An **End Event** in workflows defines where a workflow process ends. When the workflow execution reaches this element, the process is completed and no further actions are taken.
9+
An **End** event in workflows defines where a workflow process ends. When the workflow execution reaches this element, the process is completed and no further actions are taken.
1010

11-
A workflow can have multiple end events, as shown in the example below:
11+
A workflow can have multiple end events. Starting from Studio Pro 11.6, workflows can also terminate through any one of these end events. This means that activities with multiple outgoing paths, such as user tasks or decisions, can direct each path to its own **End** event, as shown in the example below:
1212

13-
{{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png" alt="End Event Example" width="400" >}}
13+
{{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png" alt="End Event Example" max-width=30% >}}
1414

15-
In this example, there is a decision element where the workflow can take two different paths based on a condition. Each path leads to a different end event, either of which ends the process. In addition, an interrupting boundary event is attached to one of the user tasks, which also leads to its own end event. In all of these cases, only one path will be taken, and the process ends when it reaches the corresponding end event.
15+
In the example above, there is a decision element where the workflow can take two different paths based on a condition. Each path leads to a different end event, either of which ends the process. Out of the two paths, only one path will be taken, and the process ends when it reaches the corresponding end event.
16+
17+
{{% alert color="info" %}}
18+
In Studio Pro 11.6 and below, a workflow can also have multiple end events but it is required to terminate it with a single end event at the end of the main flow.
19+
{{% /alert %}}
1620

1721
## Properties
1822

19-
The **End Event** does not have any configurable properties.
23+
The **End** event does not have any configurable properties.
5.9 KB
Loading

0 commit comments

Comments
 (0)