There are many features that you get access to when you use a document management application like SharePoint that you just don’t have in a server file share. One of them is the ability for the owner of a file to be notified when a change has been made to the file. This is especially useful for official corporate documents or templates, for example. SharePoint has had the document approval feature for many years, but it has always been cumbersome. The process involved visiting the document library, looking at the properties of a file, going to the “more” option, then “approvals,” then approving the change. If you were managing any more than a small handful of files with infrequent changes, it would become a hated task in short order. An improvement to this process was needed, and now we have one in Microsoft Flow.
Here’s what the old process looked like before using Microsoft Flow. It was an “Old McDonald’s Farm” situation. (With a click-click here and a click-click there, here a click, there a click, everywhere a click-click.) Imagine staff in a company moving their mouse through the procedure below for each and every document change that came their way! (Those completely unfamiliar with Flow can check out this tutorial from Microsoft.)
A much easier email-based approval method
When a document is saved after being edited, you receive an informative email letting you know which file has been changed, where it resides, who edited it, and a link to the file so you can review it. No one will see the change until you take action. When you are ready you can hit the “approve” or “reject” button.
If you reject the change, you’ll find out that you don’t get an opportunity to send a notice to the person that it’s been rejected. In fact, they’ll never know. The only person that knows is you. This is obviously a problem that will need to be addressed.
After you’ve approved (or rejected) the file, the content of the email changes, so if you’re later browsing through your email you aren’t left to wonder whether you handled the request yet or not.
Here’s how you implement ‘approvals’ via email
Make a library that requires approvals. Kind of an obvious step, but as a reminder, this is where you perform that task. You will find it under “list settings, versioning settings.” Choose the radio button “yes” under “require content approval for submitted items?” You can also select other options to retain the item’s previous versions, set who can see unapproved or draft items, and set the check-out requirement. None are required for the approval process, though.
Back in the document library, click “flow,” “add a new flow from templates” and “see more templates.” Select “start approval when a new item is added,” as seen below.
Open the Flow and immediately click the link at the bottom to go into “advanced” mode. In advanced mode, we’re going to be able to customize the email to add some critical information that will allow the approver to make an intelligent decision. It should look like the figure below.
The diagram that you now see before you is the step through flow chart of how Flow is going to work. Start at the top providing it the information that it needs.
When a new item is created, it asks for the site access and list name. Using the drop-down box you should be able to select the site and list you want to use this Flow on. If it doesn’t find it, don’t use the manual entry option. It won’t work. You’ll need to check to make sure that the account you’re operating under has admin permission to the library. Then come back and try again.
“Start an approval” asks for some basic information. The “item link” and “item link description” are called dynamic content and correspond to the fields you have configured in your list or library.
Now here is where it gets interesting. Remember at the top of this article where I mentioned that the person who edited the article doesn’t get an email letting them know that you’ve approved or rejected it? Well, we have the option to include that in this Flow. It’s in the “condition.” You’ll want to click “edit” to customize the email that they will receive. See the figure below for some suggestions
That’s it! Your Flow is ready to go, but it won’t start working right away. I don’t have a reason for this other than it’s in the queue for processing at Microsoft but it will take an hour, almost exactly in my testing, for the Flow to become active and start to work. So hold off on your testing, go to lunch or something, and when you get back it’s ready to test.
Convert Microsoft Flow into a Team Flow
One more thing about Microsoft Flow that you need to know. The account that you just used to create the Flow is the owner of that Flow. If that account goes away, so do the Flows configured under it. To prevent the loss of this Flow you will want to convert it into a Team Flow.
It’s a simple process. All you need to do is invite someone else to the Flow. Click on the “people” icon next to the Flow. Then enter their name to add them.
The process that I’ve developed is that as soon as I’m ready to declare that a Flow is in production, I add another team member. Those in-production Flow then move over to the Team Flows tab in Flow. The rest of the Flows that I’m still working on are under My Flows. Here we see my Team Flows.
Microsoft Flow is the powerful tool that SharePoint administrators have been waiting for. Previously, this kind of functionality was the expensive purview of developers, but now admins have a great deal of power to bring solutions to long-standing problems or annoyances to the businesses they support. Being able to bring solutions to the business groups is what makes one admin outshine another, and businesses out-compete their competition.