The CAD data management functionality referred to in the out-of-the-box profiles is controlled by the action, View Related CAD Documents in the set action visibility list.

Profile Actions and User Interface Elements

When creating a profile, you can specify visibility at the global level or by making specific actions and user interface elements visible within a specific application context.

The Set Action Visibility step displays a list of all the actions and user interface elements that can be hidden or made visible in a profile. The actions and user interface elements are displayed based on the application context in which they reside in the user interface, for example, the Products , Projects, Libraries, and Programs contexts.

Within each column, visibility can be given to all or only a subset of actions or user interface elements within a specific application context by selecting the corresponding checkbox.

For more information on setting visibility of the actions, see help available in the

Participant Administration utility.

Visibility can also be specified at the global level using the Global column in the Edit Profile window. For example, if you are creating a profile where visibility should be given for everything in the Change and Library contexts, you can select the checkboxes in the Global column for View Library Tab and View Change Tab.

The global settings are available for profiles only and cannot be modified in a context instance. Application context managers can only modify the action list that is applicable to their active context.

Default Settings for Actions

Out-of-the-box, most of the actions and user interface elements are selected by default. That is, they are made visible by default in a profile unless the administrator deselects the corresponding checkbox.

The following table lists the out-of-the-box actions that are deselected by default, unless an administrator specifically grants visibility by selecting the checkboxes:

This section introduces basic concepts about context teams, shared teams, and team templates.

For more information, see the Teams and Roles help and the Team Template Administration help.

299

Overview

Windchill teams are made up of participants and can be associated with objects, a context, or, in the case of team templates, life cycle or workflow processes.

•When business objects (such as parts and documents) are created, a unique team is created as its own object and is associated with the business object. The team contains all the roles consolidated from the team, life cycle, and workflow templates. The roles then get mapped to users.

•At the context level, the manager can create a context team specific to a particular project, library, program, or product. Each context team identifies the members of the specific project, library, program, or product and assigns the members to roles that have been established in the context. Each context team can be made up of a local team, a shared team, or the combination of a local team and shared team. Context teams are also used when creating the team and team roles associated with a specific business object.

•A team template can map participants and actors to roles. The team template can be assigned to a life cycle or workflow-managed business object, when it is created, to use as a template for roles resolution for the team.

For more information, see the Teams and Roles help and Team Template Administration help.

Context Teams

A context team is a list of the members of a project, program, product, or library context. Using the Teams page for the context, a context manager can manage the team by adding users to roles and creating additional roles within the team.

For more information, see the Teams and Roles help.

Shared Teams

Depending on how a context team is set up, team members can be added individually or they can be part of a shared team. Shared teams are created in an organization context and can be used by multiple application contexts within the organization. Using shared teams rather than adding all users individually to each context team can reduce the work of maintaining multiple context teams. Like context teams, shared teams have established roles available and additional roles can be added. Changes made to a shared team’s members or roles are immediately evident in context teams that use the shared team. Shared teams can only be added when a context is created.

For more information, see the Teams and Roles help.