Templates
Template items identify the templates that provide users with the required information used when creating and processing Windchill objects.
Windchill provides the following types of templates (not all types of templates are available from all Windchill solutions):
• Context templates provide the required and optional administrative items that are used to create context. There are five types of context templates:
◦ Product templates define default values and other information, such as team roles and access policies, which are used when an administrator creates a product.
◦ Library templates define default values and other information, such as team roles and access policies, which are used when an administrator creates a library.
◦ Project templates define default values and other information, such as folder structure and team roles, which are used when an administrator creates a project.
◦ Program templates define default values and other information, such as folder structure and team roles, which are used when an administrator creates a program.
◦ Organization templates define default values and other information, such as folder structure and user-defined groups, which are used when an administrator creates an organization context. Each Windchill solution provides a unique set of organization templates.
• Document templates provide content files and default values, which are used when users create different types of documents. For example, content might include skeleton documents for memos or reports.
• CAD document templates define the content and default values, which are used when users create CAD documents.
• Life cycle templates define the phases and gates associated with various business objects when the objects are initialized.
• Report templates define default values, which are used when users run reports.
• Team templates define default roles, which are used when users populate teams associated with life cycles.
• Workflow templates define default values, which are used when users initiate a workflow.
• Note templates provide a starting point for creating a note from standardized text that can be associated to parts. Note templates can be modified and attachments can be associated to communicate important information about a part.
• Task form templates contain various form fields, such as labels, text fields, and radio buttons. These form fields are place holders to display the attributes of a task like variables, process name and type to the task participant. For more information, see Using Task Form Templates in a Workflow.
Installed Site Templates
The templates loaded in the site context are associated with the /System domain.
The following sections describe the templates that are loaded and how to remove or hide templates.
 |
CAD Document Templates and Note Templates appear in the list for Windchill PDMLink and Windchill ProjectLink, but do not have installed templates.
|
Organization Context Templates
When Windchill PDMLink is installed, the following organization context templates are loaded in the site context:
• General (PDM)
• DemoTemplate (not enabled)
When Windchill ProjectLink is installed, the following organization context templates are loaded in the site context:
• General
• Enterprise
• Supplier
• Customer
For additional information about organization context templates, see Out-of-the-box Organization Templates. For specific information about creating organization context templates, see Organization Templates.
Workflow Templates
The following workflow templates are loaded in the site context for all Windchill solutions:
• Submit
• Review
For Windchill PDMLink, the following workflow templates are loaded in the site context:
These templates are not used by Arbortext Content Manager.
• Problem Report Workflow
• Change Request Workflow
• Change Notice Workflow
• Change Activity Workflow
• Promotion Request Approval Process
• Promotion Request Review Process
• Variance Workflow
For Windchill ProjectLink, the following workflow templates are loaded in the site context:
• Approval Process
• Notify Process
• Release Process
• Review Process
• Two Level Approval Process
Life Cycle Templates
For the details on out-of-the-box life cycle templates, see Out-of-the-box Life Cycle Templates.
Team Templates
Team templates are used with life cycle templates.
For Windchill PDMLink, the following team templates are loaded in the site context:
These templates are not used by Arbortext Content Manager.
• Default
• Change Activity Team
• Change Notice Team
• Change Request Team
• Promotion Request Team
• Variance Team
• Problem Report Team
For Windchill ProjectLink, there are no team templates loaded.
Document Templates
For Windchill ProjectLink, the following document templates are loaded in the site context:
• Agenda Template
• Memo Template
• Minutes Template
• MS Project Plan Template
• Presentation Template
• Requirements Template
No document templates are loaded for Windchill PDMLink.
Project Templates
For Windchill ProjectLink, the following project templates are loaded in the site context:
• Custom
• Design
• General
• Manufacturing
No project templates are loaded for Windchill PDMLink.
Program Templates
For Windchill ProjectLink, the following program template is loaded in the site context:
• General
No program templates are loaded for Windchill PDMLink.
Product Templates
For Windchill PDMLink, the following product templates are loaded in the site context:
• Demo Product Template (not enabled)
• General Product
• Product Design
No product templates are loaded for Windchill ProjectLink.
If Windchill MPMLink is installed then additional product and design templates are available.
Library Templates
For Windchill PDMLink, the following library templates are loaded in the site context:
• Document Library
• General Library
• Part Library
No library templates are loaded for Windchill ProjectLink.
Report Templates
For Windchill PDMLink, the following report templates are loaded in the site context:
These templates are not used by Arbortext Content Manager.
• All Average Change Notice Completion Time
• All Average Change Request Completion Time
• All Average Problem Report Completion Time
• All Change Notice Influx and Resolution
• All Change Request Influx and Resolution
• All Open Change Notices
• All Open Change Requests
• All Open Problem Reports
• All Problem Report Influx and Resolution
• Average Change Notice Completion Time
• Average Change Request Completion Time
• Average Problem Report Completion Time
• Change Notice Influx and Resolution
• Change Request Influx and Resolution
• Change Request Track Breakdown
• ChangeNotice_ChangeAdmin_Given
• ChangeNotice_ChangeAdmin_NotGiven
• ChangeRequest_ChangeAdmin_Given
• ChangeRequest_ChangeAdmin_NotGiven
• Domain Reports
• Open Change Notices
• Open Change Requests
• Open Problem Reports
• Overdue Running Processes
• Problem Report Influx and Resolution
• ProblemReport_ChangeAdmin_Given
• ProblemReport_ChangeAdmin_NotGiven
• Process Initiated by Current User
• Variance_ChangeAdmin_Given
• Variance_ChangeAdmin_NotGiven
For Windchill ProjectLink, the following report templates are loaded in the site context:
• Project Action Items
• Project Activities
• Project Deliverables
• Project Milestones
• Project Summary Activities
• Project Tasks
• Project-Program Status Report Query
• Projects Created Query
• Projects Owned Query
Task Form Templates
The following task form templates are loaded in the site context for all Windchill solutions:
|
Primary Business Object Class
|
Type
|
Name
|
|---|---|---|
|
wt.fc.WTObject
|
XDP
|
default
|
|
wt.fc.WTObject
|
JSP
|
default
|
|
wt.fc.WTObject
|
Native
|
default
|
|
wt.change2.WTChangeRequest2
|
Native
|
Analyze Change Request
|
|
wt.change2.WTChangeOrder2
|
Native
|
Audit Change Notice
|
|
wt.change2.WTChangeActivity2
|
Native
|
Complete Change Notice Task
|
|
wt.change2.WTChangeRequest2
|
Native
|
CRB Review Change Request
|
|
wt.change2.WTChangeActivity2
|
Native
|
Review Change Notice Task
|
|
wt.change2.WTChangeIssue
|
Native
|
Review/Approve Problem Report
|
|
wt.maturity.PromotionNotice
|
Native
|
Review/Approve Promotion Request
|
|
wt.change2.WTVariance
|
Native
|
Review/Approve Variance
|
Editing Templates
To edit templates, navigate to the Templates table by clicking the Templates link within a specific context and then select the type of template from the table view drop-down list. The list of templates that are available from the context appears in the table. Each type of template has its own method of editing the templates. Generally, editing can be initiated either by clicking an icon at the top of the Templates table or selecting an action from a row in the table.
For details on templates and how to edit them, see the help that is available from the Templates table. For specific information about editing context templates, see Context Templates.
Removing, Hiding, or Disabling Templates
You can remove, hide, or disable the templates that have been loaded. If you do not want a template to be used by anyone, PTC recommends that you disable the use of the template instead of removing it. By disabling it, the template is not available for use in any context, but remains in the system in case it is needed in the future. If you do not want a template to be used in a specific context, but want to allow its use in other contexts, you can hide the template in the specific context and show the template in other contexts.
To view the templates that have been loaded, select Site 
> . Select the type of template from the view drop-down list to display the templates in the table. You can then use the disable row action to make individual templates unavailable throughout the user interface or use the hide action to hide the visibility of individual templates in a specific context.
> . Select the type of template from the view drop-down list to display the templates in the table. You can then use the disable row action to make individual templates unavailable throughout the user interface or use the hide action to hide the visibility of individual templates in a specific context.For additional help on template actions, click the help icon on the Templates table to display the templates help.
Managing Document Template Preferences
When your Windchill solution is installed, default preference settings for document templates are established. For example, the default name of a document that is created from a template is set in the Document from Template Filename preference. You can change the defaults to better meet the needs of users by opening the Preference Management utility from within the context in which you want the settings to take effect. Document template preferences are listed under the Documents category.