|
| 1 | +--- |
| 2 | +title: Workflow dynamic content |
| 3 | +description: This article describes how to use connectors in Purview dynamic content |
| 4 | +author: zeinam |
| 5 | +ms.author: zeinam |
| 6 | +ms.service: purview |
| 7 | +ms.subservice: purview-workflows |
| 8 | +ms.topic: how-to #Required; leave this attribute/value as-is. |
| 9 | +ms.date: 11/11/2022 |
| 10 | +ms.custom: template-how-to #Required; leave this attribute/value as-is. |
| 11 | +--- |
| 12 | + |
| 13 | +# Workflow dynamic content |
| 14 | + |
| 15 | +[!INCLUDE [feature-in-preview](includes/feature-in-preview.md)] |
| 16 | + |
| 17 | +You can use dynamic content inside Microsoft Purview workflows to associate certain variables in the workflow. |
| 18 | + |
| 19 | +## Current workflow dynamic content |
| 20 | + |
| 21 | +Currently, the following dynamic content options are available for a workflow connector in Microsoft Purview: |
| 22 | + |
| 23 | +|Prerequisite connector |Built-in dynamic content |Functionality | |
| 24 | +|---------|---------|---------| |
| 25 | +|When data access request is submitted |Workflow.Requestor |The requestor of the workflow | |
| 26 | +| |Workflow.RequestRecepient |The request recipient of the workflow | |
| 27 | +| |Asset.Name |The name of the asset | |
| 28 | +| |Asset.Description |The description of the asset | |
| 29 | +| |Asset.Type |The type of the asset | |
| 30 | +| |Asset.FullyQualifiedName |The fully qualified name of the asset | |
| 31 | +| |Asset.Owner |The owner of the asset | |
| 32 | +| |Asset.Classification |The display names of classifications of the asset | |
| 33 | +| |Asset.Certified |The indicator of whether the asset meets your organization's quality standards and can be regarded as reliable | |
| 34 | +|Start and wait for an approval |Approval.Outcome |The outcome of the approval | |
| 35 | +| |Approval.Assigned To |The IDs of the approvers | |
| 36 | +| |Approval.Comments |The IDs of the approvers | |
| 37 | +|Check data source registration for data use governance |DataUseGovernance |The result of the data use governance check| |
| 38 | +|When term creation request is submitted |Workflow.Requestor |The requestor of the workflow | |
| 39 | +| |Term.Name |The name of the term | |
| 40 | +| |Term.Formal Name |The formal name of the term | |
| 41 | +| |Term.Definition |The definition of the term | |
| 42 | +| |Term.Experts |The experts of the term | |
| 43 | +| |Term.Stewards |The stewards of the term | |
| 44 | +| |Term.Parent.Name |The name of parent term if exists | |
| 45 | +| |Term.Parent.Formal Name |The formal name of parent term if exists | |
| 46 | +|When term update request is submitted <br> When term deletion request is submitted | Workflow.Requestor |The requestor of the workflow | |
| 47 | +| |Term.Name |The name of the term | |
| 48 | +| |Term.Formal Name |The formal name of the term | |
| 49 | +| |Term.Definition |The definition of the term | |
| 50 | +| |Term.Experts |The experts of the term | |
| 51 | +| |Term.Stewards |The stewards of the term | |
| 52 | +| |Term.Parent.Name |The name of parent term if exists | |
| 53 | +| |Term.Parent.Formal Name |The formal name of parent term if exists | |
| 54 | +| |Term.Created By |The creator of the term | |
| 55 | +| |Term.Last Updated By |The last updator of the term | |
| 56 | +|When term import request is submitted |Workflow.Requestor |The requestor of the workflow | |
| 57 | +| |Import File.Name |The name of the file to import | |
| 58 | + |
| 59 | +## Next steps |
| 60 | + |
| 61 | +For more information about workflows, see these articles: |
| 62 | + |
| 63 | +- [Workflows in Microsoft Purview](concept-workflow.md) |
| 64 | +- [Approval workflow for business terms](how-to-workflow-business-terms-approval.md) |
| 65 | +- [Manage workflow requests and approvals](how-to-workflow-manage-requests-approvals.md) |
0 commit comments