Presented by

Srini Sistla
@srinisistla

 CAPAREA SPONSORS AUDIENCE

 Samples and screen shots are from

Ignite SPC 2012

 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 2010 ARCHITECT / CONSULTANT / SME

 ARCHITECTURE DETAILS YOUR DEVELOPMENT MACHINE FOR WORKFLOWS

 SharePoint 2010 hosted the Workflow

Workflow now treated as a service in

Foundation (WF) workflow runtime

Tightly coupled workflow to SharePoint 2010

SharePoint 2013
Moved to Windows Azure Workflow
No longer runs in the content farm No longer runs on SharePoint WFE / App

Workflow data kept in SharePoint content

databases
Challenges:
Designed for on-premise deployments

servers Harnesses the latest workflow technology from Microsoft

Windows Azure Workflow available for on-

(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

prem deployments
Improves stability, scalability &

transparency

Access Control

SharePoint
Events Content People Sharing 2010 WF

SharePoint Designer

OAuth

Visual Studio

_API (REST OM) Workflow Services Manager

Instances Deployment Interop Messaging
Workflow Client

Workflow Manager

Service Bus

WF Service Application Proxy

SHAREPOINT 2013 AND WORKFLOW SERVICE SharePoint

Events Content People Sharing 2010 WF

Access Control

SharePoint Designer

OAuth

Visual Studio

_API (REST OM) Workflow Services Manager

Instances Deployment Interop Messaging
Workflow Client

Workflow Manager

Service Bus

WF Service Application Proxy

 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

 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 email 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

 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

SharePoint Designer
Reusability Include in SP App Custom Code Custom Actions Visio Integration Debugging Consume, not create Create reusable WF

Visual Studio
Create WF templates

Yes; underlying activities

 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

SharePoint
_API

Workflow Backend
1 2

Site User s

Tasks

web/siteuserinfolist/items?$filter=id eq {0} web/lists(guid'{0}')/reservelistitemid web/lists(guid'{0}')/items

Service Bus

REST/OData message format Retry on failure Repeatable (idempotent) Create, Read, Update and Delete Merge update with conflict resolution (HTTP ETag)

Instances

SharePoint
_API

Workflow Frontend

Workflow Backend

Site User s

Tasks

Service Bus

Messages

Instances

Farm Node

Farm Node

Farm Node

SP Farm 1

Workflow Client

Workflow Cluster

SP Farm 2

load balancer

Workflow Client

Each SP farm targets a different Workflow Manager scope Independent security realms

Federated Topology

Register-SPWorkflowService SPSite http://sp/sites/awfs WorkflowHostUri http://sp:12291 AllowOAuthHttp

 @srinisistla blog.srinisistla.com

SharePoint Designer 2013 http://www.microsoft.com/en-us/download/details.aspx?id=35491 What's new in WF in 2013 http://technet.microsoft.com/en-us/library/jj219638.aspx

Getting Started - http://technet.microsoft.com/en-us/library/jj227177.aspx

Develop using VS 2012 - http://technet.microsoft.com/en-us/library/jj163199.aspx

Setup configure WF Manger - http://technet.microsoft.com/en-us/library/jj163276.aspx

Workflow Manager 1.0 - http://technet.microsoft.com/en-us/library/jj193528.aspx