Basic Administration > Managing Data > Product and Library Administration > Working with Products and Libraries > Product and Library Utilities
Product and Library Utilities
The utilities listed on the Products > Utilities and Libraries > Utilities allow you to perform administrative actions at a product and library level. The same set of utilities appears on both Products > Utilities and Libraries > Utilities. The difference is the context from which each utility is launched:
• Clicking a link from Products > Utilities launches the utility within the context of the current product.
• Clicking a link from Libraries > Utilities launches the utility within the context of the current library.
The utilities are grouped according to whether they are system administration utilities or business administration utilities.
System Administration
The System Administration links provide access to the administration of the environment in which your Windchill solution runs relating to a specific product or library, such as external storage of data and the control over generating visualization information. These links are described below:
Administration Link
Description
(Windchill PDMLink only) This utility manages the exchange of file data and metadata with other systems using XML files.
(Windchill PDMLink only) This utility manages the collaboration of design data with other Windchill systems using importable package delivery files.
This utility manages the mapping of attributes between a sending system and your system when importing package delivery files.
Business Administration
The Business Administration links provide access to the administration of business objects within your Windchill solution relating to a specific product or library, such as data importing and exporting, life cycles, and workflow. These links are described below:
Administration Link
Description
This utility allows you to view the available business rules.
Displays information on how to define business object numbering schemes relating to the current product or library.
Displays information on how to control identifiers generated for object versions relating to the current product or library.
This utility allows you to create and manage life cycle templates used for defining the phases and transitions of various business objects.
This utility allows you to create and manage rules for object initialization that set default values for object attributes relating to the current product or library.
This utility allows you to manage administrative domains and their access control, indexing, and notification policies.
This utility allows you to view and set the preferences for your product or library.
This utility allows you to view and edit promotion preferences.
This utility allows you to control the generation of visualization objects in the current product or library context.
This utility allows you to create, update, and delete reports using the Query Builder tool. A report is the output of a predefined search and is used for generating statistics and metrics against business information.
This utility allows you to create and manage team templates. When creating a life cycle-managed object, you can use a team template as a base for the team participants throughout its life cycle.
This utility manages the visualization configurations including watermark files and publish rules in the current product or library context.
(Windchill PDMLink only) This utility allows you to create and manage workflow templates.
(Arbortext Content Manager or Windchill PDMLink only) This utility allows you to search for workflow processes, view activity and task level details, restart stalled workflows, and terminate or delete workflows.
(Windchill PDMLink only) This utility allows you to search for workflow processes, view activity and task level details, restart stalled workflows, and terminate or delete workflows.
This utility allows you to view the status of visualization publish jobs in the current product or library context.
This utility allows you to create and execute WVS jobs in the current product or library context.
Was this helpful?