Using Current Library Context as a Template
The library context provides the framework from which user actions are executed. When you create a library, you establish this initial framework by selecting a library template. Although your Windchill solution provides a set of out-of-the-box templates, you can also create a template that can then be used by your organization or the entire site. The recommended method for creating a library template is to create a library using an existing template and then modify the library settings. After the modifications are complete, select either of the following actions from the actions list on the information page of the library:
• The Export as Template action is available to the product and library managers as well as the site and organization administrators from the right-click actions menu for the library on the Libraries table or the Actions menu on the library information page. The action allows you to export the current library as a template, creating a ZIP file on your system. Using the ZIP file as the content for a new template, you can then create the template in the site or an organization context (if you have the correct access permissions). For information on creating library templates, see Working With Context Templates.
• The Save as Template action is available to site and organization administrators, and provides a way to create a new template from the current library. The newly created library template appears in the current organization Templates table when the Current View is Library Templates.
Selecting either of these actions opens a window from which you can do the following:
• Name the template that is being exported or saved.
• Enter a description of the template.
• Select which of the following items to include in the template data file:
◦ Folder Structure (not including the folder contents)—If you created a domain structure, the structure is exported through this option. Also, if you are using folder domains, these folders are exported. Folder domains are available when the > preference is set to true.
◦ Team Members—If the team uses a shared team, then the shared team member information is included when you select this check box.
◦ Document Templates
◦ Object Initialization Rules
◦ Template Visibility—If you have hidden some templates in the context, then this information is included when you select this check box.
◦ Preferences
 |
Access policy rules and team roles are automatically included in the template.
|