5.4swiss_sharepoint_club_mvp_track4_workflows-sharepoint_2013_serge_luca_shareql.com
Download as PPTX, PDF•1 like•433 views
This document provides an overview of the SharePoint 2013 workflow platform presented by Serge Luca, a SharePoint MVP. It compares the 2010 and 2013 workflow platforms, discusses the different workflow topologies, and demonstrates creating workflows using SharePoint Designer 2013 and Visual Studio 2013. Key points include that 2013 workflows are decoupled and run outside of SharePoint, there are different workflow topologies like co-located, federated and distributed, and Visual Studio is better for debugging while SharePoint Designer is better for power users.
5.4swiss_sharepoint_club_mvp_track4_workflows-sharepoint_2013_serge_luca_shareql.com
- 1. Serge Luca @sergeluca SharePoint MVP Brussels Overview of the SharePoint 2013 workflow platform
- 2. About Me 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 certification exam
- 4. Agenda Introduction Workflow Architecture Creating workflows with SharePoint Designer 2013 Creating workflows with Visual Studio Conclusions Q&A
- 5. Introduction SharePoint client object model (CSOM, REST) Office and SharePoint Store Workflow Access services Apps et cloud app model Search Workflows
- 6. 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* No Apps App friendly .Net framework used by SP (.Net 3.51) .Net framework xxx (.Net 4.5 today, xxx tomorrow)
- 7. • Collect Feedback* • Collect Signatures* • Approval* • Disposition Approval* • Tree State* 7
- 10. 2 workflow platforms SharePoint 2010 workflows Windows Server SQL Server Non supporté en SharePoint Foundation SharePoint 2013 workflows Windows Server SQL Server SP 2013 farm WWoorkrflkofwl oFawrm Farm
- 11. Topologies 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
- 12. Topologies: co-located (from Harbar & wilén) Workflow Manager Workflow Manager Workflow Manager
- 13. Topologies: Federated (from Harbar & wilén) Workflow Manager Scope 1 (SP Farm 1) Scope 2 (SP Farm 2)
- 14. Topologies: ‘Distributed’ (from Harbar & wilén) Workflow Manager Scope 1 (SP Tenant1) Scope 2 (SP Tenant 2) Workflow Manager Scope 1 (SP Tenant3) Scope 2 (SP Tenant 4) SP Tenant 1 SP Tenant 2 SP Tenant 3 SP Tenant 4
- 15. SharePoint 2013 and Workflow Service SharePoint Events Content People Sharing 2010 WF _API (REST OM) Workflow Services Manager Service Bus Instances Interop Deployment Messaging WF Service Application Proxy Workflow Manager Access Control OAuth Workflow Client
- 17. 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
- 18. What’s new in SPD workflows Stages
- 19. Demo 1 Stages
- 20. 2
- 21. geneva json 2 2
- 22. 2
- 23. Demo 2 : calling REST/JSON web services
- 24. 2
- 25. Demo 3 : calling the SharePoint REST API (GET)
- 26. 2
- 27. Demo 4 : calling the SharePoint REST API (POST)
- 29. 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
- 30. 3
- 31. 3
- 32. The workflow is hidden in the App 3
- 33. Demo 5 : (App) Workflow hidden in the App
- 35. 3
- 36. Demo 6 : (App)Workflow visible in SharePoint
- 38. Conclusions
- 40. Contoso App catalog 4
- 41. Serge Luca @sergeluca SharePoint MVP Brussels
Editor's Notes
- #8: 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
- #11: Workflow manager : former Windows Azure Workflow Server (WAS)…same code base as Windows Azure service bus Multitenant Rest based .Net 4.5 Scalable reliable
- #16: 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
- #21: Workflow and app permission feature TaskContentType feature appinv.aspx <AppPermissionRequests> <AppPermissionRequest Scope="http://sharepoint/content/sitecollection/web" Right="FullControl" /> </AppPermissionRequests>
- #23: http://api.worldweatheronline.com/free/v1/weather.ashx?q=geneva&format=json&num_of_days=2&key=txq75v64h4szxyqft7e9kcyx