Index to XML Element Definitions for Process Template Plug-ins
By using the index of elements in this topic, you can look up the syntax structure and find examples of how to use each element of the schema definition for process templates.
In this topic
Alphabetical Index
Elements That Define the Root Plug-in for Process Templates
Elements That Define Plug-in Tasks
Type Definition Elements That Define Objects for Tracking Work
Warning
The schema definition for process templates uses a mix of camel-case and all capitalized elements. If you encounter errors when validating your type definition files, check the case structure of your elements. Also, the case structure of opening and closing tags must match according to the rules for XML syntax.
Alphabetical Index
|
|
|
Back to top
Elements That Define the Root Plug-in for Process Templates
The ProcessTemplate file contains two main parent elements within the ProcessTemplate root element: metadata and groups. The syntax for each of the following elements and their child elements is described in ProcessTemplate XML Elements Reference.
metadata: description, nnname, plugin, plugins
groups: dependencies, dependency, group, tasklist
Back to top
Elements That Define Plug-in Tasks
You use the tasks element and its child elements to define the artifacts to be uploaded or specific elements to be created for each plug-in. You can access the topic that provides detailed information and examples for each plug-in and element in the following table.
Plug-in |
Related topic |
Elements |
|---|---|---|
All |
dependencies, dependency, ProcessTemplate, task, tasks, taskXml |
|
Build |
Permission, ProcessTemplate |
|
Classification |
Define the Initial Areas and Iterations in the Classification Plug-in |
Children, Node, Nodes, properties, property |
Groups and Permissions |
group, groups, member, members, permission, permissions |
|
Lab |
Permission, ProcessTemplate |
|
Portal |
activateFeatures, documentLibraries, documentLibrary, feature, file, files, folder, folders, Portal, site |
|
Reports |
datasources, folder, folders, parameter, parameters, properties, property, reference, report, reports, ReportingServices, site |
|
Test Management |
dependencies, dependency, TestConfigurations, TestResolutionState, TestSettings, TestVariables |
|
Version Control |
Define the Initial Configuration of Team Foundation Version Control |
checkin_note, exclusive_checkout, get_latest_on_checkout, permission |
Work Item Tracking |
Define and Customize Objects for Tracking Work Items By Using the Work Item Tracking Plug-in |
CATEGORIES, FIELD, GLOBALLISTS, HYPERLINK, LINKTYPE, LINKTYPES, Permission, Query, QueryFolder, QUERIES, WI, WORKITEMS, WORKITEMTYPE, WORKITEMTYPES |
Back to top
Type Definition Elements That Define Objects for Tracking Work Items
In the Work Item Tracking plug-in, you can specify several type definition files and query definition files to upload. You can access the topic that provides detailed information and examples for each object and element in the following table:
Object |
Related topic |
Elements |
|---|---|---|
Categories |
CATEGORIES, CATEGORY |
|
Global lists |
GLOBALLIST, GLOBALLISTS, LISTITEM |
|
Link types |
LinkType, LinkTypes |
|
Work item queries |
TeamFoundationServer, TeamProject, Wiql, WorkItemQuery |
|
Work item types |
Top level elements only: DESCRIPTION, FIELDS (Definition), FORM, GLOBALLISTS, WITD, WORKFLOW, WORKITEMTYPE |
Back to top
See Also
Concepts
Work Item Type Definition Localization and Globalization
Determine the Scope of Your Customization Requirements
All WITD XML Elements Reference
Customize Project Tracking Data, Forms, Workflow, and Other Objects