Skip to content

Commit 47fc919

Browse files
committed
Update require-doc-approval.md
Fixed spacing between bullets and number sets.
1 parent 89b6d87 commit 47fc919

File tree

1 file changed

+2
-30
lines changed

1 file changed

+2
-30
lines changed

docs/business-apps/power-automate/guidance/require-doc-approval.md

Lines changed: 2 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,6 @@ Settings > Versioning settings > Require content approval for submitted items
1616
After this setting is enabled, when users upload documents to this specific library, the document’s **Approval Status** is either in:
1717

1818
- **Draft** (if minor and major versions are enabled) or
19-
2019
- **Pending** (if only the major version is enabled) state
2120

2221
You can always visit the document library to approve and reject documents but this exercise is tedious. It requires receiving notifications about the pending document(s), finding the appropriate document(s) for approval, then identifying approvers, and finally generating the command to approve/reject the document(s).
@@ -32,37 +31,24 @@ To set the content approval status of the document, with the SharePoint connecto
3231
The following actions occur:
3332

3433
1. Power Automate uses a SharePoint *trigger* when a new file is added to the library.
35-
3634
2. *Get file metadata* provides the *ETag* property (along with many others) required when dealing with content approvals.
37-
3835
a. ETag is a special identifier that identifies the specific version of that item pending approval.
39-
4036
3. Start an approval action:
41-
4237
a. Include people for approving the documents.
43-
4438
b. Approvers should be either **Site Owners** or **Site Members**.
45-
4639
c. If you are managing users in SharePoint groups, make sure approvers are part of the **Design** permission-level group.
47-
4840
4. If approval response is approved:
49-
5041
a. Set content approval status of the document to **Approved**.
51-
5242
b. Send an email to the document author regarding the approval along with any comments.
53-
5443
5. If approval response is not approved:
55-
5644
a. Set content approval status of the document to **Rejected**.
57-
5845
b. Send an email to the document author regarding the rejection along with any comments.
5946

6047
## Setting up the flow in Power Automate
6148

6249
Using the following template, create a flow in Power Automate.
6350

6451
1. In the SharePoint library, from the command bar, select **Automate** > **Power Automate** > **Create a flow**.
65-
6652
2. Next, select the template: **When a new file is added in SharePoint, complete a custom action**.
6753

6854
![File add custom action](../../../images/new-file-custom-action.png)
@@ -76,13 +62,9 @@ Using the following template, create a flow in Power Automate.
7662
The content approval action requires the following entries:
7763

7864
- SharePoint site
79-
8065
- Library name
81-
8266
- Identifier of the item (in this case, the document ID)
83-
8467
- Content approval action
85-
8668
- Comments
8769

8870
To see the *ETag*, expand **Show advanced options**.
@@ -95,31 +77,21 @@ To see the *ETag*, expand **Show advanced options**.
9577
You must ensure you enter the correct site and library name. However, you can get the rest of the values from the previous actions in the flow.
9678

9779
- Identifier
98-
9980
- Using the *Id* property from the *trigger output*
100-
10181
- Comments
102-
10382
- Using the *comments* property from the *approval response*
104-
105-
- ETAG
106-
107-
- Using the *ETag* property from the *Get file metadata* action output
83+
- ETAG
84+
- Using the *ETag* property from the *Get file metadata* action output
10885

10986
You can now use the content approval status action to approve and reject the document based on the approval response.
11087

11188
The end result is that:
11289

11390
1. After the flow is triggered, approvers get an email to approve/reject the document with the document link.
114-
11591
2. Approvers can now:
116-
11792
a. If your email client supports Outlook-actionable messages: Approve it within the email using actionable messages if your Outlook client supports it.
118-
11993
b. If your email client does not support Outlook-actionable messages: Select **Approve** or **Reject** that takes you to Power Automate site where you can approve or reject the document.
120-
12194
3. After approval or rejection:
122-
12395
a. Document creator receives an email with the approval status along with the approval comments.
12496

12597
![Email approval status](../../../images/email-approval-status.png)

0 commit comments

Comments
 (0)