Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly
Download as PPTX, PDF•1 like•1,045 views
This document provides an overview of Ricardo Wilkins' experience and qualifications as a SharePoint Solutions Architect. It includes details on his technical skills such as application development, web development, application lifecycle management, and technical training. It also lists his blog and contact information. The document consists of 22 pages that cover topics like reusable components, visualized workflows, and deploying SharePoint solutions. It concludes by noting Ricardo's email, blog, and includes a copyright notice.
Business Process Automation with SharePoint & Workflow - The Good, the Bad, and the Ugly
- 1. Ricardo Wilkins SharePoint Solutions Architect Information Control Corporation 1
- 2. • • − − − − − • 2
- 3. Ricardo Wilkins SharePoint Solutions Architect • App Dev (.NET; embedded) • Web Dev (ASP.NET, PHP) • Application Lifecycle Management (TFS Admin) • Technical Training • Blog: rixbits.blogspot.com • : @ricardo303 SharePooch 3
- 4. • • • 4
- 5. 5
- 6. Initialize Compile Test Document Drop Code 6
- 7. • • • • • • 7
- 8. • 8
- 9. 9
- 10. • − − − 10
- 11. • 11
- 12. 12
- 13. • − − − − 13
- 14. • 14
- 15. Reusable 15
- 16. Visualized 16
- 17. Deploy as solution 17
- 18. • • 18
- 19. • − − − − 19
- 20. 20
- 21. High Cost range of empowered/skilled users Low basics easy-yet-powerful most advanced Functionality 21
- 22. • − [email protected] [email protected] • http://rixbits.blogspot.com ©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. 22
Editor's Notes
- #22: Let’s now see how Nintex Workflow 2010 is positioned to continue its momentum in the marketplace. It continues to fill market and customer needs, not covered by tools like SharePoint Designer and Visual Studio, despite the improvements in the new versions of such tools. Let’s take a look in how Nintex Workflow 2007 used to fill a broad range of usage scenarios and will continue to do so in its 2010 version.(* the slide advances with 3 clicks. Speaker can tie the talking points to each of the clicks)1) We start by looking at these 2 variables: cost and functionality, we can place each workflow tool in the space it fits best:SharePoint Designer offered functionality to cover the basics, and did so at a very low cost (one could say $0 because of free price tag, let’s just remember other aspects of TCO). SPD offered the basic design for linear workflows, using a wizard paradigm and offering some 30 activitiesOn the other side of the spectrum, Visual Studio offers all the functionality to handle even the most complex workflows. That comes with higher costs: software price, higher and steeper learning curve, and the fact skilled developers will be demand to focus on multiple projects, that might take priority over the task at hand of improving workflowsNintex Workflow capabilities answer to customer needs of empowering business users to model and improve from simple to complex workflows. While keeping IT in control of monitoring and manageability. And it offers combination of rich functionality at competitive price point2) In the 2010 wave, all products evolved and invested in better richer functionality, ‘pushing the curve or boundaries’ of what customers can expect and accomplish:We recognize and give credit to SPD improvements, getting to work with Visio, for a more visual design experience, but there are still a couple of limitations, not bringing workflow to everyone: Still not all done in one environment (one needs to design in Visio, import to SPD, configure without the graphical interface and finally publish to SharePoint)Requires client applications (SPD and Visio), and the associated licensing costs, deployment and skilling up the set of licensed usersSPD now does support parallel processing, but still lacking support for more complex logic such as loops and state machines Visual Studio also gets enriched, and continues to handle those most complex scenariosNintex Workflow 2010 continues to fill that broad spectrum of customer needs not yet fulfilled optimally by SPD nor VS3) And let’s add a 3rd variable to this chart, placing these ‘stretched bubbles’ to represent the ‘range of empowered/skilled users’ apt to design, model and deploy workflows. Visual Studio: mainly developers only; SPD: some power users; and the 2010 version becomes more complex. Nintex: broad range of skilled users, given it’s ease of use. That adds value for empowering business units, while still reserving IT the controls for policies and manageability