5. #SPSVB @PGBhoyar
Important Concepts
LessComplexity
Why Workflows in SharePoint?
• Reliable -last machine reboots
• Visualize Workflows Graphically
• Reporting is supported
• Reusable Workflows
• Export Workflows into Visual Studio and Third Party
Products
9. #SPSVB @PGBhoyar
OOTB Workflows
List and Libraries:
• Approval
• Collect Feedback
• Collect Signature
• Disposition Approval
Lists :
• Three State (available in Foundation)
10. #SPSVB @PGBhoyar
OOTB Workflows
Approval Workflows
• Good for business processes requiring approvals
• Set up to a list, library, or content type
• Manual/Automatic (Creation/Change/Deletion)
• Stop/Terminate
• Tight Integration with Office
13. #SPSVB @PGBhoyar
SharePoint Designer
Customize OOTB Workflows
• Customize appearance, behavior and result of the
workflow
• Two Methods of Edit
• Directly Edit – Not Recommended
• Copy and Edit
14. #SPSVB @PGBhoyar
SharePoint Designer
Features
• Edit OOTB Workflows
• Apply Business logic
• Save the custom workflow as template
• Publish workflows globally
• No Code Drop
• Export to Visual Studio
20. #SPSVB @PGBhoyar
Visual Studio Workflows
Features
• Add SharePoint Designer Missing Action
• Add Custom Data or Action
• Use of Event Receivers and Timer Jobs
• Exposes full power of .NET
27. #SPSVB @PGBhoyar
Third Party Tools
Nintex
• Small Installation Footprints
• Tightly Integrated in SharePoint
• Non tech/developers can create workflows
30. #SPSVB @PGBhoyar
K2 Products
Short Comings (Personal
Thoughts)
• Steep Learning Curve
• Work Outside SharePoint
• Extensive Use of K2 Support
• K2 Experts are Rare Commodity
34. #SPSVB @PGBhoyar
Questions? Feedback? Contact me:
Twitter: @PGBhoyar
Blog: http://pgbhoyar.wordpress.com( limited contents)
Email: pgbhoyar@gmail.com
Thank You
Organizers, Sponsors and You for Making this Possible.
Hinweis der Redaktion
Automation of Business Processes : Approvals, Escalations, History, Reports and AuditsWorkflows are important for the success of SharePoint Implementation
This is common scenario for the developersChanging the approach in the middle of the project leaves huge impact on the schedule and budgetAlways go to drawing room, study the requirements and analyze the pros and cons and then take a decision
Sequential : Automation Tasks, less human interactions , Sequential Flow ChartsState Machine : Long Pauses between the steps, human interaction or external system interaction. Example Support System Queue.
Build workflows and process-driven applications without code
Expand workflows beyond SharePoint DesignerRich visual designer from SharePointLot of OOTB Activities
Small installation footprintStart in SharePoint, stay in SharePoint
Reporting & Analysis – Process automation enables efficiency and analysis. Process status is presented graphically and by table summary reports.
Steep Learning CurveWork Outside SharePointExtensive use of K2 SupportK2 Experts are rare commodity
IT LimitationsRequirements (State Machine Vs Sequential)FunctionalityBudgetDon’t attempt to fully automate every step of every business process. Evaluate which steps are appropriate and stop there. Take the time to analyze potential ROI from process automation