Skip to content

Commit 213c204

Browse files
committed
Laguage and style review
1 parent ae5218d commit 213c204

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ weight: 20
55
---
66

77
{{% alert color="info" %}}
8-
Non-interrupting boundary events were released in beta in Studio Pro 10.15 and released in GA in Studio Pro 10.16.
8+
Non-interrupting boundary events were in public beta in Studio Pro 10.15 and released in GA in Studio Pro 10.16.
99
{{% /alert %}}
1010

1111
## Introduction
@@ -82,15 +82,16 @@ With non-interrupting boundary events, the parent activity remains active/in pro
8282

8383
## Boundary Event Variables
8484

85-
With boundary events we have direct access to the values of the parent if it is either a userTask or Call Workflow. There we can get information such as DueDate about the parent, which can be used in the boundary event flow and it's expressions.
85+
Boundary events have dedicated variables that can be used to get direct access to the values of the parent activity if it is either a user ask or Call workflow activity. For example, you can get information such as the parent activity's `DueDate`, which can be used in the boundary event flow and its expressions.
86+
8687
The list of variables is described below:
8788

88-
* `$ParentTask`The parent User-Task of the attached boundary event.
89-
* `$CalledWorkflowInstance`The parent Call Workflow of the attached boundary event
89+
* `$ParentTask`the parent user task of the attached boundary event
90+
* `$CalledWorkflowInstance`the parent Call workflow activity of the attached boundary event
9091

91-
## Current Limitations
92+
## Current Limitation
9293

93-
The current release of boundary events has the following limitations which are actively being developed:
94+
The current release of boundary events has the following limitation which is actively being developed:
9495

9596
* Non-interrupting timer boundary events currently have no recurrence. They are only executed once and will not repeat.
9697

0 commit comments

Comments
 (0)