Microsoft is making overwhelming changes to the world of SharePoint Workflows. Couple of years back, they deprecated the SharePoint Workflows (Both SharePoint 2010 and 2013 styled workflows) altogether for SharePoint Online which has been already covered in detail in my other blog post referenced below
AgilePoint product and customers were able to navigate through these flurry of changes elegantly with very minimal impact due to the robust architecture of the AgilePoint’s SharePoint integration which provides a loose coupling with the SharePoint platform hence eliminating impact due to architectural changes done in the underlying SharePoint platform.
Recently, Microsoft announced that the SharePoint 2019 support is coming to an end and it is recommended that all customers should move to SharePoint Subscription Edition. However, there are few of the SharePoint services which will be deprecated in SharePoint Subscription Edition. The key ones being Microsoft Workflow Manager, SharePoint 2010 Workflows, InfoPath Form Services and SharePoint Designer 2013. If you want to read about the feature retirement timelines, please refer to the following article
We understand that these announcements will leave customer using AgilePoint NX for SharePoint On-Premises with few questions and AgilePoint has partnered closely with Microsoft to make sure there is no impact on our valued customers who rely on AgilePoint and Microsoft to manage and run their business-critical processes.
In this article, I would try to cover few commonly asked questions depending on customer’s usage of AgilePoint’ integration for SharePoint and the way forward
Customers who create SharePoint Online workflows using AgilePoint
We already have a way forward with zero impact on your already exiting workflow apps which was released late last year. None of your AgilePoint Workflow or Forms have to be touched. We just need to replace the old SharePoint app components with the new one for which we already provide an automated migration utility.
Customers who just use AgilePoint’s SharePoint Connector to read/write data from SharePoint list and libraries in SharePoint On-Premises but do not use AgilePoint Workflow for SharePoint On-Premises
This would be the case for majority of the customers who use eForms lookups, file upload and SharePoint activities in the workflow but do not have any AgilePoint Workflows for SharePoint list or libraries. There is no impact of these announcements for these features.
Customers who use AgilePoint NX SharePoint Workflow Solution for SharePoint On-Premises
As mentioned in the Microsoft’s announcement, existing Microsoft and AgilePoint customers can continue to use Microsoft Workflow Manager and SharePoint 2010 workflows till July 14 2026. There is no immediate impact for existing customers and as mentioned in the way forward section later in this article, we are already working on a solution as per new guidelines from Microsoft.
This means that existing Microsoft and AgilePoint customers can continue to use existing SharePoint Solutions and workflows till July 14 2026 and we plan to have a seamless replace of app in Q1 2026 itself which will give customers enough time to plan the deployment of new workflow trigger solution.
What is impact on the AgilePoint workflows for SharePoint On-Premises
Good News! There is no impact on any of the investments you made while creating Apps, AgilePoint eForms for SharePoint list, workflow activities and eForms lookup for SharePoint and AgilePoint workflow for SharePoint list and libraries created using AgilePoint.
AgilePoint since last two decades has always advocated the advantages of building your SharePoint workflows in a way which is loosely coupled with the underlying SharePoint Platform. While a lot Non-AgilePoint customers who use SharePoint Designer and other 3rd party workflow products to generate native SharePoint Workflow’s and forms and have to scamper to redesign these in wake of these announcements and spend millions of dollars for migration, AgilePoint customers will reap the benefits in such instances where the platform vendor makes sweeping changes in their platform but those changes do not impact any of the customer investments due to AgilePoint’s architecture.
Let’s understand this a bit more in detail. Even though you might be creating your SharePoint Workflows, Integration and List Forms replacement using AgilePoint, those do not get deployed to SharePoint. AgilePoint workflow for SharePoint list and libraries and eForms for SharePoint list are stored and executed externally on AgilePoint Server hence any changes done on the SharePoint side including version upgrades do not impact these workflows and forms. Long-Term customers have already seen these benefits over the years when they migrated from one SharePoint server version to other with no impact on AgilePoint workflows and forms.
What is impact on the AgilePoint’s own product source code
Good News! there is very minimal impact which can be handled easily. Our dependency on SharePoint 2010 Workflow and Microsoft Workflow Manager was very limited. For, AgilePoint’s own product modules like Work Center, Process Viewer or eForms which are rendered in SharePoint, there is no impact. The same SharePoint WSPs deployed will continue to work as is. All that investment we have done in the product remains intact.
Lastly, AgilePoint’s use of SharePoint 2010 styled workflow and Microsoft Workflow Manager is only limited to one single step SharePoint workflow which acts as an event listener where we use it to listen to events like Item Added or Document uploaded to call our REST endpoint to kick off a business process in AgilePoint. Once workflow is kicked off on AgilePoint side, all this SharePoint workflow does is to show the InProgress/Completed status of the AgilePoint workflow. We have never ever changed this workflow from day 1. It is literally one step. Rest of the workflow is executed on AgilePoint server. This trigger workflow can be easily migrated to a SharePoint 2013 styled workflow and use the newly recommended SharePoint Workflow Manager.
What is AgilePoint’s plan to migrate the SharePoint Trigger Workflow
Good News! AgilePoint product team has been diligently following these announcements from Microsoft and we are already working on converting this one step SharePoint 2010 styled trigger workflow to a SharePoint 2013 styled trigger workflow which we intend to make it available to all customers during Q1 2026 even though they have time till July 14 2026. This should give customers enough time to replace existing AgilePoint NX SharePoint Workflow trigger solution with the new one which is a simple process. It is just a backend change for us and does not impact any of your existing AgilePoint workflow apps. AgilePoint Professional Services team will be using an automated migration utility to remove your old SharePoint 2010 styled workflow trigger and replace it with new SharePoint 2013 styled workflow trigger and rest of your investments will be intact.
In Q1 2026, our support and services team will start working with customer’s SharePoint Admins to make this transition to new workflow trigger as seamless as possible.
Conclusion
I hope this article has addressed some of the immediate questions you may have had regarding the retirement notices for the SharePoint 2010 styled workflow and Microsoft Workflow Manager.
Please feel free to reach out to your AgilePoint account manager or support and ask a question or leave a comment below I would be more than happy to answer your query.