Chapter 9. Forms in Visual Studio workflows

This chapter deals with forms that run inside a workflow including association, initiation, and modification forms.

Initiation forms gather information directly before the workflow starts. With association and modification forms, users enter information into the workflow. The difference between the two is that an association form is presented to users when the workflow is added to the list, library, or site, and modification forms are presented to users during the workflow’s execution.

Initiation forms come in handy when you need to gather data from the user before the workflow starts, as with an expense report. When you initiate a workflow, you might not know who needs to approve the expense report. An initiation form could capture from the submitter the identification of their manager, and the workflow could then ensure that the proper individual receives the approval request.

The association form is also useful with expense reports. Rather than have employees specify their managers every time they upload an expense report, you could use an association form so that employees enter the information only once—when the custom workflow is first added to the library.

9.1. Adding .NET code to an InfoPath form

9.2. Programmatically retrieving form data from within a workflow

9.3. InfoPath forms in Visual Studio workflow

9.4. ASP.NET forms in Visual Studio workflows

9.5. Summary