This document provides an overview of workflows in SharePoint 2013 and Office 365. It discusses the workflow architecture including the new workflow platform and topology options. It also covers creating workflows with SharePoint Designer 2013 and Visual Studio, demonstrating common workflow scenarios. Best practices for workflows are presented along with conclusions.
3. Serge Luca
Brussels
@sergeluca
Freelance, author, speaker
SharePoint MVP since 2007
With another (SQL Server) MVP : www.shareql.com
Works with SharePoint since v1 in 2002
Author of Workflow Foundation certification exam for Microsoft
About Me
10. 2 workflow platforms
SP 2013 farm Workflow FarmWorkflow Farm
SharePoint 2010
workflows
Windows
Server
SQL Server
Non supporté en SharePoint
Foundation
SharePoint 2013
workflows
Windows
Server
SQL Server
11. Workflow Farm = 1 or 3 machines (not 2, not 4,…)
• Collocated = Workflow Manager on (1 or 3 ) SP machines
• Federated = Workflow Manager farm serving multiple SharePoint Farms
• Distributed = Multiple Workflow Manager farms serving multiple
SharePoint tenants and potentially SharePoint Farms
Topologies
15. SharePoint 2013 and Workflow Service
SharingContentEvents People
SharePoint
2010 WF
_API (REST OM)
Workflow Services Manager
Service Bus
Instances Interop
Deployment Messaging
WF Service Application Proxy
Workflow
Manager
OAuth
Access
Control
WorkflowClient
16. Comparing 2010 and 2013 Workflows
SharePoint 2010 SharePoint 2013
Legacy (backward comp, i.e
upgrade)
Future
Coupled to SP servers Decoupled (other consuming
platforms)
In process Out process, on premise or
cloud (Azure if O365)
Declarative or custom code Declarative
SP Foundation and SP server SP server
Content types No*
App friendly
.Net framework used by SP
(.Net 3.51)
.Net framework xxx (.Net 4.5
today, xxx tomorrow)
18. Which Microsoft Workflow tool ?
SharePoint Designer 2013 Visual Studio 2013
Power Users, SP devs SP devs
Can use Visio No
Cannot debug Can debug, including SP online
No ALM support Full ALM support
Cannot be part of Apps Can be part of Apps
1
30. Demo 4 : calling the SharePoint REST API
(POST)
31.
32. Do your remember ?
SharePoint Designer 2013 Visual Studio 2013
Can use Visio No
Power Users, SP devs SP devs
Cannot debug Can debug, including online
No ALM support Full ALM support
Cannot be part of Apps Can be part of Apps
3
Template may not be modified
Twitter hashtag: #spsbe for all sessions
Workflow manager : former Windows Azure Workflow Server (WAS)…same code base as Windows Azure service bus
Multitenant
Rest based
.Net 4.5
Scalable reliable
Service bus is the host
Microsoft.Workflow.Client.dll
Performance: NIC (network interface configuration)
Scale SQL server first
OAuth2 between SP and WFM
App Management service must be started in SP, UPServices as well
Users must be populated in UPS, their UPN (user Principal name) must be ok : not available in SPFoundation
Monitoring packs
Disaster Recovery complicate, undocumented
Patching SP farm, you have to republish new activities to WFM, SP_registerWorkflowService- force
Service bus architecture: http://msdn.microsoft.com/en-us/library/azure/dn459033.aspx
Exemple de site workflow : un workflow qui toutes les heures affichent la liste des 5 dernières modifications de chaques listes (sorte de newsfeed)
List workflow
Collect signature http://office.microsoft.com/en-us/sharepoint-foundation-help/all-about-collect-signatures-workflows-HA102639357.aspx?CTT=5&origin=HA102420739