5 Stages of SharePoint Grief: Coming to Terms with the Rebuilt Workflow Platform in SharePoint 2013
•Als PPTX, PDF herunterladen•
0 gefällt mir•837 views
This document outlines the 5 stages of grief that users experience when transitioning from SharePoint 2010 workflows to SharePoint 2013 workflows: denial, anger, bargaining, depression, and acceptance. It discusses the key changes to the workflow architecture in SharePoint 2013 including the new Workflow Manager service, declarative development model in SharePoint Designer, and ability to build workflows using Visual Studio. It provides an overview of installing and configuring workflows in SharePoint 2013, demonstrations of workflows in SharePoint Designer and Visual Studio, and important resources for learning more about the new workflow platform.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (18)
Ähnlich wie 5 Stages of SharePoint Grief: Coming to Terms with the Rebuilt Workflow Platform in SharePoint 2013
Ähnlich wie 5 Stages of SharePoint Grief: Coming to Terms with the Rebuilt Workflow Platform in SharePoint 2013 (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
5 Stages of SharePoint Grief: Coming to Terms with the Rebuilt Workflow Platform in SharePoint 2013
- 1. 5 Stages of SharePoint Grief Coming to Terms with the Rebuilt Workflow Platform in SharePoint 2013
- 2. Who is this guy? • • • • • • Software Engineer at Applied Information Sciences Year 8 of 10-Life with SharePoint @SPSamL SharePointTherapy.Blogspot.com Blog.Appliedis.com Contributing Author: Microsoft SharePoint 2013 Inside Out
- 3. Agenda • Denial • Look back at Workflow 2010 • Anger • Intro to 2013 changes • Bargaining • Administration & Configuration • Depression • Development • Demos • Acceptance • Important Resources • Q&A
- 4. SharePoint 2010 Workflow • Built into SharePoint install • Added layer on top of WF • All workflows ran within the context of a SharePoint process • SPD Workflows became useful • Visio design • Lots of Actions & Extensible • VS templates made powerful workflows easier to build
- 5. SharePoint 2013 Changes • • • • New Architecture SharePoint ditches control Declarative development SPD Loops!
- 6. New Architecture • Workflow Manager • New service to host workflow • Farm environment • Not SharePoint specific • Interacts with SharePoint via Web Services • Unloads SharePoint of processing
- 7. Install and Config • Can run on SharePoint box • Dev/Small farms • PowerShell required to associate WF Farm to SharePoint • WF Farm can support nonSharePoint WF as well • Register-SPWorkflowService –SPSite “http://intranet.wingtip.com” –WorkflowHostUri “http://wingtipserver:122291” -AllowOAuthHttp
- 8. SharePoint Designer Development • Designer has loops! • Web Service interactions • Dictionaries • Array of objects • Build, Count, Get Item • App Step – elevated security • InfoPath forms are gone
- 9. SPD Demo
- 10. Visual Studio Development • So, you love coded Workflows? Keep tears to a minimum, please. • Declarative Workflow • DynamicValue • What’s the point if there’s no custom logic? • Web Services! • HTTPSend activity • CSOM Integration • Workflow in SP Apps • Custom Task Outcomes • BIG PLUS – No more Correlation Tokens!
- 11. VS Demo
- 12. Resources • • • • Andrew Connell’s PluralSight Video - http://bit.ly/ACsSPWFonPS Fabian Williams’ SPD and Fiddler Post - http://bit.ly/FWsSPDPOSTREST My Workflow Install & Config Video - http://youtu.be/6haTejk98hU Running Workflow with Elevated Permissions - http://msdn.microsoft.com/enus/library/jj822159.aspx
- 13. Questions
Hinweis der Redaktion
- - I’ll have these slides up on my blogAIS blog will have a post mirroring this presentation, but with reference to 1st post project
- Orange layer is where you lived. Everything else was wrapped up in a bow for the most part.
- - Introducing Workflow Manager- 2013 begins to show MS’ move to cloud with offloaded servicesBusiness users will finally get loops
- WFM is a separate installBig improvement in scalability and re-use because of break from SP and farm envWF Events > WF Manager Client using Azure Service Bus – returns SP REST API back into SP --- Oauth authentication
- MUST INSTALL/CONFIG as WF Service acct or you’ll get errors
- SPD gets loops instead of hacksWeb services for custom/SP data read/writeDictionary (not quite DynamicValue, from my understanding, though)We’ll see Build and Get Item in demoCan still create 2010 WF, tooCustom forms are now ASPX – HTML and JS
- WAW Config – sort ofWas going to do code, but ran out of time and samples on MSDN are for B1R (TAP) , not B2 (Public)
- You can write code activities/actions for on-prem, but obviously won’t work in the cloudDynamicValue: Basically it understands JSON. So when you call a WCF/RESTful service with an HTTP activity, it returns an object of type DynamicValue. You then use another activity to pull data out of this variables of this data type using an XPATH like notation. (c/o AC)Can be nestedArrays of DynamicValues can be iterated (see demo)WCF devs can join the SP fun. Web Services is where custom code lives for WFSee more offloading of processingBest practice for code, not custom actions (see Devices and Services company)Activities to directly interact w/ said services – get and set data through these activities and your SP/other servicesIf you haven’t heard, CSOM got a Barry Bonds sized shot of steroids (How many recognize that name? Jose Conseco? Ivan Drago?)Client-side interaction w/ WFSP Apps (NEW NEW NEW) driven/driving WFDon’t like Approve/Reject? Create new ones using custom Site Column and CT.Catch is the OOTB ones show when using WorkflowTask CT as baseDon’t you love tokens? How many people have had broken WF and find out it’s just a bad token reference?