Document to Document Relationships

There are several different types of document to document relationships in your Windchill solution:

•A document can reference another document from the Related Objects tab on the document information page. This relationship creates a link of type WTDocumentDependencyLink.

•A document can serve as the parent to a second child document from the Structure tab on the document information page. This relationship creates a link of type WTDocumentUsageLink.

There are no configuration options available for document to document relationships.

Best Practices for Object Initialization Rules

Although you can set object initialization rules for individual product and library contexts, consider the consequences of doing this.

For most sites, the recommended approach is to set the rules at either the organization or site level so that an entire organization or site is using the same set of rules.

If you choose to set different rules in a product or library context, be aware that the ability to move objects between contexts may be restricted. Specifically, if you create a life cycle template in a specific product or library and the template is not available in other products or libraries, then you cannot move any object that uses the life cycle template. The same is true if the team template is unique to a product or library; objects using the team template cannot be moved. Similarly, the versioning scheme used for an object must match the scheme set in the destination product or library or the object cannot be moved.

Note

For demonstration purposes, the Product Design template (available by default when you create a product) includes object initialization rules that sets different default life cycle templates and versioning schemes for parts, documents, and CAD documents than is set out-of-the-box at the site level. This template demonstrates the used of simplified life cycles and state-based versioning. Unless you have overriding business practices that require unique rules, PTC recommends that if you want to use these features, you modify the organization or site object initialization rules and remove them from the Product Design template.

8

Understanding Projects and

Programs

This section provides an overview for administering projects and programs and describes the typical duties that an administrator performs. It also provides additional information about some of the main administrative tasks for projects and programs.

For more information, see the Project and Program Administration help topics.

237

Project and Program Administration

Overview

Project and program managers (also known as project and program administrators) are responsible for creating and managing projects and programs hosted by a parent organization. The capabilities of project and program managers are nearly identical.

Project and program managers control the project and program configuration, and control the membership in their project and program teams within the confines of a specific project or program application context. They control access to project and program information; they define the schedule, resources, and plan details, and monitor and manage the project and program activities.

Project application contexts are online work areas used to collect information that teams need to track, collaborate, and manage as well as plan work activities to meet a specific objective. Project contexts are defined by project creators who are authorized by the parent organization. Projects inherit templates, roles, userdefined groups, and policies from their parent organization context. The project manager can also define project-specific templates, roles, and policies.

Program application contexts provide a central area to link together information, people, and plans for a series of projects. Program contexts are defined by program creators who are authorized by the parent organization. Programs inherit templates, roles, user-defined groups, and policies from their parent organization context. The program manager can also define program-specific templates, roles, and policies.

Note

By default, programs are hidden. To make programs visible and available for use in your Windchill solution, a site administrator can set the value of the

preference to “No”. This preference is available from the Preference Management utility on Site Utilities. For more information on using the Preference Management utility, see help available from the

Preference Management utility.