SharePoint 2010, InfoPath, and SharePoint Designer are nearing end of life. What should you do? In this session we discussed the technology decisions and announcements from Microsoft.
3. 3
AT-A-GLANCE
Perficient Profile
Alliance partnerships
with major tech
vendors
Multiple vendor &
industry tech and
growth awards
Global delivery
centers in China,
India and Mexico
Dedicated
solution
practices
35
Global Locations
$565M
2019 Revenue
1997
Founded in
~4,500
Colleagues
~90%
Repeat Business Rate
PRFT
Public, NASDAQ
4. 4
As a Gold-Certified, award-winning Microsoft partner
and one of just a handful of National Solution
Providers, we are a recognized cloud expert that has
taken more than 6 million users to Microsoft Cloud.
But that’s just part of the story.
Industries We Serve
• Healthcare
• Life Sciences
• Financial Services
• Automotive
• Retail
Solution Expertise
2020 Microsoft Health
Innovation Award
Global NSP Partner
FastTrack Ready
20+ Years of Experience
Certified Cloud Consultants
Deployments
85
2000+
Gold-Certified National Solution Provider
Cloud Transformation
Dynamics CRM
M365 Deployment &
Migration
Power
Platform
Modern Intranet Teams Meetings, Calling &
Collaboration
Tenant-to-tenant
Migration
6. 6
Agenda
• Microsoft Announcement: SharePoint 2010 Workflow
• Microsoft COE Starter Kit
• Perficient Approach
• Analysis of Modernization: SharePoint 2010/2013 Workflows & Power Platform
7. 7
Simplified Announcements from Microsoft
Date Action
AUG 1, 2020 SharePoint 2010 workflows Blocked for NEW tenants
NOV 1, 2020 SharePoint 2013 workflow turned off for NEW tenants
NOV 1, 2020 SharePoint 2010 workflow turned off for ALL tenants
FEB 1, 2021 SharePoint 2010 workflow turned off for ALL tenants
* All dates are the beginning of when they start to turn disable or block or remove.
8. 8
Old and Crusty – New Hotness
SharePoint Designer
Site and Process Designer
InfoPath
Forms Designer
Old and Crusty
New Hotness
Third Party
Enhancements
10. 11
Maker Culture and Movement…
Maker movement
The maker culture represents a technology-
based movement of DIY culture intersecting with
geek culture and revels in the creation of
inexpensive clever new inexpensive solutions
based on distributed, democratized tools.
16. 17
Overview
Implementing a Power Platform COE:
• Envisioning
• Legacy application assessment
• Program definition
• Governance
• Scheduling & backlog
• Application support planning
17. 18
Review existing legacy solutions and legacy application Power Platform candidates
Work with admins to confirm and supplement the application information
Work with admins and stakeholders to establish a plan for interviewing application owners
Categorize the applications and meet with application owners
Finalize the assessment and categorization
Envision
Existing
Application
Assessment
Program
Definition
Implement
Governance
Schedule &
Backlog
Application
Support
18. 19
SharePoint Workflow 2010 & 2013 End of Life
The story in a nutshell: If you’re online, consider rebuilding workflows in Power Automate ASAP – on premises has more time.
Aug 2020
•SharePoint 2010 workflows will be turned off for new SharePoint Online tenants.
•SharePoint 2013 workflows will be *blocked* on new SharePoint Online Tenants including SharePoint Designer.
Nov 2020
•SharePoint 2010 workflows *block* ability to run or create from existing tenants, download by exception.
•New SharePoint 2013 workflows *blocked* for existing SPO Tenants (existing WF supported, but deprecated).
•Existing SharePoint 2013 workflows will be turned off by default in new tenants. (PowerShell script by exception).
Feb 2021
•SharePoint 2010 workflow services will be completely removed from all tenants.
July 2026
•SharePoint Designer 2013 created workflows will continue to be supported with SharePoint 2016 and SharePoint 2019 (on
premises).
References: (As of 7/8/2020)
Announcement: https://aka.ms/sp-workflows-update
Support: https://aka.ms/sp-workflows-support
Migration Guidance: https://aka.ms/sp-workflows-guidance
@joeloleson
Perficient.com
Collabshow.com
19. 20
Download & Run
Modernization Scanner
https://bit.ly/wfscanner
Find All SP 2010 & 2013
Workflows
Upgradability Score
Usage & History
To Filter
Candidate Workflows
Go/No Go
Decisions
(Hire vs. Build)
Create New Power
Automate Flows
DIY 3-part series on Modernization Scanner: https://www.toddklindt.com/FindO365Workflows
20. 21
Analysis of SharePoint Workflows
SharePoint
Modernization
Scanner
Workflow
Report XLS
Business
Value
Assignment
Upgradability
Score+
Removal
23. 24
Power Automate Third Party Considerations
•Flow needs to call itself to restart the clock ticking30-day run limit for flows
•Limited to 8 levels in the nested IF statement in flowIf statement limit
•If flows use this premium connector, create a “service account” to consolidateHTTP connector
•While there is not a flow action to accomplish this, it is possible to do it with an HTTP callCustom permissions
•There is no reusable workflow concept as they are item-centricReusable flows
•Looping commands are limited to 5000 items/iterations without premium licensingLooping limited
•Flow history context is differentWorkflow history storage
•SharePoint 2010 workflows impersonation not possible. Flows run under user creator context.Impersonation
•Evaluate external data sources as they may require premium licensingPremium connectors
•Flow-based modification notification may execute multiple times with modern editingModified trigger
Perficient has been a Microsoft Gold Partner since its inception in 1997. We are a National Service Provider (NSP) with Microsoft (1 of 36 in the US). The company has earned the status of Microsoft Partner of the Year on either the regional or national level over 10 times in the past 12 years. We are also a member of the following programs:
SharePoint Partner Advisory Council (PAC) - (1 of 16)
Office 365 Partner Advisory Council (PAC) – (1 of 16)
SharePoint Business Applications Program (1 of 20)
SharePoint Content Services Program (1 of 14)
Microsoft FastTrack Ready Program (Top 1% of Microsoft Partners)
M365 Partner-Customer Success Management Program (P-CSM) – (6 members)
Joel
Scan the legacy source if possible.
Categorize- Are the applications still in use? If we cannot tell from the scan send a survey? Identifying application owners is typically a problem at first.
Group by complexity, business criticality, what type of solutions. Some outliers may spin off to be custom apps.
The retirement of SP2010 workflows is an example. Joel will walk through assessment steps.