Skip to content

Commit 80ee9cc

Browse files
authored
Merge pull request #209389 from nayenama/release08262022
rich text changes
2 parents 23f9160 + 08e0575 commit 80ee9cc

File tree

4 files changed

+57
-2
lines changed

4 files changed

+57
-2
lines changed

articles/purview/how-to-create-import-export-glossary.md

Lines changed: 50 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,46 @@ To create a new glossary term, follow these steps:
2828
3. Give your new term a name, which must be unique in the catalog. The term name is case-sensitive, meaning you could have a term called **Sample** and **sample** in the catalog.
2929

3030
4. Add a **Definition**.
31-
31+
32+
### Adding rich text to a definition
33+
34+
Microsoft Purview enables users to add rich formatting to term definitions such as adding bolding, underlining, or italicizing text. Users can also create tables, bulleted lists, or hyperlinks to external resources.
35+
36+
:::image type="content" source="media/how-to-create-import-export-glossary/rich-text-editor.png" alt-text="Screenshot that shows the rich text editor.":::
37+
38+
Below are the rich text formatting options:
39+
40+
| Name | Description | Shortcut key |
41+
| ---- | ----------- | ------------ |
42+
| Bold | Make your text bold. Adding the '*' character around text will also bold it. | Ctrl+B |
43+
| Italic | Italicize your text. Adding the '_' character around text will also italicize it. | Ctrl+I |
44+
| Underline | Underline your text. | Ctrl+U |
45+
| Bullets | Create a bulleted list. Adding the '-' character before text will also create a bulleted list. | |
46+
| Numbering | Create a numbered list Adding the '1' character before text will also create a bulleted list. | |
47+
| Heading | Add a formatted heading | |
48+
| Font size | Change the size of your text. The default size is 12. | |
49+
| Decrease indent | Move your paragraph closer to the margin. | |
50+
| Increase indent | Move your paragraph farther away from the margin. | |
51+
| Add hyperlink | Create a link in your document for quick access to web pages and files. | |
52+
| Remove hyperlink | Change a link to plain text. | |
53+
| Quote | Add quote text | |
54+
| Add table | Add a table to your content. | |
55+
| Edit table | Insert or delete a column or row from a table | |
56+
| Clear formatting | Remove all formatting from a selection of text, leaving only the normal, unformatted text. | |
57+
| Undo | Undo changes you made to the content. | Ctrl+Z |
58+
| Redo | Redo changes you made to the content. | Ctrl+Y |
59+
60+
> [!NOTE]
61+
> Updating a definition with the rich text editor adds a new additional attribute `microsoft_isDescriptionRichText": "true"` in the term payload. This attribute is not visible on the UX and is automatically populated when any rich text action is taken by user. See the snippet of term JSON message with rich text definition populated below.
62+
63+
>```json
64+
> {
65+
> "additionalAttributes": {
66+
> "microsoft_isDescriptionRichText": "true"
67+
> }
68+
> }
69+
>```
70+
3271
5. Set the **Status** for the term. New terms default to **Draft** status.
3372
3473
:::image type="content" source="media/how-to-create-import-export-glossary/overview-tab.png" alt-text="Screenshot of the status choices.":::
@@ -38,8 +77,11 @@ To create a new glossary term, follow these steps:
3877
- **Draft**: This term isn't yet officially implemented.
3978
- **Approved**: This term is official/standard/approved.
4079
- **Expired**: This term should no longer be used.
41-
- **Alert**: This term needs attention.
80+
- **Alert**: This term needs attention.
4281
82+
> [!Important]
83+
> if an approval workflow is enabled on the term hierarchy then when a new term is created it will go through the approval process and only when it is approved it is stored in catalog. See here to learn about how to manage approval workflows for business glossary [Approval workflows for business glossary](how-to-workflow-business-terms-approval.md)
84+
4385
6. Add **Resources** and **Acronym**. If the term is part of hierarchy, you can add parent terms at **Parent** in the overview tab.
4486
4587
7. Add **Synonyms** and **Related terms** in the related tab.
@@ -50,6 +92,11 @@ To create a new glossary term, follow these steps:
5092
5193
9. Select **Create** to create your term.
5294
95+
> [!Important]
96+
> if an approval workflow is enabled on term hierarchy path, you will see **Submit for approval** instead of create button. Clicking on submit for approval will trigger the approval workflow for this term.
97+
98+
:::image type="content" source="media/how-to-create-import-export-glossary/submit-for-approval.png" alt-text="Screenshot of submit for approval." border="true":::
99+
53100
## Import terms into the glossary
54101
55102
The Microsoft Purview Data Catalog provides a template .csv file for you to import your terms into your Glossary.
@@ -71,6 +118,7 @@ Notice that term names are case-sensitive. For example, `Sample` and `saMple` co
71118
> [!Important]
72119
> The system only supports importing columns that are available in the template. The "System Default" template will have all the default attributes.
73120
> However, custom term templates will have out of the box attributes and additional custom attributes defined in the template. Therefore, the .CSV file differs both from total number of columns and column names depending on the term template selected. You can also review the file for issues after upload.
121+
> if you want to upload a file with rich text definition, make sure to enter the definition with markup tags and populate the column **IsDefinitionRichText** to true in the .csv file.
74122
75123
:::image type="content" source="media/how-to-create-import-export-glossary/select-file-for-import.png" alt-text="Screenshot of the Glossary terms page, select file for Import.":::
76124

articles/purview/how-to-workflow-self-service-data-access-hybrid.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,13 @@ This guide will show you how to create and manage self-service access workflows
6464
The template has the following steps:
6565
1. Trigger when a data access request is made.
6666
1. Approval connector that specifies a user or group that will be contacted to approve the request.
67+
68+
### Assign Data owners as approvers
69+
Using the dynamic variable **Asset.Owner** as approvers in Approval connector will send approval requests to the data owners on the entity.
70+
71+
>[!Note]
72+
> Since entities may not have data owner field populated, using the above variables might result in errors if no data owner is found.
73+
6774
1. Condition to check approval status
6875
- If approved:
6976
1. Condition to check if data source is registered for [data use management](how-to-enable-data-use-governance.md) (policy)
67.3 KB
Loading
69.4 KB
Loading

0 commit comments

Comments
 (0)