View
367
Download
0
Embed Size (px)
DESCRIPTION
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.
Citation preview
Forms and Workflow: Putting the Right Work
in the Right PlaceMike Fitzmaurice
VP – Product TechnologyNintex
About me
• Mike Fitzmaurice
• Vice President of Product Technology, Nintex
• 11 years at Microsoft
• SharePoint’s original technical evangelist
It’s not always about forms
The Form is the User Interface
• Not the workflow
• Not the data
If (x and y) then do this do thatEnd if
If (user is Bob) then do this and that and the other thing undo thatEnd if
If (x and y) then do this do thatEnd if
If (x and y) then do this do thatEnd if
If (user is Bob) then do this and that and the other thing undo thatEnd if
If (x and y) then do this do thatEnd if
Form-Only App Problems
• Hidden logic
• Disconnected logic
• Security
• Complexity without code
User Interface
Process Logic Data Access
Begin Step 1
Step 2Step 3
End
Think About the Whole App
Make the Workflow Do More of the Work
• Documented
• Auditable
One Form Per Step
• Submit
• Start
• Task
Task Forms
• Workflow can route new data
• New data can be written to original form
• All info can be sent to other places
It’s Not All About Spreadsheets, Either
• Same problem, different file type
• Example: HUGE Excel file with macros
• Workflow: route, track, remind
Questions?
Thank You