HOUSEKEEPING…  Download EventBoard Mobile and remember to fill out session evaluations…  Phasers set to stun, mobile devices set to silent…  You must be present to win at the wrap-up…

THANKS TO OUR SPONSORS!!!

Join us at #SharePint sponsored by K2 at World of Beer of Reston in the Towncenter just across the bridge Why? To network with fellow SharePoint professionals What? SharePint!!! When? 6:00 PM Where? World of Beer Reston 1888 Explorer Street Reston, VA Thanks to? K2!

INTRODUCTION TO SHAREPOINT 2013 WORKFLOW – PART I Presented by Srini

THANK YOU  RESTON SHAREPOINT GROUP  MICROSOFT  SPONSORS  AUDIENCE

ABOUT ME  AUTHOR  Pro SharePoint 2010 Business Intelligence (Apress)  Pro SharePoint Migration (Apress)  SharePoint 2013 Development Machine (Self Published)  SPEAKER  INETA, SharePoint Saturday, CAPAREA.NET, SUGDC  BLOGGER  SHAREPOINT SOLUTIONS ARCHITECT / CONSULTANT / SME

AGENDA  SharePoint 2013 Workflows Architecture (On-prem and SharePoint Online)  How to build your Virtual Machine to run workflows  Tricks, Tips and Tools to build workflows on your development machine  Building your first workflow using SharePoint Designer  Working with Office 365 workflows and setup  Understanding Visio integration

COMPARISON

2010 VS  SharePoint 2010 hosted the Workflow Foundation (WF) workflow runtime  Tightly coupled workflow to SharePoint 2010  Workflow data kept in SharePoint content databases  Challenges:  Designed for on-premise deployments (scale)  In SharePoint, extending WF meant you had to be a box admin  Analytics on current/previous workflow instances hard to acquire  Executed in the context of SharePoint as super user  Workflow now treated as a service in SharePoint 2013  Moved to Windows Azure Workflow  No longer runs in the content farm  No longer runs on SharePoint WFE / App servers  Harnesses the latest workflow technology from Microsoft  Windows Azure Workflow available for on- prem deployments  Improves stability, scalability & transparency

ARCHITECTURE SharingContentEventsPeople Visual Studio SharePoint Designer SharePoint 2010 WF _API (REST OM) Workflow Services Manager Service Bus InstancesInterop DeploymentMessaging WF Service Application Proxy Workflow Manager OAuth Access Control Workflow Client

SHAREPOINT 2013 AND WORKFLOW SERVICE SharingContentEventsPeople Visual Studio SharePoint Designer SharePoint 2010 WF _API (REST OM) Workflow Services Manager Service Bus InstancesInterop DeploymentMessaging WF Service Application Proxy Workflow Manager OAuth Access Control Workflow Client

ARCHITECTURE

IMPROVEMENTS

 Introducing “Stages”  Provides support for repeating & skipping workflow steps  Declarative workflows have loops  Loop # times / with condition / with expression  Declarative workflows can call REST/SOAP services  SharePoint 2010 required developers when:  Call SharePoint API  Connect & query databases  Consume feeds (ATOM / REST)  Call Web Services / REST  SharePoint 2013 enables workflow authors to do all this declaratively

WORKFLOWS IN DESIGNER  Improved visual designer  Integrated the Visio designer into SharePoint  Can switch between visual designer & sentence-style  Editable properties helper  Stages & Loops  Calling REST Web Services  Designer supports cut / copy / paste / undo / redo / select-all  Improved editor (rich formatting)  Each stage has an entry point & gate  Gate: conditional transition point where workflow exits  Underlying core in WF4 flow step in a flowchart  Can contain multiple steps  Mitigates SharePoint Designer loop limitations

WORKFLOWS IN VISUAL STUDIO  Can create WF 3.5 or WF 4 workflows  For WF 4, Azure Workflow required  For WF 3.5, see Workflow Interop Bridge…  Focus is around declarative workflows  Push custom code logic to Web services  Programmatic workflows still possible, but only in Windows Azure Workflow  Workflow tools: SharePoint Designer & Visual Studio

DESIGNER VS VISUAL STUDIO SharePoint DesignerVisual Studio Reusability Create reusable WFCreate WF templates Include in SP App Custom Code Custom Actions Consume, not createYes; underlying activities Visio Integration Debugging

INTEROP BRIDGE  Enables SharePoint 2010 workflows to work in 2013  Execution engine hosted in SharePoint 2013  Interop bridge:  Negotiates between two execution engines (SP2010 & SP2013)  Delegates SP2010 workflows to SharePoint from WAWS  Invoke SP2010 workflow action from WAWS with InvokeSharePointWorkflow action

INTEROP BRIDGE

Workflow Backend SharePoint Tasks Instances _API 123 GET /…/web/siteuserinfolist/items?$filter=id eq {0} Site Users POST /…/web/lists(guid'{0}')/reservelistitemid POST /…/web/lists(guid'{0}')/items REST/OData message format Retry on failure Repeatable (idempotent) Create, Read, Update and Delete Merge update with conflict resolution (HTTP ETag) Service Bus

Workflow Backend SharePoint Tasks Instances _API 123 Site Users REST/OData message format Retry on failure Repeatable (idempotent) Create, Read, Update and Delete Merge update with conflict resolution (HTTP ETag) Service Bus

Workflow Backend SharePoint Tasks Instances _API Site Users Workflow Frontend Service Bus Messages

Workflow Backend SharePoint Tasks Instances _API Site Users Workflow Frontend Service Bus Messages

Farm Node

SP Farm 1 Workflow Cluster SP Farm 2 load balancer Workflow Client Each SP farm targets a different Workflow Manager scope Independent security realms Federated Topology

CONFIGURE

Register-SPWorkflowService –SPSite “ –WorkflowHostUri “ – AllowOAuthHttp

DEMO

CONTACT  blog.srinisistla.com

USEFUL DOWNLOADS / LINKS SharePoint Designer 2013 – What's new in WF in 2013 – Getting Started - Develop using VS Setup configure WF Manger - Workflow Manager