About workflow. xml feature. XML in Moss workflow development

If workflow and feature options are not found in the code snippet function, refer to this article:
Http://www.cnblogs.com/xiaoshatian/archive/2006/12/31/608479.html

This article also shows you the roles of these two files.
Http://weblog.vb-tech.com/nick/archive/2006/09/04/1760.aspx

My workflow. XML content: <elements xmlns = "http://schemas.microsoft.com/sharepoint/">
<Workflow
Name = "My Workflow"
Description = "this workflow"
Id = "9e22a7b0-4fef-411a-b8c2-4ff8cca31e85"
Codebesideclass = "hellospwf. applyworkflow"
Codebesideassembly = "hellospwf, version = 3.0.0.0, culture = neutral, publickeytoken = 4bfa53b046e311f6"
Tasklistcontenttypeid = "0x01080100c9c9515de4e24001095074f980f93160"
Associationurl = "_ layouts/cstwrkflip. aspx"
Instantiationurl = "_ layouts/iniwrkflip. aspx"
Modificationurl = "_ layouts/modwrkflip. aspx">

<Categories/>
<! -- Tags to specify infopath forms for the workflow; Delete tags for forms that you do not have -->
<Metadata>
<Association_formurn> urn: Schemas-Microsoft-com: Office: infopath: bxd-apply1:-myXSD-2007-02-06T06-43-51 </association_formurn>
<Instantiation_formurn> urn: Schemas-Microsoft-com: Office: infopath: bxd-apply1:-myXSD-2007-02-06T06-43-51 </instantiation_formurn>
<Task0_formurn> urn: Schemas-Microsoft-com: Office: infopath: BXD-MARK:-myXSD-2007-02-09T08-06-41 </task0_formurn>

<Modification_guid_formurn> modificationurn </modification_guid_formurn>
<Modification_guid_name> name of modification </modification_guid_name>

<Statuspageurl> _ layouts/wrkstat. aspx </statuspageurl>
</Metadata>
</Workflow>
</Elements>

The workflow subnode contained in the element is the description of the workflow attributes.
Attribute meaning of workflow:

Name: The name of the workflow. The workflow is identified in the site set function. Description: Description of the workflow. The description of the workflow is displayed. ID: ID of the workflow. The ID here is guid. You can use system. guid. newguid () is used to obtain the guid, but a program I wrote below can be used to obtain the guid, because this number is not enough for our lifetime. Codebesideclass: This attribute indicates the class in which the workflow exists. Here, my workflow exists in the applyworkflow class in the hellospwf namespace. Codebesideassembly: assembly information, that is, the Assembly deployed in GAC (Global Assembly Cache). The reflector can obtain the complete assembly information. Tasklistcontenttypeid: content type ID of the task, which generally does not need to be modified. Associationurl: the default path of the Association form. Instantiationurl: default path of the instantiation form Modificationurl: default path of the modification form The metadata of the form is saved in the metadata node, which is also a concern for us. For example, a workflow application uses a union form (used by the SPS management layer to set data information when deploying a workflow to a project ), the initialization form (the form entered by the workflow initiator) and the task processing form (the form used by the approver to process the approval information ). The form used by this workflow is uniquely identified by the urn (Uniform Resource name, which is a subset of the URI) of these forms and then stored in metadata.

Association_formurn: the urn of the Union form. Instantiation_formurn: Initialize the form's urn TaskN_ Formurn: urn of the task editing form, where N can be 0, 1, 2 ,...., the Natural Number of N indicates that the editing form is used by different tasks. For example, the editing form used by the manager may be different from the editing form used by the accountant.

Note: how to obtain the urn of the infopath form First, open the infopath form in the designed mode. 1. 2.

Content of my feature. xml <feature id = "4d44d6cb-50ac-4e2b-a15d-2d9eb0db56d2"
Title = "why?
Description = "€"
Version = "12.0.0.0"
Scope = "Site"
Receiverassembly = "Microsoft. Office. workflow. feature, version = 12.0.0.0, culture = neutral, publickeytoken = 71e9bce111e9429c"
Receiverclass = "Microsoft. Office. workflow. feature. workflowfeaturereceiver"
Xmlns = "http://schemas.microsoft.com/sharepoint/">
<Elementmanifests>
<Elementmanifest location = "workflow. xml"/>
</Elementmanifests>
<Properties>
<Property key = "globallyavailable" value = "true"/>

<! -- Value for registerforms key indicates the path to the forms relative to feature file location -->
<! -- If you don't have forms, use *. xsn -->
<Property key = "registerforms" value = "*. xsn"/>
</Properties>
</Feature>

The element in the feature node identifies the function description of the workflow:

Name: indicates the name of a node. The workflow is identified in the site set function. Description: Description of the node. The workflow description is displayed. ID: ID of the node. The ID here is guid. Elementmanifests: defines the XML file of the workflow.

From http://www.cnblogs.com/burnett/archive/2007/02/27/646965.html