The primary method for allocating users to roles is by using the context team. You can find the team on the Team page of Products or Libraries . Both out-of- the-box product templates define two context roles, Promotion Approvers and Promotion Reviewers, to work with the promotion process. These context team roles, along with role mapping, copy any users and user-defined groups from these roles into the team instance of the promotion request at creation. When a new product is created, the Promotion Approvers role is empty; any approval tasks are sent to the promotion request creator unless this role (or another mapping) is properly defined. For each product, resolve at least one user into the promotion request team instance for the Approver role to ensure that a proper approval is obtained prior to promotion. Out-of-the-box, this can be done in the following ways:

•Adding the approver to the Promotion Approvers role of the context team

•Modifying the team template to have a default participant for the Approver role

•Modifying the preference mapping to add additional roles for the Approver role, ensuring that at least one user is assigned to at least one of the roles in the context team.

Life Cycle Teams in Windchill ProjectLink

When routing a life cycle managed object in Windchill ProjectLink, only the members of the context team roles that match the life cycle phase roles will be pulled into the life cycle team. The entire context team is no longer pulled into the life cycle team. This is the default behavior for the wt.property file (wt.team. addEntireContainerTeam).

A message will be thrown if a user tries to create an advanced life cycle template via the Life Cycle Template Administration utility and does not associate a workflow template to the life cycle phases or gates. In this case, the message requests the user to change the life cycle template from advanced to basic for better performance and scalability.

Restrictions on Moving Objects Between Contexts

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.

336	PTC Windchill® Basic Administration Guide

Note

For demonstration purposes, the Product Design template (available by default when you create a product) includes object initialization rules that set different default life cycle templates and versioning schemes for parts, documents, and CAD documents than are set out-of-the-box at the site level. This template demonstrates the use 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.

Understanding Life Cycles

337