When SharePoint 2013 hit the streets, it continued to run the SharePoint 2010 workflows with SharePoint’s built-in workflow engine, but it had a trick up its sleeve. Microsoft also recognized that workflows would be a big part of their burgeoning cloud platform, and they had a team working on making it as secure, resilient, and full-featured as possible. This worked well, but it was somewhat limited by what it could interact with. The workflow engine was written by the SharePoint team and was hosted on the SharePoint servers as part of SharePoint.

SharePoint 2010 continued this approach to workflows. All those workflows were being executed in the background by a workflow engine that came with SharePoint. The adventurous folks could also create workflows with code. Workflows could also be created with SharePoint Designer, the recently renamed FrontPage. It came with some simple out-of-the-box workflows, like Document Approval. SharePoint 2007 introduced us to the concept of Workflows. How did we get here? SharePoint’s relationship with workflows has been complicated. A Brief History of the SharePoint 2010 Workflows In this blog post, I’ll cover what the retirement means, how you can see if your environment is affected, and what to do if it is. Wherever you fall on the spectrum, these workflows are really getting retired, and if there’s SharePoint Online in your present or future, you’ll need to know how this impacts you. This announcement was met with various reactions, ranging from “What?” to “Are people still using SharePoint 2010 workflows? That stuff’s ten years old!” They announced in July that they would be unceremoniously stopping support for SharePoint 2010 workflows in SharePoint Online.

There have been many things to deal with this year, and Microsoft added more chaos to our already tumultuous days. Home > Blog > SharePoint > SharePoint 2010 Workflows Retirement – What Should Be Your Next Steps SharePoint 2010 Workflows Retirement – What Should Be Your Next Steps

Sharepoint 2010 use workflow as timer