Postope Designer 2010 Workflow Engine Retirement
On 6th July 2020, it was suddenly announced that SharePoint 2010 workflow engine is going to stop working by November 2020.
For at least a few of my clients it will represent a catastrophe.
Our suggestion is to push back the retirement date to a more reasonable date. For example, match if with SharePoint Designer 2013 support lifecycle or with InfoPath support lifecycle.
Large organizations depend on clear sunsetting timelines. Announcement that leaves them only four months to react is completely unrealistic. Organizations need to plan resources, budget, hire SharePoint SME’s and involve business owners that rely on these workflows and much more.
Reasons for postponement:
- The clients were not properly warned about the Workflows retirement.
- There are SPO tenants with thousands SharePoint 2010 Workflows running with no direct path of quick replacement.
- Not all Workflow 2010 can be replaced with Workflow 2013 engine or Power Automate because of features differences.
- Many Clients do not have enough time and resources to replace the existing workflows.
- Pandemic is still not over and this announcement feels very out of place.
Denis Molodtsov
shared this idea
AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
We’ve been working one on one with customers deeply impacted by this change and encourage people to reach out to support if they have special circumstances. However, we wanted to provide clarity that our policy will not be changing and our previously communicated timelines will continue. In that regard, we will be retiring 2010 Workflows on November 1st, 2020 in SharePoint Online. After November 1st, 2020, while existing 2010 workflows will stop to run, users can still open and view their workflows in SharePoint Designer. Please visit the following link to get the latest updates about the 2010 Workflows retirement: https://aka.ms/sp-workflows-support.
181 comments
Comments are closed-
Jason Dozier
commented
We spoke with our TAM and Sales Representative, basically told they have no control over the product team and we should express our feedback here. I expressed concern over enabling PowerAutomate company wide because of governance issues and they provided some documentation for setting up governance for the PowerPlatform, which will of course require us to invest in some more premium licenses. Got to love one of the richest companies in the history of the world yanking the carpet out from under their customers feet then extorting them for more money.
I think the take away here is don't trust Microsoft with enterprise processes. They are not reliable and do not care about their customers. We are an ATM for extracting funds, nothing more.
-
Phil Silvio
commented
Is Microsoft even listening to their customers? 1300 votes for this item and no response. I have gone into admin center as suggested and disliked the message. I have also put in a ticket asking for an extension, which they came back and made me fill out business impact statement. Maybe if we inundate Microsoft with requests and comments they will finally get the hint.
-
Peace BeUponYou
commented
Please provide feedback also through Admin portal> message center. Look for MC217999, dislike and provide your feedback.
When contacted our Microsoft Technical Account Manager (TAM), they also suggested to create professional service ticket with the concerns. -
Anonymous
commented
The notification came too late from MS. Not possible to implement this change in this short duration.
-
Please postpone! This deadline is very unreasonable to ask of organizations, we need time to plan and implement!
-
Anonymous
commented
Postpone this Microsoft - we have critical processes running on SPD2010 some created specifically to handle the pandemic. If Power Automate cannot mimic the functionality then we cannot migrate yet simple as...
please reconsider and postpone this - also this coming at this time is causing a lot of organizations additional stress trying to put together a crisis migration team in tight deadlines which are not possible to achieve
-
Ken L
commented
We need at least a year to get our 2010 Workflows converted to something else. Either that or we will need to migrate our SPO sites back to on-premises SharePoint.
-
Erez Nir
commented
Let me blunt.
This is an infuriating idea. Technologies pitched by Microsoft, cannot be trusted to be there for the long haul. Completely overlooking what CIOs are trying to put in place for their companies. We are looking for a somewhat coherent architecture of an enterprise offering for our users and at a reasonable price. This is being ignored with such a decision. This will be driving us to figure out a way around Microsoft products and services.
I have to admit, I loved the fact I could get an integrated solution but I do not like how we are being treated as customers. We expect to be treated diffidently.
Microsoft needs to postpone this no doubt!
-
David Nelson
commented
This is not sufficient notice to remove a key component of our legacy sites. Please delay this plan.
-
jon vander zand
commented
Please Delay !
No one liked 2013 workflow. 2010 works great and easy to use !
Power automate has a learning curve and lots new conditions syntax.
Need time to learn it. Anyone that has a path to you tube tutorials please post. -
Erica Johnson
commented
please Delay!
-
Anonymous
commented
This announcement seems sudden and the deadline provided to be much too close to the timing of the announcement.
We're still trying to untangle the web of new tools (Power Apps, Power Automate, Microsoft Flow, Forms, etc.) provided by Microsoft, and trying to figure out whether any of them will be the solution we need to convert dozens of our forms and workflows.
With all that we have on our plates at the moment during the pandemic, this is not something we have the resources to jump into and convert all of our forms and workflows at this time.
We respectfully request Microsoft reconsider this strategy and adjust your timelines accordingly.
-
Anonymous
commented
Postpone this! You extended server 2010 due to the pandemic, why push this now?? This is not an adequate amount of time to communicate a deprecation of a product. We have thousands of 2010 workflows alone. This is not feasible for organizations to adequately plan and execute this change. Shame on you
-
Wayne Hill
commented
To short of a runway to take action needs to be delayed.
-
Aaron365
commented
PostPwned
-
miles loretta
commented
There's almost no way to convert the workflows in time for the EOL.
-
Anonymous
commented
We have over 1000 SP2010 workflows, with a good portion being highly critical apps for business and mfg processes. There is a high cost to the business for this conversion just in people/time/resources/hours to make these conversions. Not to mention the added cost if Power Automate requires purchase of additional connector functionality, as well as, PA not have similar functionality as in SP2010, so what do we do then? It begs to ask why the SP 2010 workflows cannot be deprecated within same timeline as the SP 2013 workflows (year 2026). People are dealing with the Covid-19 impact and this is causing an extreme burden on your customers that are already trying to mitigate the financial impact of Covid-19. Please take note of this and if possible extend the SP 2010 workflow deprecation timeline by at least one year. Thank you.
-
Joyce Slavik
commented
Please postpone
-
Janet Zeleny
commented
We need more time - 3 months is not enough notice. We have over 1400 workflows that need to be transitioned. 400 are part of an InfoPath form process, so that complicates it even further.
-
imoors
commented
This is not acceptable for us. We have to change lot's of worklfows in a relative short time. This costs a lot of money and time.
Please postpone !
