business process automation with sharepoint & workflow - the good, the bad, and the ugly
TRANSCRIPT
1
Business Process Automation with SharePoint & WorkflowThe Good, the Bad, and the Ugly
Ricardo WilkinsSharePoint Solutions ArchitectInformation Control Corporation
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
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
4
The Process• Start with process, not technology• Be on the same page – literally• No frills for Iteration #1
5
6
Iteration 1
Initialize Compile
Document
Test
Drop Code
7
InfoPath• Design forms via point-n-click• Validation• Enforce business rules• Powerful rules engine• Better user experience• Client or browser
8
The Ugly• Visual Studio 2008 & Workflow
Foundation
9
10
The Ugly• Visual Studio 2008 & Workflow
Foundation− Too much plumbing− Not reusable− Devs needed for maintenance
11
The Bad• SharePoint Designer 2007
12
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
14
The Good• SharePoint Designer 2010
15
Reusable
16
Visualized
17
Deploy as solution
18
The Good• Power users can create/maintain• Reusable & deployable
19
The More Good• Nintex Workflow
− Lots of good Actions− Very reusable/deployable− Good visualization− Faster dev time
20
Demo
21
Nintex Workflow 2010 Positioned for Success
Cost
Functionality
basics most advancedeasy-yet-powerful
Low
H
igh
range of empowered/skilled users
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?