Teamcenter 10.

Rich Client Interface Guide

Publication Number
PLM00191 J
Proprietary and restricted rights notice

This software and related documentation are proprietary to Siemens Product

Lifecycle Management Software Inc.
© 2013 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenter
is a trademark or registered trademark of Siemens Product Lifecycle Management
Software Inc. or its subsidiaries in the United States and in other countries. All
other trademarks, registered trademarks, or service marks belong to their respective
holders.

2 Rich Client Interface Guide PLM00191 J

Contents

Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2

Getting started with the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Getting started with the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Basic concepts for using the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Basic tasks using rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Choose a display language for the rich client . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Start a Teamcenter rich client session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Rich client interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Teamcenter rich client perspectives and views . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Using the Getting Started application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Localizing property values in Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Managing the Teamcenter client interface . . . . . . . . . . . . . . . . . . . . . . . 2-1

Managing the Teamcenter client interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Using application perspectives and views in your rich client session . . . . . . . . 2-1
Opening application perspectives in the rich client . . . . . . . . . . . . . . . . . . . . 2-1
Views available to rich client application perspectives . . . . . . . . . . . . . . . . . . 2-15
Managing views, layouts, and view networks . . . . . . . . . . . . . . . . . . . . . . . . . 2-73
Rich client menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79
Working with the rich client navigation pane . . . . . . . . . . . . . . . . . . . . . . . . 2-91
Customizing the toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-101
Changing user settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-103
Using the information center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-107
Using the Launch Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-109
Cutting, copying, pasting, and deleting data objects . . . . . . . . . . . . . . . . . . . 2-110
Dragging and dropping data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-113
Using the Localization button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-115
Organize data in folders and pseudofolders . . . . . . . . . . . . . . . . . . . . . . . . . 2-115
User interface panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-124
Configuring table data display in the rich client . . . . . . . . . . . . . . . . . . . . . . 2-129
Printing information about your data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-130
Using preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-140
Working with preferences in the rich client . . . . . . . . . . . . . . . . . . . . . . . . . 2-145
View and set rich client Eclipse window preferences . . . . . . . . . . . . . . . . . . 2-156
Working with rich client persistent caches . . . . . . . . . . . . . . . . . . . . . . . . . 2-157
Working with the FMS server cache (FSC) and FMS client cache (FCC) . . . . . 2-159

Searching in Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Searching in Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Using quick search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Using the Search view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Using the Simple Search view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

PLM00191 J Rich Client Interface Guide 3

Contents

Using the Search Results view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Using full-text searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Combining full-text search with metadata queries . . . . . . . . . . . . . . . . . . . . . 3-26
My Saved Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Search techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Using search pane buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Using search pane tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Creating property finder formatter (PFF) objects . . . . . . . . . . . . . . . . . . . . . . 3-47
Where-used and where-referenced searches . . . . . . . . . . . . . . . . . . . . . . . . . 3-49

Using the Application Interface Viewer . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Using the Application Interface Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Understanding Application Interface Viewer objects . . . . . . . . . . . . . . . . . . . 4-1
Tracking requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Share data with the external application . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Open the Application Interface Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Using incremental changes with requests . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Administering data transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Option reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Option reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
NX Remote Manager (AIE) options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
ARM Transaction Monitor options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Content Management options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Cross Probing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Dataset options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Generic Relationship Manager (GRM) options . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Integration for I-deas options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
List of values (LOV) options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Live update options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Logging options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Mail options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Manufacturing Process Management (ME) options . . . . . . . . . . . . . . . . . . . . 5-14
NX options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Product Structure options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Project options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Refresh notify options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
STEP Translator options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Security options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Status indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
System options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Systems Engineering options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Work Breakdown Structure (WBS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Computer-Aided Engineering (CAE) Tools options . . . . . . . . . . . . . . . . . . . . . 5-28
Calendar options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Change Management options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
DesignContext options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
General options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Graphical BOM Compare options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
Multi-Site Collaboration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
Search options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Visualization options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
Workflow options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56

4 Rich Client Interface Guide PLM00191 J

 Contents

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

PLM00191 J Rich Client Interface Guide 5

Chapter

1 Getting started with the

rich client

Getting started with the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Basic concepts for using the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Basic tasks using rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Choose a display language for the rich client . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Start a Teamcenter rich client session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Logging on to the Teamcenter rich client . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Rich client interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Teamcenter rich client perspectives and views . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Using the Getting Started application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Localizing property values in Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Viewing, editing, and adding translations for a property using the Localization
button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

PLM00191 J Rich Client Interface Guide

Chapter

1 Getting started with the

rich client

Getting started with the rich client

The Teamcenter rich client, a platform-independent client implementation (Java
application) for users who interact frequently with Teamcenter, runs on client hosts
and serves as a gateway to your company’s product information.
• The rich client provides a broad selection of application perspectives and views
to manage your product information.

• The rich client accesses Teamcenter databases using a remote or local server.

• You can integrate and run Teamcenter’s product data management perspectives
along with applications such as Microsoft Office, custom applications, Java
plug-ins, or CAD/CAM/CAE applications, all from a common platform.

• You can use the rich client to maintain Teamcenter, design and configure product
data, and create processes and process structures.

Many of the capabilities provided by the rich client are available in other clients
such as the thin client, as described in Thin Client Interface Guide and various
third-party products, such as Microsoft Excel, as described in Extensions for
Microsoft Office Guide.
For an overview of Teamcenter functionality and clients, see Getting Started with
Teamcenter.

Before you begin

Prerequisites Any standard Teamcenter user account can run the rich client.
Certain features of the rich client must be activated by
installation of an appropriate license file, including various
functionality levels for Teamcenter lifecycle visualization and
the Embedded Software Solutions. Specific license requirements
are described in the relevant topics in this guide and in
application-specific documentation.

PLM00191 J Rich Client Interface Guide 1-1

Chapter 1 Getting started with the rich client

Enable rich The rich client application is deployed on workstations by

client Teamcenter Environment Manager or by the Over-the-Web
Installer, depending on which Teamcenter network architecture
you use. Rich client does not need to be enabled before you
use it, but your administrator must create an account for you
to log into the system.
For information about deploying the rich client, see the
appropriate installation guide for your environment.
If you have trouble accessing an application in the rich client,
see your system administrator. It may be a licensing issue.
Configure rich You can set various preferences (options) to configure the
client user interface and certain default functions to suit your
requirements. These preferences are stored in your personal
preference file in the Teamcenter database. In addition, the
system administrator sets site preferences that configure
other user options to the same values for all users. Group
administrators may also set preferences that configure user
options for all users in a group.
Set your user preferences by choosing the Edit→Options menu
command and selecting the appropriate preference.
For more information about setting preferences, see Using
preferences and the Preferences and Environment Variables
Reference Guide.

Basic concepts for using the rich client

The rich client is a platform-independent client implementation (Java application)
for users who interact frequently with Teamcenter.
The rich client:
• Runs on client hosts and serves as a gateway to your company’s product
information.

• Accesses Teamcenter databases using a remote or local server.

You can integrate and run Teamcenter product data management application
perspectives along with applications such as Microsoft Office, custom applications,
Java plug-ins, or CAD/CAM/CAE applications, all from a common platform.

Basic tasks using rich client

Use the rich client to:
• Work with Teamcenter applications perspectives and views.

• Create and manage data.

• Print information about your data

1-2 Rich Client Interface Guide PLM00191 J

 Getting started with the rich client

• Search for data in the Teamcenter database.

• Exchange data between Teamcenter and external applications.

• Set options and preferences.

Choose a display language for the rich client

By default, the rich client is displayed in the language specified by the operating
system.
Note • Your ability to set the language for the rich client depends on the
character set encoding of the Teamcenter server host and also the
character set encoding of the Teamcenter database.
For more information about configuring language display during
installation, see the appropriate server installation guide (for Windows
or UNIX/Linux).

• If you find that Asian multibyte characters do not display correctly in the
rich client, set your system font to a font that supports Asian multibyte
characters. For example, on Microsoft Windows systems, the Arial
Unicode MS font can be set to Message Box to correct this problem.
Similarly, if you find that Asian multibyte characters do not display
correctly when you start the rich client using the native language (-nl)
option, restart your system in the appropriate locale and set your system
font to a font that supports Asian multibyte characters.

If you want to override the default language to launch the rich client in a desired
language, add the -nl argument to the rich client launch command:
• Windows systems:
TC_ROOT\portal.bat –nl locale-code

• Linux systems:
TC_ROOT/start_portal –nl locale-code

Replace TC_ROOT with the Teamcenter home directory, and replace locale-code
with the desired locale code listed in .
For example, to launch the rich client Italian user interface, enter the following
from a command prompt:
• Windows systems:
D:\tc\rac\portal.bat –nl it_IT

• Linux systems:
/tc/rac/start_portal –nl it_IT

Alternatively, on Windows systems, you can customize the properties for the
Teamcenter rich client desktop shortcut icon to specify a desired language:

PLM00191 J Rich Client Interface Guide 1-3

Chapter 1 Getting started with the rich client

1. On your desktop, right-click the Teamcenter rich client shortcut icon .

2. Choose Properties.
A properties dialog box is displayed.

3. Click the Shortcut tab.

4. In the Target box, add an -nl argument to specify the desired language.
The -nl argument accepts a single string as value. The string must be one of the
locale codes listed in .
For example, to run the rich client Italian user interface:
D:\tc\rac\portal.bat

becomes:

D:\tc\rac\portal.bat —nl it_IT

Note To prevent mixed-language display the next time you run the rich client
after you change the -nl argument value, or after you change your operating
system locale, delete the Teamcenter directory under your user directory.
• On Windows clients, delete:
C:\Documents and Settings\user-name\Teamcenter

• On Linux clients, delete:

$HOME/Teamcenter1

Start a Teamcenter rich client session

• Choose Start→All Programs→Teamcenter→Teamcenter or double-click the
Teamcenter icon on your desktop.
Note Your Teamcenter client may be installed so the menu items include a
version number, such as Teamcenter 10.1.

Tip If you do not have a Teamcenter shortcut icon:

1. Choose Start→All Programs→Teamcenter→Teamcenter, and right-click
Teamcenter.

2. Choose Send To→Desktop (create shortcut).

For information about command line options for rich client startup, see the Client
Customization Programmer’s Guide.

1. $HOME is your user home directory.

1-4 Rich Client Interface Guide PLM00191 J

 Getting started with the rich client

Logging on to the Teamcenter rich client

The rich client logon window has the following fields:
• User ID
This is a required value. User accounts are created by administrators in the
Organization application.
You must provide a valid account ID to interact with Teamcenter.

• Password
This is a required value. Passwords are created by administrators in the
Organization application.

• Group
This is an optional value. A group is an organizational collection of users who
share data. A user account can belong to multiple groups and must be assigned
to a default group. Groups are created by administrators in the Organization
application. If you do not specify a group, the default group associated with the
user account is used.

• Role
This is an optional value. Function-oriented cluster of users that models skills
and/or responsibilities. The same roles are typically found in many groups. Roles
are created by administrators in the Organization application. If you do not
specify a role, the default role associated with the group is used.

• Server
Specify the server to provide database access for your rich client session. Servers
are configured during installation.

For information about users, passwords, groups, and roles, see the Organization
Guide.
Note Depending on whether your site uses proxy servers, multiple environments,
or Security Services components such as single sign-on, you may be required
to select an environment or respond to one or more additional authentication
dialog boxes.

Rich client interface

The rich client interface has a standard menu bar and toolbar with options that vary
depending on the currently active application perspective. You can place the cursor
over a rich client toolbar button to display a tooltip description.

PLM00191 J Rich Client Interface Guide 1-5

Chapter 1 Getting started with the rich client

1 Back and The Back and Forward buttons allow you to move between
Forward buttons loaded Teamcenter applications. The small arrows next
to the buttons let you select from the list of currently
loaded applications.
For more information about moving between loaded
applications, see Switch between open perspectives.
2 Application The application banner shows the name of the active
banner application and lists the current user and role. You can
double-click the user and role to display the User Settings
dialog box in which you can change your current role if
multiple roles are available to your user.
For information about User Settings options, see
Changing user settings.
3 Search box The Search box provides predefined quick searches
using dataset, item ID, item name, keyword search, and
advanced search features.
For more information, see Searching in Teamcenter.

1-6 Rich Client Interface Guide PLM00191 J

 Getting started with the rich client

4 Navigation pane The navigation pane provides quick access to the data
you use most. In addition to finding, organizing, and
accessing your data, you can configure the display of the
Teamcenter perspective buttons in the navigation pane to
display only those perspectives that you use regularly to
perform your tasks.

Click the reorder button above the Search box to

display the Navigation Section Ordering dialog box that
lets you hide sections or change the order of sections in
navigation pane.
For information about configuring the navigation pane,
see Working with the rich client navigation pane.
5 Application pane The application pane displays the application perspectives
that are open in your Teamcenter session. By default, the
Getting Started application perspective displays a single
Getting Started view.
Note Application perspectives are composed of views
that can be moved elsewhere in the Teamcenter
window, or can be dragged out to the desktop.
Such detached views remain connected to
Teamcenter and continue to function in concert
with other views.
6 Getting Started Provides access to the Getting Started application.
application
button
7 Primary Primary application buttons provide access to your most
applications frequently used Teamcenter application perspectives.
8 Secondary Secondary application buttons provide access to
applications Teamcenter application perspectives you use infrequently.
9 Clipboard button The clipboard button displays the Clipboard Contents
dialog box, which contains references to objects that have
been cut or copied from your workspace. The total number
of objects on the clipboard is displayed to the right of the
symbol.
For more information about the clipboard in the rich
client, see Cutting, copying, pasting, and deleting data
objects.

PLM00191 J Rich Client Interface Guide 1-7

Chapter 1 Getting started with the rich client

Note The status message area on the lower-left side of the Teamcenter window is
available to any application to indicate whether the client is ready for input
or is working, so the user interface may not be accepting input at that time.
The status messages on the lower-right side of the Teamcenter window
indicate the status or activity of background threads for any potentially
long operations.
• The default message is Working, but other messages, such as Loading
children, can be supplied by the application running the background
thread.

• Information shown in this area can often be observed in more detail in

the Progress view.

• In the Progress view, some operation messages have a Cancel button

that can be useful in cases where an operation was started but is not
wanted at that time, such as when a user is loading thousands of nodes
but decides that operation is not needed.

Note On Windows systems, operational status for the rich client interface and the
Teamcenter server is provided by the Teamcenter icon in the system tray.

To display the running status dialog box, click the Teamcenter icon in the
system tray .

The server and user interface condition symbols show the current status of
the rich client interface and the Teamcenter server.
• The server status indicates the state of the Teamcenter server:
o The server is ready, but there is no current communication
between the client and the server.

1-8 Rich Client Interface Guide PLM00191 J

 Getting started with the rich client

o The server is busy.

o The server appears to be idle.

o The server appears to be disconnected.

• The client status indicates the condition of the rich client:

o The user interface is responsive.

o The user interface is unresponsive.

Teamcenter rich client perspectives and views

Within the Teamcenter rich client user interface, functionality is provided in
perspectives and views. Some applications use perspectives and views to rearrange
how the functionality is presented. Other applications use a single perspective
and view to present information.
• Perspectives
Are containers for a set of views and editors that exist within the perspective.

o A perspective exists in a window along with any number of other

perspectives, but only one perspective can be displayed at a time.

o In applications that use multiple views, you can add and rearrange views to
display multiple sets of information simultaneously within a perspective.

o You can save a rearranged perspective with the current name, or create a
new perspective by saving the new arrangement of views with a new name.

• Views and view networks

In some Teamcenter applications, using rich client views and view networks, you
can navigate to a hierarchy of information, display information about selected
objects, open an editor, or display properties.

o Views that work with related information typically react to selection changes
in other views.

o Changes to data made in a view can be saved immediately.

o Any view can be opened in any perspective, and any combination of views
can be saved in a current perspective or in a new perspective.

o A view network consists of a primary view and one or more secondary views
that are associated. View networks can be arranged in a single view folder
or in multiple view folders.

o Objects selected in a view may provide context for a shortcut menu. The
shortcut menu is usually displayed by right-clicking.

PLM00191 J Rich Client Interface Guide 1-9

Chapter 1 Getting started with the rich client

For more information about using the shortcut menu, see the My Teamcenter
Guide.
Note If your site has online help installed, you can access application and view
help from the rich client Help menu or by pressing F1. Some views, such
as Communication Monitor, Print Object, and Performance Monitor,
are auxiliary views that may be used for debugging and that may not be
displayed automatically by any particular perspective.
For more information about auxiliary views, see the Client Customization
Programmer’s Guide.

For more information about perspectives and views and changing the layout of your
rich client window, see Managing views, layouts, and view networks.

Using the Getting Started application

The Getting Started application lets you begin work.

1 Find a part and This option is the same as the Search box in the navigation
begin my work pane.
For more information about Search in the rich client, see
Searching in Teamcenter.

1-10 Rich Client Interface Guide PLM00191 J

 Getting started with the rich client

2 Open My Loads My Teamcenter with your worklist displayed, if it has

Teamcenter any tasks to perform or track, or loads My Teamcenter with
or Worklist your Home folder displayed.
For information about My Teamcenter, see the My
Teamcenter Guide.
3 View/Edit Loads and displays the Structure Manager application.
a product
structure For information about using Structure Manager, see the
Structure Manager Guide.
4 View/Edit my Loads and displays the Classification application.
company’s
classification For information about Classification, see the Classification
data Guide.

Note The navigation pane also lets you start an application or search for data to
begin your work.
For information about configuring the navigation pane, see Working with the
rich client navigation pane.

Localizing property values in Teamcenter

The Localization button allows localization administrators to enter localized text
for property values. To place the Localization button on properties in Teamcenter, an
administrator must use the Business Modeler IDE to set the Localizable property
constant to true for those properties.
Using the Localization button, you can perform the following tasks:
• View the existing localization text.

• Modify the existing localization text.

• Add a translation value for a new locale without altering the master value of
the property.

• Remove a translation value without altering the master value of the property.

For more information about localizing values in Teamcenter, see the Localization
Guide.

Viewing, editing, and adding translations for a property using the

Localization button
The Localization button provides an easy way for users to view, edit, and add
translations for a given localizable property. For example, in the Query Builder
application, you can select a query regarding employee information.

PLM00191 J Rich Client Interface Guide 1-11

Chapter 1 Getting started with the rich client

Note • The Localization button appears by default in the following applications:

o Organization (site, group, and calendar)

o Query Builder

o Report Builder

o Classification Administration

In addition, the Localization button appears on localized property fields.

You must use Business Modeler IDE to create a customized template to
localize the individual property fields.
For more information about adding the Localization button to properties,
see the Business Modeler IDE Guide.

• Only privileged users (with the Translation privilege set in Access

Manager) can add and edit the translations.
For more information about setting the Translation privilege, see the
Localization Guide.

The presence of the Localization button indicates the dialog box content can
be localized. For example, if the master locale is set to English, you can add a
translation for this employee information query. Using the Localization button, you
can perform the following tasks:
• View the existing localization text.

• Modify the existing localization text.

• Add a translation value for a new locale without altering the master value of
the property.

• Remove a translation value without altering the master value of the property.

To localize the name of the saved query, Admin – Employee Information in the
example, click the Localization button to the right of the Name box. The Language
Translations dialog box is displayed.
The master locale and master value are retained. Click the plus button (+) to add a
localized value. Click the minus button (–) to remove a localized value. When adding
a new value, you must add text in the following fields:
• Master Locale
Displays the locale set for the site, for example, English.

• Master Value
Displays the original text. This is the value that is stored when a new object is
created. The content of this field can only be changed from the main dialog box.

• Value
Specifies the property value content.

1-12 Rich Client Interface Guide PLM00191 J

 Getting started with the rich client

• Status
Specifies the status of the localization. From the list, select one of the following:

o Approved
The text change is approved for use.

o Invalid
The text change is not valid.

o Pending
The text change is pending approval.

o Review
The text change is in review.

• Locale
Specifies the locale. The list displays the locales that have been made available
by the administrator, for example:

o French

o German

o Italian

o Spanish

PLM00191 J Rich Client Interface Guide 1-13

Chapter

2 Managing the Teamcenter

client interface

Managing the Teamcenter client interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Using application perspectives and views in your rich client session . . . . . . . . 2-1

Opening application perspectives in the rich client . . . . . . . . . . . . . . . . . . . . 2-1

Rich client application perspectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Open a rich client perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Switch between open perspectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Save, reset, or close a rich client perspective . . . . . . . . . . . . . . . . . . . . . . 2-14

Views available to rich client application perspectives . . . . . . . . . . . . . . . . . . 2-15

Rich client views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Commonly used views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
Component views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Details view table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Configure the Details view table . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
Using the Graph Overview view . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Display images in the Graphics view . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Toolbars available in the Graphics view . . . . . . . . . . . . . . . . . . . . 2-58
Using the Image Preview view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Impact Analysis view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Using the JT Preview view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
Using the Properties view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
Using the Relation Browser view . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
Summary view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
Viewer view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65
Working with visualization data in the My Teamcenter viewer . . . 2-67
Open visualization data in My Teamcenter . . . . . . . . . . . . . . . . . 2-69
Customizing the Viewer view . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
Using auxiliary views in the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
Use the Show View command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
Display and move a view in rich client . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71
Finding information about views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72

Managing views, layouts, and view networks . . . . . . . . . . . . . . . . . . . . . . . . . 2-73

Recognizing primary and secondary views . . . . . . . . . . . . . . . . . . . . . . . . 2-74
Changing view network color presentation . . . . . . . . . . . . . . . . . . . . . . . 2-76
Change the view association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
Associate views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77
Disable and enable response to selection . . . . . . . . . . . . . . . . . . . . . . 2-77

PLM00191 J Rich Client Interface Guide

 Set input to recent selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77
Hide and display views and view folders . . . . . . . . . . . . . . . . . . . . . . . . . 2-78

Rich client menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79

Window menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79
Show View menu command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-81
Shortcut menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82
Shortcut menus in My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86

Working with the rich client navigation pane . . . . . . . . . . . . . . . . . . . . . . . . 2-91

Rich client navigation pane section order . . . . . . . . . . . . . . . . . . . . . . . . 2-93
Configuring the Quick Links section . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-93
Add a folder to your rich client quick links . . . . . . . . . . . . . . . . . . . . . 2-94
Remove a folder from your rich client quick links . . . . . . . . . . . . . . . . 2-94
Rename a rich client quick links folder . . . . . . . . . . . . . . . . . . . . . . . 2-94
Organize your rich client quick links . . . . . . . . . . . . . . . . . . . . . . . . . 2-94
Manage rich client saved searches . . . . . . . . . . . . . . . . . . . . . . . . . . 2-94
Add a saved search to your saved searches list (rich client) . . . . . . 2-95
Remove a saved search from the list in the rich client . . . . . . . . . . 2-95
Rename a saved search in the rich client . . . . . . . . . . . . . . . . . . . 2-95
Organize your saved searches list in the rich client . . . . . . . . . . . . 2-95
Manage your links in the rich client . . . . . . . . . . . . . . . . . . . . . . . . . 2-96
Add a link to your list of links in the rich client . . . . . . . . . . . . . . 2-96
Remove a link from the rich client My Links list . . . . . . . . . . . . . . 2-96
Rename a link in the rich client . . . . . . . . . . . . . . . . . . . . . . . . . 2-96
Organize your rich client My Links list . . . . . . . . . . . . . . . . . . . . 2-96
Customize your I Want To links in the rich client . . . . . . . . . . . . . . . . 2-97
Add a task to the rich client I Want To list . . . . . . . . . . . . . . . . . . 2-97
Remove a task from the rich client I Want To list . . . . . . . . . . . . . 2-97
Organize your rich client I Want To list . . . . . . . . . . . . . . . . . . . . 2-98
Show or hide the navigation pane in the rich client . . . . . . . . . . . . . . . 2-98
Configuring the display of applications . . . . . . . . . . . . . . . . . . . . . . . . . . 2-98
Select available applications for display . . . . . . . . . . . . . . . . . . . . . . . 2-99
Display primary and secondary applications . . . . . . . . . . . . . . . . . . . 2-99
Show more applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100
Show fewer applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100
Add favorites to organize your data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100
Add a link to your Favorites list . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100
Add a subfolder to your Favorites list . . . . . . . . . . . . . . . . . . . . . . . 2-101
Rename a folder in the Favorites list . . . . . . . . . . . . . . . . . . . . . . . . 2-101
Remove a link or folder from the Favorites list . . . . . . . . . . . . . . . . . 2-101

Customizing the toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-101

Button groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
Remove buttons from the toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
Add buttons to the toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
Change the order of buttons in the toolbar . . . . . . . . . . . . . . . . . . . . . . . 2-103
Show and hide the toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-103

Changing user settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-103

Application bar display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-104
Change your user profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-105
Change your password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-105
Change your default group and volume settings . . . . . . . . . . . . . . . . . . . 2-105

Rich Client Interface Guide PLM00191 J

 Set your default role within a group . . . . . . . . . . . . . . . . . . ... . . . . . . 2-106
Change administrative settings . . . . . . . . . . . . . . . . . . . . . ... . . . . . . 2-106
Change your group, role, volume, and logging session settings .. . . . . . . 2-106
Set your work context . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . 2-107
Set your current project . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . 2-107

Using the information center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-107

Set information center display options . . . . . . . . . . . . . . . . . . . . . . . . . 2-108

Using the Launch Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-109

Cutting, copying, pasting, and deleting data objects . . . . . . . . . . . . . . . . . . . 2-110

Cut data objects and paste them into another Teamcenter application . . . 2-111
Copy data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-112
Pasting data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-112
Paste the contents of the clipboard . . . . . . . . . . . . . . . . . . . . . . . . . 2-112
Paste an item or item revision and specify the relation type . . . . . . . 2-112
Pasting object references to applications outside the Teamcenter
environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-113

Dragging and dropping data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-113

Using the Localization button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-115

Organize data in folders and pseudofolders . . . . . . . . . . . . . . . . . . . . . . . . . 2-115

Home, Newstuff, and Mailbox folders . . . . . . . . . . . . . . . . . . . . . . . . . . 2-117
Working with pseudofolders and smart folders . . . . . . . . . . . . . . . . . . . . 2-118
Working with folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
Create a new folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
Rename a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-121
Reorder objects in a folder or view . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122
Print a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-123
Delete a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-123

User interface panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-124

Using the folder tree pane and data panes . . . . . . . . . . . . . . . . . . . . . . . 2-125
Using the Folder pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-125
Using data panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-125
Using the Summary pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-126
Using the Details pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-126
Configuring application tables . . . . . . . . . . . . . . . . . . . . . . . . . 2-126
Using the Viewer pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-128
Using the Referencers pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-129
Using the Display Data pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-129

Configuring table data display in the rich client . . . . . . . . . . . . . . . . . . . . . . 2-129

Printing information about your data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-130

Formatting information for printing . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-132
Print object information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-133
Print objects information from the Properties dialog box . . . . . . . . . . . . . 2-134
Print information contained in tables . . . . . . . . . . . . . . . . . . . . . . . . . . 2-136
Print where-referenced information . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-136
Print form properties from the Properties dialog box . . . . . . . . . . . . . . . 2-136

PLM00191 J Rich Client Interface Guide

 Print form properties from the viewer . . . . . . . . . . . . . . . . . . . . . . . . . . 2-137
Printing Teamcenter objects in Teamcenter Rapid Start . . . . . . . . . . . . . 2-138

Using preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-140

Preference definition elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-141
System and hierarchical preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-143
Managing protection scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-144

Working with preferences in the rich client . . . . . . . . . . . . . . . . . . . . . . . . . 2-145

Set a preference option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-145
Searching for preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-146
Search for a preference by name . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-146
Search for a preference using keywords . . . . . . . . . . . . . . . . . . . . . . 2-146
Defining preferences and creating preference instances . . . . . . . . . . . . . 2-147
Type options for preference values . . . . . . . . . . . . . . . . . . . . . . . . . 2-148
Create a preference category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-148
Delete a preference category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-148
Creating preferences and adding preference instances . . . . . . . . . . . 2-149
Create a new preference definition . . . . . . . . . . . . . . . . . . . . . . 2-149
Create a preference instance for a group . . . . . . . . . . . . . . . . . . 2-150
Create a preference instance for a nonadministrator user . . . . . . 2-151
Modify the values of a preference instance . . . . . . . . . . . . . . . . . . . . . . . 2-152
Generating preference reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-153
Create preference reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-154
Sharing preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-154
Export preferences from the database to an XML file . . . . . . . . . . . . 2-154
Import preferences into the database . . . . . . . . . . . . . . . . . . . . . . . 2-155

View and set rich client Eclipse window preferences . . . . . . . . . . . . . . . . . . 2-156

Working with rich client persistent caches . . . . . . . . . . . . . . . . . . . . . . . . . 2-157

Working with the FMS server cache (FSC) and FMS client cache (FCC) . . . . . 2-159

Rich Client Interface Guide PLM00191 J

Chapter

2 Managing the Teamcenter

client interface

Managing the Teamcenter client interface

You can make your Teamcenter client a more efficient tool to accomplish your work
by:
• Changing the view layout in your applications

• Changing user settings

• Adjusting information center options

• Working with the navigation pane

• Configuring the toolbar

• Managing options and preferences

• Configuring data display in tables

Using application perspectives and views in your rich client session

You can open, or load, one or more applications in your rich client session.
Each application perspective is displayed in the rich client window and each
application perspective contains one or more views.
You can have any number of views open in any application perspective, and you can
associate views so they operate as a network.
For more information about application perspectives, see Opening application
perspectives in the rich client.
For more information about views, see Views available to rich client application
perspectives.

Opening application perspectives in the rich client

In the rich client, you can open application perspectives several ways:
• Use the navigation pane to select a primary or secondary application or to
include other available applications in the primary or secondary listings.

PLM00191 J Rich Client Interface Guide 2-1

Chapter 2 Managing the Teamcenter client interface

Tip If the navigation pane is not visible, use the Window→Navigation Pane
menu command to display it or click the Navigation Pane icon in
the toolbar.

• Select a perspective using the Window→Open Perspective menu command.

• Use the shortcut menu Send To command to open a selected object in another
application.
Note Not all perspectives may be installed or licensed at your site, and your site
may have added or renamed perspectives after installation. Also, the order
presented by the Window→Open Perspective menu command defaults to an
automatic alphabetization that gives precedence to uppercase letters over
lowercase letters. The order of presentation may vary at your site.

Rich client application perspectives

Application Button Description
4G Designer Lets you manage the design data of
large products such as those found in the
shipbuilding, automotive and aerospace
industries. Use 4G Designer to create and
manage collaborative designs, partitions,
worksets, subsets, and design elements.
For more information about 4G Designer,
see the 4th Generation Design Guide.
4G Designer- Lets you build a manufacturing bill of
MBOM materials by assigning design elements
Reconciliation from a collaborative design into a product
structure representing the MBOM.
For more information about the
4G Designer-MBOM Reconciliation
perspective, see the Manufacturing Process
Planner Guide.
ADA License Allows you to access International Traffic
in Arms Regulations (ITAR), intellectual
property (IP), and exclusion license
administration capabilities as a non-DBA
group Teamcenter user.
For more information about ADA License,
see the Authorized Data Access License
Guide.
Access Manager Enables administrators to control access
to data in Teamcenter using the Access
Manager (AM) rule tree, which is a
collection of rules available at your site.
For information about Access Manager, see
the Access Manager Guide.

2-2 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Application Button Description

Appearance Enables administrators to configure the
Configuration use of appearances, which cache data to
improve performance when managing
large product structures. Tasks include
defining the appearance sets for which the
site tracks appearances and configuring
the mapping of occurrence notes into
appearance attributes.
For information about Appearance
Configuration, see the Appearance
Configuration Guide.
As-Built Manager Lets you manage the as-built configuration
of an asset realized from a product
definition structure, such as a design
or manufacturing structure. This is a
separately licensed application installed
as an optional overlay on the standard
Teamcenter product.
For more information about managing
as-built configurations, see the As-Built
Manager Guide.
Audit Manager System administrators use Audit Manager
to create and control audit logs that track
selected properties for specified actions in
the database.
For information about Audit Manager, see
the Audit Manager Guide.
Authorization System administrators use Authorization
to grant access to Teamcenter
administrative applications and utilities to
users based on their group membership or
their role in a group.
For information about Authorization, see
the Application Administration Guide.
CAE Manager Lets you identify product data for analysis
and create and manage corresponding CAE
data.
For information about CAE Manager,
see the Simulation Process Management
Guide.

PLM00191 J Rich Client Interface Guide 2-3

Chapter 2 Managing the Teamcenter client interface

Application Button Description

CAE Manager Provides CAE Manager and Inspector
(Legacy) (formerly views to let you manage CAE processes
CAE Structure and procedures, including definition of
Editor) components for analysis, design validation,
and analysis procedure verification.
For information about CAE Manager,
see the Simulation Process Management
Guide.
CAE Structure Enables you to create and manage
Designer (formerly structure map rules that can be used to
StructureMap generate CAE model structures.
Builder)
For information about CAE Structure
Designer, see the Simulation Process
Management Guide.
Change Manager Let you track changes to a product
throughout its life cycle. You propose a
change to a product and then manage
the entire cycle of review, approval, and
implementation of the change.
For information about Change Manager,
see the Change Manager Guide.
Classification Enables you to classify and categorize your
product data based on predefined attribute
values.
For information about Classification, see
the Classification Guide.
Classification Enables administrators to define the
Administration groups, classes, subclasses, and views that
form the Classification hierarchy.
For information about Classification
Administration, see the Classification
Administration Guide.
Command Provides Applications, Suppress
Suppression Commands, and Organization views to let
administrators control the display of menu
and toolbar commands within Teamcenter
perspectives. You can suppress the display
of commands for an entire group hierarchy
or a specific role within the hierarchy, for
entire groups of users, and for users who
are assigned a role within a group. It
also allows you to suppress the display of
specific commands on a designated menu
or to suppress the display of entire menus.

2-4 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Application Button Description

For information about Command

Content Management
DPV Measurements
Dashboard
Database Utilities
DesignContext
Suppression, see the Application
Administration Guide.
Enables you to manage SGML and XML
information stored in a Teamcenter
database in conjunction with SGML/XML
authoring tools to create technical
publications in multiple formats.
For information about Content
Management, see the Content Management
Guide.
Allows Dimensional Planning and
Validation data managers to view
measurement data events based on their
date or job serial number and to activate or
deactivate selected events.
For more information about DPV
Measurements, see the Dimensional
Planning and Validation Administration
Guide.
Shows the Reporting and Analytics
dashboard.
For more information about the Dashboard
application, see the Report Builder Guide.
Used to access Teamcenter volume
information and database user information.
For information about using the Database
Utilities application, see Getting Started
with Automotive Edition.
Lets you quickly focus on a particular work
part in the Repeatable Digital Validation
(RDV) environment and on any other parts
affected within the context of a change to
that part.
RDV lets you accurately model specific
product assembly configurations and
use the results with analytical and
visualization tools to facilitate learning
and decision making.
For information about DesignContext, see
the DesignContext Guide.

PLM00191 J Rich Client Interface Guide 2-5

Chapter 2 Managing the Teamcenter client interface

Application Button Description

Getting Started Provides a point from which you can
quickly start working in Teamcenter. You
can search for a part, open your worklist,
view or edit product structure, or view or
edit classification data.
For information about using the Getting
Started application, see Using the Getting
Started application.
For general information about Teamcenter,
see Getting Started with Teamcenter.
Issue Manager Tracks problems, or issues, with a product
by letting you manage the review, approval,
and implementation of the issue. Also
lets you view and manage requests for
the penetration of structures that were
generated in NX.
For information about Issue Manager, see
the Issue Manager Guide.
Launch Pad Provides a visual desktop to place items
and notes, called nodes, for quick reference
in either a carousel or grid display mode.
Note By default, the Launch Pad
application is hidden unless an
administrator removes it from the
HiddenPerspectives preference
value list.

For information about using the Launch

Pad application, see Using the Launch Pad.
Lifecycle Viewer Used for visualization of parts and
assemblies, Lifecycle Viewer provides
multiple views that let you display and
work with design data typically stored
in CAD-data formats. Lifecycle Viewer
functionality is available in multiple
product configurations along with a variety
of optional software modules.
Note Teamcenter supports product
visualization requirements in
multiple ways, including:
• Lifecycle Viewer – A
Teamcenter application
available in the rich client.

• Embedded viewers – Viewers

accessed within Teamcenter

2-6 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Application Button Description

applications such as My
Teamcenter and Structure
Manager.

• Stand-alone viewer –
An application installed
separately from Teamcenter,
which supports both local and
Teamcenter-managed data.

For information about Lifecycle Viewer

Manufacturing – 4D
Scheduling
Manufacturing –
BOM Reconciliation
Manufacturing –
Process Sequencing
Manufacturing –
Work Instructions
and other visualization options, see Getting
Started with Product Visualization.
Provides a Schedule Manager view
alongside process and product views to
enable 4D analysis of very large structures.
This analysis allows a manufacturing
planner to visualize what parts of a
structure are already assembled by a
specific date in a given area of the product.
For information about the Manufacturing
– 4D Scheduling perspective, see the
Manufacturing Process Planner Guide.
Provides two structure views with their
accompanying Graphics views to help
you align the engineering BOM with the
manufacturing BOM.
For information about Manufacturing
Process Planner perspectives, see the
Manufacturing Process Planner Guide.
Provides PERT and Process Gantt views to
help you specify the process flow.
For information about Manufacturing
Process Planner perspectives, see the
Manufacturing Process Planner Guide.
Provides Standard Text, Standard Text
Library, and Textual Work Instruction
views to assist you in authoring work
instructions by choosing from a library of
standard text elements.
For information about the Manufacturing
– Work Instructions perspective, see the
Manufacturing Process Planner Guide.

PLM00191 J Rich Client Interface Guide 2-7

Chapter 2 Managing the Teamcenter client interface

Application Button Description

Manufacturing Enables you to design a process plan for
Process Planner manufacturing a product. The process
(formerly plan describes the overall strategy used to
Manufacturing manufacture the product and defines the
Structure Editor) specific processes and operations used in
the plan.
For information about Manufacturing
Process Planner, see the Manufacturing
Process Planner Guide.
Multi-Structure Enables you to manage any of the structure
Manager (formerly types compatible with Teamcenter,
called Collaboration including product structures and
Context) manufacturing process structures.
For information about Multi-Structure
Manager, see the Multi-Structure Manager
Guide.
My Teamcenter Provides Teamcenter Component,
Summary, Details, Viewer, and Impact
Analysis views you use to perform many
basic tasks such as viewing and modifying
your data, initiating and participating in a
workflow process, and checking your data
into and out of the Teamcenter database.
For information about My Teamcenter, see
the My Teamcenter Guide.
Organization Lets the Teamcenter administrator create
and maintain your company’s virtual
organization within Teamcenter. This
virtual organization is a way of organizing
user accounts and their respective
permissions and user groups.
For information about Organization, see
the Organization Guide.
PLM XML/TC XML Enables administrators to create PLM
Export Import XML import and export rules used to
Administration configure the import and export of data in
PLM XML format.
For information about PLM XML/TC
XML Export Import Administration, see
the PLM XML/TC XML Export Import
Administration Guide.
Part Planner Enables you to design a plan that details
how to manufacture a piece part product.
For information about Part Planner, see
the Part Planner Guide.

2-8 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Application Button Description

Plant Designer Enables you to author and view factory
(formerly called layouts.
Factory Structure
Editor) For information about Plant Designer, see
the Plant Designer Guide.
Platform Designer Provides a mechanism to plan and control
the evolution of product structures at
your site by building generic structures of
your products that contain a high degree
of variability. Platform Designer uses
architecture breakdowns to create and
disseminate design content and product
variability.
For information about Platform Designer,
see the Platform Designer Guide.
Product Configurator Lets you define and manage the variability
of a product, including options, option
values, option families, option rules, and
constraints (rule checks).
For more information about Product
Configurator, see the Product Configurator
Guide.
Project Enables administrators to control access
to a Teamcenter database that is used by
multiple organizations, such as project
teams, development teams, suppliers, and
customers. Access to data is controlled on
a project-by-project basis.
For information about Project, see the
Project and Program Guide.
Query Builder Enables administrators to create, modify,
and delete saved queries that are
made available to the Teamcenter user
community.
For information about Query Builder, see
the Query Builder Guide.
Registry Editor Enables the editing of Teamcenter rich
client registry files. This perspective is
used only for editing registry files that
are used for internationalization, dynamic
class invocation, and configuration in the
rich client framework.
For information about Registry Editor, see
the Registry Editor Guide.

PLM00191 J Rich Client Interface Guide 2-9

Chapter 2 Managing the Teamcenter client interface

Application Button Description

Relation Browser Provides Relation Browser, Image
Preview, Graph Overview, and Properties
views you use to perform basic tasks such
browsing object relations, viewing 2D
images, locating an object graphically in
a map of relations, and examining the
properties of a selected object.
Report Builder Enables administrators to build summary,
item, and custom reports.
For information about Report Builder, see
the Report Builder Guide.
Report Generator Generates reports on products,
manufacturing processes, and plant
structures managed by Manufacturing
Process Management.
For information about Report Generator,
see the Report Generator Guide.
Requirements Enables the identification, allocation,
Manager and ongoing maintenance of product
requirements.
For information about Requirements
Manager, see the Systems Engineering
Guide.
Resource Manager Manages manufacturing resources, such as
cutting tools, machine tools, fixtures, weld
guns, robots, and related documents.
For information about Resource Manager,
see the Resource Manager Guide.
Schedule Manager Enables you to define and manage
schedules for your projects. These
schedules can be shared with members of
your team. You can allow team members to
update specific tasks, schedule subsections
of the project, or update the entire project
schedule.
For information about Schedule Manager,
see the Schedule Manager Guide.

2-10 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Application Button Description

Service Manager
Service Planner
Service Request
Manager
Service Scheduler
Setup Wizard
Supports as-maintained structure
management and service event
management capabilities using the
Contains, Disposition History, Log
Entries, Physical Part Usage History,
Service Details, Service Editor, and
Utilization views.
For information about Service Manager,
see the Service Manager Guide.
Lets you create and manage service
plans, service requirements, work cards,
activities, and other information to support
the service planning process. Uses the
Service Planner and Plan Details views.
For information about Service Planner, see
the Service Planner Guide.
Supports service request management
capabilities using the Open Service
Request, Request Home, and Service
Request Status views.
For information about Service Request
Manager, see the Service Request Manager
Guide.
Provides the capability to define, schedule,
and implement service work using the
Home, Service Editor, Service Scheduler,
Work Order Home, and Summary views.
For information about Service Scheduler,
see the Service Scheduler Guide.
Facilitates postinstallation set up of a
Teamcenter database using an input file
to populate the information required
to create the basic components of the
Teamcenter organization. Using Setup
Wizard, a system administrator can create
user/person definitions, assign a group/role
to a user, and optionally define a default
volume for assigned groups.
For information about Setup Wizard, see
the Setup Wizard Guide.

PLM00191 J Rich Client Interface Guide 2-11

Chapter 2 Managing the Teamcenter client interface

Application Button Description

Software Parameter Lets you manage embedded software
Manager parameters and their location into
hardware controller memory space.
You can segregate controller memory
into multiple segments that can be
divided into blocks. Software Parameter
Manager provides the framework to import
parameter addresses and conversion rules
as well as to generate the flash file for each
memory segment.
For more information, see the Embedded
Software Solutions Guide.
Specification Enables you to view and work with
Manager specifications that capture the complete
definition of products and how to
manufacture them.
For information about Specification
Manager, see the Specification Manager
Guide.
Structure Manager Enables you to create, edit, and configure
(formerly called product structures.
Product Structure
Editor) For information about using Structure
Manager, see the Structure Manager
Guide.
Subscription Monitor Enables administrators to query
subscriptions created in the database, to
monitor and delete subscription events and
actions, and to generate statistical reports
related to subscriptions, events, and
actions in either text or bar chart format.
For information about Subscription
Monitor, see the Subscription Monitor
Guide.
Systems Engineering Encompasses functional modeling and
requirements management.
Functional modeling lets you represent the
functional breakdowns of a product and
decompose your proposed design or product
into functional subsystems.
Systems Engineering lets you identify,
allocate, and maintain product
requirements.
These capabilities are provided by the
Requirements view and the Function view,
respectively.

2-12 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Application Button Description

For information about functional modeling

Validation Manager
Volume Management
Web Browser
Workflow Designer
Workflow Viewer
and requirements management, see the
Systems Engineering Guide.
Provides a decision mechanism to let users
ensure an item revision meets compliance
before it is released. Once validation
processes are configured, users can select
an item revision from My Teamcenter and
confirm its compliance with the business
rules defined at your site.
For information about Validation Manager,
see the Validation Manager Guide.
Allows administrators to improve
performance by creating migration policies
that move lower priority files to either
destination volumes or third-party storage
systems. All data continues to appear
online to users. Files stored on secondary
and tertiary tiers can be read without
moving them to the highest level.
For information about Volume
Management, see the Volume Management
Guide.
Provides access to Web pages from within
the rich client framework. Web Browser
lets you navigate to Web pages and view
Web pages within the rich client rather
than switching to a separate Web browser.
Web Browser also provides the capability
to access MIME (Multipurpose Internet
Mail Extension) file types and to view
files created in other applications, such
as Microsoft Word and Excel, through the
Web browser.
For information about Web Browser, see
the Application Administration Guide.
Enables administrators to design workflow
processes using predefined tasks and
handlers.
For information about Workflow Designer,
see the Workflow Designer Guide.
Enables you to view in-progress workflow
processes and related data.
For information about Workflow Viewer,
see the Workflow Viewer Guide.

PLM00191 J Rich Client Interface Guide 2-13

Chapter 2 Managing the Teamcenter client interface

Open a rich client perspective

You open an application perspective in the rich client in any of the following ways:
• Click the application button in the navigation pane.

• Select the perspective from the Window→Open Perspective menu.

• Select an object in a navigation view and use the Send To shortcut menu
command to select an application.

• Double-click an object in a navigation view to open the perspective associated

with that object type.

For example, to open My Teamcenter in the rich client, click My Teamcenter

in the navigation pane.
If you do not see My Teamcenter listed as a primary application, check for the My
Teamcenter button in the secondary application button bar at the bottom of the
navigation pane. You can use Configure Applications ( ) at the bottom of the
navigation pane to find and place the My Teamcenter button in the navigation pane.
Note You can configure the display of application buttons in the rich client
interface by designating perspectives to be primary or secondary.
For more information, see Configuring the display of applications.

Switch between open perspectives

Use any of the following methods to change from the currently displayed open
perspective to another open perspective:
• Use the Back button in the toolbar, its associated menu, , or Ctrl+Shift+F8
to display an application opened before the current application.

• Use the Forward button in the toolbar, its associated menu, , or Ctrl+F8 to
display an application opened before the current application.

• Hold down Ctrl+F8 to display a Perspectives menu, and then release F8 and
use your mouse or your keyboard arrows to select the perspective to display.

Save, reset, or close a rich client perspective

To save the currently active perspective when you have arranged a useful layout of
views and view networks:
1. Choose Window®Save Perspective As.

2. Enter a new name for the perspective.

3. Click OK.

To restore a perspective to its default state, choose Window®Reset Perspective.

This returns all default views to their original locations.

2-14 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

You close an application perspective in rich client in any of the following ways:
• Click the X in the application banner.
Note If you click the X in a view tab, only the selected view is closed and the
application perspective remains active.

• Select the application, and then select Window®Close Perspective.

Views available to rich client application perspectives

Rich client perspectives may have one or more views; most currently have a single
view. For example, the Schedule Manager application perspective has, by default, a
single Schedule Manager view.
For information about specific views, see Rich client views.
You can add views to any perspective, remove views, rearrange views and, in the
case of perspectives provided with the rich client, restore the default layout of
a perspective.
For information about rearranging views in a perspective, see Display and move a
view in rich client.
When the rich client or a rich client view is resized, view toolbars and menus always
stay in same row.
• When the view toolbar is not wide enough to display all its items, a chevron
button is added to toolbar to indicate there are hidden toolbar items.

• Click the chevron button on a view toolbar to display a popup list for access
to any hidden items.

Rich client views

Views in the rich client are displayed:
• When you open an application perspective, each of which displays one or more
views.

• When you select a toolbar button or a link in the navigation pane that opens a
view.

• From the Window®Show View®Other command to display the Show View

dialog box.
Expand the categories to display views, and then double-click a view name to
display the view in the currently-active perspective.
Note Some views listed in this topic may be unavailable at your site, and
additional views may be present, depending on your Teamcenter installation
configuration. Your site can also display or hide perspectives using the
HiddenPerspectives preference.

Typical view categories include:

PLM00191 J Rich Client Interface Guide 2-15

Chapter 2 Managing the Teamcenter client interface

• General
• Admin
• Application
• CAE Manager
• CAE Manager (Legacy)
• Change Management
• Content Management
• Diagnostic
• Issue Management
• Manufacturing
• Material Management
• Projects
• Schedule Manager
• Service Manager
• Service Planner
• Service Request Manager
• Service Scheduler
• Substance Compliance
• Systems Engineering
• Teamcenter
• Utilities
• Validation Manager
• Visualization
• Other

General views

View Symbol Description

Change Lets you add and remove change items associated with
Details a schedule task. In addition, you can add multiple items
at once.
For more information, see the Change Manager Guide.
Console Not displayed by default in any perspective, you can use
the Console view in the Business Modeler IDE mapping
designer to display output from loading and building
projects to map data model from one product lifecycle
management (PLM) system to another.
For information about using Console, see the Business
Modeler IDE Guide.
Note This view is intended for use by system
administrators. The Console view is an Eclipse
platform view that displays standard input and
output messages. For more information about the
Console view, see the Eclipse documentation.

2-16 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Outline Not displayed by default in any perspective.
This is a helper view that can display an outline of a
structured object open in an editor. It is not currently
used by Teamcenter.
Note This view is an Eclipse platform view. For more
information about this view, see the Eclipse
documentation.
Palette Not displayed by default in any perspective. This is a
helper view for graphical editing applications. It is not
currently used by Teamcenter.
Note This view is an Eclipse platform view. For more
information about this view, see the Eclipse
documentation.
Progress Not displayed by default in any perspective. The
Progress view lets you monitor progress messages and
units of completed work for selected long-running jobs
(those lasting more than a second) such as large-scale
data object transfers.
For more information about using the Progress view
to monitor data exchange between sites, see the Data
Exchange Guide.
Note The Progress view is an Eclipse platform view.
For more information about the Progress view,
see the Eclipse documentation.
Properties Displayed as part of the Relation Browser perspective.
The Properties view displays object data, such as name,
creation date, ownership, and description for the selected
object. This view also provides Show Categories, Show
Advanced Properties, and Restore Default Value buttons
for use as appropriate. This functionality is separate
from the shortcut menu Properties command, which also
supports editing of some attribute values.
For information about the Properties view in the Relation
Browser application, see the Relation Browser Guide.
Note The Properties view is an Eclipse platform
view that displays basic properties of a selected
resource. For more information about the
Properties view, see the Eclipse documentation.
Summary Provides attribute information for a selected object. This
is a default view in the My Teamcenter perspective.
For information about the Summary view in My
Teamcenter, see the My Teamcenter Guide.

PLM00191 J Rich Client Interface Guide 2-17

Chapter 2 Managing the Teamcenter client interface

Admin views

View Symbol Description

Access Enables administrators to control access to data in
Manager Teamcenter using the Access Manager (AM) rule tree,
which is a collection of rules available at your site.
This is the single view in the default layout of the
Access Manager perspective.
For information about Access Manager, see the Access
Manager Guide.
Appearance Enables administrators to configure the use of
Configuration appearances, which cache data to improve performance
when managing large product structures.
This is the single view in the default layout of the
Appearance Configuration perspective.
For information about Appearance Configuration, see
the Appearance Configuration Guide.
Applications Displayed by default as part of the Command
Suppression perspective.
For information about Command Suppression, see the
Application Administration Guide.
Audit Manager System administrators use Audit Manager to create
and control audit logs that track selected properties for
specified actions in the database.
This is the single view in the default layout of the Audit
Manager perspective.
For information about using Audit Manager, see the
Audit Manager Guide.
Classification Enables administrators to define the groups, classes,
Admin subclasses, and views that form the Classification
hierarchy.
The default layout of the Classification Admin
perspective contains a single Classification Admin view.
For information about Classification Admin, see the
Classification Administration Guide.

2-18 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

DPV Enables Dimensional Planning and Validation data
Measurements managers to view measurement data events based
on their date or job serial number and to activate or
deactivate selected events.
The default layout of the DPV Measurements
perspective contains a single DPV Measurements view.
For more information about DPV Measurements, see the
Dimensional Planning and Validation Administration
Guide.
Organization Displayed as part of the Command Suppression
perspective.
For information about Command Suppression, see the
Application Administration Guide.
Organization Lets the Teamcenter administrator create and maintain
your company’s virtual organization within Teamcenter.
This virtual organization is a way of organizing user
accounts and their respective permissions and user
groups.
The default layout of the Organization perspective
contains a single Organization view.
For information about using Organization, see the
Organization Guide.
PLM XML/TC Enables administrators to create PLM XML import and
XML Export export rules used to configure the import and export of
Import data in PLM XML format.
Administration
The default layout of the PLM XML/TC XML Export
Import Administration perspective contains a single
PLM XML/TC XML Export Import Administration view.
For information about using PLM XML/TC XML Export
Import Administration, see the PLM XML/TC XML
Export Import Administration Guide.
Query Builder Enables administrators to create, modify, and delete
saved queries that are made available to the Teamcenter
user community.
The default layout of the Query Builder perspective
contains a single Query Builder view.
For information about using Query Builder, see the
Query Builder Guide.

PLM00191 J Rich Client Interface Guide 2-19

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Report Builder Enables administrators to build summary, item, and
custom reports.
The default layout of the Report Builder perspective
contains a single Report Builder view.
For information about Report Builder, see the Report
Builder Guide.
Setup Wizard Facilitates postinstallation set up of a Teamcenter
database using an input file to populate the information
required to create the basic components of the
Teamcenter organization. Using Setup Wizard, a
system administrator can create user/person definitions,
assign a group/role to a user, and optionally define a
default volume for assigned groups.
For information about the Setup Wizard, see the Setup
Wizard Guide.
Subscription Enables administrators to query subscriptions created
Monitor in the database, to monitor and delete subscription
events and actions, and to generate statistical reports
related to subscriptions, events, and actions in either
text or bar chart format.
The default layout of the Subscription Monitor
perspective contains a single Subscription Monitor
view.
For information about Subscription Monitor, see the
Subscription Monitor Guide.
Suppress Part of the Command Suppression perspective.
Commands
For information about Command Suppression, see the
Application Administration Guide.
Volume Allows administrators to improve performance by
Management creating migration policies that move lower priority
files to either destination volumes or third-party storage
systems. All data continues to appear online to users.
Files stored on secondary and tertiary tiers can be read
without moving them to the highest level.
The default layout of the Volume Management
perspective contains a single Volume Management view.
For information about Volume Management, see the
Volume Management Guide.

2-20 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Volume Administrators use the Volume Monitor tab to monitor
Monitor free space and manage volume usage for all volumes
at your site.
The default layout of the Volume Monitor perspective
contains a single Volume Monitor view.
For information about the Volume Monitor view, see the
Volume Management Guide.
Workflow Enables administrators to design workflow processes
Designer using predefined tasks and handlers.
The default layout of the Workflow Designer application
perspective contains a single Workflow Designer view.
For information about Workflow Designer, see the
Workflow Designer Guide.

Application views

View Symbol Description

As-Built Lets you manage the as-built configuration of an asset
Manager realized from a product definition structure, such
as a design or manufacturing structure. This is a
separately-licensed application installed as an optional
overlay on the standard Teamcenter product.
For more information about managing as-built
configurations, see the As-Built Manager Guide.
CAE Manager The CAE Manager (Legacy) view is one of two views
(Legacy) displayed by default by the CAE Manager (Legacy)
perspective. CAE Manager (Legacy) views let you
manage CAE processes and procedures, including
definition of components for analysis, design validation,
and analysis procedure verification.
For information about using CAE Manager(Legacy), see
the Simulation Process Management Guide.
CAE Structure Enables you to create and manage structure map rules
Designer that can be used to generate CAE model structures.
This is the single view in the default layout of the CAE
Structure Designer perspective.
For information about the CAE Structure Designer
application, see the Simulation Process Management
Guide.

PLM00191 J Rich Client Interface Guide 2-21

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Classification Enables you to classify and categorize your product data
based on predefined attribute values.
The default layout of the Classification perspective
contains a single Classification view.
For information about using Classification, see the
Classification Guide.
DesignContext Allows you to quickly focus on a particular work part in
the Repeatable Digital Validation environment and on
any other parts affected within the context of a change
to that part.
Repeatable Digital Validation (RDV) allows you
to accurately model specific product assembly
configurations and use the results with analytical and
visualization tools to facilitate learning and decision
making.
The default layout of the DesignContext perspective
contains a single DesignContext view.
For information about using DesignContext, see the
DesignContext Guide.
Getting Provides a point from which you can quickly start
Started working in Teamcenter. You can search for a part, open
your worklist, view or edit product structure, or view
or edit classification data.
The default layout of the Getting Started perspective
contains a single Getting Started view.
For information about the Getting Started perspective,
see Getting Started with Teamcenter.
Multi-Structure Enables you to manage any of the structure types
Manager compatible with Teamcenter, including product
structures and manufacturing process structures.
The default layout of the Multi-Structure Manager
perspective contains a single Multi-Structure Manager
view.
For information about Multi-Structure Manager, see the
Multi-Structure Manager Guide.

2-22 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Platform Provides a mechanism to plan and control the evolution
Designer of product structures at your site by building generic
structures of your products that contain a high degree
of variability. Platform Designer uses architecture
breakdowns to create and disseminate design content
and product variability.
The default layout of the Platform Designer application
perspective contains a single Platform Designer view.
For information about using Platform Designer, see the
Platform Designer Guide.
Schedule Enables you to define and manage schedules for your
Manager projects. These schedules can be shared with members
of your team. You can allow team members to update
specific tasks, schedule subsections of the project, or
update the entire project schedule.
The default layout of the Schedule Manager perspective
contains a single Schedule Manager view.
For information about Schedule Manager, see the
Schedule Manager Guide.
Note The Schedule Manager view provides
scheduling information for 4D analysis in
Manufacturing Process Planner. Scheduling
tasks are associated with process activities to
allow a planner to visualize what parts of a
structure are already assembled by a specific
date in a given area of a product. In this view,
you can perform all schedule management
tasks that you can in the Schedule Manager
application perspective. In Manufacturing
Process Planner, the view displays the schedule
name in the view tab.
For more information, see the Manufacturing
Process Planner Guide.

Note The Schedule Manager view is also displayed

as the Service Scheduler view in the Service
Scheduler application. The Service Scheduler
view is not listed in the Show View dialog box.

PLM00191 J Rich Client Interface Guide 2-23

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Specification Lets you view and work with specifications that
Manager capture the complete definition of products and how to
manufacture them.
The default layout of the Specification Manager
perspective contains a single Specification Manager
view.
For information about Specification Manager, see the
Specification Manager Guide.
Structure Enables you to create, edit, and configure product
Manager structures.
The default layout of the Structure Manager perspective
contains a single Structure Manager view.
For information about Structure Manager, see Getting
Started with Product Structure.
Workflow Enables you to view in-progress workflow processes and
Viewer related data.
The default layout of the Workflow Viewer perspective
contains a single Workflow Viewer view.
For information about Workflow Viewer, see the
Workflow Viewer Guide.

CAE Manager views

View Symbol Description

Analysis Provided as part of the CAE Manager perspective,
this view lets you interactively define and populate
CAEAnalysis item revisions that can reference a
defining CAEModel item. It lets you manage the solver
execution results, relate the results to a CAEAnalysis
item, and assign other analysis inputs that define CAE
analysis.
For more information, see the Simulation Process
Management Guide.
Attachments Provided as part of the CAE Manager perspective, this
view lets you view and manage attachments to the
selected line or item revision, for example, a dataset or
form.
For more information about CAE Manager views, see
the Simulation Process Management Guide.

2-24 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

CAE Provided as part of the CAE Manager perspective, this
Accountability view lets you compare attribute values between related
Check instances of a model structure and a product structure.
For more information, see Simulation Process
Management Guide.
Composite Provided as part of the CAE Manager perspective, this
view lets you view and manage a hybrid structure of
references for all lines of a CAE model structure (in
Product view), product structure (in Model view), and
CAE Analysis item revision (in Analysis view) at one
time.
For more information about CAE Manager views, see
the Simulation Process Management Guide.
Graphics Provided as part of the CAE Manager perspective, this
view displays any visualization data associated with the
selected structure or object in the primary view.
For more information about CAE Manager views, see
the Simulation Process Management Guide.
Inspector Provided as part of the CAE Manager perspective, this
view lets you evaluate the CAEModel structure against
the product structure.
For more information, see the Simulation Process
Management Guide.
Model Provided as part of the CAE Manager perspective,
this view lets you interactively define and manipulate
hierarchical CAE models that can reference target
product models and source products or CAE geometry.
For more information, see Simulation Process
Management Guide.
Product Provided as part of the CAE Manager perspective, this
view lets you interactively identify hierarchical product
structures that are referenced by CAEModel items.
For more information, see Simulation Process
Management Guide.
Target Provided as part of the CAE Manager perspective, this
References view lets you view a product structure represented by a
CAE model structure.
For more information about CAE Manager views, see
the Simulation Process Management Guide.

PLM00191 J Rich Client Interface Guide 2-25

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Variants Provided as part of the CAE Manager perspective, this
view lets you display and edit variant options, option
defaults, and rule checks currently defined for the
product selected in the structure pane.
For more information, see the Getting Started with
Product Structure guide.

CAE Manager (Legacy) views

View Symbol Description

Inspector Provided as part of the CAE Manager perspective, this
view lets you evaluate the CAEModel structure against
the product structure.
For more information, see the Simulation Process
Management Guide.

Change Management views

View Symbol Description

BOM Changes Displays changes to the structure of the selected object,
based on the displayed engineering change.
For more information about this view, see the Change
Manager Guide.
Change Displays the end item effectivity information for the
Effectivity selected impacted/solution items in an enterprise change
notice. End item effectivity information is created,
modified, and displayed in this view.
For more information about this view, see the Change
Manager Guide.
Change Home Contains saved searches for change objects defined by
system administrators and users. The default search is
My Open Changes.
For more information about this view, see the Change
Manager Guide.
Open Change Displays change folders and any attached forms or other
objects.
For more information about this view, see the Change
Manager Guide.
Open Task Displays change folders associated with a Schedule
Manager task used for work breakdown planning
For more information about this view, see the Change
Manager Guide.

2-26 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Roll Up Displays all objects in the folders of the selected change
and its associated work breakdown tasks at one level,
eliminating the need to look through multiple levels of
the work breakdown structure.
For more information about this view, see the Change
Manager Guide.

Content Management views

View Symbol Description

Preview Displays the published content of an XML or SGML
publication.
For more information about content authoring and
Content Management administration, see the Content
Management Guide.
Publication Enables you to navigate, create, and maintain
Structure the structure of a publication with XML or SGML
components, by adding, removing, and moving topics.
For more information about content authoring and
Content Management administration, see the Content
Management Guide.

Diagnostic views

View Symbol Description

Communication Not displayed by default in any perspective, the
Monitor Communication Monitor view lets you see the calls
made between the rich client and server.
For information about using Communication Monitor,
see the Client Customization Programmer’s Guide.
DB Walker This view is intended for Siemens PLM internal use
only and should be used only when advised by customer
support.
For information about DB Walker, see the Client
Customization Programmer’s Guide.
Print Object Not displayed by default in any perspective, the Print
Object view lets you see an object’s internal attribute
values.
For information about using Print Object, see the Client
Customization Programmer’s Guide.

PLM00191 J Rich Client Interface Guide 2-27

Chapter 2 Managing the Teamcenter client interface

Issue Management views

View Symbol Description

Issue Home Provided as part of the Issue Manager perspective to let
you track problems, or issues, with a product by letting
you manage the review, approval, and implementation
of the issue.
For information, see the Issue Manager Guide.
Issue List Provided as part of the Issue Manager perspective,
Details displays details about all issues, visual issues, or
penetration requests in a list of issues, such as a list of
all the issues that you created.
For information, see the Issue Manager Guide.
Issue Preview Provided as part of the Issue Manager perspective,
displays thumbnail images captured before and after a
fix for each issue report revision selected.
For information, see the Issue Manager Guide.

Manufacturing views

View Symbol Description

2D Viewer For snapshots associated with a line in a product
structure, displays an attached image dataset. If there
are multiple image datasets attached, you can select the
desired image.
For more information about using 2D snapshots, see the
Manufacturing Process Planner Guide.
4D Results Displays the results of running a 4D analysis. This
analysis is performed on a process with associated task
and part data. You can query a process, taking the date
into consideration, to ascertain what has been built up
to and including a specific date.
For more information about using 2D snapshots, see the
Manufacturing Process Planner Guide.
Accountability Lets you manage the results of the last accountability
Check check that you run in Manufacturing Process Planner
perspective. This report lists the problem lines in the
source and target and provides a list of conflict details.
For information about using the Accountability Check
view, see the Manufacturing Process Planner Guide.
Activities Displays all activities to be completed as part of
the operation selected in a process. This view is
structure-dependent (it displays a tree table).
For more information, see the Manufacturing Process
Planner Guide.

2-28 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Activity Gantt Provides a visual depiction of the start time and
duration for all the activities scheduled for an operation.
The chart is organized according to the resources
assigned to each activity. If more than one resource is
assigned to the same activity, a separate line displays
for each activity and resource pair.
For information about using this view, see the Part
Planner Guide.
Assignments This view lets you create and edit the logical
assignments of a process or operation
For more information, see the Manufacturing Process
Planner Guide.
Attachments Displays the properties of all related components
(including the base item component and all related
subcomponents) of the object selected in the structure
view.
The Attachments view is a structure-dependent data
view, which is always available when an object is
selected in a structure view.
For more information, see the Manufacturing Process
Planner Guide.
Classification Displays attribute values that exist in the Classification
Properties application for the object currently selected in the
structure view if that object is classified. Although
you can open this view in several manufacturing
perspectives, you can only edit Classification attribute
values in Resource Manager.
For more information, see the Resource Manager Guide.
Classification Displays matches found when searching for resources
Table in Resource Manager using the Classification Search
Dialog or the object ID search. The Classification Table
view manages multiple search results.
For more information, see the Resource Manager Guide.
Collaboration Shows all open structures in the application.
Context Tree
For more information, see the Manufacturing Process
Planner Guide.

PLM00191 J Rich Client Interface Guide 2-29

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Generic BOP Displays a process plan that represents the processes
for building a generic product for a type of product.
For example, you can define a generic process plan
for building any model of pickup truck. You build
this process plan from standard tools, processes, and
operations, excluding elements that are unique to a
particular model.
For more information, see Getting Started with
Manufacturing.
Graphics Displays any visualization data associated with the
selected structure. The Graphics view is closely
associated with the primary view from which you open
it. If you close the associated primary view, Teamcenter
closes the Graphics view as well.
For more information about displaying images in this
view, see the Manufacturing Process Planner Guide.
Incremental The Incremental Change view allows you to add, edit,
Change or remove incremental changes from a selected line.
For more information, see the Manufacturing Process
Planner Guide.
Intermediate The Intermediate Data Capture view displays any
Data Capture intermediate data captures associated with the selected
structure. You can switch between captured states of an
IDC by selecting from the Captured State list.
For more information, see the Manufacturing Process
Planner Guide.
Line Presents a bar chart where the horizontal axis shows the
Balancing process areas or active resources (worker or machine).
Chart
For more information, see the Manufacturing Process
Planner Guide.
Line Lets you check whether there are any overall constraint
Balancing violations within the process station.
Constraints
For more information, see the Manufacturing Process
Planner Guide.

2-30 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Linked Shows whether the selected BOM line (occurrence) is
Occurrence linked to something else from its associated product or
Paths plant structures.
The complete path is displayed in this view so you can
identify exactly what is being consumed (for example,
the left front or right front wheel). You can also remove
the links or identify a corresponding BOM line in the
associated product/plant structure view using menu
commands in the shortcut menu.
For more information, see Manufacturing Process
Planner Guide.
Made From Enables you to view the stock materials or standard
parts from which the parts in your program are made.
For more information about stock materials, see the
Aerospace and Defense Solution Guide.
Manufacturing Shows all the manufacturing features under the current
Features product scope in a table-like view.
For more information, see Manufacturing Process
Planner Guide.
PAD One of three views that helps you work with Process
Assembly Documents. The PAD view displays
information about the MEPAD item and lists its child
MEPSD items.
For information about the PAD view, see the
Manufacturing Process Planner Guide.
PAD Element One of three views that helps you work with Process
Assembly Documents. The PAD Element view displays
information about the MEPADElement items and assists
you in consuming elements into the PAD structure.
For information about the PAD Element view, see the
Manufacturing Process Planner Guide.
Part Planner Displays all activities to be completed as part of the
Activities operation selected in a process. In addition, it displays
tool number, start, and duration times for each of the
activities.
For information about creating operations and activities,
see the Part Planner Guide.

PLM00191 J Rich Client Interface Guide 2-31

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

PERT Use for a process displayed in a structure view or for
activities displayed in the Activities view.
• When opened on a process, this view shows the
sequence of the first-level processes or operations
that exist for the selected process.

• When opened on a top-level activity, the PERT chart

displays the first-level activities.

For information about using the PERT view, see the

Manufacturing Process Planner Guide.
Plant BOP Displays a process plan that represents all processes
or operations that are performed at a specific plant or
work station.
For more information, see Getting Started with
Manufacturing.
Process A primary structure view that displays the processes
and operations required to manufacture a product.
For more information about using the Process view, see
the Manufacturing Process Planner Guide.
Process Gantt Displays processes and operations and the relations
between them in a chart. A process Gantt chart is a bar
chart that illustrates the work breakdown structure
of a project. It illustrates the start and finish times of
the operations or processes and summary elements
(operations or higher level processes) of the project using
a time line. The Gantt chart also shows the dependency
(sequence) relationships between the elements.
For more information about the Process Gantt view, see
the Manufacturing Process Planner Guide.
Product A primary structure view that displays the product
that you want to manufacture in a hierarchical tree
structure.
For more information about the Product view, see the
Manufacturing Process Planner Guide.
Product BOP Displays a process plan that represents the processes
for building a particular model. It is derived from the
generic BOP for the corresponding type of product,
allowing for commonality and reuse between different
products of the same type.
For more information, see Getting Started with
Manufacturing.

2-32 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Product Displays work instructions created using a Product
Manual Manual role.
For information about work instructions, see the
Manufacturing Process Planner Guide.
Product View Lets you search for all product views associated with a
Search particular part so that you can update them.
For more information about searching for product views,
see the Manufacturing Process Planner Guide.
PSD One of three views that helps you work with Process
Assembly Documents. The PSD view displays
information about the MEPSD item and lists its child
MEPADElement items.
For more information about working with process
assembly documents, see the Manufacturing Process
Planner Guide.
Report Lets you create reports for all three types of structures:
products, processes (including their operations and
activities) and plants. The generated report is presented
through a browser window.
You can create customized style sheets or use other
formatting tools to customize both the data content and
the report format.
For more information about generating reports, see the
Report Generator Guide.
Required Displays the items that are assigned to a manufacturing
Items process using the MERequired relation.
These are objects that are used by a process but not
consumed by it, such as glue or heat treatment.
For more information, see the Manufacturing Process
Planner Guide.
Resource Displays a tree hierarchy representing the logical
built-up structure of the assembly. The root node
represents the assembly itself. The subnodes are links
to the components that make up the assembly. All node
names contain the object ID and optionally a textual
description that you can use to identify the object.
For more information about this view, see the Resource
Manager Guide.

PLM00191 J Rich Client Interface Guide 2-33

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Search Study Displays all the studies that contain a selected process or
Results operation. The Search Study Results view opens when
you run the Search Study command in Manufacturing
Process Planner.
For more information, see the Manufacturing Process
Planner Guide.
Standard Text Used to create and manage the standard text elements
such as text, data collection definitions, and symbols
that are compiled to create textual work instructions.
The Standard Text view is generally used by the
standard text librarian to manage the elements that
the work instruction author chooses to create work
instructions.
For more information about working with standard text
elements, see the Manufacturing Process Planner Guide.
Standard Text Displays the hierarchy of folders that contain standard
Library text elements.
Each standard text element can be associated with
specific content comprised of text, data collection
information, and symbols. Following is an example of a
standard text library structure and the standard text
editor displaying a preview of specific standard text
content.
For more information about working with standard text
libraries, see the Manufacturing Process Planner Guide.
Structure Provided for use with the Manufacturing Process
Search Planner and Multi-Structure Manager perspectives. Lets
you perform several types of queries, as well as configure
your own searches. You can search a manufacturing
structure using various properties of the structure’s
lines. It then reports the results in the Structure Search
Results view.
• The search mechanism searches a structure using
structure line properties.

• The search is not limited to the loaded lines of

the structure and can search an entire structure
without loading it. It then expands the structure
to the found lines.

For more information, see the Manufacturing Process

Planner Guide or the Multi-Structure Manager Guide.
Structure Displays the results of a structure search.
Search
Results For more information, see the Manufacturing Process
Planner Guide.

2-34 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Study Holds a manufacturing study. Studies are structures
used to scope elements of other structures. You can have
a shared study where changes made to the study are
also made to the source structure or isolated studies
where the changes to the source structures are not
reflected in the study.
A planner can decide to propagate changes from the
study back to the source structure or synchronize
changes from the source structure to the study.
Studies are also used to pass data to Process Simulate
for use in event and time based simulations.
For more information, see the Manufacturing Process
Planner Guide.
Textual Work Use to author work instructions by choosing from a
Instructions library of standard text elements. Using this view, you
can quickly create or edit textual work instructions for
manufacturing processes or operations.
For more information about textual work instructions,
see the Manufacturing Process Planner Guide.
TiCon Search Accesses time data from TiCon, an external time
management system, using a web service and assign
the data to activities. You can search for time elements
in TiCon, create new activities, or overwrite existing
activities with the timing data of time elements, and
update activities assigned to time elements that were
changed in TiCon.
For more information TiCon searches, see the
Manufacturing Process Planner Guide.
Time Use to store individual times for each activity, operation,
or process in a process structure. This view provides
information specific to the process or operation so that
its appearance varies depending on which of these you
select.
For more information about managing times, see the
Manufacturing Process Planner Guide.
Tool Displays the tools that match the search criteria
Requirement contained in the tool requirement in both the work area
Resolver (and child work areas) associated to the immediate
process area and the classification hierarchy. Tool
requirements can be created under a process or
operation in a generic or product BOP.
For more information about managing times, see the
Manufacturing Process Planner Guide.

PLM00191 J Rich Client Interface Guide 2-35

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Variants Use to display and edit variant options, option defaults,
and rule checks currently defined for the product
selected in the structure pane.
For more information variant options, see the
Manufacturing Process Planner Guide and Getting
Started with Product Structure.
Work Use to create published pages containing manufacturing
Instruction data. You can organize collections of publishing pages
into portfolios, which you can view, publish to a Web
server or PDF, or print in My Teamcenter.
For information about creating, viewing, and editing
manufacturing documentation, see the Manufacturing
Process Planner Guide.
Workarea Displays a factory, plant, work station, or other
physical location in a manufacturing environment as a
hierarchical tree structure.
The root level identifies the high-level plant structure.
Each layer beneath the root level breaks down the
work areas within the plant until the lowest level in
the structure represents individual work areas where
specific operations are performed.
For more information, see the Plant Designer Guide.

Material Management
View Symbol Description
Material and Lets you roll up and display relevant material and
Substance substance information and details of materials of a part
Dashboard listed under item revisions,
For information about viewing material and substance
information, see the Materials Management Solution
Guide.

Projects views
View Symbol Description
AM Rules Displays the In Project branch of the rule tree, which is
used to apply access rules to project or program data.
For information see the Project and Program Guide.
Definition Used to create projects or programs and manage project
and program resources, including adding members,
assigning member privileges, and designating team
administrators.
For information see the Project and Program Guide.

2-36 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Libraries Displays data dictionaries (libraries) that have been
defined in the Classification Administration application,
and provides tools for associating these libraries with
specific projects or programs.
For information, see the Project and Program Guide.
My Projects Not displayed by default in any perspective, the My
Projects view is also accessible from the Quick Links
section of the navigation pane. The My Projects view
lets you work with the project smart folder hierarchy,
project data, project team, and project details panes.
For information about the My Projects view, see the My
Teamcenter Guide.
Project Enables administrators to control access to a Teamcenter
database that is used by multiple organizations, such
as project teams, development teams, suppliers,
and customers. Access to data is controlled on a
project-by-project basis.
For information about using Project, see the Project and
Program Guide.
Smart Used in conjunction with the Project perspective,
Folder Filter the Smart Folder Filter Configuration view lets
Configuration administrators set up the filter criteria against each of
the nodes in the top-level smart folder hierarchy or the
project specific smart folder hierarchy.
For information about the Smart Folder Filter
Configuration view, see the Project and Program Guide.

Schedule Manager views

View Symbol Description

Schedule Task Lets you update the execution data of a selected
Execution schedule task.
Select a schedule task in a My Teamcenter component
view such as a Home or My Worklist view, or in a
Search Results view, and then select the Schedule Task
Execution from the Show View dialog box displayed by
the Window®Show View®Other menu command.
The Schedule Task Execution can be opened in other
applications such as Schedule Manager and Change
Manager.
For information about the Schedule Task Execution
view, see the Schedule Manager Guide.

PLM00191 J Rich Client Interface Guide 2-37

Chapter 2 Managing the Teamcenter client interface

Service Manager views

View Symbol Description

Contains Displays the physical parts contained in the selected
physical location or the selected asset group.
For information about Service Manager, see the Service
Manager Guide.
Disposition Displays disposition state information for a physical
History part, including disposition type, operational status,
disposition assign time, and disposition end time.
For information about Service Manager, see the Service
Manager Guide.
Log Entries Displays the log entries recorded against a log book, or
log entries for a particular physical part.
For information about Service Manager, see the Service
Manager Guide.
Physical Part Displays part usage information for a physical part.
Usage History Usage information includes when a physical part was
installed, uninstalled, or replaced or when the location
of a physical part was changed.
For information about Service Manager, see the Service
Manager Guide.
Service Display a Details view and provides a menu with Show
Details Details, Show In Progress, Completed, Show Part
Movements information.
Service Editor Supports a wide range of tasks, such as edit part
logistics data, create lot definitions, create serial number
generators, and create physical location structures.
For information about Service Manager, see the Service
Manager Guide.
Utilization Display utilization information (life, date, and
observation characteristic values) on service events.
For information about Service Manager, see the Service
Manager Guide.

Service Planner views

View Symbol Description

Plan Details Displays the details about the selected service plan,
service partition, service requirement, work card, or
activity.
For information about Service Planner, see the Service
Planner Guide.

2-38 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Service Plan Displays the Service Plan view in the Service Planner
application.
For information about Service Planner, see the Service
Planner Guide.

Service Request Manager views

View Symbol Description

Request Displays open service requests in the Service Request
Home Manager application.
For information about Service Request Manager, see the
Service Request Manager Guide.
Service Displays the status of a service request, including
Request closure, maturity, and disposition states, as well as the
Status request date of the service request and or needed by
date of the requested activity of all lower level service
requests and requested activities.
For information about Service Request Manager, see the
Service Request Manager Guide.

Service Scheduler views

View Symbol Description

Service Lets you schedule service activities.
Scheduler
Work Order Displays work orders.
Home

Substance Compliance

View Symbol Description

Substance Lets you roll up and display relevant material and
Compliance substance information and details of materials of a part
Dashboard listed under item revisions,
For information about viewing substance compliance
summary information, see the Substance Compliance
Solution Guide.

Systems Engineering

View Symbol Description

Associated Lists the signals associated with the selected interface
Signals or connection in the function or logical structure.

PLM00191 J Rich Client Interface Guide 2-39

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

BOM Compare Systems Engineering application view that is not used
Report in this version.
Budgets Lets you associate quantifiable requirements and values
with a structure for managing targets and goals across
the life cycle.
For more information on budgets, see the Systems
Engineering Guide.
Custom Notes Used to capture issues, actions, questions, or other
ad hoc types of information. Custom notes contain
anything and are edited with Microsoft Word.
For information about adding information using custom
notes, see the Systems Engineering Guide.
Diagram Lists available diagrams for a selected function.
Explorer
Function Lets you use functions to represent the purpose of a
system element, showing how that system or subsystem
works.
For information about defining system functions, see the
Systems Engineering Guide.
Logical Block Lets you illustrate systems and system elements by
building decompositions that capture the relationships
and interactions among the subsystems.
For information about describing solution alternatives,
see the Systems Engineering Guide.
Requirement Displays input parameters to CAD models for NX
Expression parts for a requirement design and condition formula,
variables, and severity level for NX parts for a
requirement validation.
For information about using validation requirements,
see the Systems Engineering Guide.
Requirements Enables the identification, allocation, and ongoing
maintenance of product requirements.
For information about developing and managing
requirements, see the Systems Engineering Guide.
Traceability Lets you view defining and complying relationships,
generate traceability reports, and check requirement
structures against product and process structures
For more information about how to view defining and
complying relationships, see the Systems Engineering
Guide.

2-40 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Traceability Lets you display information about trace links between
Matrix two selected structures, for example, a requirement
specification and a functional model. In its rows and
columns, the Traceability Matrix view reports certain
details that help you analyze allocations among the
structure elements.
For more information about the Traceability Matrix view,
see the Systems Engineering Guide.

Teamcenter views

View Symbol Description

BOM Markup Lets you review and comment on BOM markup.
View
For information about BOM markup functionality, see
the Structure Manager Guide.
Content Shows the contents of a selected collaborative design,
Explorer design element, partition, workset, or subset definition.
Any object you open in 4G Designer is shown in this
view. The content of the object is shown in a standard
explorer format.
For more information, see the 4th Generation Design
Guide.
Content Lets you define and execute searches of a collaborative
Search design, subset definition, or partition for content. You
can open it from a Content Explorer view and use it to
search a single context.
For more information, see the 4th Generation Design
Guide.
Details Provides attribute property information for selected
items. This is a default view in the My Teamcenter
perspective.
For information about the Details view in the My
Teamcenter perspective, see the My Teamcenter Guide.
Effectivity Displays the end item effectivity information for the
selected impacted/solution items in an enterprise
change notice. End item effectivity information is
created, modified, and displayed in this view. Clicking
the Create button opens the Create Effectivity dialog
box. Use this dialog box to search for end items and to
set unit and date effectivities.
For more information about the Effectivity view, see the
Change Manager Guide.

PLM00191 J Rich Client Interface Guide 2-41

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Image Preview One of the Lifecycle Viewer perspective views. This
view displays a 2D image associated with the selected
object, if such an image is available.
For information about the Image Preview view from
Lifecycle Viewer, see Getting Started with Product
Visualization.
Impact Provides graphical where-used and where-referenced
Analysis search capabilities. This is a default view in the My
Teamcenter perspective.
For information about the Details view in My
Teamcenter, see My Teamcenter Guide.
JT Preview Provided as part of the Lifecycle Viewer perspective.
For information about JT Preview, see Getting Started
with Product Visualization.
L10N Result Displays objects found by the localization filter search
View based on translation criteria.
For information about using the localization Filter
Objects dialog box, see the Localization Guide.
MS Word In the Teamcenter systems engineering and
requirements management perspective, lets you view
and edit requirement content in an embedded Word
window.
For information about Teamcenter systems engineering
and requirements management, see the Systems
Engineering Guide.
Process Displays the Workflow or Schedule Manager process of
History the business object selected in the Home, My Worklist,
or Search Results view in My Teamcenter.
For more information, see Getting Started with
Workflow.
Recipe Display and edit the recipe applied to subsets, subset
design elements and dynamic partitions in the Content
Explorer. You can open one or more Recipe views for
each view network.
For more information, see the 4th Generation Design
Guide.

2-42 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Relation The Relation Browser view is part of the Relation
Browser Browser perspective. In conjunction with the Image
Thumbnail Preview, Graph Overview, and Properties
views, you use Relation Browser to perform basic tasks
such browsing object relations, viewing 2D images,
locating an object graphically in a map of relations, and
examining the properties of a selected object.
For information about Relation Browser, see the
Relation Browser Guide.
Saved Variant Lets you manage saved variant rules (SVRs). The view
Rules lists all SVRs for the current item revision. Click a field
to display the secondary Variant Expressions Editor
view to add, remove, and edit rules.
For more information, see the Product Configurator
Guide.
Search The Search view is available for use in any perspective.
For information about the Search view, see Using the
Search view.
Search The Search view is available for use in any perspective.
Results
For information about the Search Results view, see
Using the Search Results view.
Simple Search Lets you create business object searches based on one
or more property values.
For information about the Simple Search view, see
Using simple search.
Specification Displayed when you start Specification Manager to let
Manager you search for specifications by either ID or name
For more information, see the Specification Manager
Guide.
Variant Used to set variant conditions on one or more conditional
Conditions model elements, for example, design elements, design
features, and partitions.
For more information, see the 4th Generation Design
Guide.
Variant Lets you view and define the variant scope for content
Configuration such as design elements. Objects that have a defined
variant condition can be filtered based on variant
configurations.
For more information about the Variant Configuration
view, see the 4th Generation Design Guide.

PLM00191 J Rich Client Interface Guide 2-43

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Variant Lets you define constraints (rule checks) for selected
Constraints value in the context of the current item.
For more information, see the Product Configurator
Guide.
Variant Lets you define derived default rules within the context
Defaults of the currently selected item.
For more information, see the Product Configurator
Guide.
Variant Lets you view and edit the details of one or more variant
Expression expressions. It is a secondary view of any other view
Editor that lists variant expressions, including the Variant
Defaults, Variant Constraints, and Saved Variant Rules
views.
For more information, see the Product Configurator
Guide.
Variant Lets you create or edit option groups, families, and
Options values. The variant options are organized in a tree table,
with groups at the top level of the tree. Each group
displays the option families allocated to it as children.
Each family displays its list of values as children.
For more information, see the Product Configurator
Guide.
Visio Diagram Use to capture system logic and connectivity; how the
elements that make up a product are connected. Shapes
in the stencil are pre-mapped to Teamcenter objects.
As these shapes from the mapped stencils are dropped
on the diagram, objects and relationships are created
in Teamcenter.
Note This view is currently used only by the Systems
Engineering application.

For information about diagramming functional and

logical decompositions, see the Systems Engineering
Guide
Where Displayed as part of the My Teamcenter perspective,
Allocated this view lets you find allocations belonging to a BOM
revision. Allocations are created and used in the
Multi-Structure Manager application.
For information about using the Where Allocated view,
see the Multi-Structure Manager Guide.

2-44 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Utilities views

View Symbol Description

Dashboard Shows the Teamcenter Reporting and Analytics
dashboard.
For more information about the Dashboard application,
see Report Builder Guide.
Database Used to execute batch utilities from Teamcenter and
Utilities determine Teamcenter volume information such as the
node on which the volume exists, the node name, and
the volume name.
For information about using the Database Utilities view,
see Getting Started with Automotive Edition.
Registry Enables the editing of Teamcenter rich client registry
Editor files. This view is used only for editing registry
files that are used for internationalization, dynamic
class invocation, and configuration in the rich client
framework.
For information about using Registry Editor, see the
Registry Editor Guide.
Web Browser Provides access to Web pages from within the rich client
framework. Web Browser is a rich client view that lets
you navigate to Web pages and view Web pages within
the rich client rather than switching to a separate Web
browser. Web Browser also provides the ability to access
MIME (Multipurpose Internet Mail Extension) file types
and to view files created in other applications, such as
Microsoft Word and Excel, through the Web browser.
The default layout of the Web Browser perspective
contains a single Web Browser view.
For information about Web Browser, see the Application
Administration Guide.

Validation Manager views

View Symbol Description

BOM Grading Used in the Validation Manager application.
Result
For information about using the Validation Manager
perspective, see the Validation Manager Guide.

PLM00191 J Rich Client Interface Guide 2-45

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Validation Used in the Validation Manager application to ensure
Agent Viewer an item revision meets compliance before it is released.
Once validation processes are configured, users can
select an item revision from a view in My Teamcenter
and confirm its compliance with the business rules
defined at your site.
For information about using the Validation Manager
perspective, see the Validation Manager Guide.
Validation Used in the Validation Manager application.
Results
Viewer For information about using the Validation Manager
perspective, see the Validation Manager Guide.

Visualization views

View Symbol Description

3D Viewer Provided to support manufacturing, issue management,
structure management, and part planning functionality.
For information, see Working with 3D Models.
Assembly Provided as part of the Lifecycle Viewer perspective for
visualization of parts and assemblies. Lifecycle Viewer
provides multiple views that let you display and work
with design data typically stored in CAD-data formats.
For information about Lifecycle Viewer, see Getting
Started with Product Visualization.
Compare Provided for comparing ECAD documents as part of
Lifecycle Viewer perspective.
For information about the Compare view, see Getting
Started with Product Visualization.
Constraints Provided for managing part constraints as part of the
Lifecycle Viewer perspective.
For information about the Constraints view, see Getting
Started with Product Visualization.
Cross Provided as part of Lifecycle Viewer perspective.
Sections
For information about the Cross Sections view, see
Getting Started with Product Visualization.
ECAD DXF Provided as part of the Lifecycle Viewer perspective.
For information about using Lifecycle Viewer, see
Getting Started with Product Visualization.
ECAD Layer Provided as part of the Lifecycle Viewer perspective.
For information about Lifecycle Viewer, see Getting
Started with Product Visualization.

2-46 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Groups Provided as part of Lifecycle Viewer perspective.
For information about using Lifecycle Viewer, see
Getting Started with Product Visualization.
Navigator Provided as part of Lifecycle Viewer perspective.
For information about Navigator, see Getting Started
with Product Visualization.
PMI Provided as part of the Lifecycle Viewer perspective.
For information about using Lifecycle Viewer, see
Getting Started with Product Visualization.
Paths Provided as part of Lifecycle Viewer perspective.
For information about using Lifecycle Viewer, see
Getting Started with Product Visualization.
Snapshots Provided as part of the Lifecycle Viewer perspective.
For information about using Lifecycle Viewer, see
Getting Started with Product Visualization.

Other views

View Symbol Description

ADA License Part of the ADA License application used to
Details access International Traffic in Arms Regulations
(ITAR), intellectual property (IP), and exclusion
license administration capabilities as a non-DBA
groupTeamcenter user.
For more information about this view, see the Authorized
Data Access License Guide.
ADA Licenses Part of the ADA License application used to
access International Traffic in Arms Regulations
(ITAR), intellectual property (IP), and exclusion
license administration capabilities as a non-DBA
groupTeamcenter user.
For more information about this view, see the Authorized
Data Access License Guide.
Assigned In the Software Parameter Manager, lets you select the
Parameters memory block or memory layout you want to view or
assign parameters.
For more information, see the Embedded Software
Solutions Guide.

PLM00191 J Rich Client Interface Guide 2-47

Chapter 2 Managing the Teamcenter client interface

View Symbol Description

Authorization System administrators use Authorization to grant
access to Teamcenter administrative applications and
utilities to users based on their group membership or
their role in a group.
This is the single view in the default layout of the
Authorization perspective.
For information about Authorization, see the Application
Administration Guide.
Available After viewing the parameter, lets you assign more
Parameters parameters by selecting one or more parameters.
For more information, see the Embedded Software
Solutions Guide.
Graph Part of the Relation Browser perspective. This view
Overview shows the entire layout of the graph, regardless of
the zoom factor, with a box around the area currently
displayed in the graph view.
For information about the Relation Browser perspective,
see the Relation Browser Guide.
Graph One of the Lifecycle Viewer perspective views and part
Thumbnail of the Relation Browser perspective. This view displays
Preview a 2D image associated with the selected object, if such
an image is available.
For information about the Relation Browser perspective,
see Relation Browser Guide.
Home This is a Teamcenter component view that displays a
searchable tree view of Teamcenter components.
For information about Teamcenter Component views in
My Teamcenter, see the My Teamcenter Guide.
Launch Pad Provides a visual desktop to place items and notes,
called nodes, for quick reference in either a carousel or
grid display mode.
For information about the Launch Pad view, see Using
the Launch Pad.
Memory Lets you create and manage memory layouts and blocks.
Layout
For information, see the Embedded Software Solutions
Guide.
Open in SR Displays the Open Service Request view in the Service
Manager Request Manager application.
For information about Service Request Manager, see the
Service Request Manager Guide.

2-48 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

View Symbol Description

Report Generates reports on products, manufacturing processes,
Generator and plant structures managed by Manufacturing
Process Management.
The default layout of the Report Generator perspective
contains a single Report Generator view.
For information about Report Generator, see the Report
Generator Guide.
Search The Search view is available for use in any perspective.
Results
For information about the Search Results view, see
Using the Search Results view.
Snapshot Lets you manage 2D snapshots, which are dynamic
Gallery objects that represent a 2D scene (a view of the base
image and markups) but are more than just image
captures.
For information about working with 2D snapshots using
Teamcenter and Lifecycle Visualization, see Working
with 2D Images.
Teamcenter Provides navigation and selection capabilities. This
Component view adopts the name of the root object in the current
navigation tree and displays the root object type symbol
in the view tab. This is a default view in the My
Teamcenter perspective. This view displays the Home
folder at startup.
For information about Teamcenter Component views in
My Teamcenter, see the My Teamcenter Guide.
Variant Lets you view and define the variant scope for content
Configuration such as design elements. Objects that have a defined
variant condition can be filtered based on variant
configurations
For more information, see the 4th Generation Design
Guide.
Viewer Displays visualization files or summary attributes for
a selected object. This is a default view in the My
Teamcenter perspective.
For information about the Viewer view in My
Teamcenter, see the My Teamcenter Guide.

Commonly used views

In the rich client, an application perspective can use views that are exclusive to a
particular perspective and can also incorporate views that work with two or more
perspectives.
• Views that are used in multiple perspectives are described as commonly used
views.

PLM00191 J Rich Client Interface Guide 2-49

Chapter 2 Managing the Teamcenter client interface

• Commonly used views, such as the Properties, Summary, and Details views,
work identically in each perspective and can be useful in a variety of situations.

• To provide online help for commonly used views, many of these are documented
in this guide, with links provided to additional material relevant to the
applications that may use these views.

Component views
The Teamcenter Component view is opened by default by several Teamcenter
perspectives.
Component views support standard navigation functionality such as expand,
expand-all, and double-click, as well as standard context-specific shortcut menus.

To manually open a component view:

1. Choose Window®Show View®Other....
The Show View dialog box is displayed.

2. Expand the Other folder.

3. Select Teamcenter Component.

To open an object in a new component view, you can:

• Select an object in the navigation pane, right-click, and choose Send to®My
Teamcenter.

• Select an object in a current component view and choose File→Open.

• Double-click an item or item revision in a current component view.

In the My Teamcenter perspective, the default component view is the Home view,
and every object opened in My Teamcenter gets its own component view.
When you open an object in My Teamcenter, a new component view opens with
the opened object as the root.
This view lets you navigate the content of the opened object. For example, opening
My Worklist from the navigation pane opens an instance of the component view
with your worklist as the root node. Similarly, opening the Newstuff folder opens a
component view with your Newstuff as the root node and clicking My Projects opens
a component view with your current project as the default node.
A component view includes the following elements:

2-50 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

• Filter Text box and Find something locally button

Finds objects currently or previously expanded and displayed in the current
component view and whose display names match the filter text.
Note
Click the Find something locally button to display the filter text
box, and then type text to begin the dynamic results filtering. You can
expand returned objects to find matching values.

• Collapse to the root object button

• Expand the selected objects button

• Expand the selected objects to all levels button

When you click this button, a dialog box is displayed to show progress. You can
choose to run the operation in the background or cancel the operation.

• View menu
Contains:
o The Move menu, for moving selected objects to a different level in the tree
display.
Up moves a selected folder up (for example, closer to the top-level folder) to
the area of the tree that you specify.
Down moves a selected folder down to a location that you specify.
Top moves a selected folder to the top of the tree.
Bottom moves a selected folder to the bottom of the tree.

Enable response to selections button

The selected object in the view can change when you select a different object
in an associated view.

The Teamcenter Component view is available by default in My Teamcenter.

For information about working with My Teamcenter, see the My Teamcenter Guide.

Details view table

Tables presented in separate views have their own menus for configuration.
The Details view presents a tabular display of properties of the children of the object
currently selected in the component view.
• Individual columns can be moved left or right by clicking and dragging the
column head to a new position.

• With objects selected in the table, you can right-click a column head to display
the shortcut menu.

PLM00191 J Rich Client Interface Guide 2-51

Chapter 2 Managing the Teamcenter client interface

Note The default display order for column contents in most views is specified by
the Teamcenter server. In the rich client, you can click a column header to
cycle through ascending, descending, and server default order. For rich client
Teamcenter component (tree) views and for the Search Results view, use
Edit®Options to display the Options dialog box, and then select UI and click
the General tab to select a Tree displaying order option.

The Details view menu includes the following options:

• Refresh
Refreshes the display in the Details view.

• Column
Displays the Column Management dialog box. Use this dialog box to select
properties to display and column order.

• Save Column Configuration

Displays the Save Column Configuration dialog box. Use this dialog box to save
the current column configuration of the Details view table display. You can access
saved column configurations using the Apply Column Configuration command.

• Apply Column Configuration

Displays the Apply Column Configuration dialog box.

o Select Default and click Apply to restore the default column configuration
to the Details view table display. This restores columns removed by the
right-click Remove this column command.

o Select and apply a previously saved column configuration to the Details

view table display.

• Sort
Provides three levels of sorting.

• Filter
Displays the Auto Filter dialog box with available condition expressions.
o The ALL option displays properties for all the children of the object currently
selected in the component view.

o You can use the Filter Condition Editor to create condition expressions for
filtering the display.

o Expressions cannot be edited after they are listed in the Auto Filter dialog
box, but they can be deleted.

o Teamcenter retains your filter condition expressions until you delete them.

To create conditions, click Add a new search condition to display the Filter
Condition Editor.

2-52 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

o To create an initial condition expression, select a property column value and

a logical operator, and then enter an object value or select one from the list of
objects displayed in the table, and then click Add a new search condition .
Note The = = operator tests for an exact match. The = operator tests for a
match but is not case sensitive.

o To expand the expression with additional conditions, use the ADD and OR
operators.

o Click Remove the selected condition(s) to delete the selected condition

line.

o Click Clean all the conditions to delete the entire expression.

o Click ...not meet the condition(s) to negate the selected condition.

o Click OK to add the condition expression to the Auto Filter dialog box.

• Find In Display
Displays the Find In Display dialog box that lets you find objects based on
property names and search values.

• Print Table
Lets you print to either HTML/Text using the Teamcenter Print dialog box, or
Graphics, using the system printers.

• Copy Selected Data

Lets you copy selected rows:

o With Headers

o Without Headers

o For Query
This option displays the Select Columns For Query dialog box in which you
can select specific properties to copy.

• Objects to Word
Displays the Export To Word dialog box. You can specify:

o Output: Static Snapshot, Live Integration with Word, Export for Markup

o Live options: Export for structure editing and work offline, Check out
objects before export
Note The checkout applies to all objects being exported. You should use
this option carefully if you are exporting a large set of objects or
perhaps an entire specification.

o Template override

PLM00191 J Rich Client Interface Guide 2-53

Chapter 2 Managing the Teamcenter client interface

To use a Word export template other than the default, select a template from
the Specification Templates list or select an object type from the Override
Object Template for: list. If you select an object type from the Override
Object Template for: list, you then select a template from the Available
Object Templates list to add to the table.

o Copy URL
The URL Generated message is displayed, confirming that the URL for the
export document is in your Windows Clipboard and showing the URL details.
Note The Copy URL button is unavailable if you select more than
one object to export.

The Copy URL button is unavailable if the Check out objects

before export option is selected.

o OK
Generate the export Word file.

• Objects to Excel
Displays the Export To Excel dialog box. You can specify:

o Object Selection
Either Export Selected Objects or Export All Objects in View.

o Output Template
Either Export All Visible Columns or Use Excel Template.
When you export all visible columns to Excel, the relation column is not
exported because the relation is not a property on the object.
The Use Excel Template option provides access to a list of templates.

o Output
Either Static Snapshot, Live integration with Excel (Interactive), Live
integration with Excel (Bulk Mode) or Work Offline and Import.
Note Export using work offline mode exports properties such as item_id,
object_name and the real type name so that the data can be
imported correctly to Teamcenter. These properties are exported
even if they are not specifically selected.
Only numeric and string properties are supported for import
from Excel. Read-only, reference, and relation properties should
be marked as Ignored in the Excel control file sheet. Run-time
properties also are not supported for work offline.

o To check out objects while exporting to live Excel, select Check out objects
before export.
Note The checkout applies to all objects being exported. You should use
this option carefully if you are exporting a large set of objects or
perhaps an entire specification.

2-54 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

o Copy URL
The URL Generated message is displayed, confirming that the URL for the
export document is in your Windows Clipboard and showing the URL details.
Note Copy URL is unavailable if you select more than one object to
export.

Copy URL becomes unavailable when you select any of the

following dialog box options:
◊ Export All Objects in View

◊ Export All Visible Columns

◊ Work Offline and Import

◊ Check out objects before export

o OK
Generate the export Excel file.

• Objects to CSV
Displays the Export To CSV dialog box to export Teamcenter data in
comma-separated value (CSV) format. You can specify:

o Export all Objects in View

o Export Selected Objects

Note To export to alternate character set languages and have readable output
in Microsoft Excel, you may need to set the proper language in Microsoft
Excel. For example, for Chinese PRC in Microsoft Excel 2010, choose
File®Options®Language®Editing Language : Chinese PRC.

The Details view is available by default in My Teamcenter.

For information about working with My Teamcenter, see the My Teamcenter Guide.

Configure the Details view table

1. In the Details view, click the View Menu button and then choose Column
from the view menu.
The Column Management dialog box appears.

PLM00191 J Rich Client Interface Guide 2-55

Chapter 2 Managing the Teamcenter client interface

2. Add or remove columns from the Details view table.

a. To add a column, select a property from the Available Properties list and
click the Add to Displayed Columns button .

b. To remove a column, select a property in the Displayed Columns list and

click the Remove from Displayed Columns button .

3. (Optional) Click the Move Up and Move Down buttons, to the right of the
Displayed Columns list, to adjust the order of the displayed columns.

4. Click Apply to apply the configuration to the current view, or click Save to save
the configuration for later use.
Note You can use the Apply Column Configuration command on the view
menu to:
• Apply a saved configuration.

• Restore the default configuration. This is the only way to restore

columns removed using the right-click Remove this column
command.

You can use the Save Column Configuration command on the view
menu to save the current configuration of the table display.

5. Click Close to close the Column Management dialog box.

2-56 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Using the Graph Overview view

When you select an object in the navigation pane in an application that uses the
Graph Overview, such as the Relation Browser perspective, the Graph Overview
view displays the newly selected object as the root object.
If you zoom in on a complicated graph, the Graph Overview view shows your display
location within the graph. You can pan around the display in the Graph Overview
view to examine other objects.
The Graph Overview view is available by default in the Relation Browser application.
For information about using Relation Browser, see the Relation Browser Guide.

Display images in the Graphics view

Note The Graphics view is available for use in multiple applications. Not
all applications use all the functionality listed here and may add other
functionality as needed.
For additional information, see the documentation for your application.

If an image is associated with the object selected in a structure view, opening the
associated Graphics view displays that image.
The following image types are available in this view:
• DirectModel
Imported .jt files or .jt files created by the translators. These datasets containing
these files must be attached to the item or item revision with a Rendering
relation.

• DirectModelMarkup
Captured image of a DirectModel dataset.

• DrawingSheets and Markup

Imported .cgm files.

• Image
Imported .tif, .gif, .jpeg and similar file types.
Note If the images that are attached to the BOM line are 2D snapshots,
Teamcenter displays them in the 2D Viewer view.

When you open an image in the Graphics view, the Graphics menu is displayed
in the menu bar.
1. Right-click a line in the structure view and click in the view toolbar.
Teamcenter opens the Graphics view associated with the structure view from
which you open it.
Note Do not confuse this assembly viewer with the viewers that you can open
using the Open With shortcut menu command. The assembly viewer has
more features that you can use to view and manipulate 3D assemblies.

PLM00191 J Rich Client Interface Guide 2-57

Chapter 2 Managing the Teamcenter client interface

2. Select the check boxes next to the components in the tree that you want to display
in the Graphics view. If you select the root item, the entire structure is displayed.

The following states exist for the check boxes.

Check box State

The part or assembly is fully loaded and visible.

The assembly component is fully loaded but only partly

visible. This can be because a part is turned off or because
geometry does not exist for one or more parts.
The assembly component is partially loaded and only partially
visible.
All available geometry is visible, but geometry does not exist
for every part.
The part or assembly is loaded but not visible.

No geometry exists for the selected part, or if this is a parent

structure, it is not fully loaded and not visible.

Tip If you want to display a single component in a large structure, additionally

use the Viewer view that you open using the Open With shortcut menu
command.

Toolbars available in the Graphics view

Note The Graphics view is available for use in multiple applications. Not all
applications use all the tools listed here and may add other tools as needed.
For additional information, see the documentation for your application.

2-58 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Use this toolbar To

3D Alignment Move individual parts or groups of parts and
align them to other parts in the viewer.
3D Appearance Work with advanced appearance attributes.
3D CAE Viewing View Computer Aided Engineering (CAE) Finite
Element Analysis (FEA) results.
3D Clearance Check the clearance of parts in your model.
3D Comparison Compare the geometry of two sets of parts.
3D Coordinate System Create and manage coordinate systems. You
can also align parts or your view to a coordinate
system.
3D Display Modes Control the display mode of geometry in
the viewer. You can display geometry as
shaded, tessellated lines, feature lines, or any
combination of these. Tessellation or feature
lines hidden by other geometry can be viewed as
normal, semi-transparent, or invisible.
3D GDT Markup Insert GD&T markups on your 3D models.
3D Markup Add text or graphical elements on your 3D model
in the viewer.
3D Measurement Measure your 3D model.
3D Movie Capture Capture the contents of the viewer as you
move the camera around, show or hide parts,
transform parts, play animation sequences, and
play VFM motion files associated with your
model.
3D Navigation Manipulate the 3D view.
3D PMI Display and control Product and Manufacturing
Information (PMI) in your model.
Note PMI functionality is available only when
PMI is enabled on your system. If PMI
is enabled, you can right-click a part and
choose one of the following commands:
• Show PMI
Shows all effective PMI on the
selected part or subassembly and its
children.

• Toggle in PMI Tree

Adds PMI from the selected part or
subassembly and its children to the
PMI tree. Alternatively, if the part
or subassembly is already in the PMI
tree, Teamcenter removes it.

PLM00191 J Rich Client Interface Guide 2-59

Chapter 2 Managing the Teamcenter client interface

Use this toolbar To

3D Part Manipulation Manipulate parts by dragging.
3D Part Transformation Translate, rotate, and scale parts in your model.
3D Section Work with cross sections of your 3D model.
3D Selection Pick part entities.
3D Standard Views Examine your model from different views.
3D Thrustline Editor Create and manipulate thrustlines.
3D Visibility Hide obscuring parts and clip areas of your
model.
Create Markup Create product views, capture an image of the
current geometry or show or hide the 3D PMI
tree.
Print Print an image or display a print preview.

For more information about using these toolbars, see Getting Started with Product
Visualization.

Using the Image Preview view

When a selected node has an associated 2D preview image, the preview image is
displayed in the Image Preview view.
Note Display of thumbnail images in the graph view is controlled by the
TC_Graph_Node_Thumbnail_Shown preference.

For information about the using Image Preview view from Lifecycle Viewer, see
Getting Started with Product Visualization.

Impact Analysis view

The Impact Analysis view responds to the current selection in the active component
view and provides the following functionality:
• Search Text box and Find button. Search supports the following actions:

2-60 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

o Press Enter or click the Find button to start a search.

o Press F3, Page Down, or Down to find the next matching object.

o Press Page Up, or Up to find the previous matching object.

o Press Home to find the first matching object.

o Press End to find the last matching object.

• Clear button to clear the Search Text box.

• Open button to display the Open by Name dialog box that lets you use names,
wildcard characters, and revision level to find objects. You can copy found objects
to the clipboard, load all found components into the table, and step through
found components in groups.

• Where
Select either Referenced or Used.

• Depth
Select One Level, All Levels, or Top Level.

• Reverse horizontal layout style.

• Vertical layout style.

• Tree layout style.

• Where-Used/Referenced Report
Note
The Impact Analysis view lets you disable and enable responsiveness
to selections in other views, so you can keep the currently selected root object
in the view while you investigate other objects in other views.

Note Administrators can set the WhereReferencePOMPref preference to

display the Referenced (POM) search option in the Impact Analysis view.

This option returns all instances and classes found in the database that
contain references to the selected instance.
For more information, see the Preferences and Environment Variables
Reference.

The Impact Analysis view is available by default in My Teamcenter.

PLM00191 J Rich Client Interface Guide 2-61

Chapter 2 Managing the Teamcenter client interface

For information about working with My Teamcenter, see the My Teamcenter Guide.

Using the JT Preview view

When a selected node has an associated .jt part, the .jt part is displayed in the JT
Preview view.
For information about the using JT Preview view from Lifecycle Viewer, see Getting
Started with Product Visualization.

Using the Properties view

When you select an object in the navigation pane and send it to Relation Browser:
• The Relation Browser view displays the newly selected object as the root object.

• The Properties view displays properties of the object.

When you select a different node in the Relation Browser view, Properties view
displays properties of the newly selected object.
For information about using Relation Browser, see the Relation Browser Guide.

Using the Relation Browser view

The Relation Browser view provides the following features and functionality:
• When you select an object in the navigation pane, the Relation Browser view
displays the newly selected object as the root object, and the Properties view
displays properties of the object.

• Zoom in , zoom out , and fit content buttons are available.

• Choose a context from the Relation Browser view menu .

Menu command Description

Contexts→Default
Contexts→Traceability
View structure relations in the Relation
Browser view. In this context, defined
structure relations display when you show
successors or predecessors.
This is the default view context.
View trace links in the Relation Browser view.
In this context, defined trace links appear
when you show successors.

• Choose a layout orientation from the Relation Browser view menu .

Menu command Description

Hierarchical→ Creates a graph beginning with a top node
Top-to-Bottom and flowing to the bottom.

Hierarchical→ Right-to-Left Creates a graph beginning with node at the

right and flowing to the left.

2-62 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Menu command Description

Hierarchical→ Left-to-Right Creates a graph beginning with a node at the
left and flowing to the right.
Hierarchical→ Creates a graph beginning with a node at the
Bottom-to-Top bottom and flowing to the top.

Hierarchical→ Incremental Creates a graph beginning with a top node in

the upper-left corner and flowing to the bottom
and to the right.
Circular Displays group and tree structures within a
network in a ring and star pattern.
Orthographic Creates compact graphs with no overlaps,
few crossings, and few bends. It is most
appropriate for medium-sized sparse graphs.
Organic Creates a layout with the nodes spaced as
far away from each other as possible, still
while minimizing this distance. It is most
appropriate for undirected, complex graphs.
Balloon Creates a layout with a central node and child
nodes extending from this in a radial fashion.
It is most appropriate for large, hierarchical
structures.

• You can select any node to browse further related objects one level at a time.

• Each node has a type symbol and object string to represent the component on
the graph. If any node has an associated 2D preview image, the preview image
can be displayed as a thumbnail image along with the text string in the Relation
Browser layout and is also displayed in the Image Preview view.

• When you right-click a node in the graph, the shortcut menu displays the same
commands as when you select a node on the navigation pane tree, based on
the type of object.

• Each node can have predecessors and successors, based on the application with
which the object is associated. You can select an object and use the shortcut
menu to expand or collapse predecessors and successors. For example, an
application can show predecessors as where-referenced objects and can show
successors by showing default children context.

The Relation Browser view is available by default in the Relation Browser and
My Teamcenter applications.
For information about using Relation Browser, see the Relation Browser Guide.
For information about working with My Teamcenter, see the My Teamcenter Guide.

Summary view
The Summary view lets you see properties for a selected object and edit attributes
such as name or description for supported items for which you have appropriate
permissions.

PLM00191 J Rich Client Interface Guide 2-63

Chapter 2 Managing the Teamcenter client interface

The configuration and contents of the Summary view vary according to the
information display configured for type of object selected.
• The Summary view toolbar includes buttons to let you check out and edit the
properties of objects, check in and save edited properties, cancel checkout, or
save changes and keep checked out.

• The area at the top of the view displays basic information about the selected
object.

• The Summary view may include the following expandable and collapsible areas:
o One or more Properties areas

o A Preview if a 2D dataset is selected or is attached to the selected item or

item revision

2-64 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

o An Actions area listing actions appropriate to the selected object

• Tabs, such as Overview, Attachments, and History are displayed, as needed and
as configured, to organize information about the selected object.

• Action buttons, such as Copy, Save As, Revise, and Submit for Review are
displayed. The location of these buttons vary based on the objects selected.

• List, table or tree view selection buttons for objects.

• When the functionality is enabled, you can see when other users are available
for instant messaging with Microsoft Office Communicator. You can view the
current status of the owning and last modified users, and you can click the
Microsoft Office Communicator symbol in Teamcenter to initiate communication.

For information about configuring Teamcenter instant messaging with Microsoft

Office Communicator, see the Application Administration Guide.

• Within a specified area, the groups of objects within each tab (object sets) are
configured in the XRT style sheet. Each group of information can be configured
to display in table, list, tree, or thumbnail format. Each can also be supported
by action command buttons such as Cut and Copy.
For information about creating object sets, see the Client Customization
Programmer’s Guide.

The Summary view is available by default in My Teamcenter.

For information about working with My Teamcenter, see the My Teamcenter Guide.

Viewer view

The content displayed in the Viewer view depends on the type of the object selected
in the current component view or in the Details view.

• To display the form attributes, select a form object in a component view or in

the Details view.

• To display Microsoft Office datasets in the Viewer view, display the Viewer view
and then click the dataset in the component view.
Note When you double-click a dataset, the stand-alone Microsoft Office
application is launched with the dataset. If you then click the dataset in
the component view to display the contents of the dataset in the Viewer
view, you cannot save changes to the dataset from the stand-alone
application.

PLM00191 J Rich Client Interface Guide 2-65

Chapter 2 Managing the Teamcenter client interface

• To display Microsoft Office datasets on Microsoft Windows 7 systems in the

Viewer view rather than externally, you must install a patch or initiate an action
provided by Microsoft Support.
o For Microsoft Office 2007, the Microsoft Fix it 50298 patch is available at
http://support.microsoft.com/kb/927009.

o For Microsoft Office 2010, use the Microsoft Let me fix it myself method
available at http://support.microsoft.com/kb/982995.
Note The patches are designed for systems using Internet Explorer 7 and
Internet Explorer 8.
If the patch installer displays a message indicating the fix does not
apply to your operating system or application version, use the Let me
fix it myself method described on the link pages to create the registry
file manually and apply the patch.
Embedded Word is not supported when running the 32-bit version of
Microsoft Word with the 64-bit Teamcenter rich client.

• To display 2D or 3D data, select an item or item revision with attached 2D or 3D

data, or select an object such as a snapshot or associated image or direct model
(JT) data in a component view or in the Details view.
Note When a supported 2D or 3D dataset is modified by an external
application, such as a CAD tool, you can view the changes in the Viewer
view by using either of these methods:
o Right-click the dataset and choose Refresh.

o Select the dataset and choose View→Refresh Window.

For information about the working with 2D and 3D data, see Getting Started
with Product Visualization.
For information about creating and working with snapshots, see the Lifecycle
Visualization Integration Guide.

• To display the object properties for the item or item revision with no associated
displayable datasets, select the item or item revision.
Note When the functionality is enabled, you can see when other users are
available for instant messaging with Microsoft Office Communicator.
You can view the current status of the owning and last modified
users, and you can click the Microsoft Office Communicator symbol in
Teamcenter to initiate communication.

For information about configuring Teamcenter instant messaging with

Microsoft Office Communicator, see the Application Administration
Guide.

2-66 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

• To display tiled thumbnail views of several objects, use Shift+click or Ctrl+click

to select two or more objects.

• To display users assigned to perform a signoff task, select a task to perform in

the My Worklist component view, and then use the Viewer view with Task View
selected.
When the functionality is enabled, you can see when other users are available
for instant messaging with Microsoft Office Communicator. You can view the
current status of other users on the signoff list, and you can click the Microsoft
Office Communicator symbol to initiate communication.
For information about configuring Teamcenter instant messaging with Microsoft
Office Communicator, see the Application Administration Guide.

• To display Web Link object properties in the Viewer view, select a URL link
object in a component view.
Note When you select a URL link object, Teamcenter automatically opens a
Web Browser view to display the Web page associated with the object.

• To display the content of a text file or PDF file in the Viewer view, or to display or
edit standard office files such as Microsoft Word or Excel files in the Viewer view,
click on the dataset object in a component view or a Details view.
Note This functionality depends on your system settings for browsing
documents in the same window.
For example, to enable editing of a Microsoft Word document in the
Viewer view in a Teamcenter client on a Windows XP system, open a My
Computer window and choose Tools→Folder Options. In the Folder
Options dialog box, select the DOC extension for the registered file type,
and then click Advanced to display the Edit File Type dialog box. For the
Open action, select Browse in same window.

Caution Changes may be lost if you select another object in a Teamcenter

component view while editing cell content in an Excel file displayed
in the Viewer view.
To avoid losing your changes when you edit content in an Excel file
displayed in the Viewer view, you must either change the focus to
a different cell or save the file prior to selecting another object in
Teamcenter component view.

The Viewer view is available by default in My Teamcenter.

For information about working with My Teamcenter, see the My Teamcenter Guide.

Working with visualization data in the My Teamcenter viewer

The Viewer view in My Teamcenter displays content dependent on the type of
object selected in the current component view or in the Details view. Support for
visualization data includes:
• If an item or item revision is selected, the viewer displays the associated image,
printed circuit board, schematic, or JT data.

PLM00191 J Rich Client Interface Guide 2-67

Chapter 2 Managing the Teamcenter client interface

• If an image, ECAD PCB, ECAD Schematic, or JT dataset is selected, the viewer

displays the image, printed circuit board, schematic, or model.

Visualization use cases

• View and markup of parts, printed circuit boards, schematics, drawings and
images, without having to launch the stand-alone viewer or the Lifecycle Viewer.

Visualization tools available

• 2D GDT Markup
Create 2D GD&T markups.

• 2D Markup
Create 2D markups.

• 2D Measurement
Perform 2D measurements.

• 2D Multipage
Navigate among pages in multiple-page 2D images or documents.

• 2D Viewing
Pan, zoom, rotate, and flip 2D images.

• 3D Markup
Create 3D markups.

• 3D Measurement
Perform 3D measurements.

• 3D Navigation
Pan, rotate, and zoom 3D models.

• 3D PMI
View and manipulate PMI in your model.

• 3D Section
Create 3D cross sections.

• 3D Selection
Select parts and pick part entities.

• 3D Standard Views
Examine your model from preset viewing angles.

• ECAD Base
Manipulate the view of ECAD document layers, control layer color and visibility,
search, and create reports.

2-68 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

• ECAD Markup
Create ECAD markups.

• ECAD Multipage
Navigate among pages in multiple-page schematic documents.

• ECAD Viewing
Pan, zoom, rotate, and flip image.

• Print
Print documents.

Open visualization data in My Teamcenter

1. In My Teamcenter, select an item, item revision, dataset, or other object
associated with a 2D or 3D file.

2. Select the Viewer view.

The visualization components load and the My Teamcenter embedded viewer
opens.
Tip Right-click the embedded viewer toolbar area to turn on additional
visualization toolbars.

Customizing the Viewer view

The framework for the Viewer view in the rich client uses preferences to configure
the Viewer view to traverse the data model and present a viewer for the selected
business object type. When an object is selected in the rich client, the preference
configuration is read, and the correct target viewer is presented.
Administrators can use four preferences to configure the Viewer view:
• defaultViewerConfig.VIEWERCONFIG
Use this preference to specify the default Viewer view configuration by defining
which Generic Relationship Management (GRM) rules to expand and the viewer
to use for each type of object specified in the preference.

o To use an alternate configuration, define it using the

<viewer-config-ID>.VIEWERCONFIG preference.

o For default values, see the defaultViewerConfig.VIEWERCONFIG

preference description in the Preferences and Environment Variables
Reference.

• <viewer-config-ID>.VIEWERCONFIG
Use this preference to specify an alternate Viewer view configuration instead
of the defaultViewerConfig.VIEWERCONFIG preference. This preference
defines which Generic Relationship Management (GRM) rules to expand, and
the viewer to use for each type of object specified in the preference.

PLM00191 J Rich Client Interface Guide 2-69

Chapter 2 Managing the Teamcenter client interface

o You can create your own preference using the

<viewer-config-id>.VIEWERCONFIG format for the name. The name
must end with .VIEWERCONFIG.

o To use this preference instead of the default viewer configuration

preference, you must specify this preference name in the
Viewer.VIEWERCONFIGTOLOAD preference.
Note There is no default value for the <viewer-config-ID>.VIEWERCONFIG
preference. Enter values for your own configuration.
For an example of values, see the
defaultViewerConfig_VIEWERCONFIG preference.

• Viewer.VIEWERCONFIGTOLOAD
Use this preference to specify the Viewer view configuration to load. This
preference must point to a .VIEWERCONFIG preference name.
By default, this preference points to the
defaultViewerConfig.VIEWERCONFIG preference. To point to an alternate
preference, enter a <viewer_config_id>.VIEWERCONFIG preference name.

For information about how to define a custom viewer, see the Client Customization
Programmer’s Guide.

Using auxiliary views in the rich client

Auxiliary views are rich client views that are not present by default in any
perspective.
• Some auxiliary views, such as the Communication Monitor view, are primarily
for use by an administrator. Such views are described in relevant administration
documentation.

• Some auxiliary views, such as the Progress view or the Search view, can be
useful in one or more application perspectives.
o The Search view, useful in almost every application, is described in the rich
client documentation.

o The Progress view, which lets you monitor the progress of data exchanges
between sites, is described in the Data Exchange Guide.

Use the Show View command

Relevant views are displayed automatically when you select an application. To
display a view in an application, you can use the Window→Show View menu
command.
• Choose the Window→Show View menu command to display a list of common
and recently-used views.

• Choose Window→Show View→Other to display the Show View dialog box.

2-70 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

The Show View dialog box organizes views in categories such as General,
Admin, Application, Diagnostic, Inspector Category, Manufacturing, Projects,
Teamcenter, Utilities, Visualization, and Other.
Note Available views and categories may be different at your site.

When online help is configured for your site, you can display online help in your
default Web browser for most rich client views.
Most versions of Teamcenter introduce new views and rename or make obsolete
other views. Online help is usually available immediately from the Help menu,
but in some cases, you must access help by using the help library table of contents
or the search capability.
• To access help for the current active view in the rich client, press the F1 key
or choose Help®Current Application.

• To open the help library, press Ctrl+F1 or choose Help®Help Library.

Display and move a view in rich client

This procedure uses the example of opening and moving the Image Thumbnail
Preview view in the My Teamcenter perspective.
1. With the My Teamcenter application open, choose Window→Show View→Image
Thumbnail Preview.
The Image Thumbnail Preview view appears in the My Teamcenter perspective.

2. Click the Image Thumbnail Preview tab. Do not release the mouse button.

3. Move the mouse to drag the tab to another area in the perspective or outside the
Teamcenter window entirely.
Note
The stack cursor appears as you drag the view across other view tabs.

4. Release the mouse button to drop the view in the desired location.
As you move the view around the current perspective, the mouse pointer changes
to the appropriate drop cursor to indicate where the view will be docked when
you release the mouse button.
You can resize views in a perspective by dragging the border between the views.
If you select a location where the is no view folder yet, a new view folder is
created.
Note If a view is moved outside the Teamcenter window, you can click and
drag the view tab into the application perspective to return it to the
Teamcenter window.

Drop
cursor Description
The view is placed at the top of the window.

PLM00191 J Rich Client Interface Guide 2-71

Chapter 2 Managing the Teamcenter client interface

Drop
cursor Description
The view is placed at the bottom of the window.

The view is placed on the left side of the window.

The view is placed on the right side of the window.

The view is placed in the stack of views in the current area.

The view is detached and moved outside the Teamcenter window.

The view cannot be placed in the current area.

Note On most systems you can use the Move shortcut menu command to move
a view, or the Detached shortcut menu command to open a view in its own
window.
These menu commands are not available on IBM AIX systems.

Finding information about views

The Teamcenter rich client displays views when you select an application and when
you use the Window®Show View®Other command to display the Show View dialog
box.
• Some views may not respond to requests for online help. In most cases, these
views are described in the Teamcenter HTML Help Collection, and most
descriptions include links to additional information.

• The Rich client views topic lists views by category.

This list may contain views that are not available in your installation because
the corresponding applications are not installed.

If the Teamcenter HTML Help Collection is installed, you can display documentation
for most rich client views by selecting an active view using either of the following
methods:
• Press F1.

• Choose Help®Current Application.

To display information about a view when the Teamcenter HTML Help Collection is
installed, but help is not found for the current rich client view, do the following:
1. Choose Help®Help Library or press Ctrl+F1.

2. Expand Using Teamcenter Interfaces.

3. Select Rich Client Interface Guide.

2-72 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

4. Expand Managing the Teamcenter client interface, expand Views available to

rich client application perspectives, and then select Rich client views.

5. Select the appropriate category or scroll to the listing for the view for which you
want documentation.
• If a link is available for more information, click the link.

• If a link is not available for information, use the online help Search
capability.

Managing views, layouts, and view networks

In the rich client, a view is always displayed in the context of an application
perspective. Each application perspective always displays one or more views.

For example, by default, the My Teamcenter application the Home component view
is displayed in a view folder to the right of the navigation pane, and the Summary,
Details, Impact Analysis, and Viewer views are displayed in a view folder to the
right of the Home component view.
• A layout is the arrangement of the views and view folders in an application
perspective. Each application perspective has a default layout.
o You can rearrange the views in an application perspective, and add or
remove views, to create new layouts.

o You can save new layouts and redisplay them later.

Each layout has a current state and a saved state.

• A view folder is set of one or more views displayed in a specific area in the
Teamcenter window.

PLM00191 J Rich Client Interface Guide 2-73

Chapter 2 Managing the Teamcenter client interface

For example, by default, the My Teamcenter application displays component

views in a view folder immediately to the right of the navigation pane. A second
view folder contains the Summary, Details, Impact Analysis, and Viewer views.
Moving a view to a new area, such as the bottom of the window, creates a new
view folder in that location. You can move views between view folders.

• A view network consists of a primary view and one or more secondary views that
are associated. View networks can be arranged in a single view folder or in
multiple view folders.

• You associate a secondary view with a primary view by choosing Associate from
the view menu and choosing a primary view.

• A primary view, such as a component view, lets you make selections that cause
other views to react.
For example, a Teamcenter component view displays a hierarchical view of
lists of objects and their attachments. When you select an object, such as an
item revision, a secondary view reacts by displaying information relevant to
the selection in the primary view. Secondary views can be associated with
a primary views.

• A secondary view, such as a Details or Summary view, displays information

relevant to the selection in a primary view.
o An associated secondary view reacts to a single, specific primary view in a
view network. You can change a view association by choosing Associate from
the view menu and choosing None or a different primary view.

o A secondary view associated with a specific primary view reacts to

the current selection in that primary view. The associated view closes
automatically when its primary view is closed.

o Depending on the particular views involved, a secondary view can also react
to other secondary views in its network.

o A secondary view not associated with a specific primary view reacts to the
selection in the most recently selected primary view.
Note View tab tooltips indicate:
• The root selection in a primary view.

• The source primary view for a secondary view.

Recognizing primary and secondary views

A primary view has a distinctive border color. This border color is also displayed by
all secondary views that display content based on the primary view.
Note To open an additional view, such as a second or third Summary view to use
in a view network, select an object in a component view and then use the
shortcut menu Open with command.

2-74 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

A currently selected view has a dark background tab and a distinctive color border.
• When a secondary view is not associated with a specific primary view, that
secondary view:
o Displays content based on the currently selected primary view.

o Has a border the same color as the primary view to which it is reacting.

o Has a dashed-line border at the top of the view tab.

• When a secondary view is associated with a specific primary view, that secondary
view:
o Displays content based only on the primary view with which it is associated.

o Has a solid-line border at the top of the view tab.

Object selection in one view can change the selection in another view.
• Selecting an object in a primary view changes the displayed information in
currently related secondary views.

• Selecting an object in a secondary view may change the selection in a related

primary view, if the object selected in the secondary view is currently visible in
the primary view.

• Selecting an object in a primary view may change the selection in other primary
views, if the object selected in the first primary view is also already displayed
in the other primary views.

PLM00191 J Rich Client Interface Guide 2-75

Chapter 2 Managing the Teamcenter client interface

Changing view network color presentation

Choose Window®Preferences®View Network Presentation®Teamcenter to display
the color control options for view networks.

You can specify 12 sets from 156 color and pattern options.

Each set is used in turn as you create new view networks.

Change the view association

Do one of the following:
• In the secondary view, click the Associate button and select the view to
which you want to associate the secondary view from a list of all primary views
currently open.
o If you activate the Disable response to selections button , the Associate
button is not available.

2-76 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

o If the Disable response to selections button is not available (if the secondary
view is responding to selections), when you change selection, the secondary
view changes its content based on that new selection in these cases:
The secondary view is not associated to any view.

The secondary view is associated to the active view (where the selection
change occurred).

The secondary view and the active view (where the selection change
occurred) are both associated to the same primary view.

• Select the line in the primary view to which you want to associate the secondary
view, and click the Set input to recent selection button to set the scope for
a secondary view.
You can use the Set input to recent selection button from any view, regardless of
the association state.

o If you set the scope from the primary view to which the secondary view is
associated, the secondary view is still associated to that primary view.

o If the secondary view is not associated to any primary view when you set
the scope, Teamcenter performs no association.

o If the secondary view is associated to primary view A and you set the scope
from primary view B, the secondary view is associated to primary view B.

Teamcenter associates the secondary view with the selected primary view.

Associate views
• Click Associate and select an object in the list.
This secondary view is associated to the selected object in the primary view.

Disable and enable response to selection

1. Click Disable response to selection .

The secondary view does not change when you select a different object in the
primary view.

2. Click Enable response to selection .

The secondary view changes when you select a different object in the primary
view.

Set input to recent selection

• Click Set input to recent selection .

The secondary view changes to the currently selected object in the primary view
even if you have disabled the response to the selection.

PLM00191 J Rich Client Interface Guide 2-77

Chapter 2 Managing the Teamcenter client interface

Hide and display views and view folders

You can manage visibility of views and view folders.

• Click the view folder menu Show List to display all the views in a view folder.
Currently hidden views are indicated by bold text.

• To control visibility of individual views, use the Fast View command in view
tab shortcut menu.

This puts a Fast View icon representing the view in the bottom border of the
Teamcenter window.

o Click the Fast View icon to redisplay or hide the view temporarily.

o Right-click the icon and deselect the Fast View command to restore the view
to its original view folder and location.

• To control visibility of an entire view folder, use the view folder Minimize,
Restore, and Maximize commands.

2-78 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

The Minimize and Maximize commands are available in the upper-right corner
of the view folder, to the right of the view tab area, and in the view folder tab
bar shortcut menu.
The Restore command is available when a view folder is maximized or
minimized. Right-click the minimized view folder icon, or by clicking the Restore.

o The Minimize command puts icons representing the view folder and its views
in the right border of the Teamcenter window. Click a view icon to display
the view. Click the Restore view folder icon to replace the view folder and its
views in the original location.

o The Maximize command expands the view folder to fill the Teamcenter
window, except for the navigation pane.

o The Restore command returns a minimized or maximized view folder to

its prior size and location.
Note Right-click the primary view for a view network and choose Reveal Related
Views to display views when you have:
• Minimized a view folder containing associated secondary views and do
not see icons for the view folder and views in the right-side border of the
Teamcenter window.

• Multiple views in Fast View mode and want to display only the views
related to a particular view.

Rich client menus

Menu commands are available in an initial installation of the Teamcenter software.
Each application provides some common menu commands, and other menu
commands specific to the application.

For information about most menu commands, see the documentation for the current
application.
Note The menu commands available at your site may differ based on site-specific
configuration.

Window menu
Use the Window menu commands to open a new application window and customize
your desktop.

Command Purpose
Open This command is not used by default. If enabled at your site, this
Perspective command allows you to open alternate collections of view panes.

PLM00191 J Rich Client Interface Guide 2-79

Chapter 2 Managing the Teamcenter client interface

Command Purpose
Show View Allows you to open alternate views.
Depending on the configuration at your site, a variety of views
may be available.
1. Choose Window®Show View®Other to display the Show View
dialog box.

2. Expand one or more categories to display the views available in

those categories.

3. Select a view.

4. Click OK.

The selected view is displayed in the current application

perspective.
For information about rich client views, see Views available to rich
client application perspectives.
Save Saves a rearranged perspective with the current name, or creates a
Perspective new perspective by saving the new arrangement of views with a
As new name.
Reset Restores a rearranged perspective to the default view arrangement.
Perspective
Close This command is not used by default. If enabled at your site, this
Perspective command allows you to close an alternate perspective.
Preferences Use the Window®Preferences menu command to display the
standard Eclipse Preferences dialog box, where you can set
Relation Browser preferences, Teamcenter preferences for search
and view network presentation, and Web browser preferences.
Graphical Relation Browser Layout
Used by the Relation Browser and the Teamcenter Integration
for NX.
For information about using the these options to configure
Relation Browser, see the Relation Browser Guide.
Install/Update
Standard Eclipse functionality.
Network Connections
Standard Eclipse functionality.
Security
Standard Eclipse functionality.
Teamcenter
Show traditional style tabs

2-80 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Command Purpose

Select to display rectangular tabs instead of rounded tabs.

Minimum characters for view title
Specifies the minimum number of characters displayed in view
titles prior to putting titles into the associated view list.
Search
Select to set a wide range of search options.
For information about setting search options, see the Working
with search options.
View Network Presentation
Select to set colors and patterns for view networks.
For information about changing view network color and pattern
presentation options, see the Changing view network color
presentation.
Note Most Teamcenter application options and preferences are
set in the Options dialog box. Choose Edit→Options to
display the Options dialog box.
For more information about options and preferences, see
the Rich Client Interface Guide.
Toolbar Displays or hides the toolbar. A check mark indicates that the
toolbar is displayed under the menu bar.
Navigation Displays or hides the navigation pane. A check mark indicates that
Pane the navigation pane is displayed.
Full Screen Alternates between full-screen display and adjustable-window
display.

Show View menu command

Depending on the configuration at your site, a variety of views may be available.

1. Choose Window®Show View®Other to display the Show View dialog box.

2. Expand one or more categories to display the views available in those categories.

3. Select a view.

4. Click OK.

The selected view is displayed in the current application perspective.

For information about rich client views, see Views available to rich client application
perspectives.

PLM00191 J Rich Client Interface Guide 2-81

Chapter 2 Managing the Teamcenter client interface

Shortcut menus
When you select an object in a rich client view, you can often use the right mouse
button to display a shortcut menu containing commands relevant to the currently
active application or the currently selected object. The shortcut menu is dynamic;
the available commands reflect the current context.
Shortcut menu commands are referenced and described in procedure and reference
documentation in context of the application or object selection to which the
commands apply.
Note On some Linux platforms, you must hold down the right mouse button while
you select the desired command.

Much of the functionality available from menu commands is also available in

shortcut menus, depending on type of object or objects selected when you click the
right mouse button.
For example, the following are some of the commands that are available in the My
Teamcenter shortcut menu, depending on type of object or objects selected.

Command Purpose
Copy Lets you copy a Teamcenter reference to a selected image,
Reference Microsoft Excel, or JT dataset and paste that reference into a
Microsoft Word document.
For more information about adding a dataset reference to a Word
document, see the Systems Engineering Guide.
New Change When an item revision is selected, displays the New Change
in context in context dialog box. You can select the type of change to be
created, such as a problem report or a change request.
For more information about creating change objects, see the
Change Manager Guide.
New Creates a new object of a selected type.
Cut Removes a selected data object reference from the current location
and places it on the clipboard. You must have read privileges on
the object and write privileges on its container to move or remove
an object.
For more information, see Cutting, copying, pasting, and deleting
data objects.
Copy Replicates a data object reference in another application. You
must have read privileges for the selected object that you want to
copy. You can also create a copy by dragging the object to another
Teamcenter application.
For more information, see Cutting, copying, pasting, and deleting
data objects.

2-82 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Command Purpose
Paste Moves a data object reference from the clipboard to the current
location in the data object area. It is important to select the
proper destination for the data object reference before choosing
the Paste menu command. You must have read and write
privileges to the destination object.
For more information, see Cutting, copying, pasting, and deleting
data objects.
Note If your administrator has defined mandatory properties
for the type of relation by which the pasted object
reference (secondary object) is associated to the primary
object, a dialog box lets you define attribute values for
the objects.
Pin to Launch Adds the selected object to the default launch pad.
Pad
For information, see the Using the Launch Pad.
Unpin from Removes the selected object from the default launch pad.
Launch Pad
For information, see the Using the Launch Pad.
Resequence Resequences a structure.
Structure
Generate Creates item reports generated in the context of one or more
Report selected objects. Item reports generate in multiple output formats
and follow PLM XML standards allowing integration with
third-party reporting tools.
For more information about generating reports for an item, see
the My Teamcenter Guide.
Send To Selects an object in a navigation view; use the Send To shortcut
menu command to choose an application to open with the object
selected.
Note For example, you can send a structure to Structure
Manager from My Teamcenter. Teamcenter opens
Structure Manager, loads the structure, and then applies
the default revision rule.
• When an empty Structure Manager window is already
open, Teamcenter loads the structure into it, and then
applies the default revision rule.

• When a Structure Manager window is already open

and contains a configured structure, Teamcenter loads
the structure into it, and then applies the revision rule
used to configure the previously displayed structure.

For more information about your available applications, see the

Rich client application perspectives.

PLM00191 J Rich Client Interface Guide 2-83

Chapter 2 Managing the Teamcenter client interface

Command Purpose
Check In/Out Reserves exclusive access to one or more objects and/or their
attachments by locking the objects in the database upon checkout.
You restore access to the objects using checkin. Only your
administrator is allowed to circumvent the security that these
menu commands provide.
For more information, see the My Teamcenter Guide.
Purge Permanently removes old versions of a dataset from the database.
You can select whether to purge all old versions or specific
versions of a dataset.
If sequence functionality is enabled and the latest sequence is
selected, the system removes all nonimmune sequences of an item
except for the latest sequence. If a sequence other than the latest
sequence is selected, only the selected sequence is purged.
Make Immune Specifies an item revision sequence cannot be deleted from the
system by a purge or checkin action.
The Make Immune command is not available for the latest
sequence. The system displays an error message dialog if you try
to make the latest sequence immune.
Remove Removes immunity from an item sequence. The item can then be
Immunity deleted from the system during a purge or checkin operation.
The Remove Immunity command is not available for the latest
sequence. The system displays an error message dialog if you try
to remove the latest sequence.
Refresh Reads information from the database and updates the information
displayed in the workspace area.
Edit Properties For selected, single editable objects, displays the Check-Out
dialog box, and then displays the Edit Properties dialog box for
the selected object.
For more information, see the My Teamcenter Guide.
View Allows you to view the properties of a selected data object.
Properties For more information, see the My Teamcenter Guide.
Properties on Lets you edit and save properties on custom relations.
Relation
• When one secondary object is selected, this command displays
the Properties dialog box showing the relation between the
selected secondary object and the related primary object.

• When multiple secondary objects are selected, this command

displays the Common modifiable properties dialog box.

For more information about modifying custom properties, see the

My Teamcenter Guide.

2-84 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Command Purpose
Allows you to view, change, and/or apply access permissions for
Access a selected object.
For more information about access permissions, see the Access
Manager Guide.
Project Assigns or removes objects from projects.
For more information about projects, see the Project and Program
Guide.
License Lets users attach or detach licenses:
• Users with IP Admin privileges can use the Attach or Detach
commands to manage licenses for authorized data access
(ADA) for intellectual property (IP) data objects.
For information about associating licenses with data objects
for intellectual property security, see the relevant topics in
the Security Administration Guide.

• Users with ITAR Admin privileges can Attach or Detach

commands to manage licenses for authorized data access
(ADA) for data objects controlled through International
Traffic in Arms Regulation (ITAR) policies.
For information about associating licenses with data objects
for ITAR policies, see the relevant topics in the Security
Administration Guide.
Internal Trace Displays complying or defining objects related to a selected
Report linking or data object.
For more information about trace links, complying objects, and
defining objects, see the My Teamcenter Guide.
Add Design to Opens the Add Design to Product wizard that guides you through
adding your CAD design to an installation assembly attached to
Product an architecture breakdown element.
For information about adding designs to products, see the
Platform Designer Guide.
Add Part to Opens the Add Part to Product wizard that guides you through
adding an enterprise resource planning (ERP) part to an
Product
architecture breakdown element.
For information about adding parts to products, see the Platform
Designer Guide.
Manage Global Lets you work with global alternates. A global alternate part is
Alternates interchangeable with another part, regardless of where the part
is being used in the product structure.
For more information about global alternates, see the Structure
Manager Guide.

PLM00191 J Rich Client Interface Guide 2-85

Chapter 2 Managing the Teamcenter client interface

Command Purpose
Multisite For data shared with participating sites in a distributed network,
Synchronization lets you update objects, components, and assemblies.
For more information about sharing data in a distributed
network, see the Multi-Site Collaboration Guide.
Subscribe Allows you to create subscriptions.
You can also access this menu command from a shortcut menu
by right-clicking a data object.
For more information about subscriptions, see the My Teamcenter
Guide.
Subscription Allows you to manage (query, edit, and delete) persistent
Manager subscriptions.
For more information about subscriptions, see the My Teamcenter
Guide.
Add To Lets you add selected objects to your Favorites list in the
Favorites navigation pane.
For more information, see Add favorites to organize your data.
Compare For comparing two requirements or comparing a requirement
Contents or specification to a previous versions, lets you start and end
comparisons, or compare to a previous object.
For more information about comparing requirement content, see
the Systems Engineering Guide.

Note Some menu commands must be enabled by your Teamcenter administrator.

Shortcut menus in My Teamcenter

Much of the functionality available from menu commands is also available in
shortcut menus, depending on type of object or objects selected when you click the
right mouse button.
For example, the following are some of the commands that are available in the My
Teamcenter shortcut menu, depending on type of object or objects selected.

Command Purpose
Copy Lets you copy a Teamcenter reference to a selected image,
Reference Microsoft Excel, or JT dataset and paste that reference into a
Microsoft Word document.
For more information about adding a dataset reference to a Word
document, see the Systems Engineering Guide.
New Change When an item revision is selected, displays the New Change
in context in context dialog box. You can select the type of change to be
created, such as a problem report or a change request.
For more information about creating change objects, see the
Change Manager Guide.

2-86 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Command Purpose
New Creates a new object of a selected type.
Cut Removes a selected data object reference from the current location
and places it on the clipboard. You must have read privileges on
the object and write privileges on its container to move or remove
an object.
For more information, see Cutting, copying, pasting, and deleting
data objects.
Copy Replicates a data object reference in another application. You
must have read privileges for the selected object that you want to
copy. You can also create a copy by dragging the object to another
Teamcenter application.
For more information, see Cutting, copying, pasting, and deleting
data objects.
Paste Moves a data object reference from the clipboard to the current
location in the data object area. It is important to select the
proper destination for the data object reference before choosing
the Paste menu command. You must have read and write
privileges to the destination object.
For more information, see Cutting, copying, pasting, and deleting
data objects.
Note If your administrator has defined mandatory properties
for the type of relation by which the pasted object
reference (secondary object) is associated to the primary
object, a dialog box lets you define attribute values for
the objects.
Pin to Launch Adds the selected object to the default launch pad.
Pad
For information, see the Using the Launch Pad.
Unpin from Removes the selected object from the default launch pad.
Launch Pad
For information, see the Using the Launch Pad.
Resequence Resequences a structure.
Structure
Generate Creates item reports generated in the context of one or more
Report selected objects. Item reports generate in multiple output formats
and follow PLM XML standards allowing integration with
third-party reporting tools.
For more information about generating reports for an item, see
the My Teamcenter Guide.

PLM00191 J Rich Client Interface Guide 2-87

Chapter 2 Managing the Teamcenter client interface

Command Purpose
Send To Selects an object in a navigation view; use the Send To shortcut
menu command to choose an application to open with the object
selected.
Note For example, you can send a structure to Structure
Manager from My Teamcenter. Teamcenter opens
Structure Manager, loads the structure, and then applies
the default revision rule.
• When an empty Structure Manager window is already
open, Teamcenter loads the structure into it, and then
applies the default revision rule.

• When a Structure Manager window is already open

and contains a configured structure, Teamcenter loads
the structure into it, and then applies the revision rule
used to configure the previously displayed structure.

For more information about your available applications, see the

Rich client application perspectives.
Check In/Out Reserves exclusive access to one or more objects and/or their
attachments by locking the objects in the database upon checkout.
You restore access to the objects using checkin. Only your
administrator is allowed to circumvent the security that these
menu commands provide.
For more information, see the My Teamcenter Guide.
Purge Permanently removes old versions of a dataset from the database.
You can select whether to purge all old versions or specific
versions of a dataset.
If sequence functionality is enabled and the latest sequence is
selected, the system removes all nonimmune sequences of an item
except for the latest sequence. If a sequence other than the latest
sequence is selected, only the selected sequence is purged.
Make Immune Specifies an item revision sequence cannot be deleted from the
system by a purge or checkin action.
The Make Immune command is not available for the latest
sequence. The system displays an error message dialog if you try
to make the latest sequence immune.
Remove Removes immunity from an item sequence. The item can then be
Immunity deleted from the system during a purge or checkin operation.
The Remove Immunity command is not available for the latest
sequence. The system displays an error message dialog if you try
to remove the latest sequence.
Refresh Reads information from the database and updates the information
displayed in the workspace area.

2-88 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Command Purpose
Edit Properties For selected, single editable objects, displays the Check-Out
dialog box, and then displays the Edit Properties dialog box for
the selected object.
For more information, see the My Teamcenter Guide.
View Allows you to view the properties of a selected data object.
Properties For more information, see the My Teamcenter Guide.
Properties on Lets you edit and save properties on custom relations.
Relation
• When one secondary object is selected, this command displays
the Properties dialog box showing the relation between the
selected secondary object and the related primary object.

• When multiple secondary objects are selected, this command

displays the Common modifiable properties dialog box.

For more information about modifying custom properties, see the

My Teamcenter Guide.
Allows you to view, change, and/or apply access permissions for
Access a selected object.
For more information about access permissions, see the Access
Manager Guide.
Project Assigns or removes objects from projects.
For more information about projects, see the Project and Program
Guide.
License Lets users attach or detach licenses:
• Users with IP Admin privileges can use the Attach or Detach
commands to manage licenses for authorized data access
(ADA) for intellectual property (IP) data objects.
For information about associating licenses with data objects
for intellectual property security, see the relevant topics in
the Security Administration Guide.

• Users with ITAR Admin privileges can Attach or Detach

commands to manage licenses for authorized data access
(ADA) for data objects controlled through International
Traffic in Arms Regulation (ITAR) policies.
For information about associating licenses with data objects
for ITAR policies, see the relevant topics in the Security
Administration Guide.
Internal Trace Displays complying or defining objects related to a selected
Report linking or data object.
For more information about trace links, complying objects, and
defining objects, see the My Teamcenter Guide.

PLM00191 J Rich Client Interface Guide 2-89

Chapter 2 Managing the Teamcenter client interface

Command Purpose
Add Design to Opens the Add Design to Product wizard that guides you through
adding your CAD design to an installation assembly attached to
Product an architecture breakdown element.
For information about adding designs to products, see the
Platform Designer Guide.
Add Part to Opens the Add Part to Product wizard that guides you through
adding an enterprise resource planning (ERP) part to an
Product
architecture breakdown element.
For information about adding parts to products, see the Platform
Designer Guide.
Manage Global Lets you work with global alternates. A global alternate part is
Alternates interchangeable with another part, regardless of where the part
is being used in the product structure.
For more information about global alternates, see the Structure
Manager Guide.
Multisite For data shared with participating sites in a distributed network,
Synchronization lets you update objects, components, and assemblies.
For more information about sharing data in a distributed
network, see the Multi-Site Collaboration Guide.
Subscribe Allows you to create subscriptions.
You can also access this menu command from a shortcut menu
by right-clicking a data object.
For more information about subscriptions, see the My Teamcenter
Guide.
Subscription Allows you to manage (query, edit, and delete) persistent
Manager subscriptions.
For more information about subscriptions, see the My Teamcenter
Guide.
Add To Lets you add selected objects to your Favorites list in the
Favorites navigation pane.
For more information, see Add favorites to organize your data.
Compare For comparing two requirements or comparing a requirement
Contents or specification to a previous versions, lets you start and end
comparisons, or compare to a previous object.
For more information about comparing requirement content, see
the Systems Engineering Guide.

Note Some menu commands must be enabled by your Teamcenter administrator.

2-90 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Working with the rich client navigation pane

The rich client navigation pane provides quick access to the data you use most. You
can use the rich client navigation pane to find and organize your data and to help
you perform common tasks, such as creating a part, creating a dataset, or applying
a status to a part.

PLM00191 J Rich Client Interface Guide 2-91

Chapter 2 Managing the Teamcenter client interface

1 Upper part of the • The reorder button above the Search

navigation pane box lets you display the Navigation Section
Ordering dialog box to hide sections or change
the order of sections in navigation pane.

• Quick-open Search provides predefined

searches using dataset, item ID, item name,
keyword search, and advanced search features.

• Quick Links provide access to your Home

folder, worklist, saved searches, and web links.
For information about working with Quick
Links, see the Configuring the Quick Links
section.

• Open Items displays links to items that are

open in an active perspective.

• History displays links to Teamcenter objects

that you opened in the past. Links are
displayed with the most recently closed object
displayed at the top of the History list.

• Favorites displays links to Teamcenter objects

that you have designated as favorites.
For more information, see Add favorites to
organize your data.

• I Want To provides links to the tools used to

2 Primary application
buttons
3 Secondary application
buttons
4 Configure Applications
button
complete tasks that you perform repeatedly,
such as initiating a process or change.
For more information about working with I
Want To tasks, see the Customize your I Want
To links in the rich client.
Provide access to your most frequently used
Teamcenter applications.
Provide access to the Teamcenter applications that
you use infrequently.
Provides access to the tools you can use to
configure the display of primary and secondary
applications.
For information about specifying primary and
secondary applications, see Configuring the
display of applications.

2-92 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Note You can also show or hide the navigation pane.

To show or hide the navigation pane:

• Choose Window ® Navigation Pane.

For information about displaying the navigation pane, see Show or hide the
navigation pane in the rich client.

Rich client navigation pane section order

You can reorder sections in the left-hand navigation pane using the Navigation
Section Ordering dialog box or by dragging a section to a new location above or
below the current location.
To use the Navigation Section Ordering dialog box to order and set visibility for
sections:
1. Click the reorder button to display the Navigation Section Ordering dialog
box.
Use the left and right arrows to move one or more selection to or from the
Hidden Sections box.

2. Select one or more section titles and then use the up and down arrows or
click-and-drag to move the selection up or down the list.

To drag a section to a new location in the navigation pane:

1. Click in the section title bar to the right of the section title.

2. Drag the section up or down to a new location in the navigation pane.

Note Selections are applied in the current session. Those selections, as well as the
expanded or collapsed state for sections, persist in subsequent sessions.
This feature is supported by the LHN_Nav_Items_List preference, which
tracks and maintains the navigation pane section order and the expansion
state of each section, based on section IDs and a Boolean value that indicates
the expansion state.

Configuring the Quick Links section

You can configure your Quick Links section by:
• Adding or removing containers (folders).

• Renaming containers.

• Organizing the display order of quick links containers.

Note You cannot delete or rename the Home, My Worklist, My Projects, My Links,
My Saved Searches or My View/Markup containers.

PLM00191 J Rich Client Interface Guide 2-93

Chapter 2 Managing the Teamcenter client interface

Add a folder to your rich client quick links

1. In My Teamcenter, select a folder from the tree and click the Customize link in
the Quick Links section of the navigation pane.

2. In the Customize Quick Links dialog box, click the Paste button .

3. Click OK.
The folder is added to the Quick Links section of the navigation pane.
Note If there is not enough space to display all your Quick Links in the
navigation pane, click View All to display the full list.

Remove a folder from your rich client quick links

1. Click the Customize link in the Quick Links section of the navigation pane.

2. In the Customize Quick Links dialog box, select the folder that you want to
remove from the list.

3. Click Delete .

4. Click OK.

Rename a rich client quick links folder

1. Click the Customize link in the Quick Links section of the navigation pane.

2. In the Customize Quick Links dialog box, select the folder that you want to
rename and click the Edit button .

3. In the Rename quick links dialog box, type the new name for the folder and
click OK.

Organize your rich client quick links

1. Click the Customize link in the Quick Links section of the navigation pane.

2. In the Customize Quick Links dialog box, select a folder from the list and click
the Move Up button or the Move Down button to change the position of
the folder in the list.

Manage rich client saved searches

To manage saved searches in the My Saved Searches container, you can:
• Add searches.

• Remove searches.

• Rename searches.

• Organize searches.

2-94 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

You can also choose to display search results in a list or in a tree format to show
relationships between objects.
Note For information about performing searches in the rich client, see the Using
search types.

Add a saved search to your saved searches list (rich client)

Note This example procedure assumes you have run a search from the Search
view in any perspective and have results displayed in the Search Results
view.

1. In the Search view, click the Add Search to My Saved Searches button .

2. In the Add Search to My Saved Searches dialog box, provide a name for the
saved search.
Tip Click the Create In dialog box to expand the dialog. You can specify a
folder or create a new folder in which to put the saved search.

3. Click OK.
A link to the search is added to your My Saved Searches list.

Remove a saved search from the list in the rich client

1. Click the My Saved Searches link in the Quick Links section of the navigation
pane.

2. In the Customize My Saved Searches dialog box, select the search that you
want to remove.

3. Click Delete .

Rename a saved search in the rich client

1. Click the My Saved Searches link in the Quick Links section of the navigation
pane.

2. In the Customize My Saved Searches dialog box, select the search that you
want to rename and click the Edit button .

3. In the Rename saved search dialog box, type the new name for the search,
and click OK.

Organize your saved searches list in the rich client

1. Click the My Saved Searches link in the Quick Links section of the navigation
pane.

2. In the Customize My Saved Searches dialog box, select a search name from the
list and click the Move Up button or the Move Down button to change
the position of the search in the list.

PLM00191 J Rich Client Interface Guide 2-95

Chapter 2 Managing the Teamcenter client interface

Manage your links in the rich client

The My Links section of the navigation pane provides quick access to the Web
sites that you visit most. When you click a link in the list, the Web page opens
in a separate browser window.
You can add links to the list, remove links from the list, and change the order in
which links appear in the list.

Add a link to your list of links in the rich client

1. Click the My Links link in the Quick Links section of the navigation pane.

2. In the Customize My Links dialog box, click the Create a new Web link button .

3. In the New URL dialog box, enter the following information:

a. In the Name box, type the name that will be displayed for the link in your
My Links list.

b. Type the URL for the link in the URL box.

c. Click OK.

4. Click OK to close the Customize My Links dialog box.

The link is added to your My Links list.

Remove a link from the rich client My Links list

1. Click the My Links link in the Quick Links section of the navigation pane.

2. In the Customize My Links dialog box, select the link that you want to remove
from the list.

3. Click the Remove button .

4. Click OK.

Rename a link in the rich client

1. Click the My Links link in the Quick Links section of the navigation pane.

2. In the Customize My Links dialog box, select the link that you want to rename
and click the Rename button .

3. In the Rename link dialog box, type the new name for the link, and click OK.
The new name of the link is displayed in your My Links list.

Organize your rich client My Links list

1. Click the My Links link in the Quick Linkssection of the navigation pane.

2-96 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

2. In the Customize My Links dialog box, select a link name from the list and click
the Move Up button or the Move Down button to change the position
of the link in the list.

Customize your I Want To links in the rich client

The I Want To links, which are both user-specific and application-specific, can provide
quick access to the tools you use to perform common tasks.
• When you create an I Want To action, you do so in the context of the currently
active application.

• To create the same action in a different application, you must repeat the process.

The Create an Item, Create a Dataset, and Create a Workflow Process links are
provided in your Teamcenter installation.

You can add links to other tasks, remove links to tasks, and organize the display
order of tasks.

Add a task to the rich client I Want To list

1. Click the Customize link in the I Want To section of the navigation pane.

2. In the Customize I Want To dialog box, select an action from the Available
Entries tree.

3. Click the Add button to add the action to the Selected Entries list.

4. Click OK.
The task is added to your I Want To list.

Remove a task from the rich client I Want To list

1. Click the Customize link in the I Want To section of the navigation pane.

2. In the Customize I Want To dialog box, select the task from the Selected Entries
tree.

3. Click the Remove button .

4. Click OK.
The task is removed from your I Want To list.

PLM00191 J Rich Client Interface Guide 2-97

Chapter 2 Managing the Teamcenter client interface

Organize your rich client I Want To list

1. Click the Customize link in the I Want To section of the navigation pane.

2. In the Customize I Want To dialog box, select a task from the list and click
the Move Up button or the Move Down button to change the position
of the task in the list.

3. Click OK.

Show or hide the navigation pane in the rich client

Choose Window→Navigation Pane to display or hide the navigation pane. A check

mark on the left of the Navigation Pane menu command indicates the navigation
pane is displayed.

Configuring the display of applications

You can configure the display of applications in the navigation pane by choosing a
command from the Configure Applications menu at the bottom of the navigation
pane. Menu commands include the following:
• Show More Applications
Shows more applications in the listings for primary applications and secondary
applications.

• Show Fewer Applications

Shows fewer applications to the listings for primary applications and secondary
applications.

• Navigation Pane Options

Specifies and organizes applications for listing as primary applications and
secondary applications.

• Add or Remove buttons in the Navigation Pane Options dialog box.

Moves applications between the primary applications and the secondary
applications list.

Note You can drag the sash up or down in the navigation pane to adjust the
number of application buttons that appear in the primary and secondary
application lists. If the secondary application area cannot contain all the
applications, the applications that do not fit are displayed at the bottom of
the Configure Applications menu .

For information about configuring the navigation pane, see Working with the rich
client navigation pane.

2-98 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Select available applications for display

1. Click Configure Applications at the bottom of the navigation pane and

choose Add or Remove Buttons.
The system displays the list of applications not already specified as primary or
secondary applications.

2. Select an application.
Applications added this way become secondary applications available at the
bottom of the navigation pane or, if space is not available there, at the bottom of
the Configure Applications menu.

Display primary and secondary applications

For each application you want to display in the navigation pane as primary or
secondary applications, follow these steps:

1. Click at the bottom of the navigation pane and choose Navigation Pane
Options.

2. In the Navigation Pane Options dialog box, select applications from the
Available Applications list and move them to the Primary Applications list or
Secondary Applications list using the button.

Tip You can change the display order of the applications using the up arrow
and down arrow buttons located next to the Primary Applications or
Secondary Applications lists.

PLM00191 J Rich Client Interface Guide 2-99

Chapter 2 Managing the Teamcenter client interface

3. Click OK.

Show more applications

• Click at the bottom of the navigation pane and choose Show More
Applications .

The system displays the button corresponding to the first application in your
Secondary Applications list as a primary application and moves it to the Primary
Applications list in the Navigation Pane Options dialog box.

Show fewer applications

• Click at the bottom of the navigation pane and choose Show Fewer
Applications .

The system displays the button corresponding to the last application in your
Primary Applications list as a secondary application and moves it to the Secondary
Applications list in the Navigation Pane Options dialog box.

Add favorites to organize your data

You can use favorites to track objects you access frequently, such as parts, forms,
or processes.
In the rich client, use either of the following methods to add the objects to your
Favorites list in the navigation pane:

• Right-click the object and choose Add to Favorites .

• Select the object in any hierarchy or detail view and drag it to a folder in the
Favorites list in the navigation pane.

To display the object, click the link in the Favorites list. The file is opened in the
application associated with the object or data type. For example, clicking a link to a
Word document opens the file in Microsoft Word. Clicking a link to an item revision
opens the item revision in My Teamcenter.
Note You can organize your favorites into folders using the Organize Favorites
dialog box. Click the Organize button in the Favorites section to access
the Organize Favorites dialog box.

Add a link to your Favorites list

1. Right-click the object you want to add to your Favorites list.

2. Choose Add to Favorites .

3. In the Add Favorites dialog box, select a folder for the new favorites link and
click OK.

2-100 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Add a subfolder to your Favorites list

1. Click the Organize link in Favorites section.

2. In the Organize Favorites dialog box, click the Create New Folder button .

3. Type a name for the new folder and click OK.

4. Click Close.

Rename a folder in the Favorites list

1. Click the Organize link in Favorites section.

2. In the Organize Favorites dialog box, select the folder to rename.

3. Click the Rename button .

The Rename favorites folder dialog box appears.

4. Type the new folder name in the New name box.

5. Click OK.

6. Click Close.

Remove a link or folder from the Favorites list

1. Click the Organize link in Favorites section.

2. In the Organize Favorites dialog box, select the link or folder from the list.

3. Click the Delete button .

4. Click Close.

Customizing the toolbar

You can add commands or remove commands from Teamcenter rich client
perspectives.

• The Customize Toolbar shortcut menu command displays the Customize

Toolbar dialog box.

• The Customize Toolbar dialog box lets you add commands to the toolbar or
remove commands from the toolbar for each Teamcenter rich client perspective
you use frequently.

PLM00191 J Rich Client Interface Guide 2-101

Chapter 2 Managing the Teamcenter client interface

• The Restore Defaults shortcut menu command returns a perspective toolbar

to its default state.

• Remove buttons from the toolbar.

• Add buttons to the toolbar.

• Change the order of buttons in the toolbar.

• Show and hide the toolbar.

Note Some Teamcenter options do not have symbols associated with them. When
you add these options to the toolbar, the generic button is displayed and the
command name is shown as a tool tip when you move the mouse cursor
over the button.

Button groups
Buttons in the toolbar are grouped by default. The groups displayed by the Getting
Started application cannot be edited.
For other groupings, you can move buttons to different positions.

Remove buttons from the toolbar

1. Right-click in the toolbar and choose Customize Toolbar.
The Customize Toolbar dialog box appears.

2. In the Toolbar details list, select the button you want to remove.

3. Click the Remove button.

4. Click OK.
The button is removed from the toolbar.

Add buttons to the toolbar

1. Right-click in the toolbar and choose Customize Toolbar.
The Customize Toolbar dialog box appears.

2. In the Toolbar details list, select the group to which you want to add a button.

3. In the Menubar details list, select the button you want to add.

4. Click the Add button .

The option appears in the Toolbar details list.

5. (Optional) Select the option and click the Move Up button or the Move Down
button to change the position of the button in the toolbar.

2-102 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

6. (Optional) Insert a separator after a button by selecting the option in the list
and clicking the Sep button.

7. Click OK.
The button is added to the toolbar.

Change the order of buttons in the toolbar

1. Right-click in the toolbar and choose Customize Toolbar.
The Customize Toolbar dialog box appears.

2. Select an option in the Toolbar details list.

3. Click the Move Up button or the Move Down button to change the
position of the button in the toolbar.

4. Click OK.

Show and hide the toolbar

• Choose Window®Toolbar.
The toolbar is displayed when the Toolbar command has a check mark .

Changing user settings

Double-click the application banner user and role or choose Edit®User Setting
to display the User Settings dialog box to modify the following categories of user
information:
• Session – Update settings for your current logon session.

• Login – Update default logon settings and change your password.

• Person – Change user profile data including name, address, and phone number.
Note You must have administrative privileges to change your user profile.

• Administrative – Set administration and security logging.

Note This option is visible only if you are logged on as an administrator.

Tip You can also click the user information link in the application header to
access the User Settings dialog box.

PLM00191 J Rich Client Interface Guide 2-103

Chapter 2 Managing the Teamcenter client interface

Application bar display

The appbar_title_contents preference specifies values to be displayed in the title
string of the application bar for the thin client and the rich client.
Valid values include:

user
Specifies the full Teamcenter user name.
userid
Specifies the Teamcenter logon user name.
group
Specifies the group the logged-on user is assigned to.
role
Specifies the role of the logged-on user.
site
Specifies the site identifier.
curr_proj
Specifies the current project selected.
prev_login_time
Specifies the previous logon time.
prev_session_ip
Specifies the previous session address.
current_login_time
Specifies the logon time for the current session.
locationcode
Specifies the location code identifier.
change_notice
Specifies the current change notice in the rich client.
Note This value is not supported by the thin client.

version
Specifies the version of selection.

Note The rich client application bar can also display a value for Organization,
but only when the TcSetOwningOrganization constant is set to true in
the Business Modeler IDE, and Organization is configured for the group
to which a logged-on user belongs.

For more information about the appbar_title_contents preference, see the

Preferences and Environment Variables Reference.

2-104 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Change your user profile

Note You must have administrative privileges to change your user profile.

1. Choose Edit→User Setting.

2. Click the Person tab.

3. Change your information (address, city, state, ZIP code, country, organization,
employee number, internal mail code, e-mail address, and telephone number).

4. Click OK.

Change your password

1. Choose Edit→User Setting.

2. Click the Login tab.

3. Click the Change Password button.

Note When the Teamcenter rich client is configured to use Security Services,
passwords are managed by an external identity service provider (for
example, lightweight directory access protocol) rather than Teamcenter.
In this circumstance, you cannot change a password through Teamcenter.

4. Type the old password, the new password, and confirm the new password.

5. Click OK.

Change your default group and volume settings

1. Choose Edit→User Setting.

2. Click the Login tab.

3. (Optional) Change the default group.

Note The Group option displays only the groups in which you are an active
member. If your membership in a group has been deactivated, you
cannot switch to that group.

4. Change the default volume or default local volume.

Note The values of the Default Volume box and, if present, the Default Local
Volume box must not be the same.
For more information about default volumes, see the System
Administration Guide.

5. Click OK.

PLM00191 J Rich Client Interface Guide 2-105

Chapter 2 Managing the Teamcenter client interface

Set your default role within a group

1. Choose Edit→User Setting.

2. Click the Login tab.

3. Select a group from the Default Role table and choose a role from the list.
Tip You can repeat this step to specify a default role for each group of which
you are a member.

4. Click Apply.
Teamcenter saves the default role settings and applies them when you log on
to a new session.

Change administrative settings

1. Choose Edit→User Setting.

2. Click the Administrative tab.

3. Select or clear the Application Logging, Journaling, Administration Logging,

Security Logging, and/or Bypass options that you want to apply.

4. Click OK.

Change your group, role, volume, and logging session settings

Session settings allow you to assume a different group and/or role during your
current Teamcenter logon session. You can also select a different volume for storing
your data and enable application logging and journaling.
1. Choose Edit→User Setting.
The system displays the User Settings dialog box.

2. Click the Session tab.

The system displays the session settings.

3. (Optional) Select a new group, role, or volume, or, if present, local volume.
Note The Group option displays only the groups in which you are an active
member. If your membership in a group has been deactivated, you
cannot switch to that group.
A Local Volume field is available if the TC_Store_and_Forward
preference is set to true. Default local volumes are temporary local
volumes that allow files to be stored locally before they are automatically
transferred to the final destination volume. This functionality is also
known as store and forward.
For information about using local volumes and local default volumes, see
the System Administration Guide.

4. (Optional) Enable application logging and/or journaling.

2-106 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

5. Click OK.
The system applies the new session settings.

Set your work context

A work context is a particular profile you assume to complete a specific assignment.
It is a combination of your user name, group, and role for a selected project.
Your application administrator may have defined work contexts for workflow tasks.
If so, you should choose the appropriate work context for each workflow task you
are assigned.
1. Choose Edit→User Setting.

2. Click the Session Settings link.

The system displays the work contexts associated with the workflow tasks
(including target objects) that are assigned to you.
Note Your administrator can choose to display all work contexts (rather than
only those related to your assigned workflow tasks) in this list by setting
the TC_wc_show_all preference.
For more information, see the Preferences and Environment Variables
Reference.

3. Click OK.

Set your current project

Your Teamcenter administrator may have assigned a default project in which you
will work. You can override this default setting by choosing another project in the
User Settings dialog box.
1. Choose Edit→User Setting.
The system displays the User Settings dialog box.

2. Click the Session link.

The system displays the session settings.

3. Select a project from the Project list.

4. Click OK.
The system applies the new session settings.

Using the information center

When you select an object, such as an item, in a Teamcenter rich client application,
information about the selected object is shown in the information center. The
information center is located at the bottom of the Teamcenter window, to the left of
the clipboard.

PLM00191 J Rich Client Interface Guide 2-107

Chapter 2 Managing the Teamcenter client interface

Information center symbols convey where-used and where-referenced, access

privilege, child count, and status information about the selected object. To display the
information, point to the symbol. The information displays in the form of a tool tip.

Note
The indicator in the upper-right corner of any of the symbols in the
information center indicates that the status represented by the symbol does
not apply to the selected object. For example, the indicator in the corner
of the In Process symbol indicates that the object is not in process.

Symbol Description
Object access: Write access is permitted on the selected object.
Object access: Delete access is permitted on the selected object.
Object access: Change access is permitted on the selected object.
Object state: The object is the target of an active workflow process.
Object state: The object is checked out of the database.
Object state: The object is released.
Object state: The object is published.
For more information about publishing objects, see the Multi-Site
Collaboration Guide.
Object state: The object is classified.
For more information about classifying objects, see the Classification
Guide.
Where used: Where-used count for the currently selected object.
Where referenced: Where-referenced count for the currently selected
object.
Children: Number of children of the selected component.

Set information center display options

1. Right-click in the information center.
The Update Options dialog box appears.

2. Select or clear the check boxes to configure the display of information.

3. Click OK.

2-108 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Using the Launch Pad

The Launch Pad is an application perspective that provides a visual desktop to
place items and notes, called nodes, for quick reference in either a carousel or grid
display mode.
Nodes can be images, URLs, lists and other Teamcenter data that has some
relationship to the current context, with emphasis on Teamcenter data that allows
easy access to and visualization of relevant data. The active node is the node most
recently brought to the front of in carousel mode or most recently selected in grid
mode.
Note By default, the Launch Pad is hidden and not available to the user unless
an administrator removes if from the HiddenPerspectives preference
value list.
The Launch Pad is not available on IBM AIX platforms.

• In the carousel mode, nodes are arranged in a circle with simulated depth. You
can click and drag nodes to rotate nodes left or right to bring a new node forward
to become the active node.

• In grid mode, nodes are arranged in rows and columns.

PLM00191 J Rich Client Interface Guide 2-109

Chapter 2 Managing the Teamcenter client interface

The Launch Pad application provides a Getting Started context and a new component
context.
• The Getting Started context consists of predefined nodes and any object nodes
added to the Launch Pad. This is the context displayed if you select the
Launch Pad application in the navigation pane or by choosing Window®Open
Perspective®Other®Launch Pad.
To add an object to the Getting Started context, select an item and choose the Pin
to Launch Pad shortcut menu command.
To remove an object from the Launch Pad, select the item and choose the Unpin
from Launch Pad shortcut menu command.

• To create a new component context for an object, select a Teamcenter component

and choose the Send To®Launch Pad shortcut menu command. You can also
create a Launch Pad component context by double-clicking a node in the Getting
Started context.
The component context persists until you send a different object to the Launch
Pad, or you clear the context by returning to the default context.
Note To reduce crowding, you can hide nodes, which moves them to the task bar
at the bottom of the Launch Pad. Move the cursor over node buttons on the
task bar to display information about each nodes, and click a node button to
restore the node to the Launch Pad window.

For information about customizing Launch Pad, see the Client Customization
Programmer’s Guide.

Cutting, copying, pasting, and deleting data objects

You can use cutting, copying, and pasting to move data in your workspace by:

2-110 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

• Cutting an information object from one application and pasting it into another
Teamcenter application.

• Copying data to the clipboard and pasting it into another Teamcenter application.

• Copying data to the clipboard and pasting it into an application outside the
Teamcenter environment.

If you have delete permission for an object, you can also delete data from the
Teamcenter database, but you cannot delete an object from the database if that
object is referenced in multiple locations.
To delete an object from the database, you may need to:
• Perform a where-referenced search to locate all references to the object.

• Contact all the owners of the references and ask them to delete their references
to the object.

• When there are no remaining references, you can delete an object for which
you have delete permission.
Note An object contained in multiple folders can be deleted by a single action if
the object is not referenced by other nonfolder objects.

Cut data objects and paste them into another Teamcenter application
1. Select one or more objects from a tree or table.

2. Choose Edit→Cut or click the Cut button .

The object reference is removed from its current location and placed on the
clipboard.

3. Open the application where you want to paste the object.

4. Click the Clipboard button in the lower-right corner of the window.

5. Select the object from those listed in the Clipboard Contents dialog box.
The system copies the object into the open application.
Note The Cut menu command removes a reference to an information object, but it
does not delete the actual object from the database. To delete an object from
the database, use the Delete option.
You cannot delete from the database an object that is referenced in multiple
locations. Therefore, to delete an object from the database, you may need
to perform a where-referenced search to locate all references to the object,
then contact all the owners of the references and ask them to delete their
references to the object. When there are no remaining references, you can
delete an object for which you have delete permission.

PLM00191 J Rich Client Interface Guide 2-111

Chapter 2 Managing the Teamcenter client interface

Copy data objects

• Select the objects that you want to copy and click the Copy button , press
Ctrl+C, select Copy from the shortcut menu, or choose Edit®Copy.
A reference to the object is copied from its current location and placed on both
the Teamcenter and system clipboards.
Note For Teamcenter Integration for NX, after you copy data to the clipboard,
you can use the Send the clipboard contents to NX clipboard shortcut
menu command to transfer data from the Teamcenter clipboard to the NX
clipboard. Teamcenter Integration for NX must be running for this command
to work. The Send the clipboard contents to NX command does not open
the items in NX from the Teamcenter clipboard, but the Paste command
becomes available in Assembly Navigator in NX.

Pasting data objects

The Edit menu paste commands move object references from the clipboard to the
selected container object.
When the system pastes an object reference into an item or item revision container,
a relationship is established. This relationship is referred to as the default relation
type.
Because data objects are complex entities, the paste options are more complex than
similar options in other software applications.

Menu command Description

Paste It is important to select the proper destination for the data
object reference before choosing the Paste menu command.
You must have read and write privileges to the destination
object.
Paste Special Allows you to specify a relation type rather than using the
default paste relation when pasting an object reference into
an item or item revision.

Paste the contents of the clipboard

1. Cut or copy the data object to the clipboard.

2. Select the destination container for the copied object reference.

3. Right-click the container and choose Paste, or click the Paste button on the
toolbar, or choose Edit→Paste, or press Ctrl+V.
The system pastes all object references contained on the clipboard into the
selected container object.

Paste an item or item revision and specify the relation type

1. Cut or copy the item or item revision to the clipboard.

2-112 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

2. Select a container object.

3. Choose Edit→Paste Special.

4. In the Paste dialog box, select a relation type from the list and click OK.
Note If your Teamcenter administrator has configured mandatory properties
(attributes) for the relation type you select, the Properties dialog box
appears. If the Properties dialog box appears, enter values for the
mandatory properties and click OK.

Pasting object references to applications outside the Teamcenter

environment
References to objects that have been copied to the system clipboard can be pasted
outside of the Teamcenter environment as URLs.
Outside of the Teamcenter environment, you can access the data object by clicking
the URL. This launches Teamcenter and displays the data in My Teamcenter.
Note To access objects from a URL, the Teamcenter rich client must be installed
on your machine and you must have a valid user ID and password.

Dragging and dropping data objects

In situations where drag-and-drop capabilities are supported by the current
application, you can move data in the Teamcenter rich client by:
• Dragging a data object from one location to another.
For example, you can add an item to your favorites list by selecting it in My
Teamcenter and dragging it to the Favorites area in the navigation pane.
Note When you drag and drop an object in a structure management
application such as Structure Manager, the system makes a copy of the
object in the new location and does not move the original object.
When you drag and drop an object in a manufacturing application such
as Manufacturing Process Planner, the system moves the object to the
new location and does not make a copy of the original object.

• Dragging a data object from one application to another application.

For example, you can add an item revision to an assembly structure. Select the
item revision in My Teamcenter and drag it to the appropriate position in an
assembly structure open in a Structure Manager pane.

PLM00191 J Rich Client Interface Guide 2-113

Chapter 2 Managing the Teamcenter client interface

Note Drag-and-drop capabilities vary by rich client application. For example:

• In the My Teamcenter Summary view, you can drag and drop a dataset
file on the view header to attach the dataset to the currently selected
item revision object.

• In the My Teamcenter Viewer view, drag-and-drop capabilities are not

available for dropping dataset files on the view header.

• In Structure Manager, if you drag and drop a dataset onto a BOM line,
the dataset is not attached, although it is created in the Newstuff folder.

• In the Systems Engineering view, drag-and-drop capabilities are not

available for dropping dataset files onto a BOM line.

You can also open applications by dragging an object and dropping it on the
application button in the navigation pane.
For example, you can drag an item revision representing a subassembly from
the My Teamcenter tree and drop it on the Structure Manager button in the
navigation pane. The system opens the Structure Manager application and shows
the subassembly structure.
You can select multiple files and use drag and drop to link them to a business object.
For each file a dataset is created and linked to the item revision.

• When you drop files on an item in Teamcenter, the Multiple Drag and Drop
dialog box displays file information in a table.

• The table populates the most suitable Dataset Type, Tools, and Reference based
on the Default_dataset_type preference for each file dropped.

• The Dataset Type list is populated with the type which is suitable for the file
dropped by the user. This is driven by Dataset Type Definition specified in the
Business Modeler IDE.

In the rich client you can drop multiple files on following types of object and their
subtypes:

• Items and item revisions

The relation between the item or item revision and the dataset is automatically
selected, based on the default paste relation for the item or item revision type.

• Folders
Datasets are pasted in corresponding folders.

• BOM line objects

Created objects are pasted in the user Newstuff folder.
To attach datasets to underlying objects for a BOM line, you must drop the files
into the Structure Manager Attachments data pane.

2-114 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Note Set the following environment variables to specify behavior for drag and
drop actions:
DRAG_AND_DROP_Default_dataset_type
Specifies the default dataset types for files added to objects by drag and
drop actions.
DRAG_AND_DROP_file_limit
Specifies the number of the files that can be dragged and dropped by
each drag and drop action.
DRAG_AND_DROP_SWING_dialog_enable
Specifies whether to show or hide the multiple file drag-and-drop dialog
box for single-file drag-and-drop operations.

For information about environment variables, see the Preferences and

Environment Variables Reference.

Using the Localization button

If you are granted translation access privileges, when you log on to Teamcenter
you may see the Localization button in properties dialog boxes next to property
objects that are localizable.
Click the Localization button to display the Language Translations dialog box
that lists existing translation values. This button appears only if special localization
configurations are made.
For more information about the Localization button , see the Localization Guide.
Note If you find that Asian multibyte characters do not display correctly in the
rich client, set your system font to a font that supports Asian multibyte
characters. For example, on Microsoft Windows systems, the Arial Unicode
MS font can be set to Message Box to correct this problem.
Similarly, if you find that Asian multibyte characters do not display correctly
when you start the rich client using the native language (-nl) option, you
should restart your system in the appropriate locale and set your system font
to a font that supports Asian multibyte characters.

Organize data in folders and pseudofolders

A folder is a container for an aggregation of objects. Some folders, such as the
default Home , Mailbox , and Newstuff folders, have unique icons.
You can use folders to organize both company-wide and individual user data.
• Your company may create a visual method of organizing data using folders.

• Folders can be nested to practically any extent desired.

• Data can be referenced by any number of folders.

PLM00191 J Rich Client Interface Guide 2-115

Chapter 2 Managing the Teamcenter client interface

• A folder in Teamcenter is not the same as a directory in the operating system.

When you delete a folder in Teamcenter, only the folder is deleted, not the
contents of the folder.

2-116 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

A pseudofolder is a special container that stores and displays item and item
revision relations in My Teamcenter.
Pseudofolders let you easily see and navigate to objects related to the current object,
because pseudofolders are configured in hierarchical structures.
• Teamcenter automatically creates pseudofolders to display relations for many
item types.

• You can use preferences to specify properties displayed as a pseudofolder under

a node for an object.
Note Pseudofolders show relations, but pseudofolders are not physical folder
objects in Teamcenter.

For more information about working with pseudofolders, see Working with
pseudofolders and smart folders.

Home, Newstuff, and Mailbox folders

The My Teamcenter application always contains the three default folders: Home ,
Mailbox , and Newstuff . These folders are automatically created by the system.

• Home
The objects you want to work with in the My Teamcenter application can be
placed within your Home folder or within some folder structure beneath the
Home folder.

• Mailbox
The Mailbox folder is the receiving point for any Teamcenter mail that has been
sent to you. When you receive new Teamcenter mail, you see an envelope object
in your Mailbox folder.
For information about using Teamcenter mail, see the My Teamcenter Guide.

• Newstuff
The Newstuff folder is the default folder for newly created database objects. You
can designate other folders as the default location for newly created database
objects. Objects remain in a folder until you move or remove them.
Note You can move through topics in a page-by-page manner by clicking an entry
in the table of contents, and then pressing the down arrow. This displays the
next topic, and even expands collapsed hierarchies as you proceed.

PLM00191 J Rich Client Interface Guide 2-117

Chapter 2 Managing the Teamcenter client interface

Working with pseudofolders and smart folders

Pseudofolders display relations.
• In some situations, Teamcenter automatically creates pseudofolders.
For example, when you create a vendor management object such as a vendor
part, the system creates organizational pseudofolders to display related vendors,
commercial parts, quality documents, and locations.

Similarly, smart folders used by the Project application are pseudofolders and
serve as filters for project data.

Functionality for which pseudofolders are automatically created by the system

include vendor management, change management, and Project.

• You can set preferences to specify properties displayed as related pseudofolders.

You can do this by directly editing preferences provided with the system or by
adding shown relations to selected objects.
o To edit preferences directly, use the Options dialog box and select the
appropriate preference in the Index pane. Choose Edit®Options to display
the Options dialog box.
For example, by default, the system sets the
CompanyLocation_PseudoFolder preference to specify that the
ContactInCompany is displayed as a pseudofolder under a node of a
company location object. Such preferences are described in the relevant
application documentation.

2-118 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

o To create pseudofolders for a specified item or item revision type, place the
desired relations in the Shown Relations lists on the General and Related
Object tabs of the Options dialog box.
For example, you can specify that each time an item revision is created, it
contains pseudofolders for Contacts and Addressed By relations.

Choose Edit®Options to display the Options dialog box, and then select Item
Revision and move the required relations to the Shown Relations box on
both the General and Related Object tabs.

PLM00191 J Rich Client Interface Guide 2-119

Chapter 2 Managing the Teamcenter client interface

Working with folders

Folders are a flexible way to organize your product information. Folders can contain
references to other objects including other folders.
Use Teamcenter to:
• Create a new folder.

• Rename a folder.

• Print a folder.

• Delete a folder.

Create a new folder

• Choose File®New®Folder to create a new folder.

2-120 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Key points
Key points about the New Folder dialog box:
• A red asterisk indicates a required entry.

• Enter a short descriptive name. The limit is 32 ASCII characters.

• You can enter a general text description of up to 240 characters. This is optional.

• Set the Type to Folder for general-purpose folders.

Rename a folder
1. To change the name of a folder, right-click the folder object and choose Edit
Properties.
The Check-Out dialog box appears.

2. (Optional) Type a value in the Change ID box and add comments.

3. Click Yes to check out the object.

PLM00191 J Rich Client Interface Guide 2-121

Chapter 2 Managing the Teamcenter client interface

The Edit Properties dialog box for the selected folder object appears.

4. In the Edit Properties dialog box, you can enter a new name and/or description
for the folder, if desired.
Note You may need to scroll down to access the Name and/or Description
boxes to edit.

5. Click Save and Check-In , Save , Cancel Check-Out , or Close .

Reorder objects in a folder or view

You can reorder objects in a folder or view in My Teamcenter using the Move
command.
1. Select an object in a My Teamcenter folder or view.

2. Click the View Menu button for the folder or view.

3. Choose the applicable Move command.

For example, choose Move→Up to move the object closer to the top of the list of
objects in the My Teamcenter folder or view.

2-122 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Print a folder

• Select the folder and choose File®Print or File®Print....

Choose File®Print to print the folder name and a listing of the folder contents.

Choose File®Print... to access additional print options.

Delete a folder

1. Select the folder object and click Delete .

A confirmation dialog box appears so you can confirm the deletion.

PLM00191 J Rich Client Interface Guide 2-123

Chapter 2 Managing the Teamcenter client interface

2. Click More to list the object or objects selected for deletion.

3. Click Yes if you want to delete the folder.

Note When deleting a folder, the contents of the folder are not deleted. The
folder contents remain in the database and can be located and retrieved
using the search feature in My Teamcenter.

User interface panes

Some rich client applications use movable views to provide functionality, while other
applications use static panes.
Rich client application panes can include menus, buttons, and panes. Panes cannot
be moved around in an application.
• The menu bar includes commands relevant to the current Teamcenter
application.
For more information about menu commands, see Rich client menus.

• The toolbar includes buttons to access commands.

For more information about buttons, see Customizing the toolbar.

• The application tab has a blue background and white lettering on the tab to
indicate the current application.

• The Folder , or tree, pane provides dynamic hierarchical navigation through

data and structures. You change the content of the tree pane by clicking to
expand or collapse containers, or by clicking buttons such as the Home button
or My Worklist in the navigation pane.

2-124 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

• At the bottom of the tree pane, the name search box lets you quickly locate items
by name, and the Open home folder , Open Worklist , and Most Recently
Used (MRU) buttons let you quickly switch content without moving the
cursor back to the top of the tree pane.

• The rich client data pane provides Summary, Details, Viewer, Referencers,
and Display Data panes.

Using the folder tree pane and data panes

The rich client application data panes display data about a variety of objects in
several contexts:
• The Folder pane uses the Summary, Details, Viewer, and Referencers panes to
display information about currently selected objects.
Note The Viewer pane supports a wide range of formats, including compound
Microsoft Word documents, standard Microsoft Word and Excel files,
and Lifecycle Visualization embedded viewer support for 2D, 3D, and
ECAD file formats.

• The Search pane uses the Display Data pane as well as the Folder, Summary,
Details, Viewer, and Referencers panes.

Using the Folder pane

You display or hide the folder tree pane by clicking the Folder button on the
toolbar.
The Folder pane lets you:
• View and expand objects such as those contained in folders or returned as search
results.

• Modify or manipulate selected objects using applicable menu bar commands,

toolbar commands, and shortcut menu commands.

• Drag objects to other applications. For example, if you drag an item revision
representing a subassembly from the My Teamcenter tree and drop it on
the Structure Manager button in the navigation pane, the system opens the
Structure Manager application and shows the subassembly structure.

• Print object information such as properties and contents by level using tabular
property output and graphical application output.

Using data panes

The data panes support several ways to look at object information.
• The content of the button bar at the bottom of the data pane changes based on
the content and context in the data pane.

PLM00191 J Rich Client Interface Guide 2-125

Chapter 2 Managing the Teamcenter client interface

• The status indicators below the data pane indicate the write, delete, change,
process, checkout, release, publish, classification, and archive status of the
selected item.

Using the Summary pane

You can display the Summary pane by selecting that option in the upper-right
menu .
The command bar at the bottom of the Summary data pane provides alternate views
for information, including Impact Analysis, to quickly see Where: Used and Where:
Referenced information without switching to the Referencers data pane.
The Summary pane lets you:
• View properties for the selected item.

• Edit attributes such as name or description for supported items for which you
have appropriate permissions.

Your administrator can configure the content displayed in the Summary pane. For
more information about changing Summary contents, see the Client Customization
Programmer’s Guide.

Using the Details pane

You can display the Details pane by selecting that option in the upper-right menu .
The Details pane lets you:
• View properties of contained items by selecting the container object in the
navigation pane.

• View properties of contiguous or noncontiguous objects by selecting the objects in

the navigation pane for which you want to view properties.

• View results from advanced searches in tabular format.

• Modify the properties of multiple objects simultaneously by selecting the objects

in the Details pane, right-clicking the objects, and choosing Properties to display
the Common Modifiable Properties dialog box.
Note The default display order for column contents in most views is specified by
the Teamcenter server. In the rich client, you can click a column header to
cycle through ascending, descending, and server default order. For rich client
Teamcenter component (tree) views and for the Search Results view, use
Edit®Options to display the Options dialog box, and then select UI and click
the General tab to select a Tree displaying order option.

Configuring application tables

Application tables let you insert, remove, and reposition columns, as well as apply
and save column configurations.

2-126 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Insert columns in an application table

1. Right-click in the header of a column and choose Insert Column(s).

The system displays the Change Columns dialog box.

2. In the Category and Type column, expand the options and select an object type.

3. Select attributes from the Available Columns list and click the Add button .
Tip To locate attributes in the Available Columns list, type the attribute
name in the box above the list.

4. Set the display order of the columns using the Up arrow button and the
Down arrow button .

5. (Optional) Clear the Use displayable name box to display the attribute names
rather than the displayable names in the column headers.

6. (Optional) To save the column configuration, click Save.

7. In the Save Column Configuration dialog box, type a name and description for
the configuration, for example Part properties table.

8. Click Save.

9. In the Change Column dialog box, click Apply.

Remove columns from an application table

1. Right-click the header of the column that you want to remove and choose
Remove this column.

2. Click Yes to remove the column.

Reposition columns in an application table

1. Click the header of the column that you want to move and hold the mouse button.

PLM00191 J Rich Client Interface Guide 2-127

Chapter 2 Managing the Teamcenter client interface

2. Drag the column to the desired position in the table and release the mouse
button.
Tip Leaving the Object and Type columns in the first and second positions in
the table allows you to easily identify the data displayed in the table.

The column is displayed in the new position.

Apply a saved column configuration in an application table

1. Right-click in the header of a table column and choose Apply a column

configuration.

2. In the Apply Column Configuration dialog box, select a configuration and click
Apply to display the table data using the saved configuration.
Note You can also modify a saved column configuration, delete the saved
configuration, or create a new saved configuration based on a saved
configuration.

Using the Viewer pane

You can display the Viewer pane by selecting that option in the upper-right menu .
The Viewer pane displays data about a selected object or image files attached to
a selected object.
The viewer can display summary data and can let you work with a wide range of
graphic and business file formats.
• If you select a compatible office document dataset, such as Microsoft Word,
Microsoft Excel, or text files, the viewer displays the contents.

• If you select content from Systems Engineering, the viewer lets you view and
edit content in an embedded Microsoft Word environment.
For more information about working with requirements, see the Systems
Engineering Guide.

• If you have the embedded viewer installed, you can select a 2D, 3D, or ECAD
dataset and work with 2D and 3D image files of model and printed circuit board
designs.
For more information about using Lifecycle Visualization functionality, see
Getting Started with Product Visualization.

• If you are using Manufacturing Process Management application Teamcenter

Publish functionality to create PDF files of portfolios, Viewer pane can display
portfolio elements and properties. In the Viewer pane, the menu bar File menu
lets you publish Zip (compressed) or PDF files to the database, and provides
print and print preview commands.
For more information about configuring manufacturing data and creating
portfolios, see Getting Started with Manufacturing.

2-128 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Using the Referencers pane

Some rich client applications let you display the Referencers pane by selecting
that option in the upper-right menu .
Note Display of the Referencers pane is controlled by the
ReferencersPane_Shown preference.

The Referencers pane lets you work with an object you select in the navigation pane
or drag to the Referencers pane from another pane in your application.
You can:
• Conduct where-used and where-referenced searches for selected objects. For
example, you can perform a where-used search, look through the search results
to find a specific item revision, then perform a where-referenced search on that
item revision. This lets you see whether alterations to one assembly affect
another assembly.
For more information about where-used and where-referenced searches, see the
Where-used and where-referenced searches.

• Apply filtering criteria to your search from the Extended Multi-Application

Search option.
For more information about multi-application search, see the Using extended
multi-application searches.

• Expand trace links to show complying objects that partially or fully satisfy
conditions imposed by a defining object. For the selected object, any object that
is defined in a trace link with a Complying relation is shown in the Where
Referenced graphic display in the Referencers pane.
For more information about trace links, see the My Teamcenter Guide.

Using the Display Data pane

You can display the Display Data pane by selecting that option in the upper-right
menu . The Display Data pane is available for use only with Search results,
in conjunction with Property Formatter queries, to present property information
related to items returned by a search.
For more information about using the Display Data pane, see Formatting search
results by object properties.

Configuring table data display in the rich client

You can configure the way data is displayed in tables throughout the rich client
interface. The method of configuring data display in application table panes, such as
in Structure Manager, differs from the method of configuring data display in view
tables, such as the Details view in My Teamcenter.
After you configure the table data display using either method, you can:
• Apply the configuration to the current table.

• Save the configuration and apply it another time you want to view data.

PLM00191 J Rich Client Interface Guide 2-129

Chapter 2 Managing the Teamcenter client interface

To configure the data display in an applications table pane, right-click a column

header and choose the applicable command from the Table Function Menu.

To configure the data display in a view table, click the Menu button and choose the
applicable command from the view menu.

Printing information about your data

Use the Print and Print... commands on the File menu to display, format, save, and/or
print the following types of information about your Teamcenter objects:

2-130 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

• The hierarchical structure of a selected object and its descendant objects.

For example, you can select a folder and display all of the first-level descendants
or you can enter a level of descendants to be displayed. This allows you to display
and print any level of the structure.

• The hierarchical structure of a selected object (first-level descendant objects

only), including the object properties and corresponding values.

• The properties of a selected object and their corresponding values.

• The active Teamcenter table or the Referencers pane, as it appears in the

application window.
Note You can only print information related to a single selected object.

The following table describes the printing options and the expected output for each
option based on the selected object type.
Note The following table describes only the Object Properties and Contents
options in the Print dialog box. The Application options in the Print dialog
box enable you to print the active table, tree display, or Referencers pane as
it appears in your Teamcenter window.

Selected
object type File®
®Print File®
®Print...®
®
Folder Displays the folder Objects Properties displays the folder
and its first-level properties.
descendant objects.
Contents displays the folder and its
descendant objects to the level in the
hierarchy that you specify.
Form Displays the form Object Properties displays the properties
properties. associated with the form.
Form Properties displays the property
values of the specific form.
Item or item Displays the item or Object Properties displays the properties
revision item revision and its of the item or item revision.
first-level descendant
objects. Contents displays the item or item
revision and its descendant objects to the
level in the hierarchy that you specify.
BOM line Displays the BOM line Object Properties displays the BOM line
structure currently properties.
displayed in Structure
Manager. Contents displays the structure of the
BOM line as it is displayed in Structure
Manager.

PLM00191 J Rich Client Interface Guide 2-131

Chapter 2 Managing the Teamcenter client interface

Selected
object type File®
®Print File®
®Print...®
®
Dataset Displays the properties Object Properties displays the properties
of the dataset. of the dataset.
Data launches the tool associated with
the dataset and displays the contents
within the tool.
For example, if you select a text dataset
and choose File→Print...→Data, you can
select the text editor in Tool Used and
view the contents of the file associated
with the dataset.
Other Displays the properties Object Properties displays the properties
of the workspace of the selected workspace object.
object.
Contents displays the object and its
descendant objects to the level in the
hierarchy that you specify.

Formatting information for printing

After you choose the information to print, you can select the output type; graphic,
HTML, or text, and apply format options before printing or saving the information.
The following tables describe the output types.

Format Description
Application Saves and/or prints a graphical image of object or table data
(Graphics) as it is displayed in your Teamcenter window.
HTML Saves object and table data in HTML format that can be
viewed in any Web browser.
Text Text format is used to save and/or print object or table
data. The data can be aligned in columns or formatted as
delimited text strings using a user-specified delimiter.

The following table describes the formatting options.

Option Description
Title Determines whether the title of the selected object or user
interface component is printed.
Column Alignment Enables column alignment when using text format.
Delimiter Specifies the character that separates character strings.
Date Determines whether the current date is included in the
printed output.

2-132 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Option Description
Object Count Determines whether the object count is included in the
printed output.
Select Printing Displays a list of object properties to be printed, allowing you
Columns to select which properties to include in the printed output.

Click the Set Result Format button in the upper-right corner of the Print dialog
box to open the Print Format dialog box.

Print object information

1. Select the object in the tree structure or Details table and choose File→Print....
Note The contents of the dialog box differ depending on the type of object
you select.

2. Select one of the following content options:

Object Properties Creates a report of the properties of the selected

Contents
Application (HTML/Text)
object.
Creates a report of the contents of the selected
object. When the Contents option is selected, the
Level text box is activated so that you can define
the level of content to be reported.
Increasing the content level is similar to
expanding nodes in a tree structure.
For example, if you type 1 in the Level box, the
selected object and its primary components are
included in the report. If you type 2 in the Level
box, the selected object, its primary components,
and the children of the primary components
are included in the report. You can continue to
increase the level until you reach the bottom of
the structure.
Creates a tabular report of the properties of the
selected object in HTML format.
Note If the Referencers pane is displayed in
your Teamcenter window, the contents of
that pane, rather than the properties of
the selected object, are reported.

PLM00191 J Rich Client Interface Guide 2-133

Chapter 2 Managing the Teamcenter client interface

Application (Graphics) Creates a graphical report of the active table as

it appears in the application window. When this
option is selected, the results are sent directly to
the printer. There are no options for previewing
and formatting the report.
For example, if the Referencers pane is active,
its contents are printed as displayed in the
application. The same applies to the Details table.

3. Click OK.

4. (Optional) Modify the print format settings.

For more information, see Getting Started with Teamcenter.

5. Click the Print button or the Save button to print or save the output.

6. Click Close.

Print objects information from the Properties dialog box

1. Select an object from the tree or Details table.

2. Choose View→Properties.

3. Click the Print button located in the lower-right corner of the dialog box.

4. (Optional) Change the print format to Text. (HTML is the default print format.)

5. (Optional) Modify the print format settings. For more information, see
Formatting information for printing.

6. To save the file, open it in a Web browser or send it to a printer and complete the
process that is appropriate to the file type and desired output.
Open HTML files in a Web browser

a. Click the Open in Web Browser button .

b. Execute your browser’s print command.

c. Return to the Teamcenter window and click Close.

Print a text or HTML file

a. Click the Print button in the lower-right corner of the Print dialog box.

b. Define the printer to which the file is sent.

You can accept the default printer or select a different printer from the list.

c. Click Print.

2-134 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

d. Click Close.

PLM00191 J Rich Client Interface Guide 2-135

Chapter 2 Managing the Teamcenter client interface

Save output to a user-specified (HTML or text) file

a. Click the Save button in the lower-right corner of the Print dialog box.

b. Navigate to the directory location where you want to save the file.

c. Type the name of the file, including the .htm, .html, or .txt extension, in
the File name box.

d. Click Save.

e. Click Close.

Print information contained in tables

1. Right-click in the column heading area of the table, and choose Print Table.

2. Choose one of the following options:

HTML/Text Displays the contents and column properties of the table in
HTML format. If you prefer to format the table in plain text,
change the print format by selecting the Text option in the
upper-right corner of the dialog box.
Graphics Allows you to send a graphical representation of the contents
and properties of the table (as they are displayed in your
application window) to the printer.

Print where-referenced information

1. Right-click in the Referencers pane and choose Print.

2. Choose one of the following options:

HTML/Text Displays the contents and column properties of the table in
HTML format. If you prefer to format the table in plain text,
change the print format by selecting the Text option in the
upper-right corner of the dialog box.
Graphics Allows you to send a graphical representation of the contents
and properties of the table (as they are displayed in your
application window) to the printer.

Print form properties from the Properties dialog box

1. Double-click the form in the tree or Details table.
OR
Select the form and choose File→Open.

2. Click Print file in the lower-right corner of the dialog box.

3. (Optional) Change the print format to Text. (HTML is the default print format.)

4. (Optional) Format the report by performing the following steps:

2-136 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

a. Click the Set Result Format button in the upper-right corner of the
Print dialog box.

b. Modify the result format.

c. Click Update.

d. Close the Print Format dialog box.

5. To save the file, open it in a Web browser, or send it to a printer, complete the
process that is appropriate to the file type and desired output.
Open HTML files in a Web browser

a. Click the Open in Web Browser button .

b. Execute your browser’s print command.

c. Return to the Teamcenter window and click Close.

Print a text or HTML file

a. Click the Print button in the lower-right corner of the Print dialog box.

b. Define the printer to which the file is sent.

You can accept the default printer or select a different printer from the list.

c. Click Print.

d. Click Close.

Save output to a user-specified (HTML or text) file

a. Click the Save button in the lower-right corner of the Print dialog box.

b. Navigate to the directory location where you want to save the file.

c. Type the name of the file, including the .htm, .html, or .txt extension, in
the File name box.

d. Click Save.

e. Click Close.

Print form properties from the viewer

1. Select the form in the tree or Details table.

2. Click the Viewer tab.

3. Click the Print the file button in the lower portion of the viewer.

4. (Optional) Change the print format to Text. (HTML is the default print format.)

PLM00191 J Rich Client Interface Guide 2-137

Chapter 2 Managing the Teamcenter client interface

5. (Optional) Format the report by performing the following steps:

a. Click the Set Result Format button in the upper-right corner of the
Print dialog box.

b. Modify the result format.

c. Click Update.

d. Close the Print Format dialog box.

6. To save the file, open it in a Web browser, or send it to a printer, complete the
process that is appropriate to the file type and desired output.
Open HTML files in a Web browser

a. Click the Open in Web Browser button .

b. Execute your browser’s print command.

c. Return to the Teamcenter window and click Close.

Print a text or HTML file

a. Click the Print button in the lower-right corner of the Print dialog box.

b. Define the printer to which the file is sent.

You can accept the default printer displayed in the Name box or select a
different printer from the list.

c. Click Print.

d. Click Close.

Save output to a user-specified (HTML or text) file

a. Click the Save button in the lower-right corner of the Print dialog box.

b. Navigate to the directory location where you want to save the file.

c. Type the name of the file, including the .htm, .html, or .txt extension, in
the File name box.

d. Click Save.

e. Click Close.

Printing Teamcenter objects in Teamcenter Rapid Start

In Teamcenter Rapid Start, you can print the following object types:
• CAD drawings in a part, assembly, or folder

• Microsoft Office documents in a part, assembly, or folder

2-138 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Note You can print .doc, .docx, .xls, .xlsx, .ppt, and .pptx files.

• Images in a part, assembly, or folder

Teamcenter Rapid Start also allows you to print a watermark on your output. A
watermark is text or an image that appears in the background of each page of your
printed document.
The following table describes the printing options and the expected output for each
option based on the selected object type.

Selected object Print Button or

type right-click®
®Print File®
®Print...
Folder with Sends the contents of Opens a print dialog window
datasets, items, the folder to the default where you can select the desired
and/or item printer. printer and optionally specify a
revisions watermark. Once the options are
selected, the contents of the folder
are printed.
Item or item revision Sends the contents Opens a print dialog window
of the item or item where you can select the desired
revision to the default printer and optionally specify a
printer. watermark. Once the options are
selected, the contents of the folder
are printed.
Dataset Sends the contents Opens a print dialog window
of the dataset to the where you can select the desired
default printer. printer and optionally specify a
watermark. Once the options are
selected, the contents of the folder
are printed.

How to print objects

1. In Teamcenter Rapid Start, select the object or objects in the tree structure
or Details table.
Note To select multiple objects, press the Ctrl key as you click.

2. Perform one of the following:

• To send the selected files to the printer without specifying print options, click
the Print button in the toolbar or right-click and choose Print from the
shortcut menu.

• To specify print options and watermarks:

a. Choose File→Print....

b. Select Client Printer or Server Printer and then choose the printer name
from the list.

PLM00191 J Rich Client Interface Guide 2-139

Chapter 2 Managing the Teamcenter client interface

c. Optionally, to print a watermark on the documents, perform one of the

following:
o To print watermark text, select Watermark Text and then enter the
text in the corresponding text field.

o To print a watermark graphic, select Watermark Path and then click

the Browse button to locate the graphic file you want to use as the
watermark.
Note To adjust the location of the watermark, you can edit the
TC_ROOT\tcvis\VVCP\vvcp.ini file. In addition, you can
optionally specify the path to an MDS (metadata stamping)
file that contains predefined watermark text. You can use
MDS stamp commands to change, customize, and improve file
stamping. MDS stamp commands are preferences used to create
more detailed stamps to apply to your files.

d. Click Print.

Using preferences
Preferences are special environment variables stored in the Teamcenter database.
Preference instances are used to control the behavior and display of Teamcenter
applications.
• Teamcenter provides thousands of preferences that you can use to configure the
product to your specific needs.

• Administrator and nonadministrator users can configure many aspects of a

session, such as the checkout directory and how often Teamcenter checks for
new system mail. Preferences can apply to the entire site, a specific user, a
group, or a role.

Preferences control the behavior of Teamcenter clients and servers. The rich client
provides an Options dialog box that lets you interactively select to specify behaviors.
The thin client also provides an Options dialog box that lets you set a more limited
group of preferences.
For more information about working with preference setting through options in the
thin client, see the Thin Client Interface Guide.
For information about specific preferences, see the Preferences and Environment
Variables Reference.
Note In the rich client, another set of preferences are provided by the
Window®Preferences menu command. These client preferences, which
are displayed and edited in the Preferences dialog box, are local to the
user. These preferences are documented in the context of the applications
to which they apply.

2-140 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Preference definition elements

Administrators can create preference definitions in the Teamcenter rich client
Options dialog box.

A preference definition consists of the following elements:

Information box The text box on top on the right side provides information
such as recommended actions and reasons why some actions
are unavailable.
Name The preference name must be unique and can contain
uppercase and lowercase letters, numbers, periods, and the
underscore character.
Location Specifies the level at which the preference instance value is
active. The location for a preference value can be Site, Group,
Role, User, or None.
Note When Location is None, the preference has a definition
but does not have any instances.

PLM00191 J Rich Client Interface Guide 2-141

Chapter 2 Managing the Teamcenter client interface

Protection Scope Specifies who can create or edit a preference instance value.
Preference protection scope can be System, User, Role, Group,
or Site.
Note The protection scope of a System preference cannot be
changed, and the value specified for a Site or System
protection scope preference can only be changed by
Teamcenter administrators.
The protection scope for User, Role, Group, or Site
hierarchical preferences can only be modified by a
system administrator.

Category Indicates the functional area in which the preference is used.

Preferences are categorized according to the technical area of
Teamcenter they affect. For example, all dataset preferences
are assigned to the Application Encapsulation category
and all Multi-Site Collaboration preferences are assigned
to the Multisite category. As a category may contain a large
number of preferences, it may contain subcategories to allow
easier location and identification of a specific preference. For
example, the Multisite category may contain subcategories
called Multisite.General, Multisite.ODS, Multisite.IDSM, and
Multisite.RemoteImport. A system administrator can create
new categories or subcategories that are appropriate for your
business practices and assign preferences to those categories
and subcategories. Category is a property on the preference
definition and any changes apply to all existing and new
instances. Searches for preferences can be limited to certain
categories.
Environment Specifies whether a preference name can be used (Enabled)) as
an environment variable to set the preference value or cannot
be used (Disabled) as an environment variable.
You can declare the preference name as an environment
variable with an appropriate value on the Teamcenter server
host if the preference definition contains the Enabled value.
In such cases, the environment variable is considered an
instance of a preference. When the preference definition
specifies Environment as Enabled, a preference search first
checks for an environment variable with the same name as
the preference and, if defined, uses that environment variable
value. Otherwise, the normal search pattern for precedence
is followed.
For information about preference precedence, see System and
hierarchical preferences.

2-142 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Type Allows you to define one of five types of preferences:

• String
Valid values are any valid string of characters.

• Logical
Valid value is one of any logical pair (on or off, true or
false, 0 or 1).

• Integer
Valid values are any positive integer.

• Double
Valid values are floating point (real) numbers (-12.34,
99.05).

• Date
Valid values are calendar date and time entries in
DD-MM-YYYY HH-MM-SS format, for example,
23-Fe-2008 16-32-45.
Note To ensure correct display of date format in the
interface, Siemens PLM Software recommends
users set values from the Options dialog box,
rather than through the XML file.

Multiple Specifies whether a preference is defined to accept multiple

values (Multiple) or a single value (Single).
Description Provides information about the functionality affected by the
preference.
Value/Values Lists the value or values associated with the preference.
Note Do not enter localized business object names in
preferences. For example, when entering a value in a
preference, you must enter the business object name
as it appears in the database, not the localized name of
the business object.
For information about working with business objects,
see the Business Modeler IDE Guide.

System and hierarchical preferences

There are two types of preferences:
• System preferences have a protection scope of System, and apply to the entire
Teamcenter site. These preferences provide settings that apply to the entire
Teamcenter deployment. Several system preferences ship with Teamcenter.

• Hierarchical preferences have a protection scope of User, Role, Group, or Site.

The system uses the hierarchy, beginning with User, then checking Role, Group,
and Site, to retrieve a preference value.

PLM00191 J Rich Client Interface Guide 2-143

Chapter 2 Managing the Teamcenter client interface

The system uses the hierarchy to search for preference values, starting at the
level defined by the protection scope and going up the different levels in the
order: from current user, to current role, then current group, and then site.
For example, the system looks for the preference value of a role protected
preference in the following manner:

o If a value exists for the current role, that value is used.

o If no value exists for the current role, but a value exists for the current
group, that value is used.

o If no value exists for the current role or group, but a value exists for the
site, that value is used.

o If no value exists for the current role, group, or site, no value is returned.

Preference values can be defined at different levels depending on the defined

protection scope:

o Teamcenter administrators can create instances for preferences that have

a protection scope of User, Group, Role, or Site.

o Teamcenter group administrator users can create instances for preferences

that have a protection scope of Group, Role, or User.

o Teamcenter nonadministrator users can only create instances for preferences

that have a protection scope of User.

Managing protection scope

All preferences have a protection scope.
Hierarchical preferences that are available immediately in a new installation
each have a default protection scope of Site, Group, Role, or User. Only system
administrators can change the protection scope for hierarchical preferences.
Administrators can manage protection scope for preferences in two ways:

• In the rich client Options dialog box

This method is best for modifying small numbers of preferences individually.

• Using the preferences_manager utility

This method is best for updating the protection scope, values, and behavior of
multiple preferences.
For more information about using the preferences_manager utility, see the
Utilities Reference.

Note Some preferences are automatically created when certain functionality is

added.

2-144 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Working with preferences in the rich client

Preferences let you configure many aspects of a Teamcenter session. Preferences
are read by the system as soon as they are set. The current preferences are updated
whenever you change your group or role while working in Teamcenter.
Teamcenter provides many preferences required by different applications to work
properly, and each preference has default settings. You can view these preferences
in the rich client Options dialog box, in the Options, Preferences By Filters,
Preferences By Search, and Preferences By Organization panes.
System administrator users can create new preferences either by using the
Options dialog box or by creating a preference XML file for use as input by the
preferences_manager utility or by the Import tab on the Preferences By Filters ,
Preferences By Search, and Preferences By Organization panes.
• In the Options dialog box
This method is best for modifying small numbers of preferences individually.

• Using the preferences_manager utility

This method is best for updating the protection scope, values, and behavior of
multiple preferences.
For more information about using the preferences_manager utility, see the
Utilities Reference.

For detailed descriptions of the individual preferences, see the Preferences and
Environment Variables Reference.

Set a preference option

Note An option is an encapsulation of a preference in the Options pane in the
Options dialog box. Place the mouse cursor over an option to display the
preference name and its protection scope.
In the Options dialog box, on the Options pane, fields are enabled or
disabled, depending on the protection scope.
You can place your mouse cursor over a value label in the Options pane
to see a tooltip listing the name and protection scope for the relevant
preference. Preference protection scope is also displayed in the Options
dialog box on the Preferences By Filters, Preferences By Search, and
Preferences By Organization panes, when you have selected the Definition
tab, for administrator users, and the Instances tab, for all users.

1. Choose Edit→Options.
The Options dialog box is displayed with the Options pane selected.

2. Click the functional area in the tree that corresponds to the application or
system behavior that you want to modify. For example, choose General®Item
to set item-related options such as whether all revisions are displayed in the
interface by default.

3. In the right pane of the dialog box, modify the preference settings.

PLM00191 J Rich Client Interface Guide 2-145

Chapter 2 Managing the Teamcenter client interface

4. Click Apply or OK.

For more information specific options and preferences, see Option reference.

Searching for preferences

You can search for preferences in the database either by name, using the Preferences
By Filters pane or by keyword using the Preferences By Search pane. You can also
filter the results of a preference search by category and by protection scope.

Search for a preference by name

1. Choose Edit→Options.
The system displays the Options dialog box.

2. Click the Filters link at the bottom of the dialog box.

The system displays the Preferences By Filters pane. The preferences available
to you based on your access are listed alphabetically in the left section of the box.

3. Type the preference name in the Search by preference name filter box.
As you type, the system displays the preferences that match the characters you
have entered and displays the number of preferences.

Search for a preference using keywords

1. Choose Edit→Options.
The system displays the Options dialog box.

2. Click the Search link at the bottom of the dialog box.

The system displays the Preferences By Search pane.

3. (Optional) Select the appropriate Search In option.

Keys Searches for preference names.
Description Searches for keywords in preference descriptions.
Values Searches for keywords in preference values.
All Searches for the keyword in preference keys, descriptions, and
values.

4. (Optional) Select the appropriate Match option.

Case Searches for keywords that match the type case used when you
entered the keyword.
Entire Word Searches for keywords matching the entire word you entered.

5. (Optional) Specify a different character in the Wildcard box.

6. Type a keyword or partial keyword and wildcard characters in the Search On

Keywords box.

2-146 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Note To search for a text that may not appear at the beginning of a preference
name, description, or value, be sure to precede the text with the
designated wildcard character.

7. (Optional) To filter results, choose a category and either a protection scope, on

the Definition tab for administrator users, or a location, on the Instances tab
for both administrator and non-administrator users.

The system displays the preferences that match your search criteria in the
Preferences List box.

Defining preferences and creating preference instances

The definition of a preference includes all relevant information fields: Name,
Protection Scope, Category, Environment, Type, Multiple or Single (for values),
and Description.
An instance of a preference specifies the level at which a preference value applies.
In addition to the information in the preference definition, a preference instance
includes Location and Value or Values.
Note You cannot create an instance for a preference until the preference is
defined, and you can only create an instance of a preference if allowed by
the protection scope.
The protection scope for a preference definition determines who can create
a preference instance or change the value of a preference instance. For
example, only a system administrator can create an instance of a preference
defined with Protection Scope set to Site. Protection scope is a property of
the preference definition. Based on the protection scope, administrators and
users can create or modify instances.
The location of a preference instance specifies the level where the preference
instance is created. For example, a preference with a location Role: Engineer
applies to all users logged on with the Engineer role.

Administrators can create an instance of a preference with a site, group, role, or

user protection scope. For example, an administrator can create an instance of a
preference protection scope of Group, and that preference then applies to all users
of the specified group. Users belonging to multiple groups and roles can change
their group or role setting to take advantage of preference settings for a specific
group or role.

• Administrators can define, view, and modify preferences everywhere.

Only a Teamcenter administrator can view and edit all preference definitions
in the system.

• When a nonadministrator user browses or searches for preferences, all

preferences applicable to that user are listed, but only preferences with a
protection scope of User can be modified. For a preference with the protection
scope set to User, each user can create an instance of that preference and only
that user is affected by that preference instance.

PLM00191 J Rich Client Interface Guide 2-147

Chapter 2 Managing the Teamcenter client interface

• For preferences with a protection scope of Group, a group administrator can

create a group instance of that preference using the Organization pane in the
Options dialog box.

Type options for preference values

String Valid values are any valid string of characters.
Logical Valid value is one of any logical pair (on or off, true or false, 0
or 1).
Integer Valid values are any integer.
Double Valid values are paired sets of integers (12.34, 99.05).
Date Valid values are calendar date and time entries in DD-MM-YYYY
HH-MM-SS format (for example, 23-Fe-2008 16-32-45).

Create a preference category

Note You must be an administrator to create preference categories.

To create a new preference category:

1. In My Teamcenter, choose Edit→Options.

2. Click the Filters link to display the Preferences By Filters pane or click the
Search link to display the Preferences By Search pane.

3. Click Category to display the Category tab.

4. Perform one of the following:

• To create a new category, leave the Parent Category blank and enter the
name of the new category in the Category box.

• To create a new subcategory of an existing category, select a category from

the Parent Category list and enter the name of the new category in Category
box.

5. Click Create.
The new category is created in the database.
The category is populated with a placeholder preference with the name
category-name_NOTREALPREF.

Delete a preference category

Note You must be an administrator to delete preference categories.

To delete a preference category:

1. In My Teamcenter, choose Edit→Options.

2. Click the Filters link to display the Preferences By Filters pane or click the
Search link to display the Preferences By Search pane.

2-148 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

3. Click Category to display the Category tab.

4. Select the category from the Parent Category list or enter the name of the
category in Category box.

5. Click Delete.
The category is deleted from the database.
Note You cannot delete or change a preference category that contains preferences.
You must remove the preferences or change their category before
deleting or changing the preference category. Placeholder preferences
(category-name_NOTREALPREF) do not need to be deleted.

Creating preferences and adding preference instances

Note If you do not have appropriate privileges, the system displays the preference
information in read-only format.

Site, group, and role preferences are created or modified by Teamcenter

administrators. The Teamcenter administrator can also create new categories or
subcategories. The category and subcategory to which a preference is assigned does
not affect who can modify the preference.
Group and role instances of preferences are modified by users with either group
administrator or administrator privileges. The group and role with which you are
logged on to Teamcenter determines, based on the protection scope, which preference
that you, as a group administrator, can modify.
• If you are logged on as a regular user, you can create or modify only of preference
instances for preferences with User protection scope.

• If you are logged on as a group administrator, you can create or modify instances
of User, Group, or Role preferences.

• If you are logged on as an administrator user, you can create or modify

preferences with Site, Group, Role, or User protection scope.
Note Role preferences apply to all occurrences of that role, regardless of the group
to which it belongs.

Create a new preference definition

Note Only Teamcenter administrators can create new preference definitions.
Mandatory fields are marked with an asterisk (*), and must be populated
to enable the Save button.

1. Choose Edit→Options.

2. In the Options dialog box, click the Filters or Search link.

3. With the Definition tab selected, click Create a new preference definition .
Teamcenter displays the preference creation boxes.

4. Type a name for the preference in the Name box.

PLM00191 J Rich Client Interface Guide 2-149

Chapter 2 Managing the Teamcenter client interface

The preference name is case sensitive and can contain spaces and special
characters.

5. Select one of the following Protection Scope options:

User
Role
Group
Site
System

For more information about protection scope, see the Preferences and
Environment Variables Reference.

6. Select the category for this preference in the Category box.

7. Choose whether this preference can be set by using the preference name as an
environment variable in the Environment box.

8. Select the value type for this preference, either String, Integer, Double, Logical,
or Date.

9. Select one of the Multiple options. Single limits the values to a single entry.
Multiple allows multiple values to be entered for the preference.

10. Type a description of the preference in the Description box.

Descriptions allow you to communicate valid values, suggested usage, and
preference behavior.

11. For a single value, type a value in the Value box.

For multiple values:

a. Type a value in the box beneath the Values list.

b. Click the Add button .

Teamcenter adds the value to the list.

c. Repeat until all values are added.

12. Click Save.

Teamcenter adds the preference to the database and applies it to the current
session.

Create a preference instance for a group

Note Only Teamcenter administrators and group administrators can create
instances or modify values of preferences with Group and Role protection
scope.

1. Choose Edit→Options.

2-150 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

2. In the Options dialog box, click the Organization link to display the Preferences
By Organization pane.

3. In the Preferences List box, select the preference for which you want to create a
Group instance.
The details of the selected preference are displayed in the Instances tab.

4. With the preference selected, use the Organization tree to locate and select the
group to which to apply the preference instance.
The information box indicates whether you can create an instance of the selected
preference for the selected group.

5. Click Create a new preference instance .

The Value box becomes editable.

6. For a single value, type a value in the Value box.

For multiple values:

a. Type a value in the box beneath the Values list.

b. Click the Add button . Teamcenter adds the value to the list.

c. Repeat until all values are added.

7. Click Save.
Teamcenter adds the preference to the database and applies it to the current
session.

Create a preference instance for a nonadministrator user

Note Nonadministrator users can create and modify instances of preferences with
User protection scope.

1. Choose Edit→Options.

2. In the Options dialog box, click the Filters or Search link, and then click the
Instances tab.

3. In the Preferences List box, select the preference for which you want to create
a User instance.
• The details of the selected preference are displayed in the Instances tab,
and the information box indicates whether you can create an instance of
the selected preference.

• When there are several values, such as values at the site level, and for your
group, and for your role, select the level that you want to create the new
instance.
The value or values of the new instance are populated from the selected
preference instance. That is particularly useful for multivalued preferences,

PLM00191 J Rich Client Interface Guide 2-151

Chapter 2 Managing the Teamcenter client interface

when the preference contains several values and the intent at the user level
is to simply add one value to the list.
Note The selected preference may be in the Site location, but it must have
the Protection Scope set to User.

4. Click Create a new preference instance .

The Value box becomes editable.

5. For a single value, type a value in the Value box.

For multiple values:

a. Type a value in the box beneath the Values list.

b. Click the Add button . Teamcenter adds the value to the list.

c. Repeat until all values are added.

6. Click Save.
Teamcenter adds the preference to the database and applies it to the current
session.

Modify the values of a preference instance

1. Choose Edit→Options.

2. In the Options dialog box, click the Filters or Search link.

3. Locate the preference using one of the methods described in Searching for
preferences.

4. Select the preference from the Preferences List box.

5. (Optional) If you are an administrator and have selected a site preference, click
Lock site preferences to prevent another administrator from modifying the
preference while you are modifying it.
Note Administrators can modify preference protection scope, environment
variable setting, description, and values. Only Teamcenter
administrators can modify site, group, and role protection scope
preferences.

6. Prepare to modify the preference, either as administrator user or as a

nonadministrator user.
• As an administrator user, click Edit on the Definition tab, or select a value in
the Values box in the Instances tab.

• As a nonadministrator user, you do not see the Definition pane. Select a

value in the Values box in the Instances pane.

2-152 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

7. Modify a value, add a value, remove a value, or change the sequence of the
values, as follows:
Note These instructions describe modifying a multivalued preference. For
preferences with only a single value, modifications are made in the box
provided.

Modify a preference value

a. Select the value in the Values list.

b. Modify the value in the text box below the Values list, and click the Modify
current value button .
Add a value to a preference
a. Type a value in the box beneath the Values list.

b. Click the Add button .

Teamcenter adds the value to the list.
Remove a value from a preference
a. Select the value in the Values list.

b. Click the Remove button .

Teamcenter removes the value from the list.
Note While you are in the Edit mode, you can reorder values by selecting an
item in the Values list and using the up and down arrows to move the
selection up or down in the list.

8. Click the Save button.

Teamcenter saves the preference modifications in the database; they are effective
immediately.

9. (Optional) If you locked a site preference before modifying it, click Unlock site
preferences .

Generating preference reports

You can generate reports that list the changes that have been made to site
preferences at your site, and reports that list all the logged-on user’s group, role, and
user preferences in the database. The following reports can be created:
• The Site preference report lists the difference between the off-the-shelf (COTS)
preferences and any new preferences added to the database. Use this report to
determine which custom preferences have been created at your site.

• The Group preference report lists all preferences stored for your current
logged-on group.

PLM00191 J Rich Client Interface Guide 2-153

Chapter 2 Managing the Teamcenter client interface

• The Role preference report lists all preferences stored for your current logged-on
role.

• The User preference report lists all preferences stored under your current user
ID.

Create preference reports

Generate reports that list the user, group, role, or customized site preferences in
your database. If desired, you can export the report to a file.
1. In the rich client, choose Edit®Options to display the Options dialog box.

2. Click either Filters or Search.

3. Click Report in the banner above the Preferences List box.

The Report dialog box appears.

4. Select the protection scope for which you want a report: User, Role, Group,
or Site.
The Report Changes dialog box lists all the preferences of the selected scope
which have been changed, providing the original and modified values. Use
the forward and back buttons at the top of the dialog box to view the various
preferences.

5. (Optional) Export the report in XML format:

a. In the Report Changes dialog box, type a path and file name in the Export
To File box (or browse to an existing file).

b. (Optional) Select Open After Export

c. Click Export.
The preference report is exported to the specified file.

Sharing preferences
Administrator and nonadministrator users can share a category of preferences or
all preferences by exporting location preferences for user, group, role, or site, and
then editing the XML file as needed, and then importing them to a different site or
user location.

Export preferences from the database to an XML file

1. Choose Edit→Options.

2. In the Options dialog box, click the Filters, Search, or Organization link.

3. Click the Export link at the top of the pane.

4. Select the hierarchy level to export in the From Location list.

2-154 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

5. (Optional) Choose the category of preferences to be exported. If you choose a

category, all preferences in the category are exported and all preferences in all
other categories are ignored. If you do not choose a category, all preferences
in all categories are exported.

6. Type a path and file name for the export file in the Export To File box or click the
button to the right of the box and locate a file in your directory structure.

7. (Optional) Select the Open After Export check box to open the XML file when the
preference export operation is complete.

8. Click Export.
Teamcenter exports the selected preferences to the specified XML file.

Import preferences into the database

Note This procedure assumes the preferences being imported are in a Teamcenter
10 preference XML file format.
For information about creating and editing preferences from preference
.XML files, see the Preferences and Environment Variables Reference.

1. Choose Edit→Options.
The system displays the Options dialog box.

2. Click the Filters, Search, or Organization link at the bottom of the dialog box.

3. Click the Import link at the top of the pane.

4. Type the name of the XML input file in the Import File Name box, or click the
button to the right of the box and locate the file in your directory structure.
Note In the Preferences By Organization pane, an administrator can select
one or more users or groups to import the preferences to the appropriate
preference locations.

5. (Administrator only) In the To Location box, specify the Site or logged-in User
location for the preferences to be imported. For example, if you choose the
User option, the imported preferences are stored as preference instances for
the logged in user.

6. Select the location of the preferences to be imported. For example, if you choose
the User option, the imported preferences are stored as preferences for the
logged in user.

7. Select one of the following import modes:

Automatic Imports all preferences in the specified file.
Selective Compares the values of the preferences in the XML file with the
preference values in the database for the specified scope and
category and displays the differences in values in a separate
dialog box. You can browse through the preferences and modify
values before importing the preferences into the database.

PLM00191 J Rich Client Interface Guide 2-155

Chapter 2 Managing the Teamcenter client interface

8. Specify one of the following options for handling duplicate preferences

encountered during the import operation:
• Override preference values in the database with values in the XML file

• Merge preference values in the database with values in the XML file
Note The merge function work only for multivalued preferences. For
single value preferences, merge skips the preference.

• Skip the preference

9. (Optional) Select the Open the log report after Import check box to open the
report file when the preference import operation is complete.

10. Click Import.

The preferences and their values are imported into the database according to
the specified handling options.

View and set rich client Eclipse window preferences

Use the Window®Preferences menu command to display the standard Eclipse
Preferences dialog box, where you can set Relation Browser preferences, Teamcenter
preferences for search and view network presentation, and Web browser preferences.
• Graphical Relation Browser Layout
Used by Relation Browser and Teamcenter Integration for NX.
For information about using the these options to configure Relation Browser, see
the Relation Browser Guide.

• Install/Update
Standard Eclipse functionality.

• Network Connections
Standard Eclipse functionality.

• Security
Standard Eclipse functionality.

• Teamcenter
o Show traditional style tabs
Select to display rectangular tabs instead of rounded tabs.

o Minimum characters for view title

Specifies the minimum number of characters displayed in view titles prior to
displaying these titles in the associated view list.

o Content Management

2-156 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

Specify editor for topic editing, graphic tagging, and content publishing
defaults.

o Search
Select to set a wide range of search options.
For information about setting search options, see Working with search
options.

o View Network Presentation

Select to set colors and patterns for view networks.
For information about changing view network color and pattern presentation
options, see Changing view network color presentation.

• Web Browser
When Web pages are opened, specifies whether to use an internal or external
Web browser, and lets you select external Web browsers.

Working with rich client persistent caches

The Teamcenter rich client uses persistent cached information that is local and
specific to each user. The cache includes information about session windows, current
plug-ins, system configuration, dialogs, display preferences, and so on, and it
improves performance and tailors the user experience.
This information can be safely removed because the client regenerates any needed
information, returning the client to its state prior to the users initial login.
Removing the cached information is recommended when cached information
degrades client behavior or performance, or causes the client to fail entirely, as
described in the following examples:
• When a plug-in is updated with new or modified code, the cached information
does not match the new or modified plug-in, and the client may not work
properly. Remove the cache to let the rich client refresh the plug-in information.

• When a user opens thousands of items, the current application can become
slow to respond. The next time that user logs on to the rich client, the system
attempts to open the previously accessed items and can take a long time to
complete the startup. Remove the cache to work around this situation.
Note When you are logged on to My Teamcenter as an administrator, the
ClientCache folder is visible in the Home directory. This directory
holds metadata cache. Use the generate_client_meta_cache utility to
regenerate the cache if you work on style sheets.
For information about working with custom style sheets, see the Client
Customization Programmer’s Guide.

The rich client places caches in the workspace and in the program cookies location.
For optimum performance both locations should be local to the machine running the
rich client and should not be on network-mounted disk drives.

PLM00191 J Rich Client Interface Guide 2-157

Chapter 2 Managing the Teamcenter client interface

• Rich client workspace

The primary location for caching both system and application specific
information.
Its location is controlled by either:

$PORTAL_ROOT/configuration/config.ini.
Defined by the osgi.instance.area variable.
osgi.instance.area=@user.home/Teamcenter/RAC/8000.2.0/109101375341

-data directory-path
Specified as a rich client startup command line argument.

• .pcookies
For Teamcenter 2007.x installations, the .pcookies files are placed in the user
$HOME folder.
For subsequent Teamcenter releases, the .pcookies files are placed in the rich
client workspace location.

Removing the entire rich client workspace folder removes problematic cache
information, but it is not the recommended method because it removes useful cached
information that is not causing any problems.
The recommended method of resolving cache issues is to use the -clean rich client
command line argument.
Note Whenever the plug-ins folder is changed, the users’ Teamcenter caches must
be corrected by the -clean rich client command line argument.

Use one of the following methods to correct the users’ Teamcenter caches:
• Edit the rich client start file (TC_ROOT\portal\portal.bat on Windows
systems or TC_ROOT/portal/start_portal on Linux systems) to add -clean
as the first argument on the first line.
Information is automatically regenerated each time the client is run. This
typically adds a second or two to startup time.

• Modify the batch file or shell script that invokes the rich client executable to
use the -clean command line argument. This typically adds a second or two to
startup time.

• Use the -clean argument only after updating the contents of the plug-ins folder.
This provides the quickest rich client start up, but this additional step must run
on each client machine, for each user, each time the plug-ins folder is updated.
Note You can also run the rich client executable with the -clean -initialize
command line arguments to remove old cached information and generate
updated information, ready for the next time the rich client is started.

Beginning with Teamcenter 2007.2 and Teamcenter 8.0, the state of the rich client
registry is stored in workspace folder between sessions.
• Changes in the registry caused by new or updated plug-ins are ignored.

2-158 Rich Client Interface Guide PLM00191 J

 Managing the Teamcenter client interface

• The -clean command line argument does not affect cached registry information
in the workspace.

• The rich client automatically refreshes cached registry information in the

workspace if the consolidated registry XML file is updated after the workspace
registry cache is updated.

• The consolidated registry XML file is stored in the installation location under
$PORTAL_ROOT/registry and can be generated or regenerated by running
the genregxml batch file or shell script.
For more information about using the genregxml batch file or shell script, see
the Client Customization Programmer’s Guide.

Beginning with Teamcenter 9.0, you can disable an individual client from running in
client cache mode without affecting any other clients or disturbing the integrity of the
client cache on the server by setting the TC_SKIP_CLIENT_CACHE environment
variable to any value on the client, for example, TC_SKIP_CLIENT_CACHE=1.
• To disable all clients from running in client cache mode, delete the ClientCache
folder hierarchy and attached datasets. You can also run the Teamcenter
Environment Manager (TEM) or the Business Modeler IDE to update the
installation or to update a template, and then disable the Generate client cache
check box. This deletes the cache automatically.

• If the client is running in client cache mode, the log on is delayed the first time
you log on as the cache is downloaded to the client. During this time, a dialog
box informs the user that the system is synchronizing files for the rich client
installation. When the download is complete, the rich client logon completes.
Subsequent rich client logons when the metadata has not changed take less time.
No dialog box is displayed in this case. The rich client automatically detects when
new information cache is available and downloads the information to the client.

Beginning with Teamcenter 9.1, you can optionally move the metacache folder.
By default, the Shared Client Cache Types files are unzipped to the rich client
workspace. That location is controlled by the config.ini file in the configuration
folder under the rich client installation location. To keep this metacache independent
of the client workspace location, you can set the TC_RAC_METACACHE
environment variable to a location to be used as root for the rich client metacache
location.
Note This location must be local, and the user running the rich client on this
machine must have write privilege to this location.

Working with the FMS server cache (FSC) and FMS client cache (FCC)
The Teamcenter File Management System (FMS) is a file storage, caching,
distribution, and access system. FMS provides global, secure, high performance
and scalable file management.
FMS consists of two primary components:
• FMS server cache (FSC)

PLM00191 J Rich Client Interface Guide 2-159

Chapter 2 Managing the Teamcenter client interface

The FMS server cache (FSC) is the name of the FMS server cache server process.
The FSC is a shared, secure, server level cache. It uploads and downloads files
to other FSCs and to FCCs.

• FMS client cache (FCC)

The FMS client cache (FCC) is the name of the FMS client cache server process.
The FCC provides a private user-level cache, just as Web browsers provide a
read file cache. The FCC provides a high performance cache for both downloaded
and uploaded files. The FCC provides proxy interfaces to client programs and
connectivity to the server caches and volumes.
FCC runs within the Teamcenter client communication system (TCCS) container,
which also contains the TcServerProxy and TcModelEventManager
applications. Starting, stopping, and restarting any of these applications cause
the entire TCCS service (including all applications within the container) to
start, stop, or restart.

For information about using the Teamcenter File Management System, see the
System Administration Guide.
Caution If you are running Teamcenter and an error message indicates a file
management issue, you should consult your Teamcenter administrator
before trying to stop or restart the FCC on your client. Stopping or
restarting the FCC process incorrectly can create additional problems.
For information about administering FCCs, including when and why to
stop or restart an FCC, see the System Administration Guide.

2-160 Rich Client Interface Guide PLM00191 J

Chapter

3 Searching in Teamcenter

Searching in Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Using quick search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Perform a quick search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Using the Search view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Using advanced search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Perform an advanced search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Using search types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Using search forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Using search menus and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Providing search input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Working with search output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Using the Simple Search view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Using simple search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Perform a simple search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Using the Search Results view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Working with search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Navigate the search results and adjust the display setting . . . . . . . . . 3-16
Indented search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Close search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Formatting search results by object properties . . . . . . . . . . . . . . . . . . 3-17
Find properties related to objects in your search results . . . . . . . . 3-17
Compare search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Rename search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Printing search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Print a snapshot of the search results tree . . . . . . . . . . . . . . . . . . 3-19

Using full-text searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

Searching for files using keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Perform a keyword search using the Keyword Search form . . . . . . . . . 3-21
Search for keywords and properties using the Dataset form . . . . . . . . 3-21
Search for keywords and properties using the Dataset Keyword Search
form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Conceptual matching and exact matching . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Boolean operators and bracketed expressions in keyword searches . . . . . . 3-23
Proximity searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Exact phrase searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Check the indexing status of objects and manually update the search
index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Batch indexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

PLM00191 J Rich Client Interface Guide

 Combining full-text search with metadata queries . . . . . . . . . . . . . . . . . . . . . 3-26

My Saved Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

Perform a saved search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Customize saved searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Share saved searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

Search techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

Using wildcard characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Examples of searches using wildcard characters . . . . . . . . . . . . . . . . . 3-29
Using fuzzy search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Using synonym search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Searching with date and time criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Use values from table rows or columns as search criteria in a data pane. . . 3-30
Select multiple values from lists as search criteria . . . . . . . . . . . . . . . . . . 3-31
Searching for datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Finding imported PLM XML data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Searching using localized strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

Using search pane buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

Changing a search in a data pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Change your search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Refresh a search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Clear the search form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Saving searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Save search results to your My Saved Searches folder . . . . . . . . . . . . . 3-35
Save search results to a subfolder of My Saved Searches . . . . . . . . . . . 3-35
Save search results to a subfolder of My Saved Searches in a data
pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

Using search pane tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....... . 3-36

Lock the search pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....... . 3-36
View search criteria definitions . . . . . . . . . . . . . . . . . . . . . . . ....... . 3-37
Changing search criteria definition . . . . . . . . . . . . . . . . . . . . . ....... . 3-37
Change the definition of search criteria . . . . . . . . . . . . . . . ....... . 3-38
Create a user or group preference to override a saved query revision
rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....... . 3-39
Using extended multi-application searches . . . . . . . . . . . . . . . ....... . 3-39
Performing ad hoc Classification searches . . . . . . . . . . . . . ....... . 3-39
Create an ad hoc Classification search . . . . . . . . . . . . . . . . ....... . 3-39
Search for data using Classification attributes . . . . . . . . . . ....... . 3-41
Define search criteria using multiple Classification classes . ....... . 3-42
Saved queries on classification attributes . . . . . . . . . . . . . ....... . 3-42
Using target list filtering in searches . . . . . . . . . . . . . . . . ....... . 3-42
Apply target list filtering criteria to your search . . . . . . . . . ....... . 3-42
Setting search options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....... . 3-44
Working with search options . . . . . . . . . . . . . . . . . . . . . . ....... . 3-44
Working with favorite search options . . . . . . . . . . . . . . . . ....... . 3-46
Using the remote search option . . . . . . . . . . . . . . . . . . . . . ....... . 3-46
Using sort search options . . . . . . . . . . . . . . . . . . . . . . . . . ....... . 3-47

Creating property finder formatter (PFF) objects . . . . . . . . . . . . . . . . . . . . . . 3-47

Create a property finder formatter (PFF) object . . . . . . . . . . . . . . . . . . . . 3-47

Rich Client Interface Guide PLM00191 J

 Where-used and where-referenced searches . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
Where-referenced searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Perform a graphical where-referenced search . . . . . . . . . . . . . . . . . . . 3-50
Perform a where-referenced search using the Referencers print
wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Where-used searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
Perform a where-used search to display a graphical result . . . . . . . . . 3-52
Perform a where-used search to create a text or HTML report . . . . . . . 3-53

PLM00191 J Rich Client Interface Guide

Chapter

3 Searching in Teamcenter

Searching in Teamcenter
The search functionality lets you find data in the Teamcenter database and,
optionally in a related Autonomy index search engine database.
Note You can set search options such as case sensitivity, dataset version retrieval,
classification hierarchy, wildcard characters, multiple entries, escape
characters, default searches, and search locale.
For information about search options, see Setting search options.

My Teamcenter in the rich client provides the following search mechanisms:

• The Search box, at the top of the navigation pane and in the Getting Started
application, lets you perform a quick search and display results in a Quick Open
Results dialog box.

The quick search is based on a single criterion, such as item ID, keyword, item
name, or dataset name, which you select from the menu. You can also select
Advanced to display the Search view.

• The rich client Search view and Simple Search view display results in a
Search Results view.
o The Search view lets you use queries created in the Query Builder
application to search Teamcenter databases for metadata and full-text
search indexes.

o The Simple Search view, lets you create searches based on business
object property values.
Note Lists of values let you to use a search capability with the asterisk (*)
wildcard character to limit the available selections.
For example, in a General search you can search for alt* in List of
Values dialog box associated with the Type attribute. This returns
only values that begin with alt, such as AltIDItemRevision and
AltIDItemRevisionMaster.

Several rich client applications provide additional search capabilities. Procedures for
performing application-specific searches are provided in the appropriate guides.

PLM00191 J Rich Client Interface Guide 3-1

Chapter 3 Searching in Teamcenter

Using quick search

Use the quick Search input box, Perform Search button, and menu

at the top of the navigation pane to locate objects

in the Teamcenter database. A quick search can be performed based on item ID or
other search criteria listed in the quick Search menu.
Tip You can use wildcard characters such as * and ? in the value you enter in the
Search input box for your search criteria.

• Item ID
Type an item ID to search the Teamcenter database for item ID attributes.

• Keyword Search
Type a keyword to search indexed classes for attributes and indexed class
content.

• Item Name
Type an item name to search the Teamcenter database for all item name
attributes.

• Dataset Name
Type a dataset name to search the Teamcenter database for all dataset name
attributes.

• Advanced
Access the advanced search capabilities and predefined search forms.

For more information about adding quick search items, the administrator should see
the Client Customization Programmer’s Guide.

Perform a quick search

1. Locate the quick Search input box and Perform Search button and menu

at the top of the navigation pane.

2. Click the menu icon and select a search type.

Note Item ID is the default search type.

3. Type the appropriate value for your search criteria in the Search box.
Note You can use wildcard characters such as * and ? in the value you enter in
the Search input box for your search criteria.

4. Click Perform Search to execute the search.

The Quick Open Results dialog box appears showing a list of objects that match
the specified criteria.

3-2 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Note If you do not find the object you seek using the quick search, click
Cancel. You can use advanced search to access predefined search forms
with additional search criteria.
For more information about advanced search, see Using advanced search.

5. In the Quick Open Results dialog box, you can either double-click an object to
open it or select an object in the list and click the Open button.
The object is retrieved and opened in a My Teamcenter tri-pane view.

Using the Search view

Use the Search view to enter criteria and execute a search.
The Search view, which provides access to search functionality and a wide range
of predefined search criteria queries, has a standard tab, a toolbar with options
and a menu, a title, and a criteria area.

PLM00191 J Rich Client Interface Guide 3-3

Chapter 3 Searching in Teamcenter

1 Search view Contains the following options:

toolbar
• Executes the search and displays the results in the
search result view

• Change search from search history

• Select a Search

• Re-execute search. Show results in currently open

search view pane

• Clear all search fields

• Add Search to My Saved Searches

• Organize My Saved Searches

• Sort

• Menu
o Lock Search
Locks the current search criteria pane when you
open an executed query by switching between
search entries in the History area in the navigation
pane.

o View Search Criteria Definition

Lets you view current search criteria in a query
clause format.

o Change Search Criteria Definition

Lets administrators modify query criteria.

o Extended Multi-Application Search

Lets you perform advanced searches spanning
multiple applications. For example, you can run a
Classification search with multiple applications in
the target list.
For more information about searches spanning
multiple applications, see Using extended
multi-application searches.

o Preferences
Launch the preferences dialog box.
Note This accesses the same settings as the
Window®Preferences menu command.

3-4 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

2 Search title Indicates the name of the current search.

3 Search criteria Contains input boxes and lists of values for search criteria.
Note Some Teamcenter-provided saved queries include
Current Task criteria to search the Process
Stage List (process_stage_list) attribute of
the WorkspaceObject business object. In this
case, the current task examines all complete and
uncompleted tasks of the workflow associated with
the objects to search, not the current workflow
step.

Using advanced search

Advanced search lets you select a search form that includes multiple search criteria
relevant to the type of information or object being sought.
Use one of the following methods to access advanced search:
• Select Advanced from the quick Search menu at the top of the navigation pane.

• Click the Search button on the Teamcenter toolbar.

For information about search criteria, see Changing search criteria definition.
Note The advanced search buttons let you change, rerun, or save a search, and
clear the search form contents. You can also use search tools to lock a search
or to view or change criteria definitions; the content of a search form can be
modified by privileged users.

The advanced search results are shown in tree format or thumbnail format.
Note You must enable thumbnail functionality to view the thumbnail format.
For more information about enabling thumbnails, see Getting Started with
Document Management.

In some applications, results are displayed in the Folders pane.

• The name on the search tab matches the name of the search form.

• If you perform multiple queries using the same form, a number is added to the
name on subsequent tabs.

• You can rename search panes to make them easier to find and use.
For more information about renaming, see Rename search results.

PLM00191 J Rich Client Interface Guide 3-5

Chapter 3 Searching in Teamcenter

Note You must enter data in at least one field of the search form.
For searches that do not require user input the search pane displays the
following message:
This query requires no user interaction.
Please press the execute query button to perform this query.

You can confirm that a search meets your needs by choosing View Search
Criteria Definition from the Search view menu . The Query Detail dialog
box appears showing the definition of the search criteria for the search type
currently selected.
For more information about search criteria definition, see View search
criteria definitions.

Perform an advanced search

1. Click Search on the toolbar or select Advanced from the search menu at the top
of the navigation pane.
The Search pane appears showing the default search name and description
followed by the search criteria form.
Note The software ships with Item ID selected as the default search. The Item
ID search form has only the Item ID box for criteria.

2. (Optional) On the Search pane toolbar, click to select a search from the
list of search types.
The search form with the criteria for the selected type appears in the Search
pane.

3. (Optional) Click to clear the content of all boxes on the search form.

4. Type the values for the search criteria in the boxes on the search form.
Tip You can use wildcard characters such as * and ? in the value you enter
for your search criteria.

5. Click to perform the search.

Tip The Progress Information dialog box appears showing the progress of
the search. You can click the Cancel button on this dialog box to stop
the search before the processing is complete.

Results appear in the Search Results view.

For more information about using the Search view, see Using the Search view.
For more information about using the Search Results view, see Using the Search
Results view.
For more information about using the Search pane in My Teamcenter 2007, see
Using search pane buttons.

3-6 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Using search types

A search in Teamcenter involves selecting a search type, which in turn specifies
criteria for a database query and distinguishes the databases to be queried. For
example, the following search types produce different query behavior:
• An Item ID search queries the Teamcenter database for the specified item ID.

• An Item Name search queries the Teamcenter database for the specified item
name.

• A Keyword Search queries only indexed classes for attribute and full-text
retrieval using a search engine index database. The indexing search engine is an
optional, frequently installed feature.

• A Dataset Name search queries the Teamcenter database for a dataset name.

• A Dataset Keyword Search search queries the index search engine database for
dataset metadata and dataset files.

• A Dataset search queries the Teamcenter database for attributes and the index
search engine database for dataset content.
Note Other types of searches may be available, depending on your available
applications and the information desired.
For example, where-used and where-referenced searches are available in the
My Teamcenter application Impact Analysis view.
• Where-used searches identify assemblies that contain an item or item
revision.

• Where-referenced searches determine which objects in the database

reference a selected object.

Using search forms

You search for data in the database using predefined search query forms that target
specific types of information for retrieval.
• Standard search forms are delivered as part of your Teamcenter installation,
enabling you to perform basic searches both in your local database and in remote
databases corresponding to Multi-Site Collaboration sites.

• The quick Search box, at the top of the navigation pane, lets you use a single
value or text string to search for objects based on the search type you select
from the quick Search menu.
When the search succeeds and returns more than one object, the Quick Open
Results dialog box appears and you can select an object to open.
Note Shortcut context-menus are not supported in the Quick Open Results
dialog box.

• Advanced search is accessed from the Search button on the toolbar or by

selecting Advanced from the quick Search menu at the top of the navigation
pane.

PLM00191 J Rich Client Interface Guide 3-7

Chapter 3 Searching in Teamcenter

The advanced search functionality lets you find database objects and indexed
data using predefined search forms.
Note The advanced search results appear in the Search Results view, which
does support shortcut menus.

• Click the Select a Search button on the advanced Search view to display the
Change Search dialog box. Use this dialog box to select the search form you
want to use for your search criteria from a list of predefined searches.

• The My Saved Searches container located under Quick Links in the navigation
pane can be used to access search criteria you saved from a previously executed
search.

o Click the expand button to select and rerun a saved search.

o Click My Saved Searches to customize your saved searches by deleting,

renaming, or reordering the saved searches.

Using search menus and options

Using the Search and Search Results menu you can access the following search
features.
• Lock Search
Lock the search pane so the values in the search criteria form cannot be
overwritten when you select a new search or execute a saved search.

• View Search Criteria Definition

View the definition of the search criteria for the selected search form.
Note If you are logged on as an administrator, the Change Search Criteria
Definition option is also available. Administrators can use this option to
adjust the definition of the search criteria for the selected search.

• Extended Multi-Application Search

Access additional search features:

o Adhoc Classification Query

Define search criteria related to attributes of classification classes.

o Target List
Select objects from other Teamcenter applications, active workflow processes,
the clipboard, or from the results of other searches to use as search filters.

• Preferences
Set search options and preferences. Many of the same search options and
preferences can be accessed by choosing Edit®Options from the Teamcenter
menu bar and selecting Search.

3-8 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Providing search input

You can use the following as search input:

• Multiple values in search criteria boxes.

• The contents of table columns or rows.

• Lists of objects derived from other applications or from the results of a search.

• Wildcard characters and limits on the number of results that are loaded.

• Search definitions modified by advanced editing.

• Keywords for full-text searches on dataset files, if the search engine is installed
and configured at your site.

Working with search output

You can:
• Print search results.

• Lock the search pane to view results panes without overwriting search criteria.

• Work with objects in search results panes that persist from session to session.

• Rename and save search criteria to My Saved Searches or another folder.

• Compare results to the contents of your Home folder, My Worklist view, or to

other recent search results.

• Use the property finder formatter (PFF) to view additional data related to the
objects listed in the search results.

Using the Simple Search view

Use the Simple Search view to create searches based on business object property
values.

PLM00191 J Rich Client Interface Guide 3-9

Chapter 3 Searching in Teamcenter
1 Business Object
Type box
2 Select Property list
3 Edit Clause section
3-10 Rich Client Interface Guide
Enter a business object type. The menu lists
favorite types. This box accepts any valid business
object type.
Select a property. The available properties change
when you change the selected business object type.
For the selected property, specify an operator and
a value. The edit clause is added to the selected
search criteria, and you can select another property
to create another edit clause.
Note You can click the clause connector to change
AND to OR, or vice versa.
PLM00191 J
 Searching in Teamcenter

4 View toolbar The Simple Search view toolbar options let you:

• Execute the search.

• Select a business object type, beyond what is

provided by the Business Object Type list.

• Re-execute the search.

• Clear the search criteria values while

retaining the criteria.

• Display the Preferences (Filtered) dialog

box.
This dialog box lets you set query and wildcard
options, delimiting and escape characters,
and result display options. You also use this
menu to set the default business object type
and the list of favorite business object types.
Administrators can set the site-wide list of
displayed business types.
5 Selected search Start the search, change the clause order, or remove
criteria buttons clauses.

PLM00191 J Rich Client Interface Guide 3-11

Chapter 3 Searching in Teamcenter

Using simple search

The rich client Simple Search view lets you create business object searches based
on one or more property values. You first select the object type, and then build a
search by selecting properties and specifying criteria.
• Choose properties to build search criteria.
You can use attribute properties and typed reference properties, but not run-time
properties, relation properties, or compound properties.

• Business objects that are available to be searched are limited to

WorkspaceObject and its subtypes, but typed reference properties can point to
any type of business objects.
Note To retrieve objects when WorkspaceObject is selected as the business
object type, you must select the Enable the Hierarchical Type Search box
under Query Options in the Preferences (Filtered) dialog box Search
pane. This finds all types that inherit attributes from WorkspaceObject.
To set search preferences, use the Simple Search view menu bar
Preferences command to display the Preferences (Filtered) dialog box.

• The scope of the search is limited to the local Teamcenter database.

• You can execute a simple search, but it cannot be saved or reused by other users.

• Ad hoc and classification searches are not supported for business object searches.

• The search results are displayed in the Search Results view, and users can
refresh, compare, save, and assign to project the results.

• Current search preferences are applied to the simple search being executed.
Note To set search preferences, use the Simple Search view menu bar
Preferences command to display the Preferences (Filtered) dialog
box.

• Preferences can be created to support configuration of simple search:

o Default_Business_Object_To_Search
Specifies the default business object selected when the Simple Search view
is first opened.
This is the same as the Default Business Object Type in the Preferences
dialog box for Simple Search.

o Favorite_Business_Objects_To_Search
Specifies favorite business object types.

o Searchable_Business_Objects
Filters the business object types shown for the entire site, specified groups,
or roles. This preference is used by administrators.

3-12 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Note
The Simple Search view is available from the toolbar in the rich
client My Teamcenter perspective, and in other perspectives through
the Window®Show View®Other®Teamcenter®Simple Search menu
command.
The Simple Search functionality is not available in the thin client.

Perform a simple search

Use the Simple Search view to find objects in Teamcenter based on business object
properties.

1. In My Teamcenter, click Simple Search .

You can also choose Window®Show View®Other®Teamcenter®Simple Search
or, if it is present, Window®Show View®Simple Search.
The Simple Search view is displayed.

2. Select or enter a business object type.

You can also use the Select a Business Object Type To Search®More menu
command to select a type in the Select Business Object Type dialog box.

3. Select a property and choose an operator and a value for the edit clause.
You can repeat this step as many times as needed to create the search criteria.

4. Click Search.

The Search Results view is displayed with objects that meet the specified criteria.
Note If the Default_Business_Object_To_Search preference is not defined or
has no values, the Select Property list is displayed as a very narrow box.
• For immediate resolution of this situation, you can drag the right
border of the Select Property box to the right to display the attribute
list correctly.

• For permanent resolution of this situation, specify one or more values for
the Default_Business_Object_To_Search preference.

Using the Search Results view

Use the Search Results view to examine the list of objects that satisfy the search
criteria.

PLM00191 J Rich Client Interface Guide 3-13

Chapter 3 Searching in Teamcenter

1 Search Contains the following options:

Results view
toolbar • Rerun current search

• Show Previous Searches

• Export Objects to Excel

• Select PFF

• Refresh property formatter search

• Edit property formatter

• Run Adhoc from Property Formatter

• View Menu→Options
2 Search title Indicates the name of the current search and the number
of items returned.
3 Search Contains the following options:
Results view
page toolbar • Previous page

• Next page

• Load all

• Collapse to the root object

• Expand the selected object(s)

• Expands the selected object(s) to all levels

• Show
Note The Show option is available only when
thumbnails are enabled.

3-14 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

If thumbnails are enabled, options are

Tree, to display the standard tree view, and
Thumbnail, to display Small, Medium, and
Large thumbnail graphics.
For more information about enabling
thumbnails, see Getting Started with
Document Management.
4 Search results Lists objects that meet search criteria.

Working with search results

In My Teamcenter, search results appear in the Search Results view.

Each time you execute a search, the results of the latest search appear in the Search
Results view, replacing the results of the previous search. Right-click the search
name at the top of the list of search results to access the shortcut menu.

PLM00191 J Rich Client Interface Guide 3-15

Chapter 3 Searching in Teamcenter

From this menu, you can perform various actions on the search results including
assigning the objects to a project and comparing the results to those of another
search.

Navigate the search results and adjust the display setting

When you run a search, the total number of objects found and the relative position of
the displayed objects within that total appears at the top of the search results.

Item ID - ( 1 ~ 30 / 127 ) Number of items

Navigational buttons

Item ID (1) Search results (version)

standard_thread_inch
cap_screw_cb_inch

• You can see the number of items displayed (for example, 1 ~ 30) and the total
number of items found (for example, 127).

• You can move back and forth through the results by clicking the navigational
buttons and load all buttons located in the search results pane.

• You can see the search results version (for example, 1). When searches are run
multiple times, the version number distinguishes each result.

• To set the number of objects loaded in a search results pane, choose

Edit®Options and select Search. Click the General Options tab and adjust the
gauge for the Set Loading Page Size option.
Note The Set Loading Page Size option can also be accessed by selecting
Preferences from the search menu.

Indented search results

By default, search results are returned in a flat list from which you can expand
objects to navigate down to related items.

Admin – Objects By Status (1)

SM3061 – Bolt/A;1 – Bolt
SM3061 – Hub/A;1 – Hub
SM2720 – Comp2_Attachments/A;1 – Comp
000284/A;1 – 284
000285/A;1 – 285
SM3061 – Tyre/A;1 –Tyre
SM2720–Comp2_Variants/A;1 – Comp

When you select a search created with the Show Indented Results check box
selected in Query Builder, a Show Indented Results check box appears at the bottom
of the search criteria form.

3-16 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

• You can select or clear the Show Indented Results check box, depending on
which view you prefer, then execute the search.

• The indented view shows only the components related to the search criteria
in the search results.

Admin – Objects By Status (3)

000281/A;1 – item 281
Pending
SM3061– Tyre/A;1 –Tyre
Pending
000285/A;1 – 285
TCM Released
SM2720 – Comp2_Variants/A;1 – Comp
TCM Released
000282/A;1 – 282

• To view the related items for an object in the indented search results, select the
object in the search results list and open the Details view.

Close search results

Note Search results that have not been saved to a folder are lost when you close
the pane.

1. Right-click the search name at the top of the list of search results.
The Explorer Popup Menu appears.

2. Select Close to close the current search or select Close All to close all open
searches.

Formatting search results by object properties

A set of property finder formatter (PFF) objects corresponding to the basic search
types are delivered as part of the standard Teamcenter installation. PFF objects are
similar to query definitions but they navigate the relationships in the object schema
to locate the properties of the objects returned in the search results. The properties
for the objects listed in the search results are then displayed in the defined format.
Click the Select PFF button in the Search Results view to access the property finder
formatter objects available to you.

Find properties related to objects in your search results

1. Execute the applicable search to display the desired search results.

2. Click the Select PFF button in the Search Results view.

3. Select a property formatter from the list.

4. Click Refresh.

PLM00191 J Rich Client Interface Guide 3-17

Chapter 3 Searching in Teamcenter

Teamcenter populates the display data table with the properties for the objects
in the search results list, according to the definition of the formatter.
Note If you modify or refresh the search, you must also refresh the display
data table.

Compare search results

Search results can be compared to the results of other searches.
1. Execute the applicable search to display the search results list you want to
compare.

2. Right-click the search name at the top of the list of search results.
The Explorer Popup Menu appears.

3. Select Compare To to access a list of open searches.

• Select an open item from the list or, if the list is extensive, from the expanded
list under the More option.

• If the number of open items is difficult to navigate from the menu list, select
Compare to Search Result List.
The Compare To dialog box appears. You can use this dialog box to scroll
through the open items and make a selection.

4. Select a search name from the Compare To list or dialog box.

The Compare Report dialog box appears showing the contents of the selected
search results. Differences between the components in the selected search
results lists are highlighted in green, identical objects have a transparent
background, and the object currently selected is highlighted in blue.

3-18 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

5. (Optional) Browse the differences using the navigation buttons at the lower-right
corner of each pane. This can be useful when comparing components containing
a large number of objects.

6. (Optional) Select the Differences check box to display only the differences
between the components.

7. Click Close to exit the dialog box.

Rename search results

If you plan to keep a search open in your My Teamcenter window for an extended
period of time, or if you have multiple queries open, renaming the search results is a
convenient way to make your My Teamcenter window more manageable.
1. Right-click the search name at the top of the list of search results.
The Explorer Popup Menu appears.

2. Select Rename from the menu.

3. Type a new name for the search results.

4. Press Enter.
The name of the search is changed to reflect the new name.

Printing search results

You can:
• Print a snapshot of the search results tree.

• Print the properties of an object in the search results tree.

Print a snapshot of the search results tree

1. Right-click the search name at the top of the list of search results.
The Explorer Popup Menu appears.

2. Select Print.
The Print dialog box appears.

3. (Optional) Modify the print options and properties.

4. Click OK.
The list of objects in the search results tree is printed. If the tree displays all of
the results, all results are printed. If the tree only displays one page of results,
only that page is printed.

Using full-text searches

When the Autonomy search engine is installed and configured at your site, you can
perform full-text searches on dataset files.

PLM00191 J Rich Client Interface Guide 3-19

Chapter 3 Searching in Teamcenter

Full-text searches can be combined with searches for metadata, allowing you to
search for datasets by attribute value as well as searching dataset files by keyword.
For example, you can search for all documents containing the keyword cat that
belong to owning user jsmith and have been modified after December 1, 2007.

• Wildcards can be used when performing keyword searches; however, partial

keywords without wildcard characters cannot be used.

• If realtime indexing is enabled, the full-text search index is updated

automatically whenever objects or their named references are saved, modified,
or deleted.
Note Realtime indexing is enabled using the TC_fts_real_time_indexing
preference. Objects subject to realtime indexing are specified by the
TC_fts_indexed_types preference.
For more information about managing options and preferences, see
Getting Started with Teamcenter.
An administrator can use the build_fts_index utility to build keyword
indexes for the Autonomy search engine on an object-by-object basis for
both the properties of dataset objects and the contents of dataset files.

For more information about configuring full-text search, see the Application
Administration Guide.
For information about installing the full-text search engine as a Teamcenter feature,
see the appropriate server installation guide (for Windows or UNIX/Linux) and the
Teamcenter Environment Manager Help.
For information about working with preferences, see the Preferences and
Environment Variables Reference.
For information about using utilities, see the Utilities Reference.

Searching for files using keywords

Full-text searches let you search for objects based on keywords contained in the files.
Keyword searches can be performed using the Keyword Search, Dataset, or Dataset
Keyword Search form delivered as part of your Teamcenter installation.
The Dataset query form combines object properties (metadata) and full-text keyword
search, allowing you to search for properties of the dataset objects in conjunction
with keywords in the associated files. For example, you could search for files
containing the word brake that are owned by user jsmith and were modified after
01-Jan-2007. This query searches for the properties in the Teamcenter database.
The Dataset Keyword Search also combines object properties and full-text keyword
search; however, this query retrieves data from the full-text search index. If you
specify only a keyword, the Dataset and Dataset Keyword Search queries perform
identically.
Note The Keyword boxes in the query forms no longer accept search criteria in
the PropertyValue:PropertyName format.

3-20 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Perform a keyword search using the Keyword Search form

1. Click Search on the toolbar.
The Search pane appears.

2. Click the Select a Search button at the top of the search pane.

3. Select Keyword Search from the list of System Defined Searches.

The search form appears in the search pane.

4. Enter one or more keywords in the Keywords box. Boolean operators, bracketed
expressions, and partial words combined with wildcards can be used to define
the search parameters.
Note Searches for partial keywords without wildcard characters are not
supported. In addition, the keyword search is not sensitive to type case.

5. Click to execute the query.

The system runs the search and displays the results in the search results pane.

Search for keywords and properties using the Dataset form

1. Click Search on the toolbar.
The Search pane appears.

2. Click the Select a Search button at the top of the search pane.

3. Select Dataset from the list of System Defined Searches.

The search form appears in the search pane.

4. If necessary, click More to display the additional search criteria boxes.

5. Enter one or more keywords in the Keywords box. Boolean operators, bracketed
expressions, and partial words combined with wildcards can be used to define
the search parameters.
Note Searches for partial words without wildcard characters are not
supported. In addition, the keyword search is not sensitive to type case.

6. Define object property parameters for the search, such as the Name, Dataset ID,
Revision, Dataset Type, Description, Owning User, Owning Group, Created
Before date, Created After date, Modified Before date, Modified After date,
Released Before date, Released After date, Release Status or Current Task.

7. Click to execute the query.

The system runs the search and displays the results in the search results pane.

Search for keywords and properties using the Dataset Keyword Search form
1. Click Search in the toolbar.
The Search pane appears.

PLM00191 J Rich Client Interface Guide 3-21

Chapter 3 Searching in Teamcenter

2. Click the Select a Search button at the top of the search pane.

3. Select Dataset Keyword Search from the list of System Defined Searches.
The search form appears in the search pane.

4. Enter one or more keywords in the Keyword box. Boolean operators, bracketed
expressions, and partial words combined with wildcards can be used to define
the search parameters.
Note Searches for partial words without wildcard characters are not
supported. In addition, the keyword search is not sensitive to type case.

5. Define object property parameters for the search, such as Name, Dataset Type,
Description, Owning User, Owning Group, Created Before date, Created
After date, Modified Before date, Modified After date, Released Before date,
Released After date, or Release Status.
Note By default, the Dataset Keyword Search query combines the clauses
using the AND Boolean rule. You can modify the query definition to
use the OR rule.
For more information about modifying query definitions, see the Query
Builder Guide.

6. Click to execute the query.

The system runs the search and displays the results in the search results pane.

Conceptual matching and exact matching

Full-text search can use advanced pattern-matching technology to conceptually
match the queries that consist of a single keyword.
• If a keyword is entered without quotation marks, the system tries to determine
the stem of the keyword, and then finds documents that contain words that
have the same stem as the keyword.
For example, if you enter the word lovely without quotation marks, the full-text
search engine matches this word conceptually by finding the word stem, love,
and the search engine finds documents that contain words that also have the
word as a stem, such as lovely, love, loved, loving.

• When a keyword is entered in quotation marks, the system tries to find only
documents that contain exact matches of a keyword.
For example, if you enter the word "lovely", including the quotation marks, the
full-text search engine does not try to determine the word stem, but does try to
find documents that contain the word lovely.

3-22 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Note Conceptual matching searches, using stems, and exact matching searches,
using quotation marks, support only the following:
• Keyword search

• Keywords box in Dataset Keyword search

• Dataset search

Boolean operators and bracketed expressions in keyword searches

Boolean operators are available for use in searches.

Operator Description
AND Ensures that both terms are matched in every objects. For
example:
software AND hardware
Returns all documents that contain both software and hardware.
OR Broadens your search by locating a document containing any of
the terms connected by the OR operator. For example:
processor OR SpecDocument
Returns all documents that contain either processor or
SpecDocument.
NOT A term following the NOT operator is excluded from the
returned results. For example:
bolt NOT nut
Returns items that contain bolt but not nut.
XOR The logical exclusive XOR specifies that only one of the terms is
permitted to appear in returned results. For example:
software XOR hardwareQuery
Returns items containing either the term software or the term
hardware, but not both.

Note Bracketed expressions are evaluated left-to-right and can be nested. For
example, the following input query text:
(cap AND Document) OR ( cap AND SpecDocument)
Returns all documents that contain the following:
cap and Document
cap and SpecDocument

Results vary depending on how you use Boolean operators and bracketed expressions
to define search parameters.

PLM00191 J Rich Client Interface Guide 3-23

Chapter 3 Searching in Teamcenter

Keyword entry Search results

brake Documents containing the word brake.
brake AND caliper Documents containing both the words brake and
caliper.
(brake AND caliper) OR Documents that contain both brake and caliper or
(nut AND bolt) those that contain both nut and bolt.

Note Boolean operators must be entered using uppercase letters.

Proximity searches
Proximity searches let you give words that appear close together in the search string
a higher weighting than the same words located anywhere within the text.
You can apply proximity operators to words, exact phrases, or other Boolean
expressions to execute a proximity search.

Operator Description Notes

NEARnn Returns documents This query returns only documents in which
in which the second the term brake is within two words of
term is within nn the term caliper. Therefore, documents
words of the first that contain brakes and calipers and
term. documents that contain calipers and
brakes are returned, while documents that
For example: contain brakes do not require calipers
brake NEAR2 are not returned, because the words are not
caliper in close enough proximity to each other.
DNEARnn Directed NEAR. This query returns only documents in
Returns only which the term caliper follows the term
documents in which brake, and is within two words of the term
the second term is brake. This means that documents that
within nn words of contain brakes and calipers are returned,
the first term, in the while documents that contain calipers
specified order. and brakes or brakes do not require
calipers are not returned.
BEFORE Returns only This query returns only documents in which
documents in the term brake appears after the term
which the first term caliper.
precedes the second
term.
AFTER Returns only This query returns only documents in which
documents in which the term brake appears after the term
the first term caliper.
appears after the
second one.

3-24 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Exact phrase searches

You can search for an exact phrase by placing quotation marks around the phrase.
For example, include the phrase “brake caliper”, including the quotation marks, in
your search text to return all documents containing that phrase.

Check the indexing status of objects and manually update the search
index
Note This option is available only if full-text search is implemented at your site.

An administrator may:
1. Select the objects in the tree.

2. Choose Tools→Check Index Status.

The Check Index Status dialog box appears showing the current indexing status
for the selected objects. The indexing status may be:

• Updated
Indicates the index for the object is current.

• Not Updated
Indicates the object is not indexed.

• Type Not Supported

Indicates the object is not specified by the TC_fts_indexed_types
preference and is not supported for indexing.

3. In the Check Index Status dialog box, select the objects you want to index.
Note To select the objects, hold the Shift key for adjacent values and the Ctrl
key for nonadjacent values.

4. Click Reindex to run the indexing process for the selected objects.
The system displays indexing errors, if any, and updates the status in the dialog
box.
Note If the full-text search capability is not installed, the system displays a
dialog box with this message: The FTS engine could not be found.

5. Click Close to close the dialog box.

Batch indexing
An administrator can use the build_fts_index utility to create keyword indexes for
the Autonomy search engine on an object-by-object basis. These indexes become part
of the full-text keyword search functionality and can index both the properties of
dataset objects and the contents of dataset files. If a dataset file is not of a document
type supported by Autonomy, the utility can invoke a user-specified filter program to
convert the file to a supported format.

PLM00191 J Rich Client Interface Guide 3-25

Chapter 3 Searching in Teamcenter

For more information about batch indexing, see the Utilities Reference.

Combining full-text search with metadata queries

You can embed a keyword search entry into a saved query on the dataset class and
execute both the metadata query and keyword search in one operation.
Combining full-text search with metadata queries allows you to define a query, for
example, that searches for files containing the word brake that are owned by user
jsmith and were modified after 01-Jan-2004.
This functionality is included in the Dataset standard query form. For information
about using this feature, see Searching for files using keywords.
Custom queries combining full-text search and metadata search can be defined by
your Teamcenter administrator. For more information, see the Query Builder Guide.
Alternatively, the metadata of dataset objects can be indexed together with the
associated data files. This allows you to use Autonomy to perform both keyword
search and metadata search.

My Saved Searches
Searches saved from the Search pane are listed in the My Saved Searches menu in
the Quick Links section on the navigation pane.
They are also listed in the My Saved Searches folder in the Change Search dialog
box.

Perform a saved search

1. Expand the My Saved Searches menu in the Quick Links section in the
navigation pane.

2. Select a saved search.

The system displays the criteria in the Search pane and the results in the
Folders and Data panes.
The search criteria for the saved search appears in the Search pane. The results
of the search appear in the Search Results view.

For information about saving searches, see Save search results to your My Saved
Searches folder.

Customize saved searches

1. Click the My Saved Searches text in the Quick Links section on the navigation
pane.
The Customize My Saved Searches dialog box appears.

2. Select a saved search from the list of saved searches.

3-26 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

3. Use the buttons to delete , rename , or reorder the saved searches.

4. Click Apply to accept your changes; OK to accept your changes and close the
dialog box; or Cancel to discard changes and close the dialog box.

For information about saving searches, see Save search results to your My Saved
Searches folder.

Share saved searches

You can:
• Create new shared searches.

• Share existing saved searches with other users.

• Use saved searches that others users have shared.

Note Saved searches that include classification attributes are not supported in
the thin client.

1. Click the Search button on the My Teamcenter toolbar in the rich client.

2. In the Search view, click Select a Search .

The Change Search dialog box is displayed.

3. Choose a search type and provide search criteria, and then click Perform Search
.

4. Click Add Search to My Saved Searches .

The system displays the Add Search to My Saved Searches dialog box.

5. Type a name for the search.

6. Click Is Shared to create a shared search.

7. Click Create In to expand the dialog box to display existing saved searches
and folders.
In the expanded area, you can create new folders, rename or delete searches or
folders, or specify access privileges for searches.
For information about access privileges, see the My Teamcenter Guide.

8. Click OK to create the shared search.

Note By default, saved searches are private. You must select Is Shared in the
Add Search to My Saved Searches dialog box for others to view your saved
searches.

PLM00191 J Rich Client Interface Guide 3-27

Chapter 3 Searching in Teamcenter

Search techniques
Using wildcards correctly, incorporating keywords in searches, and carefully crafting
queries can increase your success.
Specific searches in some applications require additional setup.
For example, to search alternate ID values in Structure Manager, use an Item or Item
Revision search. To display alternate ID values in Structure Manager, you must edit
a preference to add the column to the BOM line display table; an administrator can
use the Business Modeler IDE to add a title for the new column.
For information about making product structure searches, see the Structure
Manager Guide.
For information about using the Structure Search view, see the Manufacturing
Process Planner Guide or the Multi-Structure Manager Guide.

Using wildcard characters

Wildcard characters, such as * and ?, broaden your searches by allowing you to
match a single character or multiple characters occupying specific positions in a
search string.
Each box in the search form corresponds to an attribute of the search class. This
attribute can be a string, date, integer, or logical type. Date, integer, and logical type
search boxes do not support wildcard characters. Wildcard characters can only be
used in boxes corresponding to string attributes.
* The asterisk wildcard searches for the root of a word followed
by one or more characters.
For example, a search for communicat* returns items
containing terms such as communicate, communicates,
communicated, communication, communications, and
communicating.
? The question mark wildcard searches for the root of a word
with the question mark as a substitute for any other character.
For example, a search for Anders?n returns items that contain
terms such as anderson, andersun, andersen, and andersin.
Three wildcard character sets (SQL Style, UNIX Style, and Windows Style) are
available and can be set using the Preferences dialog box accessed from the Search
view menu Preferences command.
Once the wildcard style has been set, it applies to all saved searches; however, it
does not affect Classification searches.
For more information, see Setting search options.
To enhance local metadata searches, your administrator can set the
search_automatic_wildcard site preference to automatically add the asterisk (*)
character as a prefix, suffix, or both for search criteria for all string attributes. This
feature is available in all Teamcenter clients. By default, this feature is turned off.
Note Remote queries, Classification queries, and other specialized searches are
not affected by the search_automatic_wildcard site preference.

3-28 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

The following values are valid for the search_automatic_wildcard site preference:
0 Search criteria are not altered. This is the default value.
1 The asterisk (*) character is added as a suffix.
2 The asterisk (*) character is added as a prefix.
3 The asterisk (*) character is added as both a suffix and a prefix.
Note All other values have the same effect as adding 0.

Examples of searches using wildcard characters

Consider searching for a text dataset named Field Report. To locate this dataset,
you could enter Field* in the Name box and text in the Type box on the search
form. Applying these values would cause the search to return all text type datasets
with names beginning with the characters F, I, E, L, and D. If you know more
details about the object, the search can be restricted further by specifying additional
criteria, such as the owning user or owning group, or the approximate date that the
object was created or modified.
Now consider searching for an item revision when the only thing you know is that
the word model appears in the middle of the item revision name. By entering
*model* in the Name box and ItemRevision in the Type box, the search returns all
item revisions with names containing the letters M, O, D, E, and L.
Note Searching a large database using wildcard characters can return an
unwieldy number of matches, and can also consume considerable time
and potentially tie up system resources, causing your current session to
terminate unexpectedly. Your administrator can define parameters for
wildcard searches to make searches more efficient. When such parameters
are in place, an error message providing information about the parameters
is displayed when input values are invalid. For example:
You must enter at least 3 character(s) before the wildcard character
for item_id

Using fuzzy search

You can use fuzzy search capabilities in dataset keyword searches to find documents
that are not normally found because of typographical errors.
To use fuzzy search, use the DREFUZZY operator with the search term, using the
following syntax:
DREFUZZY(search_term)
For example, DREFUZZY(google) returns items containing terms such as gogle,
goggle, googol, and googel.
Fuzzy search works in the navigation pane Search box, in the rich client Search
view, and in the Getting Started application.

Using synonym search

You can use synonym search to find indexed items in the navigation pane Search
box, in the rich client Search view, and in the Getting Started application.

PLM00191 J Rich Client Interface Guide 3-29

Chapter 3 Searching in Teamcenter

A Teamcenter administrator can configure synonym search to broaden searches.

For example, you can set synonyms for cat to be feline, mouser, and tabby in
English, and also set synonyms for Katzeto be Mietze, Mietzekatze, Mietzekater,
and Kater in German.
To configure synonym search, the administrator must:
• Set the TC_fts_synonym_search site preference to true.

• Create a synonym search text file.

• Configure the Autonomy full-text search engine IDOL server.

For more information about configuring synonym search, see the Application
Administration Guide.

Searching with date and time criteria

Date and time values can be used as search criteria; however, these values must
be entered in the exact format used at your site. The default format for date and
time values is:
15-Jan-1997 15:51
If you do not specify a time, the time is assumed to be 00:00, which corresponds to
12:00 midnight at most sites. Date and time value ranges are frequently used in
search forms. When start and end date and time boxes are used, the end date and
time value must be at least one second later than the start date and time value.
Note You cannot locate objects by specifying exact date and time criteria because
Teamcenter stores precise date and time values in milliseconds.

Use values from table rows or columns as search criteria in a data

pane.
1. Right-click a column header to display the Table Function Menu and set the
copying mode by choosing one of the following commands:
• Enable Row Selection
Row selection lets you select the entire contents of a row, or rows, to copy.

• Enable Column Selection

Column selection lets you select cells within the column to copy.

2. Select the rows or column cells that you want to copy to the search form box.

3. Right-click the column header again, and choose Copy Selected Data→For
Query.
The data is copied to the system clipboard.

4. Right-click in the search box into which you want to paste the selected data and
choose Replace Text or Append Text from the shortcut menu.
The data is pasted into the search form.

3-30 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Select multiple values from lists as search criteria

1. Click the list to display the values.

2. Hold the Shift key (for adjacent values) or the control key (for nonadjacent
values) and select the values from the list.

As you select values, they are displayed in the query field.

Searching for datasets

Siemens PLM Software recommends using the Dataset query (from the Search pane
System Defined Searches list), rather than the General query to search for datasets.
• Using the General query and selecting dataset as the type produces inaccurate
results.

• You can use the General query to search for a dataset, but the type parameter
must be left blank.
This method is not recommended, because initiating a general query without
specifying an item type results in a search of all object types in the database.
This is inefficient and time consuming.

Finding imported PLM XML data

Teamcenter data is usually created and contained in folders, assemblies, and in
other organizational containers that make the data easy to locate. In some cases,
however, you may not know the container involved or there is no container, as may
be the case with data imported from PLM XML files.
A Teamcenter search is a complex query on the database that you generate based
on your input. Your input depends on the type of data you want to find. Search
criteria to find imported data depend on the type of the data being imported, as
illustrated by the following examples:
• When you are importing items and you know the item IDs, you can simply
search on item ID to get imported objects.

• When you import a more complex structure consisting of several items, item
revisions, forms, and BOM lines, and you know the top BOM line ID, you can use
the top BOM line ID to get the top line, and then send that object to Structure
Manager to view the structure. Similar methods can used to get manufacturing
items, generic design elements (GDE), and so on.

• When you import objects such as forms or datasets, you can use search
criteria based on the form or dataset object type. You can, for instance, import
Teamcenter mechatronics process management objects such as signal, GDE, or
connection objects used in complex electromechanical structures, and search
based on either item ID or object type.

• For many objects you can search based on a creation date timestamp with a start
time immediately prior to the import and an end time after the import.
Note You cannot search based on creation date timestamp for occurrences
or other runtime objects.

PLM00191 J Rich Client Interface Guide 3-31

Chapter 3 Searching in Teamcenter

Searching using localized strings

You can use localized names and values as the search criteria.
For example, the objects in the following table have the object_name property
localized. The system has English and German names for the objects.

English Master
Key name German name Type Status locale
1 Wheel Radbaugruppe Item Pending English
Assembly
2 Axle Achse Item Pending English
3 Wheel Rad Item Released English
4 Wheel Radanforderungen Document Released English
Requirements
5 Change EngChange Released English
Wheel
Radänderung
6 New Car Neues Auto Item Pending German
7 New Neuer Item Pending German
Commercial Lastkraftwagen
Truck

For this example, assume Windows-style wildcards are in effect.

Also in this example, Pending and Released are internal status names with
display names in English and German.

• Pending: Needs sign-off (English), Unterzeichnung erforderlich (German)

• Released: Approved for manufacturing (English), Genehmigt für die

Herstellung (German)

For a standard Item search, results are returned based on the search locale.

Search Objects found per key in previous

locale Search criteria table
German Name: Rad* 1, 3, 4
German Name: Neu* 6, 7
German Name: New* None
German Name: *Rad* 3, 4
AND:
Status:*Herstellung*
English Name: Wheel* 1, 3, 4
English Name: New* 6, 7
English Name: Neu* None

3-32 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Search Objects found per key in previous

locale Search criteria table
English Name: *Wheel* 1
AND:
Status: *sign-off*

For information about locales and localized names and values, see the Localization
Guide.
Note When searching using a list of values (LOV) display value, if the internal
value of that given LOV matches a value used at another level of the
hierarchy, a false positive may be returned. For example, a Document
business object is a child of the Item business object, and it has a property
description with an attached LOV value of color. If a user performs a general
search and enters the value rouge, which is the French translation for red,
any business objects that are children of the Item business object that have
a value of red are returned with the search result.
You can avoid this behavior by narrowing down the search on a particular
document type. For example, select type=Document on the search dialog box.

Using search pane buttons

Search pane buttons let you execute, change, rerun, clear, and save a search.

Changing a search in a data pane

Click the Change button in the Search pane to access the Change Search dialog
box.
Search History
This tab lists, in reverse chronological order, your recent searches.

• On the Change Search form, the Advanced button lets you specify how
many searches to remember and lets you clear the search history.

• On the Change Search form, the Change Search button loads the selected
search into the Search pane. You can also double-click the selected search to
load it into the Search pane.

• You can select a search and right-click to display the shortcut menu and copy
the selected search or clear your search history.

My Saved Searches
This tab lists, in a folder view, your saved searches.

• You can select a search and right-click to display the shortcut menu to
rename or delete the selected search, or to create a new folder. The shortcut
menu also lets you paste the search you copied from your search history to
My Saved Searches in the navigation pane.

PLM00191 J Rich Client Interface Guide 3-33

Chapter 3 Searching in Teamcenter

• On the Change Search form, the Change Search button loads the selected
search into the Search pane. You can also double-click the selected search to
load it into the Search pane.

System-defined searches
This tab lists, in alphabetical order, the standard searches defined for use at
your site.

• Many searches are provided with the software. Your administrator can
adjust this list to match the needs at your site.

• The Change Search form Change Search button loads the selected search
into the Search pane. You can also double-click the selected search to load
the search into the Search.

Change your search

1. In the Search pane, click the Select a Search button.

The Change Search dialog box appears.

2. Select a new search from the System Defined Searches or My Saved Searches
categories.

3. Click OK.
The search form with the criteria for the selected search appears in the Search
pane.

Note When you change the search, the content of the currently displayed Search
pane is overwritten to display the form associated with the new search.
To prevent the search criteria from being overwritten, you can choose Lock
Search from the menu in the Search toolbar.

Refresh a search
• Click the Rerun button at the top of the Search pane to refresh queries and
update the search results.

Clear the search form

• Click the Clear button at the top of the Search pane to clear the contents of
all boxes on the search form.

Saving searches
You can save searches to the My Saved Searches folder, or you can create a hierarchy
of subfolders in which to save searches.

3-34 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Note If the Search pane is not open, you can access your saved searches from the
My Saved Searches expand button under Quick Links in the navigation
pane.

Save search results to your My Saved Searches folder

1. In the Search pane, display the desired search form and set the criteria to the
values for the search you want to save.

2. Click to perform the search to verify the criteria values are set accurately for
the intended search results.

3. Click Save at the top of the Search pane.

The Add Search to My Saved Searches dialog box appears.

4. Type a unique name for the search in the Name box.

5. Click OK.
The search is saved and listed in your My Saved Searches folder.

Save search results to a subfolder of My Saved Searches

1. In the Search pane, display the desired search form and set the criteria to the
applicable values for the search you want to save.

2. Click to perform the search to verify the criteria values are set accurately for
the intended search results.

3. Click Save at the top of the Search pane.

The Add Search to My Saved Searches dialog box appears.

4. Type a unique name for the search in the Name box.

5. Click the Create In button.

The Add Search to My Saved Searches dialog box expands to show the saved
searches folders.

6. Select a folder to save the search in or, if you want to create a new folder, select a
folder to create the new folder in and click New Folder.
A new subfolder is created in the selected folder.
With the new subfolder selected, click Rename and type a new name for the
subfolder.

7. Click OK.
The saved search is listed in the subfolder of the My Saved Searches folder
structure on the Change Search dialog box.
The saved search is also listed in the navigation pane under Quick Links in
My Saved Searches.

PLM00191 J Rich Client Interface Guide 3-35

Chapter 3 Searching in Teamcenter

Save search results to a subfolder of My Saved Searches in a data pane

1. In the Search pane, display the desired search form and set the criteria to the
applicable values for the search you want to save.

2. Click to perform the search to verify the criteria values are set accurately for
the intended search results.

3. Click Save at the top of the Search pane.

The Add Search to My Saved Searches dialog box appears.

4. Type a unique name for the search in the Name box.

5. (Optional) To save to a subfolder, select a subfolder from the Created In list.

6. (Optional) To save to a new subfolder, click the More Folders link located on the
Add Search to My Saved Searches dialog box.
The Add Search to My Saved Searches dialog box expands to show the saved
searches folders.

a. Click New Folder.

The New Saved Search Folder dialog box appears.

b. Type a name for the new folder in the Folder Name box.

7. Click OK.
The search is saved and listed in the navigation pane under Quick Links in
My Saved Searches.
If you chose to use a subfolder to save the search, the saved search is also listed
in the subfolder in the My Saved Searches folder structure in the Change
Search dialog box.

Using search pane tools

Using the Search and Search Results menu, you can access tools to:
• Lock searches.

• View search criteria definitions.

Note Administrators can also change search criteria definitions.

• Run extended multi-application searches and define search attributes for

classification data.

• Set search options and preferences.

Lock the search pane

When you change a search in the search pane, the content of the currently displayed
search form is overwritten to display the form associated with the new search.

3-36 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

You can lock the search to prevent the content of the currently displayed search
form from being overwritten:

• Choose Lock Search from the Search menu .

View search criteria definitions

Note Query forms displayed in the Search pane provide an easy way to enter
search criteria, but they intentionally do not display much information about
the construction of the underlying query.
The Query Detail dialog box displays the properties and logical operators
used to construct each search clause and the Boolean rules used to combine
the clauses. These details provide useful troubleshooting information if a
search does not return the expected results.

1. Display the search form you want to examine in the search pane.

2. Choose View Search Criteria Definition from the Search menu .

The Query Detail dialog box appears.
The properties and logical operators used to construct each search clause and
the Boolean rules used to combine the clauses in the search criteria are listed for
the selected search. These details provide useful troubleshooting information if a
search does not return the expected results.

3. Click Close to exit the dialog box.

For information about changing the search criteria definition see Changing search
criteria definition.

Changing search criteria definition

Search criteria in predefined search forms can be customized by administrators
using the query Edit dialog box.
• Teamcenter administrators can access the query Edit dialog box using the Query
Builder application or the Change Search Criteria Definition menu command.

• The Change Search Criteria Definition command is available for administrators

on the search menu .

• You can only work with local queries, unless you are working in a privileged user
account, as determined by your local administrator.

• The query Edit dialog box can also be used to create and save new queries.

• You can override the default revision rule for saved queries (predefined searches).

PLM00191 J Rich Client Interface Guide 3-37

Chapter 3 Searching in Teamcenter

Caution The following queries are implemented based on special codes and should
not be modified or copied:
• _ViewAuditLog

• Checked-Out Objects

• Keyword Search

For example, the Checked-Out Objects query is implemented based

on special codes, in this case, the QRY_RUN_BY_USER_QUERY
enumeration value. Therefore, without writing code, you cannot define
an identical saved query that returns the same results.
For more information about query code, see the Integration Toolkit
Function Reference. (The Integration Toolkit Function Reference is
available only in the Teamcenter HTML Help Collection. It is not
available in the PDF collection.)

Change the definition of search criteria

1. In the Search pane, display the search form for the search type criteria you
want to change.

2. Choose Change Search Criteria Definition from the Search menu

The Edit dialog box appears.
The class, attributes, and search criteria for the selected search are listed in the
dialog box. A new name is automatically assigned to the modified search but
can be overridden.

3. Modify the class, attributes, or criteria.

Note The search class must have at least one own attribute (an attribute not
inheriting from its parent class). Otherwise, the search returns objects
from its parent class, rather than the specified class.
You must change the value in the Name box if you want to create a new
search type.

4. Click Modify to modify the search type, or click Create to create a new search
type.
The new or modified search type is saved in the database and can be accessed
by all users at your site. You can restrict access to the search using standard
access controls.
For more information about data access, see My Teamcenter Guide.

5. Close the Edit dialog box.

Note For information about modifying query definitions, see the Query Builder
Guide.

3-38 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Create a user or group preference to override a saved query revision rule

1. Log on to the rich client using the user or role you want to be able to override
a saved query revision rule.

2. In My Teamcenter, choose Edit®Options to display the Options dialog box.

3. In the Options dialog box, click Search and use the Search on Keywords box to
find the site preference for which you want to create a user or group preference,
for example, TC_QRY_Item Revision – Latest Working_REVRULE.
Note To remove the revision rule, you can specify None as the preference
value.

4. Click New.

5. Use the same name as the site preference and select the scope, and provide the
desired revision rule.

6. Click Create.

There are now two preferences for the saved query, one governing the site and
another for the selected scope applicable to the group or user that created the new
preference.

Using extended multi-application searches

The Extended Multi-Application Search option on the Search menu provides
access to the Adhoc Classification Query and Target List search options.
• Use the Adhoc Classification Query option to define search criteria related
to attributes of classification classes.

• Use the Target List option to select objects from other Teamcenter applications,
active workflow processes, the clipboard, or from the results of other searches
to use as search filters.

Performing ad hoc Classification searches

To search for data using Classification attributes, create an ad hoc Classification
search.
When you use a saved query to search for an item, item revision, dataset, or class
that has the IMAN_classification attribute set, you add criteria for Classification
classes and attributes to the search.
For information about creating an ad hoc Classification search, using Classification
classes, and adding attributes to the search criteria, see Create an ad hoc
Classification search.
For information about searching the classification hierarchy for resources, see the
Classification Guide.

Create an ad hoc Classification search

1. In the Search pane, select an Item, ItemRevision, or Dataset search.

PLM00191 J Rich Client Interface Guide 3-39

Chapter 3 Searching in Teamcenter

2. Choose Extended Multi-Application Search from the Search menu .

The Advanced dialog box appears.

3. Click the Adhoc Classification Query tab.

4. Click the Search Classification Class button to access the Class/Attribute

Selection Popup tree.
Note If applicable, you can specify the system of measurement as metric
or nonmetric. You cannot search in both measurement systems
simultaneously.

5. Double-click a class name to select it from the popup tree.

Note If you want to search by attribute value, you must select a class that
contains attributes.

A row for the class is added to the classification search criteria definition table.
Note You can add or remove a search criteria clause by clicking the Add or
Remove button on the right side of the table.

6. Click the name of the class in the Property Name column to list and select the
desired search attribute.
Note You can use relational operators to search for a combination of attribute
values, for example, for a value range.
For information about combining search values using relational
operators, see the Classification Guide.

7. When done adding rows to the classification search criteria, click OK.
A pane with the ad hoc classification search criteria is added to the end of the
search form in the search pane.
Note You can remove the ad hoc classification search criteria pane from the
search pane by clicking the x button at the right of the pane.
You can change the values for the classification search criteria in the
Adhoc Classification Query dialog box. The classification search criteria
pane on the search form and the Adhoc Classification Query dialog
box are synchronized after any modification to the classification search
criteria clauses.

8. Click to perform the search.

The number of classes matching your search are displayed at the bottom of the
dialog box, and the first result is highlighted in the tree.

3-40 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

To navigate through the results:

Go to next Press F3, Page Down, or Down Arrow key.
match
Go to Press the Page Up or Up Arrow key.
previous
match
Go to first Press the Home key.
match
Go to last Press the End key.
match
For more information about defining ad hoc classification search criteria, see Define
search criteria using multiple Classification classes.

Search for data using Classification attributes

1. Click Search in My Teamcenter.

2. Select a search value from the LOV list for a Classification attribute if that
attribute is associated with a KeyLOV.

3. Add it to the list by double-clicking the attribute.

4. Select the Search Criteria from the list.

Note If a Classification attribute used in a saved query is hidden from the
user, this attribute is not displayed in the query form. Similarly, if a
class is hidden from the user, any saved queries of this hidden class
are not displayed.

PLM00191 J Rich Client Interface Guide 3-41

Chapter 3 Searching in Teamcenter

Define search criteria using multiple Classification classes

You can create ad hoc classification search criteria using multiple classes. The
following example illustrates using multiple classes to search for angle base plates
with more than 20 holes or with a length greater than 10:
1. Select the Angle Base Plate class, and add the following clause to the table:
Number of Holes > 20

2. Select the Base Plate class, and add the following clause to the table:
Length > 10

3. Combine these two search clauses with the OR logical operator

For information about creating ad hoc classification search criteria, see Create an ad
hoc Classification search.
For information about combining search values using relational operators, see the
Classification Guide.

Saved queries on classification attributes

In the My Teamcenter application, you can execute a Classification saved query by
filling out the query form in the same way you perform other saved queries. The
classification objects are returned to the user if the saved query is based on a class.
An ITK programmer can write code against the ITK APIs to define a Classification
query, which you can then execute in My Teamcenter.
The scope of the search is determined by the
QRY_search_classification_hierarchy user preference. The default value is
false.
• If this preference is set to false, the query searches only the specified class.

• If this preference is set to true, the saved query or ad hoc Classification query
searches the specified class as well as all classes of which the specified class is
an ancestor.
Note If a classification attribute used in a saved query is hidden from the user, this
attribute is not shown in the query form. Similarly, if a class is hidden from
the user, any saved queries of this hidden class are not shown to the user.

Using target list filtering in searches

You can select objects from other Teamcenter applications, active workflow processes,
the clipboard, or from the results of other searches to use as search filters.
To access this feature, choose Extended Multi-Application Search from the Search
menu and click the Target List tab.
Note This is supported only for Local queries.

Apply target list filtering criteria to your search

1. Choose Extended Multi-Application Search from the Search menu .

3-42 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

The Advanced dialog box appears.

2. Click the Target List tab.

The source options from which you can filter searches appear on the Target List
pane. Source options include Clipboard, Referencers, Prior Search, Active
Workflows, Applications, and Structure Manager.
Note Multiple sources can be used to filter a single query. For example, you
can select the results of a prior search along with the BOM elements of
an assembly displayed in Structure Manager.

3. Apply one or a more of the search filters.

• Clipboard
Uses objects on your clipboard to filter searches. The number of objects on
the clipboard appears to the right of the check box.
• Referencers
Filters based on all elements that appear in the Impact Analysis pane, or
the Referencers pane in some applications, as a result of a where-referenced
or where-used search performed on the selected object.
• Prior Search
Filters based on the results of prior searches. The list displays all search
results that are open in your session, and you can select one or more sets of
search results from the list. All elements in the selected search results are
included in the search filter.
• Active Workflows
Queries the database for active workflows and displays the query results.
You select a single workflow and the database is queried for the targets of
the workflow. These target objects are added to the list of items used to
define the search filter.
• Applications
Filters based on objects currently selected in the chosen application or
applications.
• Structure Manager
Lets you perform the following steps to filter based on the contents of a
Structure Manager BOM window:
a. Select the Structure Manager list to filter based on the contents of an
open BOM window. When you select a BOM window, the system displays
the Collect BomElements dialog box. This dialog box lets you specify
how the BOM lines are expanded in the selected BOM window.

b. Choose an expansion option, either Expand Selected Lines or Expand

From Top Line.
Note Depending on the search type, BOM lines are expanded and the
BOM lines, item, item revision, or occurrences, are added as
target objects for the query. When a BOM line cannot be further
expanded, only the data items from the BOM line are added as
target objects for the query.

PLM00191 J Rich Client Interface Guide 3-43

Chapter 3 Searching in Teamcenter

c. (Optional) Set Load Value. The load value determines the number of
BOM lines that are loaded before a cancellation can be effected. For
example, if the value is 250 and you click Cancel, the operation stops
after loading 250 BOM lines.

d. Click Go.
The system loads the components and closes the Collect BomElements
dialog box.

4. Click OK.
The filters and number of objects associated with each filter are displayed at the
bottom of the search pane. To remove any of the filters, click X.
Note The number of objects in each filter is displayed after the search has been
run; however, the objects associated with the filters are not saved and
the search results are not saved when you exit your Teamcenter session.

Setting search options

Search options and preferences can be set using the dialog box you access by
choosing any of the following:
• Preferences from the Window menu in Teamcenter

• Preferences from the Search menu . in a Search view.

Note Option settings persist from session to session or until reset.

Working with search options

The general Search options include settings for queries, wildcards, multiple entries,
and general defaults.
• The Query Options section includes the following settings:
o Case Sensitive
Specifies that the case of the letters used in the query form boxes, as well as
the letters themselves, are used as search criteria.
By default, object searches are case insensitive.

o Latest Dataset Versions

Specifies that only the most recent versions of the dataset are retrieved.
By default, only the latest dataset version is displayed.

o Search Classification Hierarchy

Lets you extend a classification search to include all classes descending
from the selected classification class. If this option is not selected, the
classification search is performed within the selected class only.
By default, a classification search is performed within the selected class only.

o Enable Hierarchical Type Search

3-44 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Returns subtypes as well as parent types in type-based queries.

Searches can span multiple levels of object hierarchy to obtain hierarchical
results. The results include data on the qualifying objects and relationships
from various levels of the data model, as determined by the search criteria.
Relationships refer to the various ways in which Teamcenter allows objects
to be associated with each other through attribute references.
Criteria in a saved search determine what relationships are navigated and
what objects are retrieved. Search results are displayed in a structured tree
form where the hierarchical nature on the various objects found and the
relationships between them is represented.
Search results are auto-expanded to display the objects at the different
levels. Only objects meeting search criteria are displayed at each level.
By default, hierarchical type search is not enabled.
Note This setting takes effect only when the
QRY_search_type_hierarchy user preference is set to True.
The Enable Hierarchical Type Search search option is not supported
for remote search. You cannot perform a hierarchical type search for
published objects on an Object Directory Services (ODS) site.

• The Wildcard Option section lets you specify which of the three available
wildcard character sets (SQL style, UNIX style, and Windows style) is enabled.
By default, on Windows systems, the wildcard option is Windows Style.

• The Multiple Entry Options section lets you specify a delimiting character and
an escape character.
o The Delimiting Character lets you enter multiple values, including wildcard
characters, as search criteria in many of the search form boxes. This feature
can be used in search boxes associated with lists of values as well as with
text boxes.
By default, the Delimiting Character value is the semicolon (;).

o The Escape Character value specifies a character to use to escape wildcard

characters.
By default, the Escape Character value is the tilde (~).
Note If a wildcard character that is currently in use (system wide) is defined
as a separator, it is treated as a list separator and not as a wildcard
character.

• The Default Search setting specifies the type of saved search presented by
default.
The default is Item ID.

• The Default Business Object Type setting specifies the type of business object
presented by default.
The default is Item.

PLM00191 J Rich Client Interface Guide 3-45

Chapter 3 Searching in Teamcenter

• The Search Locale setting specifies the current locale for searches.
The default is English.

The Search option for Favorites provides a two-column list with query names on
one side and check boxes on the other.
Use the arrows on the right side of the pane to move a selection up or down in the list.
You can select or clear the check box beside a query name to add or remove that query
from the top of the System Defined Searches tab in the Change Search dialog box.
The Search option for Remote displays the table of remote Multi-Site Collaboration
sites to let you specify whether to include a remote site databases as search targets.
The Search options for Results include search history, page size, open result limit,
and load all limit.
• Configure the search history size
Specifies the number of searches kept in the search history. The default value
is 8.

• Clear search history

Click to clear the search history list.

• Set Loading Page Size

Defines the number of objects to be loaded when executing a search.
The default value is 30.

• Set open search result limit

Specifies the maximum number of open searches. The default value is 30.

• Set load all limit

Specifies the maximum number of loaded searches. The default value is 400.

The search option for Saved Searches specifies whether to display My saved
searches.

Working with favorite search options

The Favorite Options tab provides a two-column list with query names on one side
and check boxes on the other. On the right side of the pane, there are arrows for
moving a selection up or down in the list.
You can select or clear the check box beside a query name to add or remove that query
from the top of the System Defined Searches tab in the Change Search dialog box.

Using the remote search option

The Remote Option tab displays the table of remote Multi-Site Collaboration sites to
let you specify whether to include remote site databases as search targets.

3-46 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Using sort search options

The Search view Sort command displays the Sort Options dialog box, which
provides a two-column list with attributes on one side and order direction settings on
the other. On the right side of the pane, there are arrows for moving a selection up
or down in the precedence list.
• To assign the sort priority of an attribute (in relation to other attributes in the
list), select the row containing the attribute and move it up or down using the
arrow buttons.

• To specify the sorting for a particular attribute, click the cell in the Order By
column and select Ascending, Descending, or None from the list.
Note For attribute precedence to take effect, you must specify an Order By value
other than None.

Creating property finder formatter (PFF) objects

The property finder formatter (PFF) can be used to gather and report properties
data related to the objects listed in the search results.
• PFF objects provide the necessary links and relationships required to locate
object properties data without reformatting the query instance.

• The PFF objects enable you to view additional information about the search
results objects that a single query could not provide.

• A set of property finder formatter (PFF) objects corresponding to the basic search
types are delivered as part of the standard Teamcenter installation. Additional
PFF objects can be created.

• To define a PFF object, you must understand where and how properties data is
stored and the relationships between data objects. Therefore, PFF objects are
generally created by a Teamcenter administrator.
Note If you build queries using property finder formatter objects, you cannot
include the dot character (.) in class names.

Create a property finder formatter (PFF) object

1. Execute the search for which you want to create a PFF object.

2. In the Search Results view, click the Select PFF button to activate the Edit
Property Formatter button.

3. In the Search Results view, click the Edit Property Formatter button.
The Edit dialog box appears.

4. Type a name for the PFF object in the Name box.

The name should reflect the name of the query or business process to which the
PFF search is related. For example, if the PFF search finds additional data

PLM00191 J Rich Client Interface Guide 3-47

Chapter 3 Searching in Teamcenter

related to the item revision saved query, you could name the PFF object Item
Revision.

5. (Optional) Type a description for the PFF object in the Description box.

6. Select a class to include in the PFF property search criteria.

a. Click the Principle Query Object button.
The Class/Attribute Selection Popup dialog box appears.

b. Select the class that matches the base class of the query.
To search for a class in the popup menu, type the class name or a partial
name and wildcard character in the box, and click Find .
Tip You can determine the base class of the query by viewing the query
details in the search criteria definition.
For more information, see View search criteria definitions.

c. Close the Class/Attribute Selection Popup dialog box.

The name of the selected class appears in the Principle Query Object button.
The class and its attributes appear in the Property Selection section.
Note To display all attributes, rather than only the class attributes, click
the Display Setting button and select All Attributes. If you change
display settings after adding search clauses to the Search Criteria
table, the table is cleared.

7. Add a search clause for each property of the primary class that you want to
include in the PFF to the Search Criteria table.
a. In the Property Selection tree, expand the class name to display the class
properties, if necessary.

b. In the Property Selection tree, double-click the property you want to include
in the PFF search criteria.
A row for the property is added to the Search Criteria table.

8. (Optional) Select a secondary class to include in the PFF property search criteria
and add the applicable search clauses to the Search Criteria table.
a. Click the Add Clauses From button.
The Class/Attribute Selection Popup dialog box appears.

b. Select the secondary class.

Note The secondary search class must match one of the object types
returned by the original query, and the data you are searching for
must be related to the secondary object type.

To search for a class in the popup menu, type the class name or a partial
name and wildcard character in the box, and click Find .

3-48 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

c. Close the Class/Attribute Selection Popup dialog box.

The name of the selected class appears in the Add Clauses From button.
The class and its properties appear in the Property Selection section.
Caution If you change display settings after adding properties to the
Search Criteria table (for the primary class attributes for
example), the Search Criteria table is cleared.

d. Add a search clause to the Search Criteria table for each property of the
secondary class you want to include in the PFF.
A. In the Property Selection tree, expand the class name to display the
class properties, if necessary.

B. In the Property Selection tree, double-click the property you want to

include into the PFF search criteria.
A row for the property is added to the Search Criteria table.

9. (Optional) Change the column name that appears in the PFF report for a
property.
• Double-click the Column Names cell for the property and type a new name.

10. (Optional) Set the precedence of the search clauses.

• Use the up-arrow and down-arrow buttons located to the right of the Search
Criteria table to adjust the sequence of the search clauses.

11. (Optional) Verify that the PFF search returns the correct data before you create
the object.
a. Close the Edit dialog box.
Note The PFF definition is retained in the Edit dialog box and appears
there the next time you open the Edit dialog box.

b. In the Search Results view, click to execute the PFF.

The results of the PFF search appear in tabular format in the Search
Results view.
Note If you specify criteria for a PFF object to be used for an ad hoc query
but do not click Create, the file size, byte size, and MIME type
information is not displayed in the ad hoc results.

12. To create the PFF object, click Create.

The PFF object appears in the Saved Property Formatter Finder tree in the
Edit dialog box.

Where-used and where-referenced searches

The where-used and where-referenced features available in the Impact Analysis
view or the Referencers pane in some applications, let you determine:

PLM00191 J Rich Client Interface Guide 3-49

Chapter 3 Searching in Teamcenter

• Whether a given item or item revision is used in any assemblies.

• What objects in the database reference a selected object.

You can use these searches to help determine the effect of modifying an item or
item revision.
For more information about where-used searches see Where-used searches.
For more information about where-referenced searches see Where-referenced
searches.

Where-referenced searches
Use a where-referenced search to find objects that reference a selected object.
There are two methods of performing where-referenced searches.
• The first method produces a graphical representation of all references to the
selected object.

• The second method uses the Referencers Print Wizard dialog box.

Perform a graphical where-referenced search

1. Select the Impact Analysis view.

2. Select an object in the tree view.

The selected object appears in the Impact Analysis view.

3. Select Referenced from the Where option list, located in the upper left area
of the pane.

4. Select a depth level from the Depth option list:

• One Level
Reports only immediate parent components of the object.
Note With this level selected, you also have the option to set the Type
and Relation filters.

• All Levels
Reports all parent components of the object, up to the top-level directory.

• Top Level
Reports only the top-level component.

5. (Optional) If you selected a depth of one level, you can also select a search filter
from the Type and Relation options.
Note If your administrator has added custom relations for your site, these
are visible in the Relation list only if they are referenced in the
WHERE_REFERENCED_RELATIONS_FILTER preference.

6. Double-click the object in the view pane to activate the search.

3-50 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

The object and the objects by which it is referenced are displayed in graphical
format. The results can be used as the basis for another where-used or
where-referenced search, or they can be formatted and printed.

Perform a where-referenced search using the Referencers print wizard

1. Select the Impact Analysis view.

2. Select an object in the tree view.

The selected object appears in the Impact Analysis view.

3. Select the Where-Used/Referenced Report option from the menu in the

upper-right of the Impact Analysis view.
The Referencers Print Wizard dialog box appears showing the first step of the
wizard.

4. Select the Where Referenced option.

5. Click Next.
Step 2 of the wizard appears in the dialog box.

6. Select a depth level.

One Level Reports only the immediate parent component of the object.
All Levels Reports all parent components of the object, up to the
top-level directory.
Top Level Reports only the top-level parent component.

7. Click Next.
Step 3 of the wizard appears in the dialog box.
In this step, the object to be used as the basis of the search is shown along with
report generation options.

8. Select a report generation option:

Generate Presents the where-referenced results in HTML format in
HTML/Text report the Print dialog box. From this window, you can format the
report and either print it or save it to a file.
Generate the Presents the where-referenced results in tree format in the
structure report Report dialog box.

9. Click Yes.
The where-referenced search is generated and the results are displayed.
At this point, you can format, save, or print your report.
For information about using the output options on the Print and Report dialog
boxes, see Getting Started with Teamcenter.

PLM00191 J Rich Client Interface Guide 3-51

Chapter 3 Searching in Teamcenter

Where-used searches
Where-used searches let you identify all the assemblies that contain an item or
item revision.
You can do this to assess the impact of engineering changes to the product structure
or to check if changes in one assembly affect other assemblies.
There are two methods of performing where-used searches.
• The first method produces a graphical representation of the assembly or
assemblies in which the item or item revision is used.

• The second method uses the Referencers Print wizard and produces a report of
the where-used results.

A where-used search can take into account the revision rule when searching the
product structures, and you can choose one of the following outputs:
• All revisions
Reports all item revisions that have an occurrence of the source item revision.
This search result displays all combinations of usage that can possibly occur;
when a particular set of revision rules is applied not all paths may be realized.

• Only the revision configured by a selected revision rule

The search result is filtered to include only those revisions configured by the
selected revision rule.
The revision rule is applied at each level, up to and including the top level. The
system displays any intermediate level nonconfigured revisions referenced by
precise occurrences, if the top of the chain of precise links is configured. To
configure this mode, set the PS_wu_configd_imprecise_only user preference
to true. This preference has no effect if the selected revision rule contains any
precise entries.
Note The All option for where-used searches is a special case mode, not a
revision rule.
The From PSE option, available only when a where-used search is
accessed from the Structure Manager application, is also a special case
mode, not a revision rule.

Perform a where-used search to display a graphical result

1. Select an item or item revision in a component or details view.

2. In My Teamcenter, select the Impact Analysis view.

3. Select Used from the Where option list, located in the upper left of the pane.

4. Select a rule from the Rule list.

This rule provides parameters to locate the assemblies in which the item or
item revision is used.
Revision rules are made up of sequential lists of entries, each of which is
evaluated to obtain a configured revision of the item.

3-52 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

For example, if you select the Any Status; Working rule, only the latest released
revision of the assembly is retrieved if it exists. Otherwise, the latest working
revision is retrieved. Released assemblies and earlier versions of the assembly
are not retrieved when this rule is selected.
For more information about revision rules, see Getting Started with Product
Structure.

5. Select one of the following depth levels from the Depth list located in the
bottom-right corner of the window:
• One Level
Reports only immediate parent components of the object.

• All Levels
Reports all parent components of the object, up to the top-level directory.

• Top Level
Reports only the top-level component.

6. Double-click the object to start the search.

• If the item or item revision is not part of an assembly that matches the
selected revision rule, the system displays a message to that effect.

• If the item or item revision is part of a configured assembly, the structure is

displayed in graphical format.
The results can be used as a basis for another where-used or where-referenced
search or they can be formatted and printed.

You can change the item revision properties that are shown in the results by
selecting the required properties from the Display list. Teamcenter remembers
your selection for future sessions.
You can also filter the results to show only selected item types. To do this, select
the Filter by Item Type check box and select the required item type and filter
level from the lists. You can also select the Include Subtypes check box to
include both item revisions whose item is of the specified type and any subtype of
that type. You can further refine the selection by showing the results only for the
top level of the structure or for all levels below the selected top level. To rerun
the where-used search with changed criteria, double-click the target node.

Perform a where-used search to create a text or HTML report

1. Select an item or item revision in the tree or Details table.

2. In My Teamcenter, select the Impact Analysis view.

3. In My Teamcenter, choose the Where-Used/Referenced Report menu command.

a. Select the Where Used option to generate a where-used report and click Next.

b. Select one of the following Depth level options and click Next:
• One Level

PLM00191 J Rich Client Interface Guide 3-53

Chapter 3 Searching in Teamcenter

Reports only immediate parent components of the object.

• All Levels
Reports all parent components of the object, up to the top-level directory.

• Top Level
Reports only the top-level component.

c. Select a Where-Used rule and click Next.

The Where-Used rule provides parameters to locate the assemblies in which
the item or item revision is used. For example, if you select the Latest
Working rule, only the latest working revision of the assembly is retrieved.
Released assemblies and earlier versions of the assembly are not retrieved
when the Latest Working rule is selected.
For more information about revision rules, see Getting Started with Product
Structure.

d. Select the item or item revision properties to include in the report and click
Next.
The system displays the item or item revision and selected revision rule that
will be the basis of the search, together with report generation options.
Note The preselected properties are those used when you last ran the
wizard. You can change them as necessary.

4. Confirm that the required items, item revisions, and revision rules are shown
correctly, and then choose a report generation option.
• Generate the HTML/Text report
Presents the where-used results in HTML format in the Print dialog box.
From this dialog box, you can format the report and either print it or save it
to a file.

• Generate the structure report

Presents the where-used results in tree format.

5. Click Yes.
Teamcenter runs the where-used search and displays the results. At this point,
you can format, save, and print your report.

• (Optional) Change the print format.

o HTML
Displays results in the default print format.

o HTML Table
Displays results in tabular format. This improves readability for large
reports.

o Text Format

3-54 Rich Client Interface Guide PLM00191 J

 Searching in Teamcenter

Displays results as text.

• (Optional) Format the report by performing the following steps:

a. Click Set Result Format in the upper-right corner of the Print dialog
box.
Teamcenter displays the Print Format dialog box. The formatting options
vary depending on the type of object selected and whether you are
printing in HTML, HTML table or text format.

b. Modify the result format.

c. Click Update.

d. Close the Print Format dialog box.

6. To save or print the report, complete the appropriate process.

• Print a text or HTML file.

a. Click Print .

b. Define the printer to which the file will be sent.

You can accept the default printer that is displayed in the Name box or
select a different printer from the list.

c. Click OK to print the file and exit the dialog box.

d. Click Close to exit the Print dialog box.

• Save output to an HTML or text file.

a. Click the Save button (located in the lower-right corner of the Print
dialog box).
The Save dialog box appears.

b. Navigate to the directory location where you want to save the file.

c. Type the name of the file, including the .htm, .html, or .txt extension, in
the File name box.

d. Click Save to save the file and exit the dialog box.

e. Click Close to exit the Print dialog box.

PLM00191 J Rich Client Interface Guide 3-55

Chapter

4 Using the Application Interface

Viewer

Using the Application Interface Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Understanding Application Interface Viewer objects . . . . . . . . . . . . . . . . . . . 4-1

Tracking requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Allowable states transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Interpreting request status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Share data with the external application . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Open the Application Interface Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Control transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Using incremental changes with requests . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Administering data transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Export data through the application interface . . . . . . . . . . . . . . . . . . . . . 4-8
Import data through the application interface . . . . . . . . . . . . . . . . . . . . . 4-10
Create a synchronization request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Process a publish request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

PLM00191 J Rich Client Interface Guide

Chapter

4 Using the Application Interface

Viewer

Using the Application Interface Viewer

The Application Interface Viewer allows you to monitor and administer data
exchanges between Teamcenter and an external application using the Application
Interface (AI) service functionality.
For more information about the AI Service, see the Services Reference in the
Teamcenter HTML Help Collection.
Note The Services Reference is available only in the Teamcenter HTML Help
Collection. It is not available in the PDF collection.

The data exchanges between Teamcenter and the external application are in PLM
XML format, and the data may represent a project, product, process, or other data
structure. The Application Interface Viewer is intended for use by administrators
and other skilled users who have an understanding of the AI service functionality
and PLM XML syntax.
The Application Interface Viewer allows you to do the following:
• View an application interface object that manages the data in an import or
export transaction.

• Create a synchronization request and track its state and status. The
synchronization request captures the data to export to the external application.

• Create a publish request and track its state and status. The publish request
captures the data to import into Teamcenter.

Understanding Application Interface Viewer objects

The following objects are used in the Application Interface Viewer:

PLM00191 J Rich Client Interface Guide 4-1

Chapter 4 Using the Application Interface Viewer

Object Description
Collaboration A persistent structure that allows data to be shared by
context different applications, for example, a Teamcenter context and
a third-party application context. It may consist of one or
more structure contexts, each of which may have a different
configuration. The children of a configuration are defined by
a configuration context. A collaboration context is typically
a project folder that contains all the information associated
with a project; it may contains references to objects in
Teamcenter, including structure contexts.
Structure context A configurable structure that consists of one or more root
objects sharing the same configuration. For example, it
may be one or more BOMs or assembly structures and their
configurations. The configuration of the structure context is
defined by a configuration context. The structure objects may
have occurrence groups, items, and item revisions.
Application A persistent workspace object that is the repository for the
interface object import and export transactions between Teamcenter and
the external application for a predefined and configured
structure. It contains:
• An ordered list of request objects.

• The transfer mode (import or export).

• The root or top-level object of the structures to exchange.

This may be any object that is valid to import into or
export from Teamcenter, for example, a structure context,
a folder, or an item (including all its revisions).

• Tracking information to allow updates of changed data

(deltas).
Master record A persistent POM object that captures information about
object import and export data. Teamcenter can detect changes to
his information and export only changed data.
Sync request object A persistent workspace object that tracks the data, state,
and status of a request to export data from Teamcenter.
The synchronization request contains the PLM XML file
holding the imported data. It also contains state and status
information that allows you to monitor the request from
creation to completion.
Publish request A persistent workspace object that tracks the data, state, and
object status of a request to publish data in Teamcenter. The publish
request contains the PLM XML file holding the imported
data. It also contains state and status information that allows
you to monitor the request from creation to completion.
Transfer mode A persistent workspace object that is a repository of details
object of one type of translation. It captures a set of closure rules,
filters, and property sets that define a PLM XML translation
on import or export.

4-2 Rich Client Interface Guide PLM00191 J

 Using the Application Interface Viewer

Tracking requests
The Application Interface Viewer allows you to track three types of requests:
• Synchronization request
This is associated with a single data export transaction.

• Publish request
This is associated with a single data import transaction.

• Notify request
This informs the Teamcenter and external application users of the success or
failure of the transaction.

The import or export of data may take significant time, depending on the size of the
structure. Each request transitions through several states and you can monitor
these states to determine the status of the request. The possible request states are:

State Request status

New The request is created but not yet processed.

Processing PLM XML data creation is in progress, or a PLM XML file
import has begun.
Pending Processing is complete and communication of the
synchronization request is in progress, or the synchronization
request is complete, but the Publish request is not processed.
Communicating Teamcenter and the external application are exchanging
data.
Completed Processing of the transaction request is complete but not
necessarily successful.
Rejected The transaction request is rejected. Teamcenter maintains
the history of requests, unless you explicitly delete them.

Allowable states transitions

The following table lists the permissible state transitions for a synchronization
request. It also shows when application interface objects and requests are locked
for update.

Initial state New state Changed by Preconditions Object locking

None. New An application The requestor None.
interface object must have
when a request write access to
creation is the application
initiated by a interface object.
user or workflow
action.

PLM00191 J Rich Client Interface Guide 4-3

Chapter 4 Using the Application Interface Viewer

Initial state New state Changed by Preconditions Object locking

New Processing An application None. The application
interface object interface object
during generation is locked for
of PLM XML for updating.
the request.
Processing Pending An application The request The application
interface object is successfully interface object is
after processing is processed. unlocked.
complete.
Pending Communicating AI service on a The request has The request is
call to start data export access locked to update
exchange. rights. and to retrieve
files.
Communicating Completed AI service on a The file transfer is The request is
call to end data complete. unlocked.
exchange.

The following table lists the permissible state transitions for a Publish request. It
also shows when application interface objects and requests are locked for update.

Initial state New state Changed by Preconditions Object locking

None. New An application The requestor None.
interface object must have
when a request write access to
creation is the application
initiated by a user interface object.
or an AI service There must
request to create a be no pending
Publish request. synchronization
request.
New Communicating AI service on a None. The request is
call to start a data locked to update
exchange. and to retrieve
files.
Communicating Pending AI service on a The file transfer is The request is
call to end a data complete. unlocked.
exchange.
Pending Processing An application The request has The application
interface object import access interface object
triggered by a rights to the is locked for
user or workflow request object. updating.
action. There must
be no pending
synchronization
request.

4-4 Rich Client Interface Guide PLM00191 J

 Using the Application Interface Viewer

Initial state New state Changed by Preconditions Object locking

Processing Completed An application Processing is The application
interface object complete. interface object is
after processing is unlocked.
complete.

Interpreting request status

Each request may have one of the following status values:

Status value Meaning

Normal No errors have been detected.
Warning An error was detected, but processing continued.
Severe A failure occurred and processing terminated.
Abort The transaction was interrupted.

The following table lists the possible status transitions and the resulting actions.

Cause New state New status Actions taken

Severe failure Completed Severe For a synchronization
during processing. request, Teamcenter deletes
Transaction cannot the request. For a publish
recover. request, the completed
processing is undone and
the request remains in the
queue.
Recoverable failure Pending Warning For a synchronization
during processing. request, Teamcenter deletes
the request. For a publish
request, the completed
processing is undone. You
may resume the transaction
at any time when the cause
is rectified.
Failure during Communicating Warning You may resume the
communication. (unchanged) transaction at any time.
The user aborted Communicating Abort You may resume the
communication. (unchanged) transaction at any time.
A reject request Rejected Normal You can delete the request
is initiated by a from the queue.
user with write
permission to the
request.
Invalid access rights Unchanged Warning You may resume the
or the object is transaction at any time
locked. when the cause is rectified.

PLM00191 J Rich Client Interface Guide 4-5

Chapter 4 Using the Application Interface Viewer

Share data with the external application

1. Select one or more BOM lines.

2. Request that the associated data is sent to the external application by choosing
Tools→Export objects→AppInterface.

3. Select the relevant application interface type from the list.

Teamcenter:

a. Creates a new structure context containing an occurrence group for the

selected BOM lines, and assigns the window configuration to the structure
context.

b. Creates a new application interface object and attaches the structure context
to it.

c. Attaches the import and export transfer modes associated with the external
application to the application interface object.

d. Traverses the structure context according to its configuration and export

transfer mode, then creates the necessary PLM XML data.

e. Creates a master record of all the objects it created and attaches them to the
application interface object.

f. Creates a synchronization request and attaches the PLM XML file to this
request.

g. Attaches the synchronization request to the application interface object.

4. The external application is launched and Teamcenter passes it the application

interface object and user identifications. It then:
a. Logs on using the AI service.

b. Retrieves the PLM XML file and the corresponding datasets.

c. Sets the synchronization request state to Completed.

d. Logs off using the AI service. The application interface object,

synchronization request, and corresponding data are deleted.

You can monitor the progress of these transactions with the Application Interface
Viewer.

Open the Application Interface Viewer

1. Select an application interface in the navigation tree.

2. Click the Viewer tab.

Teamcenter opens the Application Interface Viewer showing details about the
selected application interface transactions.

4-6 Rich Client Interface Guide PLM00191 J

 Using the Application Interface Viewer

When the Application Interface Viewer opens, it shows a table of all request
transactions with the external application. For each request object, the following
information is shown by default:

• Name

• Request Type

• Last Modified Date

• Last Modified By

• Processed Date

• Processed By

• Status

• Status Description

• State

• State Description
Note You can customize how the table of requests displays by right-clicking in the
table columns. You can then add, remove, and reposition columns in the
table. You can also define criteria for sorting data in the table, and create
and modify data display filters.

Control transactions
1. Open the Application Interface Viewer.
For more information, see Open the Application Interface Viewer.

2. Use the following buttons on the viewer to control transactions:

Add Sync
Allows you to create a new synchronization request and add it to the table
of requests.
Add Publish
Allows you to create a new publish request and add it to the table of requests.
Process
Allows you to accept the request currently selected in the table. It is disabled
if a request is not selected.
Reject
Rejects the currently selected request.
Delete
Deletes the currently selected request.
Refresh
Refreshes the status of all requests in the table.

PLM00191 J Rich Client Interface Guide 4-7

Chapter 4 Using the Application Interface Viewer

Export
Allows you to export the PLM XML file associated with the request to a
specified folder.

Using incremental changes with requests

You can use incremental change orders to manage changes to the application
interface data.
• Any such incremental change data is sent to the external system when the user
initiates a synchronization request.

• Similarly, data changes caused by a publish request may result in incremental

changes.
Note If a request object in the viewer has incremental changes associated with it,
the corresponding entry in the table is colored blue.

Administering data transfers

You can administer data transfers between Teamcenter and the external application.
You can:
• Export data through the application interface

• Import data through the application interface

• Create a synchronization request

• Process a publish request

Export data through the application interface

To send structure data to synchronize with the external application, you can create
a new synchronization request and append it to a new or available application
interface object, as follows:
1. Choose Tools→Export→AppInterface and choose the appropriate application
interface type for the external application.
The system displays the Application Interface Export dialog box.

2. In the dialog box, specify the following data:

• Request Name
Type a unique name for the synchronization request.

• Request Description
Type a unique description for the synchronization request.

• Root Objects
Displays the list of root objects such as structures to export.

4-8 Rich Client Interface Guide PLM00191 J

 Using the Application Interface Viewer

• Check Out Objects?

Select this check box to check out affected objects (structures) when data
export commences. By default, the objects are not checked out.

• Complete or Delta
By default, only changed data is exported, depending on how your
preferences are set. Select this check box to export all data.
Note If you create a new application object, only complete data may be
exported.

• Set Request State on Completion

Select if the request state is set to Pending or Complete when the export
process is complete. This allows you to track import and export activity
with the Application Interface Viewer when the user manually updates data
with import or export actions.

• (Optional) Select the Is Incremental Export check box to export only

changes to large structures. This check box is only available if the
AI_Incremental_Export preference is set to true.

3. Click the Existing AI Objects button to display and choose from a list of objects
to export, or click New to create a new application interface object. If you create
a new object, the system displays a New AI Object dialog box, where you must
define the following:

• Name
Type a unique name for the new application interface object.

• Request Description
Enter a type for the new application interface object.

• Transfer Mode
Choose a transfer mode from a list of all transfer modes in the database that
are marked as incremental.

• Site Name
Choose a site name from the list of available sites.

• Check Out Objects?

Select this check box to check out affected objects when data export
commences. By default, the objects are not checked out.

4. After you define the necessary data, click OK or Apply to create a new publish
request, generate PLM XML data, and append it to the queue of requests in the
specified application interface object.

PLM00191 J Rich Client Interface Guide 4-9

Chapter 4 Using the Application Interface Viewer

Import data through the application interface

To import structure data and update Teamcenter with the imported data, you
can create a new publish request and append it to a new or available application
interface object, as follows:
1. Choose Tools→Import→Import Through AI.
The system displays the Application Interface Import dialog box.

2. In the Application Interface Import dialog box, specify the following data:
• Request Name
Type a unique name for the publish request.

• Request Description
Type a unique description for the publish request.

• Check In Objects?
Check this check box to check in affected objects when data import
commences. By default, the objects are not checked in.

• Change Order
(Optional) Create a new change order or associate a change order with the
import process to track the incremental changes resulting from the imported
data.

3. Click the Existing AI Objects button to display and choose from a list of objects
to import, or click New to create a new application interface object.
If you create a new object, the system displays a New AI Object dialog box, where
you must define the following:

• Name
Type a unique name for the new application interface object.

• Description
Enter a type for the new application interface object.

• Transfer Mode
Choose a transfer mode from a list of all transfer modes in the database that
are marked as incremental.

• Site Name
Choose a site name from the list of available sites.

4. After you define the necessary data, click OK or Apply to create a new publish
request and append it to the queue of requests in the specified application
interface object.

4-10 Rich Client Interface Guide PLM00191 J

 Using the Application Interface Viewer

Create a synchronization request

1. To create a new synchronization request, click the Add Sync button.
The system displays the Request Creation dialog box.

2. Define the following:

• Request Name
Type a unique name for the synchronization request.

• Request Description
Type a unique description for the synchronization request.

• Full Update or Partial Update

Choose Full Update to update all the data you specified when you created
the application interface. Choose Partial Update to update only preselected
structures.

• Complete or Delta
By default, only changed data is exported, depending on how your
preferences are set. Select this check box to export all data.
Note If you create a new application object, only complete data may be
exported.

• Check Out Objects?

Check this check box to check out affected objects when data export
commences. By default, the objects are not checked out.

3. Click OK or Apply to create a new synchronization request.

Process a publish request

1. Click the Process button.
The system displays the Publish Request Process dialog box.

2. Define the following:

• Request Name
Type a unique name for the publish request.

• Request Description
Type a unique description for the publish request.

• Request State for read only

Enter the required state of the publish request for a read-only transaction.

• Request Status for read only

Enter the required status of the publish request for a read-only transaction.

PLM00191 J Rich Client Interface Guide 4-11

Chapter 4 Using the Application Interface Viewer

• Change Order
(Optional) Create a new change order or associate a change order with the
import process, to track the resulting incremental changes.

• Effectivity
Click this tab to edit the effective units or dates.

3. Click OK or Apply to process a publish request.

4-12 Rich Client Interface Guide PLM00191 J

Chapter

5 Option reference

Option reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

NX Remote Manager (AIE) options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

ARM Transaction Monitor options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Content Management options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Cross Probing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Dataset options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Generic Relationship Manager (GRM) options . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Integration for I-deas options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

List of values (LOV) options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Live update options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Logging options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Mail options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Manufacturing Process Management (ME) options . . . . . . . . . . . . . . . . . . . . 5-14

NX options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Product Structure options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Project options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Refresh notify options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

STEP Translator options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Security options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

Status indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

System options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27

Systems Engineering options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27

PLM00191 J Rich Client Interface Guide

 Work Breakdown Structure (WBS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28

Computer-Aided Engineering (CAE) Tools options . . . . . . . . . . . . . . . . . . . . . 5-28

Batch meshing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
General options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Inspector options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Package location options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Simulation tool options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
StuctureMap options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33

Calendar options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34

Default Base Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Start of Week . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34

Change Management options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34

BOM Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35

DesignContext options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Product Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Product Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38

General options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38

Checkin/checkout options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Identifier options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Item options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Item revision options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
User interface (UI) options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

Graphical BOM Compare options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43

Graphical History options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44

Multi-Site Collaboration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44

Integrated Directory Services Manager (IDSM) options . . . . . . . . . . . . . . 5-44
Import remote options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
Multi-Site Collaboration miscellaneous options . . . . . . . . . . . . . . . . . . . . 5-49
NX part family options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
Object Directory Services (ODS) options . . . . . . . . . . . . . . . . . . . . . . . . . 5-50

Search options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51

Favorite Business Object Type options . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Favorite option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
General options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
Remote option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
Results options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
Saved Searches option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53

Visualization options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53

Lifecycle Visualization options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
Product views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54

Workflow options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56

General options for workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
Inbox options for workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57

Rich Client Interface Guide PLM00191 J

Chapter

5 Option reference

Option reference
You can control the behavior and display of Teamcenter applications in both the rich
client and the thin client using options and preferences.
• Preferences are configuration variables stored in a Teamcenter database that are
read when a Teamcenter session is initiated.

• Options are preferences presented in the rich client by category (in a tree).
Options usually have predefined valid values.

For more information about setting options, see Using preferences.

NX Remote Manager (AIE) options

NX Remote Manager provides the framework and common functions required
to integrate applications with Teamcenter. This framework consists of three
components: Encapsulation Manager, NX Remote Manager, and Supplier Manager.
Use NX Remote Manager preferences to modify the integration’s behavior.
For more information about preferences, see the Preferences and Environment
Variables Reference.

Option Purpose
General tab
Save log from deleted Directs the system to save the transaction log file
connections for each connection after the connection is deleted.
The log file is saved in the top-level NX Remote
Manager connection directory. The name of the file
is the name of the connection followed by a number
to make it unique. For example, a connection named
UG-RM_001 has a corresponding transaction log file
named UG-RM_001_6671.log.
Preference name: AIE_save_transaction_log.
Export tab
Export directory Allows you to define the top-level NX Remote Manager
connection directory. This is the main directory where the
system creates the export directory for each connection.
Preference name: AIE_export_dir.

PLM00191 J Rich Client Interface Guide 5-1

Chapter 5 Option reference

Option Purpose
Export read-only files Specifies how files associated with datasets to which you
as read-only do not have write permission are exported. If this option
is selected, those files are written in the connection export
directory with read-only privileges. If not selected, all
files are written to the export directory with read/write
privileges.
Preference name: AIE_export_read_only.
Named References To Allows you to specify the named references to export to
Export a connection.
Primary Exports the primary named reference
of the dataset.
All Exports all named references of the
dataset.
Select Displays a dialog box allowing you to
select the named references to export.
The default value is Primary.
Preference name: AIE_named_refs_to_export.
Check-Out new Indicates whether new components are checked out when
components during a connection is refreshed.
refresh connection
Preference name:
AIE_checkout_new_components_during_refresh.
Import tab
File types to ignore Defines the file types to ignore during import, such as
backup files.
Preference name: AIE_file_types_to_ignore.
Import Details Master Indicates if the user has permissions to modify import
information in the XML files when importing them back
to Teamcenter.
• Application
The user is not allowed to modify the import
information from Teamcenter.

• Both
The user is allowed to modify the import information
from Teamcenter.

The default value is Both.

Preference name: AIE_import_master.
NX tab

5-2 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Copy non-master Indicates whether NX copies nonmaster data.
Preference name: AIE_copy_nonmaster.
Part Family Members Specifies whether the part family members are Lose,
Strip status, or Error.
The default value is Lose.
Preference name: AIE_part_family_members.
Autotranslate Mode Specifies whether the autotranslate mode is Default or
Legacy.
The default value is Default.
Preference name: AIE_autotranslate_mode.

For more information about NX Remote Manager, see the NX Remote Manager
Guide.

ARM Transaction Monitor options

Application Response Measurement (ARM) is a tool that Teamcenter uses for
user-level transaction monitoring. Privileged users can enable transaction
monitoring using the ARM preferences or using the Performance Monitor options.
Modifying the Performance Monitor options automatically sets the corresponding
preference instance to user scope.
For more information about ARM preferences, see the Preferences and Environment
Variables Reference.

Option Purpose
General tab
UI ARM Transactions
Expand Object Measures the elapsed time from the beginning of
the expand operation until all objects are loaded and
displayed.
Preference name: ARM_expand_object.
Create Item Measures the elapsed time from the beginning of the
creation operation until the item is loaded and displayed.
Preference name: ARM_create_item.
Create Item Revision Measures the elapsed time from the beginning of the
creation operation until the item revision is loaded and
displayed.
Preference name: ARM_create_itemrev.

PLM00191 J Rich Client Interface Guide 5-3

Chapter 5 Option reference

Option Purpose
Create Dataset Measures the elapsed time from the beginning of the
creation operation until the dataset is loaded and
displayed.
Preference name: ARM_create_dataset.
Import Dataset Measures the elapsed time from the beginning of the
dataset import operation until the operation is completed
and returns the status.
Preference name: ARM_import_dataset.
Export Dataset Measures the elapsed time from the beginning of the
dataset export operation until the operation is completed
and returns the status.
Preference name: ARM_export_dataset.
Where Used Measures the elapsed time from the beginning of the
where-used operation until the result is displayed and
returns the status.
Preference name: ARM_where_used.
Where Referenced Measures the elapsed time from the beginning of the
where-referenced operation until the result is displayed
and returns the status.
Preference name: ARM_where_referenced.
Search Object Measures the elapsed time from request until found
objects are displayed. Returns the status, number of
objects found, and IDs of objects.
Preference name: ARM_search_object.
Save As Item Measures the elapsed time from the beginning of the
operation until all objects are loaded and displayed.
Returns the status and new item ID and item revision ID.
Preference name: ARM_saveas_item.
Open Dataset Measures the elapsed time from the beginning of the
operation until all objects are loaded and displayed.
Returns the status and new dataset ID.
Preference name: ARM_open_dataset.
Display Properties Measures the elapsed time from the beginning of the
operation until all objects are loaded and displayed.
Returns the status, object ID, and the number of
properties.
Preference name: ARM_display_prop.
Update Properties Measures the elapsed time from the beginning of the
operation until all objects are loaded and displayed.
Returns the status and object ID.
Preference name: ARM_update_prop.

5-4 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Display Form Measures the elapsed time from the beginning of the
operation until all objects are loaded and displayed.
Returns the status, form ID, and number of properties
in the form.
Preference name: ARM_display_form.
Update Form Measures the elapsed time from the beginning of the
operation until all objects are loaded and displayed.
Returns the status, form ID, and number of properties
in the form.
Preference name: ARM_update_form.
Cut Objects Measures the elapsed time from the beginning of the
operation until all objects are loaded and displayed.
Returns the status, number of objects cut, first object ID,
and number of properties in the form.
Preference name: ARM_cut_objects.
Copy Objects Measures the elapsed time from the beginning of the
operation until all objects are loaded and displayed.
Returns the status, number of objects cut, and first object
cut.
Preference name: ARM_copy_objects.
Paste Objects Measures the elapsed time from the beginning of the
operation until all objects are loaded and displayed.
Returns the status, number of objects cut, and first object
cut.
Preference name: ARM_paste_objects.
Check Out Objects Measures the elapsed time from the beginning of the
operation until all objects are checked out. Returns the
status, number of objects checked out, and first object
checked out.
Preference name: ARM_checkout_objects.
Check In Objects Measures the elapsed time from the beginning of the
operation until all objects are checked in. Returns the
status, number of objects checked in, and first object
checked in.
Preference name: ARM_checkin_objects.
Delete Objects Measures the elapsed time from the beginning of the
operation until all objects are deleted. Returns the
status, number of objects deleted, and first object deleted.
Preference name: ARM_delete_objects.

PLM00191 J Rich Client Interface Guide 5-5

Chapter 5 Option reference

Option Purpose
Print File Measures the elapsed time from the time the Print
command is chosen until the Print dialog box is displayed.
Returns the status and object ID.
Preference name: ARM_print_file.
Load LOV Measures the elapsed time from selecting a LOV until
all values are loaded and displayed. Returns the status,
LOV name, and number of values in the LOV.
Preference name: ARM_load_lov.
Server ARM Transactions
Logout Measures the elapsed time from clicking the Yes button
on the Exit dialog box until the process exits.
Preference name: ARM_session_logout.
Acquire License Measures the elapsed time from request to the FlexLM
server to the return of the license key. Returns the status
and checkout license key.
Preference name: ARM_acquire_license.
Structure Manager tab
UI ARM Transactions
Expand BOM view Measures the elapsed time from the beginning of the
operation until first-level components are loaded and
displayed. Returns the status and number of BOM lines
expanded.
Preference name: ARM_expand_bomview.
Expand Below BOM Measures the elapsed time from the beginning of the
view operation until all components are loaded and displayed.
Returns the status and number of BOM lines expanded.
Preference name: ARM_expandbelow_bomview.
Save BOM view Measures the elapsed time from the beginning of the
operation until the BOM view is saved. Returns the
status.
Preference name: ARM_save_bomview.
BOM Compare Measures the elapsed time from the beginning of the
operation until the BOM compare is completed. Returns
the status.
Preference name: ARM_bom_compare.
Workflow tab
UI ARM Transactions
Open inbox Measures the elapsed time to open the user’s inbox.
Returns the status.
Preference name: ARM_open_inbox.

5-6 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Open Tasks to Track Measures the elapsed time to expand the Tasks to Track
folder. Returns the status and number of tasks in the
folder.
Preference name: ARM_open_task2track.
Open Tasks to Perform Measures the elapsed time to expand the Tasks to
Perform folder. Returns the status and number of tasks
in the folder.
Preference name: ARM_open_task2perform.
Initiate Process Measures the elapsed time from clicking the OK button
until all relevant process tasks are in all task performers
inboxes. Returns the status and process name.
Preference name: ARM_initiate_process.
Perform Signoff Measures the elapsed time from clicking the OK button
to next set of process tasks in all task performer’s inboxes
or until the process is complete. Returns the status and
task name.
Preference name: ARM_perform_signoff.
Change Management tab
UI ARM Transactions
Create Change Item Measures the elapsed time from the time that all
required change item fields are completed by the user
and they click the OK or Apply button until the change
item is created and relevant tasks (first tasks) are in the
inboxes of all task performers. Returns the status and
change item ID.
Preference name: ARM_create_changeitem.
Display Change Item Measures the elapsed time from the time the change item
is opened or sent to the Change Viewer until all folders
are displayed. Returns the status and change item ID.
Preference name: ARM_display_changeitem.
Create Supersedure Measures the elapsed time from the time the Create New
Supersedure button is clicked (with items selected in
each BOM) until the supersedure folder is populated and
displayed. Returns the status.
Preference name: ARM_create_supersedure.
Display Genealogy Measures the elapsed time from the time the superseded
item is selected until the graph is displayed in the
supersedure panel.
Preference name: ARM_display_genealogy.
System Admin tab
Server ARM Transactions

PLM00191 J Rich Client Interface Guide 5-7

Chapter 5 Option reference

Option Purpose
tcfs Open/Close Measures file open or close time in both the Teamcenter
server and in the Teamcenter File Services service.
Preference name: ARM_tcfs_open_close.
tcfs Export File Measures the time to export a file from the server into
the Teamcenter File Services volume. Applies only to
the Teamcenter server.
Preference name: ARM_tcfs_export_file.
tcfs Import File Measures the time to import a file from the server from
the Teamcenter File Services volume. Applies only to
the Teamcenter server.
Preference name: ARM_tcfs_import_file.
Multi-Site Collaboration tab

Server ARM Transactions

IDSM Import Enables performance monitoring of IDSM import
transactions.
Preference name: ARM_idsm_import.
IDSM Version Enables performance monitoring of IDSM version
transactions.
Preference name: ARM_idsm_version_check.
datasync Update Enables performance monitoring of data synchronization
update transactions.
Preference name: ARM_tcsync_update.
datasync Object File Enables performance monitoring of object file data
synchronization transactions.
Preference name: ARM_tcsync_object_file.
ODS Remote Find Enables performance monitoring of ODS remote find
transactions.
Preference name: ARM_ods_remote_find.
ODS Publish Enables performance monitoring of ODS publish
transactions.
Preference name: ARM_ods_publish.
ODS Unpublish Enables performance monitoring of ODS unpublish
transactions.
Preference name: ARM_ods_unpublish.

5-8 Rich Client Interface Guide PLM00191 J


Content Management options
Option
Topic type group
Processing data
Disable S1000D unique ID
schema validation
Save state of the Publication
Structure
Publish to file system
Publish to file system location
Deploy absolute path
Deploy link prefix
Graphic classes
Graphic extensions
PLM00191 J
Option reference
Purpose
General tab
Limits the topic type groups that can be used
for creating new topics.
Preference name: ctm0TopicTypeGroup.
Maps processing data properties to content
during the XML attribute exchange in the
compose process.
Preference name: ctm0_processing_data.
Disables the schema validation check on the
attributes that comprise the unique identifier
for S1000D objects at the time the objects are
created.
Preference name:
ctm0DisableS1000DItemIdCheck.
Controls the save state of the Publication
Structure view.
Preference name:
ctm0RestoreStateOfPubStructure.
Publish tab
Enables publishing to a file system.
Preference name: publish_to_file_system.
Specifies the name of the parent folder to store
published content.
Preference name: publish_to_file_system_loc.
Specifies the file path to the folder specified in
the publish_to_file_system_loc preference for
published content.
Preference name: deploy_absolute_path.
Specifies the URL to connect to the folder storing
published content.
Preference name: deploy_link_prefix.
Graphic tab
Displays installed graphic classes for selection
during import.
Preference name: ctm0GraphicClassPref.
Filters the files that are listed for selection when
graphics are imported.
Preference name: ctm0GraphicExtPref.
Rich Client Interface Guide 5-9
Chapter 5 Option reference

Option Purpose
Graphic usages Maps graphic option usages to graphic file
extensions; provides a default selection when
graphics are imported to Content Management.
Preference name: ctm0GraphicUsagePref.
Translation graphic priority Specifies the graphic priority preference
assigned to translation orders when they are
created in Content Management.
Preference name:
ctm0_translation_graphicpriority.

Cross Probing options

Option Purpose
Relation Depth Specifies the relation traversal depth to be used in cross
Traversal probing search mechanism.
Preference name:
CrossProbing_RelationDepthTraversal.
Indirect Trace Link Enables users to retrieve indirect trace links on selected
Search objects in order to display in traceability reports.
Preference name: Indirect_Tracelink_Report.
Cross Probing Specifies the relation traversal type to be used in
Direction cross-probing search mechanism.
Preference name:
CrossProbing_RelationTraversalType.
Allowed Relations Lists the relation names available to be selected for the
Selected Relations list.
Preference name:
CrossProbing_AllowedRelationTypes.
Selected Relations Specifies the relation names that are part of the
cross-probing search mechanism.
Preference name:
CrossProbing_SelectedRelationTypes.

Dataset options
Option Purpose
Dataset Type Specifies the type of dataset associated with the default
tool.

5-10 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Default Tool A default tool is associated with each dataset type. If the
preferences do not specify the default tool for use with a
given dataset type, the dataset type is checked.
Use MIME Type to Controls how the tool is located. If this option is not
Search Application for selected, the runner application uses the file extension to
Default Tool find the tool. If selected, the runner uses the MIME type
for the tool to find the tool.
Named Reference Specifies whether named reference files are converted to
Export Options lowercase, uppercase, or whether they retain the case of
the original file name when exported.
Preference name: Dataset_File_Export_Option.

For more information about dataset types and tools, see the Business Modeler IDE
Guide.

Generic Relationship Manager (GRM) options

GRM options set the primary object type for each relation type. Teamcenter uses
this option to automatically create a relation property on the specified object type.
Note The relation-type_relation_primary preference controls only whether the
relation is valid for display under particular types in your workspace. It does
not affect the validity of attaching relations, which is implemented using
methods on relation types.
PSBOMView and ItemRevision (for items) and PSBOMViewRevision
(for item revisions) are special relations that are not affected by this
preference.

Option Purpose
Primary requirement Sets the primary object type for requirement relations;
relation either Item or Item Revision. The default setting for this
option is Item.
Preference name: TC_requirement_relation_primary.
Primary manifestation Sets the primary object type for manifestation relations;
relation either Item or Item Revision. The default setting for this
option is Item.
Preference name:
TC_manifestation_relation_primary.
Primary reference Sets the primary object type for reference relations;
relation either Item or Item Revision. The default setting for this
option is Item.
Preference name: TC_reference_relation_primary.

PLM00191 J Rich Client Interface Guide 5-11

Chapter 5 Option reference

Option Purpose
Primary master form Sets the primary object type for master form relations;
relation either Item or Item Revision. The default setting for this
option is Item.
Preference name:
TC_master_form_relation_primary.

Integration for I-deas options

If Teamcenter Integration for I-deas is available, a broad range of options are
available.
Otherwise, this page displays a message to indicate that Teamcenter Integration for
I-deas is not available.
Documentation for options on this page is provided in context in the Teamcenter
Integration for I-deas User’s Guide, which is provided separately from Teamcenter
online help.

List of values (LOV) options

Option Purpose
Value description pair display
Separator between For value-description attachments, defines the separator
value and description used between values and their descriptions and lets
you specify whether to display descriptions along with
a particular list of values.
Note A table format is used to display LOV values
and their descriptions in the rich client. The
separator is used by the thin client only.

• The default separator is the comma (,) unless

the value-description pairs are created as an
interdependent LOV.

• When the value-description pairs are created as an

interdependent LOV, the default separator is the
forward-slash character (/).

Any character can be used as a separator; however,

Siemens PLM Software recommends using one of the
following characters:
,
/
–
@
#

5-12 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
&

Preference name: LOV_value_desc_separator.

Select LOV to Show or To hide the description when value-description pairs are
Hide Description used for a list of values, choose the list of values from
the Shown list, move it to the Hidden list, and click OK
or Apply.
If the value and description are attached to two different
properties of a single type and the list of values
description is shown, the value and description are
displayed side-by-side in both lists. However, when
the selection has been made, the Description box
displays only the description, rather than the value and
description combination.
Preference name: LOV_hide_desc.

Live update options

Option Purpose
Allow Live Updates Allows live updates for selected elements.
For more information, see the Business Modeler IDE
Guide.
Preference name: BMIDE_ALLOW_LIVE_UPDATES.
Live Update Elements Lists elements that are either available for live update or
that are selected to be updated (deployed) to a database
without system downtime using the Business Modeler
IDE Live Update functionality or the Teamcenter
Environment Manager Update Database ( Perform
Live Updates Only – System downtime not required)
deployment option.
The elements in the Selected for Live Updates list can
appear in the custom template deployed to the production
database.
For more information, see the Business Modeler IDE
Guide.
Preference name: Live Update.

PLM00191 J Rich Client Interface Guide 5-13

Chapter 5 Option reference

Logging options
Option Purpose
Application logging Records events for applications, such as My Teamcenter
and Structure Manager, or for any Teamcenter utility. The
log files (.log) are stored in the operating system temp
directory.
Preference name: TC_Application_Logging.
Journaling logging Enables the creation of journal files containing a list of
programmatic interaction between the application and
other basic software modules (for example, ITK).
These journal (.jnl) files are stored in the directory specified
by the $TC_TMP_DIR environment variable. The specific
modules that participate in journaling are controlled by the
TC_Journal_Modules preference.
For more information about environment variables and
preferences, see the Preferences and Environment Variables
Reference.
Preference name: TC_Journalling.

Mail options
Option Purpose
Interval to check for Sets time interval, in minutes, between checks of the mail
new mail system. Move the slider to select the number of minutes.
The default setting for this option is 10 (ten) minutes.
Preference name: TC_mail_interval.

Manufacturing Process Management (ME) options

Option
Load Related Structures for
Plant/Process/Product
Purpose
General tab
Specifies autoloading of related process, product,
and plant structure when a process, product
or plant is opened in Manufacturing Process
Planner.
Preference name:
MSE_load_related_product_process_plant.

5-14 Rich Client Interface Guide PLM00191 J


Option
Expand First Level On Load
Default Occurrence Type
Parent Configuration Upon
Assigned Child Configuration
PLM00191 J
Option reference
Purpose
Sets expansion when loading/expanding
the tree structure when any structure
(process/plant/product) is opened in
manufacturing.
Preference name:
MEExpandFirstLevelOnLoad.
Configures the default occurrence type used for
paste, assign and drag-and-drop operations.
You can specify multiple values, each value
corresponding to a row in the table.
Set the Target Type (to) and Source Type (from)
fields to All to use the default occurrence type for
all types that are not specifically listed in the
table.
Leave the Default Occurrence Type field blank
to enforce that no default occurrence type is
used.
The values that you specify here are saved in
the MEAssignCustomizedOccurrenceType
preference.
Preference name:
MEAssignCustomizedOccurrenceType.
Specifies what parent types in bill of process
(BOP) should be configured according to its child
occurrences of controlling types.
Note If nothing is specified, parent lines, such
as operations, are not configured out by
its children.
1. Select an item, operation, or process subtype
in the Parent Type column.
2. Choose one of the following options in the
Configure Out Rule column:
• One
Parent type is configured out if any
one of its controlling occurrences is
configured out.
• All
Parent type is configured out only if
all of its controlling occurrences are
configured out.
Rich Client Interface Guide 5-15
Chapter 5 Option reference

Option Purpose

• AllLoaded
Parent type is configured out only if all
of its loaded controlling occurrences are
configured out.

• OneLoaded
Parent type is configured out if any one
of the loaded controlling occurrences is
configured out.

Preference name:
typeAndRuleForProcessConfiguration.
Show Checked-Out Objects On Indicates whether the Find Checked Out
Exit Objects dialog box is displayed when you exit
Teamcenter. The dialog box displays all objects
in the database that are checked out to the user.
Preference name:
TC_show_checkout_objects_on_exit.
Expand To Selection Indicates whether the synchronizing view
partially expands the hierarchy and highlights
the selection.
Preference name: MEExpandToSelection.
Pert tab
Auto Size Pert Boxes Turns autosizing on or off. When autosizing is
off, the size of all newly created PERT nodes
is uniform. When autosizing is on, the size of
the newly created PERT nodes is automatically
fitted to the displayed text, including allowing
for multiple lines. This preference is applied to
all PERT chart types (process, activity, and plant
PERT charts).
Preference name: PertChart.AutoSizeMode.
Configure Pert Node Text Customizes the node fields that are displayed in
the pert node; defines a formula from the node’s
fields.
1. Select an object type (process, operation,
activity, or plant type) in the Object Type
column.

2. Type a text pattern in the Pert Node Text

Pattern Column using the following format:
free-text[property-name]free-text...

5-16 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose

free-text can be any text except square

parentheses.
property-name is any Teamcenter property
name.

Preference name: Configure Pert Node Text.

Time tab
Current Time Unit Defines the ID of the time unit in which all new
time data is displayed.
Preference name: MECurrentTimeUnit.
Decimal Places Specifies the number of decimal places.
Preference name: METimeDecimalPlaces.
Colors Representing Time Specifies the colors associated with the types of
Analysis Types activities.
Preference name: MEActivityTypeColors.
Default Time Activity Specifies the default type of a new activity
created in the Activities tree table on the Times
tab for operations in Manufacturing Process
Planner application.
A new activity is created at any of the following
stages:
• Create New Activity

• Add Below (performed in the Activities table

in the Operation Time tab.)

• Add After (performed in the Activities table

in the Operation Time tab.)

Preference name: MEDefaultActivityType.

Time Reports
Time Reports Specifies which time report to use:
• Time Analysis Report

• Allocated Time Report

Preference name:
METimeAnalysisReportDefinitionID.
Report Definition Specifies the report definition used to define the
time report.
Preference name:
METimeAnalysisReportDefinitionID.

PLM00191 J Rich Client Interface Guide 5-17

Chapter 5 Option reference

Option Purpose
Stylesheet Specifies the style sheet for the time report.
Preference name:
METimeAnalysisReportDefinitionID.
Data Card
Data Card Location Specifies the location of the data card.
Preference name: METimeDataCardPath.
Time Unit Factor Specifies the factor used to convert data card
time into seconds.
Preference name: METimeDataCardPath.
Gantt tab
Behavior
Behavior Specifies the behavior of the Gantt chart, either
Show calculated duration or Full edit mode.
Show calculated duration specifies whether the
calculated duration time is displayed by default
in the Process Gantt View.
Preference name:
MEGANTTDefaultDisplayMode.
Full edit mode allows you to use drag options to
edit and modify the elements in the Gantt chart.
Preference name:
MEGANTTDefaultEditMode.
Appearance
Zoom level Specifies the X-axis zoom level that is active
when a Gantt chart is opened.
Preference name:
MEGANTTDefaultZoomLevel.
Element height Specifies the height of one element of the Gantt
chart in the navigation and the representation
area (the amount of pixels that are used for
one element). There is no space between the
elements (10 elements use 10 times the space of
one element).
Preference name: MEGANTTElementHeight.
Element color Specifies the fill color of the elements in RGB
code.
Preference name:
MEGANTTElementRGBfillColor.

5-18 Rich Client Interface Guide PLM00191 J

 Option reference

Option
Critical path element color
Selection color
Calculated duration color
Flow color
Critical path flow color
Implicit flow color
Structure Type
Type Name
Purpose
Specifies color of the critical path elements in
the Process Gantt View representation area.
Preference name:
MEGANTTDefaultMarkedColor.
Specifies the color of selected element in the
Process Gantt View representation area.
Preference name:
MEGANTTDefaultSelectionColor.
Specifies the color of the duration time bar in the
Process Gantt View representation area.
Preference name:
MEGANTTDefaultDurationTimeColor.
Specifies the color of a flow in the Process Gantt
View representation area.
Preference name:
MEGANTTDefaultFlowColor.
Specifies the color of critical path flow in the
Process Gantt View representation area.
Preference name:
MEGANTTMarkedFlowColor.
Specifies the color of an implicit flow (created by
Teamcenter to retain necessary dependencies) in
the Process Gantt View representation area.
Preference name:
MEGANTTImplicitFlowColor.
Graphics tab
Specifies the type of structure for which objects
can be set to blank or display:
• Process
• Product
• Plant
Specifies the type of object or occurrence type
that you want to blank or display.
Preference name: MEBlankDisplayTypes.

PLM00191 J Rich Client Interface Guide 5-19

Chapter 5 Option reference

NX options
Option Purpose
Show Open in NX
command Displays the Open in NX button on the rich client
toolbar.
Preference name: TC_show_open_in_nx_button.

Product Structure options

Option Purpose
Default View Type Specifies the default BOM view used when opening
Structure Manager or pasting in an assembly when more
than one BOM view is used at the site. The default
setting for this option is View.
Preference name: PSE_default_view_type.
BOM Line Title format Displays the BOM line title as your choice of any of the
for items of type BOM line properties together with fixed text in a single
column. The default setting for this option is Item.
Preference name: BOMLine_title_format.
Default Revision Rule Specifies the default revision rule that is used when
opening and printing imprecise BOM views or BOM view
revisions. The default setting for this option is Latest
Working.
For more information about revision rules, see the
Structure Manager Guide.
Preference name: TC_config_rule_name.
Pack Structure Specifies how the structure is displayed when there are
Manager display by a number of components with the same item revision.
default Options include whether the structure is displayed as one
line in Structure Manager (packed) or one line for each
component (unpacked).
Preference name: PSEAutoPackPref.
Allow Structure Specifies whether Structure Manager appearance
Manager to perform searches try remote sites.
search using
Appearance Search Preference name: TC_appr_allow_remote_query.
Engine at remote sites
Display Markups for Specifies whether the Structure Manager displays
pending edits markups for pending edits.
Preference name: PSE_Display_Pending_Edits.

5-20 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
BOM Precision Option Specifies whether BOM view revisions are created as
precise or imprecise. The default precision setting is
Imprecise.
For more information about precise and imprecise BOMs,
see the Structure Manager Guide.
Preference name: TC_BOM_Precision_Preference.

Project options
Option
Relation Propagation Rules
Include
BOMView/BOMViewRevision
for Item/ItemRevision
Purpose
Use the Exclude Relations and Include
Relations lists to specify the relation types by
which a secondary object must be related to a
primary object to be considered for propagation
to a project when the primary object is assigned
to a project.
Specifies that BOM views and BOM view
revisions are propagated when an item or item
revision is assigned to a project.
Note BOM views and BOM view revisions are
attached to items and item revisions by
attribute reference rather than relation
type.

Refresh notify options

Refresh notify options define options for configuring refresh notification behaviors
and specify behavior for the Tools®Subscribe to Refresh Notification menu
command in My Teamcenter.
Note The TC_refresh_notify and TC_refresh_notify_scope preferences must
be set to enable this functionality.
TC_refresh_notify_subscribe_to_types and
TypeName_subscribe_to_events preference values determine the types
and events for which notification is available.
For more information about preferences, see the Preferences and
Environment Variables Reference.

Option Purpose
Refresh Notify Enables display of the refresh notification button in the
lower-right corner of the Teamcenter window.
Preference name: TC_refresh_notify.

PLM00191 J Rich Client Interface Guide 5-21

Chapter 5 Option reference

Option Purpose
Interval In Minutes To Specifies the time interval for pulling refresh notification.
Pull Notifications
• The valid value is an integer.

• The value must be greater than 0.

• The unit of the value is minute.

• The default value is 15.

Note The user can use the display of the refresh
notification button in the lower-right corner of the
Teamcenter window at any time to display the
Refresh Notification dialog box to pull changed
objects.

Preference name:
TC_refresh_notify_pull_time_interval.
Maximum Number Of Specifies the maximum number of the objects that can
Objects Per Pull be put onto the refresh notification list, postponing
processing the events for other objects.
• The valid value is an integer.

• When the value is 0 or negative, there is no restriction

on the number of the objects that can be put onto the
refresh notification list.

• The unit of the value is minute.

• The default value is 0.

Note This preference is used for tuning the refresh
response performance.

Preference name: TC_refresh_notify_list_maximum.

Automatic Refresh
Waiting Time In Specifies the waiting time to start automatic refresh
Minutes Before upon receiving refresh notification. When receiving the
Refreshing Notified refresh notification, the rich client automatically starts
Objects refreshing the objects after waiting the specified time.
• The valid value is an integer.

• When the value is 0 or negative, the rich client

immediately starts refreshing the objects upon
receiving the refresh notification.

• The unit of the value is minute.

5-22 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose

• The default value is 0.

Preference name:
TC_automatic_refresh_waiting_time.
Interval In Minutes Specifies the time interval for performing each automatic
To Refresh Notified refresh.
Objects
• The valid value is an integer.

• The value must be greater than 0.

• The unit of the value is minute.

• The default value is 10.

Preference name:
TC_automatic_refresh_time_interval.
Maximum Number Of Specifies the maximum number of the objects that can be
Objects Per Refresh refreshed at one time.
• The valid value is an integer.

• When the value is 0 or negative, there is no restriction

on the number of the objects that can be refreshed
each time.

• The unit of the value is minute.

• The default value is 0.

Note This preference is used for tuning the refresh
response performance.

Preference name:
TC_automatic_refresh_list_maximum.

STEP Translator options

Option Purpose
General tab

PLM00191 J Rich Client Interface Guide 5-23

Chapter 5 Option reference

Option Purpose
Name Sequence Sets the order that person information (last name, first
name, middle name or initial) is imported and exported
from the database. Select from the following options:
last Person’s last name
delimiter ASCII character defined by the Name
delimiter option
space ASCII soft space character
first Person’s first name
middle Person’s middle name or initial
prefix_titles Person’s prefix (For example, Mr., Mrs.,
Dr.)
suffix_titles Person’s suffix (For example, Jr., Ph. D.)
Preference name: TC_name_sequence.
Part Items Defines this item type as a member of the STEP part
classification. The default setting is Item.
This is a site option.
Preference name: STEP_part_items.
Approved Status Sets this item type as approved and imports approved
STEP data into Teamcenter as in-process data. This is
accomplished by defining a list of strings that, when
detected during import, denote approved status. The
default setting is approved.
Note This option applies only to STEP AP214.

Preference name: STEP_approved_status.

Not approved status Supports the STEP AP214 data format and sets the item
type as not yet approved. This allows you to import
not-yet-approved STEP data into Teamcenter as working
data.
This is a site option.
Preference name: STEP_not_yet_approved_status.
Spec tab
Material specification Maps Teamcenter dataset types to the STEP CAD file
classification. The default setting is UGMASTER.
This is a site option.
Preference name: STEP_material_specification_pref.

5-24 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Process specification Maps Teamcenter dataset types to the STEP process
specification classification. There is no default setting
for this option.
This is a site option.
Preference name: STEP_process_specification_pref.
Surface finish Maps Teamcenter dataset types to the STEP surface
specification finish specification classification. There is no default
setting for this option.
This is a site option.
Preference name:
STEP_surface_finish_specification_pref.
Design specification Maps Teamcenter dataset types to the STEP design
specification classification. The default setting is Text.
This is a site option.
Preference name: STEP_design_specification_pref.
Drawing Maps Teamcenter dataset types to the STEP drawing
classification. The default setting is UGPART.
This is a site option.
Preference name: STEP_drawing_pref.
CAD filename Maps Teamcenter dataset types to the STEP CAD file
classification. The default setting is UGMASTER.
This is a site option.
Preference name: STEP_cad_filename_pref.
Make or buy Defines the item revision master attribute that stores the
STEP make_or_buy value for item revisions imported
via the STEP Translator. There is no default setting for
this option.
This is a site option.
Preference name: STEP_make_or_buy_attr.
Import directory Displays the Import dialog box used to select the import
directory to be used when importing data via the STEP
Translator. Sets location of STEP physical file.
Preference name: STEP_import_directory.
Export directory Displays the Export dialog box used to select the export
(destination) directory used when exporting data via the
STEP Translator. This is where the STEP physical file
is written.
Preference name: STEP_export_directory.

PLM00191 J Rich Client Interface Guide 5-25

Chapter 5 Option reference

Option Purpose
Export data format Sets STEP data format used for the export operation.
This preference accepts the values AP203 or AP214.
Preference name: STEP_export_data_format.
SysAdmin tab
Organization ID Defines an organizational identifier for your enterprise.
There is no default setting for this option.
Preference name: TC_organization_id.
Name delimiter Defines an ASCII character used as a delimiter in the
person name string. Teamcenter stores the entire person
name (last name, first name, middle name or initial)
as a single string in the database. However, the STEP
Translator requires this information to be handled
separately. The delimiter partitions the person name
such that another application can break this single string
into multiple strings. The default name delimiter is a
comma (,).
Preference name: TC_name_delimiter.

Security options
Option Purpose
Security Logging Enables or disables security logging for the entire
site. Security logging creates a record of denied access
to objects. The default setting for this option is ON,
which enables security logging and writes data to the
TC_LOG/security.log file.
Preference name: TC_Security_Logging.

Status indicators
Option Purpose
Status Indicators Specifies the indicator used in Schedule Manager for
indicated state and status combinations, such as In
Progress/Needs Attention or In Progress/Late.

5-26 Rich Client Interface Guide PLM00191 J

 Option reference

System options
Option Purpose
Maximum number of Sets the number of times Teamcenter should retry locking
retries an object before reporting an error. The default setting
for number of retries is 3 (three).
Preference name: TC_max_number_of_retries.
Retry Time Interval Sets time interval in seconds between each object locking
retry. The default setting for retry time interval is 5 (five)
seconds.
Preference name: TC_retry_time.

Systems Engineering options

Option Purpose
Trace Link Mode Configures trace link features for applications, such
as Systems Engineering, My Teamcenter, Structure
Manager, and Multi-Structure Manager.
Preference name: Tracelink_Edit_enabled.
Indirect Trace Link Enables users to retrieve indirect trace links on selected
Search objects in order to display in traceability reports.
Preference name: Indirect_Tracelink_Report.
Left-Right Trace View Sets the display for the Defining Object and Complying
Object panes of the Traceability view.
When this option is selected, the Traceability view
displays the Defining Object pane on the left and the
Complying Object pane on the right (horizontally).
When this option is not selected (the default value), the
Traceability view displays the Defining Object pane on
the top and the Complying Object pane on the bottom
(vertically).
Preference name: SE_Trace_Report_Layout.
Apply Templates (for Enables viewing and editing of requirement content in
embedded editing) an embedded Word window in the View/Edit pane.
When this option is selected, the View/Edit pane displays
the content specified by the document template that is
associated with the requirement object type.
When this option is not selected, the View/Edit pane
displays only the body text of the requirement.
Preference name: Apply_templates.

PLM00191 J Rich Client Interface Guide 5-27

Chapter 5 Option reference

Option Purpose
Browse Clear Text When selected, the MS Word view displays in plain text
context.
Preference name:
RequirementBrowseClearText_enabled.
Quick Create Panel When selected, the Quick Create bar is enabled, which
saves time when creating requirement objects.
Preference name: REQ_quick_create_panel.
Calculate When selected, Defining Objects and Complying
Defining/Complying Objects properties for SpecElement, SpecElement
Objects Revision, Requirement Spec, RequirementSpec
Revision, Functionality, and FunctionalityRevision
objects as well as BOM lines are displayed by default
with a trace link relation.
To see the properties for other types of business objects,
set the Fnd0RuntimeTraceProperty type constant to
True in the Business Modeler IDE.
Preference name: REQ_calculate_def_comp_objects.
Keywords to Import When you import requirement specifications from
Microsoft Word, Systems Engineering uses the Word
document’s outline level styles to parse the document into
a hierarchy of parent, child, and sibling requirements. By
configuring the keywords that occur in the document, you
can further control the separation of requirements.
Preference name: REQ_import_keywords.

Work Breakdown Structure (WBS)

A work breakdown structure (WBS) is a way for managers to provide a quick
reference to a task in the breakdown structure. This makes it easy for all those
working on the project to find their assigned tasks and indicate the completion
status of each.
Click Define WBS Format to display the Define WBS Format dialog box.
For more information about defining the WBS code format, see the Schedule
Manager Guide.
Preference name: SM_WBS_INITIAL_PREF.

Computer-Aided Engineering (CAE) Tools options

CAE tools options (preferences) configure and control the behavior of the Teamcenter
simulation process management features.

5-28 Rich Client Interface Guide PLM00191 J

 Option reference

Batch meshing options

Option Purpose
General tab
CAE Output Directory Defines the root directory under which batch
meshing is performed.
Preference name:
CAE_batch_meshing_root_dir.
Meshing Tools Defines the meshing tools that can be chosen for
batch meshing operations. To define the tools:

1. Click the button in the bottom-right

corner of the Meshing Tools box.
A box and buttons to add, modify, and
sequence the tools appears.

2. In the box, type a string value for the

meshing tool and click .

You can use the up arrow and down arrow to

change the order in which a tool appears in the
list or you can use the button or the button
to remove tools from the list or modify the name
of the tool.
Preference name: CAE_batch_meshing_tools.
Default Meshing Tool Specifies the default tool used for batch meshing.
If you do not select a default tool, the system
assigns the first tool in the Meshing Tools list
as the default tool.
Preference name:
CAE_default_batch_meshing_tool.
Always Re-Mesh Specifies whether the system automatically
re-meshes the input data regardless of whether
it is up to date. If this option is not selected, the
system only re-meshes if the input data is not
up to date.
Preference name: CAE_always_remesh.
Always Create New CAEModel Specifies whether the system always creates a
new CAEModel item to hold the batch meshing
output or whether an existing CAEModel item
is used.
Preference name:
CAE_batch_meshing_always_create_new.
Tools Input Information tab

PLM00191 J Rich Client Interface Guide 5-29

Chapter 5 Option reference

Option
Input Geometry
Parameter/Criteria Files
Startup Scripts/Server Info
Tools Output Information tab
Tool Information for Output
Files
Set CAEModel Attributes
Purpose
Specifies the dataset type and reference type for
the geometry associated with each meshing tool.
Preference name: CAE_input_geometry.
Maps each batch meshing tool to a parameter
item, item revision, and dataset and also to a
criteria item, item revision, and dataset.
Preference name:
CAE_meshing_params_criteria_source.
Maps each batch meshing tool to a corresponding
startup script.
A sample startup script,
sample_batchmesher_script.bat, is included
in your Teamcenter installation and is located in
the data folder in your Teamcenter installation
directory.
Preference name: CAE_startup_scripts.
Defines the file extension, dataset type,
reference, and relation type for the output of
each batch meshing tool.
Preference name:
CAE_batch_meshing_import_file_extensions.
Specifies values for selected CAEModel item or
item revision attributes for a batch meshing tool.
Preference name:
CAE_batch_meshing_attribute.

General options
Option Purpose
Significant Relations tab
Significant Relationship Types Defines significant relationship types for
for CAEModel CAEModel and its subtypes.
Preference name:
CAE_significant_relation_types_for_CAEModel.
Significant Relationship Types Defines significant relationship types for
for CAEAnalysis CAEModel and its subtypes.
Preference name:
CAE_significant_relation_types_for_CAEAnalysis.
Highlights tab

5-30 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Action Specifies the highlight color used by Simulation
Process Management operations to indicate an
action is needed on an object.
Preference name:
CAE_action_highlight_color.
Caution Specifies the highlight color used by Simulation
Process Management operations to indicate
caution is needed on an object.
Preference name:
CAE_cautionary_highlight_color.
No Action Specifies the highlight color used by Simulation
Process Management operations to indicate no
action is needed on an object.
Preference name:
CAE_no_action_highlight_color.
Out of Scope Specifies the highlight color used by Simulation
Process Management operations to indicate an
object is not considered by the operation.
Preference name:
CAE_out_of_scope_highlight_color.

Inspector options
Option
Inspector Execution Summary
Dataset Name
Product Structure tab
Product with no Model
Missing Model Components
Purpose
General tab
Specifies the name of the dataset in which the
Inspector Summary value is saved as a named
reference.
Preference name:
CAE_Inspector_summary_dataset_name.
Determines whether product BOM line is not
linked to any CAEModel BOM line in the model
structure.
Preference name:
CAE_Product_Structure_Default_Actions.
Determines whether the number of BOM lines
for a CAEModel item revision is less than the
number of BOM lines of the linked product item
revision.
Preference name:
CAE_Product_Structure_Default_Actions.

PLM00191 J Rich Client Interface Guide 5-31

Chapter 5 Option reference

Option
Model Structure tab
Model With Different Product
Revision Target
Model With No Product
Extra Model Components
Root Node Default Action
Default Root BOMLine Action
Default New Model Action Item
Type
Purpose
Determines if the CAEModel BOM line is linked
to a different revision of the product BOM line.
Preference name:
CAE_Simulation_Structure_Default_Actions.
Determines if the CAEModel BOM line is not
linked to any product BOM line in the product
structure.
Preference name:
CAE_Simulation_Structure_Default_Actions.
Determines if the number of BOM lines for
a CAEModel item revision is more than the
number of BOM lines of the linked product item
revision.
Preference name:
CAE_Simulation_Structure_Default_Actions.
Root Node tab
Select a BOM line action:
Do Nothing Leaves the root
CAEModel item revision
as is.
Use Revised Model Revises a root CAEModel
item revision and adds it to
the BOM structure.
Use New Model Creates a root CAEModel
item revision and adds it to
the BOM structure.
Preference name:
CAE_Root_BOMLineAction.
Select an appropriate item type, such as
CAEModel.
Preference name:
CAE_Root_Item_Type_Preference.

Package location options

Option Purpose
Site Identifies the item revision used to manage the
site-level CAE package definitions.
Preference name:
CAE_package_template_site.

5-32 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Group Identifies the item revision used to manage the
group-level CAE package definitions.
Preference name:
CAE_package_template_group.
User Identifies the item revision used to manage the
user-level CAE package definitions.
Preference name:
CAE_package_template_user.

Simulation tool options

Option Purpose
CAE Simulation Specifies the dataset name of the CAE simulation tool.
Tool Configuration
Dataset Name Preference name:
CAE_simulation_tool_config_dsname.
Enable Context Specifies the context-based menu for simulation tool
Based Menu for launch.
Simulation Tool
Launch Preference name: CAE_enable_context_based_menu.
My Favorite Specifies the simulation tools configured as favorite tools.
Simulation Tools
Preference name: CAE_my_favorite_simulation_tools.
Simulation Tools in Specifies the simulation tools configured to appear in the
Toolbar CAE Manager toolbar.
Preference name: CAE_my_favorite_simulation_tools.

StuctureMap options
Option Purpose
Data Map Files Specifies the UID of the item revision used to manage the
Location data map definition files.
Preference name: CAE_datamap_files_location.
Create relationship Specifies whether to create relationships between
between CAEModel CAEModel objects and StructureMap objects.
and StructureMap
Preference name:
CAE_create_GeneratedByRelationship.
Persist StructureMap Specifies whether the StructureMap object is retained.
log
Preference name: CAE_persist_StructureMapLog.

PLM00191 J Rich Client Interface Guide 5-33

Chapter 5 Option reference

Option Purpose
StructureMap Log Specifies the name of the dataset used to store the process
Dataset Name log file generated by the execution of a data map or a
StructureMap operation.
Preference name:
CAE_structuremap_log_dataset_name.
Enable ancestor data Specifies whether ancestor data mapping is enabled.
mapping
Preference name: CAE_enable_AncestorMapping.
Maximum levels Specifies from 0 to 99 levels of ancestor data mapping.
of ancestor data
mapping Preference name: CAE_ancestorMapping_level.

Calendar options
Calendar options enables you to select a base calendar type and specify the day of
the week on which each week must start in your calendars.

Default Base Calendar

Option Purpose
Default Base Calendar Enables you to specify one of the following base calendar
types:
• Standard

• Night Shift

• 24 Hours

Preference name:
Default_Base_Calendar_Preference.

Start of Week
Option Purpose
Start of Week Enables you to specify the day of the week on which each
week must start in your calendars.
Preference name:
Calendar_StartOfWeek_Preference.

Change Management options

Change management is the process of controlling changes to a product’s definition
and configuration. It compares the selected affected item with the associated
problem line in the change by displaying two panes. The left pane displays

5-34 Rich Client Interface Guide PLM00191 J

 Option reference

modifications to the affected item assembly, the right pane displays modifications
from the problem item assembly. You can change the default comparison colors
using the BOM tracing option.
For more information about comparing structures under change management using
Structure Manager, see the Structure Manager Guide.

BOM Tracking
Option Purpose
BOM Tracking Allows you to define the color associated with different
time analysis types. Each type of comparison has
a corresponding color and icon. When viewing the
comparisons between two objects in the viewer, the
different parts of the revisions are displayed in different
colors, indicating that they have been added, canceled,
moved or reshaped. Colors also indicate quantity change,
note change, variant change, and common part types.
• Add
Preference name: CM_color_of_add.

• Cancel
Preference name: CM_color_of_cancel.

• Move
Preference name: CM_color_of_moved.

• Reshape
Preference name: CM_color_of_reshaped.

• Quantity Change
Preference name: CM_color_of_quantity_change.

• Note Change
Preference name: CM_color_of_notechange.

• Variant Change
Preference name: CM_color_of_variantchange.

• Common Part
Preference name: CM_color_of_common.

PLM00191 J Rich Client Interface Guide 5-35

Chapter 5 Option reference

DesignContext options
Many of the options in the RDV feature and DesignContext application can be
customized to match your company’s business practices.
For more information about preferences, see the Preferences and Environment
Variables Reference.
While most RDV and DesignContext preferences are site-based and must be set by a
privileged user, there are also a number of user-based options that you can set using
the Options command on the Edit menu.

General
Option Purpose
Automatically Specifies the maximum number of target appearances
determine variant for the Valid Overlays Only button on the Filter
rule set if a maximum Configuration pane. This option limits the processing
of Target Appearances time spent determining and evaluating the set of variant
and Relevant Options rules that configure a set of target appearances.
• Target Appearances
Preference name: PortalDesignContext
SetVariantRulesMaxTargetAppearances.

• Relevant Options
Preference name: PortalDesignContext
SetVariantRulesMaxVariantRules.
Maximum Number of Specifies the maximum number of components (for
Matches Allowed for example, work parts, change items, or workflow jobs)
Wildcard Searches that a search can match. Input provided in the Context
and Structure Manager Definition pane may cause new objects to be loaded.
Searches If you type wildcard characters in these boxes when
performing a product item search, response times may
be unacceptable.
Specifies the maximum number of assembly components
that a Structure Manager search can match. Input
provided in the Context Configuration window can cause
new objects to be loaded. If you type wildcard characters
in these boxes, response times may be unacceptable.
• Wildcard Searches
Preference name: PortalDesignContext
MaxMatchingObjects.

• Structure Manager Searches

Preference name: PortalDesignContext
MaxMatchingBOMLines.

5-36 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Product Structure Specifies product structure interoperability for CAD and
Interoperability Teamcenter lifecycle visualization.
Options
Prune Tree Makes branches of the structure that
do not contain any components invisible
to the application to which the context
is being loaded. This is essential for
extremely large structures, as it decreases
load time.
Suppress Used in conjunction with the Prune Tree
Components command to suppress the loading of
potential BOM line components other
than those explicitly selected. This is
beneficial, because you may not know that
the selected BOM line is, for example, an
assembly with 180,000 components.
Hide Used in conjunction with the Prune Tree
Components command to load but not display the
components of a selected assembly.
Preference name:
PortalDesignContextVISbookmarkType.
Show Open in Specifies whether the Open in Structure Manager
Structure Manager command is displayed in the DesignContext application
Command interface.
Preference name: TC_show_open_in_pse_button.
Select Search Engine Specifies the search engine used for product structure
for Product Structure searches. Available options are;
Searches
• UG/NX-Based QPL Search Engine

• JT-Based QPL Search Engine

• Appearance-Based Search Engine

• Cacheless Search Engine

Preference name:
PortalDesignContextSearchEnginePreference.
Refine Cacheless Specifies whether to use TruShape data when performing
Search searches.
Preference name: RDV_QSEARCH_REFINE.

PLM00191 J Rich Client Interface Guide 5-37

Chapter 5 Option reference

Option Purpose
Structure Context Specifies whether newly added component instances are
Object Entries included as structure context object entries.
• Include newly added Component Instances
Preference name:
DesignContextLoadRDVContextObjectMode.

• Automatically synchronise and prune

DesignContext selections with Structure
Manager
Preference name:
DesignContext_PSE_Synchronization.

Product Context
Option Purpose
Product Context Defines the list of displayed product context properties.
Properties
Preference name:
PortalDesignContextProductContext
ColumnsHiddenPref.

Product Item
Option Purpose
Product Item Defines the list of displayed product item properties.
Properties
Preference name: PortalDesignContextProductItem
ColumnsHiddenPref.

General options
General options (preferences) configure and control overall Teamcenter behavior.
The following types of general options can be set using the Options command on
the Edit menu:
• UI options that control workspace behaviors, such as at what point in a process
data is saved.

• Item options and item revision options that customize the way items and item
revisions are displayed in My Teamcenter.

• Checkin/checkout options, such as enabling and disabling auto checkout and

specifying the operating system directory that will contain exported files.

• Alias options for DesignContext.

5-38 Rich Client Interface Guide PLM00191 J

 Option reference

Checkin/checkout options
Option Purpose
General tab
Remove file on check Deletes (removes) previously exported files from the
in operating system directory specified by the Check out
directory option.
The default setting for this option is YES (remove file at
checkin or cancel checkout).
Preference name: TC_remove_file_on_check_in.
Check out directory Specifies the operating system directory that contains
the exported files.
This option accepts a single string as a value. This string
must be the full operating system directory path or a
null value. The null value sets export of the files to the
current working operating system directory. Default
setting is null.
Preference name: TC_check_out_dir.
Export files on check Exports files to the operating system when a dataset is
out checked out.
By default, this option is not selected (do not export files).
Preference name: TC_checkout_and_export.
Sys Admin tab
Auto check out Enables or suppresses automatic implicit checkout
of non-NX datasets. Implicit checkout automatically
prevents users from gaining write access to a non-NX
dataset if another user has opened it. The default setting
is ON (auto checkout enabled).
This is a site preference.
Preference name: TC_Auto_Checkout.

Identifier options
Option Purpose
Length of Context Defines the maximum number of characters for the
context name. If set to 0, only the alias ID is displayed.
The default length is seven (7) characters.
Preference name: IdentifierLengthPref.
How the context Defines the character used to separate the context name
should be attached and alias ID.
Preference name: IdentifierContextPref.

PLM00191 J Rich Client Interface Guide 5-39

Chapter 5 Option reference

Item options
Option Purpose
General tab
Separator between Defines the character used to separate items and item
Item and Item Revision revisions. The default separator is the forward slash (/)
character.
Preference name: FLColumnCatIVFSeparatorPref.

Relations for item

Select item type Allows you to select the item type to which the paste
region applies.
Preference name: Item_DefaultChildProperties.
Default paste relation Sets the default paste relation for the specified item type.
When an object from the clipboard is pasted to an item or
item revision, this option defines the type of relationship
that is created between the pasted object, for example, a
dataset and the item.
Preference name: Item_default_relation.
Shown relations for Determines which relations are displayed (shown)
item after an item of the specified type is expanded in
My Teamcenter. Relation types can be selected and
moved between the Available and Selected lists by
double-clicking or using the Add and Remove buttons.
Note To include subclasses in the list of relations,
the value Item must be specified for the
TYPE_DISPLAY_RULES_list_types_of_subclasses
site preference. Site preferences are set by your
Teamcenter administrator.
Related Object tab
Shown item relations for pseudo-folder
Select item type Allows you to select the item type to which the paste
region applies.
Preference name: Item_PseudoFolder.
Shown item relations Lists which relations of a specified item type are
for pseudo-folder displayed (shown) as pseudofolders. Any relations listed
in the equivalent Shown relations for item option, but
not listed in the corresponding Shown item relations for
pseudo-folder option are displayed directly under the
parent object without the intermediate pseudofolder.
Display tab
Revision display filter

5-40 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Select item type Allows you to select the item type to which the display
filter applies.
Preference name: Item_rev_display_order.
Display order Defines whether items of the specified type are displayed
in ascending or descending order in the tree and Details
pane.
Preference name: Item_rev_display_order.
Show all revisions Displays all revisions of an item, regardless of status.
Preference name: Item_rev_display_all.
Show displayable Enables you to filter the display of item revisions by
revisions only applying filtering rules.
Preference name: Item_rev_display_rule.
Specify the order Specifies the filtering to be applied to revisions associated
and rule for revisions with the selected item type. For example, you can filter
display the item revision display so that only released item
revisions with production status matching the Any
status, working configured revision rule display by
performing the following steps:

1. Click the Add button to the right of the table.

Teamcenter displays an active row in the table.

2. Choose Configured by from the list in the Rule

column.

3. Choose Any Status;Working from the list in the

Condition column.

4. Click Apply.

You can define a limit for the number of item revisions

displayed by typing a positive integer value in the Limit
column.
Preference name: Item_rev_display_rule.

Item revision options

Option Purpose
General tab
Separator between Defines the character used to separate the item/item
Item/ItemRevision and revision and name. The default separator is a dash (-)
name character.
Preference name: FLColumnCatObjSeparatorPref.

PLM00191 J Rich Client Interface Guide 5-41

Chapter 5 Option reference

Option Purpose
Separator between Defines the character used to separate the item/item
Item/ItemRevision and revision and sequence ID. The default separator is a
sequence id semicolon (;) character.
Preference name: FLColumnCatSeqSeparatorPref.
Relations for Item Revision
Select item revision Allows you to select the item revision type.
type
Preference name:
ItemRevision_DefaultChildProperties.
Default paste relation Sets the default paste relation for the specified item
revision type. When an object from the clipboard is
pasted to an item or item revision in My Teamcenter, this
option specifies the type of relationship that is created
between the pasted object and the item revision.
Preference name: ItemRevision_default_relation.
Shown relations for Determines which relations should be displayed (shown)
Item Revision after an item of the specified type is expanded in
My Teamcenter. Relation types can be selected and
moved between the Available and Selected lists by
double-clicking or using the Add and Remove buttons.
Note To include subclasses in the list of relations,
the value ItemRevision must be specified as a
displayable subclass.
For more information about configuring this
display, see the Business Modeler IDE Guide.
Related Object tab
Shown item revision relations for pseudo-folder
Select item revision Allows you to select the item revision type.
type
ItemRevision_PseudoFolder.
Shown item relations Lists which relations of a specified item revision type are
for pseudo folder displayed (shown) as pseudo folders in My Teamcenter.
Any relations listed in the equivalent Shown relations for
item revision option, but not listed in the corresponding
Shown item revision relations for pseudo folder option
are displayed directly under the parent object without
the intermediate pseudo folder.
ItemRevision_PseudoFolder.

User interface (UI) options

Option Purpose
General tab

5-42 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Insert with selection Specifies the folder in which new workspace objects are
placed. Choose one of the following options:
• All Selected Folders

• First Selected Folders

• Newstuff Folders

• None

Choosing the None option causes the item to be saved in

the database but not displayed in My Teamcenter.
Preference name: WsoInsertSelectionsPref.
Insert without Specifies the default folder that is referenced when no
selection object is selected. Choose one of the following options:
• Newstuff Folders

• Home Folder

• None

The default setting for this option is Newstuff Folders.

Preference name: WsoInsertNoSelectionsPref.
Tree displaying order Allows you to display the items in the tree in ascending
or descending alphabetical order.
Preference name: treeDisplayOrder.
Sys Admin tab
Display Name Specifies whether the displayable names or real property
names of objects are displayed in the interface.
Preference name: TC_display_real_prop_names.
Dataset version purge Specifies the number of old dataset versions stored in
limit the database. When this number is exceeded, the oldest
dataset version is deleted.
The default setting for this option is 3 (three) datasets.
Preference name: AE_dataset_default_keep_limit.

Graphical BOM Compare options

The graphical BOM compare options are available for graphical history settings.
For more information understanding graphical comparisons with Structure Manager,
see the Structure Manager Guide.

PLM00191 J Rich Client Interface Guide 5-43

Chapter 5 Option reference

Graphical History options

Option
Initial Position Of Sliders
Show common parts
Purpose
Graphical History
Sets the initial position of the slider controls. If set
to 100, only the affected assembly is displayed. If
set to 0, only the problem assembly is displayed.
Any number in between 0 and 100 displays both the
added and canceled parts.
Preference name:
CM_initial_position_of_sliders.
By default, the common parts that remain
unchanged between problem and affected
assemblies are not displayed in the graphical
viewer, making it easier to distinguish the changed
parts and hastening loading time. Displaying
common parts allows you to more easily see the
changes in context of the larger assembly.
Preference name: CM_show_common_parts.

Multi-Site Collaboration options

Most Multi-Site Collaboration options are implemented as site options, and therefore
must be set by a user with dba privileges.
For more information, see the Multi-Site Collaboration Guide.

Integrated Directory Services Manager (IDSM) options

Option Purpose
IDSM Permitted Sites Specifies the sites that can access your data.
Note This is a site option.

Preference name: IDSM_permitted_sites.

IDSM Restricted Sites Specifies the sites that are prohibited from accessing
your data.
Note This is a site option.

Preference name: IDSM_restricted_sites.

5-44 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
IDSM Permitted Specifies the sites that are authorized to transfer
Transfer Sites ownership of objects owned by the site served by an IDSM
server. If this option is not defined, transfer of ownership
is not permitted from this site.
Note This is a site option.

Preference name: IDSM_permitted_transfer_sites.

Import remote options

Option Purpose
General tab
Transfer
Transfer Ownership Specifies that site ownership is transferred to the target
site. When the this option is not set, the originating site
retains ownership.
Note Siemens PLM Software recommends that you
retain the default setting (unset) for this option.
Perform Import/Export Runs the remote import operation in the background,
in Background allowing you to continue using Teamcenter while the
operation runs.
You can use import in background to import only a single
object; therefore, Siemens PLM Software recommends
that you use this option for importing an entire assembly
by selecting a parent item rather than individual parts.
While the background operation runs, you can perform
other Multi-Site Collaboration operations including a
nonbackground remote import of other objects. Only
one Multi-Site Collaboration user license is used when
multiple simultaneous operations are running.
Note When this option is set, the remote import
progress indicators are not available.
Item
Include All Revisions Exports all revisions. When transferring site ownership,
this is the only available option.
Latest Revision Only Exports the latest revision regardless of whether it is a
working or released revision.
Latest Working Exports only the latest working (non-released) revision.
Revision Only
Latest Working/Any Exports the latest working revision, if any; if no working
Release Status revision, the latest released revision with any release
status is exported.

PLM00191 J Rich Client Interface Guide 5-45

Chapter 5 Option reference

Option Purpose
Latest Any Release Exports the latest released revision with any release
Status status.
Selected Revision(s) Exports only the revisions selected in My Teamcenter.
Only This option is not valid for remote import.
Specific Release Exports only the latest revision with the given release
Status Only status selected from the list.
General
Note These options allow you to filter objects that you want to include in or
exclude from the import/export operation. These options are normally
applied to subobjects within items, such as revisions, forms, and datasets.
These options are not available when transferring site ownership.
Include Modified Includes an object only if it was modified since the last
Objects Only time it was exported to the target sites. For example, if
only the specification dataset was modified, it is included
and the remaining items are excluded. When exporting
to multiple target sites, an object is exported if it was
modified since the last export to any site on the list.
Exclude Excludes objects that are protected (via Access Manager)
Export-Protected from import/export to remote sites. For example, if
Objects revisions of an item do not have export and/or import
privileges granted at the owning site, you will receive an
error when attempting to import/export the item unless
this option is set.
Note If you do not know the privileges assigned to a
remote item and its reference objects, attempt to
import/export with the Exclude Export-Protected
Objects option unset. If an error message
indicating no export or import privilege is
displayed, set the option and import/export the
objects again.
Exclude Folder Excludes all objects that are contained in folders to be
Contents exported.
Save
Save All Options as Saves all currently selected options as user preferences.
Default The saved options serve as the default values on
subsequent rich client import or export operations.
Dataset
Include All Versions Includes all dataset versions with each dataset selected
for import or export. When this option is not selected,
only the latest version of each selected dataset is
imported/exported.

5-46 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Include All Files Includes all underlying operating system files (named
references) with each dataset selected for import or
export.
If you do not select this option, only the dataset metadata
is imported or exported. If you import or export a dataset
without including the named references, you can display
it in My Teamcenter, but you cannot open it with the
associated software application (tool).
Note When transferring ownership, the Include All
Versions and Include All Files options are
automatically set to ensure that the new owner
receives all data associated with the exported
objects.
Product Structure
Include Entire BOM Includes all components if the selected item is an
assembly. Use the revision selectors to choose which
revision to export with the selected item and its
component items, if applicable. You can choose only one
revision selector.
Note Importing and exporting items when the Include
Entire BOM option is set allows you to specify
other options about the import/export of the
assembly and its components.
Transfer Top-Level Transfers site ownership of the selected assembly item
Item Only and exports all components without transferring site
ownership. This option is enabled only if the Transfer
Ownership option is selected.
Exclude Excludes all components that have no TRANSFER_OUT
Transfer-Protected and/or TRANSFER_IN privileges granted at the owning
Components site. If this option is not selected and a transfer-protected
component is found, the import/export operation fails.
This option is enabled only if the Transfer Ownership
option is selected.
Exclude Excludes all components that have no EXPORT and/or
Export-Protected IMPORT privileges granted at the owning site. If this
Components option is not selected and an export-protected component
is found, the import/export operation fails.
Note If you do not know the protection applied to
components at the owning site, attempt the
import/export with the component-related
option unset. If you receive an error message
indicating lack of privilege on a component, set
the appropriate component-related option and
attempt the import/export operation again.
Session

PLM00191 J Rich Client Interface Guide 5-47

Chapter 5 Option reference

Option Purpose
Preview With Report Performs a dry run of the import or export operation
and generates a report of the objects that will be
exported/imported if the actual operation is performed.
The report may also contain potential errors that will
occur in the actual operation.
Generate Performs the actual import/export operation
Import/Export Report and generates a report of the objects that are
exported/imported.
Continue on Error Errors on optional objects, such as those attached by
manifestation or reference relationships are ignored,
allowing the import/export operation to continue.
Advanced tab
Relationship
Include and Exclude Define the types of related objects to be imported and
lists exported. Some relations (Specification, Requirement,
Master, and Form) cannot be excluded—they are essential
pieces of the object being imported or exported. However,
other relations can be explicitly included or excluded.
Synchronization Notification
Synchronize Synchronizes replica data automatically when the
Automatically master copy is modified. This option requires that the
Subscription Manager be running at both the owning and
replica site.
Synchronize in Batch Synchronizes the replace when the data_sync batch
Mode utility is run at the owning site. This is the default option.
Notify by E-Mail Notifies the user by e-mail if the master copy is modified.
This option requires that the Subscription Manager be
running at both the owning and replica site.
NX Part Families tab
Assemblies With Part Family Member Components
Include part family Includes part family members when you import or export
members an assembly containing part family members.
Include part family Includes part family templates rather than the part
templates instead of family members when you import or export an assembly
members containing part families.
Include both the part Includes part family members and templates when you
family members and import or export an assembly containing part families.
their templates
Include neither the part Includes neither part family members nor templates
family members nor when you import or export an assembly containing part
their templates families.
Part Family Templates
Include part family Includes part family members when you import or export
members a part family template.

5-48 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
Part Family Members

Include part family Includes part family templates when you import or export
templates a part family member.

Multi-Site Collaboration miscellaneous options

Option Purpose
Enter transfer Specifies the temporary directory used by Multi-Site
directory Collaboration when performing import/export operations.
The default setting for this option is \tmp.
Warning In the event of a system crash the contents
of the \tmp directory are normally deleted
when the system is rebooted, deleting any
import/export data that may be required for
export recovery. Therefore, Siemens PLM
Software recommends that you change this
setting.

Preference name: TC_transfer_area.

Publishable Classes Defines the Teamcenter classes that can be published by
the Object Directory Service (ODS).
For more information about ODS, see the Multi-Site
Collaboration Guide.
Note This is a site option.

If this option is not defined, only items are published.

If the preference is set to a single value of NONE,
publication is disabled. However, other Multi-Site
Collaboration operations can still be performed.
The following classes are currently supported: Item,
Dataset, Form, and Folder. Item revisions cannot
be published by themselves (publishing a revision will
publish its item) and should not be included in the list.
Preference name: TC_publishable_classes.

NX part family options

Option Purpose
Publishing assemblies containing part family member component options

PLM00191 J Rich Client Interface Guide 5-49

Chapter 5 Option reference

Option Purpose
Publish part family Specifies that part family member components are
members published when you publish assemblies.
Preference name:
Tc_publish_pfdata_with_assemblies.
Publish part family Specifies that part family templates, rather than part
templates instead of family members, are published when you publish
members assemblies.
Preference name:
Tc_publish_pfdata_with_assemblies.
Publish both part Specifies that both part family members and their
family members and associated templates are published when you publish
templates assemblies.
Preference name:
Tc_publish_pfdata_with_assemblies.
Publish neither part Specifies that neither part family members nor their
family members nor associated templates are published when you publish
templates assemblies.
Preference name:
Tc_publish_pfdata_with_assemblies.
Publishing part family template options
Publish part family Specifies that when a part family template is published,
members also the corresponding part family members are also
published.
Preference name:
Tc_publish_pfmembers_with_pftemplate.
Publishing part family member options
Publish part family Specifies that when part family members are published,
templates also the corresponding part family template is also published.
Preference name:
Tc_publish_pftemplate_with_pfmember.

Object Directory Services (ODS) options

Option Purpose
General tab

5-50 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose
ODS Searchable Sites Specifies the searchable sites that appear in the Remote
Query Options dialog box.
This option defines the ODS sites that are searched
during the session or until the searchable sites list is
changed. The combination of this option and the ODS
Searchable Sites Excluded option define a complete list
of all possible ODS sites that can be searched.
Preference name: ODS_searchable_sites.
ODS Searchable Sites Specifies the searchable sites that appear in the Remote
Excluded Sites to Search - Exclude list.
Preference name: ODS_searchable_sites_excluded.
Sys Admin tab
ODS Site Specifies the default ODS (Object Directory Services) site.
Preference name: ODS_site.
ODS Permitted Sites Specifies sites that are allowed access to the ODS
database.
Preference name: ODS_permitted_sites.
ODS Restricted Sites Specifies sites that are not allowed access to the ODS
database.
Preference name: ODS_restricted_sites.

Search options
The general search options include settings for queries, wildcards, multiple entries,
and general defaults.

Favorite Business Object Type options

Option Purpose
Business Object Type Specifies a list of business object types users search
frequently for quick access when the Simple Search view
is opened.
Preference name:
Favorite_Business_Objects_To_Search.

Favorite option
Option Purpose
Favorite Determines the queries available for selection from the
Find menu in both the rich client and the thin client.
Preference name: QRYColumnsShownPref.

PLM00191 J Rich Client Interface Guide 5-51

Chapter 5 Option reference

General options
Option Purpose
Case Sensitive Determines if object searches are case sensitive.
Preference name: TC_ignore_case_on_search.
Latest Dataset Determines whether the latest version or all versions of
Versions a dataset object are displayed when query results are
returned.
Preference name: QRY_dataset_display_option.
Search Classification Specifies whether saved and ad hoc classification queries
Hierarchy performed with the My Teamcenter search feature
searches across the classification hierarchy or only the
given class.
Preference name:
QRY_search_classification_hierarchy.
Enable Hierarchical Determines whether subtypes are included in query
Type Search results. The system uses type hierarchy functionality to
query types and subtypes.
Preference name: QRY_search_type_hierarchy.
Wildcard Option Specifies the wildcard character used for all searches
and queries.
Preference name: TC_pattern_match_style.
Delimiting Character Defines the character used to separate multiple entries
for queries.
Preference name: WSOM_find_list_separator.
Escape Character Specifies a character to use to escape wildcard characters.
Preference name: TC_escape_character.
In the General section
Default Search Determines which saved query displays in the search
panel by default.
Preference name: Change_Search_Default.
Default Business Specifies a default business object type to search when
Object Type the business object Simple Search view is opened.
Preference name:
Default_Business_Object_To_Search.
Search Locale Specifies the locale used in doing search operations. The
search criteria specified by the user is assumed to be
in this locale. If the value is not set, the search locale
defaults to the client locale.
Preference name: TC_language_search.

5-52 Rich Client Interface Guide PLM00191 J

 Option reference

Remote option
Option Purpose
Remote Specifies the ODS sites that Teamcenter searches for
published remote objects during a remote search.
Preference name: ODS_searchable_sites.

Results options
Option Purpose
Configure the search Determines the number of searches maintained in the
history size search history. When the limit is reached, the oldest
search is deleted.
Preference name: MySearchHistory_Limit.
Set Loading Page Size Determines the number of objects loaded to workspace
after performing a Find action before asking for user
confirmation.
Preference name: WSOM_find_set_search_limit.
Set open search result Preference name: Open_Search_Result_Limit.
limit
Set load all limit Preference name: Search_result_load_all_limit.

Saved Searches option

Option Purpose
Display my saved Preference name: MSS_display_folder_expanded.
searches

Visualization options
Visualization options (preferences) control viewing NX part files, opening
visualization data in Lifecycle Visualization, and options about how you work with
product views.

Lifecycle Visualization options

Option Purpose
View NX .prt files as 2D Allows you to view part files with embedded CGM
images data in either 2D or 3D (default) format in Lifecycle
Visualization. This preference is valid only when viewing
.prt files in Lifecycle Visualization.
Preference name: VIS_view_nx_prt_as_2d.

PLM00191 J Rich Client Interface Guide 5-53

Chapter 5 Option reference

Option Purpose
Show Open in
Lifecycle Visualization Displays the Open in Visualization button in the rich
Command client toolbar.
This button launches Lifecycle Visualization.
Preference name: TC_show_open_in_vmu_button.

Product views

Option
In the Product View Creation Preferences section
Create geometry asset
Include outline capture with Optionally, you can specify if an outline capture
asset
Show product view name
dialog
View Toggle Warning Level
View Toggles to consider
Purpose
Specifies whether a 3D geometry asset should
be captured when a product view is created.
should be included with the 3D geometry asset.
Preference name: Vis_PV_Geometry_Asset.
When selected, you are to be prompted for a
name each time your create a product view.
If cleared, the application generates the name
automatically.
Preference name:
Vis_PV_Show_Name_Dialog.
When selected, Teamcenter displays a warning
or prevents you from continuing if you try to
create a product view when one or more view
toggle options to show unconfigured data are
selected.
Preference name:
Vis_PV_InvalidConfigWarnLevel.
Select view toggle states to show unconfigured
data if View Toggle Warning Level is selected.
The view toggle states include the following:
• Show Unconfigured Variants

• Show Unconfigured Assigned Occurrences

• Show Suppressed Occurrences

• Show Unconfigured Changes

• Show Unconfigured By Occurrence

Effectivity

• Show GCS Connection Points

5-54 Rich Client Interface Guide PLM00191 J

 Option reference

Option Purpose

Preference name:
Vis_PV_BlockingViewToggles.
In the Image Capture section
Image Capture Specifies if the application saves a preview image
of the 3D product view when it is captured.
You can choose one of the following options:
• If you choose Do not perform Image Capture
an image capture is not created and the
image capture preferences are unavailable.

• If you choose Perform Image Capture (using

Image Export Dialog), you are prompted
for the settings to use. The image capture
options are unavailable.

• If you choose Perform Image Capture (with

preferences), the capture uses values
that you choose from the Image Capture
preferences.

Preference name: Vis_PV_ImageCapture.

Image Format If you selected Perform Image Capture (with
preferences), you can determine the file format,
Width of image resolution, and size of the preview image.
Image Resolution If you selected Perform Image Capture (using
Height of image Image Export Dialog), these options are disabled.
Preference name:
Vis_PV_ImageCaptureType.
Preference name:
Vis_PV_ImageCaptureWidth.
Preference name:
Vis_PV_ImageCaptureResolution.
Preference name:
Vis_PV_ImageCaptureHeight.
In the Thumbnail section
Width (in pixels) Determine the size of the thumbnail.
Height (in pixels) Determine the quality (resolution) of the
thumbnail by moving the slider.
Quality
Preference name: Vis_PV_ThumbnailWidth.
Preference name: Vis_PV_ThumbnailHeight.
Preference name: Vis_PV_ThumbnailQuality.

PLM00191 J Rich Client Interface Guide 5-55

Chapter 5 Option reference

Option
In the Product View Apply Preferences section
Play motion in current view
Configuration rule to use
Purpose
If selected, motion files (.vfm) in the current
product view play when the view is selected.
Preference name: Vis_PV_Play_Motion.
Specify the configuration rule for creating the
product view.
You can choose from the following:
• Use configuration from the current BOM,
which ignores stored rules and preserves
the configuration that was active before you
applied the product view.

• Use configuration from product view, which

considers any arrangements, effectivity,
variant rules, and revision rules stored with
the product view when you apply it.

Preference name:
Vis_PV_HowTo_Configure_BOM.

Note Your administrator may configure these preferences with SITE or GROUP
protection scope, rather than USER protection scope. If so, you may be able
to view but not change the current settings.

Workflow options
Workflow options are a broad category of preferences used to configure and control
workflow processes. These are typically implemented as site preferences and can
be set by a privileged user. Inbox and new process options can be set using the
Options command on the Edit menu.

General options for workflow

Option Purpose
Default View Specifies whether the task or process is the default
workflow view.
Preference name:
TCVIEWER_default_workflow_view.
Show Advanced Paste Specifies whether the Advanced Paste button is
in New Process displayed in the New Process dialog box.
Preference name: WORKFLOW_advanced_paste.

5-56 Rich Client Interface Guide PLM00191 J

 Option reference

Inbox options for workflow

Option Purpose
Inbox interval Specifies the interval at which the inbox is checked for
checking for new new tasks.
tasks
Disable Inbox status is not checked.
Check Once Inbox is checked when you log on to
when logging Teamcenter.
in
Interval Inbox is checked when you log in and at
(mins) intervals determined by the value (in
minutes) entered in this field.
Preference name: TC_inbox_interval.
Suspended Tasks Determines how suspended tasks are handled and
displayed in your inbox.
Preference name: INBOX_hide_suspended_tasks.

PLM00191 J Rich Client Interface Guide 5-57

Appendix

A Glossary

PLM00191 J Rich Client Interface Guide

Appendix

A Glossary

access control entry (ACE)

In Access Manager, each pairing in the access control list of an accessor with the
granted privileges.

access control list (ACL)

Access Manager component that contains a list of accessors and, for each accessor,
the privileges granted, denied, and not set.

Access Manager (AM)

Teamcenter application that enables the system administrator to grant users access
to Teamcenter objects.

accessor
Access Manager component that grants or denies privileges to clusters of users who
share certain common traits (for example, perform the same function or work on
the same project).

ACE
See access control entry (ACE).

ACL
See access control list (ACL).

action handler
Handler used to extend and customize workflow task actions. Action handlers
perform such actions as displaying information, retrieving the results of previous
tasks (inherit), notifying users, setting object protections, and launching applications.
See also task handler.

add status task

Task template that creates and adds a release status to the target objects of a
workflow process. There is no dialog box associated with this template.

ad hoc process modification

Functionality that allows users to add tasks to, or delete tasks from, an active
workflow process.

alias ID
Identifier of a part that is similar to the current part. You can use it as a substitute
part in the product structure. Contrast with alternate ID.

PLM00191 J Rich Client Interface Guide A-1

Appendix A Glossary

alternate ID
Different identifier for the current part, but one that represents the same part.
Different organizations and suppliers can have their own part numbers. With
alternate IDs, you are able to find the part you are looking for using your naming
scheme. Contrast with alias ID.

AM
See Access Manager (AM).

AP212
See STEP AP212.

application
Related functional elements collected and arranged in a software package, designed
to accomplish specified tasks. See also perspective.

Application Interface Viewer

Viewer data tab in applications that allows users to monitor and control PLM
XML data exchanges between Teamcenter and another application through a
collaboration context.

approver
User who has a signoff in a workflow process regardless of role and group
membership. In Access Manager, the approver accessor is used to allocate privileges
that apply to all signoffs (for example, read access). See also RIG approver, role
approver, and group approver.

assembly
Compound object that is assembled from other objects and may add additional
information to their interpretation.
• In the context of an assembly, other assemblies are called subassemblies, while
noncompound objects are called components.

• A single-level compound object that is distinct from a multilevel product

structure or bill of materials, which is a hierarchy of assemblies. Assembly
data is stored in a BOM view revision.

attribute
Named storage variable that describes an object and is stored with the object. Users
can search the database for objects using object attributes.
In an object, an attribute is a name/value pair; in the database, an attribute is a field.

bid package
Contains line items supplied to vendors to submit quotes.

bid package line item

Part of a bid package; contains an assembly or part with specific context rules.

BOM view
Teamcenter object used to manage product structure information for an item.

A-2 Rich Client Interface Guide PLM00191 J

 Glossary

BOM view revision (BVR)

Workspace object that stores the single-level assembly structure of an item revision.
Access can be controlled on the structure (BOM view revision) independently of
other data. BOM view revisions are meaningful only in the context of the item
revisions for which they are created.

BVR
See BOM view revision (BVR).

change
Temporary or permanent change to a configuration, design requirement, or
documentation.

change order
Teamcenter object that references the problem, originating change requests,
solutions, and related information. A change order contains sufficient information to
incorporate the change.

change request
Teamcenter object that requests a change, reference the problem, proposed solutions,
and related information. A change request contains sufficient information to allow a
decision to proceed further with the change.

change type
Template of a change process. Change types are created by a system administrator
using the Business Modeler IDE.

Closure Rule
Rule that controls the scope of the translation of data imported to and exported from
Teamcenter. Closure rules specify how the data structure is traversed by specifying
the relationships of interest and the actions to occur when these relationships are
encountered.

collaboration context
Teamcenter object that holds a collection of data contained in structure and
configuration contexts. This data allows you to capture multiple different
Teamcenter structures in one container. You can open a collaboration context in
the Multi-Structure Manager application, in Manufacturing Process Planner, or in
Part Planner. You can also use a collaboration context to collect data to share with
a third-party application. See also structure context.

Command Suppression
Teamcenter application that enables the system administrator to control the
display of menu and toolbar commands within Teamcenter applications. Command
Suppression allows suppressing the display of commands for an entire group
hierarchy or a specific role within the hierarchy, for entire groups of users, and for
users who are assigned a role within a group. It also allows suppressing the display
of specific commands on a designated menu or the display of entire menus.

CommercialPart
Business object type related to a Part object type by a structure relation. A
commercial part is made externally by a vendor who resells, builds, or designs and
builds the part for the OEM (original equipment manufacturer). Commercial parts

PLM00191 J Rich Client Interface Guide A-3

Appendix A Glossary

may be off-the-shelf market parts or custom-designed parts. A commercial part is

a part whose form, fit, and function may be satisfied by one or more vendor parts
that the OEM may source from one or more vendors.

component
• Objects used to build up an assembly or subassembly.

• Part in a product structure defined in Teamcenter. A component is the lowest

level part in the product structure: it cannot be broken down into subparts.

configuration rule
Rule that configures a structure. There are two kinds of configuration rules: revision
rule and variant rule.

connection
Object that defines the connectivity between two or more terminals in a physical
model.

container object
Any Teamcenter object used to hold other objects and organize product information.
For example, folders and items are container objects.

Content Management
Teamcenter application that enables users to manage SGML and XML information
stored in a Teamcenter database and publish documents in multiple formats
using SGML/XML editing and publishing tools. Content Management is used to
collect and publish content, storing the content as components that can be reused
in multiple publications, while links are maintained between components. The
application includes processes for structuring publications so that they can be stored,
published, and used for different purposes. Content Management also stores and
manages graphics for use in publications, provides content revision control, and can
incorporate Teamcenter workflows to facilitate the content development process.

dataset
Teamcenter workspace object used to manage data files created by other software
applications. Each dataset can manage multiple operating system files, and each
dataset references a dataset tool object and a dataset business object.

dataset business object

Teamcenter object that contains a list of tools that can operate on a dataset.

dataset tool
Teamcenter object that is the tool used to create or modify a dataset.

deep copy rule

Business rule that defines whether relational type objects can be copied as object,
copied as reference, or not copied when the user performs a save-as or revise
operation.

direct model dataset

Dataset containing a JT (visualization) file.

A-4 Rich Client Interface Guide PLM00191 J

 Glossary

document
Subtype of an item that represents all revisions of a real-world document. This
item type supports documentation for products, processes, standards, and other
aspects of a business, typically from applications such as Microsoft Word, Microsoft
Excel, and so on.

document management
Management of real-world documents through the use of item revision definition
configuration (IRDC) objects to configure document management behavior. IRDC
simplifies user interaction with information and reduces the need for users to
understand the Teamcenter data model and relationship model. See also item
revision definition configuration (IRDC) objects.

Do task
Task template that includes the EPM-hold handler, which stops the task from
automatically completing when the task is started. This template has a customized
dialog box that allows administrators to set a check box to indicate when the task is
complete.

effectivity rule
Rule used to set effective dates on released products and processes with a released
status.

envelope
Teamcenter workspace object that represents a mail message sent by a Teamcenter
user. Envelopes can be used to send workspace object references as well as text
messages.

feature
Physical or geometric object associated with a product, component, or part.
Alternatively, a logical attribute of a product, component, or part. Examples: a weld
point, a signal, or a geometric pattern. A feature may be represented by a generic
design element (GDE) in a BOM. See also generic design element.

File Management System (FMS)

System that manages uploading and downloading file data between clients and
volumes in both two-tier and four-tier architecture deployments.
• FMS provides volume servers for file management, a shared server-level
performance cache for shared data access between multiple users, a client-based
private user cache for rich clients, and a transient datastore mechanism for
transporting reports, PLM XML, and other nonvolume data between the
enterprise and client tiers.

• FMS file caching enables placing the data close to the user, while maintaining a
central file volume and database store.

filter rules (PLM XML)

Rules that allow a fine level of control over which data is translated, in PLM XML
format, along with the primary objects by specifying that a user-written function be
called to determine the operation applied against a specified object.

PLM00191 J Rich Client Interface Guide A-5

Appendix A Glossary

FMS
See File Management System (FMS).

FMS client cache (FCC)

FMS process that runs on a client host, uploading files to an FMS server cache
process, requesting files from an FMS server cache process, and caching files on
the client host. The FCC process manages two caches of whole files: a write cache
containing files uploaded to a Teamcenter volume and a read cache containing files
downloaded from a Teamcenter volume. It also manages one segment file cache for
Teamcenter lifecycle visualization. Each Teamcenter rich client host requires a
local FMS client cache.

FMS master configuration file

File that configures FMS (fmsmaster.xml). The FMS master configuration file
describes the FMS network and defines groups of server caches. It can also define
default values for server caches and client caches, such as maximum sizes. Values
defined in the server cache configuration file and in the client cache configuration file
can override the default values defined in the master configuration file.

FMS master host

Host that contains the FMS master configuration file (fmsmaster.xml). This file is
optionally mounted at each FSC server.

FMS server cache (FSC)

FMS process that runs on a server host and performs as a volume server (when
running on a host where a volume is located or directly mounted) or a cache server
(when running on a host where a volume is not located or directly mounted) and a
configuration server. As a volume or cache server, the FSC checks all file access
requests for a ticket that Teamcenter generates to authorize file access. As a cache
server, it manages two segment file caches, one for downloading files and one for
uploading files. As a configuration server, it provides FMS configuration information
to file client caches and other FSCs. As a transient server, it delivers PLM XML and
other transient files to clients. A minimum of one FSC must be deployed in any
Teamcenter installation. Multiple FSCs can be deployed, with each FSC performing
one designated purpose as either a volume, a cache, or a configuration server.

folder
Graphical representation of an aggregation of objects, such as a group, class, or
subclass. For easy distinction in the class hierarchy, each of these aggregations has
a different type of folder icon associated with it: a group folder icon, a class folder
icon, or a subclass folder icon.

form
Teamcenter workspace object used to display product information (properties) in a
predefined template. Forms are often used to create an electronic facsimile of a
hardcopy form in Teamcenter. See also master form.

FSC
See FMS server cache (FSC).

FSC configuration file

File that configures an individual FMS server cache (fsc.xml). The FSC
configuration file defines such values as the address of the master FSC, the
maximum sizes of the segment file caches, and the upload time-out value. It can also
define default values for FCCs and other FSCs.

A-6 Rich Client Interface Guide PLM00191 J

 Glossary

FSC group
Group of server caches defined in the FMS master configuration file.

GDE
See generic design element.

generic design element

BOM item that cannot have different revisions. See also feature.

group (Organization)
Organizational grouping of users at a site. Users can belong to multiple groups
and must be assigned to a default group.

group administrator
User with special maintenance privileges for a group.

group approver
User who is a signoff in a workflow process with a specific group of users. In Access
Manager, the group approver accessor is used in Workflow ACLs and matches the
signoff definition (that is, group) for the release level associated with the Workflow
ACL. The group approver accessor ensures that only signoffs are given privileges, not
a user who matches the group. See also approver, RIG approver, and role approver.

group preference
Teamcenter preference applying to an entire group.

harness
Assembly of insulated conductors formed to a predetermined pattern or
configuration; also called a wiring harness.

item
Workspace object generally used to represent a product, part, or component. Items
can contain other workspace objects including other items and object folders.

item relation
Description of an association between a Teamcenter item and a piece of information
that describes or is related to the item.

item revision
Workspace object generally used to manage revisions to items.

item revision definition configuration (IRDC) objects

Objects that define how item revisions are handled at specific times in the life cycle,
such as at item creation, checkin, checkout, save as, and revise. IRDC objects are
defined in the Teamcenter Business Modeler IDE application. Any item can be
associated with an IRDC. For example, IRDC objects typically support business
processes by managing document checkin and checkout and by specifying rendering
of visualization or markup versions from source datasets.

PLM00191 J Rich Client Interface Guide A-7

Appendix A Glossary

item revision relation

Description of an association between a Teamcenter item revision and a piece of
information that describes or is related to the item revision.

Lifecycle Visualization
Visualization components available in the rich client, the thin client, and as a
stand-alone application. A scalable solution for the viewing and analysis of 2D and
3D product data, Lifecycle Visualization is available in a number of configurations
to meet the requirements of different organizations.

ManufacturerPart
Business object type that is related to a CommercialPart object type by a Satisfies
relation. A manufacturer part, which can be obtained from one or more vendors, has
a part number assigned by the actual builder of the part. The ManufacturerPart
object is represented in the Teamcenter user interface by the term Vendor Part.

master form
Teamcenter workspace object used to display product information (properties) in
a predefined template. Master forms are used to display product information in
a standardized format.

master FSC
FMS server cache that reads the master configuration file directly from the FMS
master host. An FSC is configured either to read the master configuration file
directly from the master host or to download it from another FSC with access to it.

master object
Controlling object in a Multi-Site Collaboration network.
When an object is created and saved, that instance is the master object until it
is exported with transfer of ownership. There can be only one master object in a
Multi-Site Collaboration network, and only the master object can be modified. If
a master object is replicated, it cannot be deleted until all replicated objects are
deleted.

metadata
Object description in the Teamcenter database.

Multi-Site Collaboration
Teamcenter capability that allows the exchange of data objects among several
Teamcenter databases. Transfer of objects among databases is controlled by daemon
processes running on designated servers. Objects are replicated by exporting them
from their original database and importing them into the requesting database.
Configuration of Multi-Site Collaboration is optional.

named ACL
Named group of access controls. See also access control list (ACL).

A-8 Rich Client Interface Guide PLM00191 J

 Glossary

named reference
File types that are managed by a dataset. Datasets are the only workspace objects
that use named references.

naming rule
Business rule that defines the naming conventions for the string property value in
different type objects. Naming rules can be attached to the following properties:
• Item ID, item revision ID, and name in item types
• Dataset name, ID, and revision number in dataset types
• Name form types

navigation pane
Rich client framework component that displays buttons of the applications available
for use in the rich client. Clicking the application button launches the application.

object-based protection
Use of access control lists to create exceptions to rules-based protection on an
object-by-object basis. Object access control lists are most useful for either granting
wider access or limiting access to a specific object.

object chooser
Displays objects appropriate for linking with another Teamcenter product. In
determining the objects to display, the object chooser considers the security rights of
the person accessing the Teamcenter product. See also remote workflow.

object directory services server

Multi-Site Collaboration network node that runs a daemon process to handle
publication of data objects within a Multi-Site Collaboration environment. One
ODS server node must be designated for each object directory services site and each
server node can act only for one object directory services site.

object directory services site

Site with the database that maintains a record of each object in a Multi-Site
Collaboration network. At least one Teamcenter database on a Multi-Site
Collaboration network must be designated as an ODS site. This site is used to store
publication records for the data objects.

object launcher
Launches another Teamcenter product from a linked object. Each Teamcenter
product has an object launcher. See also remote workflow.

ODS server
See object directory services server.

ODS site
See object directory services site.

Organization
Teamcenter application that enables a system administrator to create and manage
critical Teamcenter files and database entries. It is the point of access for creating a
company’s virtual organization and for performing system administration activities
such as volume creation, maintenance, and site administration. Organization

PLM00191 J Rich Client Interface Guide A-9

Appendix A Glossary

enables creation and management of person, user, role, and group definitions;
definition of the hierarchical structure of the Teamcenter organization; management
of data volumes; and establishment and maintenance of Teamcenter sites.

owner
User that owns an object, initially the user who created it. Ownership can be
transferred from the owner to another user. An object owner usually has privileges
that are not granted to other users (for example, the privilege to delete the object).

owning group
Group that owns an object, usually the group of the user creating the object. Because
users commonly share data with other members of a group, additional privileges may
be granted to the owning group (for example, the privilege to write to the object).

owning site
Multi-Site Collaboration site where the master object resides. The owning site is the
only site where the object can be modified.

part
Business object type that can participate in a structure as an assembly or component,
with or without attached datasets. In Teamcenter, a business item managed in a
company’s part releasing system. Typically, the assembly or component is designed
and built by the OEM.

persistent object manager (POM)

Interface between Teamcenter objects and the Relational Database Management
System (RDBMS). The persistent object manager provides definition of classes
by inheritance from other classes and definition of attributes, manipulation of
in-memory objects and support for their saving and retrieval to and from the
underlying RDBMS, support for applications accessing the same data concurrently,
protection against the deletion of data used by more than one application, and
support for the access control lists attributed to objects.

person
Definition containing real-world information about each Teamcenter user, such as
name, address, and telephone number. Person definitions are stored as simple text
strings so that they can be easily changed and updated. The name must be unique.

perspective
Container in the rich client user interface for a set of views and editors collected to
accomplish specified tasks. See also view.

PLM XML
Siemens PLM Software format for facilitating product life cycle interoperability
using XML. PLM XML is open and based on standard W3C XML schemas.
Representing a variety of product data both explicitly and via references, PLM
XML provides a lightweight, extensible, and flexible mechanism for transporting
high-content product data over the Internet.

preference
Configuration variable stored in a Teamcenter database and read when a Teamcenter
session is initiated. Preferences allow administrators and users to configure many

A-10 Rich Client Interface Guide PLM00191 J

 Glossary

aspects of a session, such as user logon names and the columns displayed by default
in a properties table.

preference protection scope

Hierarchical range for which a Teamcenter preference can be set. The protection
scope of a hierarchical preference can be site, group, role, or user.

privileged team member

Project team member with privileges to assign and remove objects from that
project. Compare with project team member.

process assignment list

Distribution list associated with a workflow process template, allowing users to
assign resources for all tasks in a process from a single dialog box.

process structure
Hierarchy of manufacturing processes and operations with a sequenced relationship
that together describe how a related product is manufactured. Compare with
product structure.

process template
Blueprint of a workflow process defined by placing workflow and/or change
management tasks (for example, do, perform signoff, route, and checklist) in the
required order of performance. Additional process requirements, such as quorums
and duration times are defined in the template using workflow handlers.

product structure
Hierarchy of assembly parts and component parts with a geometric relationship
between them, for example, a bill of materials (BOM). Variant and revision rules
define the generic BOM. This BOM can then be loaded to display the configured
variant.

product view
Saved configuration of the assembly viewer, including the selection of objects, zoom
factor, rotation angle, and pan displacements.

project
Basis for identifying a group of objects available to multiple organizations, such as
project teams, development teams, suppliers, and customers for a particular piece
of work.

Project administrator
Teamcenter super user with unrestricted access to administer projects they create
using the Project application. A Project administrator creates, modifies, and deletes
project information and team members.

project team administrator

Project team member with privileges to modify project information and project team
members for that project. Only one project team administrator is allowed per project.

project team member

Team member who does not have privileges to assign objects to or remove objects
from their projects. Compare with privileged team member.

PLM00191 J Rich Client Interface Guide A-11

Appendix A Glossary

property format finder (PFF)

Feature that allows you to gather and report data related to the objects returned by
a query. PFF objects provide the necessary links and relationships required to locate
arbitrary data without reformatting the query instance. PFF objects also enable you
to acquire additional information that a single query would be incapable of rendering.

property rule
Business rule that allows an administrator to control access to and the behavior of
object properties.

pseudofolder
Special container in Teamcenter that stores and displays item and item revision
relations in My Teamcenter. See also smart folder.

published object
Object available to other sites in a Multi-Site Collaboration network. Publishing an
object creates a record in the ODS site database that can be read and searched by
other sites. Until an object is published, it can be seen only by the owning site.

Query Builder
Teamcenter application that enables a system administrator to create and maintain
customized searches for objects in the Teamcenter databases, both local and remote.
Saved queries are subject to standard object protection and can be accessed by users
through the search feature in My Teamcenter.

query form
Predefined query used in My Teamcenter to quickly search the database without
building a custom query. Query forms limit search criteria to boxes displayed in the
form. Accessing additional search capabilities requires building a custom query.

quorum
Number of users who must vote to approve a task for that task to be approved.

quote
Response to bid package line items.

registry file
Properties (.properties) file that contains the user-defined configuration settings
(keys and values) that are relative to how the application displays and performs
in the Teamcenter rich client. Each application registered in the rich client has a
.properties file known as a registry file.

relation
Description of an association between a Teamcenter object and a piece of information
that describes or is related to the object.

release status
Status associated with a workspace object when it is released through a workflow
process.

A-12 Rich Client Interface Guide PLM00191 J

 Glossary

remote workflow
Teamcenter component that enables users to create links between Teamcenter
objects and objects in other Teamcenter products, such as Teamcenter portfolio,
program and project management. Users can then launch the linked Teamcenter
product from within either the rich client or the thin client.

render
Process that invokes the data translations specified for an item, such as a document
revision, to generate derived visualization data. Translate is an action on a dataset.
Render is an action taken on an object, such as a document. See also translate.

replicated object
Copy of master object residing at sites within a Multi-Site Collaboration network.
See also master object.

review task
Task template that includes the select-signoff-team and perform-signoffs subtasks.
Each subtask contains a unique dialog box for executing the process.

revision filter
Filter used to configure the display of items and item revisions based on established
revision rules.

revision rule
Parameter set by the user that determines which revision of an item is used to
configure product context.

rich client
Java-based user interface to Teamcenter installed on user workstations. The rich
client accesses Teamcenter databases using a remote or local server. Compare to
thin client.

RIG approver
User who is a signoff in a workflow process with a specified role and group. In
Access Manager, the RIG approver accessor is used in Workflow ACLs and matches
the signoff definition (that is, role in group) for the release level associated with
the Workflow ACL. This accessor ensures that only signoffs are given privileges,
not a user who matches the role in group. See also approver, group approver, and
role approver.

role
Function-oriented cluster of users that models skills and/or responsibilities. The
same roles are typically found in many groups. In Access Manager, role is an accessor
used to grant privileges to all users with the same skills and/or responsibilities
regardless of project.

role approver
User who is a signoff in a workflow process with a specific role. In Access Manager,
the role approver accessor is used in Workflow ACLs and matches the sign-off
definition (that is, role in group) for the release level associated with the Workflow
ACL. This accessor ensures that only signoffs are given privileges, not a user who
matches the role. See also approver, group approver, and RIG approver.

PLM00191 J Rich Client Interface Guide A-13

Appendix A Glossary

role in group
Specific role in a specific group. In Access Manager, role in group is an accessor
used to grant privileges to all users with the same skills and/or responsibilities
in the same group.

role in owning group

Specific role in the object’s owning group. In Access Manager, role in owning
group is an accessor used to grant privileges to users with the same skills and/or
responsibilities on the same project. For example, all designers in the owning group
are usually granted write privilege on their development data.

role preference
Teamcenter preference applying to an entire role.

root
Starting point of a hierarchy. Hierarchies are usually displayed as hanging trees
with the root of the structure at the top and the leaves at the bottom.

rule handler
Handler used to integrate workflow business rules into Enterprise Process Modeling
processes at the task level. Rule handlers attach conditions to an action. See also
task handler.

rules-based protection
Conditions or rules that control who can or cannot access objects. These rules are
global (that is, they affect the entire Teamcenter site) and are enforced by the Access
Manager. These rules are defined by a system administrator.

rule tree
Access Manager component the system administrator uses to grant users access to
Teamcenter objects. It is a tree of rules and access permissions that when processed
determines the access that each user has to a specified object.

Security Services
Services that eliminate prompts for logon credentials when users switch Teamcenter
products within a user session. Authentication is performed by an external identity
service provider, such as lightweight directory access protocol (LDAP), instead of
the Teamcenter product. At a site that deploys multiple Teamcenter products and
Security Services, users log on once to access all participating Teamcenter products.

signal
Physical representation of a message or an information flow being generated,
processed, or conveyed within an electrotechnical system.

site
Individual installation of Teamcenter comprising a single Teamcenter database,
all users accessing that database, and additional resources such as hardware,
networking capabilities, and third-party software applications (tools) required to
implement Teamcenter at that site.

A-14 Rich Client Interface Guide PLM00191 J

 Glossary

site ID
Unique identifier of a Teamcenter site. The site ID is used to generate internal
identifiers for Teamcenter objects that must be unique throughout an enterprise.
Once established, site IDs should not be modified.

site name
Unique name of a Teamcenter site stored in the database as a user-defined character
string.

site preference
Teamcenter preference that applies to the entire site.

smart folder
Pseudofolders configured in a hierarchical structure used to apply hierarchical levels
of filtering to project data. See also pseudofolder.

STEP AP212
Standard for the Exchange of Product Model Data (STEP) for the Industrial
Automation Systems and Integration – Product Data Representation and Exchange
international standard (ISO 10303). This standard provides a framework through
which industries can exchange and share product information within and between
enterprises. AP212 is an application of this standard and describes the information
necessary to customize electrotechnical products.

structure context
BOM or assembly structure contained in a collaboration context. The structure
context can contain occurrence groups, items, and item revisions. See also
collaboration context.

Structure Manager
Teamcenter application that enables creation of generic product structures that can
be configured to show the product structure that is in production, effective on a
certain date, used by a particular customer, and so forth. Structure Manager enables
creation and modification of a product structure and its associated occurrence data,
display of a product structure in a multilevel indented format, and viewing graphics
tightly coupled to the structure for easy identification of a component by location in
the structure or in the embedded viewer.

subscription
Combination of a workspace object and an event for which a Teamcenter user
requests notification of occurrence. Teamcenter notifies a subscribed user when the
event occurs in association with the object. Users can subscribe to objects from
Teamcenter applications, such as My Teamcenter and Structure Manager.

Subscription Manager
Tool used to find, delete, and modify active subscriptions.

system administrator
Teamcenter user who is a member of the system administration group.

task (workflow)
Fundamental building block used to construct a process. Each task defines a set of
actions, rules, and resources used to accomplish that task.

PLM00191 J Rich Client Interface Guide A-15

Appendix A Glossary

task handler
Small Integration Toolkit program or function. Handlers are the lowest level
building blocks in Enterprise Process Modeling. They are used to extend and
customize tasks. There are two kinds of handlers: action handlers and rule handlers.
See also action handler and rule handler.

task template
Blueprint of a workflow task.

Teamcenter Application Registry

Independent Web-based service that allows a Teamcenter product to look up other
available Teamcenter products for launching a linked object. Administrators can
register and unregister installed instances of a Teamcenter product in the registry.

Teamcenter application root directory

Directory location of the Teamcenter shared binary executables. The TC_ROOT
environment variable defines this location. Generally, the contents of this directory
change only with a new version of Teamcenter.

Teamcenter data directory

Directory location of the Teamcenter shared data subdirectories and files. The
TC_DATA environment variable defines this location. Each data directory is
associated with a single database instance.

Teamcenter option
See preference and user preference.

thin client
Teamcenter user interface that provides a streamlined browser-based view of product
information stored in a Teamcenter database. The thin client is configured in the
Web tier, which creates and serves its Web pages to the client. Compare to rich client.

transfer mode
Objects composed of rules that configure PLM XML import and export operations.
Transfer mode allows users to import and export data with little knowledge other
than the name of the transfer mode object.

translate
Process that converts data from one file format into another file format. In the
context of Teamcenter document management, source data is converted to derived
visualization data formats. The conversion is based on available translators.
Translate is an action on a dataset. Render is an action taken on an object, such as a
document. See render.

type display rule

Business rule that allows an administrator to control the object types that are
available for creation in Teamcenter.

unpublished object
Object not available to other sites in a Multi-Site Collaboration network. Users
can unpublish previously published objects so they are once again accessible only
to the owning site.

A-16 Rich Client Interface Guide PLM00191 J

 Glossary

user
Definition that is the mechanism by which Teamcenter identifies and interacts with
each user. User definitions contain a name (derived from the person definition), user
ID, operating system name, and password.

user preference
Teamcenter preference applying to a specific user.

variant condition
• Rules applicable to one component in a product structure.

• Condition set on an occurrence to specify the option values required to configure

that occurrence (for example, Load IF engine = 1200).

variant rule
Collection of option values used in determining the variant of the BOM to be
configured (for example, car type = GLS, engine = 1200, gearbox = manual).

vendor
Business object type; provider of parts or services. In Teamcenter, a vendor can take
on one or more roles. Role definitions are not fixed in the data model, and can be
adjusted to meet customer business mode. Vendor roles, for example, can include:
• Distributor: Resells, but does not make, parts.

• Supplier: Makes parts to order for OEM.

• Manufacturer: Makes parts for the general market.

vendor management
Software functionality used to model vendor contributions to a product by letting
users capture information about the vendors and the vendor parts they provide to
satisfy the form, fit, and function of commercial parts.

VendorPart
Business object type that is related to a CommercialPart object type by a Satisfies
relation. A vendor part can be obtained from one or more vendors, but the actual
builder of the part assigns a part number.

view
Software element in a rich client user interface perspective. It provides the ability to
navigate hierarchies of information, display information about selected objects, open
an editor, or display properties. See also perspective.

work context
Object containing user, group, role, and project requirements for a particular task.
Work contexts streamline the definition of the correct user settings required to
perform tasks. For example, a user typically assigned three types of tasks can create
three work contexts reflecting the required group/role settings. Rather than logging
out and logging back in with the required group/role settings, right-clicking a task
displays the user’s defined work contexts. Selecting the appropriate work context

PLM00191 J Rich Client Interface Guide A-17

Appendix A Glossary

automatically changes the user’s group/role settings. Work contexts can also define
the current project, if project functionality is used at the site.

workflow
Automation of the concept that all work flows through one or more business
processes to accomplish an objective. Using workflow, documents, information, and
tasks are passed between participants during the completion of a particular process.

Workflow Designer
Teamcenter application that enables administrators to graphically design workflow
process templates, incorporating company business practices and procedures into
the templates. Teamcenter users initiate workflow processes using these templates.

Workflow Viewer
Teamcenter application that enables users to view the progress of a workflow
process. Users are not required to be participating members of the process being
viewed. Depending on preference settings, Workflow Viewer also allows ad hoc
process modification. See also ad hoc process modification.

working revision
Revision that can be changed by a user with write privileges. No record of
intermediate states of a working revision is maintained by Teamcenter.

world
All users regardless of group or role.

A-18 Rich Client Interface Guide PLM00191 J

Index

Numerics/Symbols Opening . . . . . . . . . . . . . . . . . . . . . . 4-6

Purpose . . . . . . . . . . . . . . . . . . . . . . . 4-1
2D Viewer view . . . . . . . . . . . . . . . . . . 2-28 Application pane . . . . . . . . . . . . . . . . . . 1-7
3D Viewer view . . . . . . . . . . . . . . . . . . 2-46 Rich client . . . . . . . . . . . . . . . . . . . . . 1-7
4G Designer . . . . . . . . . . . . . . . . . . . . . 2-2 Application tab . . . . . . . . . . . . . . . . . 2-124
4G Designer-MBOM Reconciliation . . . . . 2-2 Applications
Configuring display of . . . . . . . . . . . 2-98
A Display as primary . . . . . . . . . . . . . . 2-99
Display as secondary . . . . . . . . . . . . 2-99
Access Manager . . . . . . . . . . . . . . . . . . 2-2 Primary . . . . . . . . . . . . . . . . . . . . . 2-99
Access Manager view . . . . . . . . . . . . . . 2-18 Secondary . . . . . . . . . . . . . . . . . . . . 2-99
Access shortcut menu command . . . . . 2-85, Selecting for display . . . . . . . . . . . . . 2-99
2-89 Showing fewer . . . . . . . . . . . . . . . . 2-100
Accountability Check view . . . . . . . . . . 2-28 Showing more . . . . . . . . . . . . . . . . 2-100
Action option . . . . . . . . . . . . . . . . . . . 5-31 Applications view . . . . . . . . . . . . . . . . 2-18
Activities view . . . . . . . . . . . . . . . . . . 2-28 Apply Templates option . . . . . . . . . . . . 5-27
Activity Gantt view . . . . . . . . . . . . . . . 2-29 ARM Transaction Monitor options . . . . . 5-3
ADA License . . . . . . . . . . . . . . . . . . . . . 2-2 As-Built Manager . . . . . . . . . . . . . . . . . 2-3
ADA License Details view . . . . . . . . . . 2-47 As-Built Manager view . . . . . . . . . . . . 2-21
ADA Licenses View . . . . . . . . . . . . . . . 2-47 Assembly view . . . . . . . . . . . . . . . . . . 2-46
Add Design to Product shortcut menu Assignments view . . . . . . . . . . . . . . . . 2-29
command . . . . . . . . . . . . . . . . . 2-85, 2-90 Associate secondary view to primary
Add Part to Product shortcut menu view . . . . . . . . . . . . . . . . . . . . . . . . . 2-77
command . . . . . . . . . . . . . . . . . 2-85, 2-90 Associated Signals view . . . . . . . . . . . . 2-39
Add Publish request . . . . . . . . . . . . . . . 4-7 Attachments view . . . . . . . . . . . . 2-24, 2-29
Add sync request . . . . . . . . . . . . . . . . . . 4-7 Attribute search
Add To Favorites shortcut menu Classification . . . . . . . . . . . . . . . . . . 3-39
command . . . . . . . . . . . . . . . . . 2-86, 2-90 Audit Manager view . . . . . . . . . . . . . . 2-18
Adhoc classification query Authorization view . . . . . . . . . . . . . . . 2-48
Extended multi-application search . . 3-39 Auxiliary views . . . . . . . . . . . . . . . . . . 2-70
Administrative settings, changing . . . 2-106
Advanced search . . . . . . . . . . . . . . . . . . 3-6
Allow live updates . . . . . . . . . . . . . . . . 5-13 B
Always Create New CAEModel option . . 5-29 Back and forward buttons . . . . . . . . . . . 1-6
Always Re-Mesh option . . . . . . . . . . . . 5-29 Basic concepts . . . . . . . . . . . . . . . . . . . 1-2
AM Rules view . . . . . . . . . . . . . . . . . . 2-36 Basic tasks . . . . . . . . . . . . . . . . . . . . . . 1-2
Analysis view . . . . . . . . . . . . . . . . . . . 2-24 Batch meshing options . . . . . . . . . . . . 5-29
appbar_title_contents preference . . . . 2-104 BOM Changes view . . . . . . . . . . . . . . . 2-26
Appearance Configuration . . . . . . . . . . . 2-3 BOM Compare Report view . . . . . . . . . 2-40
Appearance Configuration view . . . . . . 2-18 BOM Grading Result view . . . . . . . . . . 2-45
Application banner . . . . . . . . . . . . . . . . 1-6 BOM line title format option . . . . . . . . 5-20
Application bar . . . . . . . . . . . . . . . . . 2-104 BOM Markup View view . . . . . . . . . . . 2-41
Application interface object, definition . . 4-2 BOM precision option . . . . . . . . . . . . . 5-21
Application Interface Viewer BOM tracking options . . . . . . . . . 5-34–5-35
Objects . . . . . . . . . . . . . . . . . . . . . . . 4-1 Browse Clear Text option . . . . . . . . . . . 5-28

PLM00191 J Rich Client Interface Guide Index-1

Index
Budgets view . . . . . . . . . . . . . . . . . . . 2-40
build_fts_index utility . . . . . . . . . . . . . 3-20
Business object type
Choose . . . . . . . . . . . . . . . . .
Search . . . . . . . . . . . . . . . . .
Search options . . . . . . . . . . . .
Button bar . . . . . . . . . . . . . . . .
C Change
Caches
Rich client . . . . . . . . . . . . . . . . . . . 2-157
CAE Manager . . . . . . . . . . . . . . . . . . . . 2-3
CAE Manager (Legacy) . . . . . . . . . . . . . 2-4
CAE Manager view . . . . . . . . . . . . . . . 2-21
CAE Structure Designer . . . . . . . . . . . . 2-4
CAE Structure Designer view . . . . . . . . 2-21
CAE Structure Editor, see CAE Manager
(Legacy)
CAE tool options . . . . . . . . . . . . . . . . . 5-28
Always Create New CAEModel . . . . . 5-29
Always Re-Mesh . . . . . . . . . . . . . . . 5-29
Batch meshing . . . . . . . . . . . . . . . . . 5-29
CAE Simulation Tool Configuration Dataset
Name . . . . . . . . . . . . . . . . . . . . . 5-33
Create relationship between CAEModel and
StructureMap . . . . . . . . . . . . . . . 5-33
Data Map Files Location . . . . . . . . . . 5-33
Default Meshing Tool . . . . . . . . . . . . 5-29
Default New Model Action Item
Type . . . . . . . . . . . . . . . . . . . . . 5-32
Default Root BOMLine Action . . . . . . 5-32
Enable Context Based Menu for Simulation
Tool Launch . . . . . . . . . . . . . . . . 5-33
Extra Model Components . . . . . . . . . 5-32
General . . . . . . . . . . . . . . . . . . 5-30–5-31
Input Geometry . . . . . . . . . . . . . . . . 5-30
Inspector . . . . . . . . . . . . . . . . . . . . . 5-31
Inspector Execution Summary Dataset
Name option . . . . . . . . . . . . . . . . 5-31
Meshing Tools . . . . . . . . . . . . . . . . . 5-29
Missing Model Components . . . . . . . 5-31
Model With Different Product Revision
Target . . . . . . . . . . . . . . . . . . . . 5-32
Model With No Product . . . . . . . . . . 5-32
My Favorite Simulation Tools . . . . . . 5-33
Package location . . . . . . . . . . . 5-32–5-33
Parameter/Criteria Files . . . . . . . . . . 5-30
Persist StructureMap log . . . . . 5-33–5-34
Product with no Model . . . . . . . . . . . 5-31
Set CAEModel Attributes . . . . . . . . . 5-30
Simulation Tools in Toolbar . . . . . . . 5-33
Startup Scripts/Server Info . . . . . . . . 5-30
StructureMap Log Dataset Name . . . 5-34
Index-2 Rich Client Interface Guide
Tool Information for Output Files . . . 5-30
Calculate Defining/Complying Objects
option . . . . . . . . . . . . . . . . . . . . . . . . 5-28
. . . . . 3-11 Calendar options . . . . . . . . . . . . . . . . . 5-34
. . . . . 3-13 Case sensitivity, search option . . . . . . . 3-44
. . . . . 3-45 Categories, creating . . . . . . . . . . . . . . 2-148
. . . . 2-125 Categories, deleting . . . . . . . . . . . . . . 2-148
Caution option . . . . . . . . . . . . . . . . . . 5-31
Search . . . . . . . . . . . . . . . . . . . . . . 3-34
Search criteria definition . . . . . 3-37–3-38
Change Effectivity view . . . . . . . . . . . . 2-26
Change Home view . . . . . . . . . . . . . . . 2-26
Change Management options . . . . . . . . 5-34
BOM tracking . . . . . . . . . . . . . . . . . 5-35
Change Manager . . . . . . . . . . . . . . . . . . 2-4
Change Search options . . . . . . . . . . . . 3-33
Change Viewer options
Graphical history . . . . . . . . . . . . . . . 5-44
Show common parts . . . . . . . . . . . . . 5-44
Change_Search_Default preference . . . . 3-8
Changing
Administrative settings . . . . . . . . . 2-106
Passwords . . . . . . . . . . . . . . . . . . . 2-105
Session settings . . . . . . . . . . . . . . . 2-106
User profiles . . . . . . . . . . . . . . . . . 2-105
User session settings . . . . . . . . . . . 2-106
User settings . . . . . . . . . . . . . . . . . 2-106
Check In/Out shortcut menu
command . . . . . . . . . . . . . . . . . . . . . 2-88
Check In/Out shortcut menu
command . . . . . . . . . . . . . . . . . . . . . 2-84
Checkin options . . . . . . . . . . . . . . . . . 5-38
Checking status of indexed objects . . . . 3-25
Classification . . . . . . . . . . . . . . . . . . . . 2-4
Attribute search . . . . . . . . . . . . . . . . 3-39
Classification Admin view . . . . . . . . . . 2-18
Classification Administration . . . . . . . . . 2-4
Classification attribute searches . . . . . . 3-42
QRY_search_classification_hierarchy
preference . . . . . . . . . . . . . . . . . 3-42
Classification hierarchy search
option . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Classification Properties view . . . . . . . . 2-29
Classification Table view . . . . . . . . . . . 2-29
Classification view . . . . . . . . . . . . . . . 2-22
Clear search form . . . . . . . . . . . . . . . . 3-34
Clear search history . . . . . . . . . . . . . . 3-46
Clipboard
Pasting contents . . . . . . . . . . . . . . 2-112
Clipboard button
Description . . . . . . . . . . . . . . . . . . . . 1-7
Close Perspective command . . . . . . . . . 2-80
Closing search results . . . . . . . . . . . . . 3-17
PLM00191 J

Collaboration Context, see Multi-Structure
Manager
Collaboration Context Tree view . . . . . . 2-29
Collaboration context, definition . . . . . . . 4-2
Columns
Removing . . . . . . . . . . . . . . . . . . . 2-127
Repositioning . . . . . . . . . . . . . . . . 2-127
Command bar . . . . . . . . . . . . . . . . . . 2-126
Command Suppression . . . . . . . . . . . . . 2-5
Communication Monitor view . . . . 2-27, 2-70
Compare Contents shortcut menu
command . . . . . . . . . . . . . . . . . 2-86, 2-90
Compare search results . . . . . . . . . . . . 3-18
Compare view . . . . . . . . . . . . . . . . . . . 2-46
Comparing
Search results . . . . . . . . . . . . . . . . . 3-18
Composite view . . . . . . . . . . . . . . . . . . 2-25
Computer-Aided Engineering (CAE) tool
options . . . . . . . . . . . . . . . . . . . . . . . 5-28
Configuration context . . . . . . . . . . . . . . 4-2
Configure Applications button . . . . . . . 2-92
Configure Applications menu . . . . . . . . 2-98
Configure the search history size . . . . . 3-46
Configuring table panes . . . . . . . . . . . 2-129
Configuring view tables . . . . . . . 2-55, 2-129
Console view . . . . . . . . . . . . . . . . . . . . 2-16
Constraints view . . . . . . . . . . . . . . . . . 2-46
Contains view . . . . . . . . . . . . . . . . . . . 2-38
Content Management . . . . . . . . . . . . . . 2-5
Copy Reference shortcut menu
command . . . . . . . . . . . . . . . . . 2-82, 2-86
Copy shortcut menu command . . . 2-82, 2-87
Copying objects . . . . . . . . . . . . . . . . . 2-112
Create
Folder . . . . . . . . . . . . . . . . . . . . . . 2-120
Creating
Preferences . . . . . . . . . . . . . . . . . . 2-149
Property Finder Formatter (PFF)
objects . . . . . . . . . . . . . . . . . . . . 3-47
Creating a Teamcenter shortcut . . . . . . . 1-4
Cross Sections view . . . . . . . . . . . . . . . 2-46
Custom Notes view . . . . . . . . . . . . . . . 2-40
Customizing tables . . . . . . . . . . . . . . . . 4-7
Cut shortcut menu command . . . . 2-82, 2-87
Cutting objects from the workspace . . 2-111
D
Dashboard . . . . . . . . . . . . . . . .
Dashboard view . . . . . . . . . . . .
Data Map Files Location . . . . . .
Data pane . . . . . . . . . . . . . . . .
Database Utilities . . . . . . . . . . .
Database Utilities view . . . . . . .
PLM00191 J
Index
Dataset Keyword Search form . . . . . . . 3-21
Dataset options . . . . . . . . . . . . . . . . . . 5-10
Dataset purge limit . . . . . . . . . . . . . . . 5-43
Dataset search form . . . . . . . . . . . . . . 3-21
DB Walker view . . . . . . . . . . . . . . . . . 2-27
Default Base Calendar . . . . . . . . . . . . 5-34
Default groups, changing . . . . . . . . . . 2-105
Default Meshing Tool option . . . . . . . . 5-29
Default paste relations . . . 2-112, 5-40, 5-42
Default revision rule option . . . . . . . . . 5-20
Default roles, setting . . . . . . . . . . . . . 2-106
Default Root BOMLine Action option . . 5-32
Default Search
Search options . . . . . . . . . . . . . . . . . 3-45
Default View option . . . . . . . . . . . . . . . 5-56
Default view type option . . . . . . . . . . . 5-20
Default volumes
Changing default local volume . . . . 2-105
Changing default volume . . . . . . . . 2-105
defaultViewerConfig_VIEWERCONFIG
preference . . . . . . . . . . . . . . . . . . . . . 2-69
Definition view . . . . . . . . . . . . . . . . . . 2-36
Delete
Folder . . . . . . . . . . . . . . . . . . . . . . 2-123
Delete sync request . . . . . . . . . . . . . . . . 4-7
Deleting objects . . . . . . . . . . . . . . . . 2-110
Deleting objects from the database . . . 2-111
DesignContext . . . . . . . . . . . . . . . . . . . 2-5
DesignContext options . . . . . . . . . . . . . 5-36
DesignContext view . . . . . . . . . . . . . . . 2-22
Detach a view . . . . . . . . . . . . . . . . . . . 2-72
Details pane . . . . . . . . . . . . . . . . . . . 2-126
Details view . . . . . . . . . . . . . . . . . . . . 2-41
Diagram Explorer view . . . . . . . . . . . . 2-40
Disable response to selection . . . . . . . . 2-77
Display Data pane . . . . . . . . . . . . . . . 2-129
Displaying
Images . . . . . . . . . . . . . . . . . . . . . . 2-57
Search results . . . . . . . . . . . . . 3-15–3-16
Displaying list of value descriptions . . . 5-13
Disposition History view . . . . . . . . . . . 2-38
DPV Measurements . . . . . . . . . . . . . . . 2-5
DPV Measurements view . . . . . . . . . . . 2-19
Drag and drop data . . . . . . . . . . . . . . 2-113
E
ECAD DXF view . . . . . . . . . . . . . . . . . 2-46
. . . . . . 2-5 ECAD Layer view . . . . . . . . . . . . . . . . 2-46
. . . . . 2-45 Edit clause
. . . . . 5-33 Simple Search . . . . . . . . . . . . . . . . . 3-10
. . . . 2-125 Edit Properties shortcut menu
. . . . . . 2-5 command . . . . . . . . . . . . . . . . . 2-84, 2-89
. . . . . 2-45 Effectivity view . . . . . . . . . . . . . . . . . . 2-41
Rich Client Interface Guide Index-3
Index
Embedded viewer . . . . . . . . . . . . . . . 2-128
Enable response to selection . . . . . . . . . 2-77
Enabling
Rich client . . . . . . . . . . . . . . . . . . . . . 1-2
Escape character
Search options . . . . . . . . . . . . . . . . . 3-45
Exact phrase searches . . . . . . . . . . . . . 3-25
Export PLM XML . . . . . . . . . . . . . . . . . 4-8
Exporting
Preferences . . . . . . . . . . . . . . . . . . 2-154
Exporting data . . . . . . . . . . . . . . . . . . . 4-8
Extended multi-application search
Target list . . . . . . . . . . . . . . . . . . . . 3-39
Extended multi-application search
Adhoc classification query . . . . . . . . . 3-39
Extended Multi-Application Search . . 2-129
Extra Model Components option . . . . . . 5-32
F Hierarchical type search option
Factory Structure Editor, see Plant Designer
Fast View command . . . . . . . . . . . . . . 2-78
Favorites . . . . . . . . . . . . . . . . . . . . . . 2-92
Rich client . . . . . . . . . . . . . . . 2-92, 2-100
Search option . . . . . . . . . . . . . . . . . 3-46
Favorites folder
Rename . . . . . . . . . . . . . . . . . . . . 2-101
Folder
Create . . . . . . . . . . . . . . . . . . . . . . 2-120
Delete . . . . . . . . . . . . . . . . . . . . . . 2-123
Home, Newstuff and Mailbox
folders . . . . . . . . . . . . . . . . . . . 2-117
Print . . . . . . . . . . . . . . . . . . . . . . . 2-123
Rename . . . . . . . . . . . . . . . . . . . . 2-121
Folder pane . . . . . . . . . . . . . . 2-124–2-125
Folders
Working with . . . . . . . . . . . . . . . . . 2-120
Form-based
Search . . . . . . . . . . . . . . . . . . . . . . . 3-6
Full Screen menu command . . . . . . . . . 2-81
Full-text search . . . . . . . . . . . . . . . . . 3-19
Combining with metadata queries . . . 3-26
Full-text search indexes . . . . . . . . . . . . 3-25
Updating . . . . . . . . . . . . . . . . . . . . . 3-25
Full-text searches . . . . . . . . . . . . . . . . 3-21
Function view . . . . . . . . . . . . . . . . . . . 2-40
Fuzzy search . . . . . . . . . . . . . . . . . . . 3-29
G Inspector options . . . . . . . . . . . . . . . . . 5-31
General options . . . . . . . . . . . . . . 5-30, 5-38
Generate Report shortcut menu
command . . . . . . . . . . . . . . . . . 2-83, 2-87
Generic BOP view . . . . . . . . . . . . . . . . 2-30
Index-4 Rich Client Interface Guide
Generic Relationship Manager (GRM)
options . . . . . . . . . . . . . . . . . . . . . . . 5-11
Getting Started . . . . . . . . . . . . . . . . . . . 2-6
Getting Started button
Rich client . . . . . . . . . . . . . . . . . . . . . 1-7
Getting Started view . . . . . . . . . . . . . . 2-22
Graph Overview view . . . . . . . . . . . . . 2-48
Graph Thumbnail Preview view . . . . . . 2-48
Graphical BOM compare options . . . . . 5-43
Graphical history options . . . . . . . . . . . 5-44
Graphics view . . . . . . . . . . . 2-25, 2-30, 2-57
Group . . . . . . . . . . . . . . . . . . . . 5-32–5-33
Rich client logon . . . . . . . . . . . . . . . . 1-5
Groups view . . . . . . . . . . . . . . . . . . . . 2-47
H
Hierarchical preferences . . . . . . . . . . 2-143
. . . . . . 3-45
History links . . . . . . . . . . . . . . . . . . . 2-92
Home . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
Home folder . . . . . . . . . . . . . . . . . . . 2-117
I
I Want To links . . . . . . . . . . . . . . . . . . 2-92
Rich client . . . . . . . . . . . . . . . . . . . . 2-92
Identifier options . . . . . . . . . . . . . . . . 5-39
IDSM permitted sites option . . . . . . . . 5-44
IDSM permitted transfer sites option . . 5-45
IDSM restricted sites option . . . . . . . . . 5-44
Image files . . . . . . . . . . . . . . . . . . . . 2-128
Image Preview view . . . . . . . . . . . . . . 2-42
Impact Analysis view . . . . . . . . . . . . . 2-42
Importing
Preferences . . . . . . . . . . . . . . . . . . 2-155
Importing data . . . . . . . . . . . . . . . . . . 4-10
Inbox interval checking for new tasks
option . . . . . . . . . . . . . . . . . . . . . . . . 5-57
Incremental Change view . . . . . . . . . . 2-30
Incremental changes . . . . . . . . . . . . . . . 4-8
Information center display options,
setting . . . . . . . . . . . . . . . . . . . . . . 2-108
Information center, symbols . . . . . . . . 2-108
Information center, using . . . . . . . . . . 2-107
Input Geometry option . . . . . . . . . . . . 5-30
Inspector Execution Summary Dataset Name
option . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Inspector view . . . . . . . . . . . . . . 2-25–2-26
Instances
Preferences . . . . . . . . . . . . . 2-150–2-151
Integration for I-deas options . . . . . . . . 5-12
Interfaces
PLM00191 J
 Index

Rich client . . . . . . . . . . . . . . . . . . . . . 1-5 Value-description pair display . . . . . . 5-13

Intermediate Data Capture view . . . . . 2-30 List of values (LOV) options . . . . . . . . . 5-12
Internal Trace Report shortcut menu Live update elements . . . . . . . . . . . . . 5-13
command . . . . . . . . . . . . . . . . . 2-85, 2-89 Load search results . . . . . . . . . . . . . . . 3-16
Introduction to the rich client . . . . . . . . . 1-1 Locale
Issue Home . . . . . . . . . . . . . . . . . . . . 2-28 Search options . . . . . . . . . . . . . . . . . 3-46
Issue List Details . . . . . . . . . . . . . . . . 2-28 Localization button . . . . . . . . . . . . . . . 1-11
Issue Manager . . . . . . . . . . . . . . . . . . . 2-6 Lock search pane . . . . . . . . . . . . . . . . 3-36
Issue Preview . . . . . . . . . . . . . . . . . . . 2-28 Lock search view . . . . . . . . . . . . . . . . . 3-34
Item display options . . . . . . . . . . . . . . 5-40 Log Entries view . . . . . . . . . . . . . . . . . 2-38
Item revision options . . . . . . . . . . . . . . 5-41 Logging options . . . . . . . . . . . . . . . . . . 5-14
Item revision separator . . . . . . . . 5-41–5-42 Logical Block view . . . . . . . . . . . . . . . . 2-40
Item revision shown relations . . . . . . . 5-42 Logon, Rich client . . . . . . . . . . . . . . . . . 1-5
Item revisions . . . . . . . . . . . . . . . . . . . 5-42
Item separator . . . . . . . . . . . . . . . . . . 5-40 M
Item shown relations . . . . . . . . . . . . . . 5-40
Item Type option . . . . . . . . . . . . . . . . . 5-32 Mail options . . . . . . . . . . . . . . . . . . . . 5-14
Items . . . . . . . . . . . . . . . . . . . . . . . . . 5-40 Mailbox
folder . . . . . . . . . . . . . . . . . . . . . . 2-117
J Make Immune shortcut menu
command . . . . . . . . . . . . . . . . . 2-84, 2-88
JT Preview view . . . . . . . . . . . . . . . . . 2-42 Manage Global Alternates shortcut menu
command . . . . . . . . . . . . . . . . . 2-85, 2-90
K Manufacturing Features view . . . . . . . . 2-31
Manufacturing Process Planner . . . . . . . 2-8
Keyword search form . . . . .. . . . . . . . . 3-21 Manufacturing Structure Editor, see
Keyword searches . . . . . . .. . . . . 3-20–3-21 Manufacturing Process Planner
Boolean operators . . . . .. . . . . . . . . 3-23 Master locale . . . . . . . . . . . . . . . . . . . 1-12
Bracketed expressions . .. . . . . . . . . 3-23 Master record object . . . . . . . . . . . . . . . 4-2
Exact phrase . . . . . . . . .. . . . . . . . . 3-25 Master value . . . . . . . . . . . . . . . . . . . 1-12
Properties and keywords . . . . . . . . . 3-21 Material and Substance Dashboard . . . 2-36
Proximity . . . . . . . . . . .. . . . . . . . . 3-24 Memory Layout view . . . . . . . . . . . . . . 2-48
Keywords to Import option .. . . . . . . . . 5-28 Menu bar . . . . . . . . . . . . . . . . . . 1-5, 2-124
Rich client . . . . . . . . . . . . . . . . . . . . . 1-5
L Menu commands
Close Perspective . . . . . . . . . . . . . . . 2-80
L10N Result View view . . . . . . . . . . . . 2-42 Full Screen . . . . . . . . . . . . . . . . . . . 2-81
Latest dataset version Move . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Search option . . . . . . . . . . . . . . . . . 3-44 Navigation Pane . . . . . . . . . . . . . . . 2-81
Launch Pad . . . . . . . . . . . . . . . . 2-6, 2-109 Open Perspective . . . . . . . . . . . . . . . 2-79
Launch Pad view . . . . . . . . . . . . . . . . . 2-48 Paste Special . . . . . . . . . . . . . . . . . 2-112
Layout Preferences . . . . . . . . . . . . . . . . . . . 2-81
Saving . . . . . . . . . . . . . . . . . . . . . . 2-14 Reset Perspective . . . . . . . . . . . . . . . 2-80
Left-Right Trace View option . . . . . . . . 5-27 Save Perspective As . . . . . . . . . . . . . 2-80
Libraries view . . . . . . . . . . . . . . . . . . . 2-37 Show View . . . . . . . . . . . . . . . 2-80–2-81
License shortcut menu command . . . . 2-85, Toolbar . . . . . . . . . . . . . . . . . . . . . . 2-81
2-89 Menus
Lifecycle Viewer . . . . . . . . . . . . . . . . . . 2-7 Rich client . . . . . . . . . . . . . . . . . . . . 2-79
Lifecycle Visualization options . . . . . . . 5-53 Shortcut . . . . . . . . . . . . . . . . . . . . . 2-82
Line Balancing Chart view . . . . . . . . . . 2-30 Window . . . . . . . . . . . . . . . . . . . . . . 2-79
Line Balancing Constraints view . . . . . 2-30 Meshing Tools option . . . . . . . . . . . . . . 5-29
Linked Occurrence Paths view . . . . . . . 2-31 Microsoft Word files . . . . . . . . . . . . . . 2-128
List of values Missing Model Components option . . . . 5-31
Displaying descriptions . . . . . . . . . . 5-13 Mixed-language display

PLM00191 J Rich Client Interface Guide Index-5

Index
Rich client . . . . . . . . . . . . . . . . . . . . . 1-4
Model view . . . . . . . . . . . . . . . . . . . . . 2-25
Model With Different Product Revision Target
option . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Model With No Product option . . . . . . . 5-32
Modifying
Preference values . . . . . . . . . . . . . . 2-152
Monitoring system performance . . . . . . . 5-3
Move
Objects . . . . . . . . . . . . . . . . . . . . . 2-122
Move a view . . . . . . . . . . . . . . . . . . . . 2-71
Move menu command . . . . . . . . . . . . . 2-51
Moving data . . . . . . . . . . . . . . 2-110, 2-113
MS Word view . . . . . . . . . . . . . . . . . . 2-42
Multi-Site Collaboration options
IDSM restricted sites . . . . . . . . . . . . 5-44
Multi-Site Collaboration options
Publishable classes . . . . . . . . . . . . . 5-49
Multi-Site Collaboration options
IDSM permitted transfer sites . . . . . 5-45
Multi-Site Collaboration options . . . . . . 5-44
Multi-Site Collaboration options
Transfer directory . . . . . . . . . . . . . . 5-49
Multi-Site Collaboration options
IDSM permitted sites . . . . . . . . . . . . 5-44
Multi-Structure Manager . . . . . . . . . . . . 2-8
Multi-Structure Manager view . . . . . . . 2-22
Multiple entry search options . . . . . . . . 3-45
Multisite Synchronization shortcut menu
command . . . . . . . . . . . . . . . . . 2-86, 2-90
My Projects view . . . . . . . . . . . . . . . . . 2-37
My Teamcenter . . . . . . . . . . . . . . . . . . . 2-8
Open . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Purpose . . . . . . . . . . . . . . . . . . . . . . . 1-1
Shortcut menus . . . . . . . . . . . . 2-82, 2-86
MySearchHistory_Limit preference . . . . 3-8
N ARM Transaction Monitor . . . . . . . . . 5-3
Name search box . . . . . . . . . . . . . . . . 2-125
Navigation pane . . . . . . . . . . . . . . . . . . 1-7
Rich client . . . . . . . . . . . . . . . . . . . . . 1-7
Navigation Pane menu command . . . . . 2-81
Navigator view . . . . . . . . . . . . . . . . . . 2-47
New Change in context shortcut menu
command . . . . . . . . . . . . . . . . . 2-82, 2-86
New shortcut menu command . . . 2-82, 2-87
Newstuff folder . . . . . . . . . . . . . . . . . 2-117
No Action option . . . . . . . . . . . . . . . . . 5-31
Notify request . . . . . . . . . . . . . . . . . . . . 4-3
NX options . . . . . . . . . . . . . . . . . . . . . 5-20
NX part family options . . . . . . . . . . . . 5-49
Publish both part family members and
templates . . . . . . . . . . . . . . . . . . 5-50
Index-6 Rich Client Interface Guide
Publish neither part family members nor
templates . . . . . . . . . . . . . . . . . . 5-50
Publish part family members . . . . . . 5-50
Publish part family members also . . . 5-50
Publish part family templates also . . 5-50
Publish part family templates instead of
members . . . . . . . . . . . . . . . . . . 5-50
NX Remote Manager (AIE) options . . . . . 5-1
O
Object Directory Service (ODS)
options . . . . . . . . . . . . . . . . . . . . . . . 5-50
Object references, pasting . . . . . . . . . 2-112
Objects
Copying . . . . . . . . . . . . . . . . . . . . 2-112
Cutting . . . . . . . . . . . . . . . . . . . . . 2-111
Deleting . . . . . . . . . . . . . . . 2-110–2-111
Moving . . . . . . . . . . . . . . . . . . . . . 2-110
Printing . . . . . . . . . . . . . . . . . . . . 2-133
ODS options
Default ODS site . . . . . . . . . . . . . . . 5-51
Permitted sites . . . . . . . . . . . . . . . . 5-51
Restricted sites . . . . . . . . . . . . . . . . 5-51
Searchable sites . . . . . . . . . . . . . . . . 5-51
Searchable sites excluded . . . . . . . . . 5-51
Open
My Teamcenter . . . . . . . . . . . . . . . . 2-14
Open Change view . . . . . . . . . . . . . . . 2-26
Open items . . . . . . . . . . . . . . . . . . . . . 2-92
Open Perspective menu command . . . . . 2-79
Open Service Request view . . . . . . . . . 2-48
Open Task view . . . . . . . . . . . . . . . . . 2-26
Opening Application Interface Viewer . . . 4-6
Option defaults . . . . . . . . . . . . . . . . . . 2-36
Options . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Allow live updates . . . . . . . . . . . . . . 5-13
BOM tracking . . . . . . . . . . . . . . . . . 5-34
CAE tools . . . . . . . . . . . . . . . . . . . . 5-28
Calendar . . . . . . . . . . . . . . . . . . . . . 5-34
Change Management . . . . . . . . . . . . 5-34
Change Search . . . . . . . . . . . . . . . . 3-33
Checkin . . . . . . . . . . . . . . . . . . . . . 5-38
Checkout . . . . . . . . . . . . . . . . . . . . . 5-38
Computer-Aided Engineering (CAE)
tools . . . . . . . . . . . . . . . . . . . . . . 5-28
Dataset . . . . . . . . . . . . . . . . . . . . . . 5-10
DesignContext . . . . . . . . . . . . . . . . . 5-36
General . . . . . . . . . . . . . . . . . . . . . . 5-38
Generic Relationship Manager
(GRM) . . . . . . . . . . . . . . . . . . . . 5-11
Graphical BOM compare . . . . . . . . . 5-43
Identifier . . . . . . . . . . . . . . . . . . . . . 5-39
PLM00191 J

IDSM permitted sites . . . . . . . . . . . . 5-44
IDSM permitted transfer sites . . . . . 5-45
IDSM restricted sites . . . . . . . . . . . . 5-44
Integration for I-deas . . . . . . . . . . . . 5-12
Item display . . . . . . . . . . . . . . . . . . 5-40
Item revision . . . . . . . . . . . . . . . . . . 5-41
List of values . . . . . . . . . . . . . . . . . . 5-12
Live update elements . . . . . . . . . . . . 5-13
Logging . . . . . . . . . . . . . . . . . . . . . . 5-14
Mail . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Multi-Site Collaboration . . . . . . . . . . 5-44
Multi-Site Collaboration IDSM . . . . . 5-44
Multi-Site Collaboration import
remote . . . . . . . . . . . . . . . . . . . . 5-45
Multi-Site Collaboration
miscellaneous . . . . . . . . . . . . . . . 5-49
Multi-Site Collaboration NX part
family . . . . . . . . . . . . . . . . . . . . 5-49
Multi-Site Collaboration Object Directory
Service (ODS) . . . . . . . . . . . . . . . 5-50
NX . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
NX Remote Manager (AIE) . . . . . . . . . 5-1
Project . . . . . . . . . . . . . . . . . . . . . . 5-21
Publishable classes . . . . . . . . . . . . . 5-49
RDV . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Refresh notify . . . . . . . . . . . . . . . . . 5-21
Refresh Notify . . . . . . . . . . . . . . . . . 5-21
Rich client . . . . . . . . . . . . . . . . . . . . . 1-2
Search . . . . . . . . . . . . . . . . . . 3-44, 5-51
Security . . . . . . . . . . . . . . . . . . . . . 5-26
Setting . . . . . . . . . . . . . . . . . . . . . 2-145
Simulation tools . . . . . . . . . . . . . . . . 5-33
STEP Translator . . . . . . . . . . . . . . . 5-23
Structure Manager (Structure
Manager) . . . . . . . . . . . . . . . . . . 5-20
System . . . . . . . . . . . . . . . . . . . . . . 5-27
Systems Engineering . . . . . . . . . . . . 5-27
Transfer directory . . . . . . . . . . . . . . 5-49
User interface . . . . . . . . . . . . . . . . . 5-42
Visualization . . . . . . . . . . . . . . . . . . 5-53
Visualization options . . . . . . . . . . . . 5-53
Work Breakdown Structure (WBS) . . 5-28
Workflow . . . . . . . . . . . . . . . . . . . . . 5-56
Organization . . . . . . . . . . . . . . . . . . . . 2-8
Organization (Command Suppression)
view . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Organization view . . . . . . . . . . . . . . . . 2-19
Out of Scope option . . . . . . . . . . . . . . . 5-31
Outline view . . . . . . . . . . . . . . . . . . . . 2-17
P Launch Pad . . . . . . . . . . . . . . . . . . . . 2-6
Pack display option . . . . . . . . . . . . . . . 5-20
PAD Element view . . . . . . . . . . . . . . . 2-31
PLM00191 J
Index
PAD view . . . . . . . . . . . . . . . . . . . . . . 2-31
Palette view . . . . . . . . . . . . . . . . . . . . 2-17
Parameter/Criteria Files option . . . . . . 5-30
Part Planner . . . . . . . . . . . . . . . . . . . . . 2-8
Part Planner Activities view . . . . . . . . . 2-31
Password
Rich client logon . . . . . . . . . . . . . . . . 1-5
Passwords . . . . . . . . . . . . . . . . . . . . 2-105
Paste
Outside Teamcenter . . . . . . . . . . . . 2-113
Specify relation type . . . . . . . . . . . . 2-112
URLs . . . . . . . . . . . . . . . . . . . . . . 2-113
Paste shortcut menu command . . . 2-83, 2-87
Pasting
Clipboard contents . . . . . . . . . . . . . 2-112
Object references . . . . . . . . . . . . . . 2-112
Paths view . . . . . . . . . . . . . . . . . . . . . 2-47
Performance monitoring . . . . . . . . . . . . 5-3
BOM transactions . . . . . . . . . . . . . . . 5-6
Change transactions . . . . . . . . . . . . . 5-7
Multi-Site Collaboration
transactions . . . . . . . . . . . . . . . . . 5-8
Server transactions . . . . . . . . . . . . . . 5-6
User interface transactions . . . . . . . . . 5-3
Workflow transactions . . . . . . . . . . . . 5-6
Performing advanced searches . . . . . . . . 3-6
Performing quick searches . . . . . . . . . . . 3-2
Perspectives
4G Designer . . . . . . . . . . . . . . . . . . . 2-2
4G Designer-MBOM Reconciliation . . . 2-2
Access Manager . . . . . . . . . . . . . . . . . 2-2
ADA License . . . . . . . . . . . . . . . . . . . 2-2
Appearance Configuration . . . . . . . . . 2-3
As-Built Manager . . . . . . . . . . . . . . . 2-3
CAE Manager . . . . . . . . . . . . . . . . . . 2-3
CAE Manager (Legacy) . . . . . . . . . . . . 2-4
CAE Structure Designer . . . . . . . . . . . 2-4
Change Manager . . . . . . . . . . . . . . . . 2-4
Classification . . . . . . . . . . . . . . . . . . . 2-4
Classification Administration . . . . . . . 2-4
Closing . . . . . . . . . . . . . . . . . . . . . . 2-15
Command Suppression . . . . . . . . . . . . 2-5
Content Management . . . . . . . . . . . . . 2-5
Dashboard . . . . . . . . . . . . . . . . . . . . . 2-5
Database Utilities . . . . . . . . . . . . . . . 2-5
DesignContext . . . . . . . . . . . . . . . . . . 2-5
DPV Measurements . . . . . . . . . . . . . . 2-5
Getting Started . . . . . . . . . . . . . . . . . 2-6
In general . . . . . . . . . . . . . . . . . . . . . 1-9
Issue Manager . . . . . . . . . . . . . . . . . . 2-6
Lifecycle Viewer . . . . . . . . . . . . . . . . . 2-7
Manufacturing Process Planner . . . . . 2-8
Multi-Structure Manager . . . . . . . . . . 2-8
Rich Client Interface Guide Index-7
Index
My Teamcenter . . . . . . . . . . . . . . . . . 2-8
Opening . . . . . . . . . . . . . . . . . . 2-1, 2-14
Organization . . . . . . . . . . . . . . . . . . . 2-8
Part Planner . . . . . . . . . . . . . . . . . . . 2-8
Plant Designer . . . . . . . . . . . . . . . . . . 2-9
Platform Designer . . . . . . . . . . . . . . . 2-9
PLM XML/TC XML Export Import
Administration . . . . . . . . . . . . . . . 2-8
Product Configurator . . . . . . . . . . . . . 2-9
Project . . . . . . . . . . . . . . . . . . . . . . . 2-9
Query Builder . . . . . . . . . . . . . . . . . . 2-9
Registry Editor . . . . . . . . . . . . . . . . . 2-9
Relation Browser . . . . . . . . . . . . . . . 2-10
Report Builder . . . . . . . . . . . . . . . . . 2-10
Report Generator . . . . . . . . . . . . . . . 2-10
Requirements Manager . . . . . . . . . . 2-10
Reset . . . . . . . . . . . . . . . . . . . . . . . 2-14
Resource Manager . . . . . . . . . . . . . . 2-10
Saving . . . . . . . . . . . . . . . . . . . . . . 2-14
Schedule Manager . . . . . . . . . . . . . . 2-10
Service Manager . . . . . . . . . . . . . . . 2-11
Service Planner . . . . . . . . . . . . . . . . 2-11
Service Request Manager . . . . . . . . . 2-11
Service Scheduler . . . . . . . . . . . . . . 2-11
Setup Wizard . . . . . . . . . . . . . . . . . . 2-11
Software Parameter Manager . . . . . . 2-12
Specification Manager . . . . . . . . . . . 2-12
Structure Manager . . . . . . . . . . . . . . 2-12
Subscription Monitor . . . . . . . . . . . . 2-12
Switch between open perspectives . . . 2-14
Systems Engineering . . . . . . . . . . . . 2-13
Validation Manager . . . . . . . . . . . . . 2-13
Volume Management . . . . . . . . . . . . 2-13
Web Browser . . . . . . . . . . . . . . . . . . 2-13
Workflow Designer . . . . . . . . . . . . . . 2-13
Workflow Viewer . . . . . . . . . . . . . . . 2-13
PERT view . . . . . . . . . . . . . . . . . . . . . 2-32
Physical Part Usage History view . . . . . 2-38
Pin to Launch Pad shortcut menu
command . . . . . . . . . . . . . . . . . 2-83, 2-87
Plan Details view . . . . . . . . . . . . . . . . 2-38
Plant BOP view . . . . . . . . . . . . . . . . . 2-32
Plant Designer . . . . . . . . . . . . . . . . . . . 2-9
Platform Designer . . . . . . . . . . . . . . . . . 2-9
Platform Designer view . . . . . . . . . . . . 2-23
PLM XML/TC XML Export Import
Administration . . . . . . . . . . . . . . . . . . 2-8
PLM XML/TC XML Export Import
Administration view . . . . . . . . . . . . . 2-19
PMI view . . . . . . . . . . . . . . . . . . . . . . 2-47
Portfolio files . . . . . . . . . . . . . . . . . . 2-128
Preference
Category . . . . . . . . . . . . . . . . . . . . 2-142
Description . . . . . . . . . . . . . . . . . . 2-143
Index-8 Rich Client Interface Guide
Environment . . . . . . . . . . . . . . . . . 2-142
Location . . . . . . . . . . . . . . . . . . . . 2-141
Multiple . . . . . . . . . . . . . . . . . . . . 2-143
Name . . . . . . . . . . . . . . . . . . . . . . 2-141
Options dialog box . . . . . . . . . . . . . 2-144
Protection Scope . . . . . . . . . . . . . . 2-142
Type . . . . . . . . . . . . . . . . . . . . . . . 2-143
Value . . . . . . . . . . . . . . . . . . . . . . 2-143
Preferences . . . . . . . . . . . . . . . . . . . . 2-140
Adding values . . . . . . . . . . . . . . . . 2-153
Change_Search_Default . . . . . . . . . . . 3-8
Creating . . . . . . . . . . . . . . . . . . . . 2-149
Creating categories . . . . . . . . . . . . 2-148
Creating instances . . . . . . . . 2-150–2-151
Default Base Calendar . . . . . . . . . . . 5-34
defaultViewerConfig_
VIEWERCONFIG . . . . . . . . . . . . 2-69
Deleting categories . . . . . . . . . . . . . 2-148
Exporting . . . . . . . . . . . . . . . . . . . 2-154
Filters search . . . . . . . . . . . . . . . . 2-146
Hierarchical . . . . . . . . . . . . . . . . . 2-143
Importing . . . . . . . . . . . . . . . . . . . 2-155
Keyword search . . . . . . . . . . . . . . . 2-146
Modifying values . . . . . . . . . . . . . . 2-152
MySearchHistory_Limit . . . . . . . . . . . 3-8
Primary manifestation relation . . . . . 5-11
Primary master form relation . . . . . . 5-12
Primary reference relation . . . . . . . . 5-11
Primary requirement relation . . . . . . 5-11
QRY_search_classification_
hierarchy . . . . . . . . . . . . . . . . . . 3-42
QRY_search_type_hierarchy . . . . . . . 3-45
Refresh Notify . . . . . . . . . . . . . . . . . 5-21
Removing values . . . . . . . . . . . . . . 2-153
Rich client . . . . . . . . . . . . . . . . . . . . . 1-2
Search . . . . . . . . . . . . . . . . . . . . . . 3-44
search_automatic_wildcard . . . . . . . . 3-28
Searching for . . . . . . . . . . . . . . . . . 2-146
Start of Week . . . . . . . . . . . . . . . . . . 5-34
System . . . . . . . . . . . . . . . . . . . . . 2-143
TC_fts_indexed_types . . . . . . . . . . . . 3-20
TC_fts_real_time_indexing . . . . . . . . 3-20
TC_wc_show_all . . . . . . . . . . . . . . 2-107
<viewer-config-
ID>.VIEWERCONFIG . . . . . . . . . 2-69
Viewer.VIEWERCONFIGTOLOAD . . 2-70
Viewing . . . . . . . . . . . . . . . . . . . . . 2-147
Window . . . . . . . . . . . . . . . . . 2-81, 2-156
Preferences command . . . . . . . . . . . . . 2-81
Preferences, TC_Graph_Node_Thumbnail_
Shown . . . . . . . . . . . . . . . . . . . . . . . 2-60
preferences_manager utility . . . . . . . . 2-144
Prerequisites, Rich client . . . . . . . . . . . . 1-1
PLM00191 J
 Index

Prevent overwriting of query form PSD view . . . . . . . . . . . . . . . . . . . . . . 2-33

content . . . . . . . . . . . . . . . . . . . 3-34, 3-36 Pseudofolders
Preview view . . . . . . . . . . . . . . . . . . . 2-27 Shown relations . . . . . . . . . . . . . . . 2-119
Primary application buttons . . . . . . 1-7, 2-92 Using . . . . . . . . . . . . . . . . . . . . . . 2-118
Rich client . . . . . . . . . . . . . . . . . . . . . 1-7 Publication Structure view . . . . . . . . . . 2-27
Primary applications . . . . . . . . . . . . . . 2-99 Publish request . . . . . . . . . . . . . . . . . . . 4-3
Primary manifestation relation . . . . . . 5-11 Creating . . . . . . . . . . . . . . . . . . . . . 4-10
Primary master form relation . . . . . . . . 5-12 Processing . . . . . . . . . . . . . . . . . . . . 4-11
Primary perspective buttons Publish request object . . . . . . . . . . . . . . 4-2
Rich client . . . . . . . . . . . . . . . . . . . . 2-92 Publish request states . . . . . . . . . . . . . . 4-4
Primary reference relation . . . . . . . . . . 5-11 Publishable classes option . . . . . . . . . . 5-49
Primary requirement relation . . . . . . . 5-11 Purge shortcut menu command . . 2-84, 2-88
Print
Folder . . . . . . . . . . . . . . . . . . . . . . 2-123 Q
Print formats . . . . . . . . . . . . . . . . . . 2-132
Print Object view . . . . . . . . . . . . . . . . 2-27 QRY_search_classification_hierarchy
Printing preference . . . . . . . . . . . . . . . . . . . . . 3-42
Form properties . . . . . . . . . . 2-136–2-137 QRY_search_type_hierarchy
in Teamcenter Rapid Start . . . . . . . 2-138 preference . . . . . . . . . . . . . . . . . . . . . 3-45
Object properties . . . . . . . . . . . . . . 2-134 Query
Objects . . . . . . . . . . . . . . . . . . . . . 2-133 Cancel . . . . . . . . . . . . . . . . . . . . . . . 3-6
Search results tree . . . . . . . . . . . . . . 3-19 Definition view . . . . . . . . . . . . . . . . 3-37
Table properties . . . . . . . . . . . . . . . 2-136 Form lock . . . . . . . . . . . . . . . . 3-34, 3-36
Where-referenced reports . . . . . . . . 2-136 Search options . . . . . . . . . . . . . . . . . 3-44
Printing watermarks . . . . . . . . . . . . . 2-139 Query Builder . . . . . . . . . . . . . . . . . . . . 2-9
Process Gantt view . . . . . . . . . . . . . . . 2-32 Query Builder view . . . . . . . . . . . . . . . 2-19
Process request . . . . . . . . . . . . . . . . . . . 4-7 Query definition
Process view . . . . . . . . . . . . . . . . . . . . 2-32 Modify . . . . . . . . . . . . . . . . . . 3-37–3-38
Processes Query definitions . . . . . . . . . . . . . . . . 3-47
Creating a process flow . . . . . . . . . . . 2-32 Query options . . . . . . . . . . . . . . . . . . . 3-44
Product BOP view . . . . . . . . . . . . . . . . 2-32 Adhoc Classification . . . . . . . . . . . . . 3-39
Product Configurator . . . . . . . . . . . . . . . 2-9 Sorting by attribute . . . . . . . . . . . . . 3-47
Product Manual view . . . . . . . . . . . . . 2-33 Quick Create Panel option . . . . . . . . . . 5-28
Product Structure Editor, see Structure Quick links . . . . . . . . . . . . . . . . . . . . . 2-92
Manager Rich client . . . . . . . . . . . . . . . . . . . . 2-92
Product view . . . . . . . . . . . . . . . . 2-25, 2-32 Quick open results
Product View Search view . . . . . . . . . . 2-33 Search . . . . . . . . . . . . . . . . . . . . . . . 3-2
Product with no Model option . . . . . . . . 5-31 Quick Open search . . . . . . . . . . . . . . . 2-92
Progress view . . . . . . . . . . . . . . . . . . . 2-17 Rich client . . . . . . . . . . . . . . . . . . . . 2-92
Project . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Quick search . . . . . . . . . . . . . . . . . . . . . 3-2
Project options . . . . . . . . . . . . . . . . . . 5-21 Rich client . . . . . . . . . . . . . . . . . . . . . 1-6
Project shortcut menu command . . . . . 2-85,
2-89 R
Project view . . . . . . . . . . . . . . . . . . . . 2-37
Properties RDV options . . . . . . . . . . . . . . . . . . . . 5-36
Printing . . . . . . . . . . 2-134, 2-136–2-137 Referencers pane . . . . . . . . . . . . . . . 2-129
Properties dialog box, printing . . . . . . 2-134, Refresh . . . . . . . . . . . . . . . . . . . . . . . . 4-7
2-136 Search . . . . . . . . . . . . . . . . . . . . . . 3-34
Properties on Relation shortcut menu Refresh notify options . . . . . . . . . . . . . 5-21
command . . . . . . . . . . . . . . . . . 2-84, 2-89 Refresh Notify options . . . . . . . . . . . . . 5-21
Properties view . . . . . . . . . . . . . . . . . . 2-17 Refresh shortcut menu command . . . . 2-84,
Property Finder Formatter (PFF) . . . . . 3-17 2-88
Proximity search operators . . . . . . . . . 3-24 Registry Editor . . . . . . . . . . . . . . . . . . . 2-9
Proximity searches . . . . . . . . . . . . . . . 3-24 Registry Editor view . . . . . . . . . . . . . . 2-45

PLM00191 J Rich Client Interface Guide Index-9

Index
Reject sync request . . . . . . . . . . . . . . . . 4-7
Relation Browser . . . . . . . . . . . . . . . . 2-10
View . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Relation types . . . . . . . . . . . . . . . . . . 2-112
Remote
Search option . . . . . . . . . . . . . . . . . 3-46
Remote import options . . . . . . . . . . . . . 5-45
Exclude export-protected
components . . . . . . . . . . . . . . . . 5-47
Exclude export-protected objects . . . . 5-46
Exclude folder contents . . . . . . . . . . . 5-46
Include all dataset versions . . . . . . . . 5-46
Include all files . . . . . . . . . . . . . . . . 5-47
Include all revisions . . . . . . . . . . . . . 5-45
Include and exclude lists . . . . . . . . . . 5-48
Include entire BOM . . . . . . . . . . . . . 5-47
Include modified objects only . . . . . . . 5-46
Latest any release status . . . . . . . . . 5-46
Latest revision only . . . . . . . . . . . . . 5-45
Latest working any release status . . . 5-45
Latest working revision only . . . . . . . 5-45
Perform import/export in
background . . . . . . . . . . . . . . . . . 5-45
Save all options as default . . . . . . . . 5-46
Selected revisions only . . . . . . . . . . . 5-46
Specific release status only . . . . . . . . 5-46
Synchronize automatically . . . . . . . . 5-48
Synchronize in batch mode . . . . . . . . 5-48
Transfer top-level item only . . . . . . . 5-47
Remove Immunity shortcut menu
command . . . . . . . . . . . . . . . . . 2-84, 2-88
Removing
Columns . . . . . . . . . . . . . . . . . . . . 2-127
Rename
Favorites folder . . . . . . . . . . . . . . . 2-101
Folder . . . . . . . . . . . . . . . . . . . . . . 2-121
Rename search results . . . . . . . . . . . . . 3-19
Renaming
Search results . . . . . . . . . . . . . . . . . 3-19
Reorder
Objects . . . . . . . . . . . . . . . . . . . . . 2-122
Report Builder . . . . . . . . . . . . . . . . . . 2-10
Report Builder view . . . . . . . . . . . . . . 2-20
Report Generation Wizard . . . . . . 2-83, 2-87
Report Generator . . . . . . . . . . . . . . . . 2-10
Report Generator view . . . . . . . . . . . . . 2-49
Report view . . . . . . . . . . . . . . . . . . . . 2-33
Reports
Generate . . . . . . . . . . . . . . . . . 2-83, 2-87
Request Home view . . . . . . . . . . . . . . . 2-39
Request status transitions . . . . . . . . . . . 4-5
Request tables, customizing . . . . . . . . . . 4-7
Required Items view . . . . . . . . . . . . . . 2-33
Requirement Expression view . . . . . . . 2-40
Index-10 Rich Client Interface Guide
Requirement view . . . . . . . . . . . . . . . . 2-40
Requirements Manager . . . . . . . . . . . . 2-10
Rerun
Search . . . . . . . . . . . . . . . . . . . . . . 3-34
Resequence Structure shortcut menu
command . . . . . . . . . . . . . . . . . 2-83, 2-87
Reset Perspective menu command . . . . 2-80
Resize a view . . . . . . . . . . . . . . . . . . . 2-71
Resource Manager . . . . . . . . . . . . . . . . 2-10
Resource view . . . . . . . . . . . . . . . . . . . 2-33
Results
Search option . . . . . . . . . . . . . . . . . 3-46
Reveal Related Views command . . . . . . 2-79
Rich client
Application banner . . . . . . . . . . . . . . . 1-6
Application pane . . . . . . . . . . . . . . . . 1-7
Back and forward buttons . . . . . . . . . . 1-6
Clipboard button . . . . . . . . . . . . . . . . 1-7
Configure Applications button . . . . . . 2-92
Enabling . . . . . . . . . . . . . . . . . . . . . . 1-2
Favorites . . . . . . . . . . . . . . . . 2-92, 2-100
Getting Started button . . . . . . . . . . . . 1-7
History links . . . . . . . . . . . . . . . . . . 2-92
I Want To links . . . . . . . . . . . . . . . . 2-92
Information center . . . . . . . . . . . . . 2-107
Menu bar . . . . . . . . . . . . . . . . . . . . . 1-5
Menus . . . . . . . . . . . . . . . . . . . . . . 2-79
Navigation pane . . . . . . . . . . . . . . . . 1-7
Open items . . . . . . . . . . . . . . . . . . . 2-92
Options . . . . . . . . . . . . . . . . . . . . . . . 1-2
Persistent caches . . . . . . . . . . . . . . 2-157
Preferences . . . . . . . . . . . . . . . . . . . . 1-2
Prerequisites . . . . . . . . . . . . . . . . . . . 1-1
Primary application buttons . . . . 1-7, 2-92
Purpose . . . . . . . . . . . . . . . . . . . . . . . 1-1
Quick links . . . . . . . . . . . . . . . . . . . 2-92
Quick Open search . . . . . . . . . . . . . . 2-92
Search . . . . . . . . . . . . . . . . . . . . . . . 3-3
Search field . . . . . . . . . . . . . . . . . . . . 1-6
Search results . . . . . . . . . . . . . . . . . 3-13
Secondary application buttons . . . 1-7, 2-92
Server condition symbol . . . . . . . . . . . 1-9
Simple search . . . . . . . . . . . . . . . . . . 3-9
Starting . . . . . . . . . . . . . . . . . . . . . . 1-4
Teamcenter logon . . . . . . . . . . . . . . . . 1-5
Toolbar . . . . . . . . . . . . . . . . . . . . . . . 1-5
User interface condition symbol . . . . . . 1-9
Rich client application panes
Application tab . . . . . . . . . . . . . . . 2-124
Button bar . . . . . . . . . . . . . . . . . . 2-125
Command bar . . . . . . . . . . . . . . . . 2-126
Data pane . . . . . . . . . . . . . . . . . . . 2-125
Folder pane . . . . . . . . . . . . . 2-124–2-125
Menu bar . . . . . . . . . . . . . . . . . . . 2-124
PLM00191 J
 Index

Most recently uses (MRU) . . . . . . . . 2-125 Hierarchical type . . . . . . . . . . . . . . . 3-45

Name search box . . . . . . . . . . . . . . 2-125 Input . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Open home folder . . . . . . . . . . . . . . 2-125 Latest dataset version . . . . . . . . . . . 3-44
Open Worklist . . . . . . . . . . . . . . . . 2-125 Locale . . . . . . . . . . . . . . . . . . . . . . . 3-46
Status indicators . . . . . . . . . . . . . . 2-126 menus and options . . . . . . . . . . . . . . . 3-8
Toolbar . . . . . . . . . . . . . . . . . . . . . 2-124 Multiple entry options . . . . . . . . . . . 3-45
Tree pane . . . . . . . . . . . . . . 2-124–2-125 Options . . . . . . . . . . . . . . . . . . . . . . 3-44
User interface . . . . . . . . . . . . . . . . 2-124 overview . . . . . . . . . . . . . . . . . . . . . . 3-7
Rich client interface . . . . . . . . . . . . . . . 1-5 Preferences . . . . . . . . . . . . . . . . . . . 3-44
Rich client perspectives Query options . . . . . . . . . . . . . . . . . 3-44
Closing . . . . . . . . . . . . . . . . . . . . . . 2-15 Quick . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Opening . . . . . . . . . . . . . . . . . . . . . 2-14 Quick open results . . . . . . . . . . . . . . . 3-2
Reset . . . . . . . . . . . . . . . . . . . . . . . 2-14 Refresh . . . . . . . . . . . . . . . . . . . . . . 3-34
Saving . . . . . . . . . . . . . . . . . . . . . . 2-14 remote option . . . . . . . . . . . . . . . . . 3-46
Rich client perspectives and views . . . . . 1-9 Rerun . . . . . . . . . . . . . . . . . . . . . . . 3-34
Rich client views . . . . . . . . . . . . . . . . . . 1-9 Sort . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Role Status of indexed objects . . . . . . . . . . 3-25
Rich client logon . . . . . . . . . . . . . . . . 1-5 Synonym . . . . . . . . . . . . . . . . . . . . . 3-29
Roll Up view . . . . . . . . . . . . . . . . . . . . 2-27 Target list . . . . . . . . . . . . . . . . . . . . 3-42
Rule checks . . . . . . . . . . . . . . . . . . . . 2-36 types . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
View . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
S Wildcard options . . . . . . . . . . . . . . . 3-45
Wildcards . . . . . . . . . . . . . . . . . . . . 3-28
Save Perspective As menu command . . . 2-80 Search criteria
Save search results . . . . . . . . . . . . . . . 3-35 Date and time . . . . . . . . . . . . . . . . . 3-30
Saved queries Table values . . . . . . . . . . . . . . . . . . 3-30
Classification attributes . . . . . . . . . . 3-42 Values from lists . . . . . . . . . . . . . . . 3-31
Saved searches Search criteria definition
Search option . . . . . . . . . . . . . . . . . 3-46 Modifying . . . . . . . . . . . . . . . . 3-37–3-38
Saving View . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Search results to a folder . . . . . . . . . 3-35 Search enhancements
Search results to a folder in a data TC_QRY_xxx_REVRULE
pane . . . . . . . . . . . . . . . . . . . . . . 3-36 preference . . . . . . . . . . . . . . . . . 3-39
Schedule Manager . . . . . . . . . . . . . . . . 2-10 Search field . . . . . . . . . . . . . . . . . . . . . 1-6
Schedule Manager view . . . . . . . . . . . . 2-23 Search forms
Schedule Task Execution . . . . . . . . . . . 2-37 Dataset . . . . . . . . . . . . . . . . . . 3-21, 3-31
Search . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Dataset Keyword Search . . . . . . . . . 3-21
Ad hoc classification . . . . . . . . . . . . . 3-39 General . . . . . . . . . . . . . . . . . . . . . . 3-31
Advanced . . . . . . . . . . . . . . . . . . . . . 3-6 Keyword . . . . . . . . . . . . . . . . . . . . . 3-21
Business object type . . . . . . . . . . . . . 3-45 Search options . . . . . . . . . . . . . . . . . . 5-51
Case sensitivity . . . . . . . . . . . . . . . . 3-44 Business Object Type . . . . . . . . . . . . 5-51
Change . . . . . . . . . . . . . . . . . . . . . . 3-34 Case sensitive . . . . . . . . . . . . . . . . . 5-52
Classification attributes . . . . . . . . . . 3-42 Clear search history . . . . . . . . . . . . . 3-46
Classification data . . . . . . . . . . . . . . 3-39 Configure the search history size . . . 3-46,
Classification hierarchy . . . . . . . . . . 3-44 5-53
Clear . . . . . . . . . . . . . . . . . . . . . . . 3-34 Default business object type . . . . . . . 5-52
Default . . . . . . . . . . . . . . . . . . . . . . 3-45 Default search . . . . . . . . . . . . . . . . . 5-52
Escape character . . . . . . . . . . . . . . . 3-45 Delimiting character . . . . . . . . . . . . 5-52
Favorites . . . . . . . . . . . . . . . . . . . . . 3-46 Display my saved searches . . . . . . . . 5-53
Filters . . . . . . . . . . . . . . . . . . . . . . . 3-42 Enable hierarchical type search . . . . . 5-52
Form-based . . . . . . . . . . . . . . . . . . . . 3-6 Escape character . . . . . . . . . . . . . . . 5-52
forms . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Favorites . . . . . . . . . . . . . . . . . 3-46, 5-51
Fuzzy . . . . . . . . . . . . . . . . . . . . . . . 3-29 General . . . . . . . . . . . . . . . . . . . . . . 3-44
General options . . . . . . . . . . . . . . . . 3-44 Latest dataset versions . . . . . . . . . . . 5-52

PLM00191 J Rich Client Interface Guide Index-11

Index

Remote . . . . . . . . . . . . . . . . . . 3-46, 5-53 Secondary applications . . . . . . . . . . . . 2-99

Results . . . . . . . . . . . . . . . . . . . . . . 3-46 Security options . . . . . . . . . . . . . . . . . 5-26
Saved searches . . . . . . . . . . . . . . . . 3-46 Select item type . . . . . . . . . . . . . . . . . 5-40
Search classification hierarchy . . . . . 5-52 Select Property
Search locale . . . . . . . . . . . . . . . . . . 5-52 Simple Search . . . . . . . . . . . . . . . . . 3-10
Set load all limit . . . . . . . . . . . 3-46, 5-53 Send To shortcut menu command . . . . 2-83,
Set loading page size . . . . . . . . 3-46, 5-53 2-88
Set open search result limit . . . 3-46, 5-53 Server
Wildcard option . . . . . . . . . . . . . . . . 5-52 Rich client logon . . . . . . . . . . . . . . . . 1-5
Search pane Server condition symbol . . . . . . . . . . . . . 1-9
Lock . . . . . . . . . . . . . . . . . . . . . . . . 3-36 Service Details view . . . . . . . . . . . . . . 2-38
Search results Service Editor view . . . . . . . . . . . . . . . 2-38
Closing . . . . . . . . . . . . . . . . . . . . . . 3-17 Service Manager . . . . . . . . . . . . . . . . . 2-11
Compare . . . . . . . . . . . . . . . . . . . . . 3-18 Service Plan view . . . . . . . . . . . . . . . . 2-39
Comparing . . . . . . . . . . . . . . . . . . . 3-18 Service Planner . . . . . . . . . . . . . . . . . 2-11
Displaying . . . . . . . . . . . . . . . . 3-15–3-16 Service Request Manager . . . . . . . . . . . 2-11
Displaying related object Service Request Status view . . . . . . . . 2-39
properties . . . . . . . . . . . . . . . . . . 3-17 Service Scheduler . . . . . . . . . . . . . . . . 2-11
Printing results tree . . . . . . . . . . . . . 3-19 Service Scheduler view . . . . . . . . . . . . 2-39
Rename . . . . . . . . . . . . . . . . . . . . . 3-19 Session settings, changing . . . . . . . . . 2-106
Renaming . . . . . . . . . . . . . . . . . . . . 3-19 Set CAEModel Attributes option . . . . . . 5-30
Save to My Saved Searches . . . . . . . . 3-35 Set input to recent selection . . . . . . . . . 2-77
Saving to a folder . . . . . . . . . . . . . . . 3-35 Set load all limit . . . . . . . . . . . . . . . . . 3-46
Saving to a folder from a data pane . . 3-36 Set loading page size . . . . . . . . . . . . . . 3-46
Search results view . . . . . . . . . . . . . . . 3-13 Set open search result limit . . . . . . . . . 3-46
Search Results view . . . . . . . . . . 2-43, 2-49 Set query options . . . . . . . . . . . . . . . . 3-44
Search type Setting
Advanced . . . . . . . . . . . . . . . . . . . . . 3-2 Default role . . . . . . . . . . . . . . . . . . 2-106
Dataset Name . . . . . . . . . . . . . . . . . . 3-2 Options . . . . . . . . . . . . . . . . . . . . . 2-145
Item ID . . . . . . . . . . . . . . . . . . . . . . . 3-2 Setup Wizard . . . . . . . . . . . . . . . . . . . 2-11
Item name . . . . . . . . . . . . . . . . . . . . . 3-2 Setup Wizard view . . . . . . . . . . . . . . . 2-20
Keyword . . . . . . . . . . . . . . . . . . . . . . 3-2 Shortcut commands
Search view . . . . . . . . . . . . . . . . . . . . 2-43 New Change in context . . . . . . . 2-82, 2-86
Lock . . . . . . . . . . . . . . . . . . . . . . . . 3-34 Shortcut menu . . . . . . . . . . . . . . . . . . 2-82
search_automatic_wildcard Access . . . . . . . . . . . . . . . . . . . 2-85, 2-89
preference . . . . . . . . . . . . . . . . . . . . . 3-28 Add Design to Product . . . . . . . 2-85, 2-90
Searches Add Part to Product . . . . . . . . . 2-85, 2-90
Cancel . . . . . . . . . . . . . . . . . . . . . . . 3-6 Add To Favorites . . . . . . . . . . . 2-86, 2-90
Keyword . . . . . . . . . . . . . . . . . . . . . 3-21 Check In/Out . . . . . . . . . . . . . . 2-84, 2-88
Loading results . . . . . . . . . . . . . . . . 3-16 Compare Contents . . . . . . . . . . 2-86, 2-90
Properties and keywords . . . . . . . . . 3-21 Copy . . . . . . . . . . . . . . . . . . . . 2-82, 2-87
Share saved searches . . . . . . . . . . . . 3-27 Copy Reference . . . . . . . . . . . . 2-82, 2-86
Using keywords . . . . . . . . . . . . . . . . 3-20 Cut . . . . . . . . . . . . . . . . . . . . . 2-82, 2-87
Where-referenced . . . . . . . . . . . . . . . 3-50 Edit Properties . . . . . . . . . . . . 2-84, 2-89
Where-used . . . . . . . . . . . . . . . . . . . 3-52 Generate Report . . . . . . . . . . . 2-83, 2-87
Searching Internal Trace Report . . . . . . . . 2-85, 2-89
Criteria License . . . . . . . . . . . . . . . . . . 2-85, 2-89
Date and time . . . . . . . . . . . . . . 3-30 Make Immune . . . . . . . . . . . . . 2-84, 2-88
Table values . . . . . . . . . . . . . . . 3-30 Manage Global Alternates . . . . 2-85, 2-90
Values from lists . . . . . . . . . . . . 3-31 Multisite Synchronization . . . . . 2-86, 2-90
Full-text search . . . . . . . . . . . . . . . . 3-19 New . . . . . . . . . . . . . . . . . . . . 2-82, 2-87
Wildcard support . . . . . . . . . . . . . . . 3-28 Paste . . . . . . . . . . . . . . . . . . . 2-83, 2-87
Searching preferences . . . . . . . . . . . . 2-146 Pin to Launch Pad . . . . . . . . . . 2-83, 2-87
Secondary application buttons . . . . 1-7, 2-92 Project . . . . . . . . . . . . . . . . . . 2-85, 2-89

Index-12 Rich Client Interface Guide PLM00191 J


Properties on Relation . . . . . . . 2-84, 2-89
Purge . . . . . . . . . . . . . . . . . . . 2-84, 2-88
Refresh . . . . . . . . . . . . . . . . . . 2-84, 2-88
Remove Immunity . . . . . . . . . . 2-84, 2-88
Resequence Structure . . . . . . . . 2-83, 2-87
Send To . . . . . . . . . . . . . . . . . . 2-83, 2-88
Subscribe . . . . . . . . . . . . . . . . 2-86, 2-90
Subscription Manager . . . . . . . 2-86, 2-90
Unpin from Launch Pad . . . . . . 2-83, 2-87
View Properties . . . . . . . . . . . . 2-84, 2-89
Shortcut menus
My Teamcenter . . . . . . . . . . . . 2-82, 2-86
Show Advanced Paste in New Process
option . . . . . . . . . . . . . . . . . . . . . . . . 5-56
Show common parts option . . . . . . . . . 5-44
Show View command . . . . . . . . . . . . . . 2-70
Show View menu command . . . . . . . . . 2-80
Showing fewer applications . . . . . . . . 2-100
Showing more applications . . . . . . . . 2-100
Shown relations . . . . . . . . . . . . . . . . 2-119
Pseudo folder . . . . . . . . . . . . . . 5-40, 5-42
Significant Relationship Types for
CAEAnalysis option . . . . . . . . . . . . . . 5-30
Significant Relationship Types for CAEModel
option . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Simple search
View . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Simple Search
Edit clause . . . . . . . . . . . . . . . . . . . 3-10
Overview . . . . . . . . . . . . . . . . . . . . . 3-12
Perform . . . . . . . . . . . . . . . . . . . . . . 3-13
Select Property . . . . . . . . . . . . . . . . 3-10
User interface . . . . . . . . . . . . . . . . . . 3-9
Simple Search view . . . . . . . . . . . . . . . 2-43
Smart Folder Filter Configuration
view . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Smart folders, using . . . . . . . . . . . . . 2-118
Snapshot Gallery view . . . . . . . . . . . . . 2-49
Snapshots view . . . . . . . . . . . . . . . . . . 2-47
Software Parameter Manager . . . . . . . . 2-12
Sort
Search attributes . . . . . . . . . . . . . . . 3-47
Specification Manager . . . . . . . . . . . . . 2-12
Specification Manager view . . . . . . . . . 2-24
Specify relation type
Paste . . . . . . . . . . . . . . . . . . . . . . 2-112
Standard Text Library view . . . . . . . . . 2-34
Standard Text view . . . . . . . . . . . . . . . 2-34
Start of Week . . . . . . . . . . . . . . . . . . . 5-34
Starting rich client sessions . . . . . . . . . . 1-4
Startup Scripts/Server Info option . . . . 5-30
State transitions . . . . . . . . . . . . . . . . . . 4-3
Status indicators . . . . . . . . . . . . . . . . 2-126
STEP Translator options . . . . . . . . . . . 5-23
PLM00191 J
Index
Structure context, definition . . . . . . . . . . 4-2
Structure Manager . . . . . . . . . . . . . . . 2-12
Structure Manager options . . . . . . . . . 5-20
Allow Structure Manager to perform search
using Appearance Search Engine at
remote sites . . . . . . . . . . . . . . . . 5-20
BOM line title format . . . . . . . . . . . . 5-20
BOM precision . . . . . . . . . . . . . . . . . 5-21
Default revision rule . . . . . . . . . . . . 5-20
Default view type . . . . . . . . . . . . . . . 5-20
Display Markups for pending edits . . 5-20
Pack display . . . . . . . . . . . . . . . . . . 5-20
Structure Manager view . . . . . . . . . . . 2-24
Structure Search Results view . . . . . . . 2-34
Structure Search view . . . . . . . . . . . . . 2-34
StructureMap Builder, see CAE Structure
Designer
Study view . . . . . . . . . . . . . . . . . . . . . 2-35
Subscribe shortcut menu command . . . 2-86,
2-90
Subscription Manager shortcut menu
command . . . . . . . . . . . . . . . . . 2-86, 2-90
Subscription Monitor . . . . . . . . . . . . . . 2-12
Subscription Monitor view . . . . . . . . . . 2-20
Substance Compliance Dashboard . . . . 2-39
Summary pane . . . . . . . . . . . . . . . . . 2-126
Summary view . . . . . . . . . . . . . . . . . . 2-17
Suppress Commands view . . . . . . . . . . 2-20
Suspended Tasks option . . . . . . . . . . . . 5-57
Sync request object . . . . . . . . . . . . . . . . 4-2
Synchronization request . . . . . . . . . . . . 4-3
Creating . . . . . . . . . . . . . . . . . . 4-8, 4-11
States . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Synonym search . . . . . . . . . . . . . . . . . 3-29
System options . . . . . . . . . . . . . . . . . . 5-27
System preferences . . . . . . . . . . . . . . 2-143
Systems Engineering . . . . . . . . . 2-13, 2-128
Systems Engineering options . . . . . . . . 5-27
Apply Templates . . . . . . . . . . . . . . . 5-27
Browse Clear Text . . . . . . . . . . . . . . 5-28
Calculate Defining/Complying
Objects . . . . . . . . . . . . . . . . . . . . 5-28
Keywords to Import . . . . . . . . . . . . . 5-28
Left-Right Trace View . . . . . . . . . . . 5-27
Quick Create Panel . . . . . . . . . . . . . 5-28
Trace Link Mode . . . . . . . . . . . . . . . 5-27
T
Table panes
Configuring . . . . . . . . . . . . . . . . . . 2-129
Tables
Configure view tables data display . . . 2-55
Configuring data display . . . . . . . . . 2-129
Rich Client Interface Guide Index-13
Index
Removing columns . . . . . . . . . . . . . 2-127
Repositioning columns . . . . . . . . . . 2-127
Target list
Extended multi-application search . . 3-39
Search . . . . . . . . . . . . . . . . . . . . . . 3-42
Target References view . . . . . . . . . . . . 2-25
TC_fts_indexed_types preference . . . . . 3-20
TC_fts_real_time_indexing
preference . . . . . . . . . . . . . . . . . . . . . 3-20
TC_Graph_Node_Thumbnail_Shown
preference . . . . . . . . . . . . . . . . . . . . . 2-60
TC_QRY_xxx_REVRULE preference . . . 3-39
TC_wc_show_all preference . . . . . . . . 2-107
Teamcenter
Search . . . . . . . . . . . . . . . . . . . . . . . 3-3
Search results . . . . . . . . . . . . . . . . . 3-13
Simple search . . . . . . . . . . . . . . . . . . 3-9
Teamcenter Component view . . . . . . . . 2-49
Teamcenter interfaces
Rich client . . . . . . . . . . . . . . . . . . . . . 1-5
Teamcenter lifecycle visualization
options . . . . . . . . . . . . . . . . . . . . . . . 5-53
Teamcenter perspectives and views . . . . . 1-9
Teamcenter Rapid Start
Printing . . . . . . . . . . . . . . . . . . . . 2-138
Teamcenter sessions
Starting rich client . . . . . . . . . . . . . . . 1-4
Textual Work Instructions view . . . . . . 2-35
TiCon Search view . . . . . . . . . . . . . . . 2-35
Time view . . . . . . . . . . . . . . . . . . . . . 2-35
Tool Information for Output Files
option . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Toolbar . . . . . . . . . . . . . . . . . . . . 1-5, 2-124
Toolbar menu command . . . . . . . . . . . . 2-81
Toolbar, customizing . . . . . . . . . . . . . 2-101
Trace Link Mode option . . . . . . . . . . . . 5-27
Trace links . . . . . . . . . . . . . . . . . . . . 2-129
Traceability Matrix view . . . . . . . . . . . 2-41
Traceability view . . . . . . . . . . . . . . . . 2-40
Transactions . . . . . . . . . . . . . . . . . . . . . 4-7
Transfer directory option . . . . . . . . . . . 5-49
Transfer mode object . . . . . . . . . . . . . . . 4-2
Transfer ownership . . . . . . . . . . . . . . . 5-45
Translation privilege . . . . . . . . . . . . . . 1-12
Tree pane . . . . . . . . . . . . . . . . 2-124–2-125
U <viewer-config-ID>.VIEWERCONFIG
Unpin from Launch Pad shortcut menu
command . . . . . . . . . . . . . . . . . 2-83, 2-87
Updating search indexes . . . . . . . . . . . 3-25
URLs
Paste . . . . . . . . . . . . . . . . . . . . . . 2-113
User ID
Index-14 Rich Client Interface Guide
Rich client logon . . . . . . . . . . . . . . . . 1-5
User interface condition symbol . . . . . . . 1-9
User interface options . . . . . . . . . . . . . 5-42
User profiles, changing . . . . . . . . . . . 2-105
User session settings, changing . . . . . 2-106
User settings, changing . . . . . . . . . . . 2-106
Using the Localization button . . . . . . . 1-11
Utility
build_fts_index . . . . . . . . . . . . . . . . 3-20
Utilization view . . . . . . . . . . . . . . . . . 2-38
V
Validation Agent view . . . . . . . . . . . . . 2-46
Validation Manager . . . . . . . . . . . . . . . 2-13
Validation Results Viewer view . . . . . . 2-46
Variant Configuration view . . . . . . . . . 2-49
Variant options . . . . . . . . . . . . . . . . . . 2-36
Variants view . . . . . . . . . . . . . . . 2-26, 2-36
View
Detached . . . . . . . . . . . . . . . . . . . . . 2-72
Display using Fast View . . . . . . . . . . 2-78
Move . . . . . . . . . . . . . . . . . . . . . . . . 2-71
Search criteria definition . . . . . . . . . 3-37
View Folder
Minimize . . . . . . . . . . . . . . . . . . . . . 2-78
Restore . . . . . . . . . . . . . . . . . . . . . . 2-79
View Properties shortcut menu
command . . . . . . . . . . . . . . . . . 2-84, 2-89
View tables
Applying column configuration . . . . . 2-52
Configuring . . . . . . . . . . 2-51, 2-55, 2-129
Copying selected data . . . . . . . . . . . . 2-53
Exporting to CSV . . . . . . . . . . . . . . . 2-55
Exporting to Excel . . . . . . . . . . . . . . 2-54
Exporting to Word . . . . . . . . . . . . . . 2-53
Filtering . . . . . . . . . . . . . . . . . . . . . 2-52
Finding in display . . . . . . . . . . . . . . 2-53
Managing columns . . . . . . . . . . . . . . 2-52
Printing . . . . . . . . . . . . . . . . . . . . . 2-53
Refresh . . . . . . . . . . . . . . . . . . . . . . 2-52
Saving column configuration . . . . . . . 2-52
Sorting . . . . . . . . . . . . . . . . . . . . . . 2-52
Viewer pane . . . . . . . . . . . . . . . . . . . 2-128
Viewer pane, printing . . . . . . . . . . . . 2-137
Viewer view . . . . . . . . . . . . . . . . 2-49, 2-69
preference . . . . . . . . . . . . . . . . . . . . . 2-69
Viewer.VIEWERCONFIGTOLOAD
preference . . . . . . . . . . . . . . . . . . . . . 2-70
Views
2D Viewer . . . . . . . . . . . . . . . . . . . . 2-28
3D Viewer . . . . . . . . . . . . . . . . . . . . 2-46
Access Manager . . . . . . . . . . . . . . . . 2-18
PLM00191 J
 Index

Accountability Check . . . . . . . . . . . . 2-28 Graph Overview . . . . . . . . . . . . . . . 2-48

Activities . . . . . . . . . . . . . . . . . . . . . 2-28 Graph Thumbnail Preview . . . . . . . . 2-48
Activity Gantt . . . . . . . . . . . . . . . . . 2-29 Graphics . . . . . . . . . . . . . . . . . 2-25, 2-30
ADA License Details . . . . . . . . . . . . 2-47 Groups . . . . . . . . . . . . . . . . . . . . . . 2-47
ADA Licenses . . . . . . . . . . . . . . . . . 2-47 Home . . . . . . . . . . . . . . . . . . . . . . . 2-48
AM Rules . . . . . . . . . . . . . . . . . . . . 2-36 Image Preview . . . . . . . . . . . . . . . . . 2-42
Analysis . . . . . . . . . . . . . . . . . . . . . 2-24 Impact Analysis . . . . . . . . . . . . . . . . 2-42
Appearance Configuration . . . . . . . . 2-18 Incremental Change . . . . . . . . . . . . . 2-30
Applications . . . . . . . . . . . . . . . . . . 2-18 Inspector . . . . . . . . . . . . . . . . . 2-25–2-26
As-Built Manager . . . . . . . . . . . . . . 2-21 Intermediate Data Capture . . . . . . . . 2-30
Assembly . . . . . . . . . . . . . . . . . . . . 2-46 Issue Home . . . . . . . . . . . . . . . . . . . 2-28
Assignments . . . . . . . . . . . . . . . . . . 2-29 Issue List Details . . . . . . . . . . . . . . . 2-28
Associated Signals . . . . . . . . . . . . . . 2-39 Issue Preview . . . . . . . . . . . . . . . . . 2-28
Attachments . . . . . . . . . . . . . . 2-24, 2-29 JT Preview . . . . . . . . . . . . . . . . . . . 2-42
Audit Manager . . . . . . . . . . . . . . . . 2-18 L10N Result View . . . . . . . . . . . . . . 2-42
Authorization . . . . . . . . . . . . . . . . . 2-48 Launch Pad . . . . . . . . . . . . . . . . . . . 2-48
Auxiliary . . . . . . . . . . . . . . . . . . . . . 2-70 Libraries . . . . . . . . . . . . . . . . . . . . . 2-37
BOM Changes . . . . . . . . . . . . . . . . . 2-26 Line Balancing Chart . . . . . . . . . . . . 2-30
BOM Compare Report . . . . . . . . . . . 2-40 Line Balancing Constraints . . . . . . . 2-30
BOM Grading Result . . . . . . . . . . . . 2-45 Linked Occurrence Paths . . . . . . . . . 2-31
BOM Markup View . . . . . . . . . . . . . 2-41 Log Entries . . . . . . . . . . . . . . . . . . . 2-38
Budgets . . . . . . . . . . . . . . . . . . . . . 2-40 Logical Block . . . . . . . . . . . . . . . . . . 2-40
CAE Manager . . . . . . . . . . . . . . . . . 2-21 Manufacturing Features . . . . . . . . . . 2-31
CAE Structure Designer . . . . . . . . . . 2-21 Material and Substance Dashboard . . 2-36
Change Effectivity . . . . . . . . . . . . . . 2-26 Memory Layout . . . . . . . . . . . . . . . . 2-48
Change Home . . . . . . . . . . . . . . . . . 2-26 Model . . . . . . . . . . . . . . . . . . . . . . . 2-25
Classification . . . . . . . . . . . . . . . . . . 2-22 MS Word . . . . . . . . . . . . . . . . . . . . . 2-42
Classification Admin . . . . . . . . . . . . 2-18 Multi-Structure Manager . . . . . . . . . 2-22
Classification Properties . . . . . . . . . . 2-29 My Projects . . . . . . . . . . . . . . . . . . . 2-37
Classification Table . . . . . . . . . . . . . 2-29 Navigator . . . . . . . . . . . . . . . . . . . . 2-47
Collaboration Context Tree . . . . . . . . 2-29 Open Change . . . . . . . . . . . . . . . . . . 2-26
Communication Monitor . . . . . . 2-27, 2-70 Open Service Request . . . . . . . . . . . . 2-48
Compare . . . . . . . . . . . . . . . . . . . . . 2-46 Open Task . . . . . . . . . . . . . . . . . . . . 2-26
Composite . . . . . . . . . . . . . . . . . . . . 2-25 Organization . . . . . . . . . . . . . . . . . . 2-19
Console . . . . . . . . . . . . . . . . . . . . . . 2-16 Organization (Command
Constraints . . . . . . . . . . . . . . . . . . . 2-46 Suppression) . . . . . . . . . . . . . . . . 2-19
Contains . . . . . . . . . . . . . . . . . . . . . 2-38 Outline . . . . . . . . . . . . . . . . . . . . . . 2-17
Cross Sections . . . . . . . . . . . . . . . . . 2-46 PAD . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Custom Notes . . . . . . . . . . . . . . . . . 2-40 PAD Element . . . . . . . . . . . . . . . . . . 2-31
Dashboard . . . . . . . . . . . . . . . . . . . . 2-45 Palette . . . . . . . . . . . . . . . . . . . . . . 2-17
Database Utilities . . . . . . . . . . . . . . 2-45 Part Planner Activities . . . . . . . . . . . 2-31
DB Walker . . . . . . . . . . . . . . . . . . . 2-27 Paths . . . . . . . . . . . . . . . . . . . . . . . 2-47
Definition . . . . . . . . . . . . . . . . . . . . 2-36 PERT . . . . . . . . . . . . . . . . . . . . . . . 2-32
DesignContext . . . . . . . . . . . . . . . . . 2-22 Physical Part Usage History . . . . . . . 2-38
Details . . . . . . . . . . . . . . . . . . . . . . 2-41 Plan Details . . . . . . . . . . . . . . . . . . 2-38
Diagram Explorer . . . . . . . . . . . . . . 2-40 Plant BOP . . . . . . . . . . . . . . . . . . . . 2-32
Disposition History . . . . . . . . . . . . . 2-38 Platform Designer . . . . . . . . . . . . . . 2-23
DPV Measurements . . . . . . . . . . . . . 2-19 PLM XML/TC XML Export Import
ECAD DXF . . . . . . . . . . . . . . . . . . . 2-46 Administration . . . . . . . . . . . . . . 2-19
ECAD Layer . . . . . . . . . . . . . . . . . . 2-46 PMI . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Effectivity . . . . . . . . . . . . . . . . . . . . 2-41 Preview . . . . . . . . . . . . . . . . . . . . . . 2-27
Function . . . . . . . . . . . . . . . . . . . . . 2-40 Print Object . . . . . . . . . . . . . . . . . . . 2-27
Generic BOP . . . . . . . . . . . . . . . . . . 2-30 Process . . . . . . . . . . . . . . . . . . . . . . 2-32
Getting Started . . . . . . . . . . . . . . . . 2-22 Process Gantt . . . . . . . . . . . . . . . . . 2-32

PLM00191 J Rich Client Interface Guide Index-15

Index

Product . . . . . . . . . . . . . . . . . . 2-25, 2-32 Traceability . . . . . . . . . . . . . . . . . . . 2-40

Product BOP . . . . . . . . . . . . . . . . . . 2-32 Traceability Matrix . . . . . . . . . . . . . 2-41
Product Manual . . . . . . . . . . . . . . . . 2-33 Utilization . . . . . . . . . . . . . . . . . . . . 2-38
Product View Search . . . . . . . . . . . . 2-33 Validation Agent . . . . . . . . . . . . . . . 2-46
Progress . . . . . . . . . . . . . . . . . . . . . 2-17 Validation Results Viewer . . . . . . . . . 2-46
Project . . . . . . . . . . . . . . . . . . . . . . 2-37 Variant Configuration . . . . . . . . . . . 2-49
Properties . . . . . . . . . . . . . . . . . . . . 2-17 Variants . . . . . . . . . . . . . . . . . 2-26, 2-36
PSD . . . . . . . . . . . . . . . . . . . . . . . . 2-33 Viewer . . . . . . . . . . . . . . . . . . . . . . 2-49
Publication Structure . . . . . . . . . . . . 2-27 Visio Diagram . . . . . . . . . . . . . . . . . 2-44
Query Builder . . . . . . . . . . . . . . . . . 2-19 Volume Management . . . . . . . . . . . . 2-20
Registry Editor . . . . . . . . . . . . . . . . 2-45 Volume Monitor . . . . . . . . . . . . . . . . 2-21
Relation Browser . . . . . . . . . . . . . . . 2-43 Web Browser . . . . . . . . . . . . . . . . . . 2-45
Report . . . . . . . . . . . . . . . . . . . . . . 2-33 Where Allocated . . . . . . . . . . . . . . . 2-44
Report Builder . . . . . . . . . . . . . . . . . 2-20 Work Instruction . . . . . . . . . . . . . . . 2-36
Report Generator . . . . . . . . . . . . . . . 2-49 Work Order Home . . . . . . . . . . . . . . 2-39
Request Home . . . . . . . . . . . . . . . . . 2-39 Workarea . . . . . . . . . . . . . . . . . . . . 2-36
Required Items . . . . . . . . . . . . . . . . 2-33 Workflow Designer . . . . . . . . . . . . . . 2-21
Requirement . . . . . . . . . . . . . . . . . . 2-40 Workflow Viewer . . . . . . . . . . . . . . . 2-24
Requirement Expression . . . . . . . . . . 2-40 Visio Diagram view . . . . . . . . . . . . . . . 2-44
Resource . . . . . . . . . . . . . . . . . . . . . 2-33 Volume Management . . . . . . . . . . . . . . 2-13
Rich client . . . . . . . . . . . . . . . . . . . . . 1-9 Volume Management view . . . . . . . . . . 2-20
Roll Up . . . . . . . . . . . . . . . . . . . . . . 2-27 Volume Monitor view . . . . . . . . . . . . . . 2-21
Schedule Manager . . . . . . . . . . . . . . 2-23
Schedule Task Execution . . . . . . . . . 2-37 W
Search . . . . . . . . . . . . . . . . . . . 2-43, 3-3
Search results . . . . . . . . . . . . . . . . . 3-13 Watermarks
Search Results . . . . . . . . . . . . . 2-43, 2-49 Printing in Teamcenter Rapid
Service Details . . . . . . . . . . . . . . . . . 2-38 Start . . . . . . . . . . . . . . . . . . . . 2-139
Service Editor . . . . . . . . . . . . . . . . . 2-38 Web Browser . . . . . . . . . . . . . . . . . . . 2-13
Service Plan . . . . . . . . . . . . . . . . . . 2-39 Web Browser view . . . . . . . . . . . . . . . . 2-45
Service Request Status . . . . . . . . . . . 2-39 Where Allocated view . . . . . . . . . . . . . 2-44
Service Scheduler . . . . . . . . . . . . . . 2-39 Where-referenced reports, printing . . . 2-136
Setup Wizard . . . . . . . . . . . . . . . . . . 2-20 Where-referenced searches . . . . . . . . . 3-50
Simple search . . . . . . . . . . . . . . . . . . 3-9 Where-used searches . . . . . . . . . . . . . . 3-52
Simple Search . . . . . . . . . . . . . . . . . 2-43 Wildcard
Smart Folder Filter Configuration . . . 2-37 Search . . . . . . . . . . . . . . . . . . . . . . 3-28
Snapshot Gallery . . . . . . . . . . . . . . . 2-49 Wildcard characters . . . . . . . . . . . . . . 3-28
Snapshots . . . . . . . . . . . . . . . . . . . . 2-47 Classification search . . . . . . . . . . . . 3-28
Specification Manager . . . . . . . . . . . 2-24 Wildcard search option . . . . . . . . . . . . 3-45
Standard Text . . . . . . . . . . . . . . . . . 2-34 Window menu . . . . . . . . . . 2-79, 2-81, 2-156
Standard Text Library . . . . . . . . . . . 2-34 Work Breakdown Structure (WBS)
Structure Manager . . . . . . . . . . . . . . 2-24 options . . . . . . . . . . . . . . . . . . . . . . . 5-28
Structure Search . . . . . . . . . . . . . . . 2-34 Work contexts, setting current . . . . . . 2-107
Structure Search Results . . . . . . . . . 2-34 Work Instruction view . . . . . . . . . . . . . 2-36
Study . . . . . . . . . . . . . . . . . . . . . . . 2-35 Work Order Home view . . . . . . . . . . . . 2-39
Subscription Monitor . . . . . . . . . . . . 2-20 Workarea view . . . . . . . . . . . . . . . . . . 2-36
Substance Compliance Dashboard . . . 2-39 Workflow Designer . . . . . . . . . . . . . . . 2-13
Summary . . . . . . . . . . . . . . . . . . . . 2-17 Workflow Designer view . . . . . . . . . . . . 2-21
Suppress Commands . . . . . . . . . . . . 2-20 Workflow options . . . . . . . . . . . . . . . . 5-56
Target References . . . . . . . . . . . . . . 2-25 Default View . . . . . . . . . . . . . . . . . . 5-56
Teamcenter Component . . . . . . . . . . 2-49 Inbox interval checking for new
Textual Work Instructions . . . . . . . . 2-35 tasks . . . . . . . . . . . . . . . . . . . . . 5-57
TiCon Search . . . . . . . . . . . . . . . . . . 2-35 Show Advanced Paste in New
Time . . . . . . . . . . . . . . . . . . . . . . . . 2-35 Process . . . . . . . . . . . . . . . . . . . . 5-56

Index-16 Rich Client Interface Guide PLM00191 J

 Index

Suspended Tasks . . . . . . . . . . . . . . . 5-57 Workflow Viewer view . . . . . . . . . . . . . 2-24

Workflow Viewer . . . . . . . . . . . . . . . . . 2-13

PLM00191 J Rich Client Interface Guide Index-17