You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/purview/how-to-use-workflow-dynamic-content.md
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,27 @@
1
1
---
2
2
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.
4
4
author: zeinam
5
5
ms.author: zeinam
6
6
ms.service: purview
7
7
ms.subservice: purview-workflows
8
8
ms.topic: how-to #Required; leave this attribute/value as-is.
9
-
ms.date: 02/24/2023
9
+
ms.date: 02/27/2023
10
10
ms.custom: template-how-to #Required; leave this attribute/value as-is.
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.
18
18
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:
20
22
21
23
*[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.
23
25
24
26
## Built-in variables
25
27
@@ -63,11 +65,11 @@ Currently, the following variables are available for a workflow connector in Mic
63
65
64
66
## Expressions
65
67
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.
67
69
68
70
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).
69
71
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:
71
73
72
74
1. Select the value you're going to edit.
73
75
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
76
78
77
79
:::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.":::
78
80
79
-
## Considerations for using expression functions
81
+
###Considerations
80
82
81
83
* Function parameters are evaluated from left to right.
82
84
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.
84
86
85
87
The following example shows the correct and incorrect syntax:
86
88
@@ -90,7 +92,7 @@ When you're building a workflow and want to add an expression function to a valu
90
92
91
93
**OK**: `"@<function-name>('<parameter-name>')"`
92
94
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).
0 commit comments