SharePoint Workflow Development Drip (2)

Developing the first Sharepiont workflow: helloworldsequential Considerations

Helloworldsequential is an entry-level SharePoint workflow that basically follows the MSDN Tutorials Step-by-step, and the main purpose of my writing this text is to enumerate some of the important steps that will cause the workflow to fail as a direct result of the error handling of these steps.

Get ready

Helloworldsequential development environment is as follows, please ensure that your development environment is the same or compatible:

Deployed, available SharePoint Server 2007

. Net Framework 3.0 (download)

Visual Studio Extensions for Windows Workflow Foundation (download)

ECM Starter Kit for Visual Studio 2005 (download)

Office InfoPath 2007 RTM Chinese version

After installing ECM Starter Kit If a project template is missing please refer to my other article << Visual Studio.NET 2005 New Project dialog box solutions for disappearing project templates >>

When you add a SharePoint Workflow actions to the Toolbox, select the controls under the Microsoft.SharePoint.WorkflowActions namespace.

Visual Studio Project

The project template is the SharePoint sequential Workflow Library under SharePoint Server.

When you add and configure a workflow activity, be aware that all activities have a correlation Token attribute, notably the workflow itself (Workflow), Tasks (Task), and modifications (modification) require different correlation Token.

Create a strongly named assembly because your assembly is to be added to the GAC.

InfoPath Forms

When you create a blank form template, you check to enable only browser-compatible features.

In the security and trust of the form options, set the trust level of the form to domain or full trust.

The Accept parameter always starts with "Ows_" in the XML file that is used to set the receive parameters.

Modify the name of the group, the name of the group by default is myfields, if you want to generate class files for this form, then the name of the class is the name of the group, so it is recommended that you modify the default name (especially if your workflow project contains multiple forms that need to generate the class file).

For simplicity, publish the form to a project folder, or you need to pay special attention when you deploy.

Leave the accessible path blank when publishing the form, or it will fail when the workflow is installed

Deployment

Feature.xml and Workflow.xml can generate content in a method that inserts code snippets (snippet), and if you find that you don't have relevant code snippets, refer to my other article << solution for missing code snippets in Visual Studio 2005 >>.

The IDs of feature and workflow are two different GUIDs.

Install.bat file, replace Myfeature with a string that can be the name of the folder, preferably without spaces, or you will need to manually enclose the path in the Install.bat file with quotes.

Debugging

After you have changed the Feature.xml,workflow.xml and the form files, you need to reinstall the workflow and restart IIS.

If you only change the assembly, you need to replace the old with the new assembly, and then restart IIS.