The document discusses advancements in next-generation mobile workflows, highlighting SharePoint 2013's new features, including the integration of Windows Azure workflows and a new product called Workflow Manager. It notes the shift towards mobile access, with significant statistics on users accessing internal websites via mobile devices. Additionally, it mentions challenges and strategies for managing workflows, particularly differences between SharePoint 2010 and 2013 workflows.

2. Next Generation Workflows
Garry Whittaker
GarryJW@WhittakerMoore.com
@GARRYWMA
http://www.ConvenienceComputing.com
#spday2013
Whittaker Moore
Associates Ltd
www.WhittakerMoore.com

3. What do we mean by Next Generation
“Mobile to overtake fixed Internet
access by 2014” Mary Meeker, an
analyst at Kleiner Perkins Caufield
Byers
Google: “Mobile Web Access Speeds
Increased 30% Over The Last 12 Months”
Major Retailer: “45% of access to
internal web sites from mobile”

4. Workflow Foundation 4.5
Sharepoint 2013 Improvements
SharePoint 2013 style workflows
Uses Windows Azure Workflows
(but you don’t need Azure)

5.  Runs out of process from SharePoint and does not suffer any
constraints that SharePoint might bring.
 New product called Workflow Manager actually runs the WorkFlow
 The SharePoint web front end has another new product called the
Workflow Client built in.
 Uses REST API secured by Oauth to communicate between the two.
They don’t have to be on the same server.
 Finally a Workflow platform that can perform and scale.
 A caveat: SharePoint 2010 and older style workflows are completely
different and whilst there is an engine to run older style workflows in
SharePoint 2013 they will not benefit from the improvements.
 The Workflow Interop Bridge allows you to invoke a SP2010 style
workflow from an SP2013 style workflow if you really need to run an
older style workflow.
Sharepoint 2013 Style Workflow

6.  SharePoint 2013 Workflows are purely declarative You can’t write any C#
code inside workflow as you could in previous versions.
 A work-round is to put custom code inside a WCF Service and
declaratively call the service from workflow.
 Do not use SharePoint ‘system account’ to test workflows the workflow
will fail to run.
 Workflow Manager uses the User Profile Service (UPS). Ensure it is
running and the user who is running the workflow has a profile in UPS
 Also ensure the App Management Service is created and running.
.
Sharepoint 2013 Style Workflow Gotchas!

7. Useful Resource – Sohel Rana’s Blog
Windows Azure Workflows
http://ranaictiu-
technicalblog.blogspot.co.uk/2013/02/
sharepoint-2013-workflow-
manager.html

8. How do we make Workflows Convenient?
43% of households own tablets
75% own Smartphones
46% already use their mobile devices to access work data
Source CEA

9. Raona can help

10. Visual
Intuitive and easy to use for business
staff, without any need for
programming.
Powerful
Availability of an extensive library of
resources and workflows that provide
the basis for a wide range of business
processes
Straightforward
Easy migration/integration of
workflows from other platforms such
as Lotus Notes

11. Mobile
The possibility to interact
with workflows from a
smartphone or tablet
Integrated
Integration with corporate applications,
such as CRM, ERP and the corporate
intranet, or with cloud services

13. Thanks ;) raona_uk
raona.uk
garrywma
http://www.conveniencecomputing.com