Skip to content

Commit 52ed3d3

Browse files
committed
Update require-doc-approval.md
Deleted explicit numbers in bullets for numbered lists... always used 1. and used indentation to create sub-bullets (let the rendering engine define the bullet numbers to use)
1 parent 47fc919 commit 52ed3d3

File tree

1 file changed

+19
-19
lines changed

1 file changed

+19
-19
lines changed

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

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -31,29 +31,29 @@ To set the content approval status of the document, with the SharePoint connecto
3131
The following actions occur:
3232

3333
1. Power Automate uses a SharePoint *trigger* when a new file is added to the library.
34-
2. *Get file metadata* provides the *ETag* property (along with many others) required when dealing with content approvals.
35-
a. ETag is a special identifier that identifies the specific version of that item pending approval.
36-
3. Start an approval action:
37-
a. Include people for approving the documents.
38-
b. Approvers should be either **Site Owners** or **Site Members**.
39-
c. If you are managing users in SharePoint groups, make sure approvers are part of the **Design** permission-level group.
40-
4. If approval response is approved:
41-
a. Set content approval status of the document to **Approved**.
42-
b. Send an email to the document author regarding the approval along with any comments.
43-
5. If approval response is not approved:
44-
a. Set content approval status of the document to **Rejected**.
45-
b. Send an email to the document author regarding the rejection along with any comments.
34+
1. *Get file metadata* provides the *ETag* property (along with many others) required when dealing with content approvals.
35+
- ETag is a special identifier that identifies the specific version of that item pending approval.
36+
1. Start an approval action:
37+
- Include people for approving the documents.
38+
- Approvers should be either **Site Owners** or **Site Members**.
39+
- If you are managing users in SharePoint groups, make sure approvers are part of the **Design** permission-level group.
40+
1. If approval response is approved:
41+
- Set content approval status of the document to **Approved**.
42+
- Send an email to the document author regarding the approval along with any comments.
43+
1. If approval response is not approved:
44+
- Set content approval status of the document to **Rejected**.
45+
- Send an email to the document author regarding the rejection along with any comments.
4646

4747
## Setting up the flow in Power Automate
4848

4949
Using the following template, create a flow in Power Automate.
5050

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

5454
![File add custom action](../../../images/new-file-custom-action.png)
5555

56-
3. Add the actions as described in the previous steps.
56+
1. Add the actions as described in the previous steps.
5757

5858
![Flow content approval full](../../../images/promoted-state.png)
5959

@@ -88,11 +88,11 @@ You can now use the content approval status action to approve and reject the doc
8888
The end result is that:
8989

9090
1. After the flow is triggered, approvers get an email to approve/reject the document with the document link.
91-
2. Approvers can now:
92-
a. If your email client supports Outlook-actionable messages: Approve it within the email using actionable messages if your Outlook client supports it.
93-
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.
94-
3. After approval or rejection:
95-
a. Document creator receives an email with the approval status along with the approval comments.
91+
1. Approvers can now:
92+
- If your email client supports Outlook-actionable messages: Approve it within the email using actionable messages if your Outlook client supports it.
93+
- 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.
94+
1. After approval or rejection:
95+
- Document creator receives an email with the approval status along with the approval comments.
9696

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

0 commit comments

Comments
 (0)