Required Contents of Files Used to Create a Context Template
When creating a context template from the Templates table using the new template icon 
, you must supply a file containing the content of the template. The input file can be just the business XML file if no additional content is needed or it can be a ZIP (or JAR) file that has both the business XML file and other content files named in the XML file.
, you must supply a file containing the content of the template. The input file can be just the business XML file if no additional content is needed or it can be a ZIP (or JAR) file that has both the business XML file and other content files named in the XML file.The input file you provide in the create operation is not the same as the file used for importing. For a create operation, you can use a file that you manually create; however, PTC recommends that you always start with a business XML file that you have either downloaded or located in the Windchill installation directory. If you do use one of the Windchill load files as your starting point, PTC recommends that you do not modify the ENTITY tags in the file nor modify the content of any of the XML files referenced in the ENTITY tags.
The following sections describe the contents of the files you can use as input when you create context templates using the new template icon .
.Organization Templates
The only option available for creating an organization template is to create the input file manually and create a new template. For more information, see Methods of Creating Additional Context Templates.
You can include the following administrative items in a new organization template:
• Additional domains, folders, user-defined groups, and access control policy rules for the organization. The access control rules can include rules set for the dynamic roles that are available in the organization context. For additional information, see Using Dynamic Roles.
• Additional product, library, program, and project templates that are available from the organization.
• Object initialization rules.
• Project roles (if the organization is used with Windchill ProjectLink).
Product and Library Context Templates
When using any of the options for creating templates, you can include the following administrative items in a new product or library template:
• Domains
• Folder structure (not including the folder contents)
• Team roles (including role access to actions)
• Team members
• Document templates
• Object initialization rules
• Access control policy rules
• Template visibility
• Preferences
Program and Project Context Templates
When using any of the options for creating templates, you can include the following administrative items in a new program or project template:
• Domains
• Folder structure (not including the folder contents)
• Folder links and structure
• Project or program plan
• Deliverables
• Team roles (including role access to actions)
• Team members
• Documents
• Document templates
• Discussion specification
• Discussion template
• Object initialization rules
• Template visibility
• Shared objects in a project (if any have been created in an existing project that is exported)
• Preferences
Additionally, you can save an existing project (or program) as a new project (or program). Using this option creates a duplicate of a project (or program) under a new name.