Introduction to Windows SharePoint service workflow

InWSS 3, We can use a workflow to attach a business flow to a record (Item), The additional business flow can fully control this record, including the lifecycle of the control record. For example, we can create a simple workflow and send a document to a group of users for approval.

 Workflows can be simple or complex based on business needs. We can create workflows initiated by users orWSSWorkflow automatically initiated based on certain events.

 UseWindows SharePointWorkflow

Windows SharePointA workflow can be associated with a list or a document library, or a content type (Content type). Record of a list (Item) There can be multiple workflows. Multiple workflows can run the same record in the same list at the same time, but only one instance can exist in the same record in the same workflow. For example, if we may specify two workflows "format Review" and "validity Review" for a content type, the same record of this content type (Item) You can have instances of both the "format audit" and "validity audit" processes, but the same record cannot have two "format audit" process instances at the same time.

 SharePointWorkflow Technical Architecture

We can useVs2005OfWWF(Windows Workflow Foundation) The designer creates a process. Each workflow is compiled into its own dynamic link library file.(. DllFile).

 In addition, workflows can be directly controlled by users through custom workflow forms, which allow users to collect user information at different stages of a workflow.

 To create a workflow definitionSharePointDeploy workflows in the server farm. A workflow definition template file that containsWss3Information required for initializing and running a WorkflowXMLFile, including the following information:

• Workflow name,Guid, Workflow description
• Address of the custom form in the workflow
• WorkflowProgramCorresponding class used in

 EachSharePointThe server farm contains an association table. Each record in the table contains the association information between the workflow and the content type, list, or document library. The associated information includes the list of tasks and historical information that the workflow is automatically started, initiated by the user, and used by the workflow. If a workflow is associated with multiple content types, lists, or document libraries, each association will have a record in this table. Similarly, if a content type, list, or document library has multiple workflows, each workflow will have associated information records.

The following figure shows the technical architecture of the workflow in WSS , each content type, list, and document library are connected to the corresponding workflow through the Association Table of the server farm. Each workflow has a workflow template definition file, the XML definition file specifies the actual Assembly used by the workflow ( DLL ) and the class name in the Assembly, and specify various workflow forms required for workflow operation