Regardless of whether you're coding your own forms in ASP.NET, using InfoPath, or using a third-party product, certain practices make sense when building forms for workflow solutions. The key is to decide what work should be performed by the form and what should be done by the workflow. Thinking about the overall solution rather than only a form is essential, and this webcast will walk you through a recommended scenario of how to do so.

1. Forms and Workflow:
Putting the Right Work
in the Right Place
Mike Fitzmaurice
VP – Product Technology
Nintex
@mikefitz
mikefitz@nintex.com

2. About me
• Mike Fitzmaurice
• Vice President of Product Technology, Nintex
• 11 years at Microsoft
• SharePoint’s original technical evangelist

3. It’s not always about forms

4. The Form is the User Interface
• Not the workflow
• Not the data

5. 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

6. Form-Only App Problems
• Hidden logic
• Disconnected logic
• Security
• Complexity without code

7. Think About the Whole App
User Interface
Process Logic
Data Access

8. Make the Workflow Do More of the Work
• Documented
• Auditable

10. One Form Per Step
• Submit
• Start
• Task

12. Task Forms
• Workflow can route new data
• New data can be written to original form
• All info can be sent to other places

13. It’s Not All About Spreadsheets, Either
• Same problem, different file type
• Example: HUGE Excel file with macros
• Workflow: route, track, remind

14. Questions?

15. Thank You