Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

22
1 Business Process Automation with SharePoint Ricardo Wilkins SharePoint Solutions Architect Information Control Corporation

Transcript of Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

Page 1: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

1

Business Process Automation with SharePoint & WorkflowThe Good, the Bad, and the Ugly

Ricardo WilkinsSharePoint Solutions ArchitectInformation Control Corporation

Page 2: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

2

Agenda• The process of process automation• How SharePoint can help

− InfoPath forms− The Ugly (Visual Studio 2008)− The Bad (SharePoint Designer 2007)− The Good (2010)− The More Good (Nintex)

• Demo

Page 3: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

3

About Me

• App Dev (.NET; embedded)• Web Dev (ASP.NET, PHP)• Application Lifecycle Management

(TFS Admin)• Technical Training• Blog: rixbits.blogspot.com• : @ricardo303

Ricardo WilkinsSharePoint Solutions Architect

SharePooch

Page 4: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

4

The Process• Start with process, not technology• Be on the same page – literally• No frills for Iteration #1

Page 5: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

5

Page 6: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

6

Iteration 1

Initialize Compile

Document

Test

Drop Code

Page 7: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

7

InfoPath• Design forms via point-n-click• Validation• Enforce business rules• Powerful rules engine• Better user experience• Client or browser

Page 8: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

8

The Ugly• Visual Studio 2008 & Workflow

Foundation

Page 9: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

9

Page 10: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

10

The Ugly• Visual Studio 2008 & Workflow

Foundation− Too much plumbing− Not reusable− Devs needed for maintenance

Page 11: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

11

The Bad• SharePoint Designer 2007

Page 12: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

12

Page 13: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

13

The Bad• SharePoint Designer 2007

− Closer to a non-techie tool− Point-n-click− Still not reusable− Lots of Actions included,

but could use more

Page 14: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

14

The Good• SharePoint Designer 2010

Page 15: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

15

Reusable

Page 16: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

16

Visualized

Page 17: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

17

Deploy as solution

Page 18: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

18

The Good• Power users can create/maintain• Reusable & deployable

Page 19: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

19

The More Good• Nintex Workflow

− Lots of good Actions− Very reusable/deployable− Good visualization− Faster dev time

Page 20: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

20

Demo

Page 22: Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly

22

©2009 Microsoft, Microsoft Dynamics, the Office logo, and Your potential. Our passion. are trademarks of the Microsoft group of companies. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

• Contact:− Ricardo Wilkins –

[email protected] Hartsel – [email protected]

• Slides will be posted at:http://rixbits.blogspot.com

Questions?