SharePoint Workflows: 2010 Workflows are being retired – Are you prepared for this?

SharePoint Workflows
SharePoint Workflows

Have you been using SharePoint Workflows? Then, you must have heard by now that SharePoint 2010 Workflows are being retired.

This has been part of discussions for a while now. Microsoft has officially confirmed in early July 2020 that SharePoint Online 2010 workflows are being retired by 1st November 2020.

Couple of questions that comes to any IT Managers’ mind who is using SharePoint workflows:

What does this mean for me and my organisation?

Am I prepared for this; do I have a back-up plan to migrate from SharePoint Workflows?

So, what is actually happening with SharePoint Workflows?

Starting November 1st 2020, Microsoft will remove the ability to create or run SharePoint 2010 workflows from existing Office 365 tenants using SharePoint Online.

As part of the evolution of the Microsoft 365 service, Microsoft concluded that for SharePoint 2010 workflows, Microsoft 365 customers would be better served by modern workflow automation solutions.

Following this, SharePoint 2010 workflows have already been retired since August 1st, 2020 for new tenants. Along with that, SharePoint workflows will be removed from existing tenants by November 1st, 2020.

If your SharePoint Online site is currently using 2010 workflows anywhere, those SharePoint workflows will no longer work after November 1st.

And it doesn’t end here. Furthermore, Microsoft has indicated that SharePoint 2013 workflows will also be switched off for new Office 365 tenants. That is, from November 2020. With that, they mentioned that SharePoint 2013 workflows will follow a similar retirement path in the future.

So, if you’re going to migrate your SharePoint workflows, it would be smart to include 2013 workflows as well in your migration project.

What’s a SharePoint workflow anyway?

A SharePoint workflow is a pre-configured application that streamlines a business process. SharePoint workflows can range from collecting signatures, feedback and approvals for a document. Or, a request to tracking the current status of a routine procedure.

Overall, they are automated flows of requests through a sequence of steps that require actions or tasks from individuals. Simply, to manage a business process.

In a nutshell, workflows take care of things related to people, systems and processes. More clearly, they take care of things behind the scenes. Therefore, making your work easier and giving you time to focus on more valuable tasks.

Some of the out-of-the-box workflows that will be impacted:

  • Approval workflows: This workflow is to send an item or a specific document for approval.
  • Three-state: This workflow lets you track progress to track a high volume of issues or items, such as support issues, or project tasks.
  • Collect Feedback: This workflow is to send a document or an item to people for feedback.
  • Collect Signatures: This workflow routes a document to people to collect their signatures.

What should I do now to migrate my SharePoint workflows?

If you have been using SharePoint workflows for your business processes, there’s a couple of paths you can take.

I will focus on two of them here.

1- Migrate to Power Automate

There is Microsoft Power Automate available to you and it connects to most of the Microsoft 365 services. Subsequently, allowing you build enterprise custom workflows.

However, Microsoft Power Automate does not come as “flexible” as you might think.

It is a good solution and comes as “low-code” option for software developers to create workflow solutions with it. Power Apps borrows from app development paradigm which can be quite confusing for non-developers.

As said, you will still need to invest in software developers or expert partners. That is, to make these workflows fully reflect your unique business requirements.

If you are looking to implement end-to-end business processes you will face limitations.

For instance, you will need user licenses for multiple platforms to build end-to-end solutions. Licenses such as Power Apps, Power BI and Flow so you can you can fully leverage Power Automate.

As a result, you will incur additional costs and further integration work to make the system fully function for you.

2- Use a modern workflow automation platform to replace SharePoint workflows (like the one Kianda offers)

Second option you have, is to use a modern workflow automation platform for migrating from SharePoint workflows.

More clearly, a platform that can seamlessly integrate with SharePoint. Precisely a platform that empowers non-developers such as business users, knowledge workers to take the lead and create intuitive workflows within hours (not days or months). Connecting to your SharePoint data, 0365 users and your currently analytical systems.

workflow automation
Benefits of workflow automation

Workflow automation platform such as the one Kianda offers, is a standalone system. Meaning, the system does not require SharePoint or other Microsoft tools for it to operate. But, most importantly it can integrate seamlessly to most of the Microsoft systems.

In doing so, your cost will be based on licensing of a single platform. As well, the time your internal staff will spend on creating these workflows and successfully migrating from SharePoint workflows.

As a result, while migrating your legacy SharePoint Workflows into a modern workflow automation platform, you will also increase productivity and reduce your costs.

And let’s face it. There is not enough IT talent available. So, why not leverage your current staff who can actually be part of your IT projects such as this one.

Business users can actively create complex workflow automation solutions for your business without writing a single line of code.

Why not talk to an expert in workflow automation?

If you are looking to migrate your SharePoint workflows you can talk to our experts to discuss what options you have.

At Kianda we help business users technical or non-technical to create enterprise technology. Simply, by providing them easy-to-use no-code platform to create intuitive workflows.

Above all, Kianda seamlessly integrates with SharePoint and many other IT systems such as SAP, O365, Oracle, SQL server, File systems and more.

Talk to us today discover@kianda.com and learn how we can help you with your SharePoint Workflow migration!

Osvaldo SousaAbout Author:
Osvaldo Sousa – Enterprise collaboration and Digital process automation expert with almost two decades of experience in information technologies. He is the CEO/Co-founder of Kianda Technologies.

Automating processes – why is it so difficult?

Business Process Automation Explained (with examples)

SharePoint as an enterprise app platform together with Ember.js

Ember-SharePoint
SharePoint Enterprise Solutions

SharePoint generally is a great framework for building enterprise apps

I am not simply referring to apps built using the app model, I am referring to all the combinations of solutions that leverage services SharePoint provides. This includes client-side based solutions such as HTML5, JavaScript and traditional farm solutions.

SharePoint developers (SharePoint farm solutions developers) have been leveraging successfully of these resources to build enterprise systems for many years. This has had sometimes not so good results. Simply, due to the fact that these solutions can sometimes affect the whole SharePoint server farm. And, in a way that is detrimental to anything else running on that server farm.

The solution for this as suggested by Microsoft with the introduction of the app model is to make more use of the “platform” personality of SharePoint. This allows effectively to write code that does not run within the same process as SharePoint code does. As well, it helps to avoid (most of the times at least) the common pitfalls of SharePoint farm solutions.

From a client-side point of view. SharePoint offers a lot when it comes to resources that can be leveraged from JavaScript frameworks such as Ember or Angular.

What resources SharePoint can offer:

  • Lists
  • Document libraries
  • A robust security model
  • User profile store
  • Extensive REST API and much more…


Ember.js framework & SharePoint is the perfect marriage for building ambitious enterprise web solutions

I have been using Ember.js for a long time to deliver high standard enterprise solutions. On that note, I get asked the following obvious question many times.

Why not Angular or even ReactJS instead?

The answer to that question has many facets to it. In summary, it boils down to Ember.js being a real framework. Rather than a library being built and maintained by developers working on real life projects of their own. Moreover, any Ember.js developer can quickly become familiar to a new project. Therefore, quickly become productive, due to its heavy use of convention over configuration.

The combination of Ember.js + SharePoint enables novice and expert developers to develop highly scalable solutions. And these solutions leverage great tools like Node.js and robust systems like SharePoint. By doing so, they create a highly scalable ambitious enterprise web application.

It enables developers to dramatically reduce the amount of code they write.

At Kianda Technologies, we developed an Ember SharePoint Adapter that allows an easy development experience while building Ember apps for SharePoint. A drop of this adapter will quickly allow Ember data talk to SharePoint Lists.
 SharePoint Enterprise appsEmber SharePoint Adapter

Sample customer ordering system built in combination with SharePoint + Ember.js

Here is a good example of such use of SharePoint by employing Ember.js coupled with a few lists in SharePoint to build an order management system.

The ingredients for this hypothetical system are:

  • Two SharePoint lists (Customers and Orders with the required metadata)
  • js used to provide front-end and business logic
  • Ember SharePoint Adapter built to communicate via SharePoint JSOM / REST API to allow Ember to work with list data
  • Ember app referenced within a SharePoint page
  • A document library to host the page and its client resources

The following is sample code used in Ember app.

Ember Code Sample Customer Services

Note: In the code snippet above, SP Data represents an abstraction of the Ember Adapter, using a combination of SharePoint rest services or simply JSOM.

The advantages of building your business app this way is multiple: Easy to change and quick to adapt without lengthy deployments and the guarantee of no custom code being executed with your SharePoint process.

In conclusion; the use of a sophisticated client-side framework such as Ember.js combined with SharePoint web services can provide an ideal environment for your next business application.

About the author: Osvaldo Sousa Founder and Principal Architect of Kianda BPM (www.kianda.com) is a highly skilled engineer that held positions such as a CTO, Senior SharePoint Architect and Chief Product Architect building innovative enterprise solutions for organisations in Europe. He is considered as a SharePoint and no-code BPM expert.

Let us show you with a free live demo what Kianda can do for you.

Request your live demo

Kianda BPM sponsors European SharePoint Conference #ESPC18

European SharePoint Conference
European SharePoint Conference

Kianda BPM is delighted to announce that we are once again Silver Sponsors for the upcoming The European SharePoint, Office 365 & Azure Conference #ESPC18 takes place at The Bella Center, Copenhagen from 26-29 November 2018.

We are proud to be partnering with such a prestigious event that gathers SharePoint, Office 365 & Azure experts from around the world in one European location for the largest conference of its kind.

Check out here our sponsorship page