Workflow. xml and feature. xml nodes

If you find Code The Section function does not have the workflow and feature options. Please refer to this article. 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:: Workflow name. The workflow is identified in the site set function. Description: Workflow description. The description of the workflow is displayed. ID: WorkflowID, HereIDYesGuid, You can useSystem. guid. newguid ()You can use one of the followingProgramTo obtainGuid, You can rest assured to retrieve, because this number is not enough for our lifetime. Codebesideclass: This attribute indicates the namespace in which the workflow exists and the class. Here, my workflow exists inHellospwfIn the namespaceApplyworkflowClass. Codebesideassembly:Assembly information, that is, the Assembly deployed in GAC (Global Assembly Cache). You can obtain the complete assembly information from reflector. 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: urn of the Union form instantiation_formurn: Initialize the form's urn task n _ formurn: urn of the task editing form, where N can be, 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:: Node name. The workflow is identified in the site set function. Description: Node description. The workflow introduction is displayed. ID: NodeID, HereIDYesGuid. Elementmanifests: defines the XML file of the workflow.