Introduction to SharePoint On-Prem
Architecture & Setup
Site Management
Lists & Libraries
Pages & Content
Permissions & Security
Search & Navigation
Automation & Workflows
Integration & Extensibility
Development & Customization
Administration & Governance
Migration & Upgrades
Compliance & Records Management
SharePoint 2010/2013 Workflow Engine
SharePoint on-premises provided a powerful way to automate business processes using its built-in workflow engines. The platform had two main versions: the older SharePoint 2010 workflow engine and the more modern SharePoint 2013 workflow engine.
SharePoint 2010 Workflow Engine
The SharePoint 2010 workflow engine was the first major workflow platform for SharePoint. It was a component of the core SharePoint product, meaning it was installed and ran directly on the SharePoint servers. This engine was used to create simple, step-by-step processes like document approvals. Workflows were created using a tool called SharePoint Designer. While it was a solid tool for basic automation, its reliance on the main SharePoint server meant that complex workflows could sometimes affect the performance of the entire farm.
SharePoint 2013 Workflow Engine
The SharePoint 2013 workflow engine was a major improvement and a separate product. It runs on its own dedicated server called Workflow Manager. This separation was a significant change because it meant that the workflow engine could handle more complex, larger workflows without slowing down the main SharePoint farm. This new engine was more robust and reliable and made it possible to build workflows that could interact with external systems and services.
Key Differences
The main difference between the two engines is their architecture. The 2010 engine was a simple, built-in tool that was easy to use but limited in scale. The 2013 engine, with its separate server, was more powerful and reliable, making it suitable for more advanced business processes. While these engines were a powerful way to automate, many companies are now moving to cloud-based solutions like Power Automate for greater flexibility.
Table of Contents
