2. About me
• Vadim Tabakman
• Lead Technical Evangelist, Nintex
• Over 19 years consulting, development and corporate IT experience
• End user advocate
3. Introduction
• There are more best practices and errors to avoid
• Based on real-world projects
• Advice applies to any workflow product
• No demos
5. Why Not One Workflow History List?
• History Lists are just SharePoint lists
• Performance degradation with 2000-4000 items
• Multiple Workflows and One History List
• Grows very quickly
• Multiple Workflows and Multiple History Lists
• Shares the load.
• Faster to access workflow history
7. Good Uses of SharePoint Workflow
• Managing how people work
• Document approval & feedback
• Collaborative reviews & discussions
• Gathering signatures
8. Good Uses of SharePoint Workflow
• Automating some of SharePoint’s behavior
• Approve site creation requests
• Parse incoming email in a list and act on it
• Publishing items to target
• Moving documents through lifecycles
9. Possible Uses of SharePoint Workflow
• Manipulating other applications, data sources
• Employee onboarding
• Resource scheduling
• SharePoint lists become work queues
10. Bad Uses of SharePoint Workflow
• Transaction-oriented processes
• Blocking or modifying activity
• Application-to-application service activity
• Aggressive data transformations
• Work that doesn’t involve SharePoint at all
14. Exceptions are Initially Ignored
• Rarely is this considered in advance
• Rarely does everyone agree
• Ignored exceptions lead to bypass
15. Initial Failure as a Winning Strategy
• People do not want to hear these hard truths.
• You may have to create an initial workflow just to show how awful a
process is.
• Only then can you change it.
22. When to use a :
List Workflow
Site Workflow
Reusable Workflow Template
23. Reusability
• You should think about reusability first
• Save yourself time
• Save your colleagues time
• Save your business time and money
• Is a List workflow the best solution for you?
• It’s probably the quickest and easiest, but is it the best solution?
25. The Form is the User Interface
• Not the workflow
• Not the data
26. If (x and y) then
do this
do that
End if
If (user is Bob) then
do this and that and the other thing
undo that
End if
If (x and y) then
do this
do that
End if
If (x and y) then
do this
do that
End if
If (user is Bob) then
do this and that and the other thing
undo that
End if
If (x and y) then
do this
do that
End if
36. You’re Already Using SharePoint
• The list itself can be the report
• Users can sort, group, filter on metadata (Leverage Views!)
• Write progress information to item properties
• Stage Workflows already do this
37. Summary
• Don’t always use SharePoint Workflow
• Plan to fail
• Focus on everyday processes
• It’s not about forms
• Self-reporting workflows