Skip to content

Commit f846713

Browse files
committed
Language updates
1 parent 7ae9637 commit f846713

File tree

1 file changed

+12
-10
lines changed

1 file changed

+12
-10
lines changed

articles/purview/how-to-use-workflow-dynamic-content.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,27 @@
11
---
22
title: Workflow dynamic content
3-
description: This article describes how to use dynamic content like built-in variables and expressions in Microsoft Purview workflows.
3+
description: This article describes how to use dynamic content to create expressions with built-in variables and functions in Microsoft Purview workflows.
44
author: zeinam
55
ms.author: zeinam
66
ms.service: purview
77
ms.subservice: purview-workflows
88
ms.topic: how-to #Required; leave this attribute/value as-is.
9-
ms.date: 02/24/2023
9+
ms.date: 02/27/2023
1010
ms.custom: template-how-to #Required; leave this attribute/value as-is.
1111
---
1212

1313
# Workflow dynamic content
1414

1515
[!INCLUDE [feature-in-preview](includes/feature-in-preview.md)]
1616

17-
You can use dynamic content inside Microsoft Purview workflows to associate certain variables in the workflow or add expression functions to process values.
17+
You can use dynamic content inside Microsoft Purview workflows to associate certain variables in the workflow or add other expressions to process these values.
1818

19-
Currently available are:
19+
When you add dynamic content to your workflows, you're building expressions from provided building blocks that reference and process information in your workflow so you can get the values you need in real-time.
20+
21+
In the dynamic content menu, the currently available options are:
2022

2123
* [Built-in variables](#built-in-variables) - variables that represent values coming to the workflow from the items that triggered it
22-
* [Expressions](#expressions) - an expression is a formula, built from functions and variables that can process values in-workflow.
24+
* [Expressions](#expressions) - formulas built from functions and variables that can process values in-workflow.
2325

2426
## Built-in variables
2527

@@ -63,11 +65,11 @@ Currently, the following variables are available for a workflow connector in Mic
6365

6466
## Expressions
6567

66-
Workflow definitions in Microsoft Purview allow you to use expression functions to process values in your workflows.
68+
Workflow definitions in Microsoft Purview allow you to use functions in your expressions to process values in your workflows.
6769

6870
To find functions [based on their general purpose](#ordered-by-purpose), review the following tables. Or, for detailed information about each function, see the [alphabetical list](#alphabetical-list).
6971

70-
When you're building a workflow and want to add an expression function to a value, follow these steps:
72+
When you're building a workflow and want to add a function to your expressions, follow these steps:
7173

7274
1. Select the value you're going to edit.
7375
1. Select the **Add dynamic content** button that appears underneath the textbox.
@@ -76,11 +78,11 @@ When you're building a workflow and want to add an expression function to a valu
7678

7779
:::image type="content" source="./media/how-to-use-workflow-dynamic-content/use-expressions.png" alt-text="Screenshot showing a workflow text field with Use dynamic content highlighted and the expressions tab shown.":::
7880

79-
## Considerations for using expression functions
81+
### Considerations
8082

8183
* Function parameters are evaluated from left to right.
8284

83-
* Function expressions that appear inline with plain text require enclosing curly braces ({}) to use the expression's interpolated format instead. This format helps avoid parsing problems. If your function expression doesn't appear inline with plain text, no curly braces are necessary.
85+
* Functions that appear inline with plain text require enclosing curly braces ({}) to use the expression's interpolated format instead. This format helps avoid parsing problems. If your function expression doesn't appear inline with plain text, no curly braces are necessary.
8486

8587
The following example shows the correct and incorrect syntax:
8688

@@ -90,7 +92,7 @@ When you're building a workflow and want to add an expression function to a valu
9092

9193
**OK**: `"@<function-name>('<parameter-name>')"`
9294

93-
The following sections organize functions based on their general purpose, or you can browse these functions in [alphabetical order](#alphabetical-list).
95+
The following sections organize functions based on their [general purpose](#ordered-by-purpose), or you can browse these functions in [alphabetical order](#alphabetical-list).
9496

9597
<a name="ordered-by-purpose"></a>
9698
<a name="string-functions"></a>

0 commit comments

Comments
 (0)