Please join me on June 24th in Chattanooga, Tennessee for the third annual SQL Saturday Chattanooga! We will be discussing SharePoint BI and how Power BI brings a new level of data storytelling to collaboration.
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.
If you are using Office 365 Video to serve content within your organization, there is nothing you need to do at this time. The move to Microsoft Video will be a phased approach and Microsoft has promised that the move will include all your content and metadata.
After the transition, existing Office 365 Video embed codes and links to videos will still work, redirecting to the same content in Stream.
The full message can be viewed within your Office 365 tenant’s message center.
Originally, this post made reference to Microsoft Stream being available now. Stream will be generally available soon and another announcement will be made when it is out of preview. Sorry for any confusion the original post may have caused.
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.
For years now, power users have created solutions using Access Services within SharePoint. These solutions have often been the backbone of many business processes for small to medium-sized organizations. Now that Office 365 is widely available and is fairly cost-effective for those organizations, we have new options to solve those business needs.
Access Services & Access Web Apps shipped with SharePoint 2016 and will continue being supported as part of the SharePoint product life-cycle.
Moving forward, information workers should build their apps using PowerApps on top of SharePoint lists to give the feature-rich solutions their users need with the full on-going support of Microsoft and the tech community.