On June 22nd 2017, I will again be speaking to the Cincinnati SharePoint User Group and this time around we will be discussing workflow. I will present the options for creating workflows in SharePoint and Office 365, as well as look at the process (and potential pitfalls) for upgrading your SharePoint Designer workflows to Microsoft Flow.
Microsoft announced today the newest improvement in workflow for the SharePoint platform – easy-to-use approval workflows built-in that will enable you to route a document for approval and give you the ability to give a custom message.
In my workflow presentations, I talk about having a simple approval workflow being a great first step but we need a better user experience than what we have been given out-of-the-box with SharePoint in the past. We need the user to be able to approve/deny directly within their email client, without having to go to a SharePoint page, edit the task, complete the task, and then save it. Too many steps!!
With this new functionality using Microsoft Flow, we will now be able to ad-hoc route documents for approval and approval participant will have a one-step action link in their email.
I am excited to be speaking once again at the Nashville SharePoint Users Group. The meeting on May 9th 2017 is in-person and via online meeting and the topic is “Creating & Upgrading SharePoint Workflows”. The details of my presentation are below.
For a long time, we have used workflow for automating business processes in every version of SharePoint, while using various tools to create them: out of the box workflows, SharePoint Designer, Visual Studio, & third-party applications like Nintex and K2.
Now that SharePoint Designer will no longer updated and there is a push to move to the cloud, what are we supposed to do now to automate tasks and business workflow?
What if you aren’t moving to Office 365 and just want to know what tool you should use to create workflows moving forward?
Should you migrate your existing SharePoint Designer workflows to Microsoft Flow or a third-party tool? What would that process look like?
Should you continue to build workflows using SharePoint Designer in SharePoint 2010, 2013, 2016?In our time together, we will review those questions and more so you can be confident in your path forward with process automation, no matter what version of SharePoint you are using or where it is hosted!
[UPDATE] I had a great time with the group tonight. There were some great conversation concerning the gaps between SharePoint Designer workflows and Microsoft Flow. Everyone stay tuned to this space and make sure you register for the May 16th Microsoft Virtual Summit.