○Additionally, there are marketing and engineering roles that are unique to this template that can be used to delineate those functions in the design process.

○Access policies defined for Change Objects have been setup to work in conjunction with the closed-loop change process.

○Members of the Guest role are granted Read access to all objects.

•General Product and General Library – These templates provide examples of how to setup basic access control for a general product or library context. As described in detail later in this section, the default set of roles defined is Members, Promotion Reviewers, Collaboration Manager, Variance Approvers, Promotion Approvers, Option Administrator, Package Creator, Change Review Board, Change Admin I, Change Admin II, Change Admin III, and Received Delivery Manager. Also, the Guests and Product/Library Manager roles are created automatically. Some basic information about these roles is a follows:

○The Members role is used as a basic role to grant context team membership. A set of access rules are defined for confirmed members of the context team.

○Access policies defined for Change Objects have been setup to work in conjunction with the closed-loop change process.

○Members of the Guest role are granted Read access to all objects.

The product and library templates can define the same basic information that is discussed in Context Administrative Items on page 61 If you want to create a new. product or library template, see Understanding Context Templates on page 393

Product Design Template

The Product Design out-of-the-box template defines the following context administrative items:

• Promotion Requests subfolder in the Default domain

• Context participation

• Context access control policies

• Object initialization rules for the following objects:

○ wt.maturity.PromotionNotice

○ wt.part.WTPart

○wt.epm.EPMDocument

○wt.doc.WTDocument

Through the object initialization rules, the following life cycle templates are set as defaults in the Design Product template:

•Two Phase Development life cycle template - default template for parts and functional specifications. It has the following states:

•One Phase Development life cycle template - default template for documents and CAD documents. It has the following states:

Note

Although you can use multiple life cycle templates within a product context as is done with the demonstration Product Design template, PTC recommends that you become familiar with the functionality available through these life cycle templates and select one of the out-of-the-box templates (or create your own template) to use for all life-cycle managed objects in a product context.

The Two Phase Development and One Phase Development life cycle templates have the following transitions defined: Lock, Revise, Promote, Change, and Set State. Each template establishes different transition rules out of the box.

The following diagrams show the out-of-the-box transition rules for the Two Phase Development life cycle:

The following diagrams show the out-of-the-box transition rules for the One Phase Development life cycle:

For additional information about modifying or creating life cycle templates, see Understanding Life Cycles on page 299 The out-of-the-box workflows that are . used with the default life cycle templates are:

Out-of-the-box Subfolder for wt.maturity.PromotionNotice Objects

In the Default cabinet and Default domain, the Product Design template creates the Promotion Requests subfolder. This folder is then defined as the default folder for the wt.maturity.PromotionNotice object type. Creating and using this folder is not required, but provides a useful folder for promotion requests.

Out-of-the-box Context Participation

The Product Design template defines roles that are automatically included in product teams. These roles are the roles that automatically appear on the Members table. Additionally, roles available through the organization context can be added manually to the team.

The following roles are automatically included in the team:

•Product Manager

•Guest, which is the role to use for users who you do not want as a member of the team, but you do want them to have limited access to the product.

The out-of-the-box Product Design template adds the following roles to the team:

•Members, which is a role that can be used for team members who do not belong in other roles on the team.

•Change Admin I, which is the change administrator I change management role.

•Change Admin II, which is the change administrator II change management role.

•Change Admin III, which is the change administrator III change management role.

•Promotion Reviewers, which are the team members for reviewing promotion requests.

•Promotion Approvers, which are the team members for approving promotion requests.

•Change Review Board, which are the team members of the Change Review Board.

•Design Team Leader, which is the Design Team Leader role. This role is unique to this template.

•Designer, which is the role used to create, edit and manage business objects within the system. This role is unique to this template.

•Manufacturing Engineer, which is the Workflow Manufacturing Engineer role. This role is unique to this template.

•Marketing, which is the Marketing role. This role is unique to this template.