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
After this setting is enabled, when users upload documents to this specific library, the document’s **Approval Status** is either in:
17
17
18
18
-**Draft** (if minor and major versions are enabled) or
19
-
20
19
-**Pending** (if only the major version is enabled) state
21
20
22
21
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
32
31
The following actions occur:
33
32
34
33
1. Power Automate uses a SharePoint *trigger* when a new file is added to the library.
35
-
36
34
2.*Get file metadata* provides the *ETag* property (along with many others) required when dealing with content approvals.
37
-
38
35
a. ETag is a special identifier that identifies the specific version of that item pending approval.
39
-
40
36
3. Start an approval action:
41
-
42
37
a. Include people for approving the documents.
43
-
44
38
b. Approvers should be either **Site Owners** or **Site Members**.
45
-
46
39
c. If you are managing users in SharePoint groups, make sure approvers are part of the **Design** permission-level group.
47
-
48
40
4. If approval response is approved:
49
-
50
41
a. Set content approval status of the document to **Approved**.
51
-
52
42
b. Send an email to the document author regarding the approval along with any comments.
53
-
54
43
5. If approval response is not approved:
55
-
56
44
a. Set content approval status of the document to **Rejected**.
57
-
58
45
b. Send an email to the document author regarding the rejection along with any comments.
59
46
60
47
## Setting up the flow in Power Automate
61
48
62
49
Using the following template, create a flow in Power Automate.
63
50
64
51
1. In the SharePoint library, from the command bar, select **Automate** > **Power Automate** > **Create a flow**.
65
-
66
52
2. Next, select the template: **When a new file is added in SharePoint, complete a custom action**.
@@ -76,13 +62,9 @@ Using the following template, create a flow in Power Automate.
76
62
The content approval action requires the following entries:
77
63
78
64
- SharePoint site
79
-
80
65
- Library name
81
-
82
66
- Identifier of the item (in this case, the document ID)
83
-
84
67
- Content approval action
85
-
86
68
- Comments
87
69
88
70
To see the *ETag*, expand **Show advanced options**.
@@ -95,31 +77,21 @@ To see the *ETag*, expand **Show advanced options**.
95
77
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.
96
78
97
79
- Identifier
98
-
99
80
- Using the *Id* property from the *trigger output*
100
-
101
81
- Comments
102
-
103
82
- 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
108
85
109
86
You can now use the content approval status action to approve and reject the document based on the approval response.
110
87
111
88
The end result is that:
112
89
113
90
1. After the flow is triggered, approvers get an email to approve/reject the document with the document link.
114
-
115
91
2. Approvers can now:
116
-
117
92
a. If your email client supports Outlook-actionable messages: Approve it within the email using actionable messages if your Outlook client supports it.
118
-
119
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.
120
-
121
94
3. After approval or rejection:
122
-
123
95
a. Document creator receives an email with the approval status along with the approval comments.
0 commit comments