SharePoint workflow solution quickflow series (1)-quick flow entry

RelatedArticle:Quickflow1.0Release 

SharePoint workflows have many problems. Their capabilities in developing complex workflows are "Limited" or "Unlimited Potential", but the mining process is too complicated. For this reason, based on my experience in practical projects, I released quick flow1.0 in May for free, and introduced it at the msiw SharePoint summit in early, I have been very lazy and have not introduced it further. I will explain it in depth in the following articles.

This article provides an introduction to the basic operations of quickflow during workflow development.

Quickflow, as an extension of sharepont WF workflow, uses vs2008 as a development tool to provide a new workflow model: Flowchart of wf3.0, and provides a series of encapsulated activities.

Quickflow has the following core classes:

Class Name	Description
Flowchartworkflow	Workflow base class
Start	Workflow starts
End	Workflow ended
Label	Tag	As a virtual node, it only plays a role in displaying
Task	Task Allocation	To assign a single task, you must handle its taskcreating event and assign a value to the user attribute.
Multitak	Allocate multiple tasks	You can choose to allocate tasks in parallel or in serial mode.
Grouptask	Group to which tasks are assigned to SharePoint
Step	Procedure	It can be used as a container for other activities. The first-level activities of quickflow must be provided by itself. If you want to use other activities, such as codeactivity, you can place them inside the step.
Decison	Workflow flow direction judgment	Only two branches are supported.
Rounter + rule	Multi-path Branch judgment	In step, you can use these two activities to determine the flow direction of multiple channels.

The development steps of quickflow are basically the same as those of the standard steps for developing SharePoint + infopath workflow in vs2008:

1) create a workflow project

2) Add a reference to quickflow. dll and add activities in quickflow to the toolbar. (Download: http://quickflow.codeplex.com /)

3) modify the workflow base classFlowchartworkflow

4) Delete the default onwrokactivited activity and add the start activity.

5) Then you can continue adding other activities.

6) design the infopath form.

7) WriteCodeEstablish a connection between workflow and infopath

8) Deploy and Test

The detailed steps are as follows:

Step 1: Create a Sharepoint sequence workflow project.

Step 2: Add a reference to quickfow. dll

Step 3: change the base class to quickflow. flowchartworkflow.

Step 4: add activities in quickflow to the toolbar.

Step 5: AddStartActivity and set its correlationtoken attribute (select owneractivityname as the workflow class and correlationtoken as any string ).

Step 6: Add grouptask to the designer. Set Group to the name of a Sharepoint Group

Step 7: Add a dediton activity and set the conditon attribute. Generally, it is set to be determined based on the approval result of the previous level.

The approval result can be obtained through taskoutcomes of grouptask.

Grouptask. taskoutcomesHow does the value come from? It corresponds to the task infopath_ Taskoutcome OF THE FORMField,

In the form, you only need to give _ taskoutcome when the approval action is executed.You can obtain the corresponding values in the workflow code.

 

Step 8: design the infopath task form and publish it to the project root directory.

Step 8: Change workflow configure:

Step 9: publish a workflow.

Note: before you finally run the workflow, you must first set quickflow. dllDeploy to GAC.

Postscript:

To use infopath in Sharepoint, You need to enable the session; otherwise, an error occurs: "This form cannot be displayed because the session status is unavailable ."

Reference: http://www.cnblogs.com/TerryFeng/archive/2009/01/06/1370641.html

Sample Code:

http://cid-7f5a25cdf47d03e6.office.live.com/self.aspx/QuickFlow/Examples/ThreeStepWorkflowExample%5E_Vs%5EMInfoPath.zip