Preferences Environment Variables Reference PLM Teamcenter

Teamcenter 8.
Preferences and Environment

Variables Reference
Publication Number
PLM00026 F
Proprietary and restricted rights notice
This software and related documentation are proprietary to Siemens Product

Lifecycle Management Software Inc.
© 2010 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
All trademarks belong to their respective holders.
2 Preferences and Environment Variables Reference PLM00026 F

Contents
Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Syntax definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Basic configuration concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Basic configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Introduction to environment variables . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Environment variable script files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Setting environment variables for logging . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Environment variables listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Introduction to preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Preference interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Managing preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Teamcenter Integration for NX preferences . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Configuration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Business Modeler IDE preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Client interface preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Data management preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Dispatcher preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Full-text search preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Localization preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
Mail gateway preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
NX Integration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
Password preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-89
Teamcenter services preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-91
Remote workflow preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-92
Teamcenter LDAP synchronization preferences . . . . . . . . . . . . . . . . . . . . . . . 5-95
Validation Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-109
Access Manager and Portfolio, Program and Project Management

preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
eIntegrator Admin preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Authorization preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
File management and maintenance preferences . . . . . . . . . . . . . . . . . . 9-1
PLM00026 F Preferences and Environment Variables Reference 3

Contents
Audit Manager preferences . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Archive, restore, and migration preferences . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Action manager daemon preferences . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Subscription Manager preferences . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Subscription Monitor preferences . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . 9-13
File caching preferences . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Log file preferences . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . 9-37
Client preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Rich client preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Thin client preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-98
Workflow preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Change Viewer preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Change Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Issue Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Reports, requirements, and scheduling preferences . . . . . . . . . . . . . . 15-1

Requirements Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Schedule Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Report Designer preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-13
Classification Administration preferences . . . . . . . . . . . . . . . . . . . . . . 16-1
Classification preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
Data sharing preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Multi-Site Collaboration preferences ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Data Exchange preferences . . . . . . .... . . . . . . . . . . . . . . . . . . . . . . . . . . 18-57
PLM XML preferences . . . . . . . . . .... . . . . . . . . . . . . . . . . . . . . . . . . . . 18-66
STEP Translator preferences . . . . . .... . . . . . . . . . . . . . . . . . . . . . . . . . . 18-75
Product structure and Repeatable Digital Validation preferences . . . 19-1

Appearance Configuration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
DesignContext preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10
Multi-Structure Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-40
Structure Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-44
Platform Designer preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-106
RDV preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-113
Quick spatial search preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-131
Teamcenter’s manufacturing process management preferences . . . . . 20-1

General manufacturing preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Cloning preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-23
PERT chart preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-29
Accountability check preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-32
Time management preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-38
Publishing preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-47
4 Preferences and Environment Variables Reference PLM00026 F

Contents
PAD preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-56

Manufacturing search preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-58
Enterprise BOP preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-62
GANTT chart viewer preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-72
Manufacturing features preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-76
Standard text preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-81
Process Simulate preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-83
Visualization preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Solution-specific preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Aerospace and Defense preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1
Consumer Packaged Goods preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Teamcenter Automotive Edition preferences . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Teamcenter’s mechatronics process management preferences . . . . . . . . . . . . 22-22
Vendor management preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-51
MRO core preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-68
As-Built Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-79
Service Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-81
Service Request Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-100
Integration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1

Application Integration Environment (AIE) preferences . . . . . . . . .. . . . . . . . 23-1
Application Response Measurement (ARM) integration preferences . . . . . . . . 23-4
Teamcenter Integration for AutoCAD preferences . . . . . . . . . . . . .. . . . . . . 23-32
Configuring computer aided engineering preferences . . . . . . . . . . .. . . . . . . 23-32
Teamcenter Integration for NX I-deas preferences . . . . . . . . . . . . .. . . . . . . 23-46
Mentor Graphics Integration preferences . . . . . . . . . . . . . . . . . . .. . . . . . . 23-47
ERP Connect to SAP preferences . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 23-49
ODBC Driver preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 23-52
ClearCase Integration preferences . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 23-53
EDA preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1
Quality data preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1
ADA License preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
PLM00026 F Preferences and Environment Variables Reference 5

Chapter
1 Getting started
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Syntax definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Basic configuration concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Configure Teamcenter before deploying to other sites . . . . . . . . . . . . . . . . 1-3
Important configuration variables for your initial Teamcenter
implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
What are environment variables? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
What are preferences? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Basic configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Manually configuring the Teamcenter environment . . . . . . . . . . . . . . . . . 1-4
Running environment variable script files . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Creating and editing preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Determining required preference values . . . . . . . . . . . . . . . . . . . . . . 1-5
Creating and editing preferences from the Options dialog box . . . . . . . 1-6
Creating and editing preferences from preference .XML files . . . . . . . . 1-7
Edit a preference XML file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Specify dual OS values for a single preference . . . . . . . . . . . . . . . . . . 1-8
PLM00026 F Preferences and Environment Variables Reference

Chapter
1 Getting started
Teamcenter installation and basic configuration is performed with the Teamcenter

Environment Manager program. After Teamcenter is installed, additional
configuration is required.
Completing a Teamcenter Environment Manager installation automatically enables
the Teamcenter environment.
For more information about installation considerations and installation procedures,
see the installation guides for the operating system on which you are running
Teamcenter ( Installation on UNIX and Linux Servers Guide, Installation on UNIX
and Linux Clients Guide, Installation on Windows Servers Guide, or Installation on
Windows Clients Guide).
It is also possible to manually configure the Teamcenter environment.
For more information, see Manually configuring the Teamcenter environment.
Prerequisites
This manual is intended for system administrators, data administrators, and Java
developers who configure the Teamcenter functionality using environment settings.
A basic understanding of object-oriented programming (OOP) and Teamcenter
concepts is required.
Syntax definitions
This manual uses a set of conventions to define the syntax of Teamcenter preferences
and environment variables. Following is a sample syntax format:
PUBLISH_PDF_ This environment variable is used with Visualization
ERROR_LOG_LOC Illustration. Defines a location for the Convert/Print
error log file different from the default location
(c:\Documents and Setting\user name\Local
Settings\Temp\VisProdlocation\VVCP_error.log).
This log file records all errors occurring during the PDF
conversion process. Set this environment variable with the full
path name and file name. For example:
c:\MyFiles\Error.log
The conventions are:
PLM00026 F Preferences and Environment Variables Reference 1-1

Chapter 1 Getting started
Bold Bold text represents words and symbols you must enter exactly
as shown.
In the preceding example, you enter c:\Documents and Setting\,
\Local Settings\Temp\VisProd and \VVCP_error.log exactly
as shown.
Italic Italic text represents values that you supply.
In the preceding example, you supply values for user name and
log location.
Courier font This font, indented, indicates an example of a setting or command
you can input.
In the preceding example, you could enter
Basic configuration concepts

Much of Teamcenter behavior and display can be configured with environment
variables and preferences.
• Environment variables are run in script files to configure and control many
aspects of Teamcenter. By setting these variables for each site, Teamcenter
can be quickly adapted and configured to meet any site’s needs. Many of these
variables point to specific network nodes and/or directories so that Teamcenter
can be used in large and small homogeneous and heterogeneous environments.
Note
Two environment variables must be set before running Teamcenter:
TC_ROOT and TC_DATA. Teamcenter does not run unless these
environment variables are set. These environment variables must be set
through shell commands or a script.
For more information, see Introduction to environment variables.
• Preferences are special environment variables stored in the Teamcenter

database. They are read during Teamcenter application usage. Each application
may have associated preferences. Preferences allow you to configure many
aspects of a session of application behavior, such as how assemblies are revised,
whether extension rules are bypassed for specified operations, and which
Teamcenter objects display in integrations.
You can set preferences in the Teamcenter interface by choosing Edit→Options
to open the Options dialog box. Use the dialog box to search for preferences, set
preference values, create new preferences, and remove existing preferences.
For information about this dialog box, see Getting Started with Teamcenter.
Preferences can also be manually modified in a copy of the tc_preferences.xml
file. After modifying, use the preferences_manager utility to import the file.
1-2 Preferences and Environment Variables Reference PLM00026 F

Getting started
Configure Teamcenter before deploying to other sites

Before you deploy Teamcenter, you should fully complete the configuration process.
Some configuration tasks, such as defining log files, are difficult to redefine once
Teamcenter is deployed.
Important configuration variables for your initial Teamcenter

implementation
Teamcenter offers a wide array of environment variables and preferences which you
can use to modify all aspects of the product. The scope of a preference determines
the range of its effect across the system (site preferences affect the entire site, user
preferences affect only a particular user’s settings).
To review preferences which should be considered and set before deploying
Teamcenter, see Configuration preferences.
To review preferences which affect the fundamental behavior of the rich client, see
Rich client preferences.
What are environment variables?

Environment settings stored in the tc_profilevars properties file that allow you to
control many aspects of Teamcenter behavior. This script is run directly by Bourne
and Korn shells. C shells must use the tc_cshvars script. Some examples are:
TC_ROOT indicates the top (root) directory of the Teamcenter directory structure.
TC_LIBRARY sets the platform-specific shared display library path.
For more information, see Introduction to environment variables.
What are preferences?

Special environment variables stored in the Teamcenter database and read whenever
a preference value is set or modified in the interface or in the tc_preferences.xml
preference file.
Teamcenter offers thousands of preferences designed to configure the product to
your specific needs.
Set preferences individually in the Options dialog box accessed from the Edit
menu. Update preferences using scripts, or input batches of preferences in the
tc_preferences.xml preference file.
Use preferences to determine user-specific behavior such as user logon names and
the columns displayed by default in a properties table. You can also set preferences
for basic system behavior such as business rules, workflow, application behavior,
and security access.
For more information, see Introduction to preferences.
Basic configuration tasks

Teamcenter installation and basic configuration is performed with Teamcenter
Environment Manager. After Teamcenter is installed, additional configuration

is required. Configuration tasks include systems-based tasks, such as user

organization, file management, and data security. Additionally, most Teamcenter
applications can be configured to meet your site’s needs. Complete the following
basic configuration tasks before deploying Teamcenter at your site.
Manually configuring the Teamcenter environment

Teamcenter administrators typically configure site workstations and computers so
that users can log on without manually setting the environment. If this has not been
done by your administrator, you must manually set the Teamcenter environment
before you can run a session.
TC_ROOT and TC_DATA are the only environment variable settings required
to run the core Teamcenter application. These variables can be set automatically
at login. However, there are several stand-alone utilities such as install and
clearlocks that also require that the entire Teamcenter environment be set.
If you are unsure whether to perform this procedure, consult your administrator for
additional information.
Note
The following procedures use default path names. If other path names were
specified during Teamcenter installation, use those path names instead.
Consult your administrator for additional information.
UNIX systems
Manually configuring the Teamcenter environment on UNIX systems requires
sourcing the tc_profilevars and tc_cshvars scripts. To manually set the
Teamcenter environment, enter one of the following sets of commands:
Bourne/Korn shell:
TC_ROOT=/usr/tc2007; export TC_ROOT
TC_DATA=/usr/tc2007/tcdata; export TC_DATA
. $TC_DATA/tc_profilevars
C shell:
setenv TC_ROOT /usr/tc2007
setenv TC_DATA /usr/tc2007/tcdata
source $TC_DATA/tc_cshvars
Sourcing the $TC_DATA/tc_cshvars file creates a csh subshell in which

Teamcenter environment variables are set.
Windows systems
Manually configuring the Teamcenter environment on Windows systems requires
running the tc_profilevars.bat script. This script is called automatically when
exiting to an MS-DOS shell from the Teamcenter menu, but the environment can
also be set manually. To manually set the Teamcenter environment, enter the
following commands:
set TC_ROOT=c:\tc2007
set TC_DATA=c:\tc2007\tcdata
call %TC_DATA%\tc_profilevars

Getting started
Note
This documentation consistently uses UNIX syntax, when referring to
environment variable names, providing command line examples, and so on).
Windows users must make the following modifications:
Variable UNIX environment variable names are often prefixed with
names the dollar sign ($); Windows environment variable names
must be enclosed within two percent signs (%) in similar
circumstances. For example:
UNIX: $My_Environment_Variable
Windows: %My_Environment_Variable%
Path names UNIX path names use forward slashes (/) for subdirectories;
Windows path names use backslashes (\) for subdirectories.
For example:
UNIX: My_Dir/My_Subdir/my_file
Windows: My_Dir\My_Subdir\my_file
Running environment variable script files

Teamcenter stores environment variable settings in the tc_profilevars script file,
stored in the TC_DATA directory. You can run these scripts directly in Bourne and
Korn shells. C shells must use the tc_cshvars script. When the tc_cshvars script
is sourced from a C shell, environment variables are read from the tc_profilevars
script file. This is done so that a single file (tc_profilevars) can be used to store
environment variable settings for an entire site.
Creating and editing preferences

The behavior and display of Teamcenter applications can be controlled using
preferences and options. Preferences are configuration variables stored in a
Teamcenter database that are read when a Teamcenter session is initiated.
Preferences allow administrators and users to configure many aspects of a session,
such as user logon names and the columns displayed by default in a properties table.
You can manage preferences either through the rich client interface, or by manually
editing the preference XML file.
Determining required preference values
In this guide, the required settings for each preference is listed in the Valid Values
section of each preference description.
In the Teamcenter interface, the Options dialog box displays descriptions of many
available preferences. Most descriptions include an explanation of valid settings.

Note
Logical preferences accept a single value from any logical pair (on or off, true
or false, 0 or 1). Values for logical preferences are not case sensitive.
For example, you can require each dataset type to have its own ID counter
by setting the AE_dataset_id_gen_by_type preference with any of the
following values:
ON
on
true
True
Creating and editing preferences from the Options dialog box

In the interface, the Options dialog box enables you to work with a limited set of
preferences in the form of options, which are presented by category. These are
available from the Options tab of the dialog box.
For more information about specific options, see the Rich Client Interface Guide.
You can also work directly with the entire preference set, available from the Index
tab of the dialog box. From this view, you can search for preferences in the database,
modify preference values, delete preferences, and add preferences to the database.
Many basic preferences are shipped with Teamcenter and set with default
settings. These preferences display in the Index tab of the Options dialog box
after installation. Preferences that do not automatically display in this tab after
installation must first be created. Create desired preferences either through this
dialog box, or by editing the preference XML file.
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 Teamcenter administrator can create new categories or subcategories that are
appropriate for your business practices, and assign new or existing preferences to
them. Searches for preferences can be limited to certain categories to obtain results
more quickly.

Getting started
Note
Preferences which define columns and column widths cannot be modified
from the Options dialog box. These are interdependent preferences. When a
column preference is modified, the corresponding column width preference
should also be modified to ensure the table displays properly in the interface.
These preferences are most easily modified by right-clicking the Properties
table in the interface and selecting the Insert columns or Remove this
column command. Alternatively, you can modify these preferences using
the preferences_manager utility.
Creating and editing preferences from preference .XML files

You can manually edit preference XML files with an XML editor. Editing a
preference XML file provides greater control over preference definitions, allowing
you to set the type, array and disabled settings, as well as the preference values.
The type setting 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 paired sets of positive 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.
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.
The array setting determines whether multiple values can be set. Setting array
to true allows multiple values to be set for the preference. Setting array to false
allows only a single value to be set for the preference. The array setting can be
set to true for string, integer and double preferences. For logical preferences, the
array must always be false.
The disabled setting determines whether the preference is enabled or disabled.
This can be set to either true or false.
Alternatively, you can manually edit the preference XML files with an XML editor.
Make a copy of the tc_preferences.xml file, apply your changes, then run the
preferences_manager utility to import the file containing your changes.

Edit a preference XML file
1. Make a copy of the preference XML file, for example, the tc_preferences.xml
file.
2. Apply your changes using an XML editor.
3. Run the preferences_manager utility to import the file containing your

changes.
For more information about this utility, see the Utilities Reference.
Specify dual OS values for a single preference
You can define both UNIX and Windows values for the same preference. To do so,
you must set array to false, directing the system to return a single value for the
preference query, even when multiple values are defined.
1. Create an XML file containing the relevant preference definitions.
2. Set array to false.
3. Define platform values for both UNIX and Windows. For example:
<preference name="TC_audit_log_dir" type="String" array="false" disabled="false">
<preference_description>Specifies the audit log directory.</preference_description>
<context name="Teamcenter">
<value platform="UNX">$TC_LOG/audit</value>
<value platform="WNT">%TC_LOG%\audit</value>
</context>
</preference>
4. Import the XML file to the database with the preferences_manager utility
using the OVERRIDE option.

Chapter
2 Introduction to environment
variables
Environment variable script files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Setting environment variables for logging . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Chapter
2 Introduction to environment
variables
Use environment variables and script files to configure Teamcenter. Environment

settings allow you to configure and control many aspects of the Teamcenter software.
By setting these variables for each site, Teamcenter can be quickly adapted and
configured to meet any site’s needs. Many of these variables point to specific
network nodes and/or directories so that Teamcenter can be used in large and small
homogeneous and heterogeneous environments.
Two environment variables must be set before running Teamcenter: TC_ROOT and
TC_DATA. Teamcenter does not run unless these environment variables are set.
These environment variables must be set through shell commands or a script.
Basic environment variables are set during the installation of Teamcenter through
the tc_profilevars script.
Environment variable script files

Teamcenter environment variables are stored in the tc_profilevars script file,
stored in the TC_DATA directory. This script can be run directly by Bourne and
Korn shells. C shells must use the tc_cshvars script. When the tc_cshvars script
is sourced from a C shell, environment variables are read from the tc_profilevars
script file. This is done so that a single file (tc_profilevars) can be used to store
environment variable settings for an entire site.
System environment variables are stored as defined by your operating system.
Setting environment variables for logging

Teamcenter saves information in various log files. View log files to identify problems
by showing the state of an application at any given point.
For more information about log files, see the System Administration Guide.
You can modify Teamcenter logging behavior by setting environment variables and
preferences. Set the following environment variables to optimize logging information
sent to system log and journal files.
For more information about working with log files, see Log file preferences.

Chapter 2 Introduction to environment variables
Environment variable name Use

TC_SQL_DEBUG Accepts the following values:
J Copies all SQL statements to the
journal file as well as the system log file.
P Includes profiling data; reports the
frequency of use of each distinct
statement in a summary at the end of
log file.
T Includes timing data; reports the time
of each SQL statement.
B Binds variables; expands SQL bind
variables (this is the default setting)
b Reports bind variables in :1 format,
rather than expanding them.
Note
Set to JPT to optimize logging
information.
TC_JOURNAL Accepts the following values:
OFF Creates an empty journal file.
SUMMARY Creates a summary report listing
the total time spent on each
journal routine.
FULL Creates a full report listing each
call.
MODULE Uses the TC_Journal_Modules
preference to select which
modules should be journalled.
Note
Set to FULL to optimize logging
information.
Set to MODULE to fine tune logging
information.
API_JOURNAL Set to FULL to enable Teamcenter Integration
for NX journalling.
TC_POM_JOURNALLING Determines whether the POM module journals
nested calls.
Set to N for full journalling.

Introduction to environment variables
Environment variable name Use

TC_KEEP_SYSTEM_LOG Accepts the following values:
Y The system log is not deleted, even if
there are no errors.
N The system log is deleted if there are no
errors.
Note
Set to Y to retain the system log.
TC_TRACEBACK Accepts the following values:
ON Writes tracebacks to the system log
file.
OFF Does not write tracebacks to the system
log file.
Note
When errors occur, the system writes
tracebacks to the system log file by
default. Use this environment variable
to override the default behavior.
TC_SLOW_SQL Set to a number of seconds. Defaults to 10
seconds.
Note
SQL statements that run longer than
the specified time write explain plans to
the system log file.

Chapter
3 Environment variables
Environment variables listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Chapter
3 Environment variables
The following list of Teamcenter environment variables includes a brief description

of each variable and how the variable is set (for example, through the tc_profilevars
property file).
Environment variables listing

AdaptiveApplicationDisplay
Determines whether the adaptive application display functionality is enabled.
When enabled, icons of applications that have not been used in a certain period
of time do not display in the navigation pane, thus rarely used applications are
hidden. Users can click the More... button at the bottom of the navigation pane
allows to display the rest of the application icons. The period of disuse required to
trigger this functionality is set in the AdaptiveApplicationDisplayDuration
variable. This variable is set in the client_specific.properties file.
AdaptiveApplicationDisplayDuration
Determines the period of time, in days, an application must not
be used to trigger the adaptive application display functionality.
The AdaptiveApplicationDisplay variable must be set for this
environment variable to be implemented. This variable is set in the
client_specific.properties file.
AM_BYPASS
Bypasses Access Manager when logging on to Teamcenter to enable a system
administrator to reload the rule tree. Use this environment variable if the
rule tree needs repair. For example, perhaps an unintended consequence
of modifying a rule results in no longer being able to see your home folder,
effectively preventing you from logging in effectively. In this case, setting this
environment variable to any value prompts the system to bypass the AM rule
tree when logging in.
AM_MODE
Evaluates the user’s group value based on a union of all groups the user belongs
to. This includes groups defined by predefined conditions and by ACLs. When
this environment variable is not set, a user’s group is determined by the group
value with which the user logged in. Enable this functionality by setting this
variable with any value.
AM_PERFORMANCE_STATISTICS
Collects and displays Access Manager performance statistics for each call to a
rule or accessor function, which are useful for debugging performance issues

Chapter 3 Environment variables
with rule and accessor implementations or the rule tree. The statistics are
logged to the syslog file at server shutdown.
Enable this functionality by setting this variable with any value.
Note
Because there is a significant performance impact to collect the statistics,
the feature is disabled by default.
For more information about the statistics collected, see the Access Manager guide.
API_ALWAYS_REFRESH
Determines whether the Refresh Object caching method is enabled. This
method caches an array of refreshed objects during each system operation, such
as loading an assembly. Setting this environment variable to any value disables
this caching method.
API_FILE_CACHE
Determines whether file caching is performed during dataset-to-filename
translations. This caching method requires security levels be set to mode-0 and
all other caching methods disabled, such as IMF performance caching. Setting
this environment variable to No disables file caching. This method creates
a session-living cache.
API_JOURNAL
Enables journalling of API files. Set to FULL to log all API modules.
API_NO_CACHING
Determines whether any of the following caching methods are performed during
a system operation, such as loading an assembly. Setting this environment
variable to any value prevents all caching methods.
• Item cache contains an array of items found. Each entry is structured to
provide mapping from the Itemid to the tag.
• Item revision cache contains an array of item revisions found. Each entry
is structured to provide mapping from the Itemid/ItemRevid to the tag.
• Refreshed object cached contains an array of refreshed objects found.
API_SET_BYPASS
Set to true to enable DBA bypass of the ACL tree when using import utilities
such as import_file.
AUTHORIZATION_MODE
Evaluates all of a user’s group and role-in-group settings to determine the
effective authorization rules for the user. If left unset, the system evaluates
only the current logon settings.
BMIDE_SCRIPT_ARGS
Sets the memory allocated to the Java heap sizing. For example, set its
value to -Xmx1024M to allocate 1 GB of RAM to the Java heap space on
the server (assuming you have that much memory space available). Create
this environment on a corporate server to ensure there is enough memory to
install large templates. You can also set this value on a machine running a

Environment variables
Business Modeler IDE client to ensure there is enough memory to load templates
containing a large amount of data model.
FMS_HOME
Specifies the FMS home directory. For server side, FMS_HOME specifies the
home directory for FSC files, and on the client machine, FMS_HOME specifies
the home directory for FCC files
FSC_HOME
Specifies the path where an FMS server cache (FSC) service can find the
configuration files. Typically, this is set to TC_ROOTfsc. This environment
variable is set through the tc_profilevars property file.
FMS_FCCSTARTUPLOG
Enables logging of FCC data. Set to the location (full path and file name) in
which you want the data stored.
HSM_TAKE_BACKUP
Used by the move_tc_files utility, which relocates infrequently accessed
Teamcenter files from high-speed/low-density volumes to low-speed/high-density
volumes. This environment variable specifies whether to store a copy of the
original file in the TC_LOG directory before attempting to move the file to the
destination volume.
IMAN_SDL_MAGIC
Dumps a property table into the output page with any error generated while
accessing an object property. This table shows the name type and value of each
valid property of the relevant object. Do not use this facility in production.
IMAN_SYS_UID_DIR
Defines the directory containing the default Teamcenter display libraries. The
default Teamcenter directory structure contains separate subdirectories for
character mode (VT100) and graphical (Motif) interfaces. The tc_profilevars
script uses LIBMODE to set this environment variable to the proper
subdirectory.
IMAN_SYS2_UID_DIR
Defines the directory containing the default uncustomized Teamcenter
Integration for NX display libraries.
JRE_HOME
Specifies the path to the Java Runtime Environment (JRE) location. Typically,
this is set to TC_ROOT/install/install/jre. This environment variable is set
through the tc_profilevars property file.
KNOWLEDGEBASE_EVALUATE
Used for conditions. Determines whether the system checks the settings of
conditions. This environment variable is automatically turned off during
installation and upgrades to ensure no conditions are evaluated during the
process. This environment variable is set to ON when the installation or upgrade
completes. You can manually set this environment variable to OFF to prevent
conditions from being evaluated.
Conditions consist of one or more conditional statements evaluated at run time
to determine condition results, which are always TRUE or FALSE.

For more information about managing conditions, see the Business Modeler
IDE Guide.
LANG
Defines non-English locales on UNIX systems. Specify the system locale by
setting this environment variable and the LC_ALL environment variable
using the Common Desktop Environment (CDE). These two variables must be
identical to function properly.
For more information about country code values, see the Installation on UNIX
and Linux Servers Guide.
Use with the MB_CHARS environment variable to support localizing
Teamcenter by modifying string and date processing behavior to better conform
to local usage. Set this environment variable to a valid locale. Display the list of
locales by typing locale -a in a shell.
LC_ALL
Defines non-English locales on UNIX systems. Specify the system locale by
setting this environment variable and the LANG environment variable using the
Common Desktop Environment (CDE). These two variables must be identical to
function properly.
For more information about country code values, see the Installation on UNIX
and Linux Servers Guide.
LD_LIBRARY_PATH
Defines the shared display library path for Sun, SGI, and HP platforms. The
tc_profilevars script searches for shared display libraries using LIBMODE,
constructs a path statement, and exports LD_LIBRARY_PATH.
LDR_CNTRL
Creates a named shared library. Valid only when running on an AIX platform.
By default, AIX does not support a shared library greater than 256 MB. This
limitation affects sites running on an AIX platform and requiring significant
processing, for example, if users at your site expand very large structures in
Structure Manager.
You can overcome this limitation of the AIX platform by creating a named
shared library. Named shared library areas work similar to global library areas,
designating one segment for shared library data and one for text data. To use
a named shared library in Teamcenter, you must create an alternate memory
model that dedicates both segments to shared library text. Do this by setting this
environment variable to NAMEDSHLIB (named shared library) and specifying
the doubletext32 option for the named shared library area. For example:
LDR_CNTRL=NAMEDSHLIB=tcsp3,doubletext32
On AIX platforms, the number of data segments a process is allowed to use

limits the process memory size. The default number of data segments is one.
The size of a data segment is 256 MB. Data segments are shared for both data
and stack. The maximum number of additional data segments a process can use
is eight. The memory size can be increased by specifying a maximum address
space, as specified in the following table:

Number of Process
additional memory limit
LDR_CNTRL setting
segments increase
Unset 0 (default) 256 MB
LDR_CNTRL=MAXDATA=0x1000000 1 512 MB
LDR_CNTRL=MAXDATA=0x2000000 2 768 MB
LDR_CNTRL=MAXDATA=0x3000000 3 1 GB
LDR_CNTRL=MAXDATA=0x4000000 4 1.25 GB
LDR_CNTRL=MAXDATA=0x7000000 7 2 GB
Force AIX to use the additional memory by enabling dynamic segment allocation
(DSA) by annotating the address with @DSA. For example:
LDR_CNTRL=MAXDATA=0x8000000@DSA
Siemens PLM Software recommends using the maximum data size and memory.
For example:
LDR_CNTRL=NAMEDSHLIB=tcsp3,doubletext32@MAXDATA=0x80000000@DSA
If an invalid setting is used for this environment variable it is ignored and the
default usage (one segment) is defined.
LIB_PATH
Defines the shared display library path for the IBM platform only. The
tc_profilevars script searches for shared display libraries using LIBMODE,
constructs a path statement, and exports LIB_PATH.
LOG_VOLUME_DIR
Specifies the location of the log volume, where the Log Manager transfers logs.
This environment variable is set through the tc_profilevars property file.
LOG_VOLUME_NAME
Specifies the name of the log volume, where the Log Manager transfers logs.
MB_CHARS
Sets localized dataset naming for languages using character sets other than US
ASCII. This environment variable is normally not set (enabling a single-byte
environment); if set to 1 a multibyte environment is enabled. When a multibyte
environment is enabled, Teamcenter supports dataset names containing
Katakana, Kanji, Hiragana, and extended ASCII characters. This is used for
internationalizing Teamcenter.
MGC_HOME
Defines the directory where Mentor Graphics is installed. Used with the Mentor
Graphics Integration only.
MGC_LOCATION_MAP
Defines the full path (directory and file name) of the Mentor Graphics location
map file. Used with the Mentor Graphics Integration only.

MGC_TC_CONFIG_FILE
Defines the full path (directory and file name) of the Mentor Graphics Integration
configuration file. Used with the Mentor Graphics Integration only.
MGLS_LICENSE_FILE
Defines the full path (directory and file name) of the Mentor Graphics license
file. Used with the Mentor Graphics Integration only.
MOVE_TRANSACTIONS_COUNT
volumes. This environment variable specifies the number of transactions
that occur before the utility checks the configuration file and shuts down the
relocation process smoothly.
MOZ_PLUGIN_PATH
Set when using Security Services on a Linux platform. To log into a Security
Services-enabled environment on a Linux platform, set this environment
variable to a JRE 1.5 (or later) plug-in path. For example:
/admin/java/Solaris_JRE_1.5.0_11/plugin/sparc/ns7
NLS_SORT
Specifies how data coming back from an Oracle server is sorted. This
environment variable is set through the tc_profilevars property file.
NXMGR_ALLOW_3_TIER_INTEROP
Determines whether Teamcenter Integration for NX will integrate with
Teamcenter in three-tier mode. Setting this variable allows Teamcenter
Integration for NX to work in three-tier mode.
ORACLE_SERVER
Protected variable. Defines the Oracle server network node. Set during
Teamcenter installation and added to the $TC_DATA/tc_profilevars directory.
ORACLE_SID
Protected variable. Defines the unique name of the Oracle database instance
associated with TC_DATA. Set during Teamcenter installation and added to the
$TC_DATA/tc_profilevars directory.
PATH
Defines the tc_profilevars script appends the operating system PATH
environment variable with the full path of the $TC_ROOT/bin directory.
PLUGIN_LOGFILE
Points to a plug-in message log file for Acrobat Reader.
• Error: Not an ARF file.
Used by File Open: unrecognizable input file format.
• Error: Not Tool XML file.
Used by File Open: unrecognizable input file format.
• Error: PDF file filename not found
Used by File Open: cannot find based PDF file.

• Error: FDF file filename not found.
Used by File Open: cannot find based markup FDF file.
• Error: Unable to open file filename.
Used by File Open: cannot access to the displayed file.
• Warning: The selected file(s) have attached Markups. But cannot be

displayed in the Reader because the based PDF is not comment-right
enabled.
Used by File Open by Reader: The plug-in on the Reader requires the
based PDF to have a comment-right enable token embedded in the PDF
file for user to view and perform markup using Reader.
For more information about logging, see the System Administration Guide.
POM_SCHEMA
Protected variable. Defines the .ull file specification (directory path and file
name) of the POM schema file.
By default, the POM schema file is located in the TC_DATA directory. The file
name is very long and conforms to the following format:
pom_schema_$ORACLE_SERVER_$ORACLE_SID
$ORACLE_SERVER is the Oracle server network node, and ORACLE_SID is

the unique name of the Oracle database instance.
POM_TRANSMIT_DIR
Protected variable. Full file specification (directory path and file name) of the
POM transmit schema file. Requires a separate POM transmit schema file for
64-bit and 32-bit platforms.
By default, the POM transmit schema file is located in the
$TC_ROOT/pom_transmit directory. The file name is a concatenation of the
site ID and schema version UID.
PUBLISH_PDF_ERROR_LOG_LOC
Used with Visualization Illustration. Defines a location for
the Convert/Print error log file different from the default
location (c:\Documents and Setting\user name\Local
Settings\Temp\VisProdxxx\123\VVCP_error.log).
This log file records all errors occurring during the PDF conversion process. Set
this environment variable with the full path name and file name. For example:
PUBLISH_PDF_ERRORS
Used with Visualization Illustration. Determines whether the Convert and
Print dialog boxes close when an error occurs. The default value (yes) closes the
dialog boxes when an error occurs. Set to no for the dialog boxes to remain open
after an error occurs.
PUBLISH_PDF_INTERVAL
Used with Visualization Illustration. Determines the amount of time (in
milliseconds) before the system issues each subsequent PDF conversion. Use
this setting to prevent conflicts between simultaneous PDF jobs. This situation

occurs when publishing a portfolio to PDF using the multi PDF option. The
default setting is 1000.
PUBLISH_PDF_MAX_JOBS
Used with Visualization Illustration. Determines the maximum number of
outstanding PDF conversion jobs that can be run simultaneously. This situation
occurs when publishing a portfolio to PDF using the multi PDF option. The
default setting is 10.
PUBLISH_PDF_TIMEOUT
Used with Visualization Illustration. Determines the amount of time (in
milliseconds) allotted for each PDF conversion to complete. The default setting
is INFINITE.
PUBLISH_PDF_VVCP_DEBUG
Used with Visualization Illustration. Determines whether a Convert/Print log is
generated during PDF conversion. This setting is used for debugging. Enabling
logging greatly increases the PDF conversion time and should only be enabled
while debugging. Set to on to enable the logging. The default setting is off.
This environment variable works in conjunction with the
PUBLISH_PDF_VVCP_DEBUG_LOC environment variable. Both
environment variables must be set to enable logging.
PUBLISH_PDF_VVCP_DEBUG_LOC
Used with Visualization Illustration. Determines the location of the
Convert/Print log, which is used for debugging PDF conversion. Enabling
logging greatly increases the PDF conversion time and should only be enabled
while debugging. Set this environment variable with the full path and file name.
For example:
c:\Myfiles\VVCP.log
This environment variable works in conjunction with the

PUBLISH_PDF_VVCP_DEBUG environment variable. Both
environment variables must be set to enable logging.
PUBLISH_PDF_VVCP_TIMEOUT
Used with Visualization Illustration. Determines the amount of time (in seconds)
of the time-out for convert and print jobs. The default setting (600) is typically
adequate for PDF conversions. Set the value higher if, for example, a particular
large, single PDF conversion job is failing due to a completion time-out.
ROSE
Defines the directory containing the STEP Translator run-time application
files. Set through the tc_profilevars property file and must always point to
$TC_DATA. The STEP system fails if drive letters are used in the path pointing
to the TC_DATA directory.
ROSE_DB
Defines the directory containing the STEP Translator run-time data files.
Set through the tc_profilevars property file and it must always point to
$TC_DATA. The STEP system fails if drive letters are used in the path pointing
to the TC_DATA directory.

SHLIB_PATH
Defines the shared display library path for the Hewlett-Packard platform
only. The tc_profilevars script searches for shared display libraries using
LIBMODE, constructs a path statement, and exports SHLIB_PATH.
TAO_ROOT
Defines the directory in which the TAO object request broker (ORB) is installed.
TC_APP_UID_DIR
Defines the directory containing customized display libraries used by
an entire site. This environment variable takes precedence over the
IMAN_SYS_UID_DIR environment variable so that site customizations
override default display libraries.
TC_BIN
Protected variable. Defines the directory containing Teamcenter binary
files. This variable is set during Teamcenter installation and added to the
$TC_DATA/tc_profilevars property file.
TC_BYPASS_CANNED_METHODS
Bypasses the defined canned method. For example, various methods may need to
be bypassed during a legacy import.
When a session is started with this environment variable set, the methods
defined are bypassed for all types. Valid values are:
All
Bypass all methods for all types.
method_1
Bypass method_1 for all types that have method_1 configured.
method_1, method_2
Bypass method_1 and method_2 for all types that have method_1 and
method_2 configured.
TC_DATA
Protected variable. Defines the directory containing Teamcenter data
files. This variable is set during Teamcenter installation and added to the
$TC_DATA/tc_profilevars property file.
TC_DATA_MODEL
TC_DB_CONNECT
Protected variable. Accesses Oracle database tables by logging in to the Oracle
database as user infodba using a partially encrypted connection string passed
to the Oracle database by Teamcenter. The corresponding password is encrypted
for security reasons. This variable is set during Teamcenter installation and
added to the $TC_DATA/tc_profilevars property file.

Warning
Because this environment variable is partially encrypted, it cannot be set
manually. If it becomes corrupted or you forget the password, it must be
regenerated using the Teamcenter Environment Manager.
TC_DISABLE_FLASH
TC_FS_SERVICE
Associated with File Management System. This environment variable is set
through the tc_profilevars property file.
TC_HANDLERS_DEBUG
Determines the amount of workflow handler information sent to the system
log file. Set to ALL to send debug information on all workflow handlers to the
system log file. Set to one or more specific workflow handler names to send
debug information on the specified workflow handlers to the system log file. If
left unset, no workflow handler debug information is logged.
TC_HELP_FILE
Defines the directory containing Teamcenter online help files. This variable is
set during Teamcenter installation and added to the $TC_DATA/tc_profilevars
property file.
TC_HTDOCS
Set through the tc_profilevars property file.
TC_INCLUDE
Protected variable. Defines the directory containing custom ITK header files.
This environment variable must be set in order to access custom ITK programs.
TC_INSTALL_DIR
TC_JOURNAL
Controls journalling.
Accepts the following values:
OFF Creates an empty journal file.
SUMMARY Creates a summary report listing the total time spent on each
journal routine.
FULL Creates a full report listing each call.
MODULE Uses the TC_Journal_Modules preference to select which
modules should be journalled.
Note
Set to FULL to optimize logging information.
Set to MODULE to fine tune logging information.

TC_KEEP_SYSTEM_LOG
Controls the deletion of the system log file.
Y The system log is not deleted, even if there are no errors.
N The system log is deleted if there are no errors.
Note
Set to Y to retain the system log.
TC_LIBRARY
Sets the platform-specific shared display library path. This environment
variable is set to the LD_LIBRARY_PATH, LIB_PATH, or SHLIB_PATH
environment variable, depending on the platform detected when the Teamcenter
session is initiated.
TC_LOG
Defines the directory containing system log files created during Teamcenter
sessions. This directory is created during Teamcenter installation and must not
be removed. If this directory is removed, system log files cannot be created. This
The default setting is:
$TC_DATA/log_$ORACLE_SERVER_$ORACLE_SID
$ORACLE_SERVER is the Oracle server network node, and $ORACLE_SID is

the unique name of the Oracle database instance.
TC_LOG_DIR
volumes. This environment variable specifies the directory that error files, log
files, and output files are placed.
TC_MSG_ROOT
Specifies the path to where utilities can locate localized error messages.
Typically, this is set to $TC_ROOT/lang/textserver. This environment variable
is set through the tc_profilevars property file.
TC_no_obsolete_message
Setting this environment variable to any value suppresses ITK warning
messages.
TC_NX_DEFAULT_PART
Defines the default NX part file. This environment variable is set through the
tc_profilevars property file.
TC_ONLINE_HELP
TC_PERFORMANCE_MONITOR
Automatically displays the Performance Monitor dialog box in the rich client
after logon and enables SQL tracking statistics.

TC_POM_JOURNALLING
Determines whether the POM module journals nested calls.
Set to N for full journalling.
TC_PRINTER
Protected variable. Defines the default Teamcenter printer. Other printers can
be accessed through the Workspace System→Printer command.
TC_ROOT
Top (root) directory of the Teamcenter directory structure. This environment
variable must be set before running the application or command line utilities.
TC_SLOW_SQL
Writes explain plans to the system log file for SQL statements that run longer
than the specified time. The explain plans can be used to suggest indexes that
can be added to speed up the query. Set the environment variable to a number of
seconds. The specified value is interpreted as a floating point time in seconds. If
it is set to less than or equal to zero, explain plans are not written. The time is
real time, not CPU time. It only generates explain plans for the first 10 cases.
Defaults to 10 seconds.
TC_SOA_MAX_PROPERTIES
Defines the maximum number of properties that can be returned when an object
property policy is enacted while using Teamcenter Services.
For more information, see the Services Guide.
TC_SQL_DEBUG
J Copies all SQL statements to the journal file as well as the system log file.
P Includes profiling data; reports the frequency of use of each distinct
statement in a summary at the end of log file.
T Includes timing data; reports the time of each SQL statement.
B Binds variables; expands SQL bind variables (this is the default setting)
b Reports bind variables in :1 format, rather than expanding them.
Note
Set to JPT to optimize logging information.
TC_SSO_SERVICE
Enables Security Services functionality by setting the complete URL the ITK
server uses to communicate with Security Services. This environment variable is
set through the tc_profilevars file.
In the rich client and ITK, the ability to set or change a password in the
Teamcenter database is disabled when this environment variable is set. The
Change Password command remains available from the Actions menu. In the
Organization application, the password text field and blank password check
box are disabled.

TC_SSO_CHANGE_PASSWORD_PAGE
Determines the URL to which the thin client redirects the change password page
by setting the complete URL for the local change password page provided via
the identity provider used with Security Services. This environment variable is
optional, and when available is set through the tc_profilevars file.
This environment variable should be set only if Security Services is enabled via
the TC_SSO_SERVICE environment variable.
TC_SSO_LOGIN_PAGE
Determines the URL to which the thin client redirects the log on by setting the
complete URL for the Security Services log on page. This environment variable
is set through the tc_profilevars file.
This environment variable should be set only if Security Services is enabled
using the TC_SSO_SERVICE environment variable.
TC_SSO_LOGIN_URL
Directs the rich client to use the Security Services application client library to
obtain an appToken from the SSO applet. If the applet is not already running,
a browser is launched on the given URL to start a Security Services session. This
environment variable is set in the rich client’s properties file. For the two-tier
rich client, the file is the client_specific.properties file. For the four-tier rich
client, the file is the site_specific.properties file.
TC_SSO_APP_ID
Use this environment variable when multiple Teamcenter sites are served
by a single identity provider, or Security Services is configured to use an
ID other than Teamcenter (this is the default when the TC_SSO_APP_ID
environment variable is not set). When the multiple sites have different sets
of users authorized to use the application for each installation, or different
identifications in each installation, this environment variable is used to identify
which installation is authenticated.
Set this environment variable in both the tc_profilevars file for the server and
the client’s site_specific.properties file.
TC_TMP_DIR
Specifies where the utilities should create temporary files. This environment
variable is set through the tc_profilevars property file.
TC_TRACEBACK
Controls the writing of tracebacks to the system log file.
ON Writes tracebacks to the system log file.
OFF Does not write tracebacks to the system log file.

Note
When errors occur, the system writes tracebacks to the system log file by
default. Use this environment variable to override the default behavior.
TC_USE_DEFAULT_EXPORT_SITES
Specifies whether to use the TC_default_export_sites preference. Set to YES
to enable the preference.
TC_USE_LOV_SHARED_MEMORY
Determines whether the Teamcenter server loads localized LOV display names
into shared memory. Set this environment variable to either TRUE or FALSE.
The default setting is TRUE.
If shared memory cannot be used, the system uses process memory. In rare
instances when the system reports a problem with shared memory and cannot
fall back to using process memory, set this environment variable to FALSE and
restart the system.
Note
Because localized LOV display can slow system performance, you can use
the Fnd0LOVDisplayAsEnabled global constant to disable loading
localized LOV display names.
For more information, see the Business Modeler IDE Guide.
TC_USE_PREFS_SHARED_MEMORY
Determines whether the Teamcenter server loads preferences into shared
memory. Set this environment variable to either TRUE or FALSE. In a four-tier
configuration, the default setting is TRUE. In a two-tier configuration, the
default setting is FALSE.
Siemens PLM Software recommends using the default settings.
TC_USE_TEST_ATTR_MAPPINGS
Retrieves the test attribute mappings definition rather than the real mapping
file when set to any value.
TC_USER_LIB
Contains user-defined display libraries. If this variable is set in the
environment, the tc_profilevars property file adds this directory to the
LD_LIBRARY_PATH, LIB_PATH, or SHLIB_PATH settings.
TC_USER_MSG_DIR
Contains XML text and error message files.
TC_USER_UID_DIR
Contains customized display libraries used by a single user. This variable takes
precedence over the IMAN_SYS_UID_DIR environment variable and the
TC_APP_UID_DIR environment variables so that user customization overrides
default and site display libraries.
TC_USER_TOOLS
Protected variable. Contains user-defined software applications. Set through the

TC_WEB_NO_CACHE
Optimizes performance by caching TcScript parse trees if set to FALSE. Avoids
the need to restart the tcserver process after changes if set to TRUE. Set to
TRUE while modifying TcScript code and then set back to FALSE after you
complete your changes.
TC_WSDL_MAX_PROPERTIES
Defines the maximum number of properties that can be returned by WSDL-based
clients when using Teamcenter Services.
For more information, see the Services Guide.
TC_XML_ENCODING
Used to include templates from other languages. On the server side, controls the
encoding environment for the XML file generated. The first line in the XML file
must specify the encoding required.
TCSSO_LOGIN_SERVICE_URL
Enables the WebSEAL feature within clients. Set this variable to the URL
address of the Security Services Login Service as configured for the WebSEAL
proxy server.
TCVIS_ALSG_ENABLED
Disables support for the viewing of JtSimplification datasets in the Lifecycle
Viewer and the stand-alone viewers, such as Mockup. By default, this variable
is not set and JtSimplification is automatically enabled in properly licensed
viewers. Set this variable to False if you want to disable the functionality.
TEMP_FILESEARCHPATH
TNS_ADMIN
Identifies the path where the tnsnames.ora file and sqlora.net files are
located. These are used when communicating with an Oracle server. This
Transient_Volume_Installation_Location
Specifies the node name of the transient volume. It is a location-based logical
identifier, and is generally set to the host name of the local machine by the
tc_profilevars script. This environment variable overrides the preference of the
same name. When a four-tier transient volume is mounted on all Teamcenter
server hosts at a given location, use this setting to configure the distributed
transient volume.
UGII_APISERVER_PROGRAM
Defines the full file specification (directory path and file name) of the UG Hookup
binary. Set through the tc_profilevars property file.
UGII_BASE_DIR
Defines the topmost directory of the NX directory structure, the NX equivalent of
$TC_ROOT. This environment variable is set by NX.
UIL_INCLUDE
Specifies a semicolon-separated list of directories where .uih files to be included
are located.

UGII_OPTION
Determines how to interpret and convert file specifications. This environment
variable can drastically affect Teamcenter File Services and other Teamcenter
behavior. For example, if you create Teamcenter volumes with mixed-case names
and this preference is set to LOWER, Teamcenter File Services is not able to find
your volumes. Therefore, ensure that this environment variable is set consistent
with file specification naming conventions at your site.
This environment variable accepts the following values:
NONE File specifications are interpreted without converting case.
LOWER Converts the entire file specification (directory and file name) to all
lowercase.
UPPER Converts the entire file specification (directory and file name) to all
uppercase.
HINAME Converts the file name to all uppercase but leaves the directory path
name unchanged.
LONAME Converts the file name to all lowercase but leaves the directory path
name unchanged.
UGII_USE_NEW_SURFACE_FILE_FORMAT
Instructs the ug_spacemap utility running on the NX client to perform
platform-independent processing of input and output files. This setting only
affects surface files, not SPM file.
UGII_USERFCN
Defines the directory containing NX user function libraries. Set through the
UGS_LICENSE_SERVER
Specifies the location of the license server.
The default setting is:
port@host
Replace port with the port number and host with the host name of the license
server, for example, 28000@tchost. The port and host values must match those
you specified in the SERVER line of the Teamcenter license file.
XFILESEARCHPATH
Protected variable. Defines the directory containing X-Window System resource
definition files. Set through the tc_profilevars property file. If not set,
X-Window System uses the $HOME directory.

Chapter
4 Introduction to preferences
Preference interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Options pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Preferences pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Search by keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Current values buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Organization pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Managing preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Installation and upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Preference scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
User access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Preference precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Generating preference reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Create preference reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Migrate preferences to data model objects . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Creating and deleting preference categories . . . . . . . . . . . . . . . . . . . . . . 4-10
Teamcenter Integration for NX preferences . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Chapter
4 Introduction to preferences
Preferences are special environment variables stored in the Teamcenter database.

They are read during Teamcenter application usage. Each application may have
associated preferences. Preferences allow you to configure many aspects of a session
of application behavior, such as how assemblies are revised, whether extension
rules are bypassed for specified operations, and which Teamcenter objects display in
integrations.
Note
Some preferences are automatically created when certain functionality is
added.
Preference interface
Choose Edit→Options to open the Options dialog box. Use the Options dialog box to
search for preferences, set preference values, create new preferences, and remove
existing preferences.
Preferences can also be manually modified in a copy of the tc_preferences.xml file.
After modifying, use the preferences_manager utility to import the file.

Chapter 4 Introduction to preferences
1 Options link Displays the Options pane where you work with a
limited set of preferences in the form of options.
For more information, see Options pane.
2 Index link Displays the Preferences pane where you search for
preferences based on a preference name.
For more information, see Preferences pane.
3 Search link Displays the Search Options pane where you search
for preferences based on keywords.
For more information, see Search Options pane.
4 Organization Displays the Organization pane where you view the
link preferences applicable to group, role, and user.
For more information, see Organization pane.
Options pane
You can work with a limited set of preferences. Use the Options pane of the Options
dialog box to configure preferences.
Option details display when an option is selected from the Options tree. Option
details optionally have tabs of data to separate option configurations.
Preferences pane
The Index link displays the Preferences pane of the Options dialog box. The
Preferences pane enables you to work directly with the entire preference set.

Introduction to preferences
From the Preferences pane, you can:

• Search for preferences in the database.
• Modify preference values.
• Delete preferences.
• Add preferences to the database.
• Create new categories for organizing preferences.
• Import and export preferences.
• Report customized preferences.
Search by keyword
The Search link displays the Search Options pane of the Options dialog box. The
Search Options pane enables you to work directly with the entire preference set.
The Search Options pane operates similar to the Preferences pane, but with
additional search features.
From the Search Options pane, you can
• Search for preferences based on keywords.
• Select search in options of keys, description, and values.
• Select match options for case sensitivity and entire word.
• Specify a wildcard character.

Current values buttons

Remove Remove the selected value from the list.
Up Move the selected value up one position in the list.
Down Move the selected value down one position in the list.
Sort Order the values alphabetically.
Add Add the new value entered in the box to the list.
Modify Update the selected value with the new value entered
in the box.
Organization pane
The Organization link displays the Organization pane of the Options dialog box.
The Organization pane enables you to view preferences based on groups, roles and
users in the organization.
From the Organization pane:

• Users can see the preference applicable to their site, group, role and user scopes,
but they cannot see other users’ preferences.
• Group administrators can see the preferences for the site, the group that they
administrate, and roles and users belonging to the group.

• A system administrator can see all the preferences for the site, groups, roles,
and users.
Managing preferences
When working with preferences, you must take each preference’s scope into
consideration. The scope of a preference determines both user access to the
preference and precedence of its behavior when there are multiple incidences of the
same preference. Preference scope is displayed in the Details view of the Options
dialog box. When an existing preference is selected, its scope displays to the right
of the Name box.
For more information about this dialog box, see the Rich Client Interface Guide.
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 on working with business objects, see the Business Modeler
IDE Guide.
Installation and upgrades

Teamcenter ships all preference data in the tc_preferences.xml file, stored in
the TC_DATA directory. Teamcenter reads most of the preference data from
this directory. Any custom site preferences created at your site are stored in the
Teamcenter database.
During upgrades, the system runs the preferences_manager utility to remove the
definitions and values of any out-of-the-box preferences previously stored in the
Note
Previous to Teamcenter 2007, all preferences were stored in the Teamcenter
database. Out-of-the-box preferences are now stored in the TC_DATA
directory. Only custom site preferences are stored in the Teamcenter database.
You can also use the preferences_manager utility during upgrades to convert
legacy preference files to XML format and to import and export preferences to and
from the database. This utility parses the legacy site preference file to XML format.
Preference scope
The scope of a preference determines user access to the preference. A user’s current
group/role logon determines which existing preferences he can modify, and the scope
assigned to any newly created preference. The scope of the selected preference
displays to the right of the Name box in the Options dialog box.

The scope of a preference also determines its precedence when there are multiple
instances of the same preference in the database. For example, when one instance
of the preference for displaying the NX button in the Teamcenter toolbar is set by
a system administrator as a site preference, and another instance of the same
preference is set by an individual user as a user preference, the preference’s scope
determines which instance is given precedence.
User access
When accessing existing preferences in the Options dialog box, a user’s current
group/role logon determines which preferences can be modified. For example, a
user logged on as Engineering/Designer could modify all Engineering group
preferences and all Designer role preferences. The user could not modify other role
preferences, such as Reviewer, Manager, or Tester. Users belonging to multiple
groups and roles must change their group/role logon to modify preferences affecting
other groups or roles.
• Users logged on with system administrative access can modify all preferences.
• Users logged on with group administrative access can modify preferences with a
scope of Group, Role, or User.
• Users logged on with general user access can modify preferences with a scope
of User.
When a user creates a new preference in the Options dialog box, the current
group/role log determines the type of scope that can be assigned to the preference.
The Create New Preferences boxes differ, depending upon the user’s current logon
settings. For example, site preferences can only be created by users logged on with
administrative access. A user logged on as dba/dba can modify site preferences. A
user logged on as Engineering/Designer cannot.
• Users logged on with system administrative access can choose User, Role,
Group, or Site scope from the Scopes box.
• Users logged on with group administrative access can choose User, Role, or
Group scope from the Scopes box. The Site scope option is unavailable.
• Users logged on with general user access are not shown the Scopes box. Any
preference created is automatically assigned User scope.
Preference precedence
Preferences are stored as XML strings in specific tables in the database. Preference
scope determines in which table a preference is stored. Data from the site table
is loaded during server startup and data from the other table is loaded at user
logon. Only data from the current logon credentials are loaded. Preference scope
also determines the order in which the system searches through the tables for the
preference and its values.
The following list defines how the preferences are searched from the Teamcenter
database:
• User
When scope is User, the system searches through preference data in the
following order: User, Role, Group, Overlay, Site.
• Role

When scope is Role, the system searches through preference data in the
following order: Role, Group, Overlay, Site.
If the user changes group or role settings during a session, the appropriate group
and role preferences are loaded.
• Group
When scope is Group, the system searches through the preference data in the
following order: Group, Overlay, Site.
If the user changes group or role settings during a session, the appropriate group
and role preferences are loaded.
• Site
When scope is Site, the system searches through the preference data in the
following order: Overlay, Site.
• All
When scope is ALL, the system searches through the preference data in the
following order: environment variables, User, Role, Group, Overlay, Site.
Keeping the rules of user access and preference precedence in mind, consider the
following example:
A site administrator uses the search feature in the Options dialog box to search for
the TC_inbox_interval preference and to set it at 20, causing the system to check
inboxes for new tasks every 20 minutes. A user with very few tasks creates another
instance of this preference and sets it at 0, causing the system to check his inbox for
new tasks only once per session, at logon.
The site administrator created the preference while logged on with a group/role
of dba/dba. The user created the preference while logged on with a group/role of
accounting/auditor.
When the auditor logs on, the system automatically checks his user preferences.
Finding an instance of the TC_inbox_interval preference, the system performs
the behavior directed by the preference’s value, and checks the auditor’s inbox for
new tasks only at logon. The system then continues to check the other scopes in
precedence order. When it reaches the overlay preferences, it once again finds an
instance of the TC_inbox_interval preference. Because a user preference setting
takes precedence over an overlay setting, the system continues to perform the
behavior directed by the user’s setting.
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 delivered in the tc_preferences.xml file 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.
• 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. Click Report in the Index tab of the Options dialog box.
The Report dialog box appears.
2. Select the 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 current values. Use
the forward and back buttons at the top of the dialog box to view the various
preferences.
3. (Optional). To export the report, type a path and file name in the Export File
Name box (or browse to an existing file) and click Export.
The preference report is exported to the specified file in XML format.
Migrate preferences to data model objects

Some preferences are converted to Business Modeler IDE template data model
objects, such as business object constants. This centralizes data model-dependent
preferences in the Business Modeler IDE. If your database contains any of the
converted preferences, you must migrate them using the Preferences Migration
wizard.
The following preferences are converted:
• ItemRevision-business-object_Maturity_Level
These preferences set the status that an item revision must reach to be
considered mature. These preferences are obsolete and are migrated to values on
the MaturityStatuses business object constant. For example, if your database
had a DocumenRevision_Maturity_Level preference set to the Frozen value,
it is migrated to the Frozen value on the MaturityStatuses business object
constant on the DocumentRevision business object.
For more information about the MaturityStatuses business object constant,
see the Business Modeler IDE Guide.

Note
If you are upgrading from an earlier version of Teamcenter, you should
verify that all of your relation properties are now managed in the
Business Modeler IDE. To verify, look in your preferences for each
<relation_type>_relation_primary preference that you added, and add it
to your custom template in the Business Modeler IDE.
To find any custom preferences that fit the converted preferences, choose
Edit→Options→Index in the My Teamcenter application in the rich client. If you
find that your database contains at least one of the converted preferences, you must
perform the following steps to migrate the preferences:
1. Use the preferences_manager utility to extract site level preferences from
your current database. This is the database currently in use at your site and
not yet upgraded.
Run the command from the Teamcenter command prompt:
preferences_manager -u=user-name -p=password -g=group
-mode=generatexml -context=Teamcenter
-out_file=c:\temp\exported_preferences.xml
This extracts all the site-level preferences to the specified XML file.
2. In the Business Modeler IDE, choose File→New→Other, and in the Select

a wizard dialog box, choose Business Modeler IDE→Preferences Migration
Wizard. Click Next.
3. In the Preferences Migration dialog box, perform the following steps:

a. Click the arrow in the Project box to select the project that the preferences
will be migrated into.
b. Click the Browse button to the right of the Preferences XML File to locate
the output XML file that resulted from running the preferences_manager
utility.
c. Click Finish.
A project/install/cleanup_preferences.txt file is created that contains the
list of preferences to be deleted from the database. Do not delete this file.
This file must be maintained in your source control. This file is packaged
when you run the Package Template Extensions wizard in the Business
Modeler IDE and is used during the database upgrade to remove the
converted preferences from the database.
In addition, a project/output/upgrade/preferences_migration.log file is
created that contains the migration log.
4. To verify the migration, in the Business Modeler IDE, open the new business
objects that are created by the migration process. Ensure that the Business
Object Constants table contains the new business object constants.

Note
Only the custom ItemRevision-business-object_Maturity_Level
preferences are migrated into the project as business object constants.
All the other preferences are ignored. The preferences are migrated to
business objects named ItemRevision-business-object_Maturity_Level,
and the MaturityStatuses business object constant is applied to these
new business objects.
5. To save the changes to the data model, choose File→Save Data Model, or click
the Save Data Model button on the main toolbar. This saves template extension
files that now contain preferences converted to template elements.
6. Update the customer upgrade script to remove the migrated preferences

from the database during upgrade of the customer database. This step
ensures that when the database is upgraded, the obsolete preferences listed in
cleanup_preferences.txt also get deleted from the database.
a. Open the upgrade_template-name_vversion.default file. If this file does not
exist, create one using your old upgrade_template-name_vversion.default
script as an example.
b. Add the following text in the post-non-schema-delete section of the file:

preferences_manager -u=infodba -p=${TC_USER_PASSWD} -g=dba -mode=remove
-scope=SITE
-file=${TC_INSTALL_DIR}/template-name/cleanup_preferences.txt
Replace template-name with the name of your custom template.
7. Update your existing custom preferences data file. You may have a custom
preferences data file that installs custom preferences to your database. If this
file contains any of the preferences just migrated, remove them from this file.
This is to ensure that the preference data file does not continue installing any
of the migrated preferences.
Creating and deleting preference categories

Note
You must be an administrator to create or delete preference categories.
To create a new preference category:

1. In My Teamcenter, choose Edit→Options.
2. Click Index.
3. Click Category.
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.
To delete a preference category:

1. In My Teamcenter, choose Edit→Options.
2. Click Index.
3. Click Category.
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 a preference category that has preferences in it. You must
delete the preferences before deleting the category. Placeholder preferences
(category-name_NOTREALPREF) do not need to be deleted.
Teamcenter Integration for NX preferences

Teamcenter Integration for NX preferences control how Teamcenter interacts with
NX, such as the way part data is displayed in the rich client, or how changes made in
Teamcenter are reflected in NX assemblies and parts. Preferences controlling this
functionality are listed in the NXManagerUnigraphics category of the Options
dialog box, accessed from the Edit menu. These preferences have precedence over
Teamcenter preferences.
For information about setting these preferences, see the Rich Client Interface Guide.

Chapter
5 Configuration preferences
Business Modeler IDE preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

AltIdentifier_require_on_create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
ASSIGNED_ITEM_ID_MODIFIABLE . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
ASSIGNED_ITEM_REV_MODIFIABLE . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
BMF_CUSTOM_IMPLEMENTOR_PATH . . . . . . . . . . . . . . . . . . . . . . . . 5-2
BMIDE_ALLOW_DEPLOYMENT_FROM_CLIENT . . . . . . . . . . . . . . . . . 5-3
Bypass_property_rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
IdentifierContextPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
IdentifierLengthPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
ITEM_autogenerate_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
METHOD_CM_execute_before_custom . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
NR_BYPASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
TC_dataset_deep_copy_rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Treat_Curr_Rev_As_Any_Rev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Treat_Next_Rev_As_Any_Rev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
TYPE_DISPLAY_RULES_list_of_primary_types . . . . . . . . . . . . . . . . . . . 5-7
TYPE_DISPLAY_RULES_list_types_of_subclasses . . . . . . . . . . . . . . . . . 5-7
Client interface preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Confirmation_shown_on_reservation_dialogs . . . . . . . . . . . . . . . . . . . . . . 5-8
Confirm_cancel_checkout_suppressed . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Confirm_checkin_suppressed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Confirm_checkout_suppressed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Form_double_click . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
OCS_company_email_domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
OCS_use_email_property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
OCS_use_presence_display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Data management preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

ADA_allow_license_propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
ADA_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
ADA_saveas_propagated_license_types . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
AE_dataset_id_gen_by_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
AE_dataset_id_postfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
AE_dataset_id_prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
AE_dataset_id_separator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
AE_dataset_id_usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
AE_dataset_id_use_rev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Baseline_allowed_baserev_statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Baseline_allow_edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Baseline_create_snapshot_folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
baselineDryRun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Baseline_dryrun_always . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Baseline_nxmanager_refile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Baseline_precise_bvr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Baseline_refile_not_required_item_types . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Baseline_refile_required_dstypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Baseline_release_procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Baseline_restricted_item_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
BOB_property_optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
CheckoutOnCreatePref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
IDENTIFIER_idincontext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
IP_level_list_ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
ITAR_level_list_ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
ITEM_baseline_rev_msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
license_warning_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
SOACAD_checkout_required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
TC_check_object_before_create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
TCCheckoutReserveOnly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
TC_Dataset_Import_Exclude_Wildcard . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
TCDefaultKeepLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
TCDefaultKeepLimitByType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
TC_multi_site_ada_license_user_bypass . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
TC_session_clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
USER_baseline_dryrun_validator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Dispatcher preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

DISPATCHER_CLIENT_INSTALLED . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
ETS.Repeating_UI.<ProviderName>.<ServiceName> . . . . . . . . . . . . . . . . 5-27
ETS_available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
ETS_home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
ETS.PROVIDERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
ETS.TRANSLATORS.<ProviderName> . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
ETS.VALIDATE.<ProviderName>.<ServiceName> . . . . . . . . . . . . . . . . . 5-28
ETS_trans_rqst_referenced_dataset_types . . . . . . . . . . . . . . . . . . . . . . . 5-29
ETS_update_state_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
ETS_released_status_type_names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
ETS_trans_rqst_user_exit_states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
TC_register_internal_service_modules . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
IDEAS_translation_service_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
IDEAS_import_translation_service_name . . . . . . . . . . . . . . . . . . . . . . . . 5-31
IDEAS_translation_dataset_type_names . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
UGSideastojt_IdeasAssembly_ets_nr_types . . . . . . . . . . . . . . . . . . . . . . . 5-32
UGSideastojt_IdeasDrawing_ets_nr_types . . . . . . . . . . . . . . . . . . . . . . . 5-33
UGSideastojt_IdeasPart_ets_nr_types . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
IDEAS_import_from_tdm_gen_vis_data_display . . . . . . . . . . . . . . . . . . . 5-33
IDEAS_import_from_tdm_default_gen_vis_data_priority . . . . . . . . . . . . . 5-34
IDEAS_import_from_tdm_gen_vis_data_input . . . . . . . . . . . . . . . . . . . . . 5-34
IDEAS_import_from_tdm_options_default_gen_vis_data_priority . . . . . . . 5-35
IDEAS_check_in_generate_vis_data_priority . . . . . . . . . . . . . . . . . . . . . . 5-35
IDEAS_on_demand_generate_vis_data_priority . . . . . . . . . . . . . . . . . . . . 5-36
IMAN_capture_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
CATIA_translation_service_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
CATIA_check_in_generate_vis_data_priority . . . . . . . . . . . . . . . . . . . . . . 5-37
CATIA_checkin_generate_vis_data_priority . . . . . . . . . . . . . . . . . . . . . . 5-38
CATIA_on_demand_generate_vis_data_priority . . . . . . . . . . . . . . . . . . . . 5-38
COMMONcatiatojt_CATPart_ets_nr_types . . . . . . . . . . . . . . . . . . . . . . . 5-39
Preferences and Environment Variables Reference PLM00026 F

COMMONcatiatojt_CATProduct_ets_nr_types . . . . . . . . . . . . . . . . . . . . . 5-39
COMMONcatiatojt_ets_ds_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
CATIA_work_dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
CATIA_V4_translation_service_name . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
CATIA_V4_check_in_generate_vis_data_priority . . . . . . . . . . . . . . . . . . . 5-41
CATIA_V4_on_demand_generate_vis_data_priority . . . . . . . . . . . . . . . . . 5-41
COMMONcatiatojt_catia_ets_nr_types . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
COMMONcatiatojtV4_ets_ds_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
NX_translation_service_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
NX_tocgm_translation_service_name . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
NX_on_demand_generate_vis_data_priority . . . . . . . . . . . . . . . . . . . . . . 5-43
NX_tocgm_on_demand_generate_vis_data_priority . . . . . . . . . . . . . . . . . 5-44
UGSnxtocgmdirect_UGALTREP_ets_nr_types . . . . . . . . . . . . . . . . . . . . . 5-44
UGSnxtocgmdirect_UGMASTER_ets_nr_types . . . . . . . . . . . . . . . . . . . . 5-45
UGSnxtocgmdirect_UGPART_ets_nr_types . . . . . . . . . . . . . . . . . . . . . . . 5-45
UGSnxtocgmdirect_UGSCENARIO_ets_nr_types . . . . . . . . . . . . . . . . . . 5-45
UGSnxtocgmdirect_ets_ds_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
UGSnxtopvdirect_UGALTREP_ets_nr_types . . . . . . . . . . . . . . . . . . . . . . 5-46
UGSnxtopvdirect_UGMASTER_ets_nr_types . . . . . . . . . . . . . . . . . . . . . 5-47
UGSnxtopvdirect_UGPART_ets_nr_types . . . . . . . . . . . . . . . . . . . . . . . . 5-47
UGSnxtopvdirect_ets_ds_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
IMAN_Drawing_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
UGMASTER_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
UGPART_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
PROE_translation_service_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
PROE_on_demand_generate_vis_data_priority . . . . . . . . . . . . . . . . . . . . 5-49
UGSproetojt_ProPrt_ets_nr_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
UGSproetojt_ets_ds_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
VIS_simpgen_admin_group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Full-text search preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51

search_automatic_wildcard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
TC_fts_aci_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
TC_fts_database_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
TC_fts_default_language_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
TC_fts_engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
TC_fts_fsf_host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
TC_fts_fsf_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
TC_fts_host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
TC_fts_index_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
TC_fts_index_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
TC_fts_index_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
TC_fts_indexed_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
TC_fts_indexing_wait_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
TC_fts_max_results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
TC_fts_query_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
TC_fts_service_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
TC_fts_real_time_indexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
<TypeName>_indexed_properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
Localization preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59

TC_language_data_entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
TC_language_default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
TC_language_localization_display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62

TC_language_localized_property_value_display . . . . . . . . . . . . . . . . . . . . 5-62
TC_language_localized_property_value_entry . . . . . . . . . . . . . . . . . . . . . 5-63
TC_language_search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
Mail gateway preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65

Folder_mail_properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
Mail_server_charset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
Mail_server_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
Mail_server_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
Mail_OSMail_activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
TC_use_tc_alias_in_pa8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
TC_mail_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
NX Integration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68

Preferences set in the .tc_preferences.xml file . . . . . . . . . . . . . . . . . . . . . 5-68
API_ugpart_attr_titles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
DATASET_saveas_allow_duplicates . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
DATASET_saveas_allow_name_modification . . . . . . . . . . . . . . . . . . . 5-69
DATASET_saveas_always_copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
DATASET_saveas_force_name_validation . . . . . . . . . . . . . . . . . . . . . 5-70
DATASET_saveas_never_copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
DATASET_saveas_owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
DATASET_saveas_pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72
<DATASET TYPE>_saveas_pattern . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
NX_InterOptWithProductViewDataset . . . . . . . . . . . . . . . . . . . . . . . 5-73
TC_default_part_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
TC_NX_allow_attrsync_master_with_item . . . . . . . . . . . . . . . . . . . . 5-74
TC_NX_Allow_Deepcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
TC_NX_ATTRIBUTES_FORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
TC_NX_Database_Attributes_For_Load . . . . . . . . . . . . . . . . . . . . . . 5-75
TC_NX_DeleteMarkupsOnDrawingSheetImport . . . . . . . . . . . . . . . . 5-77
TC_NX_DrawingSheet_Deletion_Pattern . . . . . . . . . . . . . . . . . . . . . 5-77
TC_NX_Foreign_Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
TC_ugmaster_name_separator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
TC_NX_Navigator_Override_NX_Load_Option . . . . . . . . . . . . . . . . . 5-79
TC_NX_NEW_COPY_REV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79
TC_NX_NEW_NR_FORMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80
TC_NX_nonmaster_additional_forms . . . . . . . . . . . . . . . . . . . . . . . . 5-80
TC_NX_save_precise_on_uprev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-81
TC_NX_Unit_Of_Measure_As_Geometric_List . . . . . . . . . . . . . . . . . . 5-81
TC_NX_Unit_Of_Measure_Each_List . . . . . . . . . . . . . . . . . . . . . . . . 5-81
TC_NX_UPDATE_ATTRIBUTES . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
TC_NX_View_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
TC_SPSD_FOLDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-83
TC_SPSD_FOLDER_PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-83
TC_USE_TEST_ATTR_MAPPINGS . . . . . . . . . . . . . . . . . . . . . . . . . 5-84
Preferences set in the .tc_ugman_env file . . . . . . . . . . . . . . . . . . . . . . . . 5-84
UGMAN_InsertItem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-84
UGMAN_PartType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85
UGMAN_ShowPartType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85
UGMAN_UGPARTNameWRev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85
Preferences set in the ug_english.def file . . . . . . . . . . . . . . . . . . . . . . . . . 5-86
UGhookupStructureUpdateOnSave . . . . . . . . . . . . . . . . . . . . . . . . . 5-86
UGhookupStructureUpdateOnLoad . . . . . . . . . . . . . . . . . . . . . . . . . 5-86

UGhookupPartDisplayPreference . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-87
Preferences set in the .ugii_env file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-87
TRACE_BACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-87
UGII_KEEP_SYSTEM_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-87
UGII_OPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-88
UGII_TMP_DIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-88
Password preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-89

PASSWORD_minimum_characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-89
PASSWORD_special_characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-89
PASSWORD_mixed_case_required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-90
PASSWORD_minimum_special_chars . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-90
PASSWORD_minimum_digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-90
PASSWORD_minimum_alpha . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-91
Teamcenter services preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-91

SOA_MaxOperationBracketInactiveTime . . . . . . . . . . . . . . . . . . . . . . . . 5-91
SOA_MaxOperationBracketTime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-91
Remote workflow preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-92

TC_external_local_app_guid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-92
TC_external_proxiable_objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-92
TC_external_proxiable_objects_props . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-93
TC_external_Requirements_proxy_props_internal . . . . . . . . . . . . . . . . . . 5-93
TC_external_Requirements_proxy_props_external . . . . . . . . . . . . . . . . . . 5-94
IMAN_external_appl_reg_url . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-94
TC_external_application_names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-94
TC_external_application_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-95
Teamcenter LDAP synchronization preferences . . . . . . . . . . . . . . . . . . . . . . . 5-95

LDAP connection preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-96
LDAP_service_hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-96
LDAP_port_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-96
LDAP_use_ssl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-96
LDAP_cert_db_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-97
LDAP_admin_dn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-97
LDAP_admin_pw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98
Synchronization preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98
LDAP_sync_user_flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98
LDAP_sync_group_flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99
LDAP_sync_member_flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99
LDAP_sync_role_flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-100
LDAP_member_list_attr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101
LDAP_member_type_attr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101
LDAP_object_type_attr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101
Group object mapping preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-102
LDAP_group_base_dn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-102
LDAP_group_query_filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-102
LDAP_group_object_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103
LDAP_group_attr_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103
Role object mapping preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-104
LDAP_role_query_filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-104
LDAP_role_object_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-104
LDAP_role_attr_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105

User and person object mapping preferences . . . . . . . . . . . . . . . . . . . . . 5-105
LDAP_attribute_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105
LDAP_base_dn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-106
LDAP_ignore_users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107
LDAP_user_query_filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107
LDAP_user_object_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107
LDAP_person_attr_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108
Validation Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-109

Baseline_precondition_validation_rule_item_revision . . . . . . . . . . . . . . . 5-109
NXCheckMateCreate.CREATE_REGISTEREDTO . . . . . . . . . . . . . . . . . 5-109
NXCheckMate.CREATERENDERING . . . . . . . . . . . . . . . . . . . . . . . . . 5-109
NXCheckMateRevision.SUMMARYRENDERING . . . . . . . . . . . . . . . . . 5-110
NXCheckMateRevSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . 5-110
NXCheckMate.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . . . 5-110
NXCheckMateSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . . . . 5-111
NXCMValDataCreate.CREATE_REGISTEREDTO . . . . . . . . . . . . . . . . 5-111
NXCMValData.CREATERENDERING . . . . . . . . . . . . . . . . . . . . . . . . . 5-111
NXCMValDataRevision.SUMMARYRENDERING . . . . . . . . . . . . . . . . . 5-112
NXCMValDataRevSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . 5-112
NXCMValData.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . . . 5-112
NXCMValDataSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . . . 5-113
NXRDDVRevision.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . 5-113
NXRDDVRevSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . . . . . 5-113
NXRDDV.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-114
NXRDDVSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . . . . . . . 5-114
NXRDDVValDataRevision.SUMMARYRENDERING . . . . . . . . . . . . . . . 5-114
NXRDDVValDataRevSummary.SUMMARY_REGISTEREDTO . . . . . . . . 5-115
NXRDDVValData.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . 5-115
NXRDDVValDataSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . 5-115
TC_ALLOW_ADHOC_VALIDATIONS . . . . . . . . . . . . . . . . . . . . . . . . . 5-116
TC_Validation_Datasettype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-116
TC_VALIDATION_duplicate_nx_valdata_error_on_import . . . . . . . . . . . 5-116
TC_VALIDATION_FILE_TYPES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-117
TC_VALIDATION_mandatory_checkers_required . . . . . . . . . . . . . . . . . 5-117
TC_VALIDATION_PROGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-118
TC_Validation_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-118
TC_VALIDATION_RESULT_ALLOW_REPLICA_OBJECT . . . . . . . . . . 5-118
TC_VALIDATION_RULE_SET_ITEM_REVISIONS . . . . . . . . . . . . . . . 5-119
TC_VALIDATION_run_validation_hidden_agents . . . . . . . . . . . . . . . . . 5-119
TC_VALIDATION_STYLESHEET_DATASETNAME . . . . . . . . . . . . . . . 5-119
TC_VALIDATION_TIMESTAMP_NREFS . . . . . . . . . . . . . . . . . . . . . . . 5-120
TC_VALIDATION_USE_PLMXML . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-120
TC_Validation_Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-121
TC_VALIDATION_ViewValidationWithRuleSetColumnPreferences . . . . . 5-122
TC_VALIDATION_ViewValidationWithRuleSetColumnWidthPreferences . . 5-122
ValidationAgent_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . . 5-123
ValidationAgentRevision_DefaultChildProperties . . . . . . . . . . . . . . . . . 5-123
ValidationAgentRevision_Folder_default_relation . . . . . . . . . . . . . . . . . 5-123
ValidationAgentRevision_ValData_default_relation . . . . . . . . . . . . . . . . 5-124
VALIDATION_APPLICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-124
ValidationMasterFormColumnPreferences . . . . . . . . . . . . . . . . . . . . . . 5-124
ValidationMasterFormColumnWidthPreferences . . . . . . . . . . . . . . . . . . 5-125
ValToolAgentRevision_DefaultChildProperties . . . . . . . . . . . . . . . . . . . 5-126

ValToolAgentRevision_Tool_default_relation . . . . . . . . . . . . . . . . . . . . . 5-126

Chapter
5 Configuration preferences
Configuration preferences modify the underlying behavior of the rich client. These
preferences should be considered and set before deploying Teamcenter throughout
the site.
Preferences are typically set using the Options dialog box, accessed from the Edit
menu. As you create/modify preferences, your current group/role determines both
user access to the preference and the precedence of its behavior when there are
multiple incidences of the same preference.
For more information, see Preference scope.
Business Modeler IDE preferences

Business rules are fundamental objects used to model business data. They govern
how objects are handled, including how they are named, what actions can be taken
on them, and so on. Creating business rules is also known as business modeling.
Business rules can be exported to and imported from other Teamcenter sites to create
consistent behavior at multiple sites. You use the Business Modeler IDE application.
Use Business Modeler IDE preferences to modify the behavior of the Business
Modeler IDE application.
AltIdentifier_require_on_create
DESCRIPTION
Determines whether an alternate identifier is required when creating an identifiable
of the type specified in this preference in a rich client session. Valid values are to
a set of Item types. If an item type is included in this preference, whenever the
item revision associated with this type is created in the rich client, an alternate is
required.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid Teamcenter
item type.
DEFAULT
VALUES
None.
SCOPE
Site preference.

Chapter 5 Configuration preferences
ASSIGNED_ITEM_ID_MODIFIABLE
DESCRIPTION
Determines whether an automatically generated item ID can be modified by users
after it has been generated.
VALID
VALUES
0 When the item ID is generated by clicking the Assign button,
the system generated item ID cannot be modified by the user.
1 When the item ID is generated by clicking the Assign button,
the system generated item ID can be modified by the user.
DEFAULT
VALUES
0
SCOPE
Site preference.
ASSIGNED_ITEM_REV_MODIFIABLE
DESCRIPTION
Determines whether an automatically generated item revision ID can be modified by
users after it has been generated.
VALID
VALUES
0 When the item revision ID is generated by clicking the Assign
button, the system generated item revision ID cannot be
modified by the user.
1 When the item revision ID is generated by clicking the Assign
button, the system generated item revision ID can be modified
by the user.
DEFAULT
VALUES
0
SCOPE
Site preference.
BMF_CUSTOM_IMPLEMENTOR_PATH
DESCRIPTION
Defines the full path to custom libraries where any custom methods for the Business
Modeler IDE framework are maintained. Alternatively, you can add the custom
libraries to a directory in your system PATH environment variable (for example,
TC_BIN).
VALID
VALUES
Accepts a single string as value. Must be a valid file location.

Configuration preferences
DEFAULT
VALUES
None.
SCOPE
Site preference.
BMIDE_ALLOW_DEPLOYMENT_FROM_CLIENT
DESCRIPTION
Determines whether Business Modeler IDE clients can deploy templates to the
server. Templates contain all the custom defined extensions managed by the
Business Modeler IDE, such as classes, business objects, business rules, LOVs,
change tools, notes, and so on.
Set this preference to False if you are running production servers so the server
cannot be inadvertently updated from a Business Modeler IDE client. Use this
setting to schedule a server down time to update the schema using the Teamcenter
Environment Manager install wizard.
Set this preference to True if you are running test servers where the number of
users are few and updates occur more frequently.
VALID
VALUES
True Allows any Business Modeler IDE client with administrative
access to update the schema, business objects, business rules,
and other Business Modeler IDE objects on the server.
False No Business Modeler IDE client can update the server
directly. Templates must be updated using the Teamcenter
Environment Manager install wizard.
DEFAULT
VALUES
True
SCOPE
Site preference.
Bypass_property_rules
DESCRIPTION
Determines whether property rules defined in Business Modeler IDE are bypassed.
VALID
VALUES
0 Property rules are not bypassed.
1 Property rules are bypassed.
DEFAULT
VALUES
0
SCOPE
Site preference.

IdentifierContextPref
DESCRIPTION
Defines the separator between the ID or revision ID and the context name in the
object_str property of an identifier.
VALID
VALUES
Accepts a single character as a value.
DEFAULT
VALUES
@
SCOPE
User preference.
IdentifierLengthPref
DESCRIPTION
Restricts the maximum length of the ID Context Name in the object_str property
of an identifier.
VALID
VALUES
Accepts a single string as a value. Must be a positive integer. The maximum value is
240. (The maximum length of the ID Context Name is 32 characters.)
DEFAULT
VALUES
7
SCOPE
User preference.
ITEM_autogenerate_id
DESCRIPTION
Determines whether an initial ID is automatically created when creating an item of
the type specified in this preference in a rich client session.
VALID
VALUES
item type.
DEFAULT
VALUES
None.
SCOPE
Site preference.

METHOD_CM_execute_before_custom
DESCRIPTION
Determines whether all canned methods are executed at a site before site custom
methods or after site custom methods.
VALID
VALUES
0 All canned methods are registered after site custom methods
are registered.
1 All canned methods are registered before site custom methods
are registered.
DEFAULT
VALUES
None.
SCOPE
Site preference.
NR_BYPASS
DESCRIPTION
Allows you to bypass naming rules, when your group is the System Administrator
group.
VALID
VALUES
On Allows system administrators to bypass naming rules.
Off Prevents system administrators from bypassing naming rules.
DEFAULT
VALUES
Off
SCOPE
All.
TC_dataset_deep_copy_rules
DESCRIPTION
Defines which dataset business objects are deep copied when using either the Save
As or Revise command on the primary dataset. A deep copy creates copies of not
only the primary dataset, but also secondary datasets. Use this preference to define
the deep copy of the primary dataset business object, the secondary dataset business
object, and the relation with which the latter is attached to the former.
VALID
VALUES
Accepts multiple strings as values. Each value must specify a valid primary dataset,
secondary dataset, and relation in the following format:
primary dataset type:relation type:secondary dataset type

primary dataset type is the dataset attached to the item revision, secondary dataset
type is the dataset business object associated with the primary dataset type, and
relation type is the relation with which the secondary dataset is associated with the
primary dataset. For example:
UGMASTER:IMAN_Rendering:DirectModel
This value specifies that when the Save As or Revise command is performed on a
UGMASTER dataset, any secondary IMAN_Rendering datasets attached with the
DirectModel relation are also copied.
This preference accepts the asterisk (*) character as a wildcard. Use the following
setting to allow deep copy of all primary datasets with any attached secondary
dataset using any relation:
*:*:*
DEFAULT
VALUES
UGMASTER:IMAN_Rendering:DirectModel
UGPART:IMAN_Rendering: DirectModel
UGALTREP:IMAN_Rendering:DirectModel
DirectModel:TC_Derived:NXDerived
SCOPE
Site preference.
Treat_Curr_Rev_As_Any_Rev
DESCRIPTION
Sets the current revision letter for a new revision in a revision naming rule. This
preference applies to CurrentRevLetter revision naming rules.
VALID
VALUES
True Allows the administrator creating a revision naming rule to type any letter
to override the current revision letter (except the letters controlled by the
TcRevisionSkipLetters LOV).
False Prevents administrators from changing the current revision letter.
DEFAULT
VALUES
True
SCOPE
Site preference.
Treat_Next_Rev_As_Any_Rev
DESCRIPTION
Sets the next revision letter for a new revision in a revision naming rule. This
preference applies to NextRevLetter revision naming rules.

VALID
VALUES
True Allows the administrator creating a revision naming rule to type any letter
to override the next revision letter (except the letters controlled by the
TcRevisionSkipLetters LOV).
False Prevents administrators from changing the next revision letter.
DEFAULT
VALUES
True
SCOPE
Site preference.
TYPE_DISPLAY_RULES_list_of_primary_types
DESCRIPTION
Defines the list of primary business objects on which display rules can be configured
in Business Modeler IDE.
For more information about business object display rules, see the Business Modeler
IDE Guide.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid primary type.
DEFAULT
VALUES
Item
Folder
Dataset
Form
MEOP
MEActivity
MEWorkArea
MEProcess
Identifier
SCOPE
Site preference.
TYPE_DISPLAY_RULES_list_types_of_subclasses
DESCRIPTION
Shows business object display rules propagated from the sub-business objects
defined in the list of business objects in the preference.
For more information about business object display rules, see the Business Modeler
IDE Guide.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid primary type.

DEFAULT
VALUES
Identifier
CAEItem
Drawing
FND_TraceLink
CCObject
StructureContext
ConfigurationContext
MEActivity
ApperanceGroup
SCOPE
Site preference.
Client interface preferences

Client interface preferences specify behaviors across multiple clients.
Confirmation_shown_on_reservation_dialogs
DESCRIPTION
Specifies whether a Don’t show confirmation dialog again check box is displayed
in the Check-Out, Cancel Check-Out, and Check-In dialog boxes in the rich client
and thin client.
VALID
VALUES
true The Don’t show confirmation dialog again check box is
displayed.
false The Don’t show confirmation dialog again check box is not
displayed.
DEFAULT
VALUES
false
SCOPE
Site preference.
Confirm_cancel_checkout_suppressed
DESCRIPTION
Specifies whether the Don’t show confirmation dialog again check box is selected in
the Cancel Check-Out dialog box in the rich client and thin client.
VALID
VALUES
true The check box is selected and cancel checkout proceeds without
confirmation.

false The check box is not selected and cancel checkout requires
confirmation.
DEFAULT
VALUES
false
SCOPE
All.
Confirm_checkin_suppressed
DESCRIPTION
the Check-In dialog box in the rich client and thin client.
VALID
VALUES
true The check box is selected and checkin proceeds without
confirmation.
false The check box is not selected and checkin requires confirmation.
DEFAULT
VALUES
false
SCOPE
All.
Confirm_checkout_suppressed
DESCRIPTION
the Check-Out dialog box in the rich client and thin client.
VALID
VALUES
true The check box is selected and checkout proceeds without
confirmation.
false The check box is not selected and checkout requires
confirmation.
DEFAULT
VALUES
false
SCOPE
All.

Form_double_click
DESCRIPTION
Specifies, in the rich client and thin client, whether a double-click action on a form
object opens the form in edit mode or view mode.
VALID
VALUES
View Double click to view objects.
Edit Double click to edit objects.
DEFAULT
VALUES
View
SCOPE
Site.
OCS_company_email_domain
DESCRIPTION
For the Teamcenter integration with Microsoft Office Communicator, specifies the
company domain name for messages, but only when the OCS_use_email_property
preference value is false.
VALID
VALUES
Any valid e-mail domain.
DEFAULT
VALUES
None.
SCOPE
Site preference.
EXAMPLE
The e-mail ID for a specific user is user_name + email_domain.
The Person object user name is john_smith and the value of the
OCS_company_email_domain preference is domain is @company_xyz.com, so the
e-mail ID is john_smith@company_xyz.com.
OCS_use_email_property
DESCRIPTION
For the Teamcenter integration with Microsoft Office Communicator, specifies
whether to use the e-mail ID from the e-mail ID field of the user Person object.
VALID
VALUES
true The e-mail ID is taken from the user Person object e-mail
data. This is the default.

false The e-mail ID consists of the user ID and the value of the
OCS_company_email_domain preference.
DEFAULT
VALUE
true
SCOPE
Site preference.
OCS_use_presence_display
DESCRIPTION
Enables the Teamcenter integration with Microsoft Office Communicator.
VALID
VALUES
true Teamcenter integration with Microsoft Office Communicator
functionality is enabled. This is the default.
false Teamcenter integration with Microsoft Office Communicator
functionality is not enabled.
DEFAULT
VALUE
true
SCOPE
Site preference.
Data management preferences

Data management determines how Teamcenter manages the data from general user
applications such as My Teamcenter and Structure Manager.
Use data management preferences to modify the behavior of these applications.
ADA_allow_license_propagation
DESCRIPTION
Enables the propagation of authorized data access (ADA) licenses from the assigned
workspace objects to their related objects. If the propagation of licenses should not
be allowed during copy actions, such as during the Save As, Revise, and Baseline
commands, clear the value of the ADA_saveas_propagated_license_types
preference.
VALID
VALUES
true Turns on the propagation of ADA licenses.
false Turns off the propagation of ADA licenses.
DEFAULT
VALUES
true

SCOPE
Site preference.
ADA_enabled
DESCRIPTION
Enables authorized data access (ADA) features. ADA is a security solution that
complements other Teamcenter security features, such as Access Manager rules
and access control lists (ACLs).
For more information about ADA, see the Security Administration Guide.
Set this preference to True to display ITAR specific attributes to the user, based on
his current group/role settings. The user can modify the setting if his group/role
grant him write privileges.
VALID
VALUES
True Enables ADA features.
False Disables ADA features.
DEFAULT
VALUES
False
SCOPE
Site preference.
ADA_saveas_propagated_license_types
DESCRIPTION
Determines which license types are propagated for ADA, based on propagation rules.
ADA is a security solution that complements other Teamcenter security features,
such as Access Manager rules and access control lists (ACLs).
VALID
VALUES
IP_License Propagates IP_License license types.
ITAR_license Propagates ITAR_License license types.
Exclude_License Propagates Exclude_License license types.
DEFAULT
VALUES
IP_License
ITAR_License
Exclude_License
SCOPE
Site preference.

AE_dataset_id_gen_by_type
DESCRIPTION
Determines whether a single ID counter is used for all dataset types, or individual
ID counters are used for each dataset type when a dataset is created and no item or
item revision is selected.
VALID
VALUES
ON Each dataset type uses its own ID counter to generate dataset
IDs.
OFF A single ID counter is used to generate all dataset IDs for all
dataset types.
DEFAULT
VALUES
ON
SCOPE
Site preference.
AE_dataset_id_postfix
DESCRIPTION
Specifies the character string used to form the suffix for the dataset ID when a
dataset is created and no item or item revision is selected.
DEFAULT
VALUES
None.
SCOPE
User preference.
AE_dataset_id_prefix
DESCRIPTION
Specifies the character string used to form the prefix for the dataset ID when a
dataset is created and no item or item revision is selected.
DEFAULT
VALUES
None.
SCOPE
User preference.
AE_dataset_id_separator
DESCRIPTION
Specifies the character used to separate the variables that form the dataset ID
(item ID and sequence number) when a parent item or item revision is selected.

For example, if the value is set to a dash (-), the selected item is UG001, and the
next available sequence number for the dataset type (within the UG001) is 3, the
dataset ID UG001-3 is generated.
DEFAULT
VALUES
A dash (-).
SCOPE
Site preference.
AE_dataset_id_usage
DESCRIPTION
Determines whether dataset identification functionality is enabled.
VALID
VALUES
ON Dataset ID and Revision ID fields are displayed as required
fields in the New Dataset and Save Dataset As dialog boxes.
Automatic generation of dataset names is disabled.
OFF Dataset ID and Revision ID fields are not displayed. Automatic
generation of dataset names is enabled.
DEFAULT
VALUES
OFF
SCOPE
Site preference.
AE_dataset_id_use_rev
DESCRIPTION
Determines whether the dataset ID is derived from the item revision when a parent
VALID
VALUES
ON Dataset ID is derived from the item revision when a parent
OFF Dataset ID is not derived from the item revision when a parent
DEFAULT
VALUES
OFF
SCOPE
Site preference.

Baseline_allowed_baserev_statuses
DESCRIPTION
Determines which status types permit a baseline to be performed on an item
revision. For example, if you set this preference with Design Approved and QA
Approved statuses, but not Released status, users could create baselines from item
revisions which had received design and QA approval status, but they could not
create baselines for released item revisions.
If no status types are defined, baselines cannot be created for any item revisions that
have been granted any status.
VALID
VALUES
Valid Teamcenter status types.
DEFAULT
VALUES
None.
SCOPE
Site preference.
Baseline_allow_edits
DESCRIPTION
Determines whether the item ID of baselined objects can be modified. Set this
preference to ON to allow users to edit the item ID of items that have been baselined.
Once the item is released, the item ID can no longer be modified.
VALID
VALUES
ON Users can edit the item ID of items that have been baselined.
Once the item is released, the item ID can no longer be
modified.
OFF Users cannot edit the item ID of baselined items.
DEFAULT
VALUES
OFF
SCOPE
Site preference.
Baseline_create_snapshot_folder
DESCRIPTION
Determines whether a Snapshot folder is created after a baseline operation is
performed. The new Snapshot folder is attached to the baseline revision.
VALID
VALUES
0 A Snapshot folder is not created after a baseline is created.

1 A Snapshot folder is created after a baseline is created.

DEFAULT
VALUES
1
SCOPE
Site preference.
baselineDryRun
DESCRIPTION
Specifies whether or not to perform a dry run of the baseline creation. A dry run
produces a report listing error messages encountered while processing a single item
revision or traversing a structure.
VALID
VALUES
0 Does not perform a dry run of the baseline creation.
1 Performs a dry run of the baseline creation.
DEFAULT
VALUES
0
SCOPE
Site preference.
Baseline_dryrun_always
DESCRIPTION
Specifies whether or not a dry run occurs before the baseline is created. A dry run
produces a report listing error messages encountered while processing a single item
revision or traversing a structure.
VALID
VALUES
0 No automatic dry run. However, users can perform a dry run
as a separate action.
1 A dry run always occur before the actual baseline is created.
DEFAULT
VALUES
1
SCOPE
Site preference.
Baseline_nxmanager_refile
DESCRIPTION
Determines whether to synchronize an assembly using the ugmanager_refile
program.

VALID
VALUES
0 Does not synchronize the assembly.
1 Synchronizes the assembly.
DEFAULT
VALUES
0
SCOPE
Site preference or user preference.
Baseline_precise_bvr
DESCRIPTION
Specifies which type of baseline, precise or imprecise, can be created.
VALID
VALUES
0 Creates a precise baseline.
1 Creates an imprecise baseline.
2 Allows only a precise baseline to be created. Setting this value
in the site preference file override any value set in a user’s
preference file.
DEFAULT
VALUES
1
SCOPE
Site preference or user preference. The site preference values 0 and 1 can be
overwritten by the settings in a user’s preference file.
Baseline_refile_not_required_item_types
DESCRIPTION
Specifies the item types for which a refile operation is not run during baseline
creation.
VALID
VALUES
Accepts multiple strings as values; each string must be a valid Teamcenter item type.
This preference is valid only when the Baseline_nxmanager_refile preference is
set to 1.
DEFAULT
VALUES
None.
SCOPE
Site preference.

Baseline_refile_required_dstypes
DESCRIPTION
Specifies the dataset types that force a refile operation to be performed for any item
types not listed in the Baseline_refile_not_required_item_types site preference.
VALID
VALUES
Accepts multiple strings as values; each string must be a valid Teamcenter dataset
type.
This preference is valid only when the Baseline_nxmanager_refile preference is
set to 1.
DEFAULT
VALUES
None.
SCOPE
Site preference.
Baseline_release_procedures
DESCRIPTION
Lists all possible baseline release processes. A baseline release process must adhere
to a quick release template. Quick release templates are process templates that
define a zero-step release procedure, allowing the baseline to become a released
object that cannot be modified.
For more information, see Creating baseline process templates in Workflow Designer
Guide.
Once the baseline process templates are created in Workflow Designer, the process
template names are listed in this preference.
VALID
VALUES
Valid Teamcenter baseline process templates.
DEFAULT
VALUES
None.
SCOPE
Site preference.
Baseline_restricted_item_types
DESCRIPTION
Restricts the item types for which a baseline can be created. Baselines cannot be
created for items of the type listed in this preference. When you baseline a structure
and a restricted item type is found in the structure, Teamcenter displays an error
message and none of the components in the structure is baselined.

VALID
VALUES
Valid Teamcenter item types.
DEFAULT
VALUES
None. The values EngChange and Document are commented out.
SCOPE
Site preference.
BOB_property_optimizations
DESCRIPTION
Defines the set of BOB property optimizations applied to object property policy.
VALID
VALUES
Accepts one or more of the following strings as valid values:
none
all
grmCaching
compPropQuery
formBatchLoading
DEFAULT
VALUES
all
SCOPE
Site preference.
CheckoutOnCreatePref
DESCRIPTION
Determines whether the system checks out item revisions automatically upon
creation. Sequences are subrevisions of an item revision that document the content
of a revision during its evolution. Checking out an item revision increments the
sequence ID.
VALID
VALUES
0 The system does not check out item revisions automatically
upon creation.
1 The system automatically checks out item revisions upon
creation.
DEFAULT
VALUES
0
SCOPE
Site preference.

IDENTIFIER_idincontext
DESCRIPTION
Determines whether identifier IDs are to be unique within the context or unique
with respect to item IDs.
VALID
VALUES
TRUE Identifier IDs are defined within the context to be unique.
FALSE Item IDs and alternate IDs are to be unique with respect to
each other.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
IP_level_list_ordering
DESCRIPTION
Defines a list of IP classification values and clearance levels that are assigned to
data objects and users for IP access evaluation. Access Manager compares these
values to determine user access rights to the object. This preference is for use with
classification functionality.
For more information about IP clearance and classification levels, see the Security
Administration Guide.
VALID
VALUES
Accepts multiple strings as values. Each string must provide valid IP classifications
for an object and the corresponding clearance levels on a user. Access Manager
compares these values to determine user access rights to the object.
String order determines classification level: the first entry is the lowest classification,
the last entry is the highest.
Maximum string length is 128 characters. Each entry may be a comma-separated
list of equal-precedence classification levels. Thus, commas cannot occur in the
classification values. For example:
IP_level_list_ordering=
secret, confidential
top-secret
DEFAULT
VALUES
secret
super-secret,top-secret
SCOPE
Site preference.

ITAR_level_list_ordering
DESCRIPTION
Defines, in order, the list of valid government classification attributes and
corresponding government clearance levels.
• Government classification is an object attribute that specifies the clearance level

required for users to access the data associated with the object. Government
classification values are typically United States Munitions List (USML) codes or
Export Control Classification Number (ECCN) codes.
• Government clearance is a user attribute that specifies the level of clearance that
users have to classified data.
Use this preference when implementing security controls with International Traffic
in Arms Regulations (ITAR) functionality.
For more information about ITAR, see the Security Administration Guide.
VALID
VALUES
Accepts multiple strings as values. Each string must provide valid IP classifications
for an object and the corresponding clearance levels on a user. Access Manager
compares these values to determine user access rights to the object.
String order determines classification level: the first entry is the lowest classification,
the last entry is the highest.
Maximum string length is 128 characters. Each entry may be a comma-separated
list of equal-precedence classification levels. Thus, commas cannot occur in the
classification values. For example:
ITAR_level_list_ordering=
secret, confidential
top-secret
DEFAULT
VALUES
secret
super-secret,top-secret
SCOPE
Site preference.
ITEM_baseline_rev_msg
DESCRIPTION
Executes site-specific program to verifies the data associated with the baseline item
revision via a verification message. You can register functions as preconditions and
postactions against this message and perform their validations.
SCOPE
Site preference.

license_warning_level
DESCRIPTION
Specifies the threshold of available Teamcenter feature licenses. Teamcenter
displays a warning message when you create or modify a user if the number equals
the value in this preference.
VALID
VALUES
Accepts a single string as value. Must be a single, positive integer more than zero.
DEFAULT
VALUES
5
SCOPE
Site preference.
SOACAD_checkout_required
DESCRIPTION
Determines whether the system requires checkout of BOM view revisions and
datasets prior to modification.
By default, at sites using SOA CAD Services, the system requires this checkout.
(The client calling createOrUpdateRelativeStructure must checkout the BOM
view revision prior to structure update by the SOA Web Service. Similarly, the client
calling createOrUpdateParts must checkout the dataset prior to structure update
by the SOA Web Service. Use this preference to bypass these default checkout
requirements.
VALID
VALUES
True The system requires the checkout of BOM view revisions and
datasets prior to modification.
False The system bypasses the checkout. (Though the system still
verifies the objects are not checked out by other users before
attempting to modify, but does not require an explicit checkout
of the objects.)
DEFAULT
VALUES
True
SCOPE
Site preference.
TC_check_object_before_create
DESCRIPTION
Determines how item revisions are saved and revised using the createObjects
method.

VALID
VALUES
ON When Save As or Revise is performed on an item revision
using the createObjects method, the system checks whether
an object of the selected type already exists. If an object of the
selected type already exists, the object is not created.
OFF When Save As or Revise is performed on an item revision
using the createObjects method, the system does not check
if an object of the selected type already exists. The object is
always created.
DEFAULT
VALUES
ON
SCOPE
All.
TCCheckoutReserveOnly
DESCRIPTION
Specifies for which business objects a restore copy is not created during checkout.
If the business object supports sequences, a new sequence is not created during
checkout. In this case, if the checkout is cancelled, the business object’s contents
are not restored to their original values. Sequences are subrevisions of a business
object that document the content of a revision during its evolution. Checking out a
business object increments the sequence ID.
Note
If any type of item revision is specified with this preference, sequences are
disabled for that item revision type. The Undo Checkout action will not
discard changes made after the item revision was checked out.
VALID
VALUES
Accepts multiple strings as values. Each string must be a business object which can
be checked in and out.
DEFAULT
VALUES
Item
Folder
SCOPE
Site preference.
TC_Dataset_Import_Exclude_Wildcard
DESCRIPTION
Specifies whether dataset types are listed in the types list if the type has only one
named reference defined and if that is associated with a *.* file format.

VALID
VALUES
TRUE A dataset type is not listed in the types list if it has only has
one named reference defined and if that is associated with a
*.* file format.
FALSE Dataset types are listed in the types list even if they have only
has one named reference defined and if that is associated with
a *.* file format.
DEFAULT
VALUES
FALSE
SCOPE
User preference.
TCDefaultKeepLimit
DESCRIPTION
Determines the number of sequences the system maintains as an item revision is
checked in and out of the database. Sequences are subrevisions of item revisions
that document the content of a revision during its evolution. Checking out an item
revision increments the sequence ID. At logon, the system automatically removes
the oldest sequence when the limit specified with this preference is reached.
VALID
VALUES
Accepts a single string as a value. Must be a single, positive integer more than zero.
DEFAULT
VALUES
3
SCOPE
Site preference.
TCDefaultKeepLimitByType
DESCRIPTION
Determines the number of sequences the system maintains for the specified business
object as it is checked in and out of the database. Sequences are subrevisions of
a business object that document the content of a revision during its evolution.
Checking out a business object increments the sequence ID. At logon, the system
automatically removes the oldest sequence when the limit specified with this
preference is reached.
VALID
VALUES
Accepts multiple string pairs as values. Each string must be a space-delineated
pair consisting of a valid business object and a positive integer more than zero.
For example:
TCDefaultKeepLimitByType=
ItemRevision 3

DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_multi_site_ada_license_user_bypass
DESCRIPTION
Determines whether replicated objects can have corresponding licenses attached
upon import, even when the importing user does not have the required permissions to
attach such a license. This preference defined licenses and determines corresponding
licenses by license ID.
ADA is a security solution that complements other Teamcenter security features,
such as Access Manager rules and access control lists (ACLs).
VALID
VALUES
true Attaches corresponding licenses, even when the importing user
does not have the required permissions to attach such a license.
false Does not attach corresponding licenses when the importing
user does not have the required permissions to attach such
a license.
DEFAULT
VALUES
false
SCOPE
Site preference.
TC_session_clearance
DESCRIPTION
Used in conjunction with NX runtime properties, this preference enables the
establishment of indirect access controls in NX using logging or menu suppression
(blocking) to control classified data that is loaded in an Teamcenter Integration
for NX session.
Note
Allowing data out of the managed environment creates a security
vulnerability, but there may be times you want to grant a user permission
to use NX menus that involve exporting data out of the environment. The
Unmanage privilege in Access Manager allows you to grant users the ability
to access these features.
For more information about configuring logging and blocking for NX, see the Security

VALID
VALUES
log Enables auditable evidence of the use of various NX commands
on classified data. This is implemented by NX internal
mechanisms.
block Suppresses sensitive menus that, if used on classified
data, could result in exporting geometric data outside the
NX/Teamcenter managed environment. The blocking feature
also includes logging of less sensitive menu actions.
DEFAULT
VALUES
None.
SCOPE
Site preference.
USER_baseline_dryrun_validator
DESCRIPTION
Accepts the file name of the file containing the UID strings all baselined item
revisions. This allows sites to run the validations on the entire structure in one pass.
In the rich client interface, the report is displayed on the screen. It can be printed out
and saved in a text file or HTML format. In the ITK interface, a log file is generated.
VALID
VALUES
A single string as a value; must be a valid file name.
DEFAULT
VALUES
None.
Dispatcher preferences
Dispatcher is an integration of the Dispatcher Server and Teamcenter. Dispatcher
enables Teamcenter users to translate CAD data files that are managed by
Teamcenter to 3D or 2D file formats.
Use Dispatcher preferences to configure and modify translation behavior.
DISPATCHER_CLIENT_INSTALLED
DESCRIPTION
Specifies if Dispatcher is installed. This preference is used by applications to find
if Dispatcher services are installed. The system sets this preference during a
Teamcenter Environment Manager installation.
VALID
VALUES
TRUE Specifies that Dispatcher Client has been installed.
FALSE Dispatcher Client not installed.

DEFAULT
VALUES
TRUE
SCOPE
Site preference.
ETS.Repeating_UI.<ProviderName>.<ServiceName>
DESCRIPTION
Specifies if the option to repeat Dispatcher tasks for a particular provider and service
should be seen in the Translation Selection dialog box.
VALID
VALUES
TRUE The option to repeat Dispatcher tasks is shown in the
Translation Selection dialog box.
FALSE The option to repeat Dispatcher tasks is not shown in the
Translation Selection dialog box.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
ETS_available
DESCRIPTION
Specifies whether Dispatcher is fully installed and configured. The system sets this
preference during a Teamcenter Environment Manager installation.
VALID
VALUES
YES Specifies that Dispatcher has been fully configured.
NO Specifies that Dispatcher has been installed.
DEFAULT
VALUES
YES
SCOPE
Site preference.
ETS_home
DESCRIPTION
Defines the Dispatcher installation directory. It is used by Dispatcher to dynamically
construct paths to translation service executable files, configuration files, and the
XML schema. The system sets this preference during a Teamcenter Environment
Manager installation.

VALID
VALUES
Accepts a single string as a value. Must be the full path to the Dispatcher
installation directory.
DEFAULT
VALUES
TC_ROOT/ets
SCOPE
Site preference.
ETS.PROVIDERS
DESCRIPTION
Specifies the translator providers.
VALID
VALUES
Accepts multiple strings as values. Must be a valid provider name.
DEFAULT
VALUES
SIEMENS
SCOPE
Site preference.
ETS.TRANSLATORS.<ProviderName>
DESCRIPTION
Specifies the translators available for a provider.
VALID
VALUES
Accepts multiple strings as values. Must be a valid translator name.
SCOPE
Site preference.
ETS.VALIDATE.<ProviderName>.<ServiceName>
DESCRIPTION
Specifies if default validation can be done on the selected Teamcenter component.
VALID
VALUES
true Specifies that default validation can be done on the selected
Teamcenter component.
false Specifies that default validation can not be done on the selected
Teamcenter component.
DEFAULT
VALUES
true

SCOPE
Site preference.
ETS_trans_rqst_referenced_dataset_types
DESCRIPTION
Specifies which CAD dataset type names may be referenced by translation requests
as primary or secondary objects. A pre-delete action is registered for each of these
dataset types to support deletion of CAD data while a translation is in process.
VALID
VALUES
Accepts multiple strings as values. Must be a valid CAD dataset type name.
DEFAULT
VALUES
IdeasPart
IdeasAssembly
IdeasDrawing
catia
CATPart
CATProduct
UGPART
UGMASTER
UGALTREP
UGSCENARIO
ProPrt
SCOPE
Site preference.
ETS_update_state_delay
DESCRIPTION
Specifies the delay time in seconds after which a dispatcher request object can be
updated.
When there are multiple dispatcher clients in a Dispatcher installation, multiple
dispatcher clients can update the state of the same dispatcher request object. The
delay time makes sure that only one dispatcher client updates the dispatcher
request object.
Note
If you set a very high delay time, the performance of the dispatcher request
may be affected. Siemens PLM Software recommends that the delay time
should not be greater than 5 seconds.
VALID
VALUES
Must be a single positive integer.

DEFAULT
VALUES
0
SCOPE
Site preference.
ETS_released_status_type_names
DESCRIPTION
Specifies which released status types are copied from an item revision to a
visualization dataset. The status type names are used to filter the setting of the
released date and released status for visualization datasets. When an item revision’s
released status type matches a status type defined in this preference, the released
date and released status are copied to the visualization dataset.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid status type name.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ETS_trans_rqst_user_exit_states
DESCRIPTION
Specifies which translation request states activate the Dispatcher translation
request state transition user exit.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Dispatcher state.
DEFAULT
VALUES
COMPLETE
SCOPE
Site preference.
TC_register_internal_service_modules
DESCRIPTION
Registers all internal service modules. When Dispatcher is installed during
a Teamcenter Environment Manager installation, the system checks for this
preference. If it exists, the value etsus is added as a value. If it does not exist, the
preference is automatically added to the database, and the value added.

Note
Use only a single instance of this preference in the database.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid internal service
module.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IDEAS_translation_service_name
DESCRIPTION
Specifies the Dispatcher Server provider and service names of the translator to be
used for logon and on demand I-deas to JT translations.
VALID
VALUES
This preference value is specified using the provider and service attribute values
from the corresponding translator element in the Dispatcher Server module
configuration translator.xml file. Values are set in the following format:
provider name.service name
For example: UGS.ideastojt
Note
If this preference is not specified, requests for I-deas to JT translations are
ignored.
DEFAULT
VALUES
UGS.ideastojt
SCOPE
Site preference.
IDEAS_import_translation_service_name
DESCRIPTION
used for I-deas to JT import translations.
VALID
VALUES

provider name.import service name

For example: UGS.ideastojt_imp
Note
If this preference is not specified, requests for I-deas to JT translations are
ignored.
DEFAULT
VALUES
UGS.ideastojt_imp
SCOPE
Site preference.
IDEAS_translation_dataset_type_names
DESCRIPTION
Specifies which I-deas dataset type names are translated.
VALID
VALUES
Accepts multiple strings as values. Each string must be one of the following values:
IdeasPart
IdeasAssembly
IdeasDrawing
DEFAULT
VALUES
IdeasPart
IdeasAssembly
IdeasDrawing
SCOPE
Site preference.
UGSideastojt_IdeasAssembly_ets_nr_types
DESCRIPTION
Specifies the I-deas assembly dataset named references necessary for translation.
All named reference types specified by this preference must exist for a dataset of
this type to be translated. If no named reference types are specified, no named
reference type validation is performed.
VALID
VALUES
Accepts multiple strings as values. Each string must be an existing named reference
type.
DEFAULT
VALUES
IdeasGuids
IdeasPrivateData
IdeasAssembly

SCOPE
Site preference.
UGSideastojt_IdeasDrawing_ets_nr_types
DESCRIPTION
Specifies the I-deas drawing dataset named references necessary for translation. All
named reference types specified by this preference must exist for a dataset of this
type to be translated. If no named reference types are specified, no named reference
type validation is performed.
VALID
VALUES
type.
DEFAULT
VALUES
IdeasGuids
IdeasPrivateData
IdeasDrawing
SCOPE
Site preference.
UGSideastojt_IdeasPart_ets_nr_types
DESCRIPTION
Specifies the I-deas part dataset named references necessary for translation. All
VALID
VALUES
type.
DEFAULT
VALUES
IdeasGuids
IdeasPrivateData
IdeasPart
SCOPE
Site preference.
IDEAS_import_from_tdm_gen_vis_data_display
DESCRIPTION
Specifies whether the I-deas Data Sharing Import dialog box displays generate
visualization data information.

VALID
VALUES
YES Allows a data-sharing user to view generate visualization data
information.
NO Does not allow a data-sharing user to view generate
visualization data information.
DEFAULT
VALUES
YES
SCOPE
Site preference.
IDEAS_import_from_tdm_default_gen_vis_data_priority
DESCRIPTION
Specifies the default scheduler priority used for I-deas data sharing import
translations.
VALID
VALUES
0 Generates no visualization data on import.
1 Dispatcher Server scheduler priority for importing
visualization data is low.
visualization data is medium.
visualization data is high.
DEFAULT
VALUES
2
SCOPE
Site preference.
IDEAS_import_from_tdm_gen_vis_data_input
DESCRIPTION
Determines whether input is allowed in the I-deas Data Sharing Import dialog box.
VALID
VALUES
YES Allows input in the I-deas Data Sharing Import dialog box.
NO Does not allow input in the I-deas Data Sharing Import dialog
box.
DEFAULT
VALUES
NO

SCOPE
Site preference.
IDEAS_import_from_tdm_options_default_gen_vis_data_priority
DESCRIPTION
Specifies the initial I-deas Data Sharing Import Options dialog box scheduler priority.
VALID
VALUES
0 Generates no translation.
1 I-deas Data Sharing Import Options dialog box scheduler
priority is low.
priority is medium.
priority is high.
DEFAULT
VALUES
2
SCOPE
Site preference.
IDEAS_check_in_generate_vis_data_priority
DESCRIPTION
Specifies the generate visualization data scheduler priority for checked-in and
modified I-deas parts, assemblies, and drawings.
Note
Coordinate the setting of this preference with the setting of NX I-deas create
part and assembly .JT on check in preferences.
VALID
VALUES
1 Dispatcher Server scheduler priority for checked-in and
modified I-deas parts, assemblies, and drawings is low.
modified I-deas parts, assemblies, and drawings is medium.
modified I-deas parts, assemblies, and drawings is high.
DEFAULT
VALUES
2

SCOPE
Site preference.
IDEAS_on_demand_generate_vis_data_priority
DESCRIPTION
Determines the generate visualization data scheduler priority for on demand
translations of I-deas parts and assemblies.
VALID
VALUES
A nonzero value is required to display the I-deas to JT command on the Translate
menu.
1 Dispatcher Server scheduler priority for on demand
translations of I-deas parts and assemblies is low.
translations of I-deas parts and assemblies is medium.
translations of I-deas parts and assemblies is high.
DEFAULT
VALUES
3
SCOPE
Site preference.
IMAN_capture_relation_primary
DESCRIPTION
Defines primary relation objects for IMAN_capture relations. Must include
IdeasDrawing for Dispatcher to support I-deas drawings.
Note
VALID
VALUES
Accepts multiple strings as values. Each value must be a valid Teamcenter object.
DEFAULT
VALUES
None.
SCOPE
Site preference.

CATIA_translation_service_name
DESCRIPTION
used for CATIA v5 check in/save and on demand translations.
VALID
VALUES
For example: THEOREM.catiatojt
Note
If this preference is not specified, requests for CATIA v5 check in/save and
on demand translations are ignored.
DEFAULT
VALUES
THEOREM.catiatojt
SCOPE
Site preference.
CATIA_check_in_generate_vis_data_priority
DESCRIPTION
Determines the generate visualization data scheduler priority for checked-in CATIA
v5 parts and assemblies.
VALID
VALUES
1 Dispatcher Server scheduler priority for checked-in CATIA v5
parts and assemblies is low.
parts and assemblies is medium.
parts and assemblies is high.
DEFAULT
VALUES
2
SCOPE
Site preference.

CATIA_checkin_generate_vis_data_priority
DESCRIPTION
Determines the CATIA v5 to JT scheduler priority for check in and/or save
translations.
VALID
VALUES
1 Priority for checked-in/save CATIA v5 translations is low.
2 Priority for checked-in/save CATIA v5 translations is medium.
3 Priority for checked-in/save CATIA v5 translations is high.
DEFAULT
VALUES
2
SCOPE
Site preference.
CATIA_on_demand_generate_vis_data_priority
DESCRIPTION
Specifies the generate visualization data scheduler priority for on demand
translations of CATIA v5 parts and assemblies.
VALID
VALUES
A nonzero value is required to display the CATIA to JT command on the Translate
menu.
translations of CATIA v5 parts and assemblies is low.
translations of CATIA v5 parts and assemblies is medium.
translations of CATIA v5 parts and assemblies is high.
DEFAULT
VALUES
3
SCOPE
Site preference.

COMMONcatiatojt_CATPart_ets_nr_types
DESCRIPTION
Specifies the CATIA v5 CATPart dataset named references necessary for
translation. All named reference types specified by this preference must exist for a
dataset of this type to be translated. If no named reference types are specified, no
named reference type validation is performed.
VALID
VALUES
type.
DEFAULT
VALUES
catpart
SCOPE
Site preference.
COMMONcatiatojt_CATProduct_ets_nr_types
DESCRIPTION
Specifies the CATIA v5 CATProduct dataset named references necessary for
VALID
VALUES
type.
DEFAULT
VALUES
catproduct
SCOPE
Site preference.
COMMONcatiatojt_ets_ds_types
DESCRIPTION
Specifies the dataset type names of the CATIA v5 datasets which can be translated
by the CATIA v5 to JT translator. If no dataset types are specified, no named
reference type validation is performed. Additional named reference type validation
can be configured for the datasets specified by this preference value.
VALID
VALUES
Accepts multiple strings as values. Each string must be an existing dataset type.
DEFAULT
VALUES
CATProduct

CATPart
SCOPE
Site preference.
CATIA_work_dir
DESCRIPTION
Defines the NX CATIA Manager working directory.
VALID
VALUES
Accepts a single string as a value. Must be the same working directory specified
during NX CATIA Manager installation.
DEFAULT
VALUES
None.
SCOPE
Site preference.
CATIA_V4_translation_service_name
DESCRIPTION
used for CATIA v4 check in and on demand translations.
VALID
VALUES
For example: UGS.catiav4tojt
Note
If this preference is not specified, requests for CATIA v4 check in and on
demand translations are ignored.
DEFAULT
VALUES
UGS.catiav4tojt
SCOPE
Site preference.

CATIA_V4_check_in_generate_vis_data_priority
DESCRIPTION
Specifies the generate visualization data scheduler priority for checked-in/saved
CATIA v4 parts and assemblies.
VALID
VALUES

parts and assemblies is low.

parts and assemblies is medium.

parts and assemblies is high.
DEFAULT
VALUES
2
SCOPE
Site preference.
CATIA_V4_on_demand_generate_vis_data_priority
DESCRIPTION
translations of CATIA v4 parts.
VALID
VALUES
A nonzero value is required to display the CATIA to JT command on the Translate
menu.

translations of CATIA v4 parts is low.

translations of CATIA v4 parts is medium.

translations of CATIA v4 parts is high.
DEFAULT
VALUES
3
SCOPE
Site preference.

COMMONcatiatojt_catia_ets_nr_types
DESCRIPTION
Specifies the CATIA v4 dataset named references necessary for translation. All
VALID
VALUES
type.
DEFAULT
VALUES
catia
SCOPE
Site preference.
COMMONcatiatojtV4_ets_ds_types
DESCRIPTION
Specifies the dataset type names of the CATIA v4 datasets which can be translated
by the CATIA v4 to JT translator. If no dataset types are specified, no named
reference type validation is performed. Additional named reference type validation
VALID
VALUES
DEFAULT
VALUES
catia
SCOPE
Site preference.
NX_translation_service_name
DESCRIPTION
used for check in and on demand translation of NX datasets.
VALID
VALUES
For example: UGS.ugtopvdirect

Note
If this preference is not specified, requests for check in and on demand
translation of NX datasets are ignored.
DEFAULT
VALUES
UGS.ugtopvdirect
SCOPE
Site preference.
NX_tocgm_translation_service_name
DESCRIPTION
used for check in and on demand CGM translations of NX datasets.
VALID
VALUES
For example: UGS.ugtocgmdirect
Note
If this preference is not specified, requests for check in and on demand
translation of CGM translations of NX datasets are ignored.
DEFAULT
VALUES
UGS.ugtocgmdirect
SCOPE
Site preference.
NX_on_demand_generate_vis_data_priority
DESCRIPTION
translations of NX parts.
VALID
VALUES
A nonzero value is required to display the UGNX to JT command on the Translate
menu.
translations of NX parts is low.


translations of NX parts is medium.
translations of NX parts is high.
DEFAULT
VALUES
3
SCOPE
Site preference.
NX_tocgm_on_demand_generate_vis_data_priority
DESCRIPTION
translations of NX part drawings.
VALID
VALUES
A nonzero value is required to display the UGNX to CGM command on the Translate
menu.
translations of NX part drawings is low.
translations of NX part drawings is medium.
translations of NX part drawings is high.
DEFAULT
VALUES
3
SCOPE
Site preference.
UGSnxtocgmdirect_UGALTREP_ets_nr_types
DESCRIPTION
Specifies the NX UGALTREP dataset named references necessary for translation.
VALID
VALUES
type.
DEFAULT
VALUES
None.

SCOPE
Site preference.
UGSnxtocgmdirect_UGMASTER_ets_nr_types
DESCRIPTION
Specifies the NX UGMASTER dataset named references necessary for translation.
VALID
VALUES
type.
DEFAULT
VALUES
UGPART
SCOPE
Site preference.
UGSnxtocgmdirect_UGPART_ets_nr_types
DESCRIPTION
Specifies the NX UGPART dataset named references necessary for translation. All
VALID
VALUES
type.
DEFAULT
VALUES
UGPART
SCOPE
Site preference.
UGSnxtocgmdirect_UGSCENARIO_ets_nr_types
DESCRIPTION
Specifies the NX UGSCENARIO dataset named references necessary for

VALID
VALUES
type.
DEFAULT
VALUES
None.
SCOPE
Site preference.
UGSnxtocgmdirect_ets_ds_types
DESCRIPTION
Specifies the dataset type names of the NX datasets which can be translated by
the NX to CGM translator. If no dataset types are specified, no named reference
type validation is performed. Additional named reference type validation can be
configured for the datasets specified by this preference value.
VALID
VALUES
DEFAULT
VALUES
UGMASTER
UGPART
UGALTREP
UGSCENARIO
SCOPE
Site preference.
UGSnxtopvdirect_UGALTREP_ets_nr_types
DESCRIPTION
Specifies the NX UGALTREP dataset named references necessary for translation.
VALID
VALUES
type.
DEFAULT
VALUES
None.
SCOPE
Site preference.

UGSnxtopvdirect_UGMASTER_ets_nr_types
DESCRIPTION
Specifies the NX UGMASTER dataset named references necessary for translation.
VALID
VALUES
type.
DEFAULT
VALUES
UGPART
SCOPE
Site preference.
UGSnxtopvdirect_UGPART_ets_nr_types
DESCRIPTION
Specifies the NX UGPART dataset named references necessary for translation. All
VALID
VALUES
type.
DEFAULT
VALUES
UGPART
SCOPE
Site preference.
UGSnxtopvdirect_ets_ds_types
DESCRIPTION
Specifies the dataset type names of the NX datasets which can be translated by
the NX to JT translator. If no dataset types are specified, no named reference
type validation is performed. Additional named reference type validation can be
configured for the datasets specified by this preference value.
VALID
VALUES
DEFAULT
VALUES
UGMASTER

UGPART
UGALTREP
SCOPE
Site preference.
IMAN_Drawing_relation_primary
DESCRIPTION
Defines primary relation objects for IMAN_drawing relations. Must include Item,
ItemRevision and Dataset for Dispatcher to support NX drawings.
Note
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
UGMASTER_DefaultChildProperties
DESCRIPTION
Defines children of UGMASTER datasets. Must include IMAN_drawing for
Dispatcher to support NX parts.
Note
VALID
VALUES
Accepts multiple strings as values. Each value must be a valid Teamcenter relation
object.
DEFAULT
VALUES
None.
SCOPE
Site preference.
UGPART_DefaultChildProperties
DESCRIPTION
Defines children of UGPART datasets. Must include IMAN_drawing for Dispatcher
to support NX parts.

Note
VALID
VALUES
Accepts multiple strings as values. Each value must be a valid Teamcenter relation
object.
DEFAULT
VALUES
None.
SCOPE
Site preference.
PROE_translation_service_name
DESCRIPTION
used for check in and on demand Pro/ENGINEER to JT translations.
VALID
VALUES
For example: UGS.proetojt
Note
If this preference is not specified, requests for check in and on demand ProE to
JT translations will be ignored.
DEFAULT
VALUES
UGS.proetojt
SCOPE
Site preference.
PROE_on_demand_generate_vis_data_priority
DESCRIPTION
translations of Pro/ENGINEER parts.
VALID
VALUES
A nonzero value is required to display the ProE to JT command on the Translate
menu.


translations of Pro/ENGINEER parts is low.
translations of Pro/ENGINEER parts is medium.
translations of Pro/ENGINEER parts is high.
DEFAULT
VALUES
3
SCOPE
Site preference.
UGSproetojt_ProPrt_ets_nr_types
DESCRIPTION
Specifies the Pro/ENGINEER ProPrt dataset named references necessary for
VALID
VALUES
type.
DEFAULT
VALUES
PrtFile
SCOPE
Site preference.
UGSproetojt_ets_ds_types
DESCRIPTION
Specifies the dataset type names of the Pro/ENGINEER datasets which can be
translated by the Pro/ENGINEER to JT translator. If no dataset types are specified,
no dataset type validation is performed. Additional named reference type validation
VALID
VALUES
Accepts multiple strings as values. Each string must be an existing Pro/ENGINEER
dataset type.
DEFAULT
VALUES
PrtFile
SCOPE
Site preference.

VIS_simpgen_admin_group
DESCRIPTION
Lists the name of the user group that is authorized to run the Simpgen translator
from the RAC Translation menu.
VALID
VALUES
The name of a Teamcenter group.
DEFAULT
VALUES
SimpGenAdmin
SCOPE
Site preference.
Full-text search preferences

Full-text search preferences specify behavior of the Autonomy full-text search engine.
search_automatic_wildcard
DESCRIPTION
To enhance local metadata searches, automatically adds the asterisk (*) character
as a prefix, suffix, or both for search criteria for all string attributes. This feature
is available in all Teamcenter clients.
VALID
VALUES
0 Search criteria are not altered.
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.
DEFAULT
VALUES
0
SCOPE
Site preference.

TC_fts_aci_port
DESCRIPTION
Specifies the Autonomy Content Infrastructure (ACI) action port number. This port
is used to send action query commands to the Autonomy IDOL server.
VALID
VALUES
Accepts a single string as a value. Must be the number of the port used by the ACI.
This preference setting should be the same as the Port setting in the Autonomy
IDOL server’s configuration file.
DEFAULT
VALUES
Teamcenter installation provides an opportunity to install the Autonomy search
engine. If you choose this option, this preference is automatically set to 9000.
SCOPE
Site preference.
TC_fts_database_name
DESCRIPTION
Specifies the name of the Autonomy database in which Teamcenter database objects
are indexed.
This preference works in conjunction with the following preferences. Each preference
must be defined correctly to use the Autonomy search engine for indexing and
searching:
TC_fts_engine
TC_fts_host
TC_fts_aci_port
TC_fts_index_port
TC_fts_fsf_host
TC_fts_fsf_port
VALID
VALUES
Accepts a single string as a value. Must be a valid database name, in which the
Teamcenter database objects are indexed.
DEFAULT
VALUES
engine. If you choose this option, this preference is automatically set to the
user-defined database.
Additionally, the database setting can be reset in the Autonomy server configuration
file.
SCOPE
Site preference.

TC_fts_default_language_type
DESCRIPTION
Specifies the default language type used by Autonomy for indexing and searching.
VALID
VALUES
Accepts a single string as a value. Must be one of the following supported languages:
English
French
German
Chinese
Japanese
Korean
DEFAULT
VALUES
engine. If you choose this option, this preference is automatically set to the
user-selected language. This preference setting should be the same as the
DefaultLanguageType setting in the Autonomy server configuration file.
SCOPE
Site preference.
TC_fts_engine
DESCRIPTION
Specifies the search engine used by Teamcenter’s full text search (FTS) framework.
Search engines are used for searching within text documents such as MS Word
documents, PDF files, and HTML files. An opportunity to install the Autonomy
search engine (includes the IDOL server and the File System Fetch connector)
is provided during installation using the Teamcenter Environment Manager.
Alternatively, you can define a different plug-and-play search engine using this
preference.
This preference works in conjunction with the following preferences. Each preference
must be defined correctly to use the Autonomy search engine for indexing and
searching:
TC_fts_host
TC_fts_aci_port
TC_fts_index_port
TC_fts_fsf_host
TC_fts_fsf_port
TC_fts_database_name
VALID
VALUES
Accepts a single string as a value.

DEFAULT
VALUES
engine. If you choose this option during the installation, the value for this preference
is automatically set to Autonomy.
SCOPE
Site preference.
TC_fts_fsf_host
DESCRIPTION
Specifies the IP address or the name of the host machine on which Autonomy File
System Fetch is running. The host and port specified by the TC_fts_fsf_port
preference are used by the FTS to send the import command to File System Fetch,
which imports and indexes documents on the IDOL server.
VALID
VALUES
Accepts a single string as a value. Must be a valid IP address or host name.
DEFAULT
VALUES
engine. If you choose this option, the IP address of the machine on which to run
Autonomy File System Fetch is user-defined during installation. In this case, the IP
address for this preference is automatically abstracted from the installation settings.
SCOPE
Site preference.
TC_fts_fsf_port
DESCRIPTION
Specifies the port number on which Autonomy File System Fetch is listening. The
port and the host specified by the TC_fts_fsf_host preference are used by the FTS
framework to send the import command to File System Fetch, which imports and
indexes documents on the IDOL server.
VALID
VALUES
Accepts a single string as a value. Must be a positive integer.
DEFAULT
VALUES
SCOPE
Site preference.

TC_fts_host
DESCRIPTION
Specifies the IP address of the host machine running the Autonomy server.
If the Teamcenter server and the Autonomy server are installed on two different
machines, set the TC_TMP_DIR environment variable with the UNC path of the
Teamcenter server machine to a directory which can be accessed by the Autonomy
server. For example:
%TC_TMP_DIR%=\\ahi3w099\temp
In this situation, the Teamcenter server first creates temporary indexing files in the
$TC_TMP_DIR directory, then the Autonomy server reads the files for indexing.
Note
The TC_TMP_DIR environment variable is located in the tc_profilevars.bat
file in the $TC_DATA directory, or in the start_TcServer1.bat file in the
$TC_ROOT directory.
VALID
VALUES
Accepts a single string as a value. Must be the valid IP address of the host machine
running the Autonomy server.
DEFAULT
VALUES
engine. If you choose this option, the IP address of the machine on which to run the
Autonomy server (IDOL) is user-defined during installation. In this case, the IP
address for this preference is automatically abstracted from the installation settings.
SCOPE
Site preference.
TC_fts_index_port
DESCRIPTION
Specifies the index port number. This port is used to index documents for the
Autonomy IDOL server.
VALID
VALUES
Accepts a single string as a value. Must be the number of the Autonomy IDOL
server’s index port. This preference setting should be the same as the IndexPort
setting in the Autonomy IDOL server’s configuration file.
DEFAULT
VALUES
SCOPE
Site preference.

TC_fts_index_retries
DESCRIPTION
Specifies the number of times a connection with the Autonomy server is attempted
before exiting. When the number of attempts is exceeded, the system displays the
following error: aciObjectExecute failed with the message: Cannot connect.
If this message displays during full text search indexing or searching, you can
increase the value of this preference and retry.
VALID
VALUES
Accepts a single string as a value. Must be single positive integer.
DEFAULT
VALUES
2
SCOPE
Site preference.
TC_fts_index_timeout
DESCRIPTION
Specifies how long, in milliseconds, the client waits for data from the server before
closing the connection. When the length of time is exceeded, the system displays the
following error: aciObjectExecute failed with the message: Cannot connect.
If this message displays during full text search indexing or searching, you can
increase the value of this preference and retry.
VALID
VALUES
Accepts a single string as a value. Must be single positive integer.
DEFAULT
VALUES
90000
SCOPE
Site preference.
TC_fts_indexed_types
DESCRIPTION
Specifies types whose objects can be indexed. The FTS framework uses this
preference to determine if a given object should be indexed. If this preference is not
defined, the FTS framework does not filter out any objects.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid object type name.
DEFAULT
VALUES
Text
MSWordX

MSExcelX
MSPowerPointX
MSWord
MSExcel
MSPowerPoint
SCOPE
Site preference.
TC_fts_indexing_wait_timeout
DESCRIPTION
Specifies the amount of time, in seconds, the FTS search engine is allowed to
index one object. Because this preference is used during real-time indexing for the
indexing of work space objects, its setting significantly affects system performance.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_fts_max_results
DESCRIPTION
Specifies the number of query results returned by the full text search engine. Use
this preference to avoid potential performance overhead on the Autonomy server.
VALID
VALUES
A single positive integer.
DEFAULT
VALUES
300
SCOPE
Site preference.
TC_fts_query_port
DESCRIPTION
Specifies the query port number. This port is used to query Autonomy IDOL server
content.
VALID
VALUES

DEFAULT
VALUES
engine. If you choose this option, this preference is automatically set to 9000 (the
same value as the TC_fts_aci_port preference).
SCOPE
Site preference.
TC_fts_service_port
DESCRIPTION
Specifies the service port number. This port is used to query the Autonomy IDOL
server service.
VALID
VALUES
DEFAULT
VALUES
SCOPE
Site preference.
TC_fts_real_time_indexing
DESCRIPTION
Specifies whether object indices are created or updated into the FTS index database
in real time, when the objects are created, modified, or deleted.
VALID
VALUES
TRUE Performs a real-time index on the objects listed in the
TC_fts_indexed_types preference.
FALSE Does not perform a real-time index on the objects listed in the
TC_fts_indexed_types preference.
DEFAULT
VALUES
None.
SCOPE
Site preference.
<TypeName>_indexed_properties
DESCRIPTION
Specifies the properties to be indexed to the Autonomy database for a particular
object type. This preference supports type (hierarchy) inheritance.

VALID
VALUES
Accepts multiple strings as values. Each string must be a combination of a valid type
name and one or more valid property names.
The following example specifies which properties are indexed for Teamcenter forms.
Form_indexed_properties=
object_name
object_desc
The following example specifies which properties are indexed for Teamcenter folders.
Folder_indexed_properties=
object_name
object_desc
The following example specifies which properties are indexed for Adobe files.
Adobe_indexed_properties=
property1
property2
property3
DEFAULT
VALUES
engine. If you choose this option, Dataset_indexed_properties is automatically
created and set to the following values:
object_name
object_type
object_desc
owning_user
owning_group
creation_date
last_mod_date
date_released
release_status_list
SCOPE
Site preference.
Localization preferences
Localization preferences determine how text is displayed in different languages
within Teamcenter client user interfaces.
For more information about localization, see the Localization Guide.
TC_language_data_entry
DESCRIPTION
Defines which locales users may use for data entry. Limit the values of this
preference to locales supported by your database encoding. When this preference is
set, the system displays the following message after a user enters the appropriate
credentials:

You must limit data input using locales L10N_a and L10N_b.
L10N_a and L10N_b are values set for this preference.

The system implements this preference as follows:
• If the requested locale does not exist on the Teamcenter server, the connection is
served in English.
• If the requested locale does not belong to the database encoding, and the
Teamcenter server is running on a UTF-8 system (for example, Linux), the
connection is served with this locale.
• If the requested locale does not belong to the database encoding, and the
Teamcenter server is running on a non-UTF-8 system, the connection is served
in English.
• If none of these situations apply, the requested locale is served.
VALID
VALUES
Accepts multiple strings as values. Each string must be one of the following country
codes indicating the desired locale:
cs_CZ
Czech
de_DE
German
en_US
English
es_ES
Spanish
fr_FR
French
it_IT
Italian
ja_JP
Japanese
ko_KR
Korean
ru_RU
Russian
zh_CN
Chinese (as spoken in China)
zh_TW
Chinese (as spoken in Taiwan)

DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_language_default
DESCRIPTION
Defines the default language for the Teamcenter server process.
Teamcenter allows users to select the locale on their clients, regardless of the
locale used by the Teamcenter server pool manager. The only constraints are that
requested locales are properly installed on the server side (which may not be true for
customized locales) and that the server-side system can cope with the locale encoding.
Use this preference to define what the default locale should be in the event that no
locale is passed, for example, no locale is passed from services-oriented architecture
(SOA) or the thin client. The value defines the internal Teamcenter representation
associated with a given language.
VALID
VALUES
Accepts a single string as value. The string must be one of the following country
codes indicating the desired locale or the name of the directory where your
Teamcenter server customized localization files are located:
cs_CZ
Czech
de_DE
German
en_US
English
es_ES
Spanish
fr_FR
French
it_IT
Italian
ja_JP
Japanese
ko_KR
Korean
ru_RU
Russian

zh_CN
zh_TW
DEFAULT
VALUES
en_US
SCOPE
Site preference.
TC_language_localization_display
DESCRIPTION
Displays translation information as read-only for properties that are localizable.
VALID
VALUES
true Displays translation information.
false Hides translation information.
DEFAULT
VALUES
false
SCOPE
Site preference.
TC_language_localized_property_value_display
DESCRIPTION
Specifies the list of languages for displaying localized property values.
VALID
VALUES
Accepts codes representing languages, including the following codes that are
delivered with Teamcenter:
cs_CZ
Czech
de_DE
German
en_US
English
es_ES
Spanish
fr_FR
French

it_IT
Italian
ja_JP
Japanese
ko_KR
Korean
ru_RU
Russian
zh_CN
zh_TW
DEFAULT
VALUES
None.
SCOPE
User preference.
NOTES
The values may contain more than one locale, which is organized as a list from the
high to low priority. If the property value does not exist in the first locale on the list,
the value is displayed with the second locale, and so on.
RESTRICTIONS
The value entered should be a valid value as defined by the Java standard. It should
also be one of the values defined in TC_language_data_entry, if this preference
is set.
TC_language_localized_property_value_entry
DESCRIPTION
Specifies the data entry locale (master locale) of the logged-on user. The master
locale is the one used by the user to create/edit data in a localized property.
VALID
VALUES
cs_CZ Czech
de_DE German
en_US English
es_ES Spanish
fr_FR French
it_IT Italian
ja_JP Japanese

ko_KR Korean
ru_RU Russian
zh_CN Chinese (as spoken in China)
zh_TW Chinese (as spoken in Taiwan)
DEFAULT
VALUES
None.
SCOPE
User preference
NOTES
If set, all the data entered by the user is now in this language. The system does not
make any determination of whether the data entered by the user actually matches
the character set as defined by this language.
RESTRICTIONS
The value entered for this should be a valid value as defined by the Java standard.
It should also be one of the values defined in TC_language_data_entry, if this
preference is set.
TC_language_search
DESCRIPTION
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.
Caution
If localization for Classification is enabled, selecting the search language
in the attribute dictionary in the Classification Administration application
changes the value of the TC_language_search preference interactively for
all Teamcenter applications.
VALID
VALUES
cs_CZ
Czech
de_DE
German
en_US
English
es_ES
Spanish
fr_FR
French

it_IT
Italian
ja_JP
Japanese
ko_KR
Korean
ru_RU
Russian
zh_CN
zh_TW
DEFAULT
VALUES
None.
SCOPE
User preference.
Warning
Do not change the scope of this preference. The system selectively applies this
preference for a variety of applications, and changing the scope could have
unintended and undesirable consequences.
Mail gateway preferences

These preferences are used to configure and control how Teamcenter mail interfaces
with other common mail gateways.
Folder_mail_properties
DESCRIPTION
Lists all properties of an object folder that can be sent via Teamcenter mail.
VALID
VALUES
One or more strings as values; each string must be a valid object folder property
name.
DEFAULT
VALUES
object_name
owning_user
object_desc
SCOPE
All.

Mail_server_charset
DESCRIPTION
Specifies the Teamcenter mail server character set that is used to send mail.
DEFAULT
VALUES
ISO-8859-1
SCOPE
All.
Mail_server_name
DESCRIPTION
Sets the name of the mail gateway server. The server should be a machine running a
sendmail daemon.
This preference must be set to send system e-mail. The placeholder default setting
may return errors if the send command is used.
VALID
VALUES
Text server name or an numeric IP address.
DEFAULT
VALUES
your mail server machine
SCOPE
Site preference.
Mail_server_port
DESCRIPTION
Specifies the port number called by the mail gateway server.
This preference must be used in conjunction with the Mail_server_name
preference.
VALID
VALUES
Accepts a single string as a value. Must be a valid port number.
DEFAULT
VALUES
25
SCOPE
Site preference.

Mail_OSMail_activated
DESCRIPTION
Determines whether operating system e-mail can be set from Teamcenter. When
enabled, users can send OS e-mail by clicking Send to→Envelope.
VALID
VALUES
true OS e-mail can be sent from Teamcenter.
false OS e-mail cannot be sent from Teamcenter. Any value set for
the Mail_server_name preference is ignored.
DEFAULT
VALUES
true
SCOPE
Site preference.
TC_use_tc_alias_in_pa8
DESCRIPTION
Allows the use of e-mail addresses longer than 32 characters. If set to ON, the
user’s e-mail attribute is assumed to be an address list. The name of this address
list must be less than 32 characters, but the e-mail addresses of list members may
exceed 32 characters.
VALID
VALUES
ON Allows e-mail addresses of address list members to exceed 32
characters.
OFF Does not allow e-mail addresses to exceed 32 characters.
DEFAULT
VALUES
OFF
SCOPE
Site preference.
TC_mail_interval
DESCRIPTION
Determines how often Teamcenter checks for new system mail. This can also be set
in the rich client interface by choosing Edit→Options→Mail.
VALID
VALUES
DEFAULT
VALUES
10

SCOPE
User preference.
NX Integration preferences
Use the Teamcenter Integration for NX to create, store, and access your site’s NX
data within the Teamcenter database. When NX is used in Teamcenter Integration
for NX mode, Teamcenter runs simultaneously as a separate process. The integration
combines the power of NX in modeling and generating data from geometric shapes,
with the power of Teamcenter in storing and retrieving data in a controlled fashion.
Before running the integration, you must configure customer defaults in NX, and
Teamcenter Integration for NX preferences in Teamcenter.
For more information about setting customer defaults, see the Teamcenter
Integration for NX Guide, delivered with NX.
Use NX Integration preferences to modify the behavior and display of this interface.
These preferences are set in the following preference files:
• tc_preferences.xml
• .ugii_env
• .tc_ugman_env
• ug_english.def
Preferences set in the .tc_preferences.xml file

Preferences set in the tc_preferences.xml preference file control the way
Teamcenter displays and stores NX assembly and part data.
API_ugpart_attr_titles
DESCRIPTION
Lists NX attributes to synchronize with Teamcenter. This preference requires the
TC_NX_UPDATE_ATTRIBUTES preference to be set.
Note
This preference is enabled only when the newer method of
NX/Teamcenter attribute synchronization is disabled by setting the UGII
_UGMGR_ATTR_SYNC NX environment variable to OLD.
VALID
VALUES
One or more strings as values; each string must be a valid NX attribute name.
DEFAULT
VALUES
TITLE
CREATOR
PART_TYPE
PART_NO MODEL
MATERIAL
ASSEMB_NO

WEIGHT
TASK_NO
SCOPE
Site preference.
DATASET_saveas_allow_duplicates
DESCRIPTION
Affects the behavior of the Teamcenter Integration for NX SaveAs
Non-Master Part File dialog box as determined by the implementation of the
USER_copied_datasets_details user exit. This preference is only read by this
user exit.
For information, see the Integration Toolkit Function Reference manual.
Determines whether duplicate dataset names are allowed for the same item revision.
VALID
VALUES
Yes Duplicate dataset names are allowed for the same item
revision.
No Duplicate dataset names are not allowed for the same item
revision.
DEFAULT
VALUES
No
SCOPE
Site preference.
DATASET_saveas_allow_name_modification
DESCRIPTION
USER_copied_datasets_details and USER_copied_dataset_name user exits.
This preference is only read by these two user exits.
For information about these two user exits, see the Integration Toolkit Function
Reference manual.
Specifies whether Teamcenter’s recommendation for the dataset name must
be obeyed, or is a suggestion that can be edited by the user. This preferences
is ignored if the automatically generated name fails validation and the
DATASET_saveas_force_name_validation preference is set to true.
VALID
VALUES
true Allows Teamcenter Integration for NX users to modify
automatically generated names for new nonmaster datasets.
false Does not allow Teamcenter Integration for NX users to modify
automatically generated names for new nonmaster datasets.

DEFAULT
VALUES
true
SCOPE
Site preference.
DATASET_saveas_always_copy
DESCRIPTION
Reference manual.
Specifies dataset types that must always be copied when the SaveAs command is
implemented against a master part in Teamcenter Integration for NX to create a
new revision.
VALID
VALUES
Valid Teamcenter dataset types.
DEFAULT
VALUES
None.
SCOPE
Site preference.
DATASET_saveas_force_name_validation
DESCRIPTION
Reference manual.
Specifies whether, once a user has been allowed to modify an automatically
generated dataset name, it must be validated.
VALID
VALUES
true Requires nonmaster datasets created in Teamcenter
Integration for NX to pass the validation check.
false Does not require nonmaster datasets created in Teamcenter
Integration for NX to pass the validation check.

DEFAULT
VALUES
true
SCOPE
Site preference.
DATASET_saveas_never_copy
DESCRIPTION
Reference manual.
Specifies dataset types that cannot be copied when the SaveAs command is
implemented against a master part in Teamcenter Integration for NX to create a
new revision.
VALID
VALUES
Valid Teamcenter dataset types.
DEFAULT
VALUES
None.
SCOPE
Site preference.
DATASET_saveas_owner
DESCRIPTION
Reference manual.
Specifies whether the owner of the new non-master part being created using the
SaveAs command in Teamcenter Integration for NX should be the user performing
the command, or the owner of the nonmaster part being copied.
VALID
VALUES
Original The owner of the nonmaster part being copied is the owner of
the new nonmaster part being created.
SavingUser The owner of the nonmaster part being copied is the user
performing the SaveAs command.

DEFAULT
VALUES
SavingUser
SCOPE
Site preference.
DATASET_saveas_pattern
DESCRIPTION
Reference manual.
Specifies a pattern used to generate and return the output name of nonmaster items
during SaveAs of their master item. The pattern consists of literal text and the
following tokens: ${UserText}, ${ItemID} and ${RevisionID}. Existing dataset
names are expected to match this pattern, where ${ItemID} and ${RevisionID}
match the item ID and revision ID of the owning item revision respectively, and
${UserText} matches any text in the original name. For example, a typical pattern
is:
${UserText}-${ItemID}/${RevisionID}
where the site has decided that the ${UserText} at the beginning is intended to be
the name of the dataset, for example: drawing, and the minus sign (-) is literal
text. If you are saving item revision 001234/B to item revision 002345/A, and the
dataset’s existing name is drawing-001234/B then the name is said to’match
against the pattern. Because the ${UserText} at the start of this pattern matches
any string, the dataset name fea-001234/B would also match against the pattern.
However, drawing_001234/B would not match the pattern as the minus sign is
required, and drawing-001235/B would not match since the item ID is incorrect.
Once an original dataset name has been matched against the pattern, the new
dataset name is generated by replacing the ${ItemID} and ${RevisionID} with the
new revision and item ID in the pattern, and all occurrences of ${UserData} with
whatever text they matched against in the original name. This new name can then
be used for saving the new dataset. Using the example above, the two datasets are
saved as drawing-002345/A and fea-002345/A.
You can modify these generated names using the
DATASET_saveas_allow_name_modification preference. However, if the
DATASET_saveas_force_name_validation preferences is set to true, the
user-edited name is still required to match the pattern.
VALID
VALUES
${UserText} Dataset names are copied forward to the new revision
unchanged.
DEFAULT
VALUES
${UserText}

SCOPE
Site preference.
<DATASET TYPE>_saveas_pattern
DESCRIPTION
Performs the same behavior as the DATASET_saveas_pattern preference, but for
a specific dataset type. Use this preference to define different Save As patterns for
different non-master datasets.
For example, assign the naming pattern drawing-001234/B to the UGPART
dataset, and the naming pattern drawing-001234 to the UGALTREP dataset by
creating the following two preferences:
UGPART_saveas_pattern=
${UserText}-${ItemID}/${RevisionID}
UGALTREP_saveas_pattern=
${UserText}-${ItemID}
For more information about defining naming patterns, see the
DATASET_saveas_pattern preference.
VALID
VALUES
${UserText} Dataset names are copied forward to the new revision
unchanged.
DEFAULT
VALUES
None.
SCOPE
Site preference.
NX_InterOptWithProductViewDataset
DESCRIPTION
Determines whether product view datasets associated with item revisions and BOM
views are sent to Teamcenter Integration for NX along with the item revisions and
BOM views.
VALID
VALUES
TRUE Product view datasets associated with item revisions and BOM
views are sent to Teamcenter Integration for NX along with
the item revisions and BOM views.
FALSE Product view datasets associated with item revisions and BOM
views are not sent to Teamcenter Integration for NX along
with the item revisions and BOM views.
DEFAULT
VALUES
FALSE

SCOPE
Site preference.
TC_default_part_type
DESCRIPTION
Determines the default part type created.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter type.
DEFAULT
VALUES
Item
SCOPE
All.
TC_NX_allow_attrsync_master_with_item
DESCRIPTION
Use with attribute synchronization functionality. Determines whether Teamcenter
allows synchronization of UGMASTER attributes mapped to item-level properties
from Teamcenter Integration for NX to Teamcenter.
By default, attributes mapped to the properties of the Item Master form attached to
item objects (not item revisions) will synchronize from Teamcenter to Teamcenter
Integration for NX; but not in the reverse direction. These attributes are read-only
in Teamcenter Integration for NX after the first execution of the NX Save command
from the Teamcenter Integration for NX application.
Permitting mapping in the reverse direction (Teamcenter Integration for NX to
Teamcenter) allows mapping attributes to the properties of the Item Master form
stored at the item level. This must not be done. Mapping at the item level may result
in loss of data and/or the appearance of incorrect data.
VALID
VALUES
YES Attributes mapped to the properties of the Item Master
form will synchronize bidirectionally between Teamcenter
Integration for NX and Teamcenter.
Caution
This mapping allows multiple item revision objects
(Rev/A, Rev/B, Rev/C, and so on) to overwrite the
values stored on the Item Master form at the item level.
Mappings at the item level may result in loss of data
and/or the appearance of incorrect data.
NO Attributes mapped to the properties of the Item Master

form will synchronize only from Teamcenter to Teamcenter
Integration for NX.

DEFAULT
VALUES
NO
SCOPE
Site preference.
TC_NX_Allow_Deepcopy
DESCRIPTION
Determines whether deep copy functionality is supported with Teamcenter
Integration for NX.
VALID
VALUES
true Deep copy functionality is supported with Teamcenter
Integration for NX.
false Deep copy functionality is not supported with Teamcenter
Integration for NX.
DEFAULT
VALUES
true
SCOPE
Site preference.
TC_NX_ATTRIBUTES_FORM
DESCRIPTION
Specifies the form type used to display of UGPART and UGMASTER attributes.
VALID
VALUES
A single string as a value; the string must be a valid Teamcenter form type.
DEFAULT
VALUES
UGPartAttr
SCOPE
Site preference.
TC_NX_Database_Attributes_For_Load
DESCRIPTION
Specifies the set of customer-defined, non-standard database attributes that are
retrieved for each item type/dataset type whenever a part is loaded.
All database attributes are retrieved for the top-level assembly. This preference
controls the nonstandard attributes that are retrieved for the child components of
the top-level assembly and can be used for NX parts, transient parts, and JT parts.
These nonstandard attributes are defined using the attribute mapping definitions in

Teamcenter and are refreshed on demand in NX depending on the operation that

requests them. However, this may not necessarily occur when loading a part.
The refreshing of attributes does not impact performance at low latencies, but does
impact performance at higher latencies. If you are working with a latency greater
than 10 milliseconds, it is recommended that you utilize this preference to refresh
the database attributes whenever a part is loaded.
Note
To get an idea of the attributes that are being queried during load operations,
load a sample assembly and check the NX syslog for messages about inefficient
attributes loading.
Note
The following standard database attributes are always loaded for all contexts
and do not have to be specified by this preference:
• DB_PART_NAME
• DB_PART_DESC
• DB_PART_NO
• DB_PART_REV
• DB_PART_TYPE
• DB_UNITS
VALID
VALUES
The value format is three keywords and their values. The keywords are:
ItemType
DatasetType
AttributeTitle
The format informs NX which database attribute to load for a specific context
(ItemType/DatasetType). Values are enclosed in quotation marks. An empty
string (“”) can be applied to either or both of ItemType and DatasetType.
For example:
TC_NX_Database_Attributes_For_Load=
ItemType=”NXPart” DatasetType="UGMASTER" AttributeTitle=”Attribute1”

Note
• The wild card designation, "*", can be specified as the value of
AttributeTitle to indicate that all database attributes for that context
are loaded when opening a part in NX.
• A context without any entries in

TC_NX_Database_Attributes_For_Load loads standard database
attributes only.
DEFAULT
VALUES
None.
SCOPE
All.
TC_NX_DeleteMarkupsOnDrawingSheetImport
DESCRIPTION
Deletes the CGM datasets created in Teamcenter for which there are no sheets in NX.
In NX, choose File→Export→Drawings to Teamcenter to open a dialog box that
lists the names of the existing sheets. Select the names of the sheets for which
you want to create (or retain) the CGM datasets and select Delete existing sheets
from Teamcenter.
VALID
VALUES
TRUE
FALSE
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
TC_NX_DrawingSheet_Deletion_Pattern
DESCRIPTION
Contain values for sheet naming patterns. For example, if you want sheet names
called Sheet1, Sheet2, Sheet3, and so on, set this preference to Sheet.
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_NX_Foreign_Datasets
DESCRIPTION
Specifies the non-NX dataset types available to NX when it lists the datasets in
an item revision.
Note
Specifying dataset types in this preference only makes the dataset types
available to NX, it does not enable the application to read the dataset type.
VALID
VALUES
The value format is four keywords and their values. The keywords are:
DatasetType
NamedReference
NamedReferenceFormat
NamedReferenceTemplate
The format informs NX precisely which named references of the dataset contain the
CAD data. Values are enclosed in quotation marks.
Valid values for the NamedReferenceFormat keyword are BINARY or TEXT. The
named reference template must be the extension for files of that type. For example:
TC_NX_Foreign_Datasets=
DatasetType=“DirectModel” NamedReference=“JTPART”
NamedReferenceFormat=“BINARY” NamedReferenceTemplate=“jt”
DatasetType=“SE PART” NamedReference=“SE-Part”
NamedReferenceFormat=“BINARY” NamedReferenceTemplate=“par”
Note
The values are case sensitive and all of the entry must be included on one line
for each dataset type.
DEFAULT
VALUES
None.
SCOPE
All.
TC_ugmaster_name_separator
DESCRIPTION
Specifies the separator character used when generating dataset IDs from the parent
item ID and revision for UGMASTER datasets created through the NX Integration
or NX. For example, if the value is set to a slash (/), the parent item ID is NX001,
and the parent revision is A; the dataset ID is generated as NX001/A.
This preference is not added automatically during installation.

DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_NX_Navigator_Override_NX_Load_Option
DESCRIPTION
Determines which configuration to load when an assembly is opened in Teamcenter
Integration for NX from rich client. Its defined values are referenced only when
an assembly is opened from My Teamcenter; assemblies opened from Structure
Manager obey the revision rules set in Structure Manager.
VALID
VALUES
As Saved Loads the part file as it was saved in Teamcenter Integration
for NX.
Latest Loads the part file with the latest revision rule.
None Ignores the As Saved command and loads the assembly as
defined in the load_options.def file.
DEFAULT
VALUES
Latest
SCOPE
All.
TC_NX_NEW_COPY_REV
DESCRIPTION
Determines the algorithm of the Save As New Revision functionality within
Teamcenter Integration for NX.
VALID
VALUES
YES Improves the performance of the Save As New Revision
functionality within Teamcenter Integration for NX. The
performance improvement is most noticeable in a WAN
environment.
NO Performs the Save As New Revision functionality within
Teamcenter Integration for NX using the same method as
previous releases.
DEFAULT
VALUES
NO
SCOPE
Site preference.

TC_NX_NEW_NR_FORMS
DESCRIPTION
Determines whether the storage of mass properties and part attributes for
use in new assembly update structure algorithms is used. If set to OFF, the
UGII_NEW_UPDATE_STRUCTURE NX environment variable should also be set
to OFF to ensure that update structure continues to work properly.
VALID
VALUES
ON
Allows storage of mass properties and part attributes for use in new assembly
update structure algorithms.
OFF
Prevents storage of mass properties and part attributes for use in new assembly
update structure algorithms.
DEFAULT
VALUES
ON
SCOPE
Site preference.
TC_NX_nonmaster_additional_forms
DESCRIPTION
Lists the named references forms to include when creating or updating specific NX
nonmaster dataset types (UGPART, UGALTREP, or UGSCENARIO). Format for
the values is NX-Dataset-type-name:NamedRef-Name. For example:
UGPART:UGPART-BBOX
This preference affects the behavior of NX 18.0 and later versions only and is
irrelevant to the earlier versions. Also, the named reference forms considered have
nothing to do with the regular NX Integration attributes synchronization.
VALID
VALUES
UGALTREP:UGPART-BBOX
UGALTREP:UGPART-MASSPR
UGALTREP:UGPART-ATTRIBUTES
DEFAULT
VALUES
UGALTREP:UGPART-BBOX
UGALTREP:UGPART-MASSPR
UGALTREP:UGPART-ATTRIBUTES
SCOPE
Site preference.

TC_NX_save_precise_on_uprev
DESCRIPTION
Determines whether a new assembly, created in Teamcenter Integration for NX
using the Save As command, is created as precise or imprecise. For example, when
the Save As command is invoked upon a precise assembly with a revision rule of
Latest Working, the new assembly is precise or imprecise, depending on the setting
of this preference.
VALID
VALUES
yes Creates a precise assembly.
no Creates an imprecise assembly.
DEFAULT
VALUES
yes
SCOPE
Site preference.
TC_NX_Unit_Of_Measure_As_Geometric_List
DESCRIPTION
Allows you to specify a list of units of measure at your site that creates components
as geometric in NX. The wildcard character (*) can be used to designate all units
of measure at your site.
VALID
VALUES
All predefined units of measure in the database.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_NX_Unit_Of_Measure_Each_List
DESCRIPTION
Allows you to specify a list of units of measure at your site that you want to be
treated the same as each, ea, or “” when determining whether a component is
geometric. All components with these units of measure have their quantities
rounded to a whole number in NX.
VALID
VALUES
All predefined units of measure in the database.

DEFAULT
VALUES
None. The values each and ea are hard-coded and do not have to be included in
the preference.
SCOPE
Site preference.
TC_NX_UPDATE_ATTRIBUTES
DESCRIPTION
Determines whether NX attributes are synchronized with Teamcenter attributes. If
this preference is set, define the attributes by setting the API_ugpart_attr_titles
preference.
Note
This preference is enabled only when the newer method of
NX/Teamcenter attribute synchronization is disabled by setting the
UGII_UGMGR_ATTR_SYNC NX environment variable to OLD.
VALID
VALUES
yes Synchronizes NX attributes with Teamcenter attributes.
no Does not synchronize NX attributes with Teamcenter
attributes.
DEFAULT
VALUES
TITLE
CREATOR
PART_TYPE
PART_NO MODEL
MATERIAL
ASSEMB_NO
WEIGHT
TASK_NO
SCOPE
Site preference.
TC_NX_View_Type
DESCRIPTION
Sets the BOM view type that Teamcenter Integration for NX uses to read and write
product structure information.
For more information about multiple BOM views, see Structure Manager Guide.
VALID
VALUES
A single string as a value; the string must be a valid Teamcenter BOM view type.

DEFAULT
VALUES
view
SCOPE
Site preference.
TC_SPSD_FOLDER
DESCRIPTION
Defines the folder name where released item revisions containing Simulation
Process Studio datasets are stored. After this preference is defined, users can create
Simulation Process Studio processes in any folder in the Teamcenter database. To
see these processes in the Teamcenter Integration for NX palette, export the item
revisions containing Simulation Process Studio datasets to the folder specified by
this preference.
Consumers use this folder to access process templates from Teamcenter Integration
for NX.
During database installation or upgrade, a folder is created with the name specified
by this preference, if the folder does not already exist.
VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter folder name.
DEFAULT
VALUES
Simulation Process Studio
SCOPE
User preference.
TC_SPSD_FOLDER_PATH
DESCRIPTION
Defines multiple folders in the Teamcenter database where authors can create
processes for testing and verification. All processes can be accessed via Teamcenter
Integration for NX, allowing authors to test, validate, and finalize the processes.
VALID
VALUES
Accepts multiple strings as values; each string must be a valid Teamcenter folder
name.
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_USE_TEST_ATTR_MAPPINGS
DESCRIPTION
Determines whether Teamcenter references the test attribute mappings rather
than the real mappings.
VALID
VALUES
Any nonzero value.
DEFAULT
VALUES
None.
SCOPE
Site preference.
Preferences set in the .tc_ugman_env file

Preferences set in the .tc_ugman_env file generally control the behavior of
Teamcenter Integration for NX and have no effect during a Teamcenter session.
For more information about this preference file and individual preferences, see the
Teamcenter Integration for NX Guide.
Siemens PLM Software recommends using the default settings of the
UGMAN_PartType and UGMAN_ShowPartType preferences. This ensures every
Teamcenter item have an associated UGMASTER in order to support assembly
modeling.
For more information, see Teamcenter Integration for NX Guide.
UGMAN_InsertItem
DESCRIPTION
Specifies a default object type and paste location when no folder is selected when
creating a new object using the Create Part (Item) dialog box.
VALID
VALUES
1 Inserts datasets into the Newstuff folder.
2 Inserts an item into the Newstuff folder.
3 Inserts an item revision into the Newstuff folder.
DEFAULT
VALUES
2

UGMAN_PartType
DESCRIPTION
Determines the default type of the dataset created using the Create Part (Item)
dialog box. This preference is overridden by setting the UGMAN_ShowPartType
preference to 1.
VALID
VALUES
UGMASTER
UGPART
DEFAULT
VALUES
UGMASTER
UGMAN_ShowPartType
DESCRIPTION
Determines whether the option to select a dataset type is displayed in the
Create Part (Item) dialog box. When set to 1, this preference overrides by the
UGMAN_PartType preference.
VALID
VALUES
0 Does not display an option allowing the user to select a dataset
type. In this case, the UGMAN_PartType preference settings
are used.
1 Displays an option allowing the user to select a dataset type.
When this setting is used, the dataset type chosen by the user
overrides any dataset type defined in the UGMAN_PartType
preference.
DEFAULT
VALUES
0
UGMAN_UGPARTNameWRev
DESCRIPTION
Specifies the naming convention of new UGMASTER and UGPART datasets
created in the Create Part (Item) dialog box. The naming convention determines
whether the new name contains a revision. The dataset name is not defined by the
user in this dialog box, rather the dataset name is generated automatically based on
the settings of this preference.
VALID
VALUES
0 Creates new UGMASTER and UGPART datasets names
without a revision.
1 Creates new UGMASTER and UGPART datasets names with
a revision.

DEFAULT
VALUES
1
Preferences set in the ug_english.def file

Preferences set in the ug_english.def preference file generally control the way NX
handles changes made in Teamcenter are reflected in NX assemblies and parts. The
following entries provide brief descriptions of some of the preferences set in this file.
It is not intended to be an exhaustive reference to these files.
For more information, see Teamcenter Integration for NX Guide and the NX
documentation.
UGhookupStructureUpdateOnSave
DESCRIPTION
Determines whether Teamcenter BOM view revisions are updated to
reflect changes made to NX assemblies. This preference is similar to the
UGhookupStructureUpdateOnLoad preference, which updates NX assemblies
when Teamcenter BOM view revisions are changed.
VALID
VALUES
ON Updates BOM view revisions.
OFF Does not update BOM view revisions.
DEFAULT
VALUES
ON
UGhookupStructureUpdateOnLoad
DESCRIPTION
Determines whether NX assemblies are updated to reflect changes made
toTeamcenter BOM view revisions. The update occurs when the NX assembly is
loaded. This preference is similar to the UGhookupStructureUpdateOnSave
preference, which updates Teamcenter BOM view revisions when NX assemblies
are changed.
VALID
VALUES
ON Updates NX assemblies.
OFF Does not update NX assemblies.
DEFAULT
VALUES
ON

UGhookupPartDisplayPreference
DESCRIPTION
Determines the configuration of the Part Selection dialog box.
VALID
VALUES
One or more strings as values; each string must be a valid NX attribute.
DEFAULT
VALUES
None. If this preference is not set, NumberName is assumed.
Preferences set in the .ugii_env file

The .ugii_env preference file is the NX equivalent of Teamcenter’s
tc_preferences.xml preference file. Although .ugii_env stores NX preferences,
several of these preferences may at times affect Teamcenter behavior because both
programs use the same low-level libraries (libsys).
The following entries provide a partial listing of NX preferences in the .ugii_env file
that may affect Teamcenter behavior.
For more information, see the NX documentation.
TRACE_BACK
DESCRIPTION
Enables or suppresses NX traceback log files.
VALID
VALUES
ON Enables NX traceback log files.
OFF Suppresses NX traceback log files.
DEFAULT
VALUES
ON. If not set, ON is assumed.
SCOPE
Site preference.
UGII_KEEP_SYSTEM_LOG
DESCRIPTION
Determines whether to retain system log files when they contain no errors.
VALID
VALUES
Any value.
DEFAULT
VALUES
None.

SCOPE
Site preference.
UGII_OPTION
DESCRIPTION
Determines how to interpret and convert file specifications. This preference can
drastically affect Teamcenter File Services behavior. For example, if you create
Teamcenter volumes with mixed-case names and this preference is set to LOWER,
Teamcenter File Services is not able to find your volumes. Therefore, ensure that this
preference is set consistent with file specification naming conventions at your site.
VALID
VALUES
NONE File specifications are interpreted without converting case.
LOWER Converts the entire file specification (directory and file name)
to all lowercase.
UPPER Converts the entire file specification (directory and file name)
to all uppercase.
HINAME Converts the file name to all uppercase but leaves the directory
path name unchanged.
LONAME Converts the file name to all lowercase but leaves the directory
path name unchanged.
DEFAULT
VALUES
LOWER
SCOPE
Site preference.
UGII_TMP_DIR
DESCRIPTION
Specifies the temporary directory for storing application log files.
VALID
VALUES
Single string as value; each string must be the full operating system path of the
directory.
DEFAULT
VALUES
None.
SCOPE
Site preference.

Password preferences
Password site preferences are used to specify restrictions on password format.
Whenever a password is set or modified, the system checks these preferences and
validates the new password value against the preference settings.
Use password site preferences to enforce the following password requirements:
• Minimum length
• Mixed case
• Minimum number of numeric characters
• Minimum number of alpha characters
• Nonalphanumeric characters allowed as special characters
• Minimum number of special characters
PASSWORD_minimum_characters
DESCRIPTION
Defines the minimum length required for a new password.
VALID
VALUES
A positive integer whose value does not exceed the maximum storage space allocated
to a password in the database. A value of 0 means no minimum is required.
DEFAULT
VALUES
0
SCOPE
Site preference.
PASSWORD_special_characters
DESCRIPTION
Defines which nonalphanumeric characters are valid in a password.
VALID
VALUES
One or more strings as values. When left unset, any special characters are allowed.
A null string allows no special characters.
DEFAULT
VALUES
None.
SCOPE
Site preference.

PASSWORD_mixed_case_required
DESCRIPTION
Determines if mixed case is required in a password.
VALID
VALUES
true Mixed case is required in a password.
false Mixed case is not required in a password.
DEFAULT
VALUES
false
SCOPE
Site preference.
PASSWORD_minimum_special_chars
DESCRIPTION
Determines the minimum number of special characters (defined in the
PASSWORD_special_characters preference) required in a password.
VALID
VALUES
A positive integer whose value, combined with other minimum password length
values, does not exceed the maximum storage space allocated to a password in the
database. A value of 0 means no minimum is required.
DEFAULT
VALUES
0
SCOPE
Site preference.
PASSWORD_minimum_digits
DESCRIPTION
Determines the minimum number of digits required in a password.
VALID
VALUES
DEFAULT
VALUES
0
SCOPE
Site preference.

PASSWORD_minimum_alpha
DESCRIPTION
Determines the minimum number of alphabetic characters required in a password.
VALID
VALUES
DEFAULT
VALUES
0
SCOPE
Site preference.
Teamcenter services preferences

The following preferences configure aspects of Teamcenter Services. Teamcenter
Services are built using service-oriented architecture (SOA).
For more information about Teamcenter Services, see Services Guide.
SOA_MaxOperationBracketInactiveTime
DESCRIPTION
Specifies the maximum time in seconds for an operation bracket without active
server requests.
VALID
VALUES
Single positive integer.
DEFAULT
VALUES
60
SCOPE
Site preference.
NOTES
If an SOA startOperation request is issued, the operation bracket should be
terminated with a stopOperation request. If the client leaves a bracket open
without any server requests for this period of time, the bracket is automatically
terminated upon the next SOA request.
SOA_MaxOperationBracketTime
DESCRIPTION
Specifies the maximum time in seconds for an operation bracket to suppress
redundant refreshes.

VALID
VALUES
DEFAULT
VALUES
600
SCOPE
Site preference.
NOTES
If an SOA startOperation request is issued, the operation bracket should be
terminated with a stopOperation request. If bracket lasts longer than specified by
this preference, the bracket is automatically terminated.
Remote workflow preferences

Remote workflow enables users to create links between Teamcenter objects and
objects in other Teamcenter products.
Use the following preferences to define the Teamcenter applications to which links
can be created from Teamcenter, and the types of Teamcenter objects that can be
used to create these links.
TC_external_local_app_guid
DESCRIPTION
Defines the GUID (general unique identifier) of the home application, in this case,
of Teamcenter. When a link is created, the system submits its GUID to the remote
application so a bi-directional link can be created. This preference is set by the
system during the Remote workflow installation procedure.
VALID
VALUES
During the Remote workflow installation procedure, the GUID can be either
manually entered or automatically generated by the system. Siemens PLM Software
recommends autogenerating the GUID.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_external_proxiable_objects
DESCRIPTION
Defines the Teamcenter objects used to create links to other Teamcenter applications.
VALID
VALUES
Any valid Teamcenter workspace object.

DEFAULT
VALUES
Item
ItemRevision
Dataset
Form
PSBOMViewRevision
PSBOMView
Folder
EPMJob
SCOPE
Site preference.
TC_external_proxiable_objects_props
DESCRIPTION
Defines the Teamcenter properties of each proxy object provided to the remote
application.
VALID
VALUES
Any valid Teamcenter property names of workspace objects.
DEFAULT
VALUES
object_name
object_desc
owning_user
owning_group
obj_icon_url
SCOPE
Site preference.
TC_external_Requirements_proxy_props_internal
DESCRIPTION
Defines the properties of each proxy object imported from Teamcenter’s systems
engineering and requirements management to be stored in Teamcenter.
VALID
VALUES
Any valid Teamcenter property names of workspace objects.
DEFAULT
VALUES
object_app_guid
ext_obj_id
ext_obj_url
ext_obj_name
ext_obj_desc
ext_obj_icon_url
ext_id_num
ext_id_num_list

last_mod_user
last_mod_date
long_text
SCOPE
Site preference.
TC_external_Requirements_proxy_props_external
DESCRIPTION
Defines the properties of each proxy object imported from Teamcenter’s systems
engineering and requirements management to be stored in Teamcenter.
VALID
VALUES
Any valid Teamcenter property names of workspace objects. Properties specified
in this preference must correlate exactly to the properties specified in the
TC_external_Requirements_proxy_props_internal site preference.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IMAN_external_appl_reg_url
DESCRIPTION
Defines the URL of the central application registry to which Teamcenter is registered.
VALID
VALUES
Valid URL address of the central application registry to which Teamcenter is
registered.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_external_application_names
DESCRIPTION
Defines the Teamcenter applications to which Teamcenter can create links.
VALID
VALUES
Teamcenter application names as they are defined in the Teamcenter Application
Registry.
For more information, see Installation on UNIX and Linux Servers Guide or
Installation on Windows Servers Guide.

DEFAULT
VALUES
Teamcenter Project
Teamcenter Requirements
SCOPE
Site preference.
TC_external_application_types
DESCRIPTION
Defines the Teamcenter application types to which Teamcenter can create links.
VALID
VALUES
application type as defined in the TC_external_application_names preference.
DEFAULT
VALUES
Project
Requirements
SCOPE
Site preference.
Teamcenter LDAP synchronization preferences

Teamcenter’s synchronization tool, the ldapsync utility, looks at data in an LDAP
directory server and compares it with data currently in Teamcenter’s database.
User, person, group, and role entries not in the database are added. If a user
is present in both systems, the most recently modified user data in one source
overwrites the other. For example, if the LDAP information was modified more
recently than the Teamcenter information, the Teamcenter data is synchronized to
the LDAP information. If a Teamcenter user is not found in the LDAP database, the
Teamcenter user is deactivated.
Synchronization preferences manage LDAP connection behavior.
Note
For more information about implementing synchronization functionality, see
the ldapsync utility in the Utilities Reference manual.
There are five categories of LDAP synchronization preferences:

• LDAP connection preferences
• Synchronization preferences
• Group object mapping preferences
• Role object mapping preferences

• User and person object mapping preferences
LDAP connection preferences

LDAP connection preferences contain information used to connect to LDAP to
begin synchronization.
LDAP_service_hosts
DESCRIPTION
Defines the list of hosts providing LDAP directory service for the synchronization
installation.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid host name. Define
hosts running the LDAP directory that you want to use for synchronization.
DEFAULT
VALUES
None.
SCOPE
Site preference.
LDAP_port_number
DESCRIPTION
Defines the port number used when connecting to the hosts defined in the
LDAP_service_hosts preference. This preference works with the LDAP_use_ssl
preference. If this preference is set to the SSL port on the directory server, but
the LDAP_use_ssl preference is set to FALSE, the directory server ignores the
connection request from the synchronization tool, making it appear that the tool
has hung. When configuring the LDAP synchronization tool to use the SSL, make
certain the LDAP_use_ssl preference is set to TRUE.
VALID
VALUES
Accepts a single string as a value. Must be a single positive integer. Define the
Security Services server port to enable synchronization.
DEFAULT
VALUES
None.
SCOPE
Site preference.
LDAP_use_ssl
DESCRIPTION
Determines whether the connection to the LDAP server uses Security Services. If
the LDAP_port_number preference is set to the SSL port on the directory server,

but this preference is set to FALSE, the directory server ignores the connection
request from the synchronization tool, making it appear that the tool has hung.
When configuring the LDAP synchronization tool to use the SSL, make certain
this preference is set to TRUE.
VALID
VALUES
TRUE The LDAP server connection uses Security Services. If this
setting is used, the LDAP_cert_db_path preference must
also be set.
FALSE The LDAP server connection does not use Security Services.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
LDAP_cert_db_path
DESCRIPTION
Defines the path to the certificate used for the Security Services connection. The
system only checks this preference if the LDAP_use_ssl preference is set to
TRUE. Ensure this preference points to a correctly configured certificate database.
Otherwise, errors are encountered when configuring the LDAP synchronization
tool to use the SSL.
VALID
VALUES
Accepts a single string as a value. Must be the full path to the certificate database
used for the Security Services connection.
DEFAULT
VALUES
None.
SCOPE
Site preference.
LDAP_admin_dn
DESCRIPTION
Defines the user name used by the synchronization tool to connect to the LDAP
server. The user name is the distinguished name (DN) of a LDAP user with search
and read permissions in the LDAP system. The user needn’t have modification
abilities in LDAP.
VALID
VALUES
Accepts a single string as a value. Must be the DN of a LDAP user with search and
read permissions in the LDAP system.
DEFAULT
VALUES
None.

SCOPE
Site preference.
LDAP_admin_pw
DESCRIPTION
Defines the password for the LDAP_admin_dn user preference.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
Synchronization preferences
Synchronization flags control the overall nature of synchronization.
LDAP_sync_user_flags
DESCRIPTION
Defines the user synchronization setting flags in a chmod-style character string
format.
VALID
VALUES
The supported user synchronization flags are:
s (synchronize) If set, enables user synchronization.
c (create) If set, allows new externally managed user and person objects
to be created in Teamcenter during user synchronization.
d (deactivate) If set, allows externally managed user and person objects to be
deactivated in Teamcenter during user synchronization.
u (update) If set, allows externally managed user and person objects to be
updated in Teamcenter during user synchronization.
e (externalize) If set, any internally managed user and person objects found in
Teamcenter to have the same user ID and person name as a
user object in LDAP is converted to externally managed during
user synchronization.
DEFAULT
VALUES
scdue
SCOPE
Site preference.

LDAP_sync_group_flags
DESCRIPTION
Defines the group synchronization setting flags in a chmod-style character string
format.
VALID
VALUES
The supported group synchronization flags are:
s (synchronize) If set, enables group synchronization.
c (create) If set, allows new externally managed group objects to be
created in Teamcenter during group synchronization.
u (update) If set, allows externally managed group objects to be updated
in Teamcenter during group synchronization.
e (externalize) If set, any internally managed group objects found in
Teamcenter to have the same group name as a group object
in LDAP is converted to externally managed during group
synchronization.
DEFAULT
VALUES
s
c
u
e
SCOPE
Site preference.
LDAP_sync_member_flags
DESCRIPTION
Defines the group member synchronization setting flags in a chmod-style character
string format.
Note
Group member synchronization requires both user synchronization and
group synchronization to be enabled. If group member synchronization is
enabled but either user or group synchronization is not, then group member
synchronization is skipped.
VALID
VALUES
The supported group member synchronization flags are:
s (synchronize) If set, enables group member synchronization.

c (create) If set, allows new externally managed group member

objects to be created in Teamcenter during group member
synchronization.
d (deactivate) If set, allows externally managed group member objects to be
deactivated in Teamcenter during user synchronization.
e (externalize) If set, any internally managed group objects found in
Teamcenter to have the same user ID, group name, and role
name as a group member relationship in LDAP is converted to
externally managed during group member synchronization.
DEFAULT
VALUES
scde
SCOPE
Site preference.
LDAP_sync_role_flags
DESCRIPTION
Defines the role synchronization setting flags in a chmod-style character string
format.
Note
Role synchronization requires group synchronization to be enabled. If
role synchronization is enabled but group synchronization is not, then role
synchronization is skipped.
VALID
VALUES
The supported role member synchronization flags are:
s (synchronize) If set, enables role synchronization.
c (create) If set, allows new externally managed role objects to be created
in Teamcenter during role synchronization.
u (update) If set, allows externally managed role objects to be updated in
Teamcenter during role synchronization.
e (externalize) If set, any internally managed role objects found in Teamcenter
to have the same role name as a role object in LDAP is
converted to externally managed during role synchronization.
DEFAULT
VALUES
s
c
u
e
SCOPE
Site preference.

LDAP_member_list_attr
DESCRIPTION
Defines the LDAP group object attribute that contains the list of member
distinguished names (DN) for the object. This preference applies to objects
representing either groups or roles defined in LDAP. Use this preference only if the
LDAP_member_type_attr preference is set.
VALID
VALUES
DEFAULT
VALUES
uniqueMember
SCOPE
Site preference.
LDAP_member_type_attr
DESCRIPTION
Defines the LDAP group object attribute that contains the membership type (direct
or indirect) for this object.
VALID
VALUES
TRUE Specifies indirect group membership. If this setting is used,
the LDAP_member_list_attr preference must also be set.
FALSE Specifies direct group membership.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
LDAP_object_type_attr
DESCRIPTION
Defines the LDAP group object attribute that contains the object type (group
or role) for this object.
VALID
VALUES
group The object represents a group defined in LDAP.
role The object represents a role defined in LDAP.
DEFAULT
VALUES
group

SCOPE
Site preference.
Group object mapping preferences

Group object mapping preferences indicate which specific LDAP group object
attributes to use for synchronization.
LDAP_group_base_dn
DESCRIPTION
Defines the distinguished name (DN) of one or more nodes in the external directory
where the group synchronization process begins searching.
This preference limits which part of the LDAP external directory the sync tool views
when searching for groups to synchronize with Teamcenter.
Use this attribute to improve performance and to partition groups within a single
LDAP database across several Teamcenter installations. If your site’s LDAP
directory does not have a high degree of organization, set this value to the lowest
level DNs that encompass all of the Teamcenter groups. For example, a high-level
DN is:
dc=net,dc=plm,dc=ugs,dc=com
An example of a specific DN is:
ou=Engineering Groups,ou=groups,dc=net,dc=plm,dc=ugs,dc=com
VALID
VALUES
Accepts a set of one or more strings.
DEFAULT
VALUES
None.
SCOPE
Site preference.
LDAP_group_query_filter
DESCRIPTION
Defines a set of conditions that an LDAP object must satisfy to be matched as a
group object for synchronizing with Teamcenter.
If you are familiar with LDAP query filter syntax, use this optional preference,
which is a more sophisticated object matching mechanism.
VALID
VALUES
Accepts a single string in LDAP query filter syntax.
DEFAULT
VALUES
(cn=*)

SCOPE
Site preference.
LDAP_group_object_class
DESCRIPTION
Defines the LDAP object class that the customer uses to model groups to be
synchronized with Teamcenter. If you use multiple classes that all represent groups,
use this preference to specify the common base class of those classes.
This optional preference allows you to define specific subclasses in LDAP to
differentiate groups and roles. If groups and roles both have the same object
class, they must be differentiated by values of the attribute specified using the
LDAP_object_type_attr preference.
VALID
VALUES
Accepts a single string, which is the name of an LDAP object class.
DEFAULT
VALUES
groupOfUniqueNames
SCOPE
Site preference.
LDAP_group_attr_mapping
DESCRIPTION
Maps LDAP object attributes to Teamcenter group attributes. The mappings
control what information the synchronization tool (the ldapsync utility) sets in
the Teamcenter group object.
LDAP_group_attr_mapping=
LDAPGroupName
cn
%REPLACE_ME%
LDAPGroupDesc
description
%REPLACE_ME%
LDAPLastUpdate
modifyTimestamp
%REPLACE_ME%
LDAPGroupDBA
%REPLACE_ME%
0
LDAPGroupRole
%REPLACE_ME%
%REPLACE_ME%
VALID
VALUES
Accepts triples of strings.

Each attribute mapping consists of three strings: the attribute identifier, the mapped
LDAP attribute name, and the default value (to be used if there is no LDAP mapped
attribute or if the LDAP mapped attribute value is null).
DEFAULT
VALUES
None.
SCOPE
Site preference.
Role object mapping preferences

Role object mapping preferences indicate which specific LDAP role object attributes
to use for synchronization.
LDAP_role_query_filter
DESCRIPTION
Defines a set of conditions that an LDAP object must satisfy to become matched as a
role object for synchronizing with Teamcenter.
This optional preference allows administrators familiar with LDAP query filter
syntax to use a more sophisticated object matching mechanism.
VALID
VALUES
Accepts a string in LDAP query filter syntax.
DEFAULT
VALUES
(cn=*)
SCOPE
Site preference.
LDAP_role_object_class
DESCRIPTION
Defines the LDAP object class used to model roles to be synchronized with
Teamcenter. If you use multiple classes that all represent roles, use this preference
to specify the common base class of those classes.
This optional preference allows you to define specific subclasses in LDAP to
differentiate groups and roles. If groups and roles both have the same object
class, they must be differentiated by values of the attribute specified using the
LDAP_object_type_attr preference.
VALID
VALUES
Accepts a single string. Must be the name of an LDAP object class.
DEFAULT
VALUES
groupOfUniqueNames

SCOPE
Site preference.
LDAP_role_attr_mapping
DESCRIPTION
Maps LDAP attributes to Teamcenter role attributes. The mappings control what
information the synchronization tool sets in the Teamcenter role object.
LDAP_role_attr_mapping=
LDAPRoleName
cn
%REPLACE_ME%
LDAPRoleDesc
description
%REPLACE_ME%
LDAPLastUpdate
modifyTimestamp
%REPLACE_ME%
VALID
VALUES
Each attribute mapping consists of three strings: the Teamcenter attribute name,
the mapped LDAP attribute name, and the default value (to be used if there is no
LDAP mapped attribute or if the LDAP mapped attribute value is null).
DEFAULT
VALUES
None.
SCOPE
Site preference.
User and person object mapping preferences

The user and person object mapping preferences indicate which specific LDAP user
and person object attributes to use for synchronization.
LDAP_attribute_mapping
DESCRIPTION
Maps LDAP attributes to Teamcenter attributes. The mappings control what
information the synchronization tool sets in the Teamcenter user and person objects.
For example:
LDAP_attribute_mapping=
LDAPPersonName
cn
%REPLACE_ME%
LDAPEngUserId
uid

%REPLACE_ME%
LDAPLastUpdate
modifyTimestamp
%REPLACE_ME%
LDAPOsUser
uid
%REPLACE_ME%
LDAPUserGroup
%REPLACE_ME%
Engineering
LDAPUserRole
%REPLACE_ME%
%REPLACE_ME%
VALID
VALUES
Accepts multiple strings, in pairs, as values. Each pair must contain valid LDAP and
Teamcenter attributes.
DEFAULT
VALUES
None.
SCOPE
Site preference.
LDAP_base_dn
DESCRIPTION
Defines the distinguished name (DN) of the top-level entry under which all user
entries to be checked are defined. Use this preference to limit which part of the
LDAP directory the synchronization tool examines when searching for Teamcenter
users. This functionality can also be used to partition users within a single LDAP
database across several Teamcenter installations.
If a site does not have this degree of organization in its LDAP directory, this value
should be set to the lowest level in the directory that would encompass all of the
Engineering users. Following is an example of how a high-level value might appear:
dc=ugs,dc=com
A more specific entry would look as follows:
ou=Engineering Users,ou=special users,dc=ugs,dc=com
VALID
VALUES
Accepts one or more strings as a value. Must be a valid LDAP directory name.
DEFAULT
VALUES
None.
SCOPE
Site preference.

LDAP_ignore_users
DESCRIPTION
Defines a set user IDs that should not be processed by the ldapsync utility. This list
normally contains Teamcenter user IDs that are used for administrative purposes
and do not have corresponding entries in the LDAP repository.
VALID
VALUES
Accepts one or more strings.
DEFAULT
VALUES
infodba
SCOPE
Site preference.
LDAP_user_query_filter
DESCRIPTION
Defines a set of conditions that an LDAP object must satisfy to be matched as a
user object for synchronizing with Teamcenter. This optional preference allows
administrators familiar with LDAP query filter syntax to use a more sophisticated
object matching mechanism.
VALID
VALUES
Accepts a single string. Must be in LDAP query filter syntax.
DEFAULT
VALUES
(cn=*)
SCOPE
Site preference.
LDAP_user_object_class
DESCRIPTION
Defines the LDAP object class that the customer uses to model users to be
synchronized with Teamcenter. If you use multiple classes that all represent users,
then this preference should specify the common base class of those classes.
VALID
VALUES
Accepts a single string. Must be the name of an LDAP object class.
DEFAULT
VALUES
inetOrgPerson
SCOPE
Site preference.

LDAP_person_attr_mapping
DESCRIPTION
Maps LDAP user attributes to Teamcenter person attributes. The mappings control
what information the synchronization tool sets in the Teamcenter person objects.
LDAP_attribute_mapping=
LDAPPersonName
cn
%REPLACE_ME%
LDAPLastUpdate
modifyTimestamp
%REPLACE_ME%
PA1
postaladdress
%REPLACE_ME%
PA2
localityName
%REPLACE_ME%
PA3
st
%REPLACE_ME%
PA4
postalCode
%REPLACE_ME%
PA5
co
%REPLACE_ME%
PA6
o
%REPLACE_ME%
PA7
employeeNumber
%REPLACE_ME%
PA8
physicalDeliveryOfficeName
%REPLACE_ME%
PA9
mail
%REPLACE_ME%
PA10
telephoneNumber
%REPLACE_ME%
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.

Validation Manager preferences

The Validation Manager application provides a decision mechanism to let users
ensure a target meets compliance before it is released. Once validation processes are
configured, users can select a target in Teamcenter and confirm its compliance with
the business rules defined at your site.
For more information, see the Validation Manager Guide.
Baseline_precondition_validation_rule_item_revision
DESCRIPTION
Specifies the validation rule item revision for baseline preaction handler.
VALID
VALUES
Item revision name.
DEFAULT
VALUES
None.
SCOPE
Site preference.
NXCheckMateCreate.CREATE_REGISTEREDTO
DESCRIPTION
Indicates the business object to which the NXCheckMate object creation style
sheet can be applied.
VALID
VALUES
Accepts a single string as a value. It must be a valid Teamcenter business object.
DEFAULT
VALUES
NXCheckMate
SCOPE
Site preference.
NXCheckMate.CREATERENDERING
DESCRIPTION
Registers the create style sheet for NXCheckMate objects.
VALID
VALUES
DEFAULT
VALUES
NXCheckMateCreate

SCOPE
Site preference.
NXCheckMateRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for NXCheckMateRevision objects.
VALID
VALUES
DEFAULT
VALUES
NXCheckMateRevSummary
SCOPE
Site preference.
NXCheckMateRevSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business objects to which the NXCheckMateRevision summary
style sheet can be applied.
VALID
VALUES
DEFAULT
VALUES
NXCheckMateRevision
SCOPE
Site preference.
NXCheckMate.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for NXCheckMate objects.
VALID
VALUES
DEFAULT
VALUES
NXCheckMateSummary
SCOPE
Site preference.

NXCheckMateSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business objects to which the NXCheckMate summary style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
NXCheckMate
SCOPE
Site preference.
NXCMValDataCreate.CREATE_REGISTEREDTO
DESCRIPTION
Indicates the business objects to which the NXCMValData object creation style
VALID
VALUES
Accepts a single string as a value. It must be a valid Teamcenter business object.
DEFAULT
VALUES
NXCMValData
SCOPE
Site preference.
NXCMValData.CREATERENDERING
DESCRIPTION
Registers the create style sheet for NXCMValData objects.
VALID
VALUES
DEFAULT
VALUES
NXCMValDataCreate
SCOPE
Site preference.

NXCMValDataRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for NXCMValDataRevision objects.
VALID
VALUES
DEFAULT
VALUES
NXCMValDataRevSummary
SCOPE
Site preference.
NXCMValDataRevSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business objects to which the NXCMValDataRevision summary
VALID
VALUES
DEFAULT
VALUES
NXCMValDataRevision
SCOPE
Site preference.
NXCMValData.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for NXCMValData objects.
VALID
VALUES
DEFAULT
VALUES
NXCMValDataSummary
SCOPE
Site preference.

NXCMValDataSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business objects to which the NXCMValData summary style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
NXCMValData
SCOPE
Site preference.
NXRDDVRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for NXRDDVRevision objects.
VALID
VALUES
DEFAULT
VALUES
NXRDDVRevSummary
SCOPE
Site preference.
NXRDDVRevSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business objects to which the NXRDDVRevision summary style
VALID
VALUES
DEFAULT
VALUES
NXRDDVRevision
SCOPE
Site preference.

NXRDDV.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for NXRDDV objects.
VALID
VALUES
DEFAULT
VALUES
NXRDDVSummary
SCOPE
Site preference.
NXRDDVSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business objects to which the NXRDDV summary style sheet can be
applied.
VALID
VALUES
DEFAULT
VALUES
NXRDDV
SCOPE
Site preference.
NXRDDVValDataRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for NXRDDVValDataRevision objects.
VALID
VALUES
DEFAULT
VALUES
NXRDDVValDataRevSummary
SCOPE
Site preference.

NXRDDVValDataRevSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business objects to which the NXRDDVValDataRevision summary
VALID
VALUES
DEFAULT
VALUES
NXRDDVValDataRevision
SCOPE
Site preference.
NXRDDVValData.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for NXRDDVValData objects.
VALID
VALUES
DEFAULT
VALUES
NXRDDVValDataSummary
SCOPE
Site preference.
NXRDDVValDataSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business objects to which the NXRDDVValData summary style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
NXRDDVValData
SCOPE
Site preference.

TC_ALLOW_ADHOC_VALIDATIONS
DESCRIPTION
Determines whether users can set pending validation results to Pass or Fail on the
Validation Master form. Some validation utilities may not return either a pass or
fail result, so the user may have to make an ad hoc decision regarding the success or
failure of the validation.
This preference is applicable for the NX Check-Mate validation agent only.
VALID
VALUES
TRUE Allows users to set pending results to Pass or Fail.
FALSE Does not allow users to set pending results to pass or fail.
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
TC_Validation_Datasettype
DESCRIPTION
Determines which datasets types can be validated upon import.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter dataset
type.
DEFAULT
VALUES
Software
SCOPE
Site preference.
TC_VALIDATION_duplicate_nx_valdata_error_on_import
DESCRIPTION
Indicates if an error should be returned when importing an NX validation checker
that has the same checker name as an existing NX validation checker.
VALID
VALUES
TRUE
FALSE
DEFAULT
VALUES
FALSE

SCOPE
Site preference.
TC_VALIDATION_FILE_TYPES
DESCRIPTION
Determines the types of files that can be associated as datasets to validation data or
validation results objects.
This preference is applicable for the NX Check-Mate and NX RDDV
(Requirement-Driven Design Validation) validation agents only.
VALID
VALUES
Accepts one or more strings as values. Each string must contain three string values:
dataset name, RefName and referencers (which are file extensions in the following
example), defining the types of files that can contain rules or validation results.
For example:
TC_VALIDATION_FILE_TYPES=
Text Text *.mqclog
MSExcel excel *.xls
DEFAULT
VALUES
ValidationResultLog MQCXML *.xml
ValidationResultLog MQCXML *.mqcxml
ValidationResultLog MQC *.mqclog
ValidationResultLog MQC *.log
ValidationResultLog IMAGE_J *.jpg
ValidationResultLog DFA *.dfa
ValidationResultLog MSExcel *.xls
ValidationResultLog XSL *.xsl
SCOPE
Site preference.
TC_VALIDATION_mandatory_checkers_required
DESCRIPTION
Specifies whether the mandatory checkers are required to be run when performing
validation.
VALID
VALUES
Accepts multiple strings as value.
true Mandatory checkers are required.
false Mandatory checkers are not required.
DEFAULT
VALUES
false

SCOPE
Site preference.
TC_VALIDATION_PROGRAM
DESCRIPTION
Specifies the full path of your custom invocation program. This program is
executed to invoke the validations. If nothing is specified, it executes the default
invoke_validation_process.bat program under the TC_BIN directory.
VALID
VALUES
Full path to the program.
DEFAULT
VALUES
%TC_BIN%\invoke_validation_process.bat
SCOPE
Site preference.
TC_Validation_relation_primary
DESCRIPTION
Displays validation results under the specified item revision types.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid item revision type.
DEFAULT
VALUES
ItemRevision
ValidationData
ValidationResult
SCOPE
Site preference.
TC_VALIDATION_RESULT_ALLOW_REPLICA_OBJECT
DESCRIPTION
Determines whether validation results can be created at remote sites.
VALID
VALUES
TRUE Allows validation checks to be performed at remote sites on a
replica. Remote validation result objects are lost when deleted
from remote site, they cannot be exported.
FALSE Validation checks cannot be performed at remote sites on a
replica.

DEFAULT
VALUES
FALSE
SCOPE
Site preference.
TC_VALIDATION_RULE_SET_ITEM_REVISIONS
DESCRIPTION
Defines the list of item revisions that contain validation rule datasets, and which
are displayed in the Rule Setlist of the Rule Set Evaluation tab in the Validation
Manager. You can always type in or paste items and item revisions into the list.
Register them into this preference list after creation.
VALID
VALUES
The format for the entries is:
item-ID/revision-ID
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_VALIDATION_run_validation_hidden_agents
DESCRIPTION
List of Validation Agent class names to be hidden in the list in the Run Validation
dialog box.
VALID
VALUES
Accepts multiple strings as value.
DEFAULT
VALUES
NXRDDV
SCOPE
Site preference.
TC_VALIDATION_STYLESHEET_DATASETNAME
DESCRIPTION
Specifies a list of style sheet datasets information. This is a blank separated list
containing the dataset type, reference type name, named reference name, style
sheet file name, and validation result log file extension that is used to match this
style sheet dataset.

For example, the NX Check-Mate result log is in PLM XMLformat with .xml as an
extension. It needs a style sheet (checkmat_log.xsl) for a tool (Internet Explorer
for instance) to display its contents in a pre-defined format.
This preference is also used to import style sheet files into the database as style
sheet datasets during installation or the upgrade (post schema) process.
VALID
VALUES
The format is:
dataset-type dataset-reference-type-name dataset-name stylesheet-name.extension
validation-result-file-extension.
DEFAULT
VALUES
XMLReportFormatter XSL ValidationResultMQCXML checkmate_log.xsl
*.xml
SCOPE
Site preference.
TC_VALIDATION_TIMESTAMP_NREFS
DESCRIPTION
Timestamp on a validation result and dataset is compared to decide whether the
result is up-to-date. The following list is an extension to this logic. The list gives the
Namedref list against each dataset type. For the following dataset types, instead of
the dataset timestamp, the named reference timestamp is used to compare the dates.
VALID
VALUES
TRUE Enables the named reference timestamp.
FALSE Disables the named reference timestamp.
DEFAULT
VALUES
UGMASTER UGPART *.prt
UGPART UGPART *.prt
UGALTREP UGPART *.prt
UGSCENARIO UGPART *.prt
SCOPE
Site preference.
TC_VALIDATION_USE_PLMXML
DESCRIPTION
Determines how Teamcenter communicates with a validation utility. Setting this
preference to TRUE generates a single PLM XML file for all of the targets to be
validated. The validation utility must be able to parse this file properly to execute
the validation for each target. Setting this preference to FALSE causes each target
to be treated separately.

VALID
VALUES
TRUE Causes a single PLM XML file to be generated for all targets.
FALSECauses each target to be treated separately.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
TC_Validation_Utility
DESCRIPTION
Determines the utility that performs the validation and conversion process. When
importing, the input is validated using the bintool conversion and validation
utility. This utility is a command line program designed to be called within scripts
or manually called by users. It automatically detects the type of input file for the
following formats:
Motorola S1
Motorola S2
Motorola S3
Intel HEX
Intel LBA
API Binary
The utility reads the input file and provides information regarding the contents. If it
detects a failure on any line, it will not read the file and an error will be displayed. A
return code regarding the output status is provided.
Note
The BinTool utility cannot perform consistency checks on binary input data.
Thus the following formats are not testable and will not be read by the utility:
Binary
DPS Binary (SBIN)
VALID
VALUES
Accepts a single string as a value. Must be the full path defining the utility’s name
and location. For example:
TC_Validation_Utility =
C:\\temp\\bintool
DEFAULT
VALUES
C:\\temp\\bintool
SCOPE
Site preference.

TC_VALIDATION_ViewValidationWithRuleSetColumnPreferences
DESCRIPTION
Defines the list of property names to be displayed as columns in the View Validation
table.
VALID
VALUES
Accepts string array.
DEFAULT
VALUES
validation_status
validation_target
validation_name
validation_result
override_request_state
result_state_flag
validation_application
validation_user
validation_date
SCOPE
Site preference.
TC_VALIDATION_ViewValidationWithRuleSetColumnWidthPreferences
DESCRIPTION
Specifies the widths of columns displayed in the View Validation table.
VALID
VALUES
Accepts string array.
DEFAULT
VALUES
20
15
25
10
25
15
15
10
15
SCOPE
Site preference.

ValidationAgent_DefaultChildProperties
DESCRIPTION
Determines which properties are children of the ValidationAgent business object.
VALID
VALUES
Accepts one or more strings as values; each string must be a valid Teamcenter
property name.
DEFAULT
VALUES
revision_list
SCOPE
Site preference.
ValidationAgentRevision_DefaultChildProperties
DESCRIPTION
Determines which properties are children of the ValidationAgentRevision
business object.
VALID
VALUES
property name.
DEFAULT
VALUES
TC_validation_data
SCOPE
Site preference.
ValidationAgentRevision_Folder_default_relation
DESCRIPTION
Defines the default relation for creation of a Folder object in context of a
ValidationAgentRevision object.
VALID
VALUES
Accepts a single string as a value. It must be a valid Teamcenter relation business
object.
DEFAULT
VALUES
IMAN_reference
SCOPE
Site preference.

ValidationAgentRevision_ValData_default_relation
DESCRIPTION
Defines the default relation for creation of a ValData Item object in context of
an ValidationAgentRevision object.
VALID
VALUES
object.
DEFAULT
VALUES
TC_validation_data
SCOPE
Site preference.
VALIDATION_APPLICATIONS
DESCRIPTION
Enables or disables validation object functionality.
VALID
VALUES
Accepts one or more strings as values; each string must be the name of a validating
software application, such as NX or I2.
Providing a valid value enables the validation functionality.
DEFAULT
VALUES
NX Check-Mate
SCOPE
Site preference.
ValidationMasterFormColumnPreferences
DESCRIPTION
Defines the list of property names to be displayed as columns in the
ValidationMasterForm table.
VALID
VALUES
validation_target
validation_name
validation_utility_name
validation_user
validation_date
result_state_flag
validation_result
override_to_state

DEFAULT
VALUES
validation_target
validation_name
validation_result
result_state_flag
validation_user
validation_date
SCOPE
Site preference.
ValidationMasterFormColumnWidthPreferences
DESCRIPTION
Specifies the widths of the shown columns in the ValidationMasterForm table.
VALID
VALUES
10
25
15
10
10
15
10
10
10
15
DEFAULT
VALUES
15
25
10
25
15
15
10
15
SCOPE
Site preference.

ValToolAgentRevision_DefaultChildProperties
DESCRIPTION
Determines which properties are children of the ValToolAgentRevision business
object.
VALID
VALUES
property name.
DEFAULT
VALUES
TC_validation_data
TC_validation_tool
SCOPE
Site preference.
ValToolAgentRevision_Tool_default_relation
DESCRIPTION
Defines the default relation for associating a Tool object in context of a
ValToolAgentRevision object.
VALID
VALUES
object.
DEFAULT
VALUES
TC_validation_tool
SCOPE
Site preference.

Chapter
6 Access Manager and Portfolio,

Program and Project
Management preferences
AM_PROJECT_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
TC_project_validate_conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
TC_Project_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
TC_Project_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
TC_Program_Preferred_Items_relation_primary . . . . . . . . . . . . . . . . . . . . . . 6-3
TC_project_bom_2nd_level_propagate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
TC_multi_site_project_member_bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
TC_set_current_project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
TC_show_all_user_projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
TC_current_role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Chapter
6 Access Manager and Portfolio,

Program and Project
Management preferences
Access Manager provides data security by controlling user access to data. Use
Access Manager to grant/restrict access to objects in Teamcenter via the Access
Manager (AM) rule tree. The tree is built of rules and access permissions. Using this
application requires administrative privileges.
For more information, see the Access Manager Guide and the Security Administration
Guide.
Projects allow you to control user access to Teamcenter data. A project is a grouping
of objects that are accessible to users who are designated as members of the project
team. Security rules can be implemented based on projects and roles in projects
to restrict data access.
For more information, see the Project and Program Guide.
Use the following preferences to manage the behavior of various rules and
permissions associated with AM and projects.
AM_PROJECT_MODE
DESCRIPTION
Determines whether the system evaluates the roles in all the active projects of the
logged in user, or just the role of the current project, when processing the Role in
Project and Role in Projects of Object accessors.
The Teamcenter servers must be restarted after setting this site preference, for the
setting to become effective in Access Manager evaluation.
VALID
VALUES
true System evaluates the roles in all active projects of the logged in user while
processing the Role in Project and Role in Projects of Object accessors.
false System evaluates only the roles of the current project of the logged in user
while processing the Role in Project and Role in Projects of Object
accessors.
DEFAULT
VALUES
false.

Chapter 6 Access Manager and Portfolio, Program and Project Management
preferences
Note
If this preference is undefined, default behavior is false.
SCOPE
Site preference.
TC_project_validate_conditions
DESCRIPTION
Determines how the ASSIGN_TO_PROJECT and REMOVE_FROM_PROJECT
Access Manager privileges are validated in conjunction with privileged membership
validation.
For information about defining privileged membership, see the Project and Program
Guide.
The behavior of this preference is overruled by
TC_multi_site_project_member_bypass preference settings.
Note
This preference is not included in your Teamcenter installation. You must
add it to the database.
For more information, see the Rich Client Interface Guide.
VALID
VALUES
0 The system confirms the user is a privileged member of the
project before allowing the user to assign/remove objects
to/from a project.
1 The system confirms the user is either a privileged member of
the project, or that the user has the ASSIGN_TO_PROJECT
privilege before allowing the user to assign object to a project.
Likewise, a user must be either a privileged member of the
project, or have the REMOVE_FROM_PROJECT privilege
to remove an object from a project.
2 The system confirms the user is a regular project member and
has the ASSIGN_TO_PROJECT privilege before allowing
the user to assign object to a project. Likewise, a user must
have the REMOVE_FROM_PROJECT privilege to remove
an object from a project.
3 The system confirms the user is a privileged member of the
project and that the user has the ASSIGN_TO_PROJECT
privilege before allowing the user to assign object to a project.
Likewise, a user must be a privileged member of the project
and have the REMOVE_FROM_PROJECT privilege to
remove an object from a project.
DEFAULT
VALUES
0

Access Manager and Portfolio, Program and Project Management preferences
SCOPE
Site preference.
TC_Project_DefaultChildProperties
DESCRIPTION
Specifies a list of properties that can be children of the TC_Project business object
type.
VALID
VALUES
Accepts any valid property name of the TC_Project object.
DEFAULT
VALUES
TC_Program_Preferred_Items
SCOPE
Site preference.
TC_Project_PseudoFolder
DESCRIPTION
Specifies a list of properties that may be displayed as a pseudo folder under a node of
TC_Project business object type.
VALID
VALUES
Accepts any valid property name of the TC_Project object.
DEFAULT
VALUES
TC_Program_Preferred_Items
SCOPE
Site preference.
TC_Program_Preferred_Items_relation_primary
DESCRIPTION
Specifies a list of valid primary business object types for the
TC_Program_Preferred_Items relation.
VALID
VALUES
Accepts any valid business object type name.
DEFAULT
VALUES
TC_Project
SCOPE
Site preference.

preferences
TC_project_bom_2nd_level_propagate
DESCRIPTION
Note
Specifies which relation types are available for level two propagation. By default,
this preference is unset and level-two propagation is not enabled. Set this preference
to enable this functionality.
Level-two propagation processes dependent objects related to the datasets associated
with level one objects. The following data model is supported for level-two
propagation:
Item
Item
revision
Dataset Item revision (associated with the dataset by a
specified relation type)
Dataset Dataset (associated with the dataset by a specified
relation type)
Dataset Item (associated with the dataset by a specified
relation type)
Note
Dependent objects assigned through level-two propagation are explicitly
assigned to the project. Objects that are explicitly assigned to projects must
also be explicitly removed. If the BOM object to which the secondary object is
removed from the project, the dependent object remains.
For detailed information about assigning objects to projects using propagation rules,
and the differences between level-one propagation and level-two propagation, see
Project and Program Guide.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid relation type.
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_multi_site_project_member_bypass
DESCRIPTION
Determines whether a replicated object is assigned to a defined project upon import
to a remote site, regardless of whether the importing user is a privileged project
member of the project.
If the replicated object is imported by a user who is not a privileged project member,
and this preference is set to true, the replicated object is assigned to the defined
project upon import.
If the replicated object is imported by a user who is not a privileged project member,
and this preference is set to false, the replicated object is not assigned to the defined
project upon import.
Note
VALID
VALUES
true Replicated object is assigned to the defined project regardless of whether
the importing user is a privileged project member.
false Replicated object is assigned to the defined project only if the importing
user is a privileged project member.
DEFAULT
VALUES
false
SCOPE
Site preference.
TC_set_current_project
DESCRIPTION
Determines whether the project saved in the previous Teamcenter session for a
particular user is set as the current project in a new session for the same user.
VALID
VALUES
true The project saved in the previous Teamcenter session is set as the current
project in the new Teamcenter session.
false The project saved in the previous Teamcenter session is not set as the
current project in the new Teamcenter session.
DEFAULT
VALUES
true

preferences
Note
If this preference is undefined, the default behavior is true.
SCOPE
Site preference.
TC_show_all_user_projects
DESCRIPTION
Controls whether all active projects in which a user is a privileged team member are
displayed for selection in the Teamcenter interface or whether only the projects that
correlate to the user’s current group and role are displayed for selection.
VALID
VALUES
true The system displays all active projects in which the user is a privileged team
member, regardless of the user’s current group and role.
false The system displays only the active projects in which the user is a privileged
team member based on the user’s current group and role.
DEFAULT
VALUE
true
SCOPE
Site preference.
TC_current_role
DESCRIPTION
Specifies whether the user’s membership in a role enforces access to objects.
VALID
VALUES
true A member of the role has access to an object only when the role is that user’s
current role.
false A member of the role has access to an object even when the role is not the
user’s current role.
DEFAULT
VALUES
false
SCOPE
Site preference.
NOTES
• The Role in Group, Role in Owning Group, Role in Project, and Role in
Project of Object accessors work on the superset of roles the user possesses in
the relevant group or project, rather than on the current role in the session.
• When the TC_current_role preference is set, it affects the evaluation of the

Role in Owning Group and Role accessors, but it does not affect the Role in
Group accessor.

• When the AM_PROJECT_MODE preference is set, it affects the evaluation of

the Role in Project and Role in Project of Object accessors.

Chapter
7 eIntegrator Admin preferences
EINT_adapter_names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
EINT_<adapter_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
EINT_global_services_datasource_names . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
EINT_global_services_urls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
ATTRSHARING_datasource_connection_details . . . . . . . . . . . . . . . . . . . . . . 7-3
ATTRSHARING_max_rows_expected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
EINT_storage_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
EINT_update_on_save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
EINT_import_selected_rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
EINT_create_new_forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
EINT_form_refresh_pref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
EINT_item_rev_pref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
EINT_copy_to_clipboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
EINT_max_num_rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
EINT_ibi_api_library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Chapter
7 eIntegrator Admin preferences
eIntegrator Admin provides a simple integration mechanism to integrate external

data with Teamcenter. Use eIntegrator Admin to map external data systems into
equivalent objects in its database. The data can then be imported into the database
as forms.
Use the following preferences to define how eIntegrator Admin updates form data
from the external source, and how eIntegrator Admin forms are attached to item
revisions.
EINT_adapter_names
DESCRIPTION
Defines valid adapters.
VALID
VALUES
Names of valid adapters.
DEFAULT
VALUES
EINT_odbc_adapter
EINT_ibi_adapter
EINT_tcintegrator_adapter
SCOPE
Site preference.
EINT_<adapter_name>
DESCRIPTION
Determines the display name of the specified adapter. A single preference is
needed for each eIntegrator Admin adapter name. For example, if your site was
running an ODBC adapter and an IBI adapter, both a EINT_odbc_adapter and
EINT_ibi_adapter preference would need to be added to the preference file and
defined with the desired display name.
VALID
VALUES
A single string; must be the name of a valid adapter.
DEFAULT
VALUES
EINT_odbc_adapter= iMANAdapter
EINT_ibi_adapter= IBIAdapter

Chapter 7 eIntegrator Admin preferences
SCOPE
Site preference.
EINT_global_services_datasource_names
DESCRIPTION
Defines the display names for defined data sources used by the Global Services
adapter. Global Services is a Web application that enables your site to access
information stored in virtually any type of electronic data source that manages
your enterprise data.
For more information about this functionality, see the Global Services Configuration
Guide.
This preference works in conjunction with the EINT_global_services_urls
preference.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid, defined data source.
DEFAULT
VALUES
None.
SCOPE
Site preference.
EINT_global_services_urls
DESCRIPTION
Defines the data source locations, in universal resource locator (URL) format, for
the data sources defined in the EINT_global_services_datasource_names
preference. Global Services is a Web application that enables your site to access
information stored in virtually any type of electronic data source that manages
your enterprise data.
For more information about this functionality, see the Global Services Configuration
Guide.
VALID
VALUES
Accepts multiple strings as values. Each string must be in URL format, pointing to
a defined data source.
DEFAULT
VALUES
None.
SCOPE
Site preference.

eIntegrator Admin preferences
ATTRSHARING_datasource_connection_details
DESCRIPTION
Defines the data source used for attribute sharing. Only one data source can be
defined at a given time.
VALID
VALUES
Accepts a single string as a value. Must be a valid data source defined from the
eIntegrator Admin application.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ATTRSHARING_max_rows_expected
DESCRIPTION
Defines the maximum number of rows that can be returned from a result set. If the
return exceeds the number of rows defined by this preference, an error message
appears.
VALID
VALUES
DEFAULT
VALUES
100
SCOPE
Site preference.
EINT_storage_type
DESCRIPTION
Determines storage method of external data within Teamcenter.
VALID
VALUES
0 Stores external data persistently in Teamcenter.
1 Caches external data in Teamcenter.
DEFAULT
VALUES
1
SCOPE
All.

EINT_update_on_save
DESCRIPTION
Determines how to update external data when saving Teamcenter forms.
VALID
VALUES
0 Does not update external data when saving an eIntegrator Admin form.
1 Updates external data when saving an eIntegrator Admin form.
DEFAULT
VALUES
0
SCOPE
Site preference.
EINT_import_selected_rows
DESCRIPTION
Determines method of importing selected rows to the query results table.
VALID
VALUES
0 Imports all rows into the query result table.
1 Imports only selected rows into the query result table.
DEFAULT
VALUES
1
SCOPE
Site preference.
EINT_create_new_forms
DESCRIPTION
Determines whether or not to create a new form when importing external data. If
left unset, eIntegrator Admin creates a new form for the imported data.
VALID
VALUES
0 Updates the existing form with the imported data if found by the given name.
1 Always creates a new form when importing external data.
DEFAULT
VALUES
1
SCOPE
Site preference.

eIntegrator Admin preferences
EINT_form_refresh_pref
DESCRIPTION
Controls whether or not the refresh operation updates the eIntegrator Admin form
data from the external source.
VALID
VALUES
0 The form data is not updated when the refresh operation is run.
1 A SQL query runs and fetches the external data every time the eIntegrator
Admin form is refreshed.
DEFAULT
VALUES
0
SCOPE
Use as a site preference to implement the setting throughout the site.
Use as a user preference to allow administrators (users with DBA access) to
re-import form data without affecting the refresh behavior for all users at the site.
EINT_item_rev_pref
DESCRIPTION
Defines the behavior for attaching an eIntegrator Admin form to an item revision
when there is no item revision mapping and the latest version of the item revision is
released.
VALID
VALUES
0 Indicates that no new item revision can be created.
1 Creates a new item revision based on the released revision and creates and
attaches a new form to this item revision. Existing eIntegrator Admin forms,
if any, are not copied from the released revision.
DEFAULT
VALUES
0
SCOPE
Use as a user preferences to allow administrators (users with DBA access) to
EINT_copy_to_clipboard
DESCRIPTION
Determines the location of new forms after importing external data.
VALID
VALUES
0 Pastes the new forms into the user’s Newstuff folder.

1 Copies the new forms to the Teamcenter clipboard.

DEFAULT
VALUES
0
SCOPE
Use as a user preferences to allow administrators (users with DBA access) to
EINT_max_num_rows
DESCRIPTION
Determines the number of external data rows results after performing an SQL
query before asking for user confirmation.
VALID
VALUES
Single, positive integer.
DEFAULT
VALUES
30
SCOPE
User preference.
EINT_ibi_api_library
DESCRIPTION
Defines the IBI API library to be loaded dynamically. If a location is not specified,
Teamcenter look for the library in the SHLIB_PATH or LD_LIBRARY_PATH
directories, if on a UNIX or Windows platform, respectively.
VALID
VALUES
Single string as a value.
DEFAULT
VALUES
edaapi
SCOPE
Site preference.

Chapter
8 Authorization preferences
TC_authorization_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Chapter
8 Authorization preferences
Authorization enables you to control access to Teamcenter administrative

applications and utilities based on a user’s group membership or role in a group.
For more information, see the Authorization Guide.
Use the following preferences to manage the behavior of accessing applications.
TC_authorization_mode
DESCRIPTION
Determines whether to evaluate all the group memberships of a user and the user’s
role in those groups when authorizing access to an application or to evaluate the
user’s current group logon and role in that group.
For information about configuring access to an application, see the Authorization
Guide.
Example
To access the Organization application, a user must have dba privileges (be
a member of dba with the role of DBA). If the user is a member of both the
dba and the Engineering groups and logs on under the Engineering group, the
user may or may not have access to the Organization application depending
on how TC_authorization_mode is set:
• If set to on (evaluate all group memberships and the roles in the groups),
the user has administration privileges based on membership in the dba
group, even though the user is not currently logged on under that group.
The user can access the Organization application.
• If set to off (evaluate only the current logon group and the role in that
group), the user does not have administration privileges through the
Engineering group. Therefore, the user cannot access the Organization
application.
VALID
VALUES
on Evaluates all the group memberships of a user and the user’s roles in those
groups to determine the user’s access to an application.
off Evaluates only the user’s current logon group and the user’s role in that
group to determine the user’s access to an application.

Chapter 8 Authorization preferences
DEFAULT
VALUES
off
SCOPE
Site preference.

Chapter
9 File management and

maintenance preferences
Audit Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

TC_audit_manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
TC_audit_log_dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
TC_audit_buffer_size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
TC_audit_file_format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
TC_audit_delimiter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Archive, restore, and migration preferences . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

HSM_integration_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
HSM_read_thru_supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
HSM_primary_tier_hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
HSM_secondary_tier_capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Centera_Cluster_IPAddresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
TC_Store_and_Forward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
TC_Store_and_Forward_Transfer_Delay . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
TC_enable_backup_modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Action manager daemon preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

TC_actionmgrd_sleep_minutes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
TC_actionmgrd_general_processing_hours . . . . . . . . . . . . . . . . . . . . . . . 9-9
TC_actionmgrd_max_actions_to_dispatch . . . . . . . . . . . . . . . . . . . . . . . . 9-10
TC_actionmgrd_max_subprocess_to_start . . . . . . . . . . . . . . . . . . . . . . . . 9-10
TC_actionmgrd_cloning_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Subscription Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

TC_subscriptionmgrd_sleep_minutes . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
TC_subscriptionmgrd_processing_hours . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
TC_subscriptionmgrd_max_subscriptions_to_dispatch . . . . . . . . . . . . . . . 9-12
TC_subscriptionmgrd_cloning_interval . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
TC_notification_msg_ext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Subscription Monitor preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13

TC_subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
TC_refresh_notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
TC_refresh_notify_scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
TC_refresh_notify_subscribe_to_types . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
<TypeName>_subscribe_to_events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
TC_refresh_notify_pull_time_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
TC_refresh_notify_list_maximum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
TC_automatic_refresh_waiting_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17

TC_automatic_refresh_time_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
TC_automatic_refresh_list_maximum . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
TC_refresh_notify_timed_out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Mail_subscription_notify_sub_groups_too . . . . . . . . . . . . . . . . . . . . . . . . 9-18
TC_subscription_log_event_and_action_status . . . . . . . . . . . . . . . . . . . . . 9-19
TcSubscriptionColumnPreferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
TcSubscriptionColumnWidthPreferences . . . . . . . . . . . . . . . . . . . . . . . . 9-19
TcEventColumnPreferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
TcEventColumnWidthPreferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
TcActionColumnPreferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
TcActionColumnWidthPreferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
SCM_notification_history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
SCM_notification_WorkspaceObject_props . . . . . . . . . . . . . . . . . . . . . . . 9-22
File caching preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22

Caching modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
Cache purging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
syslog file output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
File caching preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
TC_Cache_Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
TC_Cache_Dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
TC_Cache_Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
TC_Cache_Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
TC_<file type>_Cache_Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
TC_Cache_Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
TC_STAGING_AREA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
TC_System_Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Ticket_Expiration_Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Multisite_Ticket_Expiration_Interval . . . . . . . . . . . . . . . . . . . . . . . . 9-27
blobbyVolume_NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
blobbyVolume_UNX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
TC_Volume_Status_Resync_Interval . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
TC_Volume_Failover_Trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
TC_Volume_Failover_Volume_Name . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
TC_VOLUME_MONITOR_WARNING_LEVEL . . . . . . . . . . . . . . . . . 9-30
TC_VOLUME_MONITOR_CRITICAL_LEVEL . . . . . . . . . . . . . . . . . 9-30
Transient_Volume_Installation_Location . . . . . . . . . . . . . . . . . . . . . . 9-31
Transient_Volume_RootDir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31
Default_Transient_Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Default_Transient_Volume_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Fms_BootStrap_Urls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
FSC_HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
UNLOAD_TRIGGER_CEILING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
UNLOAD_TRIGGER_FLOOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
UNLOAD_MINIMUM_LIFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-35
UNLOAD_LOGGING_LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-36
TC_Populate_FSC_Server_Targets . . . . . . . . . . . . . . . . . . . . . . . . . . 9-36
Log file preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37

TC_Administration_Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
TC_Security_Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
TC_allow_inherited_group_volume_access . . . . . . . . . . . . . . . . . . . . . . . . 9-38
TC_Application_Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
TC_Installation_Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38

TC_Journalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39
TC_Journal_Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39
TC_KEEP_SYSTEM_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39
TC_TMP_DIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
RECOVER_TO_UNRELEASED_STATUS . . . . . . . . . . . . . . . . . . . . . . . . 9-40
RECOVER_TO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
TC_sfr_recovery_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-41
TC_sfr_process_life_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-41

Chapter
9 File management and

maintenance preferences
Maintenance preferences modify the way Teamcenter stores, maintains, and audits
your product data.
Audit Manager preferences

Audit Manager creates audit logs that track selected properties for specified actions
in the database. These properties can include custom properties added by your site.
Use the following preferences to determine Audit Manager behavior.
TC_audit_manager
DESCRIPTION
Determines auditing behavior.
VALID
VALUES
ON Enables the Audit Manager application.
Enables full auditing functionality, providing access to out-of-the-box auditing
reports, to the Viewing the audit logs dialog box, which allows you to search
audit records, and to the View Audit File dialog box, which displays audit
information for the selected object. If a selected object has a legacy audit file
attached, the user can access this file from the Viewing the Audit Logs dialog
box.
For information about using auditing functionality, see the Rich Client
Interface Guide.

Chapter 9 File management and maintenance preferences
OFF Disables the Audit Manager application; the application is not compatible
with the legacy file-based functionality.
Enables only the legacy View Audit File dialog box, which displays audit
information for the selected object.
For information about using this dialog box, see the Rich Client Interface Guide.
DEFAULT
VALUES
OFF
SCOPE
Site preference.
TC_audit_log_dir
DESCRIPTION
Specifies the directory where audit log files are stored. If the directory specified
by this preference cannot be created, audit log files are saved to the preference’s
default setting.
The TC_LOG environment variable must be defined first before starting a
Teamcenter session.
VALID
VALUES
Single string as a value; must be a valid directory path.
DEFAULT
VALUES
%TC_LOG%\audit
SCOPE
Group preference.
TC_audit_buffer_size
DESCRIPTION
Specifies the size of the buffer that holds the audit records during a session. Once
the buffer size is met, the buffer is written to an external file. This number should
be slightly larger than the number of audited events generated during a typical
session. Thus, flushing the buffer to the external file happens only after exiting the
session with no performance penalty.
VALID
VALUES
A positive integer.
DEFAULT
VALUES
1000
SCOPE
Group preference.

File management and maintenance preferences
TC_audit_file_format
DESCRIPTION
Specifies the format of external audit files.
VALID
VALUES
0 Text format (.txt).
1 XML format (.xml).

DEFAULT
VALUES
1
SCOPE
Group preference.
TC_audit_delimiter
DESCRIPTION
Specifies the delimiter that separates fields of audit records.
This preference is used only for audit files in text format. When importing the
audit file into Microsoft Excel or Access, you must specify the same delimiter as
you defined in this preference.
VALID
VALUES
Multiple characters. Siemens PLM Software recommends a single character is used.
Though a single-character entry is not enforced, some spreadsheet programs such as
Excel do not allow multiple character delimiters.
DEFAULT
VALUES
^
SCOPE
Group preference.
Archive, restore, and migration preferences

Archiving migrates objects to primary or secondary storage media in order
to optimize online storage space. Restoration restores objects that have been
archived. You must have read privileges for the object and the object must currently
be archived. Hierarchical storage management moves lower priority files to
third-party storage systems. You can also configure Teamcenter to store files in a
temporary volume then move the files to their final destination volume according to
administer-defined criteria, thus improving performance of upload times from clients.
Use the following preferences to enable and manage archive, restore, and migration
functionality.

HSM_integration_enabled
DESCRIPTION
Enables the Volume Management application to work with third-party hierarchical
storage management (HSM) software.
For more information about HSM functionality, see the Volume Management Guide.
VALID
VALUES
true Enables the Volume Management application to work with
third-party HSM software.
false Disables the Volume Management application from working
with third-party HSM software.
DEFAULT
VALUES
false
SCOPE
Site preference.
HSM_read_thru_supported
DESCRIPTION
Declares whether read access to secondary and tertiary volumes is supported. If
your HSM system or hardware platform does not support read access from secondary
and tertiary volumes, the migrated files are moved to a higher tier to be read. For
example, the IBM Tivoli HSM product does not provide read-through capability,
and the EMC DiskXtender HSM product only provides read-through capability on
Windows. In such situations, use reverse migration to return files to the primary
tier. If this preference is set to false, the system moves the migrated files to a higher
tier during the read operation, then during the next migration, returns the files to
the tiers from which they were retrieved.
For more information, see the Volume Management Guide.
Note
This preference requires that the HSM_integration_enabled preference be
set to true.
VALID
VALUES
true Migrated files are not moved to a higher tier during the read
operation.
false Migrated files are moved to a higher tier during the read
operation. The files are returned to the tiers from which they
were stored in subsequent migrations.
DEFAULT
VALUES
true

SCOPE
Site preference.
HSM_primary_tier_hosts
DESCRIPTION
Defines the host names on which the primary tier volumes are managed by
third-party HSM software.
Note
HSM migration is applied to the volume files residing on hosts defined by this
preference. The hsm_capacity_alert utility estimates the capacities of the
volumes and uses the values defined in this preference to send e-mail alerts
when the primary tier capacity exceeds alert levels. Volumes residing on
hosts not defined by this preference are ignored for HSM migration and the
hsm_capacity_alert utility.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid host name on which
primary tier volumes reside. If all primary tier volumes are managed by third-party
HSM software, you can set this preference to ALL rather than listing the individual
host names.
DEFAULT
VALUES
None.
SCOPE
Site preference.
HSM_secondary_tier_capacity
DESCRIPTION
Sends an e-mail alert when the capacity of the second tier volume reaches capacity.
Set this preference to the estimated capacity level of the second tier volume.
Compute this estimate by totalling all storage capacities of all disks mounted on
the secondary tier.
Note
The hsm_capacity_alert utility estimates the capacities of the volumes
and uses the values defined in this preference to send e-mail alerts when the
secondary tier capacity exceeds alert levels.
VALID
VALUES
Accepts a single string as a value. The value must be the estimated capacity of
the second tier volume. For example:
HSM_secondary_tier_capacity= 16.9

DEFAULT
VALUES
None.
SCOPE
Site preference.
Centera_Cluster_IPAddresses
DESCRIPTION
Defines EMC Centera cluster IP addresses applicable for archive/restore operations
on an EMC Centera pool.
VALID
VALUES
Valid EMC Centera cluster IP addresses.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_Store_and_Forward
DESCRIPTION
Determines whether store and forward functionality is enabled, improving upload
performance for remote users. This functionality improves end-user file upload
times from clients by uploading files to a temporary volume. Users can continue to
work on their files from the temporary location. The system moves the files to its
final destination according to administer-defined criteria. Files are accessible to
FMS at all times.
Enable this functionality by defining a default local volume (an initial upload
volume) for users or groups and setting this preference to true. When users upload
files, the files are temporarily uploaded to the defined initial FMS volume, returning
control to the user in the client. In the background, the files are transferred to the
final destination volume. This allows you to place an FMS volume on the remote
users LAN, ensuring quick uploads into the FMS of this temporary volume. All file
transfers are transparent to end users.
For more information about working with default local volumes, see the System
You can view the status of file transfers from the Dispatcher request administration
console.
For more information, see Getting Started with Dispatcher (Translation
Management).
VALID
VALUES
true Enables store and forward functionality.

false Disables store and forward functionality by instructing the

system to ignore the default local volume setting, uploading
files directly to the destination volume.
This setting is useful to quickly disable store and forward
functionality. For example, if the scheduler or initial volume
at a site goes offline unexpectedly, you can use this setting to
quickly disable store and forward. The alternative is to alter
the initial volume settings of all impacted users, which is a
lengthy task.
DEFAULT
VALUES
False
SCOPE
All.
TC_Store_and_Forward_Transfer_Delay
DESCRIPTION
Determines (in minutes) how long file transfer is delayed between file upload to the
initial volume and file upload to the final destination volume.
Use this preference to improve performance if you have a large amount of revisions
created, cached, and purged at your site. Because the transfer task does not transfer
purged filed, if numerous file revisions are saved frequently at your site, a delay
time long enough to allow revisions to be purged before the transfer to the final
destination volume reduces network traffic.
For example, consider a site where all user files are automatically saved every 15
minutes, and purged after every third revision. If store and forward functionality is
enabled, and this preference is set to 46, the transfer task activates every 46 minutes,
sees that the revisions have been purged, and does not attempt the transfer. Only
files not purged are transferred to the destination volume, decreasing network traffic.
For more information about using this preference with store and forward
functionality, see the System Administration Guide.
VALID
VALUES
Any positive integer.
DEFAULT
VALUES
0
SCOPE
All.
TC_enable_backup_modes
DESCRIPTION
Determines whether backup functionality is enabled.
The integrated backup and recovery feature facilitates third-party backup systems
to perform online backup, allowing Teamcenter to operate continually. This

functionality focuses on the area of backing up metadata and math data, and
recovering that data in different restoration scenarios. To accomplish this, the
integrated backup feature places Teamcenter in different operation modes using the
backup_modes utility.
For more information about using the backup functionality, see the System
VALID
VALUES
true Enables backup functionality.
false Disables backup functionality.
DEFAULT
VALUES
false
SCOPE
Site preference.
Action manager daemon preferences

The action manager daemon dispatches events given a deferred execution time at
the time specified, as well as events intended for immediate dispatch that failed to
dispatch immediately. Information regarding events with a deferred execution time
are stored in the Teamcenter database as action objects. The action object contains
the information necessary to process the event, including event type, execution time,
and the user who generated the event.
At defined intervals, this daemon searches for action objects stored in the Teamcenter
database. It determines which of the objects are due for execution and processes a
defined number of these objects. To avoid memory leak problems, this daemon clones
and then terminates itself on a regular basis.
Define the duration of the action manager daemon’s sleep and wake cycles, the
number of objects processed, and its cloning intervals using the following site
preferences.
TC_actionmgrd_sleep_minutes
DESCRIPTION
Defines the number of minutes in the sleep period of the actionmgrd process
daemon between dispatching cycles.
VALID
VALUES
Positive integer up to 1440 (the number of minutes in a 24-hour day).
DEFAULT
VALUES
10
SCOPE
Site preference.

TC_actionmgrd_general_processing_hours
DESCRIPTION
Allows you to define processing periods for the actionmgrd process daemon at
specified times during a 24-hour day. Use this preference as an alternative to the
TC_actionmgrd_sleep_minutes site preference, which is based upon a continuous
sleep/dispatch cycle.
VALID
VALUES
Set this preference using the following syntax:
time range1(sm, mtd);time range2(sm, mtd);time range3(sm, mtd);
time range
Specifies the time range based on a 24-hour clock, expressed in hours and
minutes.
sm
Specifies the sleep minutes applicable during the defined time range. If omitted,
the value of the TC_actionmgrd_sleep_minutes site preference is used.
mtd
Specifies the maximum number of objects to dispatch. If omitted, the value of
the TC_actionmgrd_max_actions_to_dispatch site preference is used.
For example:
TC_actionmgrd_general_processing_hours=
0:00–7:00;12:00–13:00(1,100);18:00–22:00(,50)
Processing is allowed from midnight to 7 a.m. Because neither sleep minutes nor the
maximum number of objects to dispatch are specified, the values of the applicable
site preferences are used.
Processing is allowed from noon to 1 p.m. Because the sm is defined as 1, the sleep
time of the daemon is for 1 minute during this time. Since the mtd is defined
as 100, the daemon dispatches 100 events after every one minute of sleep during
the time range.
Processing is allowed from 6 p.m. to 10 p.m. Because the sm is omitted, the value of
the TC_actionmgrd_sleep_minutes site preference is used. Because the mtd is
defined as 50, the daemon dispatches 50 events every time it processes.
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_actionmgrd_max_actions_to_dispatch
DESCRIPTION
Defines how many action events are dispatched every time the actionmgrd process
daemon processes actions events in the queue. Only the action events determined
to be ready for execution are processed.
VALID
VALUES
Positive integer up to 500.
DEFAULT
VALUES
50
SCOPE
Site preference.
TC_actionmgrd_max_subprocess_to_start
DESCRIPTION
Defines how many events the actionmgrd process daemon dispatched by creating
a separate subprocess to be run by a workflow action handler. Once the defined
number is exceeded, the daemon does not dispatch any event requiring an action
handler to execute as a separate subprocess.
VALID
VALUES
DEFAULT
VALUES
10
SCOPE
Site preference.
TC_actionmgrd_cloning_interval
DESCRIPTION
Defines the number of cycles the actionmgrd process daemon completes before
cloning and terminating itself to avoid memory leak problems.
VALID
VALUES
Positive integer from 20 to 200.
DEFAULT
VALUES
100
SCOPE
Site preference.

Subscription Manager preferences

The Subscription Manager daemon searches the Teamcenter database for
subscriptions to the object for a given event type. When a subscription event
occurs (such as when an object is released), an event object is created to capture
that event and stored in a queue in the database. Event types act as the catalyst
for the subscriptionmgrd daemon, causing it to search for subscriptions to the
object for the given event type.
For more information about this daemon, see the System Administration Guide.
TC_subscriptionmgrd_sleep_minutes
DESCRIPTION
Defines the number of minutes in the sleep period of the subscriptionmgrd process
daemon between dispatching cycles.
VALID
VALUES
Positive integer up to 1440 (the number of minutes in a 24-hour day).
DEFAULT
VALUES
10
SCOPE
Site preference.
TC_subscriptionmgrd_processing_hours
DESCRIPTION
Allows you to define processing periods for the subscriptionmgrd process daemon
at specified times during a 24-hour day. Use this preference as an alternative to
the TC_subscriptionmgrd_sleep_minutes site preference, which is based on a
continuous sleep/dispatch cycle.
VALID
VALUES
time range1(sm, mtd);time range2(sm, mtd);time range3(sm, mtd);
time range
Specifies the time range based on a 24-hour clock, expressed in hours and
minutes.
sm
Specifies the sleep minutes applicable during the defined time range. If omitted,
the value of the TC_subscriptionmgrd_sleep_minutes site preference is used.
mtd
Specifies the maximum number of objects to dispatch. If omitted, the value of
the TC_subscriptionmgrd_max_subscriptions_to_dispatch site preference
is used.

For example:
TC_actionmgrd_general_processing_hours=
0:00–7:00;12:00–13:00(1,100);18:00–22:00(,50)
Processing is allowed from midnight to 7 a.m. Because neither sleep minutes nor the
maximum number of objects to dispatch are specified, the values of the applicable
site preferences are used.
Processing is allowed from noon to 1 p.m. Because the sm is defined as 1, the sleep
time of the daemon is for 1 minute during this time. Since the mtd is defined
as 100, the daemon dispatches 100 events after every one minute of sleep during
the time range.
Processing is allowed from 6 p.m. to 10 p.m. Because the sm is omitted, the value of
the TC_subscriptionmgrd_sleep_minutes site preference is used. Because the
mtd is defined as 50, the daemon dispatches 50 events every time it processes.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_subscriptionmgrd_max_subscriptions_to_dispatch
DESCRIPTION
Defines how many subscriptions the subscriptionmgrd process daemon are
dispatched each time it processes TcObjects (not event objects) queued in the
VALID
VALUES
DEFAULT
VALUES
50
SCOPE
Site preference.
TC_subscriptionmgrd_cloning_interval
DESCRIPTION
Defines the number of cycles the subscriptionmgrd process daemon completes
before cloning and terminating itself to avoid memory leak problems.
VALID
VALUES
Positive integer from 20 to 200.
DEFAULT
VALUES
100
SCOPE
Site preference.

TC_notification_msg_ext
DESCRIPTION
Defines the file type attached with Global Change notification e-mail. The system
sends .tmp files by default, which may be blocked by MS Outlook as potentially
harmful files.
VALID
VALUES
Accepts a single string as a value. Must be a valid file type extension.
DEFAULT
VALUES
.tmp
SCOPE
Site preference.
Subscription Monitor preferences

Subscription Monitor is used by system administrators to query subscriptions
created in the database and manage subscription modifications and to monitor and
delete subscription events and actions. Deleting subscription actions does not delete
the actual subscriptions. System administrators can use Subscription Monitor to
delete any active subscription. You can also use Subscription Monitor to generate
statistical reports in either text or bar chart format regarding subscriptions, events
and actions.
Subscription Manager is used by general users to search for, delete, and modify active
subscriptions. Users can search for, delete, and modify subscriptions they create.
System administrators can search for, delete, and modify all active subscriptions.
Use Subscription Monitor preferences to enable Subscription Manager, and to modify
the Subscription Monitor display.
TC_subscription
DESCRIPTION
Enables or suppresses subscription functionality.
VALID
VALUES
ON Enables subscription functionality.
OFF Suppresses subscription functionality.

DEFAULT
VALUES
OFF
SCOPE
Site preference.

TC_refresh_notify
DESCRIPTION
Determines whether refresh notification functionality is enabled. Refresh
notification allows users to be notified by the system when objects are changed by
other users. When refresh notification is enabled, users can subscribe to the objects,
types, or events for which they receive refresh notification, view a list of objects that
have been modified by other users and require refresh, and choose which objects to
refresh.
For more information about using this functionality once it is enabled, see the Rich
Client Interface Guide.
This preference is used in conjunction with the TC_refresh_notify_scope
preference.
Note
The Subscription Manager daemon (subscriptionmgrd) must be run to
clean up subscriptions and events that become invalid due to unexpected
session terminations.
For more information about this daemon, see the System Administration
Guide.
VALID
VALUES
ON Enables refresh notification functionality.
OFF Suppresses refresh notification functionality.
DEFAULT
VALUES
OFF
SCOPE
All.
TC_refresh_notify_scope
DESCRIPTION
Determines at what level (site, group, or role) refresh notification functionality is
enabled. For example, if the value is set to Group, refresh notification is enabled
at the group level. Members of the group can enable/disable this functionality. If
setting this preference to Role or Group, your current group/role logon determines
which group and role are affected.
This preference is used in conjunction with the TC_refresh_notify preference.
Refresh notification allows users to be notified by the system when objects are
changed by other users. When refresh notification is enabled, users can subscribe to
the objects, types, or events for which they receive refresh notification, view a list
of objects that have been modified by other users and require refresh, and choose
which objects to refresh.

VALID
VALUES
User All users can enable/disable this functionality.
Role Role members can enable/disable this functionality.
Group Group members can enable/disable this functionality.
Site Site administrators can enable/disable this functionality.
DEFAULT
VALUES
User
SCOPE
Site preference.
TC_refresh_notify_subscribe_to_types
DESCRIPTION
Defines which types can be selected for refresh notification. Refresh notification
can then be performed upon objects belonging to the specified types. For example,
items and item revisions.
This preference is used in conjunction with the TypeName_subscribe_to_events
preference.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter type.
For example:
Item
ItemRevision
Child types do not automatically inherit refresh notification from parent types.
DEFAULT
VALUES
None.
SCOPE
All.
<TypeName>_subscribe_to_events
DESCRIPTION
Defines the list of events for which refresh notification is sent, whenever those
events occur on the objects of the specified type. (Which types available for
refresh notification are defined via the TC_refresh_notify_subscribe_to_types
preference.) You must create a separate preference for each Teamcenter type eligible

for refresh notification; the values of each preference define the events for which
refresh notification is sent.
VALID
VALUES
Accepts multiple preferences, each preference beginning with a valid Teamcenter
type name where the TypeName portion of each preference name must correspond
with a type name defined in the TC_refresh_notify_subscribe_to_types
preference. The TC_refresh_notify_subscribe_to_types preference defines which
types can be selected for refresh notification.
Accepts multiple strings as values, each string must be a valid event type.
For example:
Item_subscribe_to_events=
_Modify
_Check_In
ItemRevision_subscribe_to_events=
_Modify
_Check_Out
_Delete
DEFAULT
VALUES
None. If no TypeName_subscribe_to_events preferences are created, it is
assumed that Modify is the only event type tracked for the types defined in the
TC_refresh_notify_subscribe_to_types preference.
SCOPE
All.
TC_refresh_notify_pull_time_interval
DESCRIPTION
Determines how often, in minutes, the system automatically performs refresh
notification. (Users can manually invoke this functionality using the Refresh
Notification dialog box at any time.)
VALID
VALUES
Accepts a single string as value. Must be a positive integer.
DEFAULT
VALUES
15
SCOPE
All.

TC_refresh_notify_list_maximum
DESCRIPTION
Determines the maximum number of objects contained in the refresh notification list.
Limiting the number of objects postpones processing the events of less important
objects. Use this preference for tuning refresh notification performance.
VALID
VALUES
Accepts a single string as value. If set to 0, a negative integer, or not set, there is no
restriction on the number of objects sent to the refresh notification list.
DEFAULT
VALUES
None.
SCOPE
All.
TC_automatic_refresh_waiting_time
DESCRIPTION
Determines the waiting time, in minutes, before the system automatically refreshes
data, upon receiving refresh notification.
VALID
VALUES
Accepts a single string as value. If set to 0 or a negative integer, the system
immediately refreshes the object after receiving refresh notification.
DEFAULT
VALUES
0
SCOPE
All.
TC_automatic_refresh_time_interval
DESCRIPTION
Determines the time interval, in minutes, for performing each automatic refresh.
VALID
VALUES
DEFAULT
VALUES
10
SCOPE
All.

TC_automatic_refresh_list_maximum
DESCRIPTION
Determines the maximum number of the objects the system will refresh at a time.
Use this preference to avoid refreshing a large number of objects at a time and
decreasing performance. This preference is used for tuning refresh notification
performance.
VALID
VALUES
Accepts a single string as value. If set to 0 or a negative integer, there is no limit on
the number of objects refreshed at one time.
DEFAULT
VALUES
None.
SCOPE
All.
TC_refresh_notify_timed_out
DESCRIPTION
Determines the time interval, in minutes, during which transient session
subscriptions are valid after a user’s session is timed out.
VALID
VALUES
DEFAULT
VALUES
0
SCOPE
Site preference.
Mail_subscription_notify_sub_groups_too
DESCRIPTION
Determines whether to include subgroups in subscription notification.
VALID
VALUES
TRUE Subgroups are included in subscription notification.
FALSE Subgroups are not included in subscription notification.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.

TC_subscription_log_event_and_action_status
DESCRIPTION
Determines whether to log the status of TcEvent and TcAction objects via the
subscriptionmgrd and actionmgrd process daemons.
VALID
VALUES
ON The subscriptionmgrd process daemon logs the status of each TcEvent
object that it processes. The actionmgrd process daemon logs the status of
each TcAction object that it processes.
OFF Neither process daemon logs the status of their respective objects as they
are processed.
DEFAULT
VALUES
OFF
SCOPE
Site preference.
TcSubscriptionColumnPreferences
DESCRIPTION
Specifies the columns displayed in the subscription table.
VALID
VALUES
Any attributes available in the Teamcenter schema.
DEFAULT
VALUES
target
object_type
subscriber
event_type
handler_parameters
expiration_date
execution_time
SCOPE
All.
TcSubscriptionColumnWidthPreferences
DESCRIPTION
Specifies the column widths displayed in the subscription table.
VALID
VALUES
One or more integers as values; each integer defines the column width in characters.
The first value set in this preference defines the column width of the first value set
in the TcSubscriptionColumnPreferences user preference, and so on.

DEFAULT
VALUES
30
15
15
30
15
15
SCOPE
All.
TcEventColumnPreferences
DESCRIPTION
Specifies the columns displayed in the event table.
VALID
VALUES
Any attributes available in the Teamcenter schema; though only attributes belonging
to the following classes yield pertinent results:
EventTypeMapping
TcAction
TcEvent
TcEventType
TcSubscription
DEFAULT
VALUES
objectstr_of_target
target_object_type
event_type
event_initiator
event_time
SCOPE
All.
TcEventColumnWidthPreferences
DESCRIPTION
Specifies the column widths displayed in the event table.
VALID
VALUES
in the TcEventColumnPreferences user preference, and so forth.
DEFAULT
VALUES
30

15
15
15
15
SCOPE
All.
TcActionColumnPreferences
DESCRIPTION
Specifies the columns displayed in the action table.
VALID
VALUES
Any attributes available in the Teamcenter schema; though only attributes belonging
to the following classes yield pertinent results:
EventTypeMapping
TcAction
TcEvent
TcEventType
TcSubscription
DEFAULT
VALUES
Default values include:
objectstr_of_target
target_object_type_name
eventtype_id
subscriber
event_initiator
event_time
handler_parameters
execution_time
retries_togo
SCOPE
All.
TcActionColumnWidthPreferences
DESCRIPTION
Specifies the column widths displayed in the action table.
VALID
VALUES
in the TcActionColumnPreferences user preference, and so on.
DEFAULT
VALUES
30

15
15
15
15
15
30
15
15
SCOPE
User preference.
SCM_notification_history
DESCRIPTION
Determines whether the notification history record is enabled or disabled.
VALID
VALUES
true Enables notification e-mail.
false Suppresses notification e-mail.
DEFAULT
VALUES
false
SCOPE
Site preference.
SCM_notification_WorkspaceObject_props
DESCRIPTION
Defines the default properties to be included in notification e-mails.
VALID
VALUES
Any attributes available in the Teamcenter schema.
DEFAULT
VALUES
object_string
object_type
SCOPE
Site preference.
File caching preferences

File caching improves performance when accessing files in Teamcenter volumes over
a WAN by reducing the number of times a file needs to be copied to the user’s local
machine. File caching is intended to improve performance for users working on the
same parts/assemblies over multiple sessions. For optimal performance, Siemens

PLM Software recommends that the file cache be on the local machine in order to
avoid performance degradation caused by network traffic.
File caching is only intended to work with certain files, such as NX-related files
and JT files transferred to the client.
The first time a file is accessed from a volume it is locally cached based on the
settings of the file caching preferences. Once a file is cached, all further read access
to that file takes place from the cache instead of the volume. The files placed into the
cache are owned by the user and have read-only access.
Caching modes
There are two different access modes: socket mode and NFS mode.
Socket mode
The first time a file is accessed in socket mode the performance should be the
same as if caching was not enabled. However, subsequent attempts to access the
file should show improved performance. The degree of improvement depends on
the network involved.
NFS mode
The first time a file is accessed when file caching is enabled in NFS mode,
there is some degradation of performance due to the file being copied into the
cache. However, the performance during subsequent attempts to access the file
should be improved, because the file is now being accessed locally. The degree
of improvement depends on the network involved.
Cache purging
Automatic purging of the cache is not supported; however, the cache can be manually
purged using the purge_file_cache utility. This utility purges the cache based on
the last access date of the files and also checks each file to make sure it still exists
within the Teamcenter volume.
syslog file output

When file caching is enabled, the following information is output to the syslog file:
• The location of the cache, as defined by the TC_Cache_Dir preference.
• The maximum size of the cache, as defined by the TC_Cache_Size preference.
• The current size of files in the cache at startup.
• The read/write status of the cache.
• The size of the cache if the maximum cache size has been exceeded. Once the
cache has exceeded its size limit, no additional files are written to the cache.
• A message regarding the failure to place files in cache is reported from the
IMF_export function. This message includes the file access method used in
lieu of placing the files in the cache.
File caching preferences

Use file caching preferences to enable file caching, define which file caching mode is
used, and configure caching functionality.

TC_Cache_Allowed
DESCRIPTION
Determines whether local file caching is enabled. This site preference must be
manually entered into the database. Create new preferences using the Options
dialog box, accessed from the Edit menu in the rich client.
VALID
VALUES
ON Enables local file caching.
OFF Disables local file caching.
DEFAULT
VALUES
OFF
SCOPE
Site preference.
TC_Cache_Dir
DESCRIPTION
Defines the directory to which files are cached. The TC_Cache_Allowed preference
must be set to ON before defining a cache directory. This preference must be
manually entered into the database. Create new preferences using the Options
VALID
VALUES
Any directory to which the user has write access.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_Cache_Size
DESCRIPTION
Defines the size of the cache in megabytes. Files stop being cached if the size of the
files in the cache directory reach the cache size specified.
The TC_Cache_Allowed preference must be set to ON and the TC_Cache_Dir
preference must be defined before this preference can be used. This preference must
be manually entered into the database. Create new preferences using the Options

VALID
VALUES
Any integer greater than zero.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_Cache_Mode
DESCRIPTION
Determines which mode of file caching is used. This preference must be manually
entered into the database. Create new preferences using the Options dialog box,
accessed from the Edit menu in the rich client.
VALID
VALUES
ALL All files are cached, regardless of how they are accessed from
the volume.
NONE No new files are cached. Previously cached files can be
accessed.
MOUNTED The Teamcenter volume files are accessed by socket transfer
and the volume is NFS mounted.
NOT_MOUNTED The Teamcenter volume files are accessed by socket transfer,
the volume is not NFS mounted.
DEFAULT
VALUES
NOT_MOUNTED
SCOPE
Site preference.
TC_<file type>_Cache_Mode
DESCRIPTION
Enables file caching for a specific file type. The file extension defined in this
preference overrides the TC_Cache_Mode preference for the given file type. In
the following example, .gif files are cached regardless of whether the Teamcenter
File Services access mode is NFS or Socket, .xls files are not cached at all, and
all other file types are cached only if the Teamcenter File Services transfer mode
is NFS access:
TC_Cache_Mode=
MOUNTED
TC_gif_Cache_Mode=
ALL
TC_xls_Cache_Mode=
NONE

This preference must be manually entered into the database. Create new preferences
using the Options dialog box, accessed from the Edit menu in the rich client.
VALID
VALUES
Valid file types.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_Cache_Protection
DESCRIPTION
Defines the operating system protections applied to files stored in the file cache.
This preference is valid only if the TC_Cache_Allowed, TC_Cache_Dir, and
TC_Cache_Size preferences are set. This preference must be manually entered
into the database. Create new preferences using the Options dialog box, accessed
from the Edit menu in the rich client.
VALID
VALUES
UNIX systems:
USER The caching user has access.
GROUP Members of the caching user’s group have access.
WORLD All users have access.
Windows systems:
USER The caching user has access.
WORLD All users have access.
DEFAULT
VALUES
USER
SCOPE
Site preference.
TC_STAGING_AREA
DESCRIPTION
Defines temporary directory for storing data when using the object_recover utility.
If this preference is not set, the current working directory is used.
VALID
VALUES
directory.

DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_System_Logging
DESCRIPTION
Enables or suppresses system logging for the entire site. System logging creates a
record of global system events such as object releases.
VALID
VALUES
ON Enables system logging.
OFF Suppresses system logging.
DEFAULT
VALUES
ON
SCOPE
Site preference.
Ticket_Expiration_Interval
DESCRIPTION
Specifies how long, in seconds, the ticket is good for access. Add this value to the
current time when the ticket is generated to calculate the ticket expiration time.
Environment variable settings override this FCC configuration file setting.
VALID
VALUES
DEFAULT
VALUES
28800 seconds (8 hours)
SCOPE
Site preference.
Multisite_Ticket_Expiration_Interval
DESCRIPTION
Specifies how long, in seconds, the ticket is good for access. Add this value to the
current time when the ticket is generated to calculate the ticket expiration time.
Environment variable settings override this FCC configuration file setting.
VALID
VALUES

DEFAULT
VALUES
259200 seconds (72 hours)
SCOPE
Site preference.
blobbyVolume_NT
DESCRIPTION
Specifies an alternate volume location on a Windows platform, allowing for constant
Teamcenter availability during hot backup.
VALID
VALUES
Accepts a single string as a value. Must be a valid volume location. Maximum
character length of the string is 15 characters. For example:
c:\temp
DEFAULT
VALUES
None.
SCOPE
Site preference.
blobbyVolume_UNX
DESCRIPTION
Specifies an alternate volume location on a UNIX platform, allowing for constant
Teamcenter availability during hot backup.
VALID
VALUES
Accepts a single string as a value. Must be a valid volume location. Maximum
character length of a string is 15 characters. For example:
/tmp
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_Volume_Status_Resync_Interval
DESCRIPTION
Indicates the minimum amount of time (in seconds) that must pass before the
percentage full value of a volume is retrieved from the FSC. The percentage full
values are cached to prevent excessive FSC requests.

The system only checks for this cached value during file import, and only
when volume failover during file import behavior is enabled by setting the
TC_Volume_Failover_Volume_Name preference.
VALID
VALUES
Accepts a single positive integer as a value.
Siemens PLM Software recommends keeping this setting similar to the default
value. Setting this value too high causes the cached percentage full value to be out of
date. Setting this value too low generates excessive FSC requests.
DEFAULT
VALUES
600
SCOPE
Site preference.
TC_Volume_Failover_Trigger
DESCRIPTION
Specifies the percentage full a volume must reach to trigger volume failover behavior
for importing files. When volume capacity reaches the percentage full specified by
this preference, importing files are directed to the failover volume specified by the
TC_Volume_Failover_Volume_Name preference.
This preference setting is used by the system only when the
TC_Volume_Failover_Volume_Name preference is set.
VALID
VALUES
Accepts a single float value, from 0–100.
Siemens PLM Software recommends setting this preference between 80 and 95.
Setting this value too low triggers failover behavior too often. Setting this value too
high prevents failover behavior from initiating.
DEFAULT
VALUES
90.0
SCOPE
Site preference.
TC_Volume_Failover_Volume_Name
DESCRIPTION
Specifies the volume to use in failover situations during file import. Setting this
preference with a volume name prompts the system to check the original target
volume before import. If the target volume is filled beyond the capacity specified by
the TC_Volume_Failover_Trigger preference, the imported file is directed to the
failover volume specified by this preference.
VALID
VALUES
Accepts a single string as a value; the string must be a valid volume name.

DEFAULT
VALUES
None
SCOPE
Site preference.
TC_VOLUME_MONITOR_WARNING_LEVEL
DESCRIPTION
Specifies the percentage full a volume must reach to achieve warning level.
When a volume’s capacity reaches warning level, its volume data is colored yellow in
the Volume Monitor view of the Volume Management perspective. Additionally, such
volumes display when filtering the table tree to list only volumes with a severity of
Warning.
For more information about how warning levels display in Volume Monitor, see
the Volume Management Guide.
VALID
VALUES
Accepts a single value between 1 and 99, inclusive. The value must be less than the
value set for the TC_VOLUME_MONITOR_CRITICAL_LEVEL preference.
DEFAULT
VALUES
80
SCOPE
All.
TC_VOLUME_MONITOR_CRITICAL_LEVEL
DESCRIPTION
Specifies the percentage full a volume must reach to achieve critical level.
When a volume’s capacity reaches critical level, its volume data is colored red in the
Volume Monitor view of the Volume Management perspective. Additionally, such
volumes display when filtering the table tree to list only volumes with a severity of
Critical.
For more information about how critical levels display in Volume Monitor, see the
Volume Management Guide.
VALID
VALUES
Accepts a single value between 1 and 99, inclusive. The value must be greater than
the value set for the TC_VOLUME_MONITOR_WARNING_LEVEL preference.
DEFAULT
VALUES
90
SCOPE
All.

Transient_Volume_Installation_Location
DESCRIPTION
Specifies the node name of the transient volume. It is a location-based logical
identifier, and is generally set to the host name of the local machine by the
tc_profilevars script. When a four-tier transient volume is mounted on all
Teamcenter server hosts at a given location, use this setting to configure the
distributed transient volume. The environment variable of the same name overrides
this preference setting.
VALID
VALUES
Accepts a single value. It must be a valid host name.
DEFAULT
VALUES
None.
SCOPE
All.
Transient_Volume_RootDir
DESCRIPTION
Specifies the transient volume’s root directory. This preference accepts multiple
values to support a UNIX/Windows heterogeneous site. FMS takes the first value
which is valid for the platform, UNIX or Windows; the validity check is simply the
presence or absence of a backslash (\) character. Environment variable settings
override this FCC configuration file setting.
Transient volumes are file locations to which tcserver processes have direct access.
These locations are typically used for server side file generation operations such
as PLM XML files. Files within transient volumes are typically generated by the
tcserver, read by a client (usually) once, then deleted.
This preference is set during the initial database population. Its value should
not be changed, even if several other Teamcenter installations point to the
same pre-populated database. If you must change the value, see the System
VALID
VALUES
Accepts multiple values, in order to support a UNIX/Windows heterogeneous site.
For example:
Transient_Volume_RootDir=
C:\temp
/tmp
DEFAULT
VALUES
None.
SCOPE
Site preference.

Default_Transient_Server
DESCRIPTION
Specifies the default transient file server location. Environment variable settings
override this FCC configuration file setting.
VALID
VALUES
Accepts a single value. Must be a valid transient file server location. For example:
Default_Transient_Serrver=
http://www.transientserver.com
DEFAULT
VALUES
None.
SCOPE
Site preference.
Default_Transient_Volume_Id
DESCRIPTION
Defines the corporate server transient volume. This preference must be defined to
enable transfer of multi-site export metadata from site to site when running in a
two-tier environment.
VALID
VALUES
Accepts a single value. Must be a valid transient volume ID.
DEFAULT
VALUES
None.
SCOPE
All.
Fms_BootStrap_Urls
DESCRIPTION
Determines which FMS server cache manages file downloads. When searching for
an assigned FMS server cache to manage file downloads, the thin client contacts the
FSC servers defined in this preference in the order listed. The server responds
with the FSC server assigned to the thin client, and all subsequent communication
is with that assigned server cache. Environment variable settings override this
FCC configuration file setting.
If there is only the thin client and one FSC server in the network, you must select
this option. Each Teamcenter network must have at least one server listed in the this
preference for thin client use. For failover purposes, you can include multiple servers.

VALID
VALUES
Accepts multiple strings as values. Each string must be a valid server location.
For example:
Fms_BootStrap_Urls=
http://abc.com
http://def.com:4040
http://ghi.com
DEFAULT
VALUES
None.
SCOPE
Site preference.
FSC_HOME
DESCRIPTION
Specifies the location of the as-installed code, including the fsc.cfg and bin files.
Environment variable settings override this FSC configuration file setting.
VALID
VALUES
Accepts a single value. Must be a valid Teamcenter directory.
DEFAULT
VALUES
Value set during installation.
SCOPE
Site preference.
UNLOAD_TRIGGER_CEILING
DESCRIPTION
Initiates the automatic cleanup of unused objects from the server memory. Specifies
(in kilobytes) what memory size must be reached to initiate the unloading of unused
objects from server memory.
Automatic cleanup is performed during the operation occurring after the specified
ceiling is reached. Thus, the specified memory size might be exceeded if the final
loading action uploads a large amount of data.
For example, if this preference is set to 12000 and memory consumption is at 11900
KB, at least one more load operation is required before the ceiling is reached. If the
next load operation adds a large amount of data, such as 20000 KB, total memory
consumption is 31900 KB when the automatic cleanup begins.

Note
Automatic cleanup of unused objects is enabled by default. This cleanup
alleviates increased memory issues.
For more information about disabling this behavior, see the System
Setting the value very low reduces the memory server footprint, but decreases
performance.
For more information about configuring the automatic cleanup of unused objects
from the server memory, see the System Administration Guide.
VALID
VALUES
Accepts any positive integer. The number must be higher than the value set for the
UNLOAD_TRIGGER_FLOOR preference. If an invalid value is set, the default
value is used. Invalid values are:
• A negative number
• A number lower than the value set for the UNLOAD_TRIGGER_FLOOR

preference
• Nonnumerical characters
Setting the value very low reduces the memory server footprint but decreases
performance because most loaded objects are quickly unloaded, and when reloaded,
must be unloaded again.
DEFAULT
VALUES
12000
SCOPE
All.
UNLOAD_TRIGGER_FLOOR
DESCRIPTION
Stops the automatic cleanup of unused objects from the server memory. Specifies (in
kilobytes) what memory size must be reached to stop the unloading of unused objects
from server memory after memory cleanup has begun.
Automatic cleanup continues until the memory size specified by this preference is
achieved. However, if the total size of ummovable object exceeds the floor amount,
the specified memory size is not reached.
For example, if objects cannot be removed because their life span does not meet
the requirements specified by the UNLOAD_MINIMUM_LIFE preference, and
the memory space consumed by these objects exceed the specified floor size, the
specified memory size is not reached.

Note
Automatic cleanup of unused objects is enabled by default. This cleanup
alleviates increased memory issues.
For more information about disabling this behavior, see the System
Determining the optimum value for this preference requires investigation, and
possibly experimentation in a working environment.
For more information about configuring the automatic cleanup of unused objects
from the server memory, see the System Administration Guide.
VALID
VALUES
Accepts any positive integer. The number must be higher than the value set for the
UNLOAD_TRIGGER_CEILING preference. If an invalid value is set, the default
value is used. Invalid values are:
• A negative number
• A number lower than the value set for the UNLOAD_TRIGGER_CEILING

preference
• Nonnumerical characters
DEFAULT
VALUES
5000
SCOPE
All.
UNLOAD_MINIMUM_LIFE
DESCRIPTION
Determines which unused objects are qualified for memory cleanup, based on when
objects were last accessed.
VALID
VALUES
Accepts any positive integer. The value specifies (in seconds) when an object must
have been last accessed to be qualified for memory cleanup. Objects accessed more
recently than the specified value are not removed from server memory.
DEFAULT
VALUES
1800
SCOPE
All.

UNLOAD_LOGGING_LEVEL
DESCRIPTION
Determines the level of detail logged in the in-session and end-session reports sent
to the .unloadlog log file.
VALID
VALUES
0 No log file is created.
1 In-session report includes number of cache objects and unload
time. End session report includes total number of objects
unloaded and the average unload time.
2 In-session report includes all information from a level 1 report,
as well as memory usage before and after loading. End-session
report includes all information from a level 1 report.
as well as callback information. End-session report includes
all information from a level 2 report, as well summary unload
reports by type.
as well object types loaded and unloaded from the cache.
End-session report includes all information from a level 3
report.
For a complete list of information included in the reports, see the System
DEFAULT
VALUES
0
SCOPE
All.
TC_Populate_FSC_Server_Targets
DESCRIPTION
Based on the preference value the exporting site decides to populate the files to
the specific file server cache (FSC) specified by the URL. Multi-Site features use a
default populate target FSC ID for populating files that can be overridden by this
preference. The exporting site interrogates the importing site for the this preference.
VALID
VALUES
A character string representing the FSCID, for example:
FSC_tri6w035_nox
DEFAULT
VALUE
None.
SCOPE
Site preference.

RESTRICTIONS
Precaching data is supported only within an enterprise and only on the FSCs defined
in the local FMSMaster.xml file (in the FSC_HOME directory).
Log file preferences

Teamcenter saves information in various log files. Access log files to obtain valuable
troubleshooting information.
For more information about log files, see the System Administration Guide.
Use log file preferences to enable and configure log file functionality.
TC_Administration_Logging
DESCRIPTION
Enables or suppresses administration logging for the entire site. Administration
logging creates a record of Teamcenter system administration activities such as
creating new users, volumes, and so forth.
VALID
VALUES
ON Enables administrative logging.
OFF Suppresses administrative logging.
DEFAULT
VALUES
ON
SCOPE
Site preference.
TC_Security_Logging
DESCRIPTION
Enables or suppresses security logging for the entire site. Security logging
creates a record of invalid access of Teamcenter objects and writes the data to
the $TC_LOG/security.log file. Enabling security logging also requires creating
a file named security.log in the TC_DATA directory. The system first checks for
the existence of this file; if it exists, it checks the value of this preference. If set to
ON, security logging is enabled.
VALID
VALUES
ON Enables security logging.
OFF Suppresses security logging.
DEFAULT
VALUES
ON
SCOPE
Site preference.

TC_allow_inherited_group_volume_access
DESCRIPTION
Allows a group to inherit access to a Teamcenter volume from its parent group.
That is, if a group is explicitly granted volume access, and this preference is set to
a nonzero number, that group’s subgroups (and its subsubgroups) are implicitly
granted access to that volume.
VALID
VALUES
0 Does not allow groups to inherit access to a volume from its parent group.
Single Allows groups to inherit access to a volume from its parent group.
positive
integer
DEFAULT
VALUES
0
SCOPE
Site preference.
TC_Application_Logging
DESCRIPTION
Enables or suppresses application logging for the entire site. Application log files are
records of events for applications such as My Teamcenter, Structure Manager, or any
Teamcenter utility. These files are stored in the $TC_TMP_DIR directory.
VALID
VALUES
ON Enables application logging.
OFF Suppresses application logging.
DEFAULT
VALUES
ON
SCOPE
All.
TC_Installation_Logging
DESCRIPTION
Enables or suppresses installation logging for the entire site. Contains a record
of activities performed by the Teamcenter Environment Manager installation
program. This log file is in the install directory under the application root directory.
The date-time stamp represents the date and time Teamcenter Environment
Manager was run. For example, install0522241627.log indicates that Teamcenter
Environment Manager was run at 4:27 on February 24, 2005.

VALID
VALUES
ON Enables installation logging.
OFF Suppresses installation logging.
DEFAULT
VALUES
ON
SCOPE
Site preference.
TC_Journalling
DESCRIPTION
Determines whether calls to the ITK are logged in journal files. The data is written
to the program.jnl file.
VALID
VALUES
ON Enables journalling.
OFF Suppresses journalling.
DEFAULT
VALUES
OFF
SCOPE
Site preference.
TC_Journal_Modules
DESCRIPTION
Determines which Teamcenter modules create application journal files when the
TC_Journalling preference is set to On.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter
application module.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_KEEP_SYSTEM_LOG
DESCRIPTION
Determines whether to retain new system log files if they do not contain errors.

VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_TMP_DIR
DESCRIPTION
Defines the temporary directory for storing application log files.
VALID
VALUES
directory.
DEFAULT
VALUES
None.
SCOPE
Site preference.
RECOVER_TO_UNRELEASED_STATUS
DESCRIPTION
Enables or suppresses recovering released objects to unreleased status when using
the object_recover utility.
VALID
VALUES
YES Released objects are not recovered.
NO Released object is recovered from the backup metafile
DEFAULT
VALUES
None.
SCOPE
Site preference.
RECOVER_TO_VOLUME
DESCRIPTION
Determines which volume receives restored data when using the object_recover
utility. If this preference is not set, all recovered objects are stored to the current
active volume.
VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter volume.

DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_sfr_recovery_interval
DESCRIPTION
Specifies (in seconds) how often the system checks for recovered files after a
user-initiated single file recovery action is activated. This preference is used for
single file recovery.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_sfr_process_life_time
DESCRIPTION
Specifies (in minutes) how long the system continues to check for recovered files after
a user-initiated single file recovery action is activated.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.

Chapter
10 Client preferences
Rich client preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

AE_dataset_default_keep_limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
AI_ignore_ic_flag_setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
AI_Incremental_Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
AI_request_no_dependancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Allow_Copy_As_Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Attachment_Alias_File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
CCCompositionTypesPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
CCObject_default_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Change_Search_Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
copyPasteChunkNumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Create_<business_object>_default_type . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Create_WorkspaceObject_mru_list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Create_WorkspaceObject_mru_max . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
<dataset_name>.FORM_REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . . . 10-7
<dataset_name>.CREATE_REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . 10-7
<dataset_name>.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
<dataset_name>.SUMMARY_REGISTEREDTO . . . . . . . . . . . . . . . . . . . 10-9
DATASET_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
DATASET_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
DATASET_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
DATASET_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
DATASETTYPE_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . 10-12
DATASETTYPE_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . 10-12
DATASETTYPE_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
DATASETTYPE_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
DatasetTypesPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
DRAG_AND_DROP_Default_dataset_type . . . . . . . . . . . . . . . . . . . . . . 10-14
DRAG_AND_DROP_file_limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
DRAG_AND_DROP_SWING_dialog_enable . . . . . . . . . . . . . . . . . . . . . 10-15
Enable_thumbnails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
FLColumnCatIVFSeparatorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
FLColumnCatObjSeparatorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
FOLDER_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
FOLDER_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
FOLDER_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
FOLDER_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
FORM_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
FORM_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
FORM_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
FORM_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
FormTypesPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
GROUP_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20

GROUP_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
GROUP_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
GROUP_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
HiddenPerspectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
IDCAttachmentColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
IDCAttachmentColumnWidthsPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
IDCStructureColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
IDCStructureColumnWidthsPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
IdentifierContextTypeDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
IdentifierTypeDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
IMAN_3D_snap_shot_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . 10-25
IMAN_customization_libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
IMAN_FLASH_FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
IMANFILE_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
IMANFILE_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
IMANFILE_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
IMANFILE_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28
IMANTYPE_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28
IMANTYPE_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
IMANVOLUME_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . 10-29
IMANVOLUME_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . 10-30
IMANVOLUME_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
IMANVOLUME_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
<Item>.FilterCriteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
ITEM_first_rev_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
ITEM_id_postfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
ITEM_id_prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
ITEM_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
ITEM_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
ITEM_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
ITEM_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
<Item>.SUMMARYRENDERING2007 . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
<ItemRevision>.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
<ItemRevision1>_<ItemRevision2>_default_relation . . . . . . . . . . . . . . . 10-36
<ItemRevision>.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . . 10-36
ItemRevision_default_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37
ITEMREVISION_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . 10-37
ITEMREVISION_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . 10-38
ITEMREVISION_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . 10-38
ITEMREVISION_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . 10-39
ItemRevision_shown_relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39
ItemRevision_thumbnail_relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-40
ItemRevision_thumbnail_references . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41
Item_shown_relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41
ITEM_smart_baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42
<Item type>_rev_display_all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42
<Item type>_rev_display_order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42
<Item type>_rev_display_rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-43
JTTreeTableColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-44
JTTreeTableShownColumnWidthsPref . . . . . . . . . . . . . . . . . . . . . . . . . 10-44
LOV_hide_desc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-45
MECollaborationContext_default_relation . . . . . . . . . . . . . . . . . . . . . . . 10-45
MEOPRevision_shown_relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46
MEProcessRevision_shown_relations . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46

MySearchHistory_Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-47
OpenAfterCreatePref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-47
PERSON_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-47
PERSON_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
PERSON_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
PERSON_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-49
PSBOMVIEW_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . . 10-49
PSBOMVIEW_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . 10-50
PSBOMVIEW_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . 10-50
PSBOMVIEW_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-51
PSBOMVIEWREVISION_object_columns_hidden . . . . . . . . . . . . . . . . . 10-51
PSBOMVIEWREVISION_object_columns_shown . . . . . . . . . . . . . . . . . 10-52
PSBOMVIEWREVISION_object_widths_hidden . . . . . . . . . . . . . . . . . . 10-52
PSBOMVIEWREVISION_object_widths_shown . . . . . . . . . . . . . . . . . . . 10-53
QRYColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-53
QRY_dataset_display_option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54
QRY_<query_name>_SortKeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54
QRY_<query_name>_SortOrder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54
QRY_search_classification_hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . 10-55
QRY_search_type_hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-55
ReferencersPane_Shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-56
ReportDefinition_ColumnPreferences . . . . . . . . . . . . . . . . . . . . . . . . . . 10-56
ReportDefinition_ColumnWidthPreferences . . . . . . . . . . . . . . . . . . . . . 10-57
ReportGenerationDlg_ColumnPreferences . . . . . . . . . . . . . . . . . . . . . . 10-58
ReportGenerationDlg_ColumnWidthPreferences . . . . . . . . . . . . . . . . . . 10-58
RESERVATION_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . 10-59
RESERVATION_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . 10-59
RESERVATION_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . 10-60
RESERVATION_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . 10-60
Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-61
Select IR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-61
Structure_Alias_File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-62
TC_AE_<datasettype>_Default_View_Tool . . . . . . . . . . . . . . . . . . . . . . 10-62
TC_Allow_Longer_ID_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
TC_Auto_Checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
TC_auto_login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
TC_check_out_dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-64
TC_checkout_and_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-64
TC_control_wildcard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-64
TC_control_wildcard_exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-65
TC_days_non_login_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-65
TC_DISABLE_FLASH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-66
TC_display_group_names_limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-66
TC_display_real_prop_names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-67
TC_display_thumbnail_in_UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-67
TC_Graph_Node_Thumbnail_Shown . . . . . . . . . . . . . . . . . . . . . . . . . . 10-67
TC_GROUP_PFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-68
TC_ignore_case_on_search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-68
TC_inbox_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-69
TC_<datasettype>_Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-69
TC_markup_named_ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-70
TC_max_number_of_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-70
TC_name_delimiter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-71
TC_name_sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-71

TC_pattern_match_style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-72
TC_QRY_display_latest_dataset_only . . . . . . . . . . . . . . . . . . . . . . . . . . 10-72
TC_QRY_search_by_rev_rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-72
TC_remove_file_on_check_in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-73
TC_retry_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-73
TC_ROLE_PFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-74
TC_show_checkedout_icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-74
TC_suppress_Edit_Latest_Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-74
TC_suppress_inactive_group_members . . . . . . . . . . . . . . . . . . . . . . . . . 10-75
TC_Thumbnail_Tooltip_Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-75
TC_USER_PFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-75
TC_user_delimiters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-76
TCViewMarkupApplicationPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-76
TC_wc_allow_subgroup_default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-77
TC_wc_setting_modifiable_default . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-77
TC_wc_show_all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-78
TOOL_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-78
TOOL_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-79
TOOL_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-79
TOOL_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-80
Tracelink_deepcopy_on_Revise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-80
Tracelink_deepcopy_on_SaveAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-80
treeDisplayOrder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-81
<Type>_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-81
<type_name>.CREATERENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . 10-82
<Type_Name>_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . . . 10-82
<type_name>.FORMRENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-86
<type_name>.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-86
<type_name>.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . . . . 10-87
USER_object_columns_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-88
USER_object_columns_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-88
USER_object_widths_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-89
USER_object_widths_shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-89
WHERE_REFERENCED_RELATIONS_FILTER . . . . . . . . . . . . . . . . . . 10-89
Word_12_installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-90
WORKSPACEOBJECT_object_columns_hidden . . . . . . . . . . . . . . . . . . . 10-90
WORKSPACEOBJECT_object_columns_shown . . . . . . . . . . . . . . . . . . . 10-91
WORKSPACEOBJECT_object_widths_hidden . . . . . . . . . . . . . . . . . . . . 10-91
WORKSPACEOBJECT_object_widths_shown . . . . . . . . . . . . . . . . . . . . 10-92
WS_icon_placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-92
WSColumnsHiddenPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-93
WSColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-93
WSDisplayTypePref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-94
WS_expand_on_paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-94
WSHiddenColumnWidthsPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-94
WsoFolderSavePref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-95
WsoInsertNoSelectionsPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-95
WSOM_find_editUserList . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-96
WsoInsertSelectionsPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-96
WSOM_find_list_separator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-97
WSOM_find_set_search_limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-97
WSOM_find_set_total_limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-97
WSOM_only_edit_effectivity_in_ecm . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-98
WSShownColumnWidthsPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-98

Thin client preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-98
General thin client preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-99
appbar_title_contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-99
JT_WEB_UI_PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-100
TcUseAppLauncher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-100
WEB_active_optimizer_server . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-102
WEB_auto_assign_ds_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-102
WEB_<Class>_default_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-102
WEB_Change_default_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-103
WEB_core_help_server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-103
WEB_dataset_shown_relations . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-103
WEB_default_site_deployed_app_name . . . . . . . . . . . . . . . . . . . . . 10-104
WEB_default_site_server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-104
WEB_disable_structure_read_optimizations . . . . . . . . . . . . . . . . . 10-105
WEB_filter_person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-105
WEB_help_server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-105
WEB_filter_user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-106
WEB_protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-106
WEB_status_icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-107
WEB_dataset_upload_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-108
WEB_column_one_new_window . . . . . . . . . . . . . . . . . . . . . . . . . . 10-108
WEB_create_<business_object>_exclude_types . . . . . . . . . . . . . . . 10-108
WEB_menu_entry_new_window . . . . . . . . . . . . . . . . . . . . . . . . . . 10-109
WEB_menu_entry_suppressions . . . . . . . . . . . . . . . . . . . . . . . . . . 10-109
WEB_item_default_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-110
WEB_itemrevision_default_relation . . . . . . . . . . . . . . . . . . . . . . . 10-110
WEB_IWantToDefaultActions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-111
WEB_login_page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-112
WEB_max_search_results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-112
WEB_NX_UseBookmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-112
WEB_package_multipart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-113
WEB_packaging_extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-113
WEB_processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-113
WEB_show_export_nx_assy_menu . . . . . . . . . . . . . . . . . . . . . . . . 10-114
WEB_show_summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-114
WEB_show_unconfigured_revs . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-114
WEB_simple_search_queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-115
WEB_style_sheet_list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-115
WEB_style_sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-115
WEB_style_sheet_list_names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-116
WEB_title_contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-116
WEB_unpackage_multipart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-117
WEB_use_activex_lov . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-117
WEB_use_lhn_home_component . . . . . . . . . . . . . . . . . . . . . . . . . . 10-117
WEB_use_lhn_inbox_component . . . . . . . . . . . . . . . . . . . . . . . . . . 10-118
Thin client column and property preferences . . . . . . . . . . . . . . . . . . . . 10-118
WEB_dataset_columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-119
WEB_inbox_columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-119
WEB_psm_columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-120
WEB_po_columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-121
WEB_wso_columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-121
Folder_ColumnPreferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-121
Thin Client image preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-122
WEB_fullsize_image_generate_type . . . . . . . . . . . . . . . . . . . . . . . 10-122

WEB_image_size_vert . . . . . . . . . . . . . . . . ........... . . . . . . 10-123
WEB_image_size_horiz . . . . . . . . . . . . . . . ........... . . . . . . 10-123
WEB_show_banner . . . . . . . . . . . . . . . . . . ........... . . . . . . 10-123
WEB_show_thumbnail_image . . . . . . . . . . ........... . . . . . . 10-124
WEB_thumbnail_image_display_type . . . . . ........... . . . . . . 10-124
WEB_thumbnail_image_generate_type . . . . ........... . . . . . . 10-124
Thin client DesignContext preferences . . . . . . . ........... . . . . . . 10-125
WebDesignContextDefaultSearchDistance . . ........... . . . . . . 10-125
WebDesignContextMaxMatchingBOMLines ........... . . . . . . 10-125
WebDesignContextMaxMatchingObjects . . . ........... . . . . . . 10-126
RDVThinClientBomlinePropsDisplay . . . . . ........... . . . . . . 10-126
RDVThinClientUserProductItem . . . . . . . . ........... . . . . . . 10-126
RDVThinClientUserrevisionRule . . . . . . . . ........... . . . . . . 10-127
Thin client Teamcenter’s manufacturing process management
preferences . . . . . . . . . . . . . . . . . . . . . . . . . ........... . . . . . . 10-127
WEB_ZoneProcess_Reports . . . . . . . . . . . . ........... . . . . . . 10-127
WEB_StationProcess_Reports . . . . . . . . . . ........... . . . . . . 10-128
WEB_MEWeldOp_Reports . . . . . . . . . . . . . ........... . . . . . . 10-130
WEB_MEPrPlantProcess_Reports . . . . . . . ........... . . . . . . 10-130
WEB_MELocateCompOp_Reports . . . . . . . ........... . . . . . . 10-131
Class_Resource_WeldGun . . . . . . . . . . . . . ........... . . . . . . 10-131
Class_Resource_Robot . . . . . . . . . . . . . . . . ........... . . . . . . 10-131
TC_suppress_report_designs . . . . . . . . . . . ........... . . . . . . 10-132
TC_TransferMode_XMLReport . . . . . . . . . . ........... . . . . . . 10-132
TC_Report_Transfer_Area . . . . . . . . . . . . . ........... . . . . . . 10-133
Batch_Report_Request_File . . . . . . . . . . . . ........... . . . . . . 10-133
Web_Report_Jars . . . . . . . . . . . . . . . . . . . ........... . . . . . . 10-133

Chapter
10 Client preferences
Client preferences modify the display and behavior of the various Teamcenter clients.
Rich client preferences

The Teamcenter rich client is a gateway to your company’s product information. The
rich client framework allows you to integrate and run Teamcenter’s product data
management applications along with various other applications, all from a common
platform. These applications can be MS Office applications, custom applications,
Java Plug-ins, or CAD/CAM/CAE applications such as NX.
Use the following preferences to modify and customize the display and behavior of
the rich client framework.
AE_dataset_default_keep_limit
DESCRIPTION
Determines the number of old dataset versions to store in the database. When this
number is exceeded, the oldest dataset version is deleted.
VALID
VALUES
DEFAULT
VALUES
3
SCOPE
Site preference.

Chapter 10 Client preferences
AI_ignore_ic_flag_setting
DESCRIPTION
Specifies the list of AppInterface types for which the incremental change flag
setting is ignored. If an incremental change is active when the SendDataTo menu is
used, the specified AppInterface types track the change.
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. If a request object in the viewer has
incremental changes associated with it, the corresponding entry in the table is
colored blue.
This preference is used with the Application Interface Viewer, which allows you
to monitor and administer data exchanges between Teamcenter and an external
application using Application Interface Web Service (AIWS) functionality.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid AppInterface type.
DEFAULT
VALUES
None.
SCOPE
All.
AI_Incremental_Export
DESCRIPTION
Determines whether changes to all structures, or only changes to large structures,
are exported when changed. This preference is used with the Application Interface
Viewer, which allows you to monitor and administer data exchanges between
Teamcenter and an external application using Application Interface Web Service
(AIWS) functionality.
VALID
VALUES
true Only changes to large structures are exported.
false All items are exported.
DEFAULT
VALUES
None.
SCOPE
Site preference.
AI_request_no_dependancy
DESCRIPTION
Determines whether synchronization and publish requests are treated independently.

Client preferences
This preference is used with the Application Interface Viewer, which allows you
to monitor and administer data exchanges between Teamcenter and an external
application using Application Interface Web Service (AIWS) functionality.
VALID
VALUES
True Prior synchronization and publish requests are ignored; the current
synchronization or publish request is processed.
False Prior synchronization and publish requests are honored.
DEFAULT
VALUES
False
SCOPE
All.
Allow_Copy_As_Revision
DESCRIPTION
Determines behavior of Save As functionality when saving item revisions in
Teamcenter and Teamcenter Integration for NX.
VALID
VALUES
true Allows saving an existing item revision to either a new item or to a new item
revision contained within an existing item.
false Allows saving an existing item revision to a new item, but not to an existing
item.
DEFAULT
VALUES
false
SCOPE
Site preference.
Attachment_Alias_File
DESCRIPTION
Determines the alias file applied to the intermediate data capture object to display
the attachments of a BOM line a tree structure format. Alias files determines what
displays in the IDCWindow. They determine the root of the window, the children
displayed in each line and the properties for each line. The files contains the following
three parent aliases, these three alias components list all the possible subaliases:
Root Determines the object to be set as the root of the window.
Children Determines the children for each intermediate data capture
line.
Property Determines the properties for each intermediate data capture
line. All the properties for the line are defined as the aliases
under the property alias.

Note
All shipped alias files are stored in the TC_DATA directory.
VALID
VALUES
Accepts a single string as a value. Must be the complete path to the alias XML file.
DEFAULT
VALUES
TC_DATA/attachment_alias.xml
SCOPE
All.
CCCompositionTypesPref
DESCRIPTION
Determines which composition types display to users in Multi-Structure Manager
and Manufacturing Process Planner. A composition is a structure that comprises
components from different top lines, in the context of a configured top-level assembly.
It is represented by a single line in the structure.
For more information about compositions, see the Multi-Structure Manager Guide.
VALID
VALUES
Accepts one or more strings as a value; each string must be a valid item, operation,
or process type.
DEFAULT
VALUES
MEProcess
MEOP
MEProductBOP
MEGenericBOP
SCOPE
All.
CCObject_default_relation
DESCRIPTION
Determines the default relation for CCObject types.
VALID
VALUES
Accepts one or more strings as a value; each string must be a valid Teamcenter object.
DEFAULT
VALUES
IMAN_CCContext
SCOPE
Site preference.

Client preferences
Change_Search_Default
DESCRIPTION
Determines which saved query displays in the search panel by default.
VALID
VALUES
Accepts a single string as a value. Must be a valid saved query.
DEFAULT
VALUES
Item ID
SCOPE
User preference.
copyPasteChunkNumber
DESCRIPTION
Specifies the number of selected objects the cut/paste function processes in a group
rather than individually. When the number of objects selected for cutting/pasting
meets or exceeds the number defined in this preference, the objects are processed by
the server in a groups the size of the set value. For example, if this preference is set
for 20, and 19 objects are selected to be cut, 19 individual cut actions are processed.
If 20 objects were selected to be cut, a single cut action is processed, encompassing
the entire group of selected objects in a single process.
This preference must be manually entered into the database. Create new preferences
using the Options dialog box, accessed from the Edit menu in the rich client.
VALID
VALUES
DEFAULT
VALUES
20 When 20 or more items are selected for cutting or pasting, the
action is processed on the selected objects in groups of 20.
SCOPE
Site preference.
Create_<business_object>_default_type
DESCRIPTION
Lists the business object (type) that has to be preselected in the Types list of the
creation dialog box for a given business object. The <business_object> variable
refers to the business object used to populate the types list in the creation dialog
box. Creation dialog boxes are accessed by menu commands such as New→Item,
New→Part, New→Design, and so on.

VALID
VALUES
Any business object name is a valid value.
DEFAULT
VALUES
Following are the standard preferences defined:
Create_Architecture_default_type=Architecture
Create_Change_default_type=CR
Create_Dataset_default_type=Text
Create_Folder_default_type=Folder
Create_Form_default_type=Item Master
Create_GeneralDesignElementLink_default_type=TC_Link
Create_Interfaces_default_type=Connection_Terminal
Create_Item_default_type=Item
Create_ItemRevision_default_type=Item
Create_PSConnection_default_type=Connection
Create_ProcessVariable_default_type=ProcessVariable
SCOPE
User preference.
Create_WorkspaceObject_mru_list
DESCRIPTION
Displays a list of the object types most recently created in the Business Object
Type dialog box. This dialog box is accessed by choosing File→New→Other in the
rich client or by choosing New→Other in the thin client.
VALID
VALUES
Business object names.
DEFAULT
VALUES
Folder
Item
SCOPE
User preference.
Create_WorkspaceObject_mru_max
DESCRIPTION
Defines the number of object types to display in the list under the Most Recently
Used heading in the Business Object Type dialog box. This dialog box is accessed
by choosing File→New→Other in the rich client or by choosing New→Other in the
thin client.
VALID
VALUES
A positive integer.

Client preferences
DEFAULT
VALUE
5
SCOPE
User preference.
<dataset_name>.FORM_REGISTEREDTO
DESCRIPTION
Teamcenter form displays are based on an XML style sheet. The style sheet must
be created and registered by a system administrator.
For more information, see the Rich Client Customization Programmer’s Guide.
The XML file allows users to define a set of form properties to display, the display
order, and the UI rendering component to be used. The file can be used by both
the rich client and thin client.
This preference is referenced by the style sheet; when a XML style sheet dataset is
selected for display in the viewer, the dataset type defined in this preference is used.
For each <type_name>.FORMRENDERING preference defined, a corresponding
<dataset_name>.FORM_REGISTEREDTO preference must be defined.
VALID
VALUES
Accepts a single string as a value. Must be the type name defined in the
corresponding <type_name>.FORMRENDERING preference.
DEFAULT
VALUES
None. This preference must be manually entered into the database. Create new
preferences using the Options dialog box, accessed from the Edit menu in the rich
client.
SCOPE
Site preference.
<dataset_name>.CREATE_REGISTEREDTO
DESCRIPTION
Indicates the business object type that an XML rendering dataset is
registered to for create style sheet use, using the form of
xml-rendering-style-sheet-dataset.CREATE_REGISTEREDTO=business-object-type.
For example, the ItemCreate.CREATE_REGISTEREDTO=Item preference
means that the ItemCreate XML rendering style sheet dataset is registered as a
create type style sheet to the Item business object type.
Teamcenter property displays are based on an XML rendering style sheet. The style
sheet must be created and registered by a system administrator.

The XML file allows users to define a set of properties to display in creation dialog
boxes, the display order, and the user interface rendering component to be used. The
file can be used by both the rich client and thin client.
This preference is referenced by the style sheet; when an XML style sheet dataset is
selected for display in the viewer, the business object type defined in this preference
is used. For each <type_name>.CREATERENDERING preference defined, a
corresponding <dataset_name>.CREATE_REGISTEREDTO preference must be
defined.
VALID
VALUES
Accepts a single string as a value. It must be the type name defined in the
corresponding <type_name>.CREATERENDERING preference.
DEFAULT
VALUES
client.
SCOPE
Site preference.
<dataset_name>.REGISTEREDTO
DESCRIPTION
Indicates the business object type that an XML rendering dataset
is registered to for property style sheet use, using the form of
xml-rendering-style-sheet-dataset.REGISTEREDTO=business-object-type. For
example, the Item.REGISTEREDTO=Item preference means that the Item XML
rendering style sheet dataset is registered as a property type style sheet to the
Item business object type.
The XML file allows users to define a set of properties to display, the display order,
and the user interface rendering component to be used. The file can be used by both
is used. For each <type_name>.RENDERING preference defined, a corresponding
<dataset_name>.REGISTEREDTO preference must be defined.
VALID
VALUES
corresponding <type_name>.RENDERING preference.

Client preferences
DEFAULT
VALUES
client.
SCOPE
Site preference.
<dataset_name>.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business object type that an XML rendering dataset is
registered to for summary style sheet use, using the form of
xml-rendering-style-sheet-dataset.SUMMARY_REGISTEREDTO=business-object-type.
For example, the ItemSummary.SUMMARY_REGISTEREDTO=Item preference
means that the ItemSummary XML rendering style sheet dataset is registered as a
summary type style sheet to the Item business object type.
is used. For each <type_name>.SUMMARYRENDERING preference defined,
a corresponding <dataset_name>.SUMMARY_REGISTEREDTO preference
must be defined.
VALID
VALUES
corresponding <type_name>.SUMMARYRENDERING preference.
DEFAULT
VALUES
client.
SCOPE
Site preference.

DATASET_object_columns_hidden
DESCRIPTION
Determines which dataset object columns are hidden. This preference can also be set
by editing column options directly from the interface.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter dataset
name. Column widths are defined using the DATASET_object_widths_hidden
user preference.
DEFAULT
VALUES
ref_list
format_used
user_class
dataset_type
tool_used
release_status_list
date_released
archive_info
owning_group
last_mod_user
creation_date
archive_date
last_mod_date
backup_date
SCOPE
User preference.
DATASET_object_columns_shown
DESCRIPTION
Determines which dataset object columns are displayed. This preference can also be
set by editing column options directly from the interface.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter object
name. Column widths are defined using the DATASET_object_widths_shown
user preference.
DEFAULT
VALUES
object_name
object_type
owning_user
revision_number
object_desc
SCOPE
User preference.

Client preferences
DATASET_object_widths_hidden
DESCRIPTION
Specifies the column width for each column defined in the
DATASET_object_columns_hidden user preference.
VALID
VALUES
in the DATASET_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
32
16
16
16
16
16
16
16
16
16
16
16
16
16
SCOPE
User preference.
DATASET_object_widths_shown
DESCRIPTION
DATASET_object_columns_shown user preference.
VALID
VALUES
in the DATASET_object_columns_shown user preference, and so on.
DEFAULT
VALUES
32
9
15
15
32
SCOPE
User preference.

DATASETTYPE_object_columns_hidden
DESCRIPTION
Determines which dataset columns are hidden. This preference can also be set by
editing column options directly from the interface.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter dataset name.
Column widths are defined using the DATASETTYPE_object_widths_hidden
user preference.
DEFAULT
VALUES
archive_info
owning_group
last_mod_user
owning_user
creation_date
archive_date
last_mod_date
backup_date
description
SCOPE
User preference.
DATASETTYPE_object_columns_shown
DESCRIPTION
Determines which dataset columns are displayed. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter dataset name.
Column widths are defined using the DATASETTYPE_object_widths_shown
user preference.
DEFAULT
VALUES
datasettype_name
list_of_tools
SCOPE
User preference.
DATASETTYPE_object_widths_hidden
DESCRIPTION
DATASETTYPE_object_columns_hidden user preference.

Client preferences
VALID
VALUES
in the DATASETTYPE_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
32
32
32
32
32
32
32
32
20
SCOPE
User preference.
DATASETTYPE_object_widths_shown
DESCRIPTION
DATASETTYPE_object_columns_shown user preference.
VALID
VALUES
in the DATASETTYPE_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
80
SCOPE
User preference.
DatasetTypesPref
DESCRIPTION
Specifies the dataset types listed when users choose the System→New→Dataset
command.
VALID
VALUES
One or more strings as values; each string must be a valid dataset type.
DEFAULT
VALUES
UGMASTER
UGPART

Text
SCOPE
Site preference.
DRAG_AND_DROP_Default_dataset_type
DESCRIPTION
Specifies one or more default dataset types for files added to objects by drag-and-drop
operations.
VALID
VALUES
file-extension:dataset-type Accepts one or more strings as values.
For example:
doc:MSWORD
txt:TEXT
pptx:MSPOWERPOINTX
DEFAULT
VALUES
List of all dataset types present in the Teamcenter database with the supported file
extension for each type as default value for that dataset type.
For example:
doc:MSWORD
docx:MSWORDX
txt:TEXT
ppt: MSPOWERPOINT
pptx: MSPOWERPOINTX
SCOPE
All.
NOTES
Users can add new dataset types and supported file extensions.
DRAG_AND_DROP_file_limit
DESCRIPTION
Specifies the number of the files that can be dragged and dropped by each
drag-and-drop operation.
VALID
VALUES
integer-value Any positive integer value.
DEFAULT
VALUES
10
SCOPE
All.

Client preferences
NOTE
The value must be greater than 1.
DRAG_AND_DROP_SWING_dialog_enable
DESCRIPTION
Specifies whether to show or hide the multiple file drag-and-drop dialog box for
single-file drag-and-drop operations.
VALID
VALUES
true The standard dialog box is displayed for single-file drag and drop operations.
false The multiple file drag-and-drop dialog box is displayed for single-file
drag-and-drop operations.
DEFAULT
VALUES
false
SCOPE
All.
Enable_thumbnails
DESCRIPTION
Enables thumbnail datasets for Teamcenter.
VALID
VALUES
TRUE Enables thumbnail datasets.
FALSE Hides thumbnail datasets.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
FLColumnCatIVFSeparatorPref
DESCRIPTION
Specifies the character used to separate an item ID from an item revision ID in
an object column.
VALID
VALUES
A single ASCII character.
DEFAULT
VALUES
A slash (/).

SCOPE
User preference.
FLColumnCatObjSeparatorPref
DESCRIPTION
Specifies the character used to separate an item ID from an item name in an object
column.
VALID
VALUES
DEFAULT
VALUES
A dash (-).
SCOPE
User preference.
FOLDER_object_columns_hidden
DESCRIPTION
Determines which folder object columns are hidden. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter folder name.
Column widths are defined using the FOLDER_object_widths_hidden user
preference.
DEFAULT
VALUES
contents
release_status_list
revision_number
date_released
archive_info
owning_group
last_mod_user
creation_date
archive_date
last_mod_date
backup_date
SCOPE
User preference.

Client preferences
FOLDER_object_columns_shown
DESCRIPTION
Determines which folder object columns are displayed. This preference can also be
VALID
VALUES
name. Column widths are defined using the FOLDER_object_widths_shown
user preference.
DEFAULT
VALUES
object_name
object_type
owning_user
object_desc
SCOPE
User preference.
FOLDER_object_widths_hidden
DESCRIPTION
FOLDER_object_columns_hidden user preference.
VALID
VALUES
in the FOLDER_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
32
32
32
32
32
32
32
32
32
32
32
SCOPE
User preference.

FOLDER_object_widths_shown
DESCRIPTION
FOLDER_object_columns_shown user preference.
VALID
VALUES
in the FOLDER_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
16
16
32
SCOPE
User preference.
FORM_object_columns_hidden
DESCRIPTION
Determines which form object columns are hidden. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter form
name. Column widths are defined using the FORM_object_widths_hidden user
preference.
DEFAULT
VALUES
data_file
release_status_list
revision_number
date_released
archive_info
owning_group
last_mod_user
creation_date
archive_date
last_mod_date
backup_date
SCOPE
User preference.

Client preferences
FORM_object_columns_shown
DESCRIPTION
Determines which form object columns are displayed. This preference can also be set
VALID
VALUES
name. Column widths are defined using the FORM_object_widths_shown user
preference.
DEFAULT
VALUES
object_name
object_type
owning_user
object_desc
form_file
SCOPE
User preference.
FORM_object_widths_hidden
DESCRIPTION
FORM_object_columns_hidden user preference.
VALID
VALUES
in the FORM_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
32
32
32
32
32
32
32
32
32
32
32
SCOPE
User preference.

FORM_object_widths_shown
DESCRIPTION
FORM_object_columns_shown user preference.
VALID
VALUES
in the FORM_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
16
16
32
30
SCOPE
User preference.
FormTypesPref
DESCRIPTION
Specifies the form types listed when users choose the File→New→Form command.
If this preference is left undefined, the New Form dialog displays rather than a
dropdown list of form types.
VALID
VALUES
One or more strings as values; each string must be a valid form type.
DEFAULT
VALUES
None.
SCOPE
Site preference.
GROUP_object_columns_hidden
DESCRIPTION
Determines which group object columns are hidden. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter group
name. Column widths are defined using the GROUP_object_widths_hidden
user preference.

Client preferences
DEFAULT
VALUES
list_of_role
volume
SCOPE
User preference.
GROUP_object_columns_shown
DESCRIPTION
Determines which group object columns are displayed. This preference can also be
VALID
VALUES
name. Column widths are defined using the GROUP_object_widths_shown user
preference.
DEFAULT
VALUES
name
description
SCOPE
User preference.
GROUP_object_widths_hidden
DESCRIPTION
GROUP_object_columns_hidden user preference.
VALID
VALUES
in the GROUP_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
32
32
SCOPE
User preference.
GROUP_object_widths_shown
DESCRIPTION
GROUP_object_columns_shown user preference.

VALID
VALUES
in the GROUP_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
32
SCOPE
User preference.
HiddenPerspectives
DESCRIPTION
Hides specified perspectives in the rich client. The value listed must be the activity
name defined in the org.eclipse.ui.activities extension point within a given
perspective’s plugin.xml file.
VALID
VALUES
AccessManager PlantDesigner
AppearanceConfiguration PartPlanner
AuditManager PlatformDesigner
Authorization PlmXmlExportImportAdministration
CAEManager Project
CAEStructureDesigner QueryBuilder
ChangeManager RegistryEditor
CMViewerClassic ReportBuilder
Classification ReportDesigner
ClassificationAdmin ReportGenerator
CommandSuppression ResourceManager
DatabaseUtilities RequirementsManager
DesignContext RelationBrowser
eIntegrator StructureManager
IssueManager ScheduleManager
LifecycleViewer SetupWizard
ManufacturingProcessPlanner SubscriptionMonitor
MyTeamcenter Validation

Client preferences
MyTeamcenterLegacy VolumeManagement
Note
The My Teamcenter (2007)
perspective.
Multi-StructureManager WorkflowDesigner
Organization WorkflowViewer
DEFAULT
VALUES
CMViewerClassic for Foundation installations; none for Foundation upgrades, GM
Overlay installations, and GM Overlay upgrades.
ChangeManager
MyTeamcenterLegacy
SCOPE
Site preference.
RESTRICTIONS
You cannot hide the Getting Started, DPV Measurements, or Web Browser
perspectives.
IDCAttachmentColumnsShownPref
DESCRIPTION
Determines the columns displayed in the IDCAttachmentTreeTable, used to display
attachments of the captured structure.
VALID
VALUES
Accepts multiple strings as values. Must be a valid IDCLine property.
DEFAULT
VALUES
Me_cl_display_string
Me_cl_object_type
Me_cl_relation
SCOPE
All.
IDCAttachmentColumnWidthsPref
DESCRIPTION
Determines the column width for the list of properties defined in the
IDCAttachmentColumnsShownPref preference.

VALID
VALUES
Accepts multiple strings as values. Each value must be a positive integer, and
align, in order, with a value defined in the IDCAttachmentColumnsShownPref
preference.
DEFAULT
VALUES
15
10
10
SCOPE
All.
IDCStructureColumnsShownPref
DESCRIPTION
Determines the columns displayed in the IDCBOMTreeTable, used to display the
captured structure.
VALID
VALUES
Accepts multiple strings as values. Must be a valid IDCLine property.
DEFAULT
VALUES
Bl_intended_title
Bl_sequence_no
Bl_rev_object_type
SCOPE
All.
IDCStructureColumnWidthsPref
DESCRIPTION
IDCStructureColumnsShownPref preference.
VALID
VALUES
Accepts multiple strings as values. Each value must be a positive integer, and
align, in order, with a value defined in the IDCStructureColumnsShownPref
preference.
DEFAULT
VALUES
15
10
10

Client preferences
SCOPE
All.
IdentifierContextTypeDefault
DESCRIPTION
Determines the default ID context type used when an object is imported without
an assigned ID context.
VALID
VALUES
Accepts a single string as a value. Must be a valid ID context type.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IdentifierTypeDefault
DESCRIPTION
Determines the default identifier type used when an object is imported without
an identifier type.
VALID
VALUES
Accepts a single string as a value. Must be a valid identifier type.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IMAN_3D_snap_shot_relation_primary
DESCRIPTION
Determines the default relation for IMAN_3D_snap_shot types.
VALID
VALUES
Accepts one or more strings as a value; each string must be a valid Teamcenter object.
DEFAULT
VALUES
ItemRevision
SCOPE
Site preference.

IMAN_customization_libraries
DESCRIPTION
Registers multiple customizations of Teamcenter. Enables the library file for each
customization defined in this preference.
For example, the following setting accepts the customizations of both Supplier1 and
Supplier2 by customizing the Supplier1.sl/so/dll library and Supplier2.sl/so/dll
library files:
IMAN_customization_registry=
Supplier1
Supplier2
VALID
VALUES
Accepts one or more strings as values; each string must be a valid customization file.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IMAN_FLASH_FILE
DESCRIPTION
Determines the flash screen displayed while the workspace is loading. This
preference is enabled by not setting the TC_DISABLE_FLASH preference.
VALID
VALUES
A single string; this string must be the full operating system path name of a valid
display file.
DEFAULT
VALUES
None.
SCOPE
User preference.
IMANFILE_object_columns_hidden
DESCRIPTION
Determines which file name columns are hidden. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter file name.
Column widths are defined using the IMANFILE_object_widths_hidden user
preference.

Client preferences
DEFAULT
VALUES
text_flag
machine_type
status_flag
time_last_modified
archive_info
owning_group
last_mod_user
creation_date
archive_date
last_mod_date
backup_date
SCOPE
User preference.
IMANFILE_object_columns_shown
DESCRIPTION
Determines which file name columns are displayed. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter file name.
Column widths are defined using the IMANFILE_object_widths_shown user
preference.
DEFAULT
VALUES
original_file_name
volume_tag
owning_user
file_name
SCOPE
User preference.
IMANFILE_object_widths_hidden
DESCRIPTION
IMANFILE_object_columns_hidden user preference.
VALID
VALUES
in the IMANFILE_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
32

32
32
32
32
32
32
32
32
32
32
SCOPE
User preference.
IMANFILE_object_widths_shown
DESCRIPTION
IMANFILE_object_columns_shown user preference.
VALID
VALUES
in the IMANFILE_object_columns_shown user preference, and so on.
DEFAULT
VALUES
32
16
16
32
SCOPE
User preference.
IMANTYPE_object_columns_shown
DESCRIPTION
Determines which type object columns are displayed. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter object name.
Column widths are defined using the IMANTYPE_object_widths_shown user
preference.
DEFAULT
VALUES
type_name
type_class
SCOPE
User preference.

Client preferences
IMANTYPE_object_widths_shown
DESCRIPTION
IMANTYPE_object_columns_shown user preference.
VALID
VALUES
in the IMANTYPE_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
20
SCOPE
User preference.
IMANVOLUME_object_columns_hidden
DESCRIPTION
Determines which volume name columns are hidden. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter volume name.
Column widths are defined using the IMANVOLUME_object_widths_hidden
user preference.
DEFAULT
VALUES
last_mod_date
archive_date
creation_date
backup_date
shadow_node_name
shadow_vms_path_name
users
shadow_unix_path_name
vms_path_name
machine_type
archive_info
last_mod_user
owning_user
owning_group
SCOPE
User preference.

IMANVOLUME_object_columns_shown
DESCRIPTION
Determines which volume name columns are displayed. This preference can also be
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter volume name.
Column widths are defined using the IMANVOLUME_object_widths_shown
user preference.
DEFAULT
VALUES
volume_name
node_name
unix_path_name
SCOPE
User preference.
IMANVOLUME_object_widths_hidden
DESCRIPTION
IMANVOLUME_object_columns_hidden user preference.
VALID
VALUES
in the IMANVOLUME_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
16
16
16
16
20
80
80
80
80
16
32
16
16
16
SCOPE
User preference.

Client preferences
IMANVOLUME_object_widths_shown
DESCRIPTION
IMANVOLUME_object_columns_shown user preference.
VALID
VALUES
in the IMANVOLUME_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
20
80
SCOPE
User preference.
<Item>.FilterCriteria
DESCRIPTION
Filter criteria to apply for displaying objects in the project smart folder of the item.
VALID
VALUES
Filter criteria as specified in the Project application.
DEFAULT
VALUES
Item name or item revision.
SCOPE
Site preference.
ITEM_first_rev_id
DESCRIPTION
Enables item revision ID sequencing. This preference is the default site preference
that is used for all item types. To apply a different revision sequencing format to a
particular item type, a site preference must be defined for the item type.
The standard naming pattern for an item type-specific preference is
ITEM_TYPE_first_rev_id, where ITEM_TYPE is the item type name. For example,
the site preference for the item type CORP_Part is CORP_Part_first_rev_id.
Revision increments are implemented by assigning a preferred value to the
preference. Revision ID prefixes and postfixes, if used, should be included in the site
preference variable value, enclosed in single quotation marks. For example, if ABC
is the revision ID prefix and XYZ is the postfix, the variable value is ‘ABC’001‘XYZ’.

In this scenario, when a new item is created, it has a revision ID of ABC001XYZ.

When this item is next revised, the value between the revision ID prefix and suffix is
incrementally increased, resulting in a new revision ID of ABC002XYZ.
Note
When creating new revisions of an existing item or item revision, the revision
increments are created according to the previous item revision ID. If the
previous item revision ID matches the pattern of the site preference variable,
the value between the prefix and postfix is incrementally increased. If the
existing revision ID pattern does not match the site preference variable
pattern, the revision increment is done as per current Teamcenter logic.
VALID
VALUES
A single string as a value.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ITEM_id_postfix
DESCRIPTION
Specifies a character string added to the end of each new default item ID.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ITEM_id_prefix
DESCRIPTION
Specifies a character string added to the beginning of each new default item ID.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.

Client preferences
ITEM_object_columns_hidden
DESCRIPTION
Determines which item object columns are hidden. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter item
name. Column widths are defined using the ITEM_object_widths_hidden user
preference.
DEFAULT
VALUES
uom_tag
release_status_list
revision_limit
revision_number
date_released
archive_info
last_mod_user
owning_group
last_mod_date
archive_date
creation_date
backup_date
IMAN_master_form
IMAN_specification
IMAN_manifestation
IMAN_requirement
IMAN_reference
IMAN_master_data
SCOPE
User preference.
ITEM_object_columns_shown
DESCRIPTION
Determines which item object columns are displayed. This preference can also be set
VALID
VALUES
name. Column widths are defined using the ITEM_object_widths_shown user
preference.
DEFAULT
VALUES
item_id
object_name
object_type
owning_user

object_desc
SCOPE
User preference.
ITEM_object_widths_hidden
DESCRIPTION
ITEM_object_columns_hidden user preference.
VALID
VALUES
in the ITEM_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
14
32
6
6
32
13
16
16
16
16
32
32
32
32
32
32
32
32
SCOPE
User preference.
ITEM_object_widths_shown
DESCRIPTION
ITEM_object_columns_shown user preference.
VALID
VALUES
in the ITEM_object_columns_shown user preference, and so on.

Client preferences
DEFAULT
VALUES
20
20
16
16
32
SCOPE
User preference.
<Item>.SUMMARYRENDERING2007
DESCRIPTION
Registers the summary style sheet of the My Teamcenter 2007 item.
The summary stylesheet refers to the Summary tab in My Teamcenter 2007.
VALID
VALUES
Any registered XML rendering style sheet.
DEFAULT
VALUES
Item name Default values

Folder FolderSummary2007
Item ItemSummary2007
ItemRevision ItemRevisionSummary2007
Dataset DatasetSummary2007
SCOPE
Site preference.
<ItemRevision>.RENDERING
DESCRIPTION
Registers the properties of the item revision.
VALID
VALUES
DEFAULT
VALUES
Name of the item revision.
SCOPE
Site preference.

<ItemRevision1>_<ItemRevision2>_default_relation
DESCRIPTION
Specifies the default relation between source object (item revision 1) and target
object (item revision 2).
VALID
VALUES
Single string value indicating the valid relation type.
DEFAULT
VALUES
CPTechnicalBriefRevision_CPPackageRoughRevision_default_relation=CP_Results_In_Package_Rough
CPMarketingBriefRevision_CPDesignBriefRevision_default_relation=CP_Has_Design_Brief
CPMarketingBriefRevision_CPTechnicalBriefRevision_default_relation=CP_Has_Technical_Brief
CPThemeBoardRevision_CPGraphicElementRevision_default_relation=CP_Has_Graphical_Element
CPDesignBriefRevision_CPGraphicElementRevision_default_relation=CP_Has_Graphical_Element
SCOPE
Site preference.
<ItemRevision>.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet of the item revision.
The summary style sheet refers to the Summary tab in My Teamcenter.
VALID
VALUES
DEFAULT
VALUES

WorkspaceObject WorkspaceObjectSummary
CPBrandEquityRevision CPBrandEquityRevisionSummary
CPMarketingBriefRevision CPMarketingBriefRevisionSummary
CPDesignBriefRevision CPDesignBriefRevisionSummary
CPTechnicalBriefRevision CPTechnicalBriefRevisionSummary
CPPackageRoughRevision CPPackageRoughRevisionSummary
CPPackageConceptRevision CPPackageConceptRevisionSummary
CPPackageItemRevision CPPackageItemRevisionSummary
CPDieLineRevision CPDieLineRevisionSummary
CPArtworkRevision CPArtworkRevisionSummary
CPGraphicElementRevision CPGraphicElementRevisionSummary
CPCopyRevision CPCopyRevisionSummary
CPCopyElementRevision CPCopyElementRevisionSummary

Client preferences

CPFinishProductRevision CPFinishProductRevisionSummary
TC_Project • ProjectSummary
• CPGProjectSummary
Schedule ScheduleSummary
CPGFormulaMaterRevision CPGFormulaMaterRevisionSummary
CPGRawMaterialRevision CPGRawMaterialRevisionSummary
CPGIngredientRevision CPGIngredientRevisionSummary
CPGChemicalRevision CPGChemicalRevisionSummary
CPSpecificationRevision CPSpecificationRevisionSummary
CPThemeBoardRevision CPThemeBoardRevisionSummary
CPBrandAssetRevision CPBrandAssetRevisionSummary
CPTradeItemRevision CPTradeItemRevisionSummary
SCOPE
Site preference.
ItemRevision_default_relation
DESCRIPTION
Defines the default relation assigned to an item revision when it is created.
This preference also determines the relation used to attach a PLM XML dataset to
an item revision when saving the dataset from Lifecycle Visualization to Teamcenter
with the File→Save As command using the DAK adapter.
VALID
VALUES
Accepts a single string as a value. Must be a valid relation type.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ITEMREVISION_object_columns_hidden
DESCRIPTION
Determines which item revision object columns are hidden. This preference can also
be set by editing column options directly from the interface.
VALID
VALUES
One or more strings as values; each string must be a valid
Teamcenter item revision name. Column widths are defined using the
ITEMREVISION_object_widths_hidden user preference.

DEFAULT
VALUES
structure_revisions
object_type
revision_number
date_released
archive_info
owning_group
last_mod_user
creation_date
archive_date
last_mod_date
backup_date
SCOPE
User preference.
ITEMREVISION_object_columns_shown
DESCRIPTION
Determines which item revision object columns are displayed. This preference can
also be set by editing column options directly from the interface.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter object name.
Column widths are defined using the ITEMREVISION_object_widths_shown
user preference.
DEFAULT
VALUES
items_tag
item_revision_id
object_name
owning_user
object_desc
release_status_list
SCOPE
User preference.
ITEMREVISION_object_widths_hidden
DESCRIPTION
ITEMREVISION_object_columns_hidden user preference.
VALID
VALUES
in the ITEMREVISION_object_columns_hidden user preference, and so on.

Client preferences
DEFAULT
VALUES
32
32
32
32
32
32
32
32
32
32
32
SCOPE
User preference.
ITEMREVISION_object_widths_shown
DESCRIPTION
ITEMREVISION_object_columns_shown user preference.
VALID
VALUES
in the ITEMREVISION_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
10
20
16
32
32
SCOPE
User preference.
ItemRevision_shown_relations
DESCRIPTION
Determines which relations display within an item revision.
VALID
VALUES
Accepts one or more strings as a value; each string must be a valid Teamcenter
relation type.
DEFAULT
VALUES
PSBOMViewRevision
IMAN_specification

IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_UG_udf
IMAN_UG_altrep
IMAN_UG_scenario
IMAN_Simulation
IMAN_Rendering
IMAN_Motion
IMAN_MEMfgModel
IMAN_snapshot
IMAN_3D_snap_shot
IMAN_external_object_link
IMAN_MEWorkInstruction
TC_ProductManual
BOM_Rollup
TC_Attaches
TCEng_rdv_plmxml_configured
TC_Is_Represented_By
TCEng_rdv_plmxml_unconfigured
Snapshot
#IMAN_classification
Note
You must uncomment the IMAN_classification value for this value to
display.
SCOPE
Site preference.
ItemRevision_thumbnail_relations
DESCRIPTION
Defines priority of relations between item revision and dataset. Teamcenter uses
this priority to determine the dataset to be used to generate thumbnail.
VALID
VALUES
Accepts relationship types.
DEFAULT
VALUES
IMAN_specification
IMAN_manifestation
IMAN_Rendering
IMAN_Motion
IMAN_3D_snap_shot
TC_Attaches
SCOPE
Site preference.

Client preferences
ItemRevision_thumbnail_references
DESCRIPTION
Defines priority of reference types for datasets in an item revision. Teamcenter uses
this priority to determine the dataset to be used to generate thumbnail.
VALID
VALUES
Reference types for datasets.
DEFAULT
VALUES
TIF_Reference
JPEG_Reference
AI_Reference
PDF_Reference
JTPART
UGPART
Image
SCOPE
Site preference.
Item_shown_relations
DESCRIPTION
Determines which relations display within an item.
VALID
VALUES
relation type.
DEFAULT
VALUES
PSBOMView
ItemRevision
IMAN_requirement
IMAN_manifestation
IMAN_reference
#IMAN_classification
Note
You must uncomment the IMAN_classification value for this value to
display.
SCOPE
Site preference.

ITEM_smart_baseline
DESCRIPTION
Determines whether the systems functions in smart copy mode, in which only items
that have changed since the previous baseline are copied into the new baseline and
unchanged items are referenced. This contrasts with standard mode, where each
item is copied into the new baseline, regardless of whether it had changed.
VALID
VALUES
true System uses smart copy mode.
false System uses standard mode.
DEFAULT
VALUES
false
SCOPE
Site preference.
<Item type>_rev_display_all
DESCRIPTION
Determines whether to display all item revisions or only the item revisions meeting
the filter criteria defined in the Revision display filter options of the Options dialog
box in the rich client interface. Users set these display options to filter the display of
item revisions in the Teamcenter interface, preventing item revisions they are not
interested in from displaying.
Item-type is the type of item selected from the Select item type dropdown list and
TRUE indicates the user selected that all item revisions display.
VALID
VALUES
TRUE Displays all item revisions.
FALSE Displays only the item revisions meeting the filter criteria.
DEFAULT
VALUES
None.
SCOPE
User preference.
<Item type>_rev_display_order
DESCRIPTION
Determines the order in which item revisions display if the Revision display filter
options are defined in the Options dialog box in the rich client interface. Users
set these display options to filter the display of item revisions in the Teamcenter
interface, preventing item revisions they are not interested in from displaying.

Client preferences
Item-type is the type of item selected from the Select item type dropdown list and 1
indicates the user selected the item revisions are displayed in descending order.
VALID
VALUES
0 Displays item revisions in ascending order.
1 Displays item revisions in descending order.
DEFAULT
VALUES
None.
SCOPE
User preference.
<Item type>_rev_display_rule
DESCRIPTION
Determines which item revisions display if the Revision display filter options are
defined in the Options dialog box in the rich client interface. Users set these display
options to filter the display of item revisions in the Teamcenter interface, preventing
item revisions they are not interested in from displaying.
For example, users can filter the item revision display so that only released item
revisions of production status matching the configured revision rule of Any status,
working displays with the following setting:
Item_rev_display_rule=
3:=: Production:
4:=:Any status, working:
In another example, users can filter the item revision display so that only three item
revisions whose statuses are not prereleased, two of which are in process, display
with the following setting:
Item_rev_display_rule=
3:!=:Pre-Released:3
2: : :2
For more information about setting these rules in the rich client interface, see the
Rich Client Interface Guide.
VALID
VALUES
One or more strings as values; each string in the following format:
status-number:relation-operator:condition:limit
• status-number accepts integers 1 through 4, each integer defining a particular
status.
• relation-operator accepts either the equal sign (=) meaning equal or an
exclamation point and equal sign (!=) meaning not equal.
• condition accepts a valid release status or revision rule.
• limit accepts a positive integer.
relation-operator is valid only when the status-number is set to released (3); there
are no further conditions to define for the working (1) and in process (2) statuses,
and a relation operator is not appropriate for configured revisions.

When released (3) or configured (4) is set for the status, condition accepts any valid
release status or revision rule.
1 Working.
2 In process.
3 Released.
4 Configured.
DEFAULT
VALUES
None.
SCOPE
User preference.
JTTreeTableColumnsShownPref
DESCRIPTION
Determines which JT tree table columns are displayed for JT export using PLM XML.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid Structure
Manager attribute.
DEFAULT
VALUES
bl_indented_title
bl_jt_editable
SCOPE
Site preference.
JTTreeTableShownColumnWidthsPref
DESCRIPTION
JTTreeTableColumnsShownPref preference.
VALID
VALUES
in the JTTreeTableColumnsShownPref preference, and so on.
DEFAULT
VALUES
40
5
SCOPE
Site preference.

Client preferences
LOV_hide_desc
DESCRIPTION
Determines whether side-by-side LOV value/descriptions display. By default, LOVs
are configured to display the value alongside its description in the user interface. Use
this preference to specify specific LOVs whose descriptions you do not want to display.
Note
The simplest method for defining side-by-side display behavior is via the
Options dialog box, accessed from the Edit menu. Use this dialog box to set
the LOVs whose value/descriptions you do not want to display side by side.
The system automatically writes this setting to the user preference file.
For more information about configuring LOV value/descriptions, see the Business
Modeler IDE Guide.
For more information about using the Options dialog box, see the Rich Client
Interface Guide.
VALID
VALUES
Accepts multiple strings as values. Each entry indicates an LOV whose
value/description will not display side-by-side. Each string must be the name of a
valid LOV. For example:
LOV_hide_desc=
LOV_name1
LOV_name2
DEFAULT
VALUES
None.
SCOPE
User preference.
MECollaborationContext_default_relation
DESCRIPTION
Determines the default relation for MECollaborationContext types.
VALID
VALUES
object type.
DEFAULT
VALUES
IMAN_CCContext
SCOPE
User preference.

MEOPRevision_shown_relations
DESCRIPTION
Determines which relations display within a MEOP revision.
VALID
VALUES
relation type.
DEFAULT
VALUES
PSBOMViewRevision
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEOutput
IMAN_METarget
IMAN_MEWorkArea
IMAN_3D_snap_shot
SCOPE
Site preference.
MEProcessRevision_shown_relations
DESCRIPTION
Determines which relations display within a MEProcess revision.
VALID
VALUES
relation type.
DEFAULT
VALUES
PSBOMViewRevision
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEOutput
IMAN_METarget
IMAN_MEWorkArea
IMAN_3D_snap_shot
SCOPE
Site preference.

Client preferences
MySearchHistory_Limit
DESCRIPTION
Determines the number of searches maintained in the search history. When the limit
is reached, the oldest search is deleted.
VALID
VALUES
DEFAULT
VALUES
8
SCOPE
User preference.
OpenAfterCreatePref
DESCRIPTION
Determines whether to open an object immediately after creating it.
VALID
VALUES
0 Opens an object immediately after creating it.
1 Does not open an object immediately after creating it.
DEFAULT
VALUES
0
SCOPE
Site
PERSON_object_columns_hidden
DESCRIPTION
Determines which person columns are hidden. This preference can also be set by
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter person
name. Column widths are defined using the PERSON_object_widths_hidden
user preference.
DEFAULT
VALUES
PA5
PA7
PA8
archive_info
owning_group
last_mod_user

owning_user
creation_date
archive_date
last_mod_date
backup_date
PA6
SCOPE
User preference.
PERSON_object_columns_shown
DESCRIPTION
Determines which person columns are displayed. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter person
name. Column widths are defined using the PERSON_object_widths_shown
user preference.
DEFAULT
VALUES
user_name
PA1
PA2
PA3
PA4
PA10
PA9
SCOPE
User preference.
PERSON_object_widths_hidden
DESCRIPTION
PERSON_object_columns_hidden user preference.
VALID
VALUES
in the PERSON_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
32
32
32
32
32

Client preferences
32
32
32
32
32
32
32
SCOPE
User preference.
PERSON_object_widths_shown
DESCRIPTION
PERSON_object_columns_shown user preference.
VALID
VALUES
in the PERSON_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
20
16
10
10
16
20
SCOPE
User preference.
PSBOMVIEW_object_columns_hidden
DESCRIPTION
Determines which BOM view columns are hidden. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter BOM view
name. Column widths are defined using the PSBOMVIEW_object_widths_hidden
user preference.
DEFAULT
VALUES
revision_number
archive_info
last_mod_user
creation_date

archive_date
last_mod_date
backup_date
date_released
owning_group
SCOPE
User preference.
PSBOMVIEW_object_columns_shown
DESCRIPTION
Determines which BOM view columns are displayed. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter BOM view
name. Column widths are defined using the PSBOMVIEW_object_widths_shown
user preference.
DEFAULT
VALUES
parent_item
object_name
object_type
owning_user
dobject_desc
release_status_list
SCOPE
User preference.
PSBOMVIEW_object_widths_hidden
DESCRIPTION
PSBOMVIEW_object_columns_hidden user preference.
VALID
VALUES
in the PSBOMVIEW_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
32
32
32
32
32
32
32

Client preferences
32
322
SCOPE
User preference.
PSBOMVIEW_object_widths_shown
DESCRIPTION
PSBOMVIEW_object_columns_shown user preference.
VALID
VALUES
in the PSBOMVIEW_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
20
10
16
32
32
SCOPE
User preference.
PSBOMVIEWREVISION_object_columns_hidden
DESCRIPTION
Determines which BOM view revision columns are hidden. This preference can also
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter
BOM view revision name. Column widths are defined using the
PSBOMVIEWREVISION_object_widths_hidden user preference.
DEFAULT
VALUES
is_precise
bom_view
revision_number
date_released
archive_info
owning_group
last_mod_user
creation_date
archive_date
last_mod_date

backup_date
SCOPE
User preference.
PSBOMVIEWREVISION_object_columns_shown
DESCRIPTION
Determines which BOM view revision columns are displayed. This preference can
also be set by editing column options directly from the interface.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter
BOM view revision name. Column widths are defined using the
PSBOMVIEWREVISION_object_widths_shown user preference.
DEFAULT
VALUES
object_name
object_type
owning_user
object_desc
occs_vla
release_status_list
SCOPE
User preference.
PSBOMVIEWREVISION_object_widths_hidden
DESCRIPTION
PSBOMVIEWREVISION_object_columns_hidden user preference.
VALID
VALUES
The first value set in this preference defines the column width of the first value
set in the PSBOMVIEWREVISION_object_columns_hidden user preference,
and so on.
DEFAULT
VALUES
32
32
32
32
32
32
32
32
32
32

Client preferences
32
SCOPE
User preference.
PSBOMVIEWREVISION_object_widths_shown
DESCRIPTION
PSBOMVIEWREVISION_object_columns_shown user preference.
VALID
VALUES
The first value set in this preference defines the column width of the first value set in
the PSBOMVIEWREVISION_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
18
16
32
32
32
SCOPE
User preference.
QRYColumnsShownPref
DESCRIPTION
Determines the queries available for selection from the Find menu in both the rich
client and the thin client.
VALID
VALUES
Valid Teamcenter query classes.
DEFAULT
VALUES
General...
Item...
Item Revision...
Remote...
Checked-Out Dataset...
SCOPE
User preference.

QRY_dataset_display_option
DESCRIPTION
Determines whether the latest version or all versions of a dataset object are
displayed when query results are returned.
VALID
VALUES
1 Displays all versions of a dataset object.
2 Displays the latest version of a dataset object.
DEFAULT
VALUES
None.
SCOPE
User preference.
QRY_<query_name>_SortKeys
DESCRIPTION
Determines the class attributes used to sort the query results. This preference must
be used in conjunction with the QRY_query_name_SortOrder preference, which
determines sort order.
VALID
VALUES
The value type of the class attribute must be a primitive value type. For example,
char, int, double or date. If a query name contains one of the following characters,
this character needs to be replaced with the underscore (_) character:
• space character
• return character (\n)
• tab character (\t)

DEFAULT
VALUES
None.
SCOPE
User preference.
QRY_<query_name>_SortOrder
DESCRIPTION
Determines the sort order of query results. This preference must be used in
conjunction with the QRY_query_name_SortKeys preference, which determines the
class attributes used to sort query results.
VALID
VALUES
1 Sorts query results in ascending order.

Client preferences
2 Sorts query results in descending order.

DEFAULT
VALUES
None.
SCOPE
User preference.
QRY_search_classification_hierarchy
DESCRIPTION
Specifies whether saved and ad hoc classification queries performed with the My
Teamcenter search feature searches across the classification hierarchy or only the
given class.
VALID
VALUES
true Saved query and ad hoc classification queries search on the given class as
well as on all the classes to which the given class is an ancestor.
false Saved query and ad hoc classification queries search only on the given class.
DEFAULT
VALUES
false
SCOPE
User preference.
QRY_search_type_hierarchy
DESCRIPTION
Determines whether subtypes are included in query results. The system uses type
hierarchy functionality to query types and subtypes.
Administrators can add this preference in the Options dialog box which can be
accessed from the Edit menu, or in the tc_preferences.xml preferences file. Users
can set this preference to true from the interface:
• In the rich client, click Edit→Options to display the Options dialog box. Select
Search folder from the tree on the left. Select the Query Options tab. Then
check the Enable Hierarchical Type Search check box. Checking this check box
automatically adds this preference to the database, and sets it to true.
• In the thin client, select the Options link from the Settings menu in the
Navigation bar to display the Options dialog box. Click the Search tab. Click
Type hierarchy on search, then select Yes from the list. Checking this check box
automatically adds this preference to the database, and sets it to true.
VALID
VALUES
true Subtypes are included in query results.
false Subtypes are not included in query results.

DEFAULT
VALUES
false
SCOPE
User preference.
ReferencersPane_Shown
DESCRIPTION
Determines whether the Referencers pane appears in My Teamcenter. Users can use
this pane to graphically display reference information regarding the selected object.
VALID
VALUES
True The Referencers option appears in the shortcut menu.
False The Referencers option does not appear.
DEFAULT
VALUES
True
SCOPE
User preference.
ReportDefinition_ColumnPreferences
DESCRIPTION
Determines which columns are displayed in the Report Builder application. This
preference can also be set by editing column options directly from the interface.
For information about changing columns from the interface, see Getting Started
with Teamcenter.
Note
Column widths are defined using the
ReportDefinition_ColumnWidthPreferences preference.
VALID
VALUES
Accepts one or more strings as values. Each string must be one of the following
report definition attributes:
rd_id
rd_name
rd_type
rd_class
rd_state
rd_source
rd_query_source
rd_property_source
owning_group
owning_user
last_mod_date

Client preferences
last_mod_user
DEFAULT
VALUES
rd_id
rd_name
rd_type
rd_class
rd_state
rd_source
rd_query_source
rd_property_source
owning_group
owning_user
last_mod_date
last_mod_user
SCOPE
Site preference.
ReportDefinition_ColumnWidthPreferences
DESCRIPTION
ReportDefinition_ColumnPreferences preference.
VALID
VALUES
Accepts one or more integers as values. Each integer defines the column width in
characters. The first value set in this preference defines the column width of the first
value set in the ReportDefinition_ColumnPreferences preference, and so on.
DEFAULT
VALUES
20
20
13
17
13
9
17
17
9
9
17
17
17
SCOPE
Site preference.

ReportGenerationDlg_ColumnPreferences
DESCRIPTION
Determines which columns are displayed in the Report Generation wizard. This
preference can also be set by editing column options directly from the interface.
For information about changing columns from the interface, see Getting Started
with Teamcenter.
Note
Column widths are defined using the
ReportGenerationDlg_ColumnWidthPreferences preference.
VALID
VALUES
Accepts one or more strings as values. Each string must be one of the following
report definition attributes:
rd_id
rd_name
rd_type
rd_class
rd_state
rd_source
rd_query_source
rd_property_source
owning_group
owning_user
last_mod_date
last_mod_user
DEFAULT
VALUES
rd_id
rd_name
SCOPE
Site preference.
ReportGenerationDlg_ColumnWidthPreferences
DESCRIPTION
ReportGenerationDlg_ColumnPreferences preference.
VALID
VALUES
Accepts one or more integers as values. Each integer defines the column width in
characters. The first value set in this preference defines the column width of the
first value set in the ReportGenerationDlg_ColumnPreferences preference,
and so on.

Client preferences
DEFAULT
VALUES
20
20
SCOPE
Site preference.
RESERVATION_object_columns_hidden
DESCRIPTION
Determines which reservation columns are hidden. This preference can also be set
VALID
VALUES
Teamcenter reservation name. Column widths are defined using the
RESERVATION_object_widths_hidden user preference.
DEFAULT
VALUES
release_status_list
revision_number
archive_info
last_mod_user
object_desc
date_released
owning_group
creation_date
archive_date
last_mod_date
backup_date
SCOPE
User preference.
RESERVATION_object_columns_shown
DESCRIPTION
Determines which reservation columns are displayed. This preference can also be
VALID
VALUES
Teamcenter reservation name. Column widths are defined using the
RESERVATION_object_widths_shown user preference.
DEFAULT
VALUES
objects
object_name
object_type
owning_user

node
path
SCOPE
User preference.
RESERVATION_object_widths_hidden
DESCRIPTION
RESERVATION_object_columns_hidden user preference.
VALID
VALUES
in the RESERVATION_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
32
32
32
32
32
32
32
32
32
32
32
SCOPE
User preference.
RESERVATION_object_widths_shown
DESCRIPTION
RESERVATION_object_columns_shown user preference.
VALID
VALUES
in the RESERVATION_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
20
16
32
20

Client preferences
40
SCOPE
User preference.
Selection Criteria
DESCRIPTION
Determines which attachments are checked in and out with the selected item
revision.
Use either the Selection Criteria preference or the Select IR preference to allow
checking item revisions in and out. If both preferences are specified, the values of
the Selection Criteria take precedence. If only the Select IR preference is set, the
item revision objects are selected without attachments.
VALID
VALUES
Valid values are in the format TypeInternalName followed by 10 spaces and then the
RelationInternalName.
DEFAULT
VALUES
UGMASTER IMAN_Specification
UGPART IMAN_Specification
SCOPE
User preference.
Select IR
DESCRIPTION
Determines whether to include the defined item revisions in check in and check out
operations. This same criteria can also be set by users in the interface.
Note
Use either the Selection Criteria preference or the Select IR preference to
allow checking item revisions in and out.
VALID
VALUES
Yes Includes the defined item revisions in the check in and check out operations.
No Does not include the defined item revisions in the check in and check out
operations.
DEFAULT
VALUES
Yes
SCOPE
User preference.

Structure_Alias_File
DESCRIPTION
Determines the alias file applied to the intermediate data capture object to display
its BOM structure. Alias files determine what displays in the IDCWindow. They
determine the root of the window, the children displayed in each line and the
properties for each line. These files contains the following three parent aliases, these
three alias components list all the possible subaliases:
Root Determines the object to be set as the root of the window.
Children Determines the children for each intermediate data capture
line.
Property Determines the properties for each intermediate data capture
line. All the properties for the line are defined as the aliases
under the property alias.
Note
All shipped alias files are stored in the TC_DATA directory.
VALID
VALUES
Accepts a single string as a value. Must be the complete path to the alias XML file.
DEFAULT
VALUES
TC_DATA/structure_alias.xml
SCOPE
All.
TC_AE_<datasettype>_Default_View_Tool
DESCRIPTION
Specifies the tool used by default to view datasets of a particular type. This setting
overrides the first tool listed in the Tools for View list for that particular dataset
type. Use the Tools for View list to specify tools that can be used to view datasets.
The default viewing tool (defined either with this preference, or as the first tool
listed in the Tools for View list) determines which dataset tool is used when opening
datasets from the View command on the File menu.
VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter tool name. Tools are
defined in the Business Modeler IDE application.
DEFAULT
VALUES
None.
SCOPE
Site and user preference.

Client preferences
TC_Allow_Longer_ID_Name
DESCRIPTION
Specifies a maximum for name and ID attributes.
VALID
VALUES
true Allows a maximum size of 128 characters for name and ID attributes.
false Sets the maximum size for name and ID attributes at 32 characters.
DEFAULT
VALUES
true
SCOPE
Site preference.
TC_Auto_Checkout
DESCRIPTION
Enables or suppresses automatic implicit check out of non-NX datasets. Implicit
check out automatically prevents users from gaining write access to a non-NX
dataset if another user has opened it.
VALID
VALUES
ON Enables automatic implicit check out.
OFF Suppresses automatic implicit check out.
DEFAULT
VALUES
ON
SCOPE
Site preference.
TC_auto_login
DESCRIPTION
Enables or suppresses the automatic logon feature for the entire site. Auto logon
uses operating system user names and passwords to log on to Teamcenter.
Note
For the automatic logon feature, the TC_auto_login preference
enables command line utilities. To enable automatic logon, set
enableAutologin=true in the client_specific.properities file.
VALID
VALUES
TRUE Enables automatic logon.
FALSE Suppresses automatic logon.

DEFAULT
VALUES
TRUE
SCOPE
Site preference.
TC_check_out_dir
DESCRIPTION
Specifies the operating system directory that contains exported dataset files. This
preference is only read if the Export Dataset on Checkout check box is enabled on
the checkout dialog box. If TC_checkout_and_export preference is set to 1, the
Export Dataset on Checkout check box is automatically checked.
VALID
VALUES
directory or a null value. For example:
zzz empty string zzz
The null value exports the files to the current working operating system directory.
DEFAULT
VALUES
Null value.
SCOPE
Site preference.
TC_checkout_and_export
DESCRIPTION
Specifies whether Teamcenter exports the file to an operating system directory at
the time of checking out a dataset.
VALID
VALUES
0 Do not export the files to the operating system on checkout.
1 Export files on checkout.
DEFAULT
VALUES
0
SCOPE
User preference.
TC_control_wildcard
DESCRIPTION
Specifies the number of characters that must be entered before a wildcard character
is entered in a search field. The wildcard character is an asterisk (*).

Client preferences
VALID
VALUES
0 No wildcard restrictions; a wildcard can be used alone or with any
combination of valid characters.
Positive The positive integer indicates the number of characters that must be
integer entered in a search field before the wildcard character can be entered.
DEFAULT
VALUES
0
SCOPE
Site preference.
TC_control_wildcard_exception
DESCRIPTION
Specifies the number of characters that must be entered before a wildcard character
is entered in a search field for a specific POM_string attribute of a class. The wildcard
character is an asterisk (*). In the following example, the user must enter at least
three characters in the item search field before a wildcard character can be entered.
TC_control_wildcard_exception=
Item.item_id:3
VALID
VALUES
Valid class name, valid attribute name and a positive integer in the following format:
class-name.attribute-name:positive-integer
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_days_non_login_timeout
DESCRIPTION
Determines whether to allow user logon, based on the number of days that have
passed since the user’s last recorded logon. Use as a security method to disable logon
for users who have not logged into the system for a specified number of days.
At logon, the system reads the last logon date/time. If the value for the last logon
is NULL, if this preference is not set, or if the last logon time falls within the time
period specified by this preference, then user logon is allowed. The current date/time
is written to the last logon value.
VALID
VALUES
Accepts a single, positive integer as a value. The value represents days.
DEFAULT
VALUES
0

SCOPE
Site preference.
TC_DISABLE_FLASH
DESCRIPTION
Enables or suppresses display of the Teamcenter logo (flash screen) while the
workspace is loading. Setting this preference to any value disables the loading of the
flash screen. Leaving this preference unset enables the loading of a flash screen and
points this preference to the IMAN_FLASH_FILE preference, which defines the
specific flash file to be loaded.
VALID
VALUES
Any value (for example, ON, TRUE, or YES).
DEFAULT
VALUES
None.
SCOPE
User preference.
TC_display_group_names_limit
DESCRIPTION
Specifies the limit for the display of group names.
VALID
VALUES
0 or Displays the full group name.
undefined.
1 Displays the first component of the group name.
2 Displays the first two components of the group name; the rest of the full
group name is truncated. An ellipses (...) is appended to the name to indicate
the truncation.
3 Displays the first three components of the group name; the rest of the full
group name is truncated. An ellipses (...) is appended to the name to indicate
the truncation.
4 Displays four or more components of the group name.
DEFAULT
VALUES
0
SCOPE
User preference.

Client preferences
TC_display_real_prop_names
DESCRIPTION
Determines whether to display real property names in the rich client.
VALID
VALUES
0 Does not display real property names in the rich client.
1 Displays real property names in the rich client.
DEFAULT
VALUES
0
SCOPE
User preference.
TC_display_thumbnail_in_UI
DESCRIPTION
Shows or hides thumbnails in the rich client.
Note
Use this preference with the Enable_thumbnails preference so that
Teamcenter generates small thumbnail images using Dispatcher. Teamcenter
downloads these small thumbnails to the rich client for efficient display. If
small thumbnails are not generated, Teamcenter uses the original image
file of the dataset. This will have performance implication on the rich client
for large size images.
VALID
VALUES
TRUE Shows thumbnails.
FALSE Hides thumbnails.
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
TC_Graph_Node_Thumbnail_Shown
DESCRIPTION
Determines whether thumbnail preview images appear above the type name and
symbol in the graphical display of the Generic Relation Browser view.
Note
Enable the Referencers pane with the ReferencersPane_Shown preference.

VALID
VALUES
True Thumbnail preview images appear in the Generic Relation Browser view if
an image is associated with the selected object.
False Thumbnail preview images do not appear in the Generic Relation Browser
view.
DEFAULT
VALUES
True
SCOPE
User preference.
TC_GROUP_PFILE
DESCRIPTION
Points to the operating system directory containing group preference files.
VALID
VALUES
A single string; this string must be the full operating system path name to the
directory.
DEFAULT
VALUES
None.
The Windows default setting %TC_DATA%\gpfiles and the UNIX default setting
$TC_DATA/gpfiles are commented out.
SCOPE
User preference.
TC_ignore_case_on_search
DESCRIPTION
Determines if object searches are case sensitive.
VALID
VALUES
0 Object searches are case sensitive.
1 Mapped attribute searches and saved query searches are case
insensitive when using an appearance set-based search engine (see
PortalDesignContextSearchEnginePreference).
Work part, engineering change, and workflow process searches are case
insensitive when using the Context Definition pane in DesignContext.
DEFAULT
VALUES
1
SCOPE
User preference.

Client preferences
TC_inbox_interval
DESCRIPTION
Determines how often, in minutes, Teamcenter checks a user’s inbox for new tasks.
Note
A small interval, less than 20 minutes, could severely impact performance of
a large database with many users.
VALID
VALUES
-1 Disables checking.
0 Checks once during user logon.
>=time-in-minutes Checks after the defined interval.
DEFAULT
VALUES
-1
SCOPE
User preference.
TC_<datasettype>_Tool
DESCRIPTION
Specifies the default software application (the Teamcenter tool) used to open the
dataset type specified in the preference name using the System→Open command.
Each dataset type requires a separate preference. For example, TC_UGPART_Tool
and TC_UGMASTER_Tool must be separate preferences.
Set each preference to the latest version of NX present on the system or to the
required software application. For example:
TC_UGMASTER_Tool=
UGII V10-ALL
TC_UGPART_Tool=
UGII V10-ALL
TC_Text_Tool=
NoteEditor
VALID
VALUES
System name of the required software application.
DEFAULT
VALUES
TC_UGMASTER_Tool=
UGII V10-ALL
TC_UGPART_Tool=
UGII V10-ALL
TC_Text_Tool=
NoteEditor

SCOPE
Site preference.
TC_markup_named_ref
DESCRIPTION
Specifies the named references that have viewable image files. The named references
of any datasets that require view and markup functionality must be defined in
this preference.
VALID
VALUES
One or more strings as values.
DEFAULT
VALUES
Image
Quickshade-Image
PLT
BMP
CAL
TIFF
Graphics-Interface
JTPART
Sheet
SCOPE
User preference.
TC_max_number_of_retries
DESCRIPTION
Sets the number of times Teamcenter retries an operation when it encounters a
database-level (Oracle or SQL Server) lock before reporting an error. The time
interval between retries is set by the TC_retry_time preference.
The value set in this preference may be overridden by the rdv_import_usage
utility when usages are loaded.
VALID
VALUES
DEFAULT
VALUES
6
SCOPE
User preference.
This preference may also be set in an environment variable.

Client preferences
TC_name_delimiter
DESCRIPTION
Specifies 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, sometimes (such as with the
Teamcenter/STEP Translator) this information must be handled separately. This
delimiter partitions the person name such that another application can break this
single string into multiple strings.
VALID
VALUES
DEFAULT
VALUES
A comma (,).
SCOPE
User preference.
TC_name_sequence
DESCRIPTION
Sets the order in which person information (last name, first name, middle name or
initial) is imported and exported from the database.
VALID
VALUES
One or more of the following values:
first First name.
middle Middle name or initial.
last Last name.
space ASCII soft space character.
delimiter ASCII character defined in the TC_name_delimeter preference.
prefix_titles Prefix; for example: Mr., Mrs., Dr.
suffix_titles Suffix; for example: Jr., Ph.D.

DEFAULT
VALUES
last
delimiter
space
first
SCOPE
User preference.

TC_pattern_match_style
DESCRIPTION
Specifies the wildcard character used for all searches and queries.
VALID
VALUES
1 SQL style: uses the percent sign (%) for multicharacter replacement and an
underscore (_) for single-character replacement.
2 UNIX style: uses an asterisk (*) for multicharacter replacement and a period
(.) for single-character replacement.
3 Windows style: uses an asterisk (*) for multicharacter replacement and a
question mark (?) for single-character replacement.
DEFAULT
VALUES
2
SCOPE
User preference.
TC_QRY_display_latest_dataset_only
DESCRIPTION
Enables the display of only the latest version of dataset objects in results of queries
with search class as the super class of dataset or its descendant classes (for example,
queries with search class as WorkspaceObject).
VALID
VALUES
0
Displays all versions of the dataset.
1
Displays only the latest version of dataset objects.
DEFAULT
VALUES
0
SCOPE
Site preference.
TC_QRY_search_by_rev_rule
DESCRIPTION
Specifies the revision rule used for the latest item revision query.
VALID
VALUES
All revision rules defined in the database (for example, Latest Working).

Client preferences
Note
Values are case sensitive.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_remove_file_on_check_in
DESCRIPTION
Determines whether to delete previously exported files from the operating system
directory specified by the TC_check_out_dir preference. This preference is only
read if the TC_checkout_and_export preference is set to 1.
VALID
VALUES
0 Does not delete existing files from the directory during an explicit checkin
while cancelling a checkout.
1 Deletes existing files from the directory during an explicit checkin or while
cancelling a checkout.
DEFAULT
VALUES
1
SCOPE
Site preference.
TC_retry_time
DESCRIPTION
Determines how often, in seconds, Teamcenter retries an operation when it
encounters a database-level (Oracle or SQL Server) lock before reporting an error.
The number of retries is defined by the TC_max_number_of_retries preference.
The value set in this preference may be overridden by the rdv_import_usage
utility when usages are loaded.
VALID
VALUES
DEFAULT
VALUES
5
SCOPE
User preference.
This preference may also be set in an environment variable.

TC_ROLE_PFILE
DESCRIPTION
Points to the operating system directory containing role preference files.
VALID
VALUES
directory.
DEFAULT
VALUES
None.
The Windows default setting %TC_DATA%\rpfiles and the UNIX default setting
$TC_DATA/rpfiles are commented out.
SCOPE
User preference.
TC_show_checkedout_icon
DESCRIPTION
Enables the display of the checked-out symbol in BOM trees, attachment trees,
activity trees and occurrence group trees, and also in the My Teamcenter view, the
Search Results view, and in detail views.
VALID
VALUES
True The checked-out symbol is displayed in the Structure Manager and My
Teamcenter views. This enhances usability, but it can impact rich client
performance when expanding tree nodes.
False The checked-out symbol is not displayed in the Structure Manager and
My Teamcenter views. This reduces network and database activity and
therefore improves performance compared to the default setting.
DEFAULT
VALUES
True
SCOPE
All.
TC_suppress_Edit_Latest_Menu
DESCRIPTION
Enables or suppresses the Edit Latest command in the rich client. This menu
command updates all version-0 datasets to reference the latest saved version in
the database.
Note
This feature is useful in a network environment when multiple users are
working on the same dataset.

Client preferences
VALID
VALUES
TRUE Enables the Edit Latest command in the rich client.
FALSE Suppresses the Edit Latest command in the rich client.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
TC_suppress_inactive_group_members
DESCRIPTION
Determines whether all group members or only active group members are displayed
in Teamcenter interfaces. You must set this preference and then relaunch
Teamcenter to activate the display suppression for the thin client. In the rich
client, you can switch between suppress or display inactive group members using
the button located on the Group panel of Organization.
VALID
VALUES
0 All group members are displayed.
1 Only active group members are displayed.
DEFAULT
VALUES
1
SCOPE
User preference.
TC_Thumbnail_Tooltip_Properties
DESCRIPTION
Specifies the data that appears over the tooltip of the thumbnail.
VALID
VALUES
Accepts multiple string values. Each string specifies the default view of display of
search result.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_USER_PFILE
DESCRIPTION
Points to the operating system directory containing user preference files.

VALID
VALUES
directory.
DEFAULT
VALUES
None. The Windows default setting %TC_DATA%\upfiles and the UNIX default
setting $TC_DATA/upfiles are commented out.
SCOPE
User preference.
TC_user_delimiters
DESCRIPTION
Specifies the delimiters that are used to separate the user’s name from the user ID
in the list of users in the Organization application user interface.
Note
• Do not use these same delimiters in either the User ID field or Person
Name field for the user.
• If you accidentally use the characters set in this preference when you
create a user or a person, use the make_utility to correct the user ID
and person name delimiters.
VALID
VALUES
Any value, for example, bracket characters { } or parentheses ( ).
The default values are used if the preference is empty or if the preference is defined
with more than two values.
DEFAULT
VALUES
()
SCOPE
User preference.
TCViewMarkupApplicationPref
DESCRIPTION
Defines the priority list of applications used by the View/Markup command to display
selected base datasets and their associated markup data. Even though defined as
a Site preference, values can be given at a user, role, group, or site level in this
order of priority.
VALID
VALUES
PDF_Tool Provides view and markup capabilities using a PDF tool.
MSWord Provides view and markup capabilities using MSWord.

Client preferences
DEFAULT
VALUES
PDF_Tool
SCOPE
All.
TC_wc_allow_subgroup_default
DESCRIPTION
Defines the default setting for the Subgroup Members Allowed check box in the
New Work Context dialog box. This option determines whether subgroup members
of the selected group are allowed to perform a task.
VALID
VALUES
true By default, the check box is checked and subgroup members
are allowed to perform a task.
false By default, the check box is not checked and subgroup members
are not allowed to perform a task.
DEFAULT
VALUES
true
SCOPE
Site preference.
TC_wc_setting_modifiable_default
DESCRIPTION
Defines the default setting for the User Settings Modifiable check box in the New
Work Context dialog box. This option determines whether user settings defined via
the work context can be changed once the work context is set as the current work
context.
VALID
VALUES
true By default, users can reset user settings defined by the work context after
the work context is set as the current work context.
false By default, users cannot reset user settings defined by the work context once
the work context is set as the current work context.
DEFAULT
VALUES
false
SCOPE
Site preference.

TC_wc_show_all
DESCRIPTION
Defines the content of the list of work contexts associated with a user.
VALID
VALUES
TRUE System displays work contexts related to the tasks in the user’s
Task to Perform folder, followed by any other work contexts
created by the user.
FALSE System displays only work contexts related to the tasks in the
user’s Task to Perform folder.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
TOOL_object_columns_hidden
DESCRIPTION
Determines which tool columns are hidden. This preference can also be set by
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter tool
name. Column widths are defined using the TOOL_object_widths_hidden user
preference.
DEFAULT
VALUES
site_classification
vendor_name
version
input_formats
output_formats
object_desc
object_type
release_status_list
revision_number
date_released
archive_info
owning_group
last_mod_user
owning_user
creation_date
archive_date
last_mod_date
backup_date

Client preferences
SCOPE
User preference.
TOOL_object_columns_shown
DESCRIPTION
Determines which tool columns are displayed. This preference can also be set by
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter tool
name. Column widths are defined using the TOOL_object_widths_shown user
preference.
DEFAULT
VALUES
object_name
symbol_name
SCOPE
User preference.
TOOL_object_widths_hidden
DESCRIPTION
TOOL_object_columns_hidden user preference.
VALID
VALUES
in the TOOL_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
32
32
32
32
32
32
32
32
32
32
32
32
32
32
32
32
32

32
SCOPE
User preference.
TOOL_object_widths_shown
DESCRIPTION
TOOL_object_columns_shown user preference.
VALID
VALUES
in the TOOL_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
32
SCOPE
User preference.
Tracelink_deepcopy_on_Revise
DESCRIPTION
Determines deep copy rules for trace link behavior when an item is revised.
VALID
VALUES
1 Copies links from complying and defining objects.
2 Copies links only from defining object.
3 Copies links only from complying objects.
4 Does not copy forward any links.
DEFAULT
VALUES
1
SCOPE
Site preference.
Tracelink_deepcopy_on_SaveAs
DESCRIPTION
Determines deep copy rules for trace link behavior when users perform a SaveAs on
an item.
VALID
VALUES
1 Copies links from complying and defining objects.

Client preferences
2 Copies links only from defining object.

3 Copies links only from complying objects.
4 Does not copy forward any links.
DEFAULT
VALUES
1
SCOPE
Site preference.
treeDisplayOrder
DESCRIPTION
Determines the order in which data is displayed in trees. Users set this preference
in the General page section of the Options dialog box. When users set the display
order through the interface, the system automatically sets this preference in the
user’s preference file.
VALID
VALUES
ascending Data in the tree is sorted in ascending order.
descending Data in the tree is sorted in descending order.
DEFAULT
VALUES
None.
SCOPE
User preference.
<Type>_PseudoFolder
DESCRIPTION
Determines whether pseudo folders are created when the defined object type
is created, and with which relation. The system automatically creates these
preferences when users select pseudo folder options from the Options dialog box,
accessed from the Edit menu in My Teamcenter.
The system creates a preference for each item and item revision type for which
Shown Relations are selected from the Related Object tab of the dialog box. The
preferences are stored in the users preference file.
VALID
VALUES
relation type.
DEFAULT
VALUES
None.
SCOPE
User preference.

<type_name>.CREATERENDERING
DESCRIPTION
Indicates the XML rendering dataset used to render the properties shown in
a creation dialog box for a particular business object type, using the form of
business-object-type.CREATERENDERING=xml-rendering-style-sheet-dataset. For
example, the Item.CREATERENDERING=ItemCreate preference means that for
Item business objects, the ItemCreate XML rendering style sheet dataset is used to
render the properties on creation dialog boxes in the user interface.
Teamcenter property displays are based on an XML style sheet. The style sheet
must be created and registered by a system administrator.
This preference determines the XML rendering for displaying
the defined type’s properties. If this preference is defined, the
<dataset_name>.CREATE_REGISTEREDTO preference must also be defined.
VALID
VALUES
Accepts a single string as a value. It must be a valid dataset name, which contains
rendering XML.
DEFAULT
VALUES
client.
SCOPE
Site preference.
<Type_Name>_DefaultChildProperties
DESCRIPTION
Determines which properties are children of the indicated type. Each type requires
its own preference. The format for each preference is:
Type_Name_DefaultChildProperties=
my_property
VALID
VALUES
property name.
DEFAULT
VALUES
Item_DefaultChildProperties=
IMAN_master_form
bom_view_tags

Client preferences
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEView
altid_list
ItemRevision_DefaultChildProperties=
IMAN_master_form_rev
structure_revisions
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_UG_udf
IMAN_UG_altrep
IMAN_UG_scenario
IMAN_Rendering
view
release_status_list
altid_list
IMAN_3D_snap_shot
Folder_DefaultChildProperties=
contents
Newstuff Folder_DefaultChildProperties=
contents
Mail Folder_DefaultChildProperties=
contents
TaskInBox_DefaultChildProperties=
tasks_to_perform
tasks_to_review
ReviewTeamDefinition_DefaultChildProperties=
valid_signoffs
EPMTask_DefaultChildProperties=
root_target_attachments
root_reference_attachments
release_status_attachments
child_tasks
signoff_profiles
EPMTaskDefinition_DefaultChildProperties=
child_taskdefinition
EPMSelectSignoffTaskDefinition_DefaultChildProperties=
signoff_profiles
EPMDoTaskDefinition_DefaultChildProperties=
EPMDoTask_DefaultChildProperties=
DirectModel_DefaultChildProperties=

Session
DMI_markup
3DMarkup
IMAN_capture
DrawingSheet_DefaultChildProperties=
DMI_markup
Image_DefaultChildProperties=
DMI_markup
User_DefaultChildProperties=
subscribed_inboxes
my_home_folder
Adds
Cancels
EngChange Revision_DefaultChildProperties=
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
affected_items
solution_items
problem_items
reference_items
addressed_by
tasks_to_perform
tasks_to_review
release_status_list
Dataset_DefaultChildProperties=
MSWord_DefaultChildProperties=
Form_DefaultChildProperties=
ItemMaster_DefaultChildProperties=
BOMView_DefaultChildProperties=
BOMViewRevision_DefaultChildProperties=
MEProcess_DefaultChildProperties=
IMAN_master_form
bom_view_tags
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
MEOP_DefaultChildProperties=
IMAN_master_form
bom_view_tags

Client preferences
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
MEProcessRevision_DefaultChildProperties=
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEMfgModel
IMAN_MEOutput
IMAN_METarget
IMAN_MEWorkArea
IMAN_3D_snap_shot
MEOPRevision_DefaultChildProperties=
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEMfgModel
IMAN_MEFeature
IMAN_MEOutput
IMAN_METarget
IMAN_3D_snap_shot
CCObject_DefaultChildProperties=
IMAN_CCContext
config_context
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
StructureContext_DefaultChildProperties=
contents
configuration_context
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
ConfigurationContext_DefaultChildProperties=
revision_rule
variant_rule
closure_rule
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference

CPMarketingBriefRevision_DefaultChildProperties=
CP_Has_Technical_Brief
CP_Has_Design_Brief
CPTechnicalBriefRevision_DefaultChildProperties=
CP_Results_In_Package_Rough
CPThemeBoardRevision_DefaultChildProperties=
CP_Has_Graphical_Element
CPDesignBriefRevision_DefaultChildProperties=
CP_Has_Graphical_Element
SCOPE
<type_name>.FORMRENDERING
DESCRIPTION
Teamcenter form displays are based on an XML style sheet. The style sheet must
be created and registered by a system administrator.
This preference determines the XML rendering for displaying the
defined type’s form properties. If this preference is defined, the
<dataset_name>.FORM_REGISTEREDTO preference must also be defined.
VALID
VALUES
rendering XML.
DEFAULT
VALUES
client.
SCOPE
Site preference.
<type_name>.RENDERING
DESCRIPTION
Indicates the XML rendering dataset used to render the properties
shown in a particular business object type, using the form of
business-object-type.RENDERING=xml-rendering-style-sheet-dataset.
For example, the Item.RENDERING=Item preference means that for Item
business objects, the Item XML rendering style sheet dataset is used to render the
properties in the user interface.

Client preferences
This preference determines the XML rendering for displaying the defined type’s
properties. If this preference is defined, the <dataset_name>.REGISTEREDTO
preference must also be defined.
VALID
VALUES
rendering XML.
DEFAULT
VALUES
client.
SCOPE
Site preference.
<type_name>.SUMMARYRENDERING
DESCRIPTION
Indicates the XML rendering dataset used to render the properties shown
in the Summary tab for a particular business object type, using the form of
business-object-type.SUMMARYRENDERING=xml-rendering-style-sheet-dataset.
For example, the Item.SUMMARYRENDERING=ItemSummary preference
means that for Item business objects, the ItemSummary XML rendering style sheet
dataset is used to render the properties on the Summary tab in the user interface.
This preference determines the XML rendering for displaying the
defined type’s summary properties. If this preference is defined, the
<dataset_name>.SUMMARY_REGISTEREDTO preference must also be defined.
VALID
VALUES
rendering XML.

DEFAULT
VALUES
client.
SCOPE
Site preference.
USER_object_columns_hidden
DESCRIPTION
Determines which user object columns are hidden. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter user
name. Column widths are defined using the USER_object_widths_hidden user
preference.
DEFAULT
VALUES
None.
SCOPE
User preference.
USER_object_columns_shown
DESCRIPTION
Determines which user object columns are displayed. This preference can also be set
VALID
VALUES
name. Column widths are defined using the USER_object_widths_shown user
preference.
DEFAULT
VALUES
user_name
person
user_id
os_username
default_group
volume
SCOPE
User preference.

Client preferences
USER_object_widths_hidden
DESCRIPTION
USER_object_columns_hidden user preference.
VALID
VALUES
in the USER_object_columns_shown user preference, and so on.
DEFAULT
VALUES
None.
SCOPE
User preference.
USER_object_widths_shown
DESCRIPTION
USER_object_columns_shown user preference.
VALID
VALUES
in the USER_object_columns_shown user preference, and so on.
DEFAULT
VALUES
20
20
20
20
20
20
SCOPE
User preference.
WHERE_REFERENCED_RELATIONS_FILTER
DESCRIPTION
Specifies custom relations displayed in the Where Referenced Options relation list.
Added relations are not displayed in the Paste Special, Paste dialog box and are
not defined as child relations.

VALID
VALUES
Accepts string values. Each string must be a relation internal name such as
CP_Has_Copy_Element or CP_Has_Package_Concept.
DEFAULT
VALUES
None.
SCOPE
Site preference.
Word_12_installed
DESCRIPTION
Indicates whether the user has MS Word 2007 installed. To edit requirement
content in a Word window embedded in the View/Edit pane, MS Word 2007 must be
installed and this preference must be set to True. Users can set this preference in
the interface by choosing Edit→Options and selecting the Word 12 Installed check
box in the Requirements Management pane.
The Requirements Manager application itself can be used without MS Word 2007.
For more information about requirement content and using the Requirements
Manager, see the Requirements Manager Guide.
Note
Users who do not have MS Word 2007 installed can edit requirement content
in a separate Word window by choosing the File→Open Text command. This
method requires the installation of the Office 2007 Compatibility Pack.
VALID
VALUES
true Indicates that MS Word 2007 is installed.
false Indicates that MS Word 2007 is not installed.
DEFAULT
VALUES
false
SCOPE
Site preference.
WORKSPACEOBJECT_object_columns_hidden
DESCRIPTION
Determines which workspace object columns are hidden. This preference can also be
VALID
VALUES
Teamcenter workspace name. Column widths are defined using the
WORKSPACEOBJECT_object_widths_hidden user preference.

Client preferences
DEFAULT
VALUES
revision_limit
revision_number
date_released
archive_info
last_mod_user
owning_group
last_mod_date
archive_date
creation_date
backup_date
release_status_list
SCOPE
User preference.
WORKSPACEOBJECT_object_columns_shown
DESCRIPTION
Determines which workspace object columns are displayed. This preference can also
VALID
VALUES
Teamcenter object name. Column widths are defined using the
WORKSPACEOBJECT_object_widths_shown user preference.
DEFAULT
VALUES
object_name
object_type
owning_user
object_desc
SCOPE
User preference.
WORKSPACEOBJECT_object_widths_hidden
DESCRIPTION
WORKSPACEOBJECT_object_columns_hidden user preference.
VALID
VALUES
the WORKSPACEOBJECT_object_columns_hidden user preference, and so on.
DEFAULT
VALUES
6
6

16
16
13
16
16
16
16
16
32
SCOPE
User preference.
WORKSPACEOBJECT_object_widths_shown
DESCRIPTION
WORKSPACEOBJECT_object_columns_shown user preference.
VALID
VALUES
the WORKSPACEOBJECT_object_columns_shown user preference, and so on.
DEFAULT
VALUES
32
16
13
32
SCOPE
User preference.
WS_icon_placement
DESCRIPTION
Determines the location of icons in the workspace.
VALID
VALUES
1 Above.
2 Right.
3 Below.
4 Left.
DEFAULT
VALUES
4
SCOPE
User preference.

Client preferences
WSColumnsHiddenPref
DESCRIPTION
Determines which workspace columns are hidden. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter column
name. Column widths are defined using the WSHiddenColumnWidthsPref user
preference.
DEFAULT
VALUES
item_id
item_revision_id
object_name
object_desc
owning_site
creation_date
date_released
backup_date
archive_date
based_on
revision_number
revision_limit
last_mod_user
process_stage
has_variants
protection
export_sites
publication_sites
SCOPE
User preference.
WSColumnsShownPref
DESCRIPTION
Determines which workspace columns are displayed. This preference can also be set
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter column
name. Column widths are defined using the WSShownColumnWidthsPref user
preference.
DEFAULT
VALUES
object_string
object_type
relation
owning_user

owning_group
last_mod_date
checked_out
SCOPE
User preference.
WSDisplayTypePref
DESCRIPTION
Determines the format of the graphical display.
VALID
VALUES
1 Vertical tree.
2 Horizontal tree.
3 Indented BOM.
DEFAULT
VALUES
3
SCOPE
User preference.
WS_expand_on_paste
DESCRIPTION
Determines whether to expand a folder immediately after an object has been pasted
into it. Because all objects in the folder must be read before it can be opened,
Siemens PLM Software recommends setting this preference to 0 to prevent delays
following the Paste function.
VALID
VALUES
0 Does not expand a folder immediately after an object has been pasted into it.
1 Expands a folder immediately after an object has been pasted into it.
DEFAULT
VALUES
0
SCOPE
User preference.
WSHiddenColumnWidthsPref
DESCRIPTION
Specifies the column width for each column defined in the WSColumnsHiddenPref
user preference.

Client preferences
VALID
VALUES
in the WSColumnsHiddenPref user preference, and so on.
DEFAULT
VALUES
12
8
40
30
12
17
17
17
17
12
3
14
13
15
3
12
30
18
SCOPE
User preference.
WsoFolderSavePref
DESCRIPTION
Determines when to save rich client data.
VALID
VALUES
1 Saves each change immediately.
2 Requires manually saving.
3 Prompts user to save changes at exit.
DEFAULT
VALUES
1
SCOPE
User preference.
WsoInsertNoSelectionsPref
DESCRIPTION
Determines the default rich client folder referenced when no object is selected.

VALID
VALUES
1 User’s Newstuff folder.
2 Top-level folder.
3 None.
DEFAULT
VALUES
1
SCOPE
User preference.
WSOM_find_editUserList
DESCRIPTION
Specifies the users for whom the Edit button is displayed on the My Teamcenter
search panel. This button provides access to the feature for extending existing
queries.
VALID
VALUES
Any valid Teamcenter user ID.
DEFAULT
VALUES
None.
SCOPE
Site preference.
WsoInsertSelectionsPref
DESCRIPTION
Determines the location for new objects in the rich client.
VALID
VALUES
1 All selected folders.
2 First selected folder.
3 User’s Newstuff folder.
4 Saves the object in the database but does not display it in the rich client.
DEFAULT
VALUES
1
SCOPE
User preference.

Client preferences
WSOM_find_list_separator
DESCRIPTION
Defines the character used to separate multiple entries for queries.
Note
No setting for this preference disables multiple entries.
VALID
VALUES
Accepts a single string as a valid value.
DEFAULT
VALUES
;
SCOPE
User preference.
WSOM_find_set_search_limit
DESCRIPTION
Determines the number of objects loaded to workspace after performing a Find
action before asking for user confirmation.
VALID
VALUES
Accepts a positive integer as a value.
DEFAULT
VALUES
30
SCOPE
User preference.
WSOM_find_set_total_limit
DESCRIPTION
Determines the total number of objects that can be returned in My Teamcenter
for any given search operation. This site-wide preference limits the total return
count, not the per-page count determined by the WSOM_find_set_search_limit
user preference.
VALID
VALUES
0 No limit
A single positive The total number of objects to be returned to My Teamcenter
integer. for any given search operation.
DEFAULT
VALUES
0

SCOPE
Site preference.
WSOM_only_edit_effectivity_in_ecm
DESCRIPTION
Enables or suppresses editing of effectivity data outside of the Change Viewer
process.
VALID
VALUES
yes Enables editing of effectivity data outside of the Change Viewer process.
no Suppresses editing of effectivity data outside of the Change Viewer process.
DEFAULT
VALUES
no
SCOPE
Site preference.
WSShownColumnWidthsPref
DESCRIPTION
Specifies the column width for each column defined in the WSColumnsShownPref
user preference.
VALID
VALUES
in the WSColumnsShownPref user preference, and so on.
DEFAULT
VALUES
32
17
13
9
9
17
4
SCOPE
User preference.
Thin client preferences

The thin client provides a streamlined browser-based view of the product information
stored in your Teamcenter database. Most interface display preferences affect both
the rich client and the thin client. The following thin client-specific preferences
modify the display and behavior of only the thin client.

Client preferences
General thin client preferences

Use these preferences to configure general thin client behavior.
appbar_title_contents
DESCRIPTION
Specifies values to be displayed in the title string of the thin client application bar.
They must be on a line by themselves. Any other values are rendered as literal
text with single space separators
VALID
VALUES
user Specifies the full Teamcenter user name.
userid Specifies the Teamcenter logon user name.
group Specifies the group logged on user is assigned to.
role Specifies the role of logged on user.
site Specifies the site identifier.
object Name of selected object.
rev_rule Specifies the revision rule in effect.
application Specifies the active application name.
curr_proj Specifies the current project selected.
version Specifies the version of selection.
DEFAULT
VALUES
(
user
(
userid
)
-
group
/
role
-
rev_rule
-
[
site
]
)

SCOPE
User preference.
JT_WEB_UI_PREF
DESCRIPTION
Works only with Teamcenter’s Automotive Edition–GM Overlay. Suppresses specific
user actions within the thin client.
VALID
VALUES
del Suppresses the ability to delete any object; removes the Delete button from
the thin client.
ini Suppresses the ability to initiate a workflow process; removes the Initiate
Process button from the thin client.
nwl Suppresses the ability to create new web links; removes the New Web Link
button from the thin client.
esv Suppresses the ability to launch external structure viewers; removes the
external structure viewers links from the External Structure Viewers section.
tdim Suppresses the ability to view the selected product in 3D.
pvug Suppresses the ability to launch Teamcenter’s lifecycle visualization products
or NX from a selected object.
pvm Suppresses the ability to create new markups by uploading a file.
wkf Suppresses the ability to perform workflow tasks from the inbox page;
suppresses task hyperlinks.
DEFAULT
VALUES
del
ini
nwl
esv
tdim
pvug
pvm
wkf
SCOPE
Site preference.
TcUseAppLauncher
DESCRIPTION
Specifies whether Teamcenter Application Launcher is used to open and edit Office
datasets in the Teamcenter thin client. Using the launcher enables Teamcenter’s
Client for Microsoft Office.

Client preferences
VALID
VALUES
true Teamcenter Application Launcher is used. Enables Client for Office for
the Teamcenter thin client.
false Teamcenter Application Launcher is not used. Disables Client for Office
for the Teamcenter thin client.
DEFAULT
VALUES
false
SCOPE
Site preference.

WEB_active_optimizer_server
DESCRIPTION
Sets the location of the ActiveWeb Optimizer Web server.
VALID
VALUES
Accepts a single string as a value. Must be a valid server location using the format
www.foo.com or the IP address. Do not include the port with the IP address.
DEFAULT
VALUES
None.
SCOPE
Site preference.
WEB_auto_assign_ds_id
DESCRIPTION
Determines whether a dataset ID should be automatically generated when one is
not provided.
VALID
VALUES
0 Always prompt the user to create a dataset ID.
1 Attempt to automatically generate a dataset ID when one is not provided.
DEFAULT
VALUES
1
SCOPE
User preference.
WEB_<Class>_default_type
DESCRIPTION
Defines the default type to be displayed in the New dialog boxes.
VALID
VALUES
One or more strings; each string must be a valid Teamcenter type.
DEFAULT
VALUES
Item
SCOPE
User preference.

Client preferences
WEB_Change_default_type
DESCRIPTION
Defines the default change type to be displayed in the New Change dialog box.
VALID
VALUES
Single string; the string must be a valid Teamcenter change type.
DEFAULT
VALUES
CR
SCOPE
Site preference.
WEB_core_help_server
DESCRIPTION
Set to the URL of your site’s core Teamcenter online help page. If you are running
online help on the thin client server, you can use a relative URL.
VALID
VALUES
Valid Web server address.
DEFAULT
VALUES
/%DEPLOYED_APP_NAME%/help/index.htm
%DEPLOYED_APP_NAME% is substituted at runtime by retrieving the

application name from the server request.
SCOPE
User preference.
WEB_dataset_shown_relations
DESCRIPTION
Sets the shown relation types for dataset pages. Add Version to this preference to
display dataset versions.
VALID
VALUES
One or more strings; each string must be a valid Teamcenter reference.
DEFAULT
VALUES
Reference
SCOPE
User preference.

WEB_default_site_deployed_app_name
DESCRIPTION
Appends the name of the application to be launched to the server URL defined in the
WEB_default_site_server preference. When both the WEB_default_site_server
and Web_default_site_deployed_app_name preferences are set, this
concatenated URL path is included in Teamcenter mail messages via the CR-notify
handler, which adds the thin client job URL to the notification mail message.
A value for this preference may be provided during installation.
VALID
VALUES
Accepts a single string as a value. Must be the name provided for the Teamcenter
application during installation.
DEFAULT
VALUES
tc
SCOPE
Site preference.
WEB_default_site_server
DESCRIPTION
Sets the server URL to be included in Teamcenter mail messages. You must
also set the Web_default_site_deployed_app_name preference, which
appends the name of the application to be launched to this URL. When both
the WEB_default_site_server and Web_default_site_deployed_app_name
preferences are set, the CR-notify handler adds the thin client job URL to the
notification mail message.
The system also uses this preference’s value for generating bookmark files while
interoperating with Teamcenter’s lifecycle visualization.
VALID
VALUES
This preference must be set in the following format:
wwwserver_name:8080
The server name is the thin client server node name as defined in the browser
location field.
DEFAULT
VALUES
None.
SCOPE
Site preference.

Client preferences
WEB_disable_structure_read_optimizations
DESCRIPTION
Disables optimization in Structure Manager structure that limits depth of
examination to the one currently displayed in browser.
VALID
VALUES
False Suppresses the display of variant options defined at a structure level that
have not been expanded in the thin client Structure Manager and are
unknown to Structure Manager.
True Displays variant options defined anywhere in the structure even if they are
in parts of the structure that have not yet been expanded.
DEFAULT
VALUES
False
SCOPE
Site preference.
WEB_filter_person
DESCRIPTION
Determines whether to automatically filter the SA Person page upon loading.
VALID
VALUES
ON Only a filter field is displayed when the page is opened. Criteria must be
entered into the field. Results display in a list box.
OFF A filter field, filter button, and a list box containing all persons contained
in the database. The list box contents may be extensive for large sites,
slowing loading time.
DEFAULT
VALUES
ON
SCOPE
User preference.
WEB_help_server
DESCRIPTION
Set to the URL of your site’s thin client online help page. If you are running online
help on the thin client server, you can use a relative URL.
VALID
VALUES
Valid Web server address.
DEFAULT
VALUES
/%DEPLOYED_APP_NAME%/help/thin_client_dhtml/book.html

%DEPLOYED_APP_NAME% is substituted at runtime by retrieving the

application name from the server request.
SCOPE
User preference.
WEB_filter_user
DESCRIPTION
Determines whether to automatically filter the SA User page upon loading.
VALID
VALUES
ON Only a filter field is displayed when the page is opened. Criteria must be
entered into the field. Results display in a list box.
OFF A filter field, filter button, and a list box containing all users contained in
the database. The list box contents may be extensive for large sites, slowing
loading time.
DEFAULT
VALUES
ON
SCOPE
User preference.
WEB_protocol
DESCRIPTION
Defines the protocol used by the web server; either http:// or https://
VALID
VALUES
http:// Web server uses the http:// protocol.
https:// Web server uses the https:// protocol.
Use this setting if you are running the Teamcenter Web
application and have configured it use a secure socket layer
(SSL).
For more information about configuring the Teamcenter Web
middle tier, see the basic deployment section of the Web
Application Deployment Guide.
DEFAULT
VALUES
http://
SCOPE
Site preference.

Client preferences
WEB_status_icons
DESCRIPTION
Determines the display of the release status icons in the thin client. You can also
use this preference to configure the display of custom release status icons. List
status names in this preference, then add a corresponding .gif and/or .png file to the
TC_ROOT/web/htdocs/tc/webtier_static/teamcenter/dhtml/icons.
The system retrieves .gif or .png files of the same
name as the values defined in this preference from the
TC_ROOT/web/htdocs/tc/webtier_static/teamcenter/dhtml/icons folder of the
deployed web tier. For example, if the value Approved is set for this preference, the
system looks for Approved.gif and Approved.png. The .gif files are preferred
by Internet Explorer browser, the .png files are preferred by Mozilla. The browser
application first attempts to load the preferred image type, then the non-preferred
type. If neither image is found for the custom status, the ReleaseStatus.gif
or .ReleaseStatus.png is displayed.
Note
Failing to provide the browser’s first choice of images has a performance
impact every time the backup image is loaded. The performance impact can
be significant and should be avoided.
When adding custom release statuses, an icon of the same name (case-sensitive)
must be added to the directory noted above. Then you must regenerate and deploy
using insweb.
Note
This preference can be modified by users in the interface under the WSO
Status Icons heading in the Edit→Options dialog box.
VALID
VALUES
release name, or one of the following custom release statuses:
external_links
in_process
configured
For each string there must be a corresponding .gif and/or .png file placed in the
TC_ROOT/web/htdocs/tc/webtier_static/teamcenter/dhtml/icons folder. The
.gif and .png file names cannot contain spaces; replace any spaces with underscores.
DEFAULT
VALUES
inprocess
configured
TCM Released
Pending
SCOPE
User preference.

WEB_dataset_upload_mode
DESCRIPTION
Determines the default upload mode for datasets.
VALID
VALUES
0 The dataset need not be checked out to upload a file to it. Thus automatic
check out is possible.
1 The dataset must be explicitly checked out to upload a file to it.
DEFAULT
VALUES
0
SCOPE
Site preference.
WEB_column_one_new_window
DESCRIPTION
Determines whether links in the first column of table-based pages open in a new
window.
VALID
VALUES
0 Does not open a new window.
1 Does open a new window.
DEFAULT
VALUES
1
SCOPE
Site preference.
WEB_create_<business_object>_exclude_types
DESCRIPTION
Defines the business objects (types) shown in the Type box in the thin client New
Item dialog box. To access the New Item dialog box, choose New→Item (and the
information derived from item):
• Signal: PSSigna
• Connection: Revisable: PSConnection
• Bid Package: BidPackage
• Commercial Part: CommercialPart

Client preferences
VALID
VALUES
Any business object name is a valid value. The list of business objects in the
preference Current Values box are shown in the Type box on the New Item dialog box.
DEFAULT
VALUES
NULL
SCOPE
Site preference.
WEB_menu_entry_new_window
DESCRIPTION
Lists the names of any menu entries to be opened in a new window.
VALID
VALUES
Accepts multiple strings as values; each string must be a valid Teamcenter menu
entry.
DEFAULT
VALUES
General...
Item — Simple
System Admin
in-CLASS
Web Collection
General Collection
SCOPE
Site preference.
WEB_menu_entry_suppressions
DESCRIPTION
Determines which menu commands display in the user interface. Any menu entry
key defined in this preference is removed from the user interface. For example:
WEB_menu_entry_suppressions=
newChangeAction
This example suppresses the Change menu command from displaying in the thin
client. If all possible commands are removed from a menu, the menu itself is deleted.
For more information about menu suppression, see the Application Administration
Guide.

Note
Thin client menu suppression can work together with the newer command
suppression functionality. Siemens PLM Software recommends using the
more detailed command suppression functionality.
For more information on command suppression, see the Command
Suppression Guide.
VALID
VALUES
Accepts multiple strings as values; each string must be a valid Teamcenter menu
entry key.
DEFAULT
VALUES
None.
SCOPE
Site preference.
WEB_item_default_relation
DESCRIPTION
Sets the default relation for the Paste command.
VALID
VALUES
A valid Teamcenter item relation type.
DEFAULT
VALUES
IMAN_reference
SCOPE
User preference.
WEB_itemrevision_default_relation
DESCRIPTION
Sets the default relation for the Paste command.
VALID
VALUES
A valid Teamcenter item revision relation type.
DEFAULT
VALUES
IMAN_reference
SCOPE
User preference.

Client preferences
WEB_IWantToDefaultActions
DESCRIPTION
Populates the left-hand navigator in the thin client with site preferences based
on the following values.
VALID
VALUES
web_lhn_iwantto_create_item:typeicons/
Item.png:javascript:popupNewBusinessObject(’Item’, true, false)
• The web_lhn_iwantto_create_item string represents the localization key
for the text to show as a link under the I Want To section of the left-hand
navigation bar in the thin client.
• The typeicons/Item.png string represents the icon to show the prefix to the
link text.
• The javascript:popupNewBusinessObject(’Item’, true, false) string

represents the javascript function to be called when the link is clicked.
web_lhn_iwantto_create_dataset:typeicons/
Dataset.png:javascript:popupNewDatasetDialog()
• The web_lhn_iwantto_create_dataset string represents the localization key
for the text to show as a link under the I Want To section of the left-hand
navigation bar in the thin client.
• The typeicons/Dataset.png string represents the icon to show the prefix to

the link text.
• The javascript:popupNewDatasetDialog() string represents the javascript

function to be called when the link is clicked.
web_lhn_iwantto_create_workflow_process:teamcenter/dhtml/images/
process.png:javascript:initiateProcess()
• The web_lhn_iwantto_create_workflow_process string represents the
localization key for the text to show as a link under the I Want To section of the
left-hand navigation bar in the thin client.
• The teamcenter/dhtml/images/process.png string represents the icon to

show the prefix to the link text.
• The javascript:initiateProcess() string represents the javascript function

to be called when the link is clicked.
DEFAULT
VALUES
web_lhn_iwantto_create_item:typeicons/
Item.png:javascript:popupNewBusinessObject(’Item’, true, false)
web_lhn_iwantto_create_dataset:typeicons/
Dataset.png:javascript:popupNewDatasetDialog()
web_lhn_iwantto_create_workflow_process:teamcenter/dhtml/images/
process.png:javascript:initiateProcess()

SCOPE
Site preference.
WEB_login_page
DESCRIPTION
Defines the page to be loaded upon logging in to the thin client.
VALID
VALUES
DEFAULT
VALUES
redirs/homefolder
SCOPE
Site preference.
WEB_max_search_results
DESCRIPTION
Defines the default number of objects returned for a search.
VALID
VALUES
A single integer.
DEFAULT
VALUES
30
SCOPE
User preference.
WEB_NX_UseBookmark
DESCRIPTION
Allows thin client users to use legacy bookmark formats for thin client to NX
communication. By default, PLM XML file formats are used for NX communication.
Note
This is required for versions of NX prior to NX7.
VALID
VALUES
Accepts one of the following strings as values: True or False.
DEFAULT
VALUES
False.
SCOPE
All.

Client preferences
WEB_package_multipart
DESCRIPTION
Defines the directory in which packaged multipart files are stored. This preference
supports markup integration.
VALID
VALUES
Accepts a single string as a value. Must be a valid directory.
DEFAULT
VALUES
/tool_box/zip -q %multipart %filelist
where %multipart is the packaged multipart (output) file name and %filelist is list
of files to be included in this packaged multipart file.
SCOPE
Site preference.
WEB_packaging_extension
DESCRIPTION
Defines the file extension for packaged multipart files. This preference supports
markup integration.
VALID
VALUES
A single string; the string must be a valid file extension type.
DEFAULT
VALUES
zip
SCOPE
Site preference.
WEB_processes
DESCRIPTION
Filters the processes displayed to the user in the New Job dialog box. Not setting
this preference causes all the processes to be displayed.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter workflow
process name.
DEFAULT
VALUES
None.
SCOPE
User preference.

WEB_show_export_nx_assy_menu
DESCRIPTION
Enables the Export NX Assembly menu command in the thin client Structure
Manager.
VALID
VALUES
DEFAULT
VALUES
False.
SCOPE
All.
WEB_show_summary
DESCRIPTION
Determines whether the Summary view of an object appears at the bottom of the
window when the object is selected.
VALID
VALUES
true The Summary view of an object appears at the bottom of the window when
the object is selected.
false The Summary view of an object does not appear at the bottom of the window
when the object is selected.
DEFAULT
VALUES
true
SCOPE
User preference.
WEB_show_unconfigured_revs
DESCRIPTION
Determines whether to display item revisions that have not been configured.
VALID
VALUES
0 Item revisions that have not been configured are not displayed.
1 Item revisions that have not been configured are displayed.
DEFAULT
VALUES
0
SCOPE
All.

Client preferences
WEB_simple_search_queries
DESCRIPTION
Lists single field saved queries to be exposed in the navigation pane quick search box.
VALID
VALUES
Localized query names.
DEFAULT
VALUES
Item ID
Keyword Search
Item Name
Dataset Name
SCOPE
User preference.
WEB_style_sheet_list
DESCRIPTION
Defines the list of style sheets available when using the thin client. The style sheets
can be defined by any URL or file path, local or not, but should point to style sheets
with the appropriate classes defined.
VALID
VALUES
Valid style sheet location; can be either a URL or file path name.
DEFAULT
VALUES
/css/tc.css
SCOPE
User preference.
WEB_style_sheet
DESCRIPTION
Determines the style sheet used by the thin client.
VALID
VALUES
Valid style sheet location; can be either a URL or file path name. The location
need not be local.
DEFAULT
VALUES
/css/tc.css
SCOPE
User preference.

WEB_style_sheet_list_names
DESCRIPTION
Defines the list of names presented as configuration options. This values in
this preference must correspond one-for-one with the values defined in the
WEB_style_sheet_list preference.
VALID
VALUES
Teamcenter
DEFAULT
VALUES
Teamcenter
SCOPE
User preference.
WEB_title_contents
DESCRIPTION
Defines the contents of the thin client title bar.
VALID
VALUES
The following variable values must be on a line by themselves. Any other values are
rendered as literal text with single space separators:
application
object
user
group
role
site
rev_rule
version
DEFAULT
VALUES
The default setting is as follows:
WEB_title_contents=
application
-
object
- [
site
]
SCOPE
User preference.

Client preferences
WEB_unpackage_multipart
DESCRIPTION
Defines the directory in which unpackaged multipart files are stored. This preference
supports markup integration.
VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter directory.
DEFAULT
VALUES
/tool_box/unzip -qq %multipart
where %multipart is the packaged multipart (input) file name.
SCOPE
Site preference.
WEB_use_activex_lov
DESCRIPTION
Determines whether ActiveX or legacy LOVs display in dialog boxes and forms.
VALID
VALUES
yes Enables display of ActiveX LOVs in dialog boxes and forms.
However, ActiveX LOVs display only if supported by the
browser. For example, Internet Explorer security settings
would need to be set to support ActiveX controls. If ActiveX
is not supported by the user’s browser, the following error
displays:
Your current security settings prohibit running ActiveX
controls on this page.
As a result the page may not display correctly
no Displays legacy LOVs in dialog boxes and forms.

DEFAULT
VALUES
yes
SCOPE
Site preference.
WEB_use_lhn_home_component
DESCRIPTION
Determines whether the Home contents appear in the Quick Links section of
the thin client navigation pane by default. Setting this preference to 0 improves
performance, particularly in cases where the user has a large Home folder.

Note
Users can also determine whether the Home contents appear by setting the
Show Home Contents in QuickLinks option in the Options dialog box.
VALID
VALUES
1 The Home contents appear in the Quick Links section of the thin client
navigation pane by default.
0 The Home contents do not appear in the Quick Links section of the thin
client navigation pane by default.
DEFAULT
VALUES
1
SCOPE
User preference.
WEB_use_lhn_inbox_component
DESCRIPTION
Determines whether the inbox contents appear in the Quick Links section of the thin
client navigation pane by default. Setting this preference to 0 improves performance,
particularly in cases where the user has a large inbox.
Note
Users can also determine whether the inbox contents appear by setting the
Show Home Contents in QuickLinks option in the Options dialog box.
VALID
VALUES
1 The inbox contents appear in the Quick Links section of the thin client
navigation pane by default.
0 The inbox contents do not appear in the Quick Links section of the thin
client navigation pane by default.
DEFAULT
VALUES
1
SCOPE
User preference.
Thin client column and property preferences

Use column preferences to define which columns are displayed in the thin client
pages. All column headings for these properties are the same as specified for the
rich client.

Client preferences
WEB_dataset_columns
DESCRIPTION
Defines which properties are displayed as columns in dataset pages.
VALID
VALUES
file_size
object_type
last_mod_date
checked_out
DEFAULT
VALUES
file_size
object_type
last_mod_date
checked_out
SCOPE
User preference.
WEB_inbox_columns
DESCRIPTION
Defines which properties are displayed as columns on inbox pages.
Tip
When using this preference as a user preference, set inbox columns using the
Options dialog box. Using this method, all valid choices are presented in the
dialog box, and manual editing of this preference is not required.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid property of the
EPMTask type.
Note
If using the EPM_comment_attachment property, additional ITK
customization is required before comments will display in the Comments
column.
For more information, see the Integration Toolkit Function Reference manual.
DEFAULT
VALUES
job_name
parent_name
resp_party
creation_date
SCOPE
All.

WEB_psm_columns
DESCRIPTION
Defines which properties are displayed as columns on BOM pages.
VALID
VALUES
bl_config_string
bl_rev_release_status_list
bl_sequence_no bl_all_notes
bl_variant_state
bl_rev_has_variants
bl_variant_condition
bl_is_occ_configured
bl_has_date_effectivity
bl_item_uom_tag
bl_rev_object_desc
bl_has_children
bl_rev_item_revision_id
bl_rev_object_name
bl_item_item_id
bl_item_object_name
bl_line_name
bl_item_object_desc
bl_is_precise
bl_pack_count
bl_is_packed
UG ENTITY HANDLE
UG GEOMETRY
UG NAME
UG REF SET
bl_rev_process_stage
bl_alternate
bl_item_object_type
bl_quantity
bl_compare_change
bl_revision_change
bl_quantity_changebl_view_type
DEFAULT
VALUES
bl_sequence_no
bl_quantity
bl_item_uom_tag
bl_all_notes
SCOPE
Site preference.

Client preferences
WEB_po_columns
DESCRIPTION
Defines which properties are displayed as columns on the search results page after a
find remote search is performed.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter property
name.
DEFAULT
VALUES
po_object_class
po_object_id
po_object_name
po_owning_site
po_owner_id
po_group_id
po_object_rel_stat_names
SCOPE
Site preference.
WEB_wso_columns
DESCRIPTION
Defines which properties are displayed as columns on various pages.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter property
name.
DEFAULT
VALUES
actions
object_type
relation
owning_user
owning_group
last_mod_date
checked_out
release_status_list
object_desc
SCOPE
Site preference.
Folder_ColumnPreferences
DESCRIPTION
Specifies the list of columns to be displayed for folder objects.

VALID
VALUES
object_string
object_type
relation
owning_user
owning_group
last_mod_date
checked_out
release_status_list
DEFAULT
VALUES
object_string
object_type
relation
owning_user
owning_group
last_mod_date
checked_out
release_status_list
SCOPE
Site preference.
Thin Client image preferences

Use image preferences to control which types of images are displayed in the thin
client.
WEB_fullsize_image_generate_type
DESCRIPTION
Defines which full-size image types are generated on thin client pages.
VALID
VALUES
One or more strings as values; each string must be specified as MIME type/subtype.
For example:
image/jpeg, image/tiff, image/gif, image/cgm,
x-world/x-vrml
DEFAULT
VALUES
image/jpeg
SCOPE
Site preference.

Client preferences
WEB_image_size_vert
DESCRIPTION
Defines the vertical dimension for full-size images on thin client pages. Size is set
in pixels.
VALID
VALUES
A single positive integer value.
DEFAULT
VALUES
890
SCOPE
Site preference.
WEB_image_size_horiz
DESCRIPTION
Defines the horizontal dimension for full-size images on thin client pages. Size is
set in pixels.
VALID
VALUES
A single positive integer value.
DEFAULT
VALUES
1048
SCOPE
Site preference.
WEB_show_banner
DESCRIPTION
Determines whether to display the current user’s name, group, role, and site name
in the banner.
VALID
VALUES
ON Displays the current user’s name, group, role, and site name in the banner.
OFF The current user’s name, group, role, and site name is not displayed in the
banner.
DEFAULT
VALUES
ON
SCOPE
Site preference.

WEB_show_thumbnail_image
DESCRIPTION
Determines whether to display thumbnail images in thin client pages.
VALID
VALUES
yes Allows thumbnail images to be displayed.
no Does not allow thumbnail images to be displayed.
DEFAULT
VALUES
yes
SCOPE
Site preference.
WEB_thumbnail_image_display_type
DESCRIPTION
Defines which thumbnail image types can be displayed on thin client pages in order
of preference. The first value is the most preferred image type.
VALID
VALUES
For example:
x-world/x-vrml
DEFAULT
VALUES
image/gif
image/jpeg
SCOPE
Site preference.
WEB_thumbnail_image_generate_type
DESCRIPTION
Defines which thumbnail image types are generated on thin client pages.
VALID
VALUES
For example:
x-world/x-vrml
DEFAULT
VALUES
image/gif

Client preferences
SCOPE
Site preference.
Thin client DesignContext preferences

Use thin client DesignContext preferences to define search behavior for context
searches performed using the thin client.
WebDesignContextDefaultSearchDistance
DESCRIPTION
Defines the search distances for RDV thin client searches. The search returns all
items within the proximity distance defined by this preference, including items
outside the box zone.
Note
If a proximity value is specified in the third screen of the DesignContext
application, the value is applied to target part appearances and the
WebDesignContextDefaultSearchDistance preference applies only to a
box zone outside the search criteria.
VALID
VALUES
Accepts a single string as a value. The string must be a positive integer.
DEFAULT
VALUES
10.0
SCOPE
User preference.
WebDesignContextMaxMatchingBOMLines
DESCRIPTION
Sets the maximum number of search matches to load. If the context search returns
more components than the number defined in this preference, an error is returned.
The user need to increase the setting of this preference.
Use this preference to avoid loading extremely large context search returns.
VALID
VALUES
A positive integer.
DEFAULT
VALUES
None.
SCOPE
All.

WebDesignContextMaxMatchingObjects
DESCRIPTION
Sets the maximum number of objects to add to an RDV context. If the context search
returns more components than the number defined in this preference, an error is
returned. The user needs to increase the setting of this preference.
Use this preference to avoid loading extremely large context search returns.
VALID
VALUES
A positive integer.
DEFAULT
VALUES
None.
SCOPE
All.
RDVThinClientBomlinePropsDisplay
DESCRIPTION
This preference specifies the BOM line properties displayed in DesignContext in the
thin client. This site preference must contain system names, not display names.
VALID
VALUES
bl_indented_title
bl_variant_state
bl_formula
DEFAULT
VALUES
bl_indented_title
SCOPE
Site preference.
RDVThinClientUserProductItem
DESCRIPTION
This preference is used to store the Product Item set by the user during the last
design context session in the thin client.
VALID
VALUES
item_name
DEFAULT
VALUES
No default value.
SCOPE
User preference.

Client preferences
RDVThinClientUserrevisionRule
DESCRIPTION
This preference is used to store the Revision Rule set by the user during the last
design context session in the thin client.
VALID
VALUES
revision_rule_name
DEFAULT
VALUES
No default value.
SCOPE
User preference.
Thin client Teamcenter’s manufacturing process management

preferences
Manufacturing report generation functionality in the thin client requires the
Report Generator and PLM XML features of Teamcenter. Ensure that you have the
appropriate Java Runtime Environment (JRE) and Lifecycle Visualization software
installed on your system. Lifecycle Visualization allows you to create and view
2D and 3D images in reports.
For the administrative prerequisites for generating thin client reports, see the
Getting Started with Manufacturing.
Tip
Be sure to read the section on creating reports in thin client in the Getting
Started with Manufacturing before setting the following preferences. This
section contains important prerequisite and configuration information.
Note
Read the section on using report templates in the Thin Client Interface Guide
for information about using these reports via the thin client.
WEB_ZoneProcess_Reports
DESCRIPTION
Used for Teamcenter’s manufacturing process management Web reports. Defines
which report formatters (XSL style sheets) can be retrieved when the zone process
report type MEPrZoneProcess is selected from the Generate ME Report menu.
Three report formats can be created from this report type:
Zone Datum Key All datums associated with any MELocateCompOp process
that is a child of any children of the zone display in a table.
Zone Weld Data All welds associated to the MEWeldOP process below the zone
Key are represented in a table.

Inspection Contains links to files that help in identification of the location

Report of a weld.
VALID
VALUES
zone_datum.xsl
zone_weld.xsl
inspection_report.xsl
DEFAULT
VALUES
zone_datum.xsl
zone_weld.xsl
SCOPE
Site preference.
WEB_StationProcess_Reports
DESCRIPTION
which report formatters (XSL style sheets) can be retrieved when the station process
report type MEPrStatnProcess is selected from the Generate ME Report menu.
The following report formats can be created from this report type:
Station Datum All datums associated with any MELocateCompOp process
Key that is a child of any children of the station display in a table.
Station Weld All welds associated with any MEWeldOp process that is a
Data Key child of any children of the station display in a table.
Process Flow Displays the image attached to this station process as
Sheet a TMXMisc dataset type, using the following naming
convention: PF_*.jpg. If multiple files match the naming
convention, the entire report structure is repeated, with a
different picture embedded in each.
Contains a table of all the consumed corporate parts
(MEConsumed/MEWorkpiece) and occurrence groups
(MEConsumed/MEWorkpiece) assigned to the station
process and the process hierarchy under it.
Metal Removal Displays the image attached to this station process as
convention: MR_*.jpg. If multiple files match the naming

Client preferences
Sealer Displays the image attached to this station process as

Application a TMXMisc dataset type, using the following naming
Sheet convention: SA_*.jpg. If multiple files match the naming
Hemmer Data Displays the image attached to this station process as
convention: HD_*.jpg. If multiple files match the naming
Induction Cure Displays the image attached to this station process as
convention: IC_*.jpg. If multiple files match the naming
Fastener Data Displays the image attached to this station process as
convention: FD_*.jpg. If multiple files match the naming
VALID
VALUES
station_datum.xsl
station_weld.xsl
process_flow.xsl
metal_removal.xsl
sealer_application.xsl
hemmer_data.xsl
induction_cure.xsl
fastener_data.xsl
DEFAULT
VALUES
station_datum.xsl

station_weld.xsl
process_flow.xsl
metal_removal.xsl
sealer_application.xsl
hemmer_data.xsl
induction_cure.xsl
fastener_data.xsl
SCOPE
Site preference.
WEB_MEWeldOp_Reports
DESCRIPTION
which report formatters (XSL style sheets) can be retrieved when the weld operation
report type MEWeldOp is selected from the Generate ME Report menu. These
report formats contain links to files that help in identification of location of a weld.
VALID
VALUES
weld_data_8X11.xsl
weld_data_11X17.xsl
DEFAULT
VALUES
weld_data_8X11.xsl
weld_data_11X17.xsl
SCOPE
Site preference.
WEB_MEPrPlantProcess_Reports
DESCRIPTION
Used for Teamcenter’s manufacturing process management Web reports.
Defines which report formatter (XSL style sheet) can be retrieved when the
MEPrPlantProcess report type is selected from the Generate ME Report menu.
This report format contains links to files that help in identification of location of a
weld.
VALID
VALUES
DEFAULT
VALUES
SCOPE
Site preference.

Client preferences
WEB_MELocateCompOp_Reports
DESCRIPTION
which report formatter (XSL style sheet) can be retrieved when the CD lead sheet
MELocateCompOp report type is selected from the Generate ME Report menu.
This report format links the Sequence of Zone Datum Key and Station Datum
Key reports.
VALID
VALUES
cd_leadsheet.xsl
DEFAULT
VALUES
cd_leadsheet.xsl
SCOPE
Site preference.
Class_Resource_WeldGun
DESCRIPTION
Used for Teamcenter’s manufacturing process management Web reports. Defines the
class names for the weld gun used within the report formatter (XSL style sheets).
VALID
VALUES
Weld Guns
DEFAULT
VALUES
None.
SCOPE
User preference.
Class_Resource_Robot
DESCRIPTION
class names for the robot used within the report formatter (XSL style sheets).
VALID
VALUES
Robots
DEFAULT
VALUES
None.
SCOPE
User preference.

TC_suppress_report_designs
DESCRIPTION
Determines whether specified manufacturing report formatters display in the
Teamcenter’s manufacturing process management thin client.
VALID
VALUES
Process-Structures The Process_Structure.xsl report formatter is
suppressed. Process structure reports do not display as a
report template option.
Product-Structures The Product_Structure.xsl report formatter is
suppressed. Product structure reports do not display as a
report template option.
Plant-Structures The Plant_Structure.xsl report formatter is suppressed.
Plant structure reports do not display as a report template
option.
DEFAULT
VALUES
Process-Structures
Product-Structures
Plant-Structures
SCOPE
Site preference.
TC_TransferMode_XMLReport
DESCRIPTION
closure rule used to generate XML files containing reports.
Note
The default value should not be changed.
VALID
VALUES
Accepts a single string as a value. String must be a valid closure rule. The default
value should not be changed.
DEFAULT
VALUES
web_reports
SCOPE
Site preference.

Client preferences
TC_Report_Transfer_Area
DESCRIPTION
absolute path to the working directory in which reports are generated.
Note
VALID
VALUES
Accepts a single string as a value. String must be the absolute path to the working
directory in which reports are generated. The default value should not be changed.
DEFAULT
VALUES
%TC_ROOT%\web\htdocs\web_reports\temp (Windows)
/vobs/web_src/htdocs/web_reports/temp (UNIX)
SCOPE
Site preference.
Batch_Report_Request_File
DESCRIPTION
absolute path to the flat file that defines how batch reports are generated.
Note
VALID
VALUES
Accepts a single string as a value. String must be the absolute path to the flat file.
DEFAULT
VALUES
%TC_ROOT%\web\htdocs\web_reports\data\batch_request.txt (Windows)
/vobs/web_src/htdocs/web_reports/data/batch_request.txt (UNIX)
SCOPE
Site preference.
Web_Report_Jars
DESCRIPTION
absolute path to the report JAR files.

Note
VALID
VALUES
Accepts a single string as a value. String must be the absolute path to the directory
in which the report JAR files for the JT Viewer are stored. The default value should
not be changed.
DEFAULT
VALUES
%TC_ROOT%\web\htdocs\web_reports\jar (Windows)
/vobs/web_src/htdocs/web_reports/jar (UNIX)
SCOPE
Site preference.

Chapter
11 Workflow preferences
SIGNOFF_required_group_and_role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
SIGNOFF_fill_in_reviewers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
CR_allow_alternate_procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
TC_CM_approvers_modifier_roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
EPM_adhoc_signoffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
SIGNOFF_adhoc_quorum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
EPM_enable_apply_template_changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
EPM_valid_user_to_apply_assignment_list . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
EPM_valid_roles_to_assign_responsible_party . . . . . . . . . . . . . . . . . . . . . . . 11-5
EPM_multiple_processes_targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
EPM_sub_process_target_inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
EPM_ARG_target_user_group_list_separator . . . . . . . . . . . . . . . . . . . . . . . . 11-8
EPM_resource_pool_recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
EPM_resource_pool_restrict_subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Global_transfer_access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
TCVIEWER_default_workflow_view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
WORKFLOW_new_route_task_panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
INBOX_hide_suspended_tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
TASK_MONITOR_SLEEP_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
ORG_UIF_spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
ORG_UIF_user_name_display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
WORKFLOW_adhoc_process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
WORKFLOW_advanced_paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
TC_external_default_launch_ui . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
EPM_notify_url_format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14
RICH_CLIENT_MARKER_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14

Chapter
11 Workflow preferences
Workflow automates one or more business processes to accomplish an objective.

Teamcenter workflow applications include Workflow Viewer, Workflow Designer, and
the worklist in My Teamcenter. Users use workflow to pass documents, information,
and tasks among participants during the completion of a particular process.
Workflows can also be used to distribute parts, projects, assignments, documents
and other business process elements throughout your organization based on process
templates that you design in Workflow Designer. The workflows distribute the
objects through worklists displayed in My Teamcenter.
For more information, see the Workflow Designer Guide.
Use workflow preferences to modify the behavior and display of the workflow
applications.
SIGNOFF_required_group_and_role
DESCRIPTION
Determines whether a user must be logged in to the correct group/role to perform an
assigned perform-signoffs task.
VALID
VALUES
0 User must be a registered member of the group and role required by the
perform-signoffs task, but does not have to be logged in as a member of that
group or role to perform the task.
1 User must be a registered member of the group and role required by the
perform-signoffs task and must be logged in as a member of that group
or role to perform the task.
DEFAULT
VALUES
0
SCOPE
Site preference.
SIGNOFF_fill_in_reviewers
DESCRIPTION
Determines how group members are selected by the CR-fill-in-reviewers handler.
Preference behavior is determined by the user’s current logon settings.

Chapter 11 Workflow preferences
VALID
VALUES
1 Selects all group members from the user’s current logon setting. Selects
all group members from the user’s default group setting. Selects all group
members from any other groups to which the user belongs.
2 Selects all group members from the user’s current logon setting. Selects all
group members from the user’s default group setting.
3 Selects all group members from the user’s current logon setting.
DEFAULT
VALUES
1
SCOPE
All.
CR_allow_alternate_procedures
DESCRIPTION
Determines whether users can select alternate workflow processes from the New
Process Dialog dialog box using Process Template Filter.
VALID
VALUES
any The dialog box displays the All and Assigned options. The All option is
preselected.
Assigned The dialog box displays the All and Assigned options. The Assigned
option is preselected.
none The dialog box does not display the All and Assigned options. It is
populated with all assigned templates. If no assigned templates are
defined for the logged on group/role, the template section of the dialog
box is empty.
DEFAULT
VALUES
any
SCOPE
User preference.
TC_CM_approvers_modifier_roles
DESCRIPTION
Lists Teamcenter roles that can create, modify and delete Change Viewer approver
lists.
VALID
VALUES
One or more strings as a value; each string must be a valid Teamcenter role.
DEFAULT
VALUES
None.

Workflow preferences
SCOPE
Site preference.
EPM_adhoc_signoffs
DESCRIPTION
Determines whether ad hoc signoff functionality is enabled.
VALID
VALUES
ON Ad hoc signoff functionality is enabled. Workflow participants performing
Select Signoff Team tasks can select workflow signoff users individually
and can select profiles.
OFF Ad hoc signoff functionality is disabled. Workflow participants performing
Select Signoff Team tasks can select profiles, but can’t select workflow
signoff users individually.
DEFAULT
VALUES
ON
SCOPE
User preference.
SIGNOFF_adhoc_quorum
DESCRIPTION
Determines the constraints placed on changing the quorum value during team
selection.
VALID
VALUES
1 When ad hoc signoff is enabled, changing the quorum value during signoff
team selection is allowed with no constraints.
2 When ad hoc signoff is enabled, changing the quorum value during signoff
team selection is allowed only if the new quorum is greater than that set in
the task’s template.
DEFAULT
VALUES
1
SCOPE
Site preference.
EPM_enable_apply_template_changes
DESCRIPTION
Determines whether edits to a workflow template can be applied to all active
workflow processes based on the template.

If this preference is set to NONE, edits to a workflow template cannot be applied

to active workflow processes based that template. The changes in the workflow
template are applied only to future implementations.
If this preference is set to OPTIONAL, administrators can choose on a case-by-case
basis whether to apply template edits to active workflow processes based on
the template. After editing a workflow template and selecting the Set Stage to
Available check box to change its stage to Available, a dialog box appears in which
the administrator must indicate whether to apply the edits to all active workflow
processes based on the template. By selecting Yes in the dialog box, active workflow
process based on the edited template is updated as follows:
• If the edits in the workflow template occur later in the workflow than the active
workflow process has reached, the edits are applied to the workflow.
• If the edits in the workflow template occur earlier, and the active workflow has
already passed the place where the edits were made, the edits do not take effect,
unless the task/path is re-executed using backward branching/loops, or when a
task is demoted.
• If the edits in the workflow template impact an active task, the edits are applied
after the task completes and only take effect if the task is re-executed.
• If the edits delete the currently active task, the next task is started.
If set to AUTOMATIC, edits made to a workflow template are automatically

applied on all active workflow processes based on the edited template. Each active
process based on the edited template is updated by the same methodology as listed
previously.
By default, this setting applies the edits in the background. However, this
functionality requires a four-tier architecture environment. (Users running
in a two-tier environment can successfully submit requests for asynchronous
processing if there is a four-tier Teamcenter environment available to accept the
request.) Additionally, Dispatcher must be enabled and configured for asynchronous
processing.
Note
If background processing is not configured and supported at your site, active
workflow processes are updated in real time, regardless of this preference
setting. When updating in real time, the Teamcenter interface pauses until
the updates complete.
VALID
VALUES
NONE
Template edits cannot be applied to active workflow processes.
OPTIONAL
Administrators can choose on a case-by-case basis whether to apply template edits to
active workflow processes based on the template.
AUTOMATIC
Edits made to a workflow template are automatically applied on all active workflow
processes that are based on the edited template.

DEFAULT
VALUES
NONE
SCOPE
Site preference.
EPM_valid_user_to_apply_assignment_list
DESCRIPTION
Determines which users are authorized to use the Assign All Tasks feature for
assigning resources to workflow processes. The feature allows users to assign all
tasks in a new or in-progress workflow process using process assignment lists.
VALID
VALUES
Accepts multiple strings as values. Each string must be one of the following values.
If specifying one or more group/role pairs, each group and role must be a valid
Teamcenter group and role.
owner The owning user of the workflow process is authorized to use
this feature.
owning group All users belonging to the owning group of the workflow process
are authorized to use this feature.
world All users are authorized to use this feature.
privileged Group and site administrators are authorized to use this
feature.
Group:role Members of the specified group and role are authorized to
use this feature.
DEFAULT
VALUES
owner
SCOPE
Site preference.
EPM_valid_roles_to_assign_responsible_party
DESCRIPTION
Determines the list of privileged users allowed to reassign the responsible party
responsibility of a task.
VALID
VALUES
Accepts multiple strings as values. Each string must be one of the following values.
responsible_party Allows the current responsible party to reassign the
responsible party responsibility of a task.
active_surrogate Allows the current surrogate user to reassign the
responsible party responsibility of a task.

task_owner Allows the owning user of the workflow process to reassign

the responsible party responsibility of a task.
task_owning_group Allows all users belonging to the group of the owning
user of the process to reassign the responsible party
world Allows all users to reassign the responsible party
privileged Allows the following users to reassign the responsible
party responsibility of a task:
• Current task owner
• Responsible party
• All administrative users
group::role Allows members of a specific group and role to reassign

the responsible party responsibility of a task. It must be
entered in the following format:
group::role
group is a valid Teamcenter group name and role is a
valid Teamcenter role name.
DEFAULT
VALUES
privileged
SCOPE
Site preference.
EPM_multiple_processes_targets
DESCRIPTION
Determines whether to allow multiple processes for the same objects.
Additionally, the EPM_sub_process_target_inheritance preference depends upon
the setting of this preference to determine the behavior of the Inherit Targets check
box, which appears as users create workflow subprocesses.
VALID
VALUES
ON Allows multiple processes for the same objects.
OFF Does not allow multiple processes for the same objects.
DEFAULT
VALUES
ON
SCOPE
Site preference.

EPM_sub_process_target_inheritance
DESCRIPTION
Works with the EPM_multiple_processes_targets preference to determine the
behavior of the Inherit Targets check box that appears as users create workflow
subprocesses.
Preferences Settings Behavior

EPM_multiple_processes_targets ON When the New Sub-Process dialog box
EPM_sub_process_target_inheritance ON appears, the Inherit Targets check box is
selected by default. Users can clear the
check box.
If left selected, subprocesses inherit the
target objects of the parent process.
EPM_multiple_processes_targets ON When the New Sub-Process dialog box

EPM_sub_process_target_inheritance OFF appears, the Inherit Targets check box
is clear by default. Users can select the
check box.
If left clear, subprocesses do not inherit
the target objects of the parent process.
EPM_multiple_processes_targets OFF When the New Sub-Process dialog box

EPM_sub_process_target_inheritance any appears, the Inherit Targets check box is
setting clear by default. Users can not modify the
check box.
Subprocesses do not inherit the target
objects of the parent process.
Regardless of how these two preferences are set to control the inheritance of target
objects from the parent process, users can always manually add or remove targets
from subprocesses.
VALID
VALUES
ON When the New Sub-Process dialog box appears, the Inherit Targets check
box is selected by default. Users can clear the check box.
OFF When the New Sub-Process dialog box appears, the Inherit Targets check
box is clear by default. Users can select the check box.
DEFAULT
VALUES
ON
SCOPE
Site preference.

EPM_ARG_target_user_group_list_separator
DESCRIPTION
Determines the separator used when multiple values are used in a handler
argument. If this preference is left unset, a comma is used.
VALID
VALUES
Accepts a single ASCII character as a value.
DEFAULT
VALUES
,
SCOPE
All.
EPM_resource_pool_recipients
DESCRIPTION
Specifies the recipients of task notification e-mails based on resource pool data. Task
notification e-mails are sent when a resource pool is selected as a task notification
recipient.
VALID
VALUES
all All members belonging to the resource pools’ specified group and
role are notified.
subscribed Only users who are subscribed to the resource pool are notified.
DEFAULT
VALUES
subscribed
SCOPE
All.
EPM_resource_pool_restrict_subscription
DESCRIPTION
Determines whether users’ subscription access to resource pools is restricted. If
restricted, users can only subscribe to resource pools for groups/roles of which they
are a member.
Note
This preference setting is not asserted retroactively.
For example, in a situation where the setting is OFF and users have
subscribed to resource pools of which they are not members, changing the
setting to ON does not remove the existing subscriptions. Only future
subscriptions are restricted.

VALID
VALUES
ON Only the groups/roles of which the user is a member are available for
subscription in the Resource Pool Subscription dialog box.
OFF All users can subscribe to any resource pool; however, they can only
perform tasks if they are valid group/role members.
In the rich client, the Accessible option is selected by default.
In the thin client, the Accessible accessible option is selected by
default.
DEFAULT
VALUES
OFF
SCOPE
Site preference.
Global_transfer_access
DESCRIPTION
Sets the access to the global_transfer utility. Using this utility, users can
transfer their own tasks to another user, or other tasks to other users. A group
administrator can transfer multiple assigned tasks to other group members. A
system administrator can transfer any user’s tasks to another user.
Note
All users, regardless of this preference setting, can use the global transfer
functionality to transfer their own tasks to someone else.
VALID
VALUES
0 Allows system administrator access.
1 Allows system administrator and group administrator access.
2 Allows all users access.
DEFAULT
VALUES
1
SCOPE
Site preference.
TCVIEWER_default_workflow_view
DESCRIPTION
Determines the default display of the Viewer tab to either Task View or Process
View. If the view is changed from the default setting during a particular session,
that view is persistent for that session only.

VALID
VALUES
task Displays the Task View window.
process Displays the Process View window.
DEFAULT
VALUES
task
SCOPE
User preference.
WORKFLOW_new_route_task_panel
DESCRIPTION
Determines the display of the Task View pane when selecting the Signoff Team
for a Route task. This pane displays either with option buttons for selecting the
assignment action, or with a list box.
Note
The option button display is a legacy method and is not supported.
When using the option button view, by default each name is added to the Signoff
Team with the Review action designation. Users must change this designation one
name at a time. This is time consuming when adding large address lists and a
different designation is required.
When using the list box method, users choose the action designation at the same
time the name is added to the Signoff Team. For example, when adding the QA
address list to the Signoff Team, the user can select the Notify action. Every member
of the QA team is automatically assigned the Notify designation.
For information about configuring Route tasks within a workflow template, see
the Workflow Designer Guide. For more information about how Route tasks are
performed by users, see the Rich Client Interface Guide.
VALID
VALUES
ON Displays the list box view of the Task View pane when selecting the
Signoff Team for a Route task.
OFF Displays the option button view of the Task View pane when selecting
the Signoff Team for a Route task.
DEFAULT
VALUES
ON
SCOPE
Site preference.

INBOX_hide_suspended_tasks
DESCRIPTION
Determines how a user’s inbox displays tasks when they are in either the Suspend
or Resume state.
VALID
VALUES
0 Affects only the task it is performed upon. Does not remove/add a task
from/to a user’s inbox.
1 Affects only the task it is performed upon. It removes/adds tasks from/to
a user’s Tasks to Perform inbox folder. Only the process initiator’s inbox
displays the task process in his Tasks to Track folder.
2 Affects the entire workflow process related to the task it is performed upon.
Does not remove/add a task from/to a user’s inbox.
3 Affects the entire process related to the task it is performed upon. It
removes/adds tasks from/to a user’s Tasks to Perform inbox folder. Only the
process initiator’s inbox displays the task process in his Tasks to Track folder.
DEFAULT
VALUES
0
SCOPE
Site preference.
TASK_MONITOR_SLEEP_TIME
DESCRIPTION
Specifies the number of minutes in the sleep period of the Task Monitor daemon
between dispatching cycles.
For more information about using this daemon, see the System Administration
Guide.
VALID
VALUES
Positive integer up to 1,440 (the number of minutes in a 24-hour day).
DEFAULT
VALUES
30
SCOPE
Site preference.
ORG_UIF_spacing
DESCRIPTION
Sets spacing in pixels between nodes in the organizational chart.

VALID
VALUES
Single integer as a value.
DEFAULT
VALUES
15
SCOPE
Site preference.
ORG_UIF_user_name_display
DESCRIPTION
Determines whether user name, person name, or both should be used in the
organizational chart.
VALID
VALUES
1 User name.
2 Person name.
3 Person name (user name).
DEFAULT
VALUES
1
SCOPE
Site preference.
WORKFLOW_adhoc_process
DESCRIPTION
Determines which types of user are allowed to modify the structure and behavior
of an active workflow process.
Users granted this access can modify an active workflow process using Workflow
Viewer in Design mode.
Note
Only one workflow process at a time can be selected for modification using
this method.
You can modify all active workflow processes based on a selected
workflow process template from Workflow Designer if the
EPM_enable_apply_template_changes preference is set to OPTIONAL
or AUTOMATIC.
VALID
VALUES
0 All users have access.
1 System administrators and users granted edit access to Workflow Designer
using the Authorization application have access.

2 System administrators, group administrators, and users granted edit access

to Workflow Designer using the Authorization application have access.
DEFAULT
VALUES
2
SCOPE
Site preference.
WORKFLOW_advanced_paste
DESCRIPTION
Determines whether the Advanced Paste option is available in the New Process
dialog box. This option opens the Advanced Paste Attachment dialog box, used to
build and append a single-level list to the process targets or process references
list. The list can be built from a variety of sources, including query results and
Structure Manager.
VALID
VALUES
ON Displays the Advanced Paste option in the New Process dialog box.
OFF Does not display the Advanced Paste option in the New Process dialog box.
DEFAULT
VALUES
OFF
SCOPE
User preference.
TC_external_default_launch_ui
DESCRIPTION
Determines which Teamcenter client (rich client or thin client) is used to launch
remote Teamcenter objects. For use with remote inbox functionality. If remote
workflow is enabled, this preference determines which client is used to view the
Teamcenter objects contained within remote tasks.
For more information about viewing remote inboxes, see the Rich Client Interface
Guide.
VALID
VALUES
thin Displays remote objects via the thin client.
rich Displays remote objects via the rich client.
dynamic Displays remote objects in same client being used to display local
workflow.
DEFAULT
VALUES
thin
SCOPE
User preference.

EPM_notify_url_format
DESCRIPTION
Determines which types of URLs are inserted into Teamcenter’s task notification
e-mail.
VALID
VALUES
Accepts one or more of the following values:
rich Inserts a URL to task object that launches the rich client when clicked.
dhtml Inserts a URL to task object that launches the thin client when clicked.
none No URL is inserted in the notification e-mail.
DEFAULT
VALUES
rich
dhtml
SCOPE
All.
RICH_CLIENT_MARKER_ID
DESCRIPTION
Defines the server marker identifying the site to launch the Teamcenter object via
the URL inserted into the task notification e-mail (see the EPM_notify_url_format
preference). The Server field in the resulting logon dialog box is populated with
this value.
VALID
VALUES
Accepts a single string as a value. Must be a valid server marker. Typically this is
the server marker used for the Teamcenter installation and the value is found in the
site_specific.properties file.
DEFAULT
VALUES
None.
SCOPE
All.

Chapter
12 Change Viewer preferences
CM_color_of_add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
CM_color_of_cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
CM_color_of_common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
CM_color_of_moved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
CM_color_of_notechange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
CM_color_of_quantity_change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
CM_color_of_reshaped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
CM_color_of_variantchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
CM_initial_position_of_sliders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
CM_progression_tree_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
CM_show_common_parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
ECM_affected_item_relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
ECM_bomchange_formtype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
ECM_bomchange_tooltip_properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
ECM_change_id_modifiable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
ECM_change_name_is_mandatory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
ECM_delivered_engine_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
ECM_form_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
ECM_genealogy_expansion_rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
ECM_note_types_to_track . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
ECM_notehistory_extra_columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
ECM_prev_structure_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
ECM_prev_structure_relation_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
ECM_property_access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
ECM_property_display_names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
ECM_property_names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
ECM_pseudofolder_names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
ECM_set_genealogy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
ECM_supercedure_tooltip_properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
ECM_track_variant_condition_changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
ECM_varianthistory_extra_columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Enable_Create_Classic_Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
Enable_Show_Classic_Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
EngChange Revision_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . 12-16
Supercedure_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
TAE_CM_change_name_is_mandatory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
TAE_CM_show_task_viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
TC_bomchange_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
TC_supercedure_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18

Chapter
12 Change Viewer preferences
Change Viewer is the process of controlling changes to a product’s definition and

configuration. Change Viewer provides an auditable history of the objects used in
a process, making an object’s various usages traceable. Your site can use Change
Viewer to propose, incorporate, review, and approve changes. Change Viewer can
also be used to track and report change history, and to notify members of your
organization of changes. You configure Change Viewer objects using the Change
Viewer.
For more information, see the Change Viewer Guide.
Use Change Viewer preferences to modify Change Viewer behavior in Structure
Manager and Change Viewer.
Note
Change Viewer is deprecated. If you are using Change Manager, see Change
Manager preferences.
CM_color_of_add
DESCRIPTION
Specifies the default color to represent BOM adds in the rich client interface. Colors
must be specified in RGB format. Red, green, and blue can be combined in various
proportions to obtain any color in the visible spectrum. Levels of R, G, and B can
each range from 0 to 100 percent of full intensity. Each color level is represented by
the range of decimal numbers from 0 to 255. The total number of available colors is
256 x 256 x 256, or 16,777,216 possible colors.
Users can also set this preference for their environment using the
Edit→Options→Change Management menu command.
VALID
VALUES
Decimal numbers from 0 to 255.
DEFAULT
VALUES
64,79,161
Blue
SCOPE
User preference.

Chapter 12 Change Viewer preferences
CM_color_of_cancel
DESCRIPTION
Specifies the default color to represent BOM cancels in the rich client interface.
Colors must be specified in RGB format. Red, green, and blue can be combined in
various proportions to obtain any color in the visible spectrum. Levels of R, G, and B
can each range from 0 to 100 percent of full intensity. Each color level is represented
by the range of decimal numbers from 0 to 255. The total number of available colors
is 256 x 256 x 256, or 16,777,216 possible colors.
VALID
VALUES
DEFAULT
VALUES
255,20,47
Red
SCOPE
User preference.
CM_color_of_common
DESCRIPTION
Specifies the default color to represent common components in the rich client
interface. Colors must be specified in RGB format. Red, green, and blue can be
combined in various proportions to obtain any color in the visible spectrum. Levels
of R, G, and B can each range from 0 to 100 percent of full intensity. Each color level
is represented by the range of decimal numbers from 0 to 255. The total number of
available colors is 256 x 256 x 256, or 16,777,216 possible colors.
VALID
VALUES
DEFAULT
VALUES
135,135,135
Grey
SCOPE
User preference.

Change Viewer preferences
CM_color_of_moved
DESCRIPTION
Specifies the default color to represent BOM moves in the rich client interface.
VALID
VALUES
DEFAULT
VALUES
122,183,122
Green
SCOPE
User preference.
CM_color_of_notechange
DESCRIPTION
Specifies the default color to represent BOM note changes in the rich client interface.
VALID
VALUES
DEFAULT
VALUES
128,0,128
Purple
SCOPE
User preference.

CM_color_of_quantity_change
DESCRIPTION
Specifies the default color to represent BOM quantity changes in the rich client
VALID
VALUES
DEFAULT
VALUES
255,118,0
Orange
SCOPE
User preference.
CM_color_of_reshaped
DESCRIPTION
Specifies the default color to represent BOM reshapes in the rich client interface.
VALID
VALUES
DEFAULT
VALUES
153,204,204
Turquoise
SCOPE
User preference.

CM_color_of_variantchange
DESCRIPTION
Specifies the default color to represent BOM variant changes in the rich client
VALID
VALUES
DEFAULT
VALUES
100,255,50
Sea green
SCOPE
User preference.
CM_initial_position_of_sliders
DESCRIPTION
Specifies the initial position of all control sliders in the Graphical History dialog box.
If set to 100, only the affected assembly is displayed. If set to 0, only the problem
assembly appears. Any number in between initially displays both the added and
cancelled parts.
VALID
VALUES
DEFAULT
VALUES
100
Initial slider position displays only the affected assembly.
SCOPE
User preference.
CM_progression_tree_relation
DESCRIPTION
Determines which of two possible relationships to use for the revisions in the
Progression tree.

VALID
VALUES
TC_based_on
Displays the problem/solution relationship where the selected revision is the solution
revision. The problem revision is shown as a parent revision. This relationship can
only be displayed in the Progression tree if the selected revision is part of a change
process.
Use this setting if your site is not using change management for BOM tracking.
EC_affected_to_problem_relation
Displays the based on relationship where the revision upon which the selected
revision was based is shown as the parent revision. This relationship is not
dependent on the selected revision being part of a change process.
Use this setting if your site is using change management for BOM tracking.
DEFAULT
VALUES
EC_affected_to_problem_relation
SCOPE
Site preference.
CM_show_common_parts
DESCRIPTION
Specifies whether or not common parts display during the initial loading of graphical
compare in the rich client interface.
VALID
VALUES
TRUE Common parts are initially displayed when a graphical compare is
loaded.
FALSE Common parts are not initially displayed when a graphical compare is
loaded.
DEFAULT
VALUES
FALSE
SCOPE
User preference.
ECM_affected_item_relations
DESCRIPTION
Sets the list of relations of the affected items of an engineering change. Workflow
handlers attach the objects under the relations as targets of the engineering change
process. Teamcenter uses this reference to add a release status to the process targets.

The setting of this preference affects the behavior of the ECM_is_affected_rev

ITK call.
For more information, see the Server Customization Programmer’s Guide.
VALID
VALUES
relation.
DEFAULT
VALUES
EC_affected_item_rel
EC_solution_item_rel
SCOPE
Site preference.
ECM_bomchange_formtype
DESCRIPTION
Sets the form type to be used for customizing BOMChange attributes.
VALID
VALUES
Accepts one or more strings as values; each string must be a valid Teamcenter form
type.
DEFAULT
VALUES
BomChange Form
SCOPE
Site preference.
ECM_bomchange_tooltip_properties
DESCRIPTION
Sets the BOMChange component properties displayed in the Genealogy WatchBox.
Item is the base component for property extraction. It is possible to derive a value
by traversing the properties starting from the item tag. For example, to display
a unit of measure for the item, enter:
UoM=uom_tag.symbol
VALID
VALUES
Accepts one or more strings as values; each string is a paring of the desired display
name and a valid Teamcenter component property.
DEFAULT
VALUES
Item ID=item_id
Item Owner=owning_user
Item Creation Date=creation_date
SCOPE
Site preference.

ECM_change_id_modifiable
DESCRIPTION
Allows you to modify the change id and the revision id values that are assigned
by the system.
VALID
VALUES
True
False
DEFAULT
VALUES
False
SCOPE
Site preference.
ECM_change_name_is_mandatory
DESCRIPTION
Determines whether the Change Name box in the Create/Revise Screen dialog box
displays in the Base Attributes tab as a mandatory field, or in the More Attributes
tab as an optional field.
VALID
VALUES
TRUE The Change Name box appears in the Base Attributes tab of the
Create/Revise Screen dialog box as a mandatory field.
FALSE The Change Name box appears in the More Attributes tab of the
Create/Revise Screen dialog box as an optional field.
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
ECM_delivered_engine_status
DESCRIPTION
Sets the status used for delivered engineering changes. BOM changes are considered
delivered engineering changes when the affected revision is assigned a delivered
release status. The genealogy functionality uses this setting to distinguish between
a normal change and a delivered change.
VALID
VALUES
Delivered Assigns a delivered status to the engineering change.
DEFAULT
VALUES
Delivered

SCOPE
User preference.
ECM_form_relation
DESCRIPTION
Sets the relation by which engineering change forms are attached to the engineering
change.
VALID
VALUES
Accepts one or more strings as values; must be a valid Teamcenter relation.
DEFAULT
VALUES
IMAN_specification
SCOPE
Site preference.
ECM_genealogy_expansion_rule
DESCRIPTION
Sets the expansion rule for the genealogy display.
VALID
VALUES
NEW Supersedures already displayed are ignored.
ALL All supersedures are displayed, irrespective of whether they have already
been displayed or not.
DEFAULT
VALUES
ALL
SCOPE
Site preference.
ECM_note_types_to_track
DESCRIPTION
Specifies which note types can be tracked for a particular change type. If an entry is
not made for a particular change type, the ability to track changes via occurrence
notes is disabled.
VALID
VALUES
Accepts multiple strings as values; each string must contain a valid Teamcenter
change type, and one or more valid Teamcenter note types using the following syntax:
ECM_note_types_to_track=
Change-Type1:Note-Type1,Note-Type2

Note
Do not set this preference with a value of UG ALTREP note type.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ECM_notehistory_extra_columns
DESCRIPTION
Determines which fields of the BOM change form are included in the Note Change
History dialog box. This dialog box is opened from the Structure Manager
application and tracks note changes for a particular component of an assembly.
The BOM change form is defined by the ECM_bomchange_formtype preference.
VALID
VALUES
Accepts multiple strings as values; each string must contain a persistent property
of the BOM change form, using the following syntax:
ECM_notehistory_extra_columns=
Form-Field1
Form-Field2
DEFAULT
VALUES
None.
SCOPE
Site preference.
ECM_prev_structure_relation
DESCRIPTION
Sets the relation that defines the problem item as identified in the engineering
change. This reference is used to create genealogy. Only one relation can be specified.
VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter relation.
DEFAULT
VALUES
EC_problem_item_rel
SCOPE
Site preference.

ECM_prev_structure_relation_name
DESCRIPTION
Sets the relation that defines the problem item as identified in the engineering
change. This relation is used to create genealogy. Only one relation can be specified.
VALID
VALUES
DEFAULT
VALUES
problem_items
SCOPE
Site preference
ECM_property_access
DESCRIPTION
Specifies the access (such as read, write) given to user for engineering change
properties in EC Viewer.
VALID
VALUES
Accepts one or more strings as values.
DEFAULT
VALUES
r-
r-
r-
r-
r-
r-
r-
SCOPE
Site preference.
ECM_property_display_names
DESCRIPTION
Sets the list of property labels displayed in by the viewer table of an engineering
change.
VALID
VALUES
DEFAULT
VALUES
Change #
Change Type
Owner

Date Created
Last Modified By
Name
Description
SCOPE
Site preference.
ECM_property_names
DESCRIPTION
Sets the list of properties displayed by the viewer table of an engineering change.
VALID
VALUES
DEFAULT
VALUES
EngChange.item_id
EngChange Revision Master.ec_type
EngChange Revision.owning_user
EngChange Revision.creation_date
EngChange Revision.last_mod_user
EngChange Revision.object_name
EngChange Revision.object_desc
SCOPE
Site preference.
ECM_pseudofolder_names
DESCRIPTION
Sets the list of relations for the selected engineering change object.
Change Viewer displays relations as pseudofolders. The names of the pseudofolders
can be configured. You can create additional pseudofolders by first creating a relation
type in Business Modeler IDE. The semantics for the relation types are defined by
the other Change Viewer preferences that follow.
Proper display names for the pseudofolder properties can be added by modifying
the property_names.uid file.
Note
Pseudofolder names must also be added to the
ItemRevision_DefaultChildProperties class in order to be displayed
in Teamcenter.
VALID
VALUES
Accepts one or more strings as values; each string must be a paring of a defined
pseudofolder name and a valid Teamcenter relation. For example:
affected_items/EC_affected_item_rel

DEFAULT
VALUES
affected_items/EC_affected_item_rel
solution_items/EC_solution_item_rel
problem_items/EC_problem_item_rel
reference_items/EC_reference_item_rel
addressed_by/EC_addressed_by_rel
SCOPE
Site preference.
ECM_set_genealogy
DESCRIPTION
Determines the display of Change Management BOM-tracking-related interface
components. Also determines whether BOMChange records are created upon
saving an affected assembly in Structure Manager.
VALID
VALUES
On BOMChange records are created upon saving an affected assembly in
Structure Manager and the supersedure definition dialog box appears. The
following components display:
• Supersedure tab in Structure Manager
• Open Supersedure button in Structure Manager
• BOM Changes tab in Change Viewer
• Open Structure Manager button in Change Viewer
Off BOMChange records are not created upon saving an affected assembly
in Structure Manager and the supersedure definition dialog box does not
display. The components listed above do not display.
DEFAULT
VALUES
On
SCOPE
Site preference.
ECM_supercedure_tooltip_properties
DESCRIPTION
Sets the supersedure component properties displayed in the Genealogy WatchBox.
Supersedure is the base component for property extraction. It is possible to derive
a value by traversing the properties starting from the supersedure tag.

Note
parent_rev is a special token supported for deriving an ItemRevision tag of
a BVR tag. Similarly, current_effectivity is a special token to display the
effectivity information of an ItemRevision tag.
VALID
VALUES
Accepts one or more strings as values; each string is a paring of the desired display
name and a valid Teamcenter component property.
DEFAULT
VALUES
Affected Assembly=affected_bvr.object_name
Affected IR Effectivity=affected_bvr.parent_rev.current_effectivity
Problem Assembly=problem_bvr.object_name
EC Owner=ec_rev_tag.owning_user
SCOPE
Site preference.
ECM_track_variant_condition_changes
DESCRIPTION
Defines the change types for which variant changes can be tracked.
VALID
VALUES
change type using the following syntax:
ECM_track_variant_condition_changes=
Change-Type1
Change-Type2
DEFAULT
VALUES
None.
SCOPE
Site preference.
ECM_varianthistory_extra_columns
DESCRIPTION
Determines which fields of the BOM change form are included in the Variant Change
Details dialog box. This dialog box is opened from the Change Viewer application
and displays the Problem side and Affected side variant conditions for the selected
occurrence.
The BOM change form is defined by the ECM_bomchange_formtype preference.
VALID
VALUES

ECM_varianthistory_extra_columns=
Form-Field1
Form-Field2
DEFAULT
VALUES
None.
SCOPE
Site preference.
Enable_Create_Classic_Change
DESCRIPTION
Shows or hides the File→New→Classic Change menu command that allows creation
of a new EngChange type object in both the rich client and thin client.
VALID
VALUES
True Shows the File→New→Classic Change menu command.
False Hides the File→New→Classic Change menu command.
DEFAULT
VALUES
False for Foundation installations and upgrades; True for GM Overlay installations
and upgrades.
SCOPE
Site preference.
NOTES
Set this preference to True to allow the creation of classic change objects.
RESTRICTIONS
None.
Enable_Show_Classic_Change
DESCRIPTION
Shows or hides references to Change Viewer Classic change objects, saved searches,
reports, property finder formatters, preferences, LOVs, item and item revision types,
and relations. It also controls whether the Send To menu command shows CM
Viewer/Change Viewer.
VALID
VALUES
True Shows references to Change Viewer Classic change objects.
False Hides references to Change Viewer Classic change objects.
DEFAULT
VALUES
False for Foundation installations; True for Foundation upgrades, GM Overlay
installations, and GM Overlay upgrades.
SCOPE
Site preference.

NOTES
Use this preference to help phase out usage of Change Viewer Classic.
RESTRICTIONS
None.
EngChange Revision_DefaultChildProperties
DESCRIPTION
Requires the following relation names. The final setting (release_status_list) is
required to display the current status in My Teamcenter.
VALID
VALUES
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
affected_items
solution_items
problem_items
reference_items
addressed_by
release_status_list
DEFAULT
VALUES
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
affected_items
solution_items
problem_items
reference_items
addressed_by
release_status_list
SCOPE
Site preference.
Supercedure_DefaultChildProperties
DESCRIPTION
Requires the following relation names.
VALID
VALUES
Adds
Cancels

DEFAULT
VALUES
Adds
Cancels
SCOPE
Site preference.
TAE_CM_change_name_is_mandatory
DESCRIPTION
Determines whether inserting a value into the Change Name field is mandatory.
VALID
VALUES
TRUE User must type a value into the Change Name field before the
system will create or revise an engineering change object.
FALSE User need not type a value into the Change Name field before
the system will create or revise an engineering change object.
DEFAULT
VALUES
None.
SCOPE
User preference.
TAE_CM_show_task_viewer
DESCRIPTION
Determines whether the Task Viewer displays in all panels of the Change Viewer
application.
VALID
VALUES
TRUE The Task Viewer displays in all panels of the Change Viewer
application.
FALSE The Task Viewer does not display in the Change Viewer
application.
DEFAULT
VALUES
None.
SCOPE
User preference.
TC_bomchange_export
DESCRIPTION
Determines whether BOMChange objects are included in the export of engineering
change objects.

VALID
VALUES
TRUE BOMChange objects are included in the export of engineering change
objects.
FALSE BOMChange objects are not included in the export of engineering
change objects.
DEFAULT
VALUES
TRUE
SCOPE
All.
TC_supercedure_export
DESCRIPTION
Determines whether supersedure objects are included in the export of engineering
change objects.
VALID
VALUES
TRUE Supersedure objects are included in the export of engineering change
objects.
FALSE Supersedure objects are not included in the export of engineering change
objects.
DEFAULT
VALUES
TRUE
SCOPE
All.

Chapter
13 Change Manager preferences
ChangeItemRevision_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . . 13-1
ChangeNotice.CREATERENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
ChangeNoticeCreate.CREATE_REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . 13-2
ChangeNoticeRevision_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . 13-2
ChangeNoticeRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
ChangeNoticeRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
ChangeNoticeRevision.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . 13-3
ChangeNoticeRevisionSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . . 13-4
ChangeRequest.CREATERENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
ChangeRequestCreate.CREATE_REGISTEREDTO . . . . . . . . . . . . . . . . . . . . 13-4
ChangeRequestRevision_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . 13-4
ChangeRequestRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
ChangeRequestRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
ChangeRequestRevision.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . 13-6
ChangeRequestRevisionSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . 13-6
CM_bomchange_formtype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
CM_change_derivations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
CM_ChangeRequestRevision_Relations_To_Propagate . . . . . . . . . . . . . . . . . . 13-7
CM_Cm0DevRqstRevision_Relations_To_Propagate . . . . . . . . . . . . . . . . . . . 13-7
CM_Effectivity_DefaultColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
CM_form_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
CM_impacted_item_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
CM_note_types_to_track . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
CM_notehistory_extra_columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
CM_ProblemReportRevision_Relations_To_Propagate . . . . . . . . . . . . . . . . . 13-10
CM_pureaddcancel_tooltip_properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
CM_relation_creation_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
CM_solution_items_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
CM_supersedure_tooltip_properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
CM_track_variant_condition_changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
CM_varianthistory_extra_columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
CM_work_breakdown_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
CMHasImpactedItem_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
CMHasProblemItem_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
CMHasSolutionItem_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
CMHasWorkBreakdown_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
CMImplements_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
CMReferences_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
Cm0DevRqst.CREATERENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
Cm0DevRqstCreate.CREATE_REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . 13-16
Cm0DevRqstRevision_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . 13-16
Cm0DevRqstRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
Cm0DevRqstRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17

Cm0DevRqstRevision.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . 13-17
Cm0DevRqstRevisionSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . 13-17
ProblemReport.CREATERENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
ProblemReportCreate.CREATE_REGISTEREDTO . . . . . . . . . . . . . . . . . . . 13-18
ProblemReportRevision_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . 13-18
ProblemReportRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
ProblemReportRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
ProblemReportRevision.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . 13-19
ProblemReportRevisionSummary.SUMMARY_REGISTEREDTO . . . . . . . . . 13-20
WEB_Enable_Create_Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20

Chapter
13 Change Manager preferences
Change Manager helps 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 more information about Change Manager, see the Change Manager Guide.
Use Change Manager preferences to modify Change Manager behavior.
ChangeItemRevision_DefaultChildProperties
DESCRIPTION
Specifies the list of properties that can be displayed as children of a
ChangeItemRevision node.
VALID
VALUES
Accepts one or more strings as values; each string must be a property of the
ChangeItemRevision object.
DEFAULT
VALUES
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
release_status_list
TC_Attaches
CMImplements
CMImplementedBy
CMHasImpactedItem
CMHasProblemItem
CMReferences
CMHasSolutionItem
CMHasWorkBreakdown
SCOPE
Site preference.
ChangeNotice.CREATERENDERING
DESCRIPTION
Registers the create style sheet for change notice objects.

Chapter 13 Change Manager preferences
VALID
VALUES
DEFAULT
VALUES
ChangeNoticeCreate
SCOPE
Site preference.
ChangeNoticeCreate.CREATE_REGISTEREDTO
DESCRIPTION
Specifies the types to which the ChangeNoticeCreate style sheet can be applied.
VALID
VALUES
Accepts one or more strings as values; each must be a valid type name.
DEFAULT
VALUES
ChangeNotice
SCOPE
Site preference.
ChangeNoticeRevision_DefaultChildProperties
DESCRIPTION
ChangeNoticeRevision node.
VALID
VALUES
ChangeNoticeRevision object.
DEFAULT
VALUES
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
release_status_list
TC_Attaches
CMImplements
CMHasImpactedItem
CMHasProblemItem
CMReferences
CMHasSolutionItem
CMHasWorkBreakdown

Change Manager preferences
SCOPE
Site preference.
ChangeNoticeRevision.REGISTEREDTO
DESCRIPTION
Specifies the types to which the ChangeNoticeRevisionProperty style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ChangeNoticeRevision
SCOPE
Site preference.
ChangeNoticeRevision.RENDERING
DESCRIPTION
Registers the properties style sheet for change notice revision objects.
VALID
VALUES
DEFAULT
VALUES
ChangeNoticeRevisionProperty
SCOPE
Site preference.
ChangeNoticeRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for change notice revision objects. The summary
style sheet is used for the Summary tab.
VALID
VALUES
DEFAULT
VALUES
ChangeNoticeRevisionSummary
SCOPE
Site preference.

ChangeNoticeRevisionSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Specifies the types to which the ChangeNoticeRevisionSummary style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ChangeNoticeRevision
SCOPE
Site preference.
ChangeRequest.CREATERENDERING
DESCRIPTION
Registers the create style sheet for change request objects.
VALID
VALUES
DEFAULT
VALUES
ChangeRequestCreate
SCOPE
Site preference.
ChangeRequestCreate.CREATE_REGISTEREDTO
DESCRIPTION
Specifies the types to which the ChangeRequestCreate style sheet can be applied.
VALID
VALUES
DEFAULT
VALUES
ChangeRequest
SCOPE
Site preference.
ChangeRequestRevision_DefaultChildProperties
DESCRIPTION
ChangeRequestRevision node.

VALID
VALUES
ChangeRequestRevision object.
DEFAULT
VALUES
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
release_status_list
TC_Attaches
CMImplements
CMImplementedBy
CMHasImpactedItem
CMHasProblemItem
CMReferences
CMHasWorkBreakdown
SCOPE
Site preference.
ChangeRequestRevision.REGISTEREDTO
DESCRIPTION
Specifies the types to which the ChangeRequestRevisionProperty style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ChangeRequestRevision
SCOPE
Site preference.
ChangeRequestRevision.RENDERING
DESCRIPTION
Registers the properties style sheet for change request revision objects.
VALID
VALUES
DEFAULT
VALUES
ChangeRequestRevisionProperty

SCOPE
Site preference.
ChangeRequestRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for change request revision objects. The summary
VALID
VALUES
DEFAULT
VALUES
ChangeRequestRevisionSummary
SCOPE
Site preference.
ChangeRequestRevisionSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Specifies the types to which the ChangeRequestRevisionSummary style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ChangeRequestRevision
SCOPE
Site preference.
CM_bomchange_formtype
DESCRIPTION
Sets the form type to be used for customizing BOMChange attributes.
VALID
VALUES
Accepts one or more strings as values; each string must be a valid Teamcenter form
type.
DEFAULT
VALUES
BomChange Form
SCOPE
Site preference.

CM_change_derivations
DESCRIPTION
Defines the type of change to create from a given source type during the derive
change process.
VALID
VALUES
source-type/derived-type
source-type is the type of change from which to derive the change; derived-type is
the type of change to be created.
DEFAULT
VALUES
ProblemReport/ChangeRequest
ChangeRequest/ChangeNotice
SCOPE
Site preference.
RESTRICTIONS
None.
CM_ChangeRequestRevision_Relations_To_Propagate
DESCRIPTION
Specifies the list of relations to be propagated when deriving a change from a change
request revision.
VALID
VALUES
One or more strings representing a valid Change Manager relation.
DEFAULT
VALUES
CMHasImpactedItem
CMHasProblemItem
CMReferences
SCOPE
Site preference.
RESTRICTIONS
None.
CM_Cm0DevRqstRevision_Relations_To_Propagate
DESCRIPTION
Specifies the list of relations to be propagated when deriving a change from a
deviation request revision.
VALID
VALUES

DEFAULT
VALUES
CMHasImpactedItem
CMHasProblemItem
CMReferences
SCOPE
Site preference.
RESTRICTIONS
None.
CM_Effectivity_DefaultColumns
DESCRIPTION
Controls the columns that can be displayed for Effectivity objects.
VALID
VALUES
Effectivity object.
DEFAULT
VALUES
release_status
effectivity_id
range_text
end_item
effectivity_protection
SCOPE
Site preference.
CM_form_relation
DESCRIPTION
Specifies the relation to use between change forms and change items.
VALID
VALUES
Any valid Teamcenter relation.
DEFAULT
VALUES
IMAN_reference
SCOPE
Site preference.

CM_impacted_item_relation
DESCRIPTION
Defines the list of relations that contain the target of a change process where
workflow handlers attach the objects.
VALID
VALUES
Change Manager relations that contain the target object of a change process. It can
be any of the following relations:
• CMHasImpactedItem
• CMHasSolutionItem
• CMImplements
• CMReferences
• CMHasProblemItem
• CMHasWorkBreakdown
DEFAULT
VALUES
CMHasImpactedItem
SCOPE
Site preference.
CM_note_types_to_track
DESCRIPTION
Specifies which product structure note types can be tracked for a particular change
type.
VALID
VALUES
change type, and one or more valid Teamcenter note types using the following syntax:
CM_note_types_to_track=
For example, a valid value is:

ChangeNotice:UG Geometry,UG NAME
DEFAULT
VALUES
None.
SCOPE
Site preference.

CM_notehistory_extra_columns
DESCRIPTION
Determines which fields of the BOM change form are included in the Note Change
History dialog box. This dialog box is opened from the Structure Manager application
and tracks note changes for a particular component of an assembly.
VALID
VALUES
CM_notehistory_extra_columns=
Form-Field1
Form-Field2
DEFAULT
VALUES
None.
SCOPE
Site preference.
CM_ProblemReportRevision_Relations_To_Propagate
DESCRIPTION
Specifies the list of relations to be propagated when deriving a change from a
problem report revision.
VALID
VALUES
DEFAULT
VALUES
CMHasProblemItem
CMReferences
SCOPE
Site preference.
RESTRICTIONS
None.
CM_pureaddcancel_tooltip_properties
DESCRIPTION
Sets the pure add and cancel properties displayed in the genealogy watch box.
VALID
VALUES
Accepts one or more strings as values in the form of bomedit-object.property-name.
The bomedit-object string is the internal name of BOM edit object. The property-name
string is a valid Teamcenter internal property name. Both internal names can be
retrieved from the Business Modeler IDE.

DEFAULT
VALUES
CMBvrTag.object_name
CMProblemBvr.object_name
CMChangeRevTag.owning_user
CMOccurenceTag.seq_no
SCOPE
Site preference.
CM_relation_creation_flag
DESCRIPTION
Determines if a newly-created in-context change item is automatically related to
the latest item revision or a user-selected revision. You can set different values
for change items and nonchange items.
VALID
VALUES
ChangeItems=1 Automatically creates a relation between the new change
item and the latest revision of the selected existing change
item.
ChangeItems=0 Forces the user to select the existing change item revision
to be related to the new change item.
NonChangeItems=1 Automatically creates a relation between the new change
item and the latest revision of the selected existing
nonchange item.
NonChangeItems=0 Forces the user to select the existing nonchange item
revision to be related to the new change item.
DEFAULT
VALUES
ChangeItems=1
NonChangeItems=1
SCOPE
Site preference.
CM_solution_items_relation
DESCRIPTION
Defines the relation containing the objects which are identified as solution objects
by the change process.
VALID
VALUES
Change Manager relation that identifies the solution object. It can be any of the
following relations:
• CMImplements

• CMReferences
DEFAULT
VALUES
CMHasSolutionItem
SCOPE
Site preference.
CM_supersedure_tooltip_properties
DESCRIPTION
Sets the supersedure component properties displayed in the genealogy watch box.
VALID
VALUES
Accepts one or more strings as values in the form of bvrrev-object.property-name.
The bvrrev-object string is the internal name of BOM view revision object. The
property-name string is a valid Teamcenter internal property name. Both internal
names can be retrieved from the Business Modeler IDE.
DEFAULT
VALUES
CMImpactedBvr.object_name
SCOPE
Site preference.
CM_track_variant_condition_changes
DESCRIPTION
Defines the change types for which variant BOM changes can be tracked.
VALID
VALUES
change type using the following syntax:
CM_track_variant_condition_changes=
Change-Type1
Change-Type2
DEFAULT
VALUES
None.
SCOPE
Site preference.

CM_varianthistory_extra_columns
DESCRIPTION
Determines which fields of the BOM change form are included in the Variant Change
History dialog box.
VALID
VALUES
CM_varianthistory_extra_columns=
Form-Field1
Form-Field2
DEFAULT
VALUES
None.
SCOPE
Site preference.
CM_work_breakdown_relation
DESCRIPTION
Defines the relation containing the work breakdown schedules of the change process.
VALID
VALUES
Change Manager relation that contains the work breakdown schedules of the change
process. It can be any of the following relations:
• CMImplements
• CMReferences
DEFAULT
VALUES
CMHasWorkBreakdown
SCOPE
Site preference.
CMHasImpactedItem_relation_primary
DESCRIPTION
Specifies the valid primary object types for the CMHasImpactedItem relation.

VALID
VALUES
Accepts one or more strings as values; each string must be a primary Teamcenter
object.
DEFAULT
VALUES
Item
ItemRevision
SCOPE
Site preference.
CMHasProblemItem_relation_primary
DESCRIPTION
Specifies the valid primary object types for the CMHasProblemItem relation.
VALID
VALUES
object.
DEFAULT
VALUES
Item
ItemRevision
SCOPE
Site preference.
CMHasSolutionItem_relation_primary
DESCRIPTION
Specifies the valid primary object types for the CMHasSolutionItem relation.
VALID
VALUES
object.
DEFAULT
VALUES
Item
ItemRevision
SCOPE
Site preference.
CMHasWorkBreakdown_relation_primary
DESCRIPTION
Specifies the valid primary object types for the CMHasWorkBreakdown relation.

VALID
VALUES
object.
DEFAULT
VALUES
Item
ItemRevision
SCOPE
Site preference.
CMImplements_relation_primary
DESCRIPTION
Specifies the valid primary object types for the CMImplements relation.
VALID
VALUES
object.
DEFAULT
VALUES
Item
ItemRevision
SCOPE
Site preference.
CMReferences_relation_primary
DESCRIPTION
Specifies the valid primary object types for the CMReferences relation.
VALID
VALUES
object.
DEFAULT
VALUES
Item
ItemRevision
SCOPE
Site preference.
Cm0DevRqst.CREATERENDERING
DESCRIPTION
Registers the create style sheet for deviation request objects.

VALID
VALUES
DEFAULT
VALUES
Cm0DevRqstCreate
SCOPE
Site preference.
Cm0DevRqstCreate.CREATE_REGISTEREDTO
DESCRIPTION
Specifies the types to which the Cm0DevRqstCreate style sheet can be applied.
VALID
VALUES
DEFAULT
VALUES
Cm0DevRqst
SCOPE
Site preference.
Cm0DevRqstRevision_DefaultChildProperties
DESCRIPTION
Cm0DevRqstRevision node.
VALID
VALUES
Cm0DevRqstRevision object.
DEFAULT
VALUES
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
release_status_list
TC_Attaches
CMImplements
CMImplementedBy
CMHasProblemItem
CMReferences
CMHasWorkBreakdown
SCOPE
Site preference.

Cm0DevRqstRevision.REGISTEREDTO
DESCRIPTION
Specifies the types to which the Cm0DevRqstRevision style sheet can be applied.
VALID
VALUES
DEFAULT
VALUES
Cm0DevRqstRevision
SCOPE
Site preference.
Cm0DevRqstRevision.RENDERING
DESCRIPTION
Registers the properties style sheet for deviation request revision objects.
VALID
VALUES
DEFAULT
VALUES
Cm0DevRqstRevisionProperty
SCOPE
Site preference.
Cm0DevRqstRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for deviation request revision objects. The
summary style sheet is used for the Summary tab.
VALID
VALUES
DEFAULT
VALUES
Cm0DevRqstRevisionSummary
SCOPE
Site preference.
Cm0DevRqstRevisionSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Specifies the types to which the Cm0DevRqstRevisionSummary style sheet can
be applied.

VALID
VALUES
DEFAULT
VALUES
Cm0DevRqstRevision
SCOPE
Site preference.
ProblemReport.CREATERENDERING
DESCRIPTION
Registers the create style sheet for problem report objects.
VALID
VALUES
DEFAULT
VALUES
ProblemReportCreate
SCOPE
Site preference.
ProblemReportCreate.CREATE_REGISTEREDTO
DESCRIPTION
Specifies the types to which the ProblemReportCreate style sheet can be applied.
VALID
VALUES
DEFAULT
VALUES
ProblemReport
SCOPE
Site preference.
ProblemReportRevision_DefaultChildProperties
DESCRIPTION
ProblemReportRevision node.
VALID
VALUES
ProblemReportRevision object.
DEFAULT
VALUES

IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
release_status_list
TC_Attaches
CMImplementedBy
CMHasProblemItem
CMReferences
SCOPE
Site preference.
ProblemReportRevision.REGISTEREDTO
DESCRIPTION
Specifies the types to which the ProblemReportRevision style sheet can be
applied.
VALID
VALUES
DEFAULT
VALUES
ProblemReportRevision
SCOPE
Site preference.
ProblemReportRevision.RENDERING
DESCRIPTION
Registers the properties style sheet for problem report revision objects.
VALID
VALUES
DEFAULT
VALUES
ProblemReportRevisionProperty
SCOPE
Site preference.
ProblemReportRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for problem report revision objects. The summary

VALID
VALUES
DEFAULT
VALUES
ProblemReportRevisionSummary
SCOPE
Site preference.
ProblemReportRevisionSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Specifies the types to which the ProblemReportRevisionSummary style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ProblemReportRevision
SCOPE
Site preference.
WEB_Enable_Create_Change
DESCRIPTION
Determines whether the File→Change→Create, File→Change→Context Create,
and File→Change→Derived Change menu commands are displayed in the thin
client.
VALID
VALUES
true Displays the menu commands.
false Hides the menu commands.
DEFAULT
VALUES
false
SCOPE
Site preference.

Chapter
14 Issue Manager preferences
ISSUE_issuelist_page_size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
ISSUE_preview_image_name_separator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
ISSUE_preview_image_size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
ISSUE_preview_tooltip_properties_after_fix . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
ISSUE_preview_tooltip_properties_before_fix . . . . . . . . . . . . . . . . . . . . . . . . 14-2
ISSUE_review_issue_menu_items_at_workflow_task . . . . . . . . . . . . . . . . . . . 14-3

Chapter
14 Issue Manager preferences
Issue Manager tracks problems, or issues, with a product by letting you manage the
review, approval, and implementation of the issue.
Use Issue Manager preferences to modify Issue Manager behavior.
For more information about Issue Manager, see the Issue Manager Guide.
ISSUE_issuelist_page_size
DESCRIPTION
Specifies the number of issues displayed per page in an issue list in the Image Home
view of Issue Manager.
VALID
VALUES
integer The larger the number, the more issues displayed per page.
DEFAULT
VALUES
15
SCOPE
Site preference.
ISSUE_preview_image_name_separator
DESCRIPTION
Specifies the delimiter used in the title of an image preview in the Image Preview
view of Issue Manager. The delimiter appears between the issue report revision
and image name.
VALID
VALUES
string Accepts a string.
DEFAULT
VALUES
:
SCOPE
Site preference.

Chapter 14 Issue Manager preferences
ISSUE_preview_image_size
DESCRIPTION
Defines the size in pixels for the image preview in the Image Preview view in Issue
Manager. The two values are, respectively, the horizontal and vertical sizes.
VALID
VALUES
integer Accepts two integers.
DEFAULT
VALUES
250
250
SCOPE
Site preference.
ISSUE_preview_tooltip_properties_after_fix
DESCRIPTION
Specifies the properties to be displayed in the tool tip for an image preview displayed
in the Issue Preview view of Issue Manager.
VALID
VALUES
string Accepts one or more strings as values; each string must be a property name
of the issue report revision object.
DEFAULT
VALUES
CMClosureComments
CMDispositionComments
SCOPE
Site preference.
ISSUE_preview_tooltip_properties_before_fix
DESCRIPTION
Specifies the properties to be displayed in the tool tip for an image preview displayed
in the Issue Preview view of Issue Manager.
VALID
VALUES
Array of strings Accepts one or more strings as values; each string must be a
property name of the issue report revision object.
DEFAULT
VALUES
object_desc (short description of issue)
design_review_gate
issue_category
due_date

Issue Manager preferences
SCOPE
Site preference.
ISSUE_review_issue_menu_items_at_workflow_task
DESCRIPTION
Defines the options available for the review issue operation for a specified issue
management workflow task. The valid format is a task name followed by a list of
review options separated by a semicolon.
VALID
VALUES
Array of strings Accepts one or more strings as values, in the format of a
task name followed by a list of review options separated by a
semicolon.
DEFAULT
VALUES
Review Issue;Defer;Reject;ApproveIssue;
Assign Issue and Fix Issue;SubmitFix;
Final Review;ApproveFix;
SCOPE
Site preference.
RESTRICTIONS
Each line starts with workflow task name, followed by the menu commands for the
Review Issue operation for this workflow task. The workflow task name must
match the issue management workflow process template in use. The default values
match the Issue lifecycle workflow process template provided with Issue Manager.

Chapter
15 Reports, requirements, and

scheduling preferences
Requirements Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

REQ_spec_template_folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
REQ_object_template_folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Schedule Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

cost_default_currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
DefaultActualToSystemDate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Default_Base_Calendar_Preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
scheduling_graph_dataSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
scheduling_graph_dataSource_filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
scheduling_graph_date_format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
scheduling_graph_date_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
scheduling_graph_domain_label_vertical . . . . . . . . . . . . . . . . . . . . . . . . 15-5
scheduling_graph_font_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
scheduling_graph_font_size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
scheduling_graph_font_style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
scheduling_graph_histogram_single_color . . . . . . . . . . . . . . . . . . . . . . . . 15-6
scheduling_graph_reference_calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
scheduling_graph_task_legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
scheduling_graph_view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
SiteTimeZone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
SM_CriticalPath_Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
SM_EVM_Calc_Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
SM_EVM_Calc_Preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
SM_EVM_Export_Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
SM_EVM_Work_Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
SM_SCHEDULING_ENGINE_DATE . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
SM_TIMESHEET_APPROVE_WORKFLOW . . . . . . . . . . . . . . . . . . . . . 15-10
SM_TIMESHEET_REVISE_WORKFLOW . . . . . . . . . . . . . . . . . . . . . . 15-11
SM_View_CriticalPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-11
SM_WBS_FORMAT_PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
SM_WBS_INITIAL_PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
TC_RA_server_parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-13
Report Designer preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-13

Enable_ReportDesigner_Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-13

Chapter
15 Reports, requirements, and

scheduling preferences
PLM XML reports can be formatted using style sheets. Requirements extends
customer involvement to all phases of the product development process. Schedules
allow your users to plan and track activities in Teamcenter. The following
preferences control report, requirements, and scheduling behavior.
Requirements Manager preferences

With Requirements Manager, customers can actively influence the product design
from requirements development and association to product testing and acceptance.
Requirements Manager simplifies requirement development and access and
substantially reduces the learning curve.
Users work with requirement specification structures that contain requirement and
paragraph objects. Requirement content is developed with Microsoft Office Word and
Excel, tools that are readily available in most organizations.
Use Requirements Manager preferences to modify the behavior of this application.
REQ_spec_template_folder
DESCRIPTION
Defines the path for the folder in which all specification templates are stored.
VALID
VALUES
Accepts a single string as a value. The string must be a valid file location.
DEFAULT
VALUES
Home\RequirementManagementTemplates\ExportTemplates\
SpecificationTemplates
SCOPE
Site preference.
REQ_object_template_folder
DESCRIPTION
Defines the path for the folder in which all object templates are stored.

Chapter 15 Reports, requirements, and scheduling preferences
VALID
VALUES
Accepts a single string as a value. The string must be a valid file location.
DEFAULT
VALUES
Home\RequirementManagementTemplates\ExportTemplates\
ObjectTemplates
SCOPE
Site preference.
Schedule Manager preferences

Schedule Manager provides coordinated, concurrent access to the schedule, allowing
multiple resources to update information at the same time. This is important when
several people are working on developing or maintaining their individual subsections
of the master schedule.
Use Schedule Manager preferences to modify the behavior of this application.
cost_default_currency
DESCRIPTION
Specifies the default currency to use for costs in the system. The value must be a
valid currency code based on the ISO-4217 standard. Set this preference to the
current value listed in the CostCurrency LOV. The default value is USD (United
States dollars). If you want to use EUR as your default currency, change the one
value in the CostCurrency LOV from USD to EUR. Then, specify EUR when using
the cost_default_currency preference.
Note
Siemens PLM Software recommends using only one currency in Teamcenter
because there is no support for currency conversion.
VALID
VALUES
Accepts one of the values listed in the CostCurrency LOV.
DEFAULT
VALUES
USD
SCOPE
Site preference.
DefaultActualToSystemDate
DESCRIPTION
Determines whether system date or scheduled date is used when initially setting
actual start date or actual end date, when the user marks a task as in progress or
complete, respectively.

Reports, requirements, and scheduling preferences
This preference is used with Schedule Manager.

VALID
VALUES
True system date is used as the default date set in actual start date or actual
end date.
False scheduled date is used as the default date set in actual start date or actual
end date.
DEFAULT
VALUES
False
SCOPE
All.
Default_Base_Calendar_Preference
DESCRIPTION
Determines the internal name of the default calendar when a schedule is created
in Schedule Manager.
VALID
VALUES
Standard
Night Shift
24 Hours
DEFAULT
VALUES
Standard
SCOPE
Site preference.
NOTES
Modify this preference when TCCalendar has multiple translations and users need
to query based on the known locale-independent name.
scheduling_graph_dataSource
DESCRIPTION
Used with Schedule Manager resource graphs. Defines the data sources for resource
graphs.
Warning
This preference must be set to TeamcenterDB in a production environment.
VALID
VALUES
randomSample The system uses a random sample generator as the data source
for resource graphs.

TeamcenterDB The system uses the Teamcenter database as the data source
for resource graphs.
DEFAULT
VALUES
TeamcenterDB
SCOPE
Site preference.
scheduling_graph_dataSource_filter
DESCRIPTION
Used with Schedule Manager resource graphs. Specifies the filtering method used
when creating resource graphs.
VALID
VALUES
none No filter is applied.
selection Users can select which schedules are used to create the
resource graph.
current The current schedule is used to create the resource graph.
DEFAULT
VALUES
none
SCOPE
Site preference.
scheduling_graph_date_format
DESCRIPTION
Used with Schedule Manager resource graphs. Determines the date and time
display in resource graphs.
VALID
VALUES
Accepts a single string as a value. The string can be any pattern that describes
date and time format.
DEFAULT
VALUES
EEE, MMM d
SCOPE
Site preference.
scheduling_graph_date_interval
DESCRIPTION
Used with Schedule Manager resource graphs. Determines the marked intervals on
the domain axis. Set this preference with any segmented time line value such as
day (default) or week, or with integer values such as 1 for a day or 7 for a week.

VALID
VALUES
Accepts multiple strings as values. Each string must be a segmented time line
value or positive integer. For example:
day
week
1440
10080
DEFAULT
VALUES
day
SCOPE
Site preference.
scheduling_graph_domain_label_vertical
DESCRIPTION
Used with Schedule Manager resource graphs. Determines whether domain labels
are vertical or horizontal.
VALID
VALUES
True Domain labels are vertical.
False Domain labels are horizontal.
DEFAULT
VALUES
True
SCOPE
Site preference.
scheduling_graph_font_name
DESCRIPTION
Used with Schedule Manager resource graphs. Determines the font displayed
in resource graphs.
VALID
VALUES
Accepts a single string as a value. The string must be a valid font type.
DEFAULT
VALUES
None.
SCOPE
Site preference.

scheduling_graph_font_size
DESCRIPTION
Used with Schedule Manager resource graphs. Determines the font size displayed
in resource graphs.
VALID
VALUES
Accepts a single string as a value. The string must be a positive integer, representing
a reasonable font size.
DEFAULT
VALUES
5
SCOPE
Site preference.
scheduling_graph_font_style
DESCRIPTION
Used with Schedule Manager resource graphs. Determines the font style displayed
in resource graphs.
VALID
VALUES
0 Normal font.
1 Bold font.
2 Italic font.
3 Bold and italic font.
DEFAULT
VALUES
0
SCOPE
Site preference.
scheduling_graph_histogram_single_color
DESCRIPTION
Used with Schedule Manager resource graphs. Determines whether single or
multiple colors bars are used in resource graphics.
VALID
VALUES
True A single color bar is used.
False Multiple color bars are used.
DEFAULT
VALUES
True

SCOPE
Site preference.
scheduling_graph_reference_calendar
DESCRIPTION
Specifies the calendar type to use for domain (x days) and range (y. availability/work
allocation) axis in the resource graph.
VALID
VALUES
resource_calendar_type Specifies the domain for the resource calendar.
system_calendar_type Specifies the domain for the system calendar.
DEFAULT
VALUES
resource_calendar_type
SCOPE
Site preference
scheduling_graph_task_legend
DESCRIPTION
Used with Schedule Manager resource graphs. Determines whether legends are
displayed for stacked bars.
Note
If this preference is set to display legends, tool tips do not include schedule
and load information.
VALID
VALUES
True Legends are displayed for stacked bars.
False Legends are not displayed for stacked bars.
DEFAULT
VALUES
False
SCOPE
Site preference.
scheduling_graph_view
DESCRIPTION
Used with Schedule Manager resource graphs. Determines whether scroll bars
are included in resource graphs.
VALID
VALUES
Classic Resource graphs display with scroll bars.

Native Resource graphs display without scroll bars.

DEFAULT
VALUES
Native
SCOPE
Site preference.
SiteTimeZone
DESCRIPTION
Stores the time zone of the server. Use this preference to determine the time zone
used by the TCCalendars in the scheduling logic. This preference is used with
Schedule Manager.
VALID
VALUES
Accepts a single value pair indicating a time zone ID from the zoneinfo database
(also known as the Olson database) in the following format:
region/city
For example:
Europe/Paris
Refer to the zoneinfo database (http://en.wikipedia.org/wiki/Zoneinfo) for the
complete list of zone IDs. The system checks for a valid value and displays an error
message when Schedule Manager is launched if an invalid value is detected.
DEFAULT
VALUES
America/Chicago
SCOPE
Site preference.
SM_CriticalPath_Color
DESCRIPTION
Sets the color for display of critical path.
VALID
VALUES
A user can set any value to this preference. The value specified must be a
valid comma-separated integer code specified using three 8-bit unsigned
integers (0 through 255) representing the intensities of red, green, and blue.
DEFAULT
VALUES
Red255,0,0(RGB)
SCOPE
All.
NOTES
This value is set when a user selects the color from the color dialog box.

SM_EVM_Calc_Labels
DESCRIPTION
Specifies whether earned value management (EVM) calculations are displayed as
EVM labels or C/SCSC (cost/schedule control systems criteria) labels.
VALID
VALUES
EVM
C/SCSC
DEFAULT
VALUES
EVM
SCOPE
All.
SM_EVM_Calc_Preference
DESCRIPTION
Specifies whether earned value management (EVM) calculations are based on cost
or hours.
VALID
VALUES
Cost
Hours
DEFAULT
VALUES
Hours
SCOPE
All.
SM_EVM_Export_Units
DESCRIPTION
Specifies whether units are displayed in the Microsoft Excel spreadsheet upon export.
VALID
VALUES
True Exports the units to the Microsoft Excel spreadsheet.
False Does not export the units to the Microsoft Excel spreadsheet.
DEFAULT
VALUES
False
SCOPE
All.

SM_EVM_Work_Complete
DESCRIPTION
Specifies whether earned value management (EVM) calculations are based on
percent of work completed or actual hours of work completed.
VALID
VALUES
Percent Complete
Actual Hours
DEFAULT
VALUES
Percent Complete
SCOPE
All.
SM_SCHEDULING_ENGINE_DATE
DESCRIPTION
Sets the default behavior for new schedules determining if they are scheduled from
the start or end date of the schedule.
VALID
VALUES
Start
Finish
DEFAULT
VALUES
Start
SCOPE
All.
NOTES
This preference determines the default setting for new schedules.
SM_TIMESHEET_APPROVE_WORKFLOW
DESCRIPTION
Overrides the default workflow. It uses a customized workflow. If this preference is
not set, the default workflow is used.
VALID
VALUES
The allowed values are names of approval workflows. For example:
TimeSheetApproval
DEFAULT
VALUES
None.

SCOPE
Site preference.
NOTES
The defined workflow is used when the timesheet entries are submitted.
This preference must be added by an administrator to override the default workflows.
SM_TIMESHEET_REVISE_WORKFLOW
DESCRIPTION
Overrides the default workflow. It uses a customized workflow. If this preference is
not set, the default workflow is used.
VALID
VALUES
The allowed values are names of approval workflows. For example:
TimeSheetRevise
DEFAULT
VALUES
None.
SCOPE
Site preference.
NOTES
The defined workflow is used when the timesheet entries are submitted.
This preference must be added by an administrator to override the default workflows.
SM_View_CriticalPath
DESCRIPTION
Sets the default display of critical path.
VALID
VALUES
True Critical path is displayed.
False Critical path is not displayed.
DEFAULT
VALUES
False
SCOPE
User preference.
NOTES
This value is set when the user chooses the menu to enable viewing critical path.

SM_WBS_FORMAT_PREF
DESCRIPTION
Specifies the default work breakdown structure (WBS) format to be used by
schedules when they are created. The format used by the individual schedules can
be changed at the schedule level.
For more information on setting the default format for new schedules, see the
Schedule Manager Guide.
VALID
VALUES
The valid values must follow this format:
[?N,?A,?a]{[.,-,/,+][?N,?A,?a]}*
? Whole number representing the minimum character length of a given
section. If no number is provided, then 1 is assumed.
N Whole number.
A Uppercase English alphabet character (A-Z).
a Lowercase English alphabet character (a-z).
. Valid separation character.
- Valid separation character.
/ Valid separation character.
+ Valid separation character.
DEFAULT
VALUES
N.N
SCOPE
All.
NOTES
[?N,?A,?a] represents a single section. A minimum of two sections and one separator
must be defined.
SM_WBS_INITIAL_PREF
DESCRIPTION
Specifies the initial starting point for work breakdown structure (WBS) codes, based
on the default WBS format.
For more information on setting the default initial value for new schedules, see
the Schedule Manager Guide.
VALID
VALUES
Some examples of valid values include:
1
1.2
2.2

The values must comply with the format.

DEFAULT
VALUES
1
SCOPE
All.
TC_RA_server_parameters
DESCRIPTION
Configures the Teamcenter’s reporting and analytics (Reporting and Analytics)
parameters at the site level: server host, port, and application name. Use Reporting
and Analytics, powered by eQube, to view, modify, and create reports.
VALID
VALUES
Accepts multiple strings as values in the following format:
Host:application-server-host-name
Port:port-number
Context:application-context
ServletName:eQube-servlet-name
DEFAULT
VALUES
Host:localhost Port:80 Context:eQube ServletName:eQubeServlet
SCOPE
Site preference.
Report Designer preferences

With Report Designer, you can control whether users can view reports from the
Report Designer Reports menu.
Enable_ReportDesigner_Reports
DESCRIPTION
Controls whether the user can view the Tools→Reports→Report Designer Reports
menu command.
VALID
VALUES
true Report Designer Reports menu command is displayed.
false Report Designer Reports menu command is not displayed.
DEFAULT
VALUES
false
SCOPE
Site preference.

Chapter
16 Classification Administration
preferences
ICS_classification_master_site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
ICS_available_languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
ICS_new_classid_pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
ICS_copy_classid_pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
ICS_migrate_classid_pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
ICS_use_view_attributes_when_moving_icos . . . . . . . . . . . . . . . . . . . . . . . . 16-4
ICS_view_selection_order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
ICS_share_related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
ICS_allow_remote_parent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
ICS_mapping_target_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
ICS_unit_default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
ICS_unit_active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
GCS_classify_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8
ICS_import_attribute_use_dbindex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8
ICS_import_attribute_find_free_dbindex . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
ICS_allow_deprecated_lovs_on_update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
ICS_allow_deprecated_lovs_on_copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
ICS_enforce_min_max_constraints_on_update . . . . . . . . . . . . . . . . . . . . . . 16-10
ICS_enforce_min_max_constraints_on_copy . . . . . . . . . . . . . . . . . . . . . . . . 16-11
ICS_allow_min_max_range_override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11
ICS_attribute_displayable_properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12
ICS_override_unit_definition_precision . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12

Chapter
16 Classification Administration
preferences
The Classification Administration application uses a hierarchical classification

structure based on the attribute values of your workspace objects. Classification of
your company’s product data-standard parts, technology data, and manufacturing
equipment saves time by making this component data easier to find and retrieve.
It reduces costs by allowing you to reuse existing parts and consolidate and/or
eliminate duplicate or out-dated parts. Use the application to define the groups,
classes, subclasses, and views that form this classification hierarchy.
For more information, see the Classification Administration Guide.
Use the following preferences to determine classification behavior, such as defining
the number of attributes loaded by default into the Attribute Dictionary table.
ICS_classification_master_site
DESCRIPTION
Determines whether the current site can perform class modifications requiring
access to all descendents. Set this preference to true at the site you want to be
the master site.
A site is the master site for a class or group if all descendants are owned at this site.
(Therefore different parts of the hierarchy can be mastered by different sites.) You
cannot add child classes/groups to parents that are not locally owned. You must
transfer the ownership to the site that is allowed to add children. By tracking
ownership, the master site keeps track of where classes are added locally.
Note
When your classification hierarchy is exchanged between sites using XML or
SML files, rather than Teamcenter Multi-Site Collaboration functionality, the
same change must be applied to all sites.
VALID
VALUES
true The site can perform class modifications requiring access to all
descendents.
false The site cannot perform class modifications requiring access

to all descendents.

Chapter 16 Classification Administration preferences
DEFAULT
VALUES
false
SCOPE
Site preference.
ICS_available_languages
DESCRIPTION
Determines which languages display in the Alias Names box of the Class Details tab
when users create a class. Users select one language from the list, which determines
the language of the alias name.
For more information regarding creating classes, see the Classification
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid language code.
For example:
cn
de
en
es
fr
it
jp
kr
ru
tw
DEFAULT
VALUES
en
SCOPE
Site preference.
ICS_new_classid_pattern
DESCRIPTION
Determines the pattern of the class ID when a new class is created.
All classes in Classification have unique identifiers. Use this preference to determine
the pattern of the class ID when a new class is created.
VALID
VALUES
Accepts a single string as a value. Can be any string, used alone or in conjunction
with the following placeholders:
${P} Represents the class ID of the parent class.

Classification Administration preferences
${NNN} Represents a three digit numerical sequence. Any number of

digits can be defined.
For example, ${P}${NNN} generates Parent000, where Parent is the name of the
parent class, and 000 is the next iterative number.
Another example, ${NNNNNN} generates 000000, where 000000 is the next
iterative number.
Another example, ${P}.new generates Parent.new, where Parent is the name of the
parent class, suffixed by .new.
DEFAULT
VALUES
${P}${NN}
SCOPE
User preference.
ICS_copy_classid_pattern
DESCRIPTION
Determines the pattern of a class ID when a class is copied.
All classes in Classification have unique identifiers. When performing a copy of a
class (hierarchy), users must enter a new class ID for all classes to be copied. These
new class IDs can also be automatically generated for one class or for all classes of
a hierarchy. Use this preference to determine the pattern of class IDs when the
classes are copied.
VALID
VALUES
${CID} Represents the original class ID when a class is copied.
For example, ${CID}${NNN} generates SourceID000, where SourceID is the original
class ID and 000 is the next iterative number.
Another example, ${NNNN} generates 0000, where 00000 is the next iterative
number.
Another example, ${P}_${NNN} generates Parent_000, where Parent is the name of
the parent class and 000 is the next iterative number.
Another example, ${CID}.new generates SourceID.new, where SourceID is the
original class ID, suffixed by .new.
DEFAULT
VALUES
${CID}${NN}
SCOPE
User preference.

ICS_migrate_classid_pattern
DESCRIPTION
Determines the pattern of a class ID when migrating legacy SML subclasses to
abstract subclasses and storage classes.
All classes in Classification have unique identifiers. When SML subclasses are
migrated, a new abstract class is created for each SML class and a storage class is
created directly below the new abstract class for each subclass belonging to the SML
class being migrated. Use this preference to determine the pattern of the class IDs
when subclasses are migrated.
VALID
VALUES
${CID} Represents the original class ID when a class is migrated.
${SID} Represents the original class ID of the SML subclass being
migrated.
For example, ${CID}${SID}${NNN} generates SMLClassIDSubclassID000, where
SMLClassID is the original class ID, SubclassID is the original class ID of the SML
subclass being migrated and 000 is the next iterative number.
Another example, ${NNNN} generates 0000, where 00000 is the next iterative
number.
Another example, ${SID}_${NNN} generates SubclassID_000, where SubclassID
is the original class ID of the SML subclass being migrated and 000 is the next
iterative number.
DEFAULT
VALUES
${CID}${SID}${NN}
SCOPE
User preference.
ICS_use_view_attributes_when_moving_icos
DESCRIPTION
Determines which attribute values are set when an classification object (ICO) is
moved to a different class. Use this site preference to set only the attribute values
visible to the user, or to set all attribute values, during ICO moves.
Moving classes in Classification is similar to copying classes, but is performed via
drag-and-drop from the Classification hierarchy tree. A user can move classes when
the class is not shared, he has read access to all children of the class, and the new
parent class is locally owned.

VALID
VALUES
true Only attribute values which the current user can see in his
view are set when an ICO is moved to a different class.
false All attribute values are set when an ICO is moved to a different
class.
DEFAULT
VALUES
false
SCOPE
Site preference.
ICS_view_selection_order
DESCRIPTION
Determines the order in which Classification views are searched, based on the
current user ID.
VALID
VALUES
Accepts the following strings as values. The order of the values determines the
order in which the views are searched.
USER
PROJECT
ROLE
GROUP
DEFAULT
VALUES
USER
PROJECT
ROLE
GROUP
SCOPE
Site preference.
ICS_share_related
DESCRIPTION
Determines which related objects of a Classification class/view are shared when the
class/view is shared. Use this preference with shared Classification functionality.
VALID
VALUES
Accepts one or more of the following values:
classImage Shares class images.
viewImage Shares view images.

partFamilyTemplates Shares part family templates.

DEFAULT
VALUES
None.
SCOPE
Site preference.
ICS_allow_remote_parent
DESCRIPTION
Determines whether classes and views can be added under classes which are not
locally owned.
VALID
VALUES
true Classes and views can be added under classes which are not
locally owned.
false Classes and views cannot be added under classes which are
not locally owned.
DEFAULT
VALUES
false
SCOPE
Site preference.
ICS_mapping_target_type
DESCRIPTION
Determines whether the mapping target item or item revision is classified.
Note
Siemens PLM Software recommends you set this preference to ItemRevision.
You can map classification objects (ICOs) from one class of your class structure
to another as needed, such as when converting catalog data to customer data. To
make the target object a classified resource, the target ICO must classify a newly
created object, usually an item revision or a similar classified object type. Use this
preference to define the target object’s type.
For more information, see the Classification Guide.

Note
Siemens PLM Software recommends you set the following preferences to
the same value as this preference:
• MRMClassifyResource
• ICS_classify_new
• GCS_classify_type
VALID
VALUES
Accepts a single string as a value. Must be Item, ItemRevision, or a valid custom
item or item revision type.
DEFAULT
VALUES
ItemRevision
SCOPE
Site preference.
ICS_unit_default
DESCRIPTION
Specifies the default system of measurement when creating a class in the
Classification Administration application.
VALID
VALUES
0 Metric system of measurement.
1 Non-metric system of measurement.
2 Both metric and non-metric systems of measurement.
DEFAULT
VALUES
0
SCOPE
User preference.
ICS_unit_active
DESCRIPTION
Specifies the active system of measurement that is initially displayed when a
classification class is defined to hold both metric and non-metric values.
VALID
VALUES
0 Metric system of measurement.
1 Non-metric system of measurement.

DEFAULT
VALUES
0
SCOPE
User preference.
GCS_classify_type
DESCRIPTION
Determines whether items/item revisions are created and classified for components
with connection points.
Note
Siemens PLM Software recommends you set this preference to ItemRevision.
When assigning connection points to non-classifying classification objects (ICOs), a

new classified object is created to receive the connection points. To make the target
object a classified resource, the target ICO must classify a newly-created object,
usually an item revision or a similar classified object type. Use this preference to
define the target object’s type.
Note
Siemens PLM Software recommends you set the following preferences to
the same value as this preference:
• ICS_mapping_target_type
VALID
VALUES
Accepts a single string as a value. Must be Item, ItemRevision, or a valid custom
item or item revision type.
DEFAULT
VALUES
ItemRevision
SCOPE
Site preference.
ICS_import_attribute_use_dbindex
DESCRIPTION
Specifies the use of the dbindex position in the database when importing
Classification Administration data.
When you import PLM XML or XML data in Classification Administration, the
dbindex position is used. To disable this, set this preference to False.

VALID
VALUES
True Teamcenter uses the dbindex position when importing data.
False Teamcenter ignores dbindex position when importing data.
DEFAULT
VALUES
True
SCOPE
Site preference.
ICS_import_attribute_find_free_dbindex
DESCRIPTION
Specifies that Teamcenter should find the next free dbindex position in the database
if the specified dbindex position is already in use when importing Classification
Administration data using PLM XML or XML data.
This preference is only evaluated if the ICS_import_attribute_use_dbindex
preference is set.
VALID
VALUES
True Teamcenter tries to find the next dbindex position when
importing data.
False If the specified dbindex position is in use, Teamcenter displays
an error.
DEFAULT
VALUES
False
SCOPE
Site preference.
NOTES
If this preference does not exist in the database, Teamcenter uses the default value
of False.
ICS_allow_deprecated_lovs_on_update
DESCRIPTION
Determines whether users can update and save classification objects (ICOs) that use
deprecated LOV values for their classification properties.
VALID
VALUES
True Allows users to use deprecated LOV values for classification
properties.
False Requires users to use non-deprecated LOV values for the
classification properties.

DEFAULT
VALUES
False
SCOPE
Site preference.
ICS_allow_deprecated_lovs_on_copy
DESCRIPTION
Determines whether users can copy classification objects (ICOs) that use deprecated
LOV values for classification properties.
This preference applies for users performing the following actions in Teamcenter:
• Performing a Revise or SaveAs operation on an Item or ItemRevision from
anywhere outside Classification.
• Revising product structure that contains the classified objects.
VALID
VALUES
True Allows users to create copies of ICOs that use deprecated LOV
values for classification properties.
False Prevents users from copying ICOs that use deprecated LOV
values for classification properties.
DEFAULT
VALUES
True
SCOPE
Site preference.
ICS_enforce_min_max_constraints_on_update
DESCRIPTION
Determines whether Classification enforces minimum and/or maximum constraints
on all classification property values during updating and saving classification objects
(ICOs).
VALID
VALUES
True Enforces minimum and/or maximum constraints on all classification
property values when updating and saving ICOs.
False Does not enforce minimum and/or maximum constraints on all classification
property values when updating and saving ICOs.
DEFAULT
VALUES
True
SCOPE
Site preference.

ICS_enforce_min_max_constraints_on_copy
DESCRIPTION
Determines whether Classification allows copying existing classification objects
(ICOs) whose property values do not conform to the minimum and/or maximum
constraints.
This preference applies for users performing the following actions in Teamcenter:
• Performing a Revise or SaveAs operation on an Item or ItemRevision from
anywhere outside Classification.
• Revising product structure that contains the classified objects.
VALID
VALUES
True Classification does not allows copying existing ICOs whose
property values do not conform to the minimum and/or
maximum constraints.
False Classification allows copying existing ICOs whose property
values do not conform to the minimum and/or maximum
constraints.
DEFAULT
VALUES
False
SCOPE
Site preference.
ICS_allow_min_max_range_override
DESCRIPTION
Determines whether the system allows Classification Administration to specify
values to the following:
• Class attribute minimum and/or maximum constraints outside the range of
Dictionary attribute minimum and/or maximum constraints.
• View attribute minimum and/or maximum constraints outside the range of

Class attribute minimum and/or maximum constraints.
VALID
VALUES
True Allows Classification Administration to specify values.
False Does not allow Classification Administration to specify values.
DEFAULT
VALUES
True
SCOPE
Site preference.

ICS_attribute_displayable_properties
DESCRIPTION
Displays the list of attribute properties on classification properties in the
Classification application.
The administrator provides valid dictionary attribute properties and user-defined
properties, for example:
• AttributeID
• Name
VALID
VALUES
Accepts strings.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ICS_override_unit_definition_precision
DESCRIPTION
Specifies whether Teamcenter overrides the precision defined in the Decimal
Places attribute in the unit definition ICO while displaying the attribute value of
the attributes for which optimized display is turned on.
VALID
VALUES
true Teamcenter overrides the number of decimal places specified in the unit
definition.
false Teamcenter displays the number of decimal places specified in the unit
definition.
DEFAULT
VALUES
false
SCOPE
All

Chapter
17 Classification preferences
ICS_attribute_mapping_trim_zeros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
ICS_classifiable_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
MRMClassifyResource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2
ICS_classify_immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
ICS_classify_immediately_NX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
ICS_classify_new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
ICS_datasettype_for_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
ICS_presented_instance_documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
ICS_default_instance_document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
ICS_presented_class_documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
ICS_default_class_document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
ICS_enable_graphical_browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
ICS_GraphicsBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
ICS_hierarchy_sort_option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
ICS_hierarchy_list_icon_size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
ICS_default_root_selector_entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
ICS_root_selector_entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
ICS_user_defined_button_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
ICS_show_autofilter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
ICS_ico_action_after_saveas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
ICS_itemrev_master_dataset_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
ICS_master_datasettypes_for_itemrev . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
ICS_max_number_of_components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
ICS_search_use_revision_rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13
ICS_search_default_revision_rule_<application name> . . . . . . . . . . . . . . . . 17-13
ICS_synchronize_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
ICS_synchronize_automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
ICS_table_header_style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
ICS_table_pagesize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
ICS_use_access_control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
ICS_web_preferred_jt_image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
ICS_classify_sendto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16

Chapter
17 Classification preferences
Classification of your company’s product data—standard parts, technology data,

manufacturing equipment—saves time by making component data easier to find and
retrieve and reduces costs by allowing you to reuse existing parts and consolidate
and/or eliminate duplicate or outdated parts. Classification is used to create and
maintain a hierarchical classification structure based on the attribute values of
your workspace objects.
Use classification preferences to configure and control aspects of a Classification
session.
ICS_attribute_mapping_trim_zeros
DESCRIPTION
Determines whether, during attribute mapping between NX and Classification,
leading and/or trailing zeros are stripped from Classification attribute values when
they are sent to NX.
VALID
VALUES
keep Does not change the Classification attribute value. For
example, 001.3400 is transferred as 001.3400 to NX.
leading Leading zeros are stripped from the Classification attribute

value. For example, 001.3400 is transferred as 1.3400 to NX.
both Leading and trailing zeros are stripped from the Classification
attribute value. For example, 001.3400 is transferred as 1.34
to NX.
DEFAULT
VALUES
keep
SCOPE
User preference.
ICS_classifiable_types
DESCRIPTION
Specifies the list of Teamcenter types that can be classified.

Chapter 17 Classification preferences
VALID
VALUES
Valid Teamcenter types. The two default values, Item and ItemRevision, are
considered a set. Therefore, if the item is classified the item revision cannot be
classified, but it inherits the classification record from the item. This also works
in the reverse; if the item revision is classified, the item cannot be classified, but
inherits the classification record.
Any types defined for the following preferences should be also defined for this
preference:
• GCS_classify_type
DEFAULT
VALUES
Item
ItemRevision
CommercialPart
ManufacturerPart
CommercialPart Revision
ManufacturerPart Revision
SCOPE
Site preference.
RESTRICTIONS
The values listed must be the internal business object names and not the display
names. You can find the internal language-independent names in the Business
Modeler IDE application.
MRMClassifyResource
DESCRIPTION
Determines whether new items and item revisions are classified at the time they are
created using the File→New→Resource menu command.
Note
Regardless of this preference’s settings, existing objects can still be classified
using the Classify Item and Classify Item Revision menu commands.
VALID
VALUES
Accepts a single string as a value. The string must be either Item or ItemRevision.
Note
Siemens PLM Software recommends classifying item revisions during
creation, otherwise some functionality (revisioning, propagated attributes,
statuses) is limited.

Classification preferences
DEFAULT
VALUES
ItemRevision
SCOPE
Site preference.
ICS_classify_immediately
DESCRIPTION
Determines the default setting of the Classify Immediately option in the New
Item, Save As, and Revise dialog boxes. This preference is valid only when the
ICS_classify_new preference is set.
VALID
VALUES
0 The Classify Immediately option is not selected by default when the
dialog box appears.
1 The Classify Immediately option is selected by default when the dialog
box appears.
DEFAULT
VALUES
1
SCOPE
User preference.
ICS_classify_immediately_NX
DESCRIPTION
Determines whether new items and item revisions are classified immediately within
Teamcenter when saved from Teamcenter Integration for NX. This preference is
valid only when the ICS_classify_new preference is set.
VALID
VALUES
0 Does not classify a new item or item revision within Teamcenter when saved
from Teamcenter Integration for NX.
1 Classifies a new item or item revision within Teamcenter when saved from
Teamcenter Integration for NX. When Teamcenter Integration for NX is
launched from rich client and a newly created part is saved in NX, the user
is asked in rich client to classify the new item or item revision.
DEFAULT
VALUES
0
SCOPE
User preference.

ICS_classify_new
DESCRIPTION
Enables the Classify Immediately option on the New Item, Save As, and Revise
dialog boxes and specifies whether it is the item or the item revision that is classified.
VALID
VALUES
Item Immediately classifies the item.
ItemRevision Immediately classifies the item revision.
DEFAULT
VALUES
ItemRevision
SCOPE
User preference.
ICS_datasettype_for_class
DESCRIPTION
Specifies the type of dataset used when images are added to subclasses.
VALID
VALUES
A valid Teamcenter dataset.
DEFAULT
VALUES
UGPART
SCOPE
All.
ICS_presented_instance_documents
DESCRIPTION
Determines which named references display in the instance viewer. The system
searches all datasets of the selected object for named references. Any named
references corresponding to the values of this preference display as a tab in the
instance viewer.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid named reference,
or one of the following values:
BOMAssembly
JTAssembly
DEFAULT
VALUES
BOMAssembly
JTAssembly
JTPART

Image
Markup
3DModel
3DMarkup
JPEG
Graphics-Interface
Shaded-Image
Common-Graphics-Meta
Direct-Model-Data
UGPART
HTML
word
excel
PDF
SCOPE
All.
ICS_default_instance_document
DESCRIPTION
Determines which of the named reference file types defined in the
ICS_presented_instance_documents preference displays in the instance viewer
by default. Limiting the values defined in this preference can quicken viewing
time. For example, by not specifying BOMAssembly object in this preference,
BOM assemblies have to be expressly selected to appear. This saves users time
when paging through classification objects of large assemblies. When none of the
document types defined in this preference are associated with a classification object,
the instance viewer displays no attachment by default.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid named reference
file type that has been defined in the ICS_presented_instance_documents
preference.
DEFAULT
VALUES
JTPART
Image
Markup
3DModel
3DMarkup
JPEG
Graphics-Interface
Shaded-Image
Common-Graphics-Meta
Direct-Model-Data
word
SCOPE
All.

ICS_presented_class_documents
DESCRIPTION
Determines which named references display in the class viewer. The system searches
all datasets of the selected class for named references. Any named references
corresponding to the values of this preference display as a tab in the class viewer.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid named reference.
DEFAULT
VALUES
ICS-ClassImage
ICS-ClassImage1
ICS-ClassImage2
ICS-ClassImage3
ICS-ClassImage4
ICS-ClassImage5
ICS-ClassImage6
ICS-ClassImage7
ICS-ClassImage8
ICS-ClassImage9
SCOPE
User preference.
ICS_default_class_document
DESCRIPTION
Determines which of the documents defined in the
ICS_presented_class_documents preference display by default.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid named reference
file type that has been defined in the ICS_presented_class_documents preference.
DEFAULT
VALUES
ICS-ClassImage
ICS-ClassImage1
ICS-ClassImage2
ICS-ClassImage3
ICS-ClassImage4
ICS-ClassImage5
ICS-ClassImage6
ICS-ClassImage7
ICS-ClassImage8
ICS-ClassImage9
SCOPE
User preference.

ICS_enable_graphical_browser
DESCRIPTION
Enables the Graphical Browser tab in Classification and the Classification Search
Dialog. You can browse through the classification hierarchy by viewing thumbnail
graphics representing each class.
For more information about using the graphical browser, see the Classification Guide.
VALID
VALUES
true Makes the graphical browser tab visible in the hierarchy pane.
false Removes the Graphical Browser tab from the user interface.
DEFAULT
VALUES
false
SCOPE
Site preference.
ICS_GraphicsBuilder
DESCRIPTION
Specifies the graphics builder utility used by Classification to enable the graphic
creation functionality in the Classification application.
VALID
VALUES
ActivationMethod:
TCE_Activation
CommandLine:
Specifies the path to the GraphicsBuilder executable script; typically located in the
Teamcenter_root\bin\nx_graph directory.
ScriptEvaluationPath
Specifies the path to the directory containing the ics_graphicsbuilder.tcl file.
evaluateScript
Specifies whether to perform script evaluation of newly created classes. Valid values
are yes, no, not set.
evaluateScriptWhenNotSet
Permits GraphicsBuilder to evaluate TCL scripts even when TCL script evaluation
is defined as not set for the Classification object’s class.
For example:
ICS_GraphicsBuilder=
NXGraphicsBuilder
NXGraphicsBuilder=
ActivationMethod:TCE_Activation
CommandLine:path-to-GraphicsBuilder-executable-script

DEFAULT
VALUES
None.
SCOPE
Site preference.
ICS_hierarchy_sort_option
DESCRIPTION
Determines how the classification hierarchy tree is sorted and displayed. The tree
is sorted and displayed alphanumerically in ascending order based on the value
assigned.
VALID
VALUES
-600 Class ID/subclass ID. Groups are treated as classes.
-607 Name.
-609 Image.
-612 User1.
-613 User2.
DEFAULT
VALUES
-600
SCOPE
All.
ICS_hierarchy_list_icon_size
DESCRIPTION
Specifies the size of the icons that are displayed in the classification hierarchy in
Classification and Classification Search Dialog.
VALID
VALUES
Accepts an integer as a valid pixel size for the images to be displayed.
DEFAULT
VALUES
35
SCOPE
All.
ICS_default_root_selector_entries
DESCRIPTION
Determines which classes display in the root node selection list. By default, this
list displays only Classification Root.

Use this preference to allow users to select a class to become the root node of their
Classification hierarchy from a predefined list. Users access this list by clicking
in the title bar of the hierarchy pane. The root node selection list appears. If your
site has a very complex classification hierarchy, use this preference to allow users to
select any point in the hierarchy to be their root node. You can store any number of
classes in the options list to change the hierarchy root node.
For more information about viewing a subset of your site’s hierarchy, see the
Classification Guide.
Note
Users can add additional classes to this list using the Add Current Class
command, which modifies the ICS_root_selector_entries preference.
VALID
VALUES
Accepts multiple string pairs as values. Each string pair must be in the following
format:
Class ID
Description
DEFAULT
VALUES
ICM
Classification Root
SCOPE
Site preference.
ICS_root_selector_entries
DESCRIPTION
Determines the class and description text for the classes that users have selected to
display in the root node selection list.
Typically, this preference is populated by users selecting a class, then selecting
the Add Current Class command from the Option menu in the Classification
application. The system prompts users for a description of the selected class. By
default, the descriptive text is the class name. The user’s selections are added as
values to this preference.
This preference can also be modified by users right-clicking a class and choosing the
Add current class to root selector option on the shortcut menu.
VALID
VALUES
Accepts multiple string pairs as values. Each string pair must be in the following
format:
Class ID
Description
For example:
ICM
Classification Root

MRM
Resource Management
TLCAC
Catalog Components
TLCUC
Customer Components
TLCUA
Customer Assemblies
DEFAULT
VALUES
None.
SCOPE
User preference.
ICS_user_defined_button_class
DESCRIPTION
Determines where the system searches for the user-defined button classes in the
Classification and Resource Manager applications.
For more information about user-defined button classes, see the Classification
VALID
VALUES
USER1 System searches in the User 1 field of the attribute in the dictionary,
class, and view for the Java class defined for the user-defined button.
USER2 System searches in the User 2 field of the attribute in the dictionary,
class, and view for the Java class defined for the user-defined button.
DEFAULT
VALUES
None.
If left undefined, the system uses the settings in the registry (property file) to
determine the Java class for the user-defined button.
SCOPE
Site preference.
ICS_show_autofilter
DESCRIPTION
Determines whether auto filter functionality is enabled in Classification.
VALID
VALUES
true Auto filter functionality is enabled in Classification. The Auto filter
button displays before the text fields of attributes.
false Auto filter functionality is not enabled in Classification.
DEFAULT
VALUES
false

SCOPE
Site preference.
ICS_ico_action_after_saveas
DESCRIPTION
Determines the action to be taken when users use the Copy, Revise, or Save As
commands on a classified object.
When users use the Copy, Revise, or Save As commands on a workspace object, the
GRM relations are copied to the new object. Therefore, when the object is a classified
object, the IMAN_classification relation is copied to the new object, resulting in
a situation where two objects (the object created by the Copy, Revise, or Save As
command and the original object) reference the same classification record.
Set this preference to delete to avoid this situation.
VALID
VALUES
copy Creates a copy of the original classification record with a resource ID
matching the ID of the new object, thus classifying the new object.
delete Deletes the IMAN_classification relation between the new object and
the classification record of the original object. The new object can then
be classified using standard Classification procedures.
DEFAULT
VALUES
copy
SCOPE
All.
ICS_itemrev_master_dataset_relation
DESCRIPTION
Specifies the relationship between the item revision and the dataset type that is
defined in the ICS_master_datasettypes_for_itemrev preference.
VALID
VALUES
Valid Teamcenter datasets.
DEFAULT
VALUES
IMAN_specification
SCOPE
All.
ICS_master_datasettypes_for_itemrev
DESCRIPTION
Specifies the dataset types that can be classified, when used in conjunction with
the ICS_classifiable_types preference. For example, if Dataset is included as a

classifiable type in the ICS_classifiable_types preference and UGMASTER is

included as a value for the ICS_master_datasettypes_for_itemrev preference,
item/item revision/UGMASTER are considered a set and the following configuration
rules apply:
• If the item is classified, the item revisions and corresponding dataset cannot be
classified, but they inherit the classification record from the item.
• If an item revision is classified, the corresponding dataset and item cannot be
classified. Other revisions of the same item can, however, be classified.
• If the dataset is classified, the corresponding item revision and item cannot be
classified. Other revisions and datasets, however, can be classified.
VALID
VALUES
Valid Teamcenter relation.
DEFAULT
VALUES
UGMASTER
SCOPE
All.
ICS_max_number_of_components
DESCRIPTION
Determines the maximum number of components an assembly can contain before
a warning appears. When the selected assembly (typically a resource assembly)
contains more than the defined number of components, the warning states the
selected assembly is large and requires the user to confirm loading the assembly.
The user can click Yes to display the assembly, or No to not display the assembly.
If set to 0 or left undefined, assemblies are always displayed, regardless of size,
without warning.
VALID
VALUES
0 All assemblies are always displayed, with no warning
regarding assembly size.
Single positive If assembly has less components than the number defined, no
integer warning appears when displaying the assembly. If assembly
has more components than the number defined, a warning
appears:
The assembly contains more than # components.
Do you really want to show it?
DEFAULT
VALUES
100
SCOPE
All.

ICS_search_use_revision_rule
DESCRIPTION
Determines whether revision rules can be used for a classification search.
VALID
VALUES
true Enables revision rules functionality for classification searches.
false Disables revision rules functionality for classification searches.
DEFAULT
VALUES
true
SCOPE
User preference.
ICS_search_default_revision_rule_<application name>
DESCRIPTION
Specifies the default revision rule used for a classification search.
Users can select revision rules to apply to classification searches from the
Classification application and from the Classification Search Dialog in other
applications. Users can select a default revision rule for searches (and thus, set this
preference from the interface) by clicking to the right of the Revision Rule link to
display the revision rule shortcut menu, then choosing Save as default.
VALID
VALUES
Accepts a single string as a value. It must be a valid revision rule. The suffix
of the preference name indicates the application for which this functionality is
enabled. Thus, the Classification suffix determines the default revision rule for
searches performed in the Classification application, the Resource_Manager suffix
determines the default revision rule for searches performed using the Classification
dialog box in the Resource Manager application, and so on. For example:
ICS_search_default_revision_rule_Classification=
Latest Working
Note
The suffix is dependent on the user’s language setting. The name of the
application must be written in the language setting used by the user. If a
user’s language setting is German, the example would be:
ICS_search_default_revision_rule_Klassifizierung=
Latest Working
DEFAULT
VALUES
None.
SCOPE
User preference.

ICS_synchronize_sites
DESCRIPTION
Specifies the sites with which Classification data can be shared via Multi-Site
Collaboration. The sites specified in this preference display in the Shared Sites
dialog box.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter site
name. Site names must be entered into the database in a Organization/Sites
format.
For more information about creating Teamcenter sites, see the Multi-Site
Collaboration Guide and the Organization Guide.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ICS_synchronize_automatically
DESCRIPTION
Enables automatic synchronization of Classification data to the sites specified in
the ICS_synchronize_sites preference.
VALID
VALUES
0 Classification hierarchy data is not shared to the selected sites whenever
the data is saved.
1 Classification hierarchy data is automatically shared to the selected sites
whenever the data is saved.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ICS_table_header_style
DESCRIPTION
Controls the display of attribute names in the table page header.
VALID
VALUES
Short Displays abbreviated attribute names.
Long Displays the full attribute name.

DEFAULT
VALUES
Short
SCOPE
All.
ICS_table_pagesize
DESCRIPTION
Determines the number of rows (instances) initially displayed in the Classification
table page in the thin client.
VALID
VALUES
A positive integer.
DEFAULT
VALUES
5
SCOPE
All.
ICS_use_access_control
DESCRIPTION
Determines the availability of the Classification access control feature.
VALID
VALUES
0 Disables access control functionality.
1 Enables access control functionality.
DEFAULT
VALUES
1
SCOPE
Site preference.
ICS_web_preferred_jt_image
DESCRIPTION
Determines which JT image is displayed in the Classification thin client when users
select TcVis from the View menu. Use this preference to determine which image
(single JT or JTs of BOM lines) displays when the classification objects contains both
a single JT image and is a BOM assembly with JTs in the BOM lines.
Note
When the classification object contains only one image, the JT displays as
follows:

• When the classified object contains a single JT file (as a direct model dataset)
the JT file appears.
• When the classified object is a BOM assembly, the JTs of the BOM lines display.
VALID
VALUES
BOM_Assembly Displays BOM assembly JTs.
Single_JT Displays single JT.
DEFAULT
VALUES
BOM_Assembly
SCOPE
User preference.
ICS_classify_sendto
DESCRIPTION
Controls which of the available applications are displayed when you use the Send
To command in Classification and Resource Manager.
VALID
VALUES
Accepts a list of strings as values. Each string must be a valid Teamcenter
application ID or application name.
DEFAULT
VALUES
com.teamcenter.rac.ui.perspectives.navigatorPerspective
com.teamcenter.rac.pse.PSEApplication
com.teamcenter.rac.designcontext.DesignContextApplication
com.teamcenter.rac.cme.mrm.MRMApplication
com.teamcenter.rac.classification.icm.ICMApplication
com.teamcenter.rac.cme.fse.FSEApplication
com.teamcenter.rac.cme.pmp.PMPApplication
com.teamcenter.rac.cme.mpp.MPPApplication
SCOPE
Site preference.

Chapter
18 Data sharing preferences
Multi-Site Collaboration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Baseline_auto_remote_checkout_allowed . . . . . . . . . . . . . . . . . . . . . . . . 18-1
HUB_no_export_record_transfer_site_list . . . . . . . . . . . . . . . . . . . . . . . . 18-2
IDSM_Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
IDSM_Compression_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
IDSM_do_not_resend_up_to_date_file . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
IDSM_dsa_sites_permitted_to_push_admin_data . . . . . . . . . . . . . . . . . . 18-4
IDSM_dsa_notification_email_address . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
IDSM_exclude_unpublished_components . . . . . . . . . . . . . . . . . . . . . . . . 18-5
IDSM_ft_buffer_kb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
IDSM_ft_client_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
IDSM_ft_get_port_number_from_services . . . . . . . . . . . . . . . . . . . . . . . . 18-6
IDSM_ft_port_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
IDSM_ft_server_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
IDSM_ft_use_rpc_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
IDSM_permitted_checkout_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
IDSM_permitted_checkout_users_from_site_<sitename> . . . . . . . . . . . . . 18-8
IDSM_permitted_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9
IDSM_permitted_transfer_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9
IDSM_permitted_transfer_users_from_site_<sitename> . . . . . . . . . . . . . . 18-9
IDSM_permitted_users_from_site_<sitename> . . . . . . . . . . . . . . . . . . . 18-10
IDSM_proxy_client_alternate_proxy_host_for . . . . . . . . . . . . . . . . . . . . 18-10
IDSM_proxy_server_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
IDSM_restricted_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
ITEM_autopublish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
ITEM_autopublish_ignore_errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12
ITEM_autopublish_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
ITEM_id_allow_if_registry_down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
ITEM_id_always_register_on_creation . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
ITEM_id_registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14
ITEM_id_registry_site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14
ITEM_id_unregister_on_delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14
ITEM_relation_types_update_lmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-15
ODS_multiprocess_idle_subprocess_timeout . . . . . . . . . . . . . . . . . . . . . 18-15
ODS_multiprocess_initial_subprocess_count . . . . . . . . . . . . . . . . . . . . . 18-16
ODS_multiprocess_max_subprocess_count . . . . . . . . . . . . . . . . . . . . . . 18-16
ODS_multiprocess_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16
ODS_permitted_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17
ODS_proxy_server_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17
ODS_publication_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18
ODS_restricted_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18
ODS_searchable_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18
ODS_searchable_sites_excluded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19

ODS_site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
ODS_suppress_pubrec_if_no_access . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
Role-based preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20
TC_ownership_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20
TC_dataset_vers_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20
TC_bom_level_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-21
TC_modified_only_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-21
TC_relation_export_hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22
TC_always_exclude_dataset_files_on_export . . . . . . . . . . . . . . . . . . 18-22
TC_<daemon name>_<site ID>_prog_number . . . . . . . . . . . . . . . . . . . . 18-23
TC_<daemon name>_<site name>_port_number . . . . . . . . . . . . . . . . . . 18-23
TC_<daemon name>_<site name>_prog_number . . . . . . . . . . . . . . . . . . 18-24
Tc_allow_users_edit_pfdata_options . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-24
TC_altrep_update_lmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-25
TC_appref_registry_site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-25
TC_assembly_xml_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-25
TC_background_object_export_dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-26
TC_bom_level_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-26
TC_check_remote_user_priv_from_sites . . . . . . . . . . . . . . . . . . . . . . . . 18-27
TC_dataset_vers_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
TC_default_export_sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
TC_directly_transferable_classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-29
TC_disallow_release_status_on_replica . . . . . . . . . . . . . . . . . . . . . . . . . 18-29
TC_disallowed_replica_relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-29
TC_do_not_insert_imported_objects_into_folder . . . . . . . . . . . . . . . . . . . 18-30
TC_EMAIL_AFTER_BACKGROUND_REMOTE_IMPORT . . . . . . . . . . 18-31
Tc_export_pfmember_replica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-31
TC_external_app_reg_url . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-31
TC_follow_ownership_chain_max_site_count . . . . . . . . . . . . . . . . . . . . . 18-32
TC_force_remote_sites_exclude_files . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-32
TC_hub_groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-33
TC_identify_plmxml_import_dataset . . . . . . . . . . . . . . . . . . . . . . . . . . 18-34
TC_idsm_client_def_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-35
TC_idsm_client_initial_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-35
TC_idsm_proxy_server_site_table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-36
TC_ie_error_report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-36
TC_master_locale_<site_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-37
TC_modified_only_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-37
TC_ods_client_extra_attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-38
TC_ods_client_def_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-39
TC_ods_client_initial_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-40
TC_ods_proxy_server_site_table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-40
TC_on_demand_sync_broadcast_mode . . . . . . . . . . . . . . . . . . . . . . . . . 18-40
TC_ownership_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-41
TC_plmxml_import_item_filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-41
TC_plmxml_sync_dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-42
TC_post_export_script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-42
TC_pre_import_script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-43
Tc_preserve_replica_pfmember_ownership . . . . . . . . . . . . . . . . . . . . . . 18-43
Tc_publish_pfdata_with_assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-44
Tc_publish_pfmembers_with_pftemplate . . . . . . . . . . . . . . . . . . . . . . . . 18-44
Tc_publish_pftemplate_with_pfmember . . . . . . . . . . . . . . . . . . . . . . . . 18-45
TC_publishable_classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-45
TC_reference_update_lmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-46

TC_rendering_update_lmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-46
TC_relation_export_on_transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-47
TC_relation_required_on_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-47
TC_relation_required_on_transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-48
TC_remote_checkin_assy_option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-48
TC_remote_checkin_exclude_relations . . . . . . . . . . . . . . . . . . . . . . . . . 18-49
TC_remote_checkin_preserve_replica_owning_user_and_group . . . . . . . . 18-50
TC_remote_checkin_relation_send_as_replica . . . . . . . . . . . . . . . . . . . . 18-51
TC_replication_exclude_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-51
TC_replica_volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-51
TC_retain_group_on_import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-52
TC_stub_dataset_files_after_ownership_transfer . . . . . . . . . . . . . . . . . . 18-52
TC_subscribable_replica_classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-53
TC_sync_max_assy_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-53
TC_sync_revision_rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-54
TC_transfer_area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-54
TC_truncate_file_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-55
TC_use_group_admin_as_default_replica_owner . . . . . . . . . . . . . . . . . . 18-56
TC_validate_stub_tickets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-56
Data Exchange preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-57

Alt_id_default_idContext_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-57
Alt_id_default_identifier_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-57
GMS_UID_mapping_dbname_index . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-57
GMS_UID_mapping_remote_site_index . . . . . . . . . . . . . . . . . . . . . . . . 18-58
GS_USER_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-58
GS_USER_PASSWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-59
PDX_pkg_file_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-59
SRM_host_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-60
TC_default_gms_site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-60
TC_default_gms_transfer_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-61
TC_gms_import_default_transfermode . . . . . . . . . . . . . . . . . . . . . . . . . 18-61
TC_gms_enable_immediate_option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-61
TC_gms_export_default_transfermode . . . . . . . . . . . . . . . . . . . . . . . . . 18-62
TC_gms_export_transfermode_for_<site_name> . . . . . . . . . . . . . . . . . . 18-62
TC_gms_gs_bos_service_url . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-62
TC_gms_gs_server_url . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-63
TC_gms_gs_uri . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-63
TC_gms_monitoring_gui_total_number_of_steps_for_transfer . . . . . . . . . 18-63
TC_gms_sso_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-64
TIE_allow_import_with_different_SML . . . . . . . . . . . . . . . . . . . . . . . . . 18-64
TIE_exp_pending_object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-64
TIE_reference_objects_list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-65
TIE_validate_against_xsd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-66
PLM XML preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-66

PIE_<transfer_mode_name>_process_in_chunks . . . . . . . . . . . . . . . . . . 18-66
PIE_<transfer_mode_name>_unload_objects . . . . . . . . . . . . . . . . . . . . . 18-67
PIE_allow_import_with_different_sml . . . . . . . . . . . . . . . . . . . . . . . . . 18-68
PIE_Extra_Error_Info_to_Xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-68
PIE_IMF_FOR_CAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-69
PIE_transfermode_languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-69
PLMXML_continue_on_error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-70
PLMXML_export_packed_bom_<transfer-mode-name> . . . . . . . . . . . . . 18-70

PLMXML_import_default_password . . . . . . . .... . . . . . . . . . . . . . . . . 18-70
PLMXML_log_file_content . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . 18-71
PLMXML_overwrite_objects_on_import . . . . .... . . . . . . . . . . . . . . . . 18-72
PLMXML_put_objects_in_newstuff_on_import ... . . . . . . . . . . . . . . . . 18-72
PLMXML_put_pie_log_in_syslog . . . . . . . . . .... . . . . . . . . . . . . . . . . 18-73
PLMXML_sdk_threshold . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . 18-73
PLMXML_use_pre_plm_appname . . . . . . . . .... . . . . . . . . . . . . . . . . 18-73
TC_export_child_groups . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . 18-74
TC_export_parent_groups . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . 18-74
STEP Translator preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-75

STEP_<relation_type> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-75
STEP_approved_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-75
STEP_default_BOMView_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-76
STEP_default_datasettype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-76
STEP_default_item_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-76
STEP_design_specification_pref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-77
STEP_drawing_pref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-77
STEP_cad_filename_pref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-77
STEP_export_data_format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-78
STEP_export_directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-78
STEP_FILETYPE_2_DATATYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-78
STEP_DMI_markup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-79
STEP_IMAN_master_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-79
STEP_IMAN_specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-79
STEP_IMAN_manifestation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-80
STEP_IMAN_requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-80
STEP_IMAN_reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-80
STEP_IMAN_UG_altrep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-81
STEP_IMAN_UG_scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-81
STEP_import_directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-81
STEP_informative_doc_role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-82
STEP_make_or_buy_attr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-82
STEP_material_specification_pref . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-82
STEP_not_yet_approved_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-83
STEP_part_items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-83
STEP_process_specification_pref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-83
STEP_surface_finish_specification_pref . . . . . . . . . . . . . . . . . . . . . . . . . 18-84
TC_organization_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-84

Chapter
18 Data sharing preferences
Data sharing preferences modify the behavior of Data Exchange, Multi-Site

Collaboration, PLM XML import/export, and STEP Translator.
Multi-Site Collaboration preferences

Multi-Site Collaboration allows you to easily share product information across a
global enterprise using semiautomated, real-time data sharing throughout the
entire enterprise.
For more information about using Multi-Site Collaboration, see the Multi-Site
Collaboration Guide.
Use the following Multi-Site Collaboration preferences to configure and modify the
behavior of Multi-Site Collaboration. Many of these preferences contain default
values that have been commented out. Remove the # symbol preceding the line to
uncomment the entry and implement the value.
Baseline_auto_remote_checkout_allowed
DESCRIPTION
Determines whether automatic remote checkout of replicated objects is allowed
during a baseline operation. If allowed, replica items, and BOM views of replica
item revisions, will be (automatically) checked out during baseline operations. The
resulting baseline object is owned by the original owning site once the item or
BOM view is remotely checked back in (automatically) after the baseline operation
successfully completes.
Use this preference at sites using the remote check out/check in method, rather than
the method of transferring ownership of objects. If your site often creates baselines
of remote objects, enabling this preference will improve system performance.

Chapter 18 Data sharing preferences
Caution
Before setting this preference to True, ensure that the baseline business rules
are the same at the owning site and remote site. Otherwise, revision IDs
produced at the baseline will be of inconsistent values.
For more information about setting business rules, see the Business Modeler
IDE Guide.
Caution
The status type to be applied at the replica site must also exist at the owning
site.
VALID
VALUES
True or On or 1 Automatic remote checkout of replicated objects is allowed
(case insensitive) during baseline operations.
False or Off or 0 Automatic remote checkout of replicated objects is not allowed
(case insensitive) during baseline operations. Users can remote checkout replica
objects manually, and proceed with a baseline operation.
DEFAULT
VALUES
False
SCOPE
Site preference.
HUB_no_export_record_transfer_site_list
DESCRIPTION
Prevents the distribution of export records when site ownership is transferred from
the hub. Use this preference to hide sensitive site information from unauthorized
sites.
This preference is valid only for a hub site. When an export record is created at the
importing site, the site objects are created if they do not already exist. As a result,
information that may be confidential (such as the site ID, site name, and IP address)
could be inadvertently distributed without this preference.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid site authorized to
transfer site ownership from the hub.
DEFAULT
VALUES
None. If this preference is not defined, all export records are always be transferred
to the new owning site of the data.
SCOPE
Site preference.

Data sharing preferences
IDSM_Compression
DESCRIPTION
Enables or disables data compression during remote import operations.
For data compression to be employed between two Multi-Site Collaboration sites,
both sites must set this preference to True to enable compression, and both sites
must specify the same compression type by setting the IDSM_Compression_type
preference.
VALID
VALUES
TRUE Enables compression at the site during remote import
operations.
FALSE Disables data compression during remote import operations.
DEFAULT
VALUES
TRUE (Commented out).
SCOPE
Site preference.
IDSM_Compression_Type
DESCRIPTION
Specifies the type of data compression use by Multi-Site Collaboration.
Currently, InfoZip is the only compression type Multi-Site Collaboration supports.
If the IDSM_Compression preference is defined, this preference must also be
defined to enable data compression.
Tip
InfoZip does not need to be manually installed; it is embedded in the
Teamcenter software. The %TC_BIN%\compress.pl script (Windows) or
$TC_BIN/compress.pl script (UNIX) is used to complete the compression.
The compress.pl is installed with the TC_ROOT directory.
VALID
VALUES
Infozip Specifies the use of InfoZip data compression.
DEFAULT
VALUES
Infozip (Commented out).
SCOPE
Site preference.

IDSM_do_not_resend_up_to_date_file
DESCRIPTION
Determines whether dataset attachments that are up-to-date are retransmitted
during a re-import. For example, when a user re-imports a dataset with an
associated file that has not been modified this preferences determines if the
associated file is retransmitted to the database, or whether the copy in the local
database is used instead. This preference prevents retransmitting up-to-date files
whether they are being re-imported or distributed with the data_share utility.
Note
Up-to-date files are never retransmitted when transferring site ownership of a
previously replicated dataset, regardless of this preference’s settings.
Warning
Attachments are not retrieved if your site uses this preference but does not
adequately synchronize import export records (IXRs). For example, a dataset
and attachment are replicated as part of an item. Then the item is deleted. A
user needs the dataset again, so searches for the dataset, locates the master
copy and re-imports it. If the data_sync utility is not run with the -verify
argument (which deletes the IXRs of objects whose replicas do not exist at
the remote sites), the new replica of the dataset does not have the original
attachment.
VALID
VALUES
TRUE Prevents the retransmission of up-to-date files.
FALSE Allows the retransmission of up-to-date files.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IDSM_dsa_sites_permitted_to_push_admin_data
DESCRIPTION
Defines the remote sites that are permitted to distribute system administration data
to the local site. This enforces site-level security; if a remote site is not defined in this
preference, that site cannot perform distributed system administration functions
that affect the local site.
This is the first preference to be checked whenever a remote site tries to send system
administration data to the local site. If this initial check results in a rejection of the
request, the other distributed system administration preferences are not checked.
VALID
VALUES
One or more strings; each string must be a valid Teamcenter site name.

DEFAULT
VALUES
None.
SCOPE
Site preference.
IDSM_dsa_notification_email_address
DESCRIPTION
Determines which administrators are notified by e-mail when system administration
data (such as organization data, relation types, revision rules) is received from a
remote site with the dsa_util utility.
VALID
VALUES
e-mail address, separated by a semicolon.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IDSM_exclude_unpublished_components
DESCRIPTION
Prevents automatic replication of unpublished components when a published
assembly is replicated.
This preference can be used only in conjunction with remote imports; it is not used
when you choose Tools→Export→Objects from the My Teamcenter menu to export
components.
VALID
VALUES
TRUE Unpublished components are not included when you perform a
remote import of a published assembly and the Include Entire
BOM command is enabled.
FALSE All components—published and unpublished—are included.
DEFAULT
VALUES
SCOPE
Site preference.

IDSM_ft_buffer_kb
DESCRIPTION
Sets the size of the network send and receive buffers in kilobytes. The maximum
default is 64K for traditional TCP implementations and is adequate for the majority
of users.
Users with extremely high-performance networks may want to increase this setting.
On some operating systems, you may need to enable the RFC1323 (Large Windows)
TCP feature to increase buffers beyond the default.
Calculate the optimum buffer size by multiplying the bandwidth by the delay.
Typically, the peak bandwidth of a network link is expressed in megabits per second
(Mbit/s). For example, a T1 line is rated at 1.544 Mbits/s. The round-trip delay for
a link can be measured with a trace route, and for WAN links is typically between
50 m/sec and 250 m/sec.
For example, a 200 m/sec delay, 2 Mbits/s path, the bandwidth delay product
is 400 Kbit/s, or 50 Kbytes/s. In this example, for optimal performance, set the
IDSM_ft_buffer_kb site preference to at least 50.
VALID
VALUES
Size of network send/receive butters in kilobytes.
DEFAULT
VALUES
64K (Commented out)
SCOPE
Site preference.
IDSM_ft_client_timeout
DESCRIPTION
Sets the amount of time, in seconds, that the client waits for file transfer connections
to respond before terminating the request.
VALID
VALUES
A positive integer.
DEFAULT
VALUES
30 (Commented out).
SCOPE
Site preference.
IDSM_ft_get_port_number_from_services
DESCRIPTION
Determines where the IDSM retrieves the TCP/IP port number.

VALID
VALUES
TRUE Overrides the IDSM_ft_port_number preference setting and
instructs the IDSM to look up the TCP/IP port number in the
/etc/services file for the service named idsmft. On Windows,
the file is located at system32\drivers\etc\services.
FALSE Does not override the IDSM_ft_port_number preference
setting.
DEFAULT
VALUES
FALSE (Commented out).
SCOPE
Site preference.
IDSM_ft_port_number
DESCRIPTION
Specifies the TCP/IP port number to use for file transfers. Must be different from the
one in use for IDSM and ODS, and must not conflict with other registered system
services.
Siemens PLM Software recommends the default setting be changed to an unused
port number in the reserved port range. Contact your network administrator for
this information.
VALID
VALUES
Valid port number.
DEFAULT
VALUES
47953 (Commented out).
SCOPE
Site preference.
IDSM_ft_server_timeout
DESCRIPTION
Sets the amount of time in seconds that the client and server wait for file transfer
connections to respond before giving up.
VALID
VALUES
A positive integer.
DEFAULT
VALUES
30 (Commented out).
SCOPE
Site preference.

IDSM_ft_use_rpc_mode
DESCRIPTION
Determines which file transfer mode is used.
VALID
VALUES
TRUE Forces the use of the original Classic File Transfer mode. This
mode is a slower remote procedure call (RPC) based transfer
mode.
FALSE Does not force the use of the original Classic File Transfer
mode.
DEFAULT
VALUES
SCOPE
Site preference.
IDSM_permitted_checkout_sites
DESCRIPTION
Defines which remote sites are authorized to check out objects owned by the local
site. If not defined, no site is allowed to checkout any object from this site.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
IDSM_permitted_checkout_users_from_site_<sitename>
DESCRIPTION
Defines which user IDs from the sites specified by the
IDSM_permitted_checkout_sites site preference are authorized to transfer
ownership of objects owned by the local site.
If this preference is not defined, all users from a site defined by the
IDSM_permitted_checkout_sites site preference can perform remote checkouts of
objects owned by the local site.
Note
Defining the TC_check_remote_user_priv_from_sites preference overrides
this preference.

VALID
VALUES
One or more strings; each string must be a valid Teamcenter user ID.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IDSM_permitted_sites
DESCRIPTION
Lists which sites can access your data via the IDSM server.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
IDSM_permitted_transfer_sites
DESCRIPTION
Defines which sites are authorized to transfer ownership of objects owned by the site
served by an IDSM server. If not defined, no site is allowed to transfer ownership of
any object from this site.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
IDSM_permitted_transfer_users_from_site_<sitename>
DESCRIPTION
Defines which user IDs from the sites specified by the
IDSM_permitted_transfer_sites site preference are authorized to transfer
ownership of objects owned by the site served by an IDSM server.

Note
this preference.
VALID
VALUES
DEFAULT
VALUES
None. If not defined, all users from the remote site are authorized to
transfer data from the local site, provided the site is defined in the
IDSM_permitted_transfer_sites site preference.
SCOPE
Site preference.
IDSM_permitted_users_from_site_<sitename>
DESCRIPTION
Defines which user IDs from the sites specified by the IDSM_permitted_sites site
preference are authorized to replicate data owned by the site served by an IDSM
server.
Note
this preference.
VALID
VALUES
DEFAULT
VALUES
None. If not defined, all users from the remote site are authorized to replicate data
from the local site, provided the site is defined in the IDSM_permitted_sites site
preference.
SCOPE
Site preference.
IDSM_proxy_client_alternate_proxy_host_for
DESCRIPTION
Allows proxy clients to optionally specify an alternate proxy host. If the initial
communication with the primary proxy host fails, the request is automatically sent
to the alternate proxy host.
VALID
VALUES
IDSM_proxy_client_alternate_proxy_host_for_gmproxy1= gmproxy2
gmproxy1 is the regular proxy host node name and gmproxy2 is the node name of
the alternate proxy host.

Alternatively, an IP address can be used instead of the node name. The node name
entry should match the entry for the node name in the site definition database. If
the IP address is used in the database, the IP address should also be used in this
preference
DEFAULT
VALUES
None.
SCOPE
Site preference.
IDSM_proxy_server_type
DESCRIPTION
Determines whether proxy server mode is available for the IDSM. A valid value
enables the proxy server mode. When not set, the proxy server mode is disabled.
VALID
VALUES
Relay Enables relay proxy server mode.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IDSM_restricted_sites
DESCRIPTION
Lists which sites cannot access your data via the IDSM server.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ITEM_autopublish
DESCRIPTION
Enables or suppresses the automatic publication of all newly created items and
the automatic republication of items when the item ID is modified. Newly created
items are published to the ODS site specified by the ITEM_autopublish_sites
site preference.
When an existing item ID is modified, it is republished only if it is already currently
published and then only to the ODS sites to which it has already been published.

The ITEM_autopublish_sites site preference does not determine which ODS site
to use for republication.
VALID
VALUES
TRUE Enables the automatic publication of all newly created items
and the automatic republication of items when the item ID is
modified.
FALSE Suppresses the automatic publication of all newly created
items and the automatic republication of items when the item
ID is modified.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ITEM_autopublish_ignore_errors
DESCRIPTION
Determines whether to ignore publication errors detected during automatic
publication. When a publication error is detected, any item creations/modifications
known to be successful at that point are retained; failed items can be published
manually at your convenience. This preference requires the ITEM_autopublish
site preference to be set.
Errors caused by invalid ODS site preference settings are ignored by this preference.
Note
Errors due to item creation or modification are not covered by this preference;
the preference applies only to publication errors.
VALID
VALUES
TRUE When automatic publishing is enabled via the
ITEM_autopublish site preference, ignores publication errors
detected during automatic publication.
FALSE When automatic publishing is enabled via the
ITEM_autopublish site preference, publication errors prompt
the system to cancel the item creation or modification.
DEFAULT
VALUES
None.
SCOPE
Site preference.

ITEM_autopublish_sites
DESCRIPTION
Defines the ODS site to which newly created items are published. This preference
requires the ITEM_autopublish site preference to be set.
VALID
VALUES
Accepts a single string as a value. Must be a valid ODS site.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ITEM_id_allow_if_registry_down
DESCRIPTION
Determines if items can be created if the registry server is not available. If the
registry is not active, this preference is ignored.
VALID
VALUES
TRUE Items can be created when the item ID registry server is
unavailable.
FALSE Items cannot be created when the item ID registry server is
unavailable.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
ITEM_id_always_register_on_creation
DESCRIPTION
Determines if item IDs are automatically registered when items are created or
the item ID is changed.
VALID
VALUES
TRUE Automatically registers item IDs to the item ID registry when
items are created or the item ID is changed.
FALSE Does not register item IDs to the item ID registry when items
are created or the item ID is changed.
DEFAULT
VALUES
FALSE

SCOPE
Site preference.
ITEM_id_registry
DESCRIPTION
Activates the item ID registry.
VALID
VALUES
TRUE During item creation (immediately before the new item is
saved to the database), the system checks the item ID registry
for duplicates. Creating the item fails if a duplicate is found.
FALSE The item ID registry is not checked for duplicates while
creating a new item.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
ITEM_id_registry_site
DESCRIPTION
Identifies the site name upon which the item ID registry server is running.
This preference must be set if the item ID registry is active. If the registry is not
active, this preference is ignored.
VALID
VALUES
A single string as a value; each string must be a valid Teamcenter site name.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ITEM_id_unregister_on_delete
DESCRIPTION
Determines if item IDs are automatically unregistered when items are deleted or
the item ID is changed.
VALID
VALUES
TRUE Automatically removes item IDs from the item ID registry
when items are deleted or the item ID is changed.

FALSE Does not remove item IDs to the item ID registry when items
are deleted or the item ID is changed.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
ITEM_relation_types_update_lmd
DESCRIPTION
Determines which relation types cause the update of the last modification date of
the parent object when the secondary object of a class dataset or form is modified,
or if the relation is added/removed from the parent object. If the relation is
added/removed, the last modification date of the parent object is updated regardless
of the class of the secondary object.
VALID
VALUES
relation. Excepting the IMAN_RES_audit and IMAN_RES_checkout relations,
which are not valid values for this preference.
DEFAULT
VALUES
IMAN_master_form
IMAN_specification
IMAN_requirement
The IMAN_master_form, IMAN_specification and IMAN_requirement relation
types are implied entries in this preference and cannot be excluded.
SCOPE
Site preference.
ODS_multiprocess_idle_subprocess_timeout
DESCRIPTION
Defines the length of time a multiprocess subprocess can be idle before it is taken
out of service and terminated.
Used when the Object Directory Services (ODS) is running in multiprocess mode. In
this mode, the ODS maintains a minimum number of subprocesses to respond to
client requests. Additional subprocesses are created on demand, up to a maximum
number (defined by the ODS_multiprocess_max_subprocess_count preference)
when the number of concurrent outstanding client requests exhaust the capacity of
the minimum number of subprocesses.
This preference’s idle timeout setting applies to the subprocesses created on demand.
The timeout is specified in minutes.
VALID
VALUES

DEFAULT
VALUES
10 (Commented out).
SCOPE
Site preference.
ODS_multiprocess_initial_subprocess_count
DESCRIPTION
Determines the number of subprocesses created and logged into the database by the
parent Object Directory Services (ODS) process at startup.
If too few subprocesses are created, remote users may notice a delay due to the time
required to create a subprocess and log on to the database. If too many subprocesses
are created, strain may be placed on system resources, resulting in slow performance.
VALID
VALUES
DEFAULT
VALUES
5 (Commented out).
SCOPE
Site preference.
ODS_multiprocess_max_subprocess_count
DESCRIPTION
Determines the maximum number of precreated subprocesses that can be created by
the parent Object Directory Services (ODS) process.
If the maximum number is too low, remote users may experience noticeable delays
when performing ODS-related operations. If the maximum number is too high,
too many system processes could be created, thus straining system resources and
causing slow performance.
VALID
VALUES
DEFAULT
VALUES
10 (Commented out).
SCOPE
Site preference.
ODS_multiprocess_mode
DESCRIPTION
Enables or suppresses multiprocess Object Directory Services (ODS) operations,
providing improved service when the ODS server process is being monopolized by

remote operations such as report generation and object publication. Multiprocess

mode can also be used to improve performance when service from the ODS server is
slow due to high numbers of operations running at multiple remote sites.
VALID
VALUES
TRUE Enables multiprocess Object Directory Services (ODS)
operations.
FALSE Suppresses multiprocess Object Directory Services (ODS)
operations.
DEFAULT
VALUES
SCOPE
All.
ODS_permitted_sites
DESCRIPTION
Sets which sites can access the Object Directory Services (ODS) database.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter site name.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ODS_proxy_server_type
DESCRIPTION
Determines whether proxy server mode is available for the ODS. A valid value
enables the proxy server mode. When not set, the proxy server mode is disabled.
VALID
VALUES
Relay Enables relay proxy server mode.
DEFAULT
VALUES
None.
SCOPE
Site preference.

ODS_publication_sites
DESCRIPTION
Lists Object Directory Services (ODS) sites that can be used to publish an object
simultaneously. The list serves as the recommended ODS list when publishing
to multiple sites using Commands→Publish→To ODS Publication List menu
commands.
This list plus the default ODS comprise the list of authorized ODS sites to which
users can publish.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter site name
and must be designated as providing ODS.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ODS_restricted_sites
DESCRIPTION
Sets which sites cannot access the Object Directory Services (ODS) database.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ODS_searchable_sites
DESCRIPTION
When set as a site preference, lists which searchable sites appear in the Remote
Sites to Search - Include list in the Find Options dialog box.
When set as a user preference in the client site preference file, defines which
Object Directory Services (ODS) sites are searched during the Teamcenter
session (or until the included list is changed). When combined with the
ODS_searchable_sites_excluded preference, defines a complete list of all possible
ODS sites that can be searched.
VALID
VALUES

DEFAULT
VALUES
None.
SCOPE
ODS_searchable_sites_excluded
DESCRIPTION
Lists the searchable sites that appear in the Remote Sites to Search - Include
list in the Find Options dialog box. The sites in the list are initially placed in the
Excluded list in the Find Options dialog box, but can be individually moved to the
Included list, if desired.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ODS_site
DESCRIPTION
Sets the default Object Directory Services (ODS) site.
VALID
VALUES
A single string as a value; must be a valid Teamcenter site name and must be
designated as the providing ODS site.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ODS_suppress_pubrec_if_no_access
DESCRIPTION
Prevents users at remote sites from knowing about publication records to which
their site has no access, and is used only at Object Directory Services (ODS) sites.
This preference is used only at ODS sites.
For information about ODS sites, see the Multi-Site Collaboration Guide.

VALID
VALUES
TRUE Protected publication records are invisible, (that is, they do not
exist for those users that do not have access). For remote sites
running pre-V6.0 software, protected publication records are
automatically invisible.
FALSE Users at remote sites that do not have read access to a
publication record see an Access Denied message in the object
list window. Find Remote produces this message.
DEFAULT
VALUES
SCOPE
Site preference.
Role-based preferences
You can define default values for certain import/export options based on a user’s
specific role. This is useful in controlling access to certain options, such as the ability
to transfer ownership of an entire assembly.
TC_ownership_export
DESCRIPTION
Prevents a user from transferring site ownership by disabling the Transfer
Ownership button in the Import/Export Options dialog box.
VALID
VALUES
Accepts the value FALSE. If set to any other value, the system ignores the
preference setting.
DEFAULT
VALUES
None.
SCOPE
Role preference.
TC_dataset_vers_export
DESCRIPTION
Prevents a user from exporting all dataset versions (unless transferring site
ownership) by disabling the Include All Versions button in the Import/Export
Options dialog box. This role-based preference applies even when running
command-line utilities such as the item_export or the data_share utility.
VALID
VALUES
Accepts the value FALSE. If set to any other value, the system ignores the
preference setting.

DEFAULT
VALUES
None.
SCOPE
Role preference.
TC_bom_level_export
DESCRIPTION
Controls assembly export options: prevents the entire assembly from being exported;
allows the entire assembly to be exported, but prevents transferring site ownership,
or allows the entire assembly to be exported. This preference does not apply when
running command-line utilities such as the item_export or the data_share utility.
VALID
VALUES
0 Prevents a user from exporting an entire assembly by disabling
the Include Entire BOM button in the Import/Export Options
dialog box.
9999 Prevents a user from transferring site ownership of an entire
assembly by disabling the Include Entire BOM button in
the Import/Export Options dialog box when the Transfer
Ownership button is selected.
Commented Allows the entire assembly to be exported.
DEFAULT
VALUES
Not applicable.
SCOPE
Role preference.
TC_modified_only_export
DESCRIPTION
Prevents a user from turning off the Include Modified Objects Only button in the
Import/Export Options dialog box. This option usually results in better overall
import/export efficiency. This preference does not apply when running command-line
utilities such as the item_export or the data_share utility.
VALID
VALUES
Accepts the value TRUE. If set to any other value, the system ignores the preference
setting.
DEFAULT
VALUES
Not applicable.
SCOPE
Role preference.

TC_relation_export_hidden
DESCRIPTION
Prevents users in certain roles from seeing all available relation types in the
Import/Export Options dialog box. This prevents users from including the
hidden relation types for import/export operations. All hidden relation types are
automatically excluded from the import/export operations.
Note
The EPM-send-target-objects action handler does not support use of the
TC_relation_export_hidden preference. The action handler fails when it
runs the preference. As a workaround, use the -exclude_relation argument
in the EPM-send-target-objects action handler.
VALID
VALUES
A list of valid relation type names, one name per line. The database name, not the
display name, of a relation type must be given. Invalid values in the list are ignored.
DEFAULT
VALUES
None.
SCOPE
Role preference.
TC_always_exclude_dataset_files_on_export
DESCRIPTION
Determines whether the dataset named reference file is excluded from export. Use
this preference in conjunction with the on-demand retrieval of dataset volume
files functionality. This preference affects Multi-Site transfers only and is ignored
by Global Services.
For more information about this functionality, see the Multi-Site Collaboration
Guide.
VALID
VALUES
true Excludes the dataset named reference file from export. This
ensures a given role can never store replica volume data at a
remote site. This setting forces the remote user to retrieve the
volume data from the owning site.
false Does not exclude the dataset named reference file from export.
DEFAULT
VALUES
Not applicable.
SCOPE
Role preference.

TC_<daemon name>_<site ID>_prog_number

DESCRIPTION
Determines which custom remote procedure call (RPC) program number the IDSM
or ODS server runs on the specified site name. This preference is only for use with
a proxy configuration.
Note
The IDSM or ODS server must first be properly configured to run on the
custom RPC program number.
VALID
VALUES
The syntax for this preference is TC_daemon name_site ID_prog_number where
the daemon name is either the ODS or IDSM process (specified in lowercase), the site
ID is the ID of a valid Multi-Site Collaboration site, and the prog_number is a valid
open network computing (ONC) RPC number. For example:
TC_ods_1122334455_prog_number=
536875580
TC_idsm_1122334455_prog_number=
536875590
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_<daemon name>_<site name>_port_number

DESCRIPTION
Allows you to bypass the remote procedure call (RPC) portmapper service (rpcbind).
You may want to avoid using the portmapper service for security reasons. The
portmapper bypass configuration allows you to configure the ODS and IDSM servers
to run on specific port numbers.
VALID
VALUES
The syntax for this preference is TC_daemon name_site name_port_number where
the daemon name is either the ODS or IDSM process (specified in lowercase), and
the site name is the name of a valid Multi-Site Collaboration site. For example:
TC_ods_athens_port_number=
47000
TC_idsm-athens_port_number=
47001
TC_ods_rome_port_number=
57000
TC_idsm_rome_port_number=
57001
DEFAULT
VALUES
None.

SCOPE
Site preference.
TC_<daemon name>_<site name>_prog_number

DESCRIPTION
Determines which custom remote procedure call (RPC) program number the IDSM
or ODS server runs on the specified site name. This preference is not valid for
a proxy configuration.
Note
The IDSM or ODS server must first be properly configured to run on the
custom RPC program number.
VALID
VALUES
The syntax for this preference is TC_daemon name_site name_prog_number where
the daemon name is either the ODS or IDSM process (specified in lowercase), the site
name is the name of a valid Multi-Site Collaboration site, and the prog_number is
a valid open network computing (ONC) RPC number. For example:
TC_ods_athens_prog_number=
536875580
TC_idsm_athens_prog_number=
536875590
DEFAULT
VALUES
None.
SCOPE
Site preference.
Tc_allow_users_edit_pfdata_options
DESCRIPTION
Determines whether options for publishing part family member items and templates
can be modified by general users in the Options dialog box, accessed from the Edit
menu. Users with system administrator privileges can always edit these options
from the Options dialog box, regardless of how this preference is set.
VALID
VALUES
TRUE General users can modify options for publishing part family
member items and templates using the Options dialog box.
FALSE General users cannot modify options for publishing part family
member items and templates using the Options dialog box.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.

TC_altrep_update_lmd
DESCRIPTION
Determines whether the last modified date of a locally owned item revision is
updated when an object with an associated altrep relation is modified.
The last modified date of the parent item is automatically updated as a consequence
of the associated item revision update.
VALID
VALUES
TRUE The last modified date of the item revision is modified when an
object with an associated altrep relation is modified.
FALSE The last modified date of the item revision is not modified
when an object with an associated altrep relation is modified.
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
TC_appref_registry_site
DESCRIPTION
Defines which Object Directory Services (ODS) site is used for all Application
Reference ITK operations. For use with Teamcenter Integration for NX I-deas
migration. When I-deas data is migrated to Teamcenter, these APIs are used to
ensure duplicate GUIDs are not created.
For more information about the Application Reference ITK module, see the
Integration Toolkit Function Reference manual.
Use this preference to direct all API operations to a site other than the default
ODS site (defined by the ODS_site site preference). This allows a separate ODS,
dedicated to item GUIDs, to be setup independent of a regular ODS.
VALID
VALUES
A single string as a value; must be a valid Teamcenter site name.
DEFAULT
VALUES
The value defined in the ODS_site site preference.
SCOPE
Site preference.
TC_assembly_xml_relation
DESCRIPTION
Indicates the relation name that is used to relate the PLM XML data generated
for the assembly.

Modify this preference value if you must have the PLM XML dataset attached using
a specific relation for business needs.
VALID
VALUES
Any existing relation name.
DEFAULT
VALUES
IMAN_Specification
SCOPE
Site preference.
TC_background_object_export_dir
DESCRIPTION
Defines the directory where export data is stored when a background export is
performed using the rich client.
When an interactive, nonremote background export operation is performed using
the rich client, the export data is stored in a subdirectory of the defined directory;
the subdirectory name is defined by the user in the Object Export dialog box. For
example, if the user specifies that the export data be stored in the directory named
my_item100, the background export output is placed in the following directory:
/mydisk/mydir/my_item100
VALID
VALUES
Valid disk drive and directory name.
DEFAULT
VALUES
c:\background_expdir (Commented out).
SCOPE
Site preference.
TC_bom_level_export
DESCRIPTION
Controls assembly export options: prevents the entire assembly from being exported;
allows the entire assembly to be exported, but prevents transferring site ownership,
or allows the entire assembly to be exported. This preference does not apply when
running command-line utilities such as the item_export or the data_share utility.
VALID
VALUES
0 Prevents a user from exporting an entire assembly by disabling
the Include Entire BOM button in the Import/Export Options
dialog box.
9999 Prevents a user from transferring site ownership of an entire
assembly by disabling the Include Entire BOM button in
the Import/Export Options dialog box when the Transfer
Ownership button is selected.

Commented Allows the entire assembly to be exported.

DEFAULT
VALUES
Not applicable.
SCOPE
User preference.
Note
This value is generated by the system and should not be changed.
TC_check_remote_user_priv_from_sites
DESCRIPTION
Determines whether individual remote user privileges are checked before remote
users are allowed to perform the remote operations listed below. Use this preference
to list the remote sites included in this security check. Whenever remote operations
are attempted from any remote site named in this preference, the system evaluates
current AM rules for the IDSM site for the remote user ID. The security check is
implemented on the IDSM server and applies to any remote site named by the local
site.
If this preference is not set, the system applies AM rules only at the site
level. In this situation, only the remote site’s AM privileges are checked
against the AM rule tree of the owning site; access to individual objects at
the owning site are not validated against individual remote user privileges.
In this scenario, the IDSM_permitted_users_from_site_<sitename>,
IDSM_permitted_transfer_users_from_site_<sitename> and
IDSM_permitted_checkout_users_from_site_<sitename> preferences can be
used to determine remote user access to replicate, transfer, and to check in or to
check out remote data. You will override these three preferences if you set the
TC_check_remote_user_priv_from_sites preference.
The remote operations affected are:
• Remote import
• Remote import with transfer of ownership
• Remote check out
• Remote export
• Remote export with transfer of ownership
• Data share utilities
• Pull synchronization
• On demand synchronization

VALID
VALUES
Accepts one or more strings as values. Each string must be the name of a valid
remote site.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_dataset_vers_export
DESCRIPTION
Prevents a user from exporting all dataset versions (unless transferring site
ownership) by disabling the Include All Versions button in the Import/Export
Options dialog box. This role-based preference applies even when running
command-line utilities such as the item_export or the data_share utility.
Note
This preference is a behind-the-scenes preference that is created when a user
selects various import/export commands; it is used internally by the system
and should not be modified.
VALID
VALUES
Defined by system.
DEFAULT
VALUES
Not applicable.
SCOPE
User preference.
TC_default_export_sites
DESCRIPTION
Specifies the list of default export target sites. This list is used to specify the target
sites when exporting using an ITK program. This preference is used only if the
TC_USE_DEFAULT_EXPORT_SITES environment variable is defined and set
to any value.
Note
This preference is not used with interactive Teamcenter and is intended only
for compatibility with ITK programs.
VALID
VALUES
Any valid site IDs.

DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_directly_transferable_classes
DESCRIPTION
Prevents any attachment of a replicated item from being transferred independent of
the item. This prevent users replicating items containing attachments, then remote
importing the attachments with a transfer of ownerships which prevents other
users from further replicating the item because ownership of the item is no longer
consistent. This situation can also cause synchronization problems.
To prevent direct transfer of ownership of all classes of objects except items and item
revisions, set this preference to Item. To enable direct transfer of other classes, such
as Folder, add the Folder class as a value.
VALID
VALUES
Accepts one or more strings as values; each string must be a valid Teamcenter object
class.
DEFAULT
VALUES
None; all classes can be transferred.
SCOPE
Site preference.
TC_disallow_release_status_on_replica
DESCRIPTION
Specifies whether replicas are allowed to be released (have a release status).
VALID
VALUES
true Prevents replicas from being released.
false Allows replicas to be released (have a release status).
DEFAULT
VALUE
false
SCOPE
Site preference.
TC_disallowed_replica_relations
DESCRIPTION
Prevents adding local attachments to replicas. Without this preference,
relation types other than IMAN_specification, IMAN_requirement and

IMAN_master_form can be used to attach files to replica items and item revisions.
This makes it possible for users to attach important data to the replica even though
the attachment is strictly local data that cannot be synchronized to other sites. This
can be unacceptable, especially when the attachments are UG Altreps.
Use this preference to prevent the attachment of manifestations, references, and UG
Altreps to replica items and item revisions.
VALID
VALUES
IMAN_manifestation Prevents the attachment of manifestations to replica items
and item revisions.
IMAN_reference Prevents the attachment of references to replica items and
item revisions.
IMAN_UG_altrep Prevents the attachment of UG Altreps to replica items
and item revisions.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_do_not_insert_imported_objects_into_folder
DESCRIPTION
Determines whether imported objects are added to the user’s home folder. This
preference affects imported objects pushed to a specific user at a remote site and
objects imported by the user using the item_import utility.
In situations where the home folder contains thousands of objects, set this preference
to TRUE to improve performance.
VALID
VALUES
TRUE Imported objects are not inserted into the specific user’s home
folder. Objects are stored in the database with no reference to
any folder. To locate the imported objects, users must search
the database.
FALSE Imported objects are inserted into the specific user’s home
folder.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.

TC_EMAIL_AFTER_BACKGROUND_REMOTE_IMPORT
DESCRIPTION
Controls whether an e-mail notification is sent after completion of a background
remote import operation.
The e-mail address must be defined in the person object of the user who started the
remote import. Otherwise, an e-mail is not sent.
VALID
VALUES
TRUE An e-mail notification is sent after completion of a background
remote import operation.
FALSE An e-mail notification is not sent after completion of a
background remote import operation.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
Tc_export_pfmember_replica
DESCRIPTION
Determines whether part family member replicas can be exported, or remote
imported, from a remote site to another remote site. This preference applies when
exporting or remote importing assemblies containing the part family member replica
components.
VALID
VALUES
TRUE Allows the export of part family member replica components.
FALSE Does not allow the export of part family member replica
components.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
TC_external_app_reg_url
DESCRIPTION
Contains the URL for of the Application Registry Web application (WAR file)
deployment. This value is required to enable Teamcenter-to-Teamcenter remote
inbox functionality.
For information more about installing and deploying the Application Registry Web
application, see the Teamcenter Interoperability guide. Teamcenter administrators

with valid WebKey accounts can access the Teamcenter Interoperability guide at
the following location:
http://support.ugs.com/docs/tc_eng/8/en/tss00004.pdf
VALID
VALUES
A single string as a value representing the URL of the ApplicationRegistry.war
file This must be in the following format:
http://appserver-host:port-number/ApplicationRegistry
DEFAULT
VALUES
None
SCOPE
Site preference.
TC_follow_ownership_chain_max_site_count
DESCRIPTION
Sets a limit on the number of sites that are queried before a replica’s owner is
designated as unknown. When the site known as the owning site returns a new
owning site, the report function queries the new owning site for the replica’s state.
This activity continues until the owning site returns the replica’s state or the value
set in the preference is reached. When the limit is reached the function checks the
TC_on_demand_sync_broadcast_mode preference to determine whether to use
broadcast mode or to designate the ownership as unknown.
VALID
VALUES
You may use any integer value up to the number of known sites.
No limit Specifies Multi-Site shall continue to query for the replicas
owner until all known sites are queried.
DEFAULT
VALUES
No limit
SCOPE
Site preference.
TC_force_remote_sites_exclude_files
DESCRIPTION
Determines if the exporting site sends replica files to the file server cache (FSC) or
stores it in the volume. The exporting site interrogates the importing site for the
this preference value. Therefore, this preference impacts the exporting site only for
online cases.
VALID
VALUES
TRUE Stores the replica files in the FSC.
FALSE Stores the replica files in the volume.

DEFAULT
VALUE
FALSE
SCOPE
Site preference.
NOTES
• The TC_force_remote_sites_exclude_files preference does not override the
display of any options in the rich client. It is a silent override.
• This preference must be set at the importing site.
TC_hub_groups
DESCRIPTION
Defines replication behavior for sharing data via Multi-Site Collaboration hubs. The
replication behavior is managed by assigning hub clients (sites connected to a hub
for data sharing purposes) to arbitrary hub groups.
The following rules govern behavior of hub group memberships. Given the following
example:
TC_hub_groups=
Company 1:partner
Company 2:partner
Company 3:supplier
Company 4:supplier
• When the site importing from the hub, and the real owning site of the replica
being imported from the hub, are in the same hub group, then the requesting
site receives its copy directly from the real owning site. In the above example,
assume Company 1 sends a replica of Item 1 to the hub. If Company 2 replicates
Item 1 from the hub, the hub does not send Item 1 to Company 2, but redirects
the request to Company 1 because Company 1 and Company 2 are in the same
hub group.
This behavior applies to components when importing a whole assembly. However,
for Company 2 to automatically receive components owned by Company 1, the
Include Distributed Components import/export command must be selected;
otherwise, the components owned by Company 1 are stubbed at Company 2.
• When the site importing from the hub and the real owning site of the replica
being imported from the hub are in different hub groups, then the requesting site
receives its copy from the hub (which is normal hub replication behavior). In the
above example, assume that Company 1 sends a replica of Item 1 to the hub. If
Company 3 tries to replicate Item 1 from the hub, the hub sends a replica of Item
1 to Company 3 because Company 1 and Company 3 are in different hub groups.
• When publishing a replica that resides on the hub when the owning site of the
replica and the target ODS are in the same hub group, the publication is not
allowed. If the owning site and the target ODS are in different hub groups, the
publication is allowed.
In the above example, assume each site has its own ODS that is accessible from
the hub. Also assume that Company 1 sends a replica of Item 1 to the hub. If

a user logged onto the hub tries to publish Item 1 to the ODS of Company 2
the publication is not allowed because Company 1 and Company 2 are in the
same hub group. Presumably, Company 1 and Company 2 are already sharing
data directly with each other and there is no need to share replicas via the hub.
Alternatively, if the user is logged onto the hub and tries to publish Item 1 to
the ODS of Company 3, then the publication is allowed. This enables Company
1 to search Company 3’s ODS and still receive its replicas from the hub and
not from Company 3.
VALID
VALUES
Accepts one or more strings as values. Define the preference only in the hub
database, using the following format:
TC_hub_groups=
site1:hub group1
site2:hub group2
site3:hub group3
Where site is the name of the hub client site. Do not enter the hub site itself as
a value.
And where hub group is a user-assigned name (maximum 32 characters) used for
grouping client sites; such customer-defined grouping is the suggested method
of managing replication and publication behavior for data shared via Multi-Site
Collaboration hubs.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_identify_plmxml_import_dataset
DESCRIPTION
Specifies the relation name, dataset type, and the named reference that identifies
the dataset used to parse the named reference PLM XML file and identify the item
revisions to be imported.
VALID
VALUES
Note
Although this preference accepts multiple string values, this to allow
importing any PLM XML file. For use with controlled replication of structured
context objects, this preference must be a single string containing the dataset
type, relation name, and named reference type.
Multiple string values delimited by colons (:) representing any existing dataset type,
relation name, and named reference type in the following format:
<dataset-type>:<relation>:<named-reference—type>
If a named reference type is not specified, ConfiguredAssembly is used.

DEFAULT
VALUES
DirectModelAssembly:IMAN_reference:ConfiguredAssembly
SCOPE
Site preference.
RESTRICTIONS
All values in the preference must exist in the Teamcenter database.
NOTES
Modify this preference value when the attached PLM XMLL dataset must be
processed for import using a specific relation, dataset type, and named reference
for your business needs.
TC_idsm_client_def_timeout
DESCRIPTION
Sets the basic timeout interval, in seconds, before network nodes (clients) attempting
to connect to the IDSM terminate the request. This timeout value is used for all
subsequent IDSM requests.
VALID
VALUES
Single numerical value. Siemens PLM Software recommends 300.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_idsm_client_initial_timeout
DESCRIPTION
to connect to the IDSM terminate the request. This timeout value is used for the
initial request to the IDSM; this may take longer than subsequent requests.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_idsm_proxy_server_site_table
DESCRIPTION
Maps the target site ID with its real node name so that the proxy server can redirect
a requesting site’s first remote procedure call (RPC) message to the target site.
VALID
VALUES
This preference must list all sites (both client sites and server sites) that use the
proxy host. This list provides the information needed to map site IDs to their real
node names. The list is also used to discriminate against clients that are not
authorized to use the proxy host. The proxy denies access to any requesting site
not on the site table list. For example:
TC_idsm_proxy_server_site_table=
Site 1 ID:real-node-name-for-Site 1
Site ID is the site ID of either an internal or external site that uses the proxy host
and real-node-name-for-Site is the actual node name for the site ID.
The IP address can be used instead of the node name.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_ie_error_report
DESCRIPTION
Determines whether a failure report is created. This preference is automatically
set by the system when users select the Save Options As Default option in the
Synchronization Preferences dialog box.
Tip
While it is possible for users to manually set this preference through the
Options dialog box accessed from the Edit menu, or for administrators to
manually edit the tc_preferences.xml file, this is not the suggested practice.
The dialog box allows users to perform on-demand synchronization (as opposed to
administrative-based synchronization using utilities, or automatic synchronization
which only occurs when the master object is modified.) This functionality provides
users with immediate visual confirmation that the synchronization has succeeded
or failed. Access the dialog box by choosing Multi-Site Collaboration→Synchronize
from the Tools menu, or right-clicking on object and choosing Multi-Site
Synchronization from the shortcut menu.
For more information about this functionality, see the Rich Client Interface Guide.
VALID
VALUES
TRUE A failure report is generated.

FALSE A failure report is not generated.

DEFAULT
VALUES
FALSE
SCOPE
User preference.
TC_master_locale_<site_name>
DESCRIPTION
Specifies the master language for the given site defined in the site pane of the
Organization application. This language is used as the locale for exports to the site
or as the locale when importing from the specified remote site to the local site.
This preference must be set for all monolingual sites in a Multi-Site environment
that also contains multilingual sites. This includes monolingual Teamcenter 8.2
sites and sites that are running pre-Teamcenter 8.2 versions.
VALID
VALUES
Accepts the standard Java language codes consisting of a two-character language
string and a two-character country string separated by an underscore character.
Each string must be one of the following codes indicating the desired locale:
cs_CZ
de_DE
en_US
es_ES
fr_FR
it_IT
ja_JP
ko_KR
ru_RU
zh_CN
zh_TW
DEFAULT
VALUE
None.
SCOPE
Site preference.
TC_modified_only_export
DESCRIPTION
Prevents a user from turning off the Include Modified Objects Only button in the
Import/Export Options dialog box. This option usually results in better overall
import/export efficiency. This preference does not apply when running command-line
utilities such as the item_export or the data_share utility.

Note
selects various import/export options; it is used internally by the system and
should not be modified.
VALID
VALUES
Defined by the system.
DEFAULT
VALUES
Not applicable.
SCOPE
Role preference.
TC_ods_client_extra_attributes
DESCRIPTION
Specifies and describes extra attributes of an object being published that you want
stored in the publication record. Only string attributes can be specified. The
attribute must have an initial value.
When adding custom attributes to the publication record, you may want to populate
these extra attributes when an object is published. For example, a new security
level attribute is added to the publication record and you want to specify where
the publication code retrieves the security information associated with the object
being published.
Use this preference for attributes that are part of the object’s extended attributes (or
any attributes from the Master form, if the object is an item or item revision).
Note
When the custom attribute is not part of the object or its master form,
you must implement a user exit to populate the custom publication record
attributes.
VALID
VALUES
Accepts multiple strings as values. Each string must be in the following format:
class-name::object-POM-attribute:pub-record-POM-attribute:option
class-name Specifies the name of the class that defines the

po_pom_attr_name attribute. This is required only
if po_pom_attr_name is used in multiple classes,
in which case you must qualify the attribute name.
This entry is optional and is normally not used.
object-POM-attribute Specifies the POM name of the extra nonarray string
attribute of the object being published. This should
either be part of the class definition of the object or
part of its master form (for items and item revisions).
This entry is required.

pub-record-POM-attribute Specifies the POM name of the extra nonarray string

attribute of the publication record class where the
value of po_pom_attr_name is stored. This should
be part of the publication record class definition at
both client and server sides. This entry is required.
Note
This attribute name cannot start with pubr,
which is reserved for internal use.
option Indicates whether an extra attribute is mandatory or

not. To indicate that an extra attribute is mandatory,
set the option value to MANDATORY. This is an
optional entry; if given, the attribute is assumed to be
optional. This value may also be set to EXTERNAL
to indicate that the attribute is not published
from this site but should be returned by a search
operation. In this case, the po_pom_attr_name
should be same as pr_pom_attr_name.
For example:
form_attr1:security:MANDATORY
immutable:immutable:EXTERNAL
DEFAULT
VALUES
None.
Note
If left undefined, no extra attributes are published through preference
settings. Publications of extra attributes can still be performed through the
USER_ods_client_publish_extra_attributes user exit.
SCOPE
Site preference.
TC_ods_client_def_timeout
DESCRIPTION
to connect to the Object Directory Services (ODS) terminate the request. This
timeout value is used for all subsequent ODS requests.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_ods_client_initial_timeout
DESCRIPTION
to connect to the Object Directory Services (ODS) terminate the request. This
timeout value is used for the initial request to the ODS; this may take longer than
subsequent requests.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_ods_proxy_server_site_table
DESCRIPTION
Maps the target site ID with its real node name so that the proxy server can redirect
a requesting site’s first remote procedure call (RPC) message to the target site.
VALID
VALUES
This preference must list all sites (both client sites and server sites) that use the
proxy host. This list provides the information needed to map site IDs to their real
node names. The list is also used to discriminate against clients that are not
authorized to use the proxy host. The proxy denies access to any requesting site
not on the site table list. For example:
TC_ods_proxy_server_site_table=
Site ID is the site ID of either an internal or external site that uses the proxy host
and real-node-name-for-Site is the actual node name for the site ID.
The IP address can be given instead of the node name.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_on_demand_sync_broadcast_mode
DESCRIPTION
Controls the report function’s query scope when the site known by the current site as
the owning site denies ownership.

VALID
VALUES
TRUE Queries all known sites to find the owner (broadcast mode).
FALSE Performs sequential queries to sites in the ownership
chain until it reaches the limit designated by the
TC_follow_ownership_chain_max_site_count preference.
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
TC_ownership_export
DESCRIPTION
Prevents a user from transferring site ownership by disabling the Transfer
Ownership button in the Import/Export Options dialog box.
Note
selects various import/export commands; it is used internally by the system
and should not be modified.
VALID
VALUES
Defined by system.
DEFAULT
VALUES
Not applicable.
SCOPE
User preference.
TC_plmxml_import_item_filter
DESCRIPTION
Specifies a property and its associated value used to prevent certain not up-to-date
item revisions from being imported during controlled replication. If this preference
is not set, all item revisions are imported.
VALID
VALUES
Multiple string values delimited by colons (:) representing any BOMLine property
used as the filtering value in the following format:
<identifier>:<value>
If multiple values are specified for the same property, the first value processed is
used.

DEFAULT
VALUES
None
SCOPE
Site preference.
NOTES
For the GM Overlay, the preference is set to bl_item_object_type:CORP_vehicle.
TC_plmxml_sync_dataset
DESCRIPTION
Specifies the relation name, dataset type, and the named reference that must be
used to create datasets using the existing PLM XML file. Also, relates the PLM XML
to the structure context object (SCO), or root item revision of a configured assembly,
for which it is generated.
VALID
VALUES
String value delimited by colons (:) representing any existing dataset type, relation
name, and named reference type in the following format:
<dataset-type>:<relation>:<named-reference—type>
If a named reference type is not specified, ConfiguredAssembly is used.

DEFAULT
VALUES
DirectModelAssembly:IMAN_reference:ConfiguredAssembly
SCOPE
Site preference.
RESTRICTIONS
All values in the preference must exist in the Teamcenter database.
NOTES
Modify this preference value when the PLM XML ataset must be attached using a
specific relation, dataset type, and named reference for your business needs.
TC_post_export_script
DESCRIPTION
Automatically compresses export data using the standard_post_export_script.pl
script when a user performs a local export operation using any of the following
methods:
Object Export command
item_export utility
Customized ITK program that exports objects via OBJIO functions
If this preference is not defined, no compression occurs.

Note
This script does not apply during remote export, which employs a different
compression/decompression method.

VALID
VALUES
Complete path name of script. If only the script name is given, the script is assumed
to be stored in the TC_BIN directory.
DEFAULT
VALUES
standard_post_export_script.pl (Commented out).
SCOPE
Site preference.
TC_pre_import_script
DESCRIPTION
Automatically decompresses export data using the
standard_post_export_script.pl when a user performs an import operation
using any of the following methods:
Files→Import→Objects command
item_export utility
Customized ITK program that exports objects via OBJIO functions
If this preference is not defined, no decompression occurs.

Note
This script does not apply during remote import, which employs a different
compression/decompression method.
VALID
VALUES
Complete path name of script. If only the script name is given, the script is assumed
to be stored in the TC_BIN directory.
DEFAULT
VALUES
standard_post_export_script.pl (Commented out).
SCOPE
Site preference.
Tc_preserve_replica_pfmember_ownership
DESCRIPTION
Determines whether part family members created at a site, which are based on a
replica part family template, is owned by the master site or the local site. This
preference is applicable when creating part family members from Teamcenter
Integration for NX.
VALID
VALUES
TRUE Part family members are created with the same site ownership
as that of their template.
FALSE Part family members are created with the local site ownership.

DEFAULT
VALUES
TRUE
SCOPE
Site preference.
Tc_publish_pfdata_with_assemblies
DESCRIPTION
Determines how part family data is published when publishing assemblies. This
preference can also be set by system administrators in the Options dialog box,
accessed from the Edit menu. General users can set this preference from the
Options dialog box only if the Tc_allow_users_edit_pfdata_options preference is
set to TRUE.
Note
This preference is effective only when publishing assembly level items with
the include BOM option.
VALID
VALUES
Members Publishes part family member components in the assembly.
Templates Publishes part family templates rather than the part family
member components in the assembly.
Both Publishes both part family member components and part
family templates in the assembly.
None Publishes neither part family member components nor part
family templates in the assembly.
DEFAULT
VALUES
Members
SCOPE
All.
Tc_publish_pfmembers_with_pftemplate
DESCRIPTION
Determines whether to publish related part family member items when
publishing part family template items. This preference can also be set by
system administrators in the Options dialog box, accessed from the Edit menu.
General users can set this preference from the Options dialog box only if the
Tc_allow_users_edit_pfdata_options preference is set to TRUE.
Note
This preference is effective only when publishing part family template items.

VALID
VALUES
TRUE Publishes the corresponding part family member items.
FALSE Does not publish the corresponding part family member items.
DEFAULT
VALUES
FALSE
SCOPE
All.
Tc_publish_pftemplate_with_pfmember
DESCRIPTION
Determines whether to publish corresponding part family templates when
publishing part family member items. This preference can also be set by
system administrators in the Options dialog box, accessed from the Edit menu.
General users can set this preference from the Options dialog box only if the
Tc_allow_users_edit_pfdata_options preference is set to TRUE.
Note
This preference is effective only when publishing part family member items.
VALID
VALUES
TRUE Publishes the corresponding part family templates.
FALSE Does not publish the corresponding part family templates.
DEFAULT
VALUES
FALSE
SCOPE
All.
TC_publishable_classes
DESCRIPTION
Defines Teamcenter classes that can be published to the Object Directory Services
(ODS) site.
VALID
VALUES
One or more strings. Each string must be one of the following Teamcenter class
names or None.
Item
Dataset
Form
Folder

If the preference is not defined, only items can be published. If set to a single
value of None, publication is disabled; other Multi-Site Collaboration operations
can still be performed.
DEFAULT
VALUES
Item (Commented out).
SCOPE
Site preference.
TC_reference_update_lmd
DESCRIPTION
updated when an object with an associated reference relation is modified.
VALID
VALUES
object with an associated reference relation is modified.
FALSE The last modified date of the item revision is not modified when
an object with an associated reference relation is modified.
DEFAULT
VALUES
SCOPE
Site preference.
TC_rendering_update_lmd
DESCRIPTION
updated when an object with an associated rendering relation is modified.
VALID
VALUES
object with an associated rendering relation is modified.
FALSE The last modified date of the item revision is not modified when
an object with an associated rendering relation is modified.
DEFAULT
VALUES
SCOPE
Site preference.

TC_relation_export_on_transfer
DESCRIPTION
Determines which relation types are included when an object is exported/imported
regardless of whether the export is a replica or with transfer of ownership.
If the exporting site and the importing site have conflicting rules, the rule at the
exporting site prevails. For example, if the importing site does not require the
manifestation relation but the exporting site does, manifestations are included.
Caution
Relations that are in this preference override relations that are also included
in the TC_relation_required_on_transfer preference. Therefore, do not
include a relation type required for ownership transfer in this preference, as
that causes the relation to export as a replica object.
VALID
VALUES
relation. An exception is the IMAN_RES_checkout relation, which is not a valid
value for this preference.
DEFAULT
VALUES
This preference is not defined by default. Therefore, there is no default value.
SCOPE
Site preference.
TC_relation_required_on_export
DESCRIPTION
without transfer of site ownership.
VALID
VALUES
relation. Excepting the IMAN_RES_audit and IMAN_RES_checkout relations,
which are not valid values for this preference.
NONE is also a valid value, indicating there are no required relation types for
export, except for the implied relation types listed above.
DEFAULT
VALUES
IMAN_master_form
IMAN_specification
IMAN_requirement
IMAN_ic_intent_rtype

The IMAN_master_form and IMAN_ic_intent_rtype relation types are implied

entries in this preference and cannot be excluded.
SCOPE
Site preference.
TC_relation_required_on_transfer
DESCRIPTION
with transfer of site ownership.
Caution
Relations that are in this preference are overridden if the relations are also
included in the TC_relation_export_on_transfer preference. Therefore,
do not include a relation type required for ownership transfer in the
TC_relation_export_on_transfer preference, as that causes the relation
to export as a replica object.
VALID
VALUES
relation. Excepting the IMAN_RES_checkout relation, which is not a valid value
for this preference.
NONE is also a valid value, indicating there are no required relation types for
export, except for the implied relation types listed above.
DEFAULT
VALUES
IMAN_master_form
IMAN_specification
IMAN_requirement
IMAN_ic_intent_rtype
The IMAN_master_form, IMAN_ic_intent_rtype and IMAN_RES relation types
are implied entries in this preference and cannot be excluded.
SCOPE
Site preference.
TC_remote_checkin_assy_option
DESCRIPTION
Determines how the system manages newly added components when a remotely
checked out BOM view revision (BVR) or item revision is remotely checked in.
The typical use case is for a remote user to remotely check out a BVR to add new
components owned by the local site (the site adding the component). When the

BVR is remotely checked in, this preference determines how these locally owned
components are handled.
Siemens PLM Software recommends site administrators set this preference as a site
preference. Because this preference as a scope of All, if individual users require
different behavior, they can set a user version of this preference.
VALID
VALUES
0 The components are stubbed upon remote check in. A copy is
not sent to the site that owns the BVR. Instead, at the owning
site, the component is replaced by a POM stub. When the
assembly containing the BVR is opened at the owning site
via Structure Manager, the application prompts the user to
remotely import the component.
1 The components are sent to the owning site as replicas. Site
ownership of the components remains with the site performing
the remote check in.
2 Site ownership of the components is transferred to the site
that owns the BVR. The components at the site performing the
remote check in become replicas.
DEFAULT
VALUES
0
SCOPE
All.
TC_remote_checkin_exclude_relations
DESCRIPTION
Determines which relations prompt the system not to transfer attachments as part
of the replica when a parent object is remotely checked in.
How the system checks in locally attached objects is determined both by this
preference and the relations added to the Include Reference list. The Include
Reference list defines the types of related objects to be imported and exported. The
list displays in the Advanced tab of the Multi-Site Collaboration, Import Remote
section of the Options dialog box, accessed from the Edit menu.
VALID
VALUES
relation.
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_remote_checkin_preserve_replica_owning_user_and_group
DESCRIPTION
Determines how ownership is assigned to replica revisions upon checkin. This
preference must be set at both sites to take effect.
Note
If this preference is set at only the owning site (and not also at the remote
site), the preference acts as if it was not set.
Warning
Do not set this preference to TRUE at the remote site and FALSE at the
owning site. In this situation, the system displays an error.
VALID
VALUES
TRUE The ownership assigned to the replica revision is preserved,
regardless of which user checks in the replica.
For example, consider an item created at Site A by User 1.
A remote export is performed on the item with transfer of
ownership to Site B User 1.
User 1 at Site A then checks out the item, revises Rev1 of the
item, and checks it back in. User 1 at Site A then checks out
Rev2 of the item, changes ownership of the item to User 2 at
Site B, and checks it back in. Both Site A and Site B see the
ownership of Rev2 is User 2.
Note
In this example, User 1 must be a valid user at both
sites and User 2 must be a valid user at both sites.
FALSE The user checking in the replica is assigned ownership,

regardless of any ownership assignments made by the user.
This preserves the concept of unified ownership.
For example, consider an item created at Site A by User 1.
A remote export is performed on the item with transfer of
ownership to Site B by User 1.
User 1 at Site A then checks out the item, revises Rev1 of the
item, and checks it back in. User 1 at Site A then checks out
Rev2 of the item, changes ownership of the item to User 2 at
Site B, and checks it back in. Site A sees the ownership of Rev2
as User 2, but Site B sees the ownership of Rev2 as User 1.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.

TC_remote_checkin_relation_send_as_replica
DESCRIPTION
Determines which relations prompt the system to transfer attachments as part of
the replica when a parent object is remotely checked in.
How the system checks in locally attached objects is determined both by this
preference and the relations added to the Include Reference list. The Include
Reference list defines the types of related objects to be imported and exported. The
list displays in the Advanced tab of the Multi-Site Collaboration, Import Remote
section of the Options dialog box, accessed from the Edit menu.
VALID
VALUES
relation.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_replication_exclude_types
DESCRIPTION
Specifies a list of item types that are ignored by the replication process that uses
PLM XML data contents to individually synchronize objects.
Modify this preference value if you must omit specific item types from replication.
VALID
VALUES
Any existing item type.
DEFAULT
VALUES
There is no default value.
SCOPE
Site preference.
TC_replica_volume
DESCRIPTION
Identifies the volume where replica files are placed upon import. Use to direct all
replica files into a specific volume. This volume does not need to be backed up
because they are replica files, you can retrieve a copy from the owning site if you
lose any of the files. You can also use operating system facilities to determine
which files have not been accessed for a certain period of time, thereby determining
unnecessary replicas.

VALID
VALUES
Single valid volume name.
DEFAULT
VALUES
None.
SCOPE
Typically defined as a site preference. Can be defined as a group or user preference
so that each group or user can define its own replica volume.
TC_retain_group_on_import
DESCRIPTION
Determines group ownership of the import. When importing an object to a site where
the original object’s user and group are not defined, the replicated object’s owning
group is defined as the importing user’s group.
To preserve the replica’s group ownership even when the original owning user is not
defined locally (but the group is defined locally) set to TRUE.
VALID
VALUES
TRUE Retains group ownership of the import when the owning group
of the original object is define locally.
FALSE General rules of replica ownership applies.
DEFAULT
VALUES
SCOPE
Site preference.
TC_stub_dataset_files_after_ownership_transfer
DESCRIPTION
Specifies whether replica files are stubbed at the original owning site when the
ownership is transferred to another site. The Multi-Site transfer of ownership
feature creates full ImanFile objects at the new owning site and adds full operating
system files to the volume. This preference indicates whether the original owning
site has the option to stub the replica ImanFile objects and purge the files from the
volume.
VALID
VALUES
TRUE Allows the replica files to be stubbed at the original owning site.
FALSE Forces the full object files to remain on the original owning
site’s volume.
DEFAULT
VALUE
FALSE

SCOPE
Site preference.
TC_subscribable_replica_classes
DESCRIPTION
Defines the list of WorkspaceObject classes whose replicas can be subscribed to
for update notification. When users subscribe to the Replica Updated event for a
replica object at a replica site, they are notified when the replica is updated due to
re-import or synchronization. The notification is sent only for the objects of classes
defined by this preference.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid workspace object
class, such as Item, ItemRevision, Dataset.
DEFAULT
VALUES
None. When not defined, no subscription functionality for replicas is enabled.
SCOPE
Site preference.
TC_sync_max_assy_level
DESCRIPTION
Defines the maximum assembly level reported when performing synchronization
in Report Only mode from the Synchronization Preferences dialog box. This
preference affects only the number of levels displayed in the report, not the
maximum assembly level synchronized.
This preference is automatically set by the system when users select the Save
Options As Default option in the dialog box.
Tip
While is possible for users to manually set this preference through the
Options dialog box accessed from the Edit menu, or for administrators to
manually edit the tc_preferences.xml file, this is not the suggested practice.
from the Tools menu, or right-clicking on object and choosing Multi-Site
VALID
VALUES
-1 All assembly levels are reported.
Any positive The number of levels specified by the integer is reported.
integer

DEFAULT
VALUES
-1
SCOPE
User preference.
TC_sync_revision_rules
DESCRIPTION
Defines the revision rules which display in the Synchronization Preferences dialog
box. If not defined, all available revision rules appear.
from the Tools menu, or right-clicking an object and choosing Multi-Site
In the dialog box, users select a revision rule from the Revision Rule list. The
selected revision rule is passed to the owning site of the selected component and is
used by the owning site to determine which item revision to synchronize. It is a
required field if the object selected for synchronization is an item.
For more information about this functionality, see the Rich Client Interface Guide.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter revision
rule.
DEFAULT
VALUES
None. If not defined, all available revision rules appear in the revision rule list.
SCOPE
Site preference.
TC_transfer_area
DESCRIPTION
Sets the directory for temporarily storing data during import and export. If not set,
the current working directory is used to store data during import and export.
VALID
VALUES
Full OS path to the directory.
This string can be a single line value, for example:
TC_transfer_area=
/tmp
This string can also contain multiple lines to support a heterogeneous site. In this
case, Teamcenter uses the first valid value for the platform (UNIX or Windows).

Validity is determined by the presence of a backslash (\). For example, where the
Windows path uses C: as the drive letter, the preference is set for both UNIX and
Windows as:
TC_transfer_area=
/tmp
c:\temp
Note
UNC paths are specified with a triple backslash. When the Windows path
is specified in UNC format, the preference for both UNIX and Windows is
defined as:
TC_transfer_area=
/tmp
\\\hostx\share_area
DEFAULT
VALUES
/tmp
Note
Typically, the /tmp directory is a volatile area of the file system. Files in this
directory can be deleted when the system is rebooted. Siemens PLM Software
strongly recommends setting up another permanent transfer directory and
setting this preference to that directory.
SCOPE
Site preference.
TC_truncate_file_name
DESCRIPTION
Determines if truncation of an original file name is necessary. Implement so
Multi-Site Collaboration can transport data between releases.
VALID
VALUES
TRUE Truncates the original file name to the length of 30.
FALSE Does not truncate the original file name to the length of 30.
Only set to FALSE if all sites are running V7.0 or higher.
DEFAULT
VALUES
SCOPE
Site preference.

TC_use_group_admin_as_default_replica_owner
DESCRIPTION
Determines whether the owning user of an imported object is the group administrator
of the owning group when the owning user is not a member of the owning group at
the importing site.
For example: the master copy at the owning site (Site 1) is owned by the user Joe,
in the Design group, and it is imported at Site 2, where Joe is not a member of the
Design group. If this preference is set to TRUE, the system searches the list of
group administrators for the Design group at Site 2, assigning ownership to the first
group administrator in the list.
VALID
VALUES
TRUE Assigns ownership of an imported object to the group
administrator of the owning group when the owning user is not
a member of the owning group at the importing site.
FALSE General rules of replica ownership applies.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
TC_validate_stub_tickets
DESCRIPTION
Determines whether Teamcenter validates stub tickets and has the site where the
associated file was transferred generate a new stub ticket for any found to be invalid.
VALID
VALUES
TRUE Validates stub tickets.
FALSE Does not validate stub tickets.
DEFAULT
VALUE
FALSE
SCOPE
Site preference.
NOTES
The frequency of synchronizing POM_stub objects with owning ImanFile objects is
a determining factor for setting this preference. The overwhelming majority of the
time, Teamcenter can find the file in local whole file cache. Rarely, Teamcenter must
seek the file in the owning site’s volume or in the FSC. There is a chance the file is
absent from the owning site’s volume due to a recently performed ownership transfer
to a third site. To ensure a stub ticket is valid, the Teamcenter site that the file was
transferred to must generate the latest stub ticket, which requires a LAN/WAN trip
to the owning site. The generated ticket can be used to search the file under the local

whole file cache. This sacrifices performance by requiring a LAN/WAN trip to the
owning site to generate the ticket for every POM_stub object.
Data Exchange preferences

Data Exchange provides a solution for various data sharing scenarios including
site data migration, supplier site exchange, Teamcenter offline exchange, and
Teamcenter variant schema exchange.
Use the following preferences to modify the behavior of Data Exchange.
Alt_id_default_idContext_type
DESCRIPTION
Specifies a default IdContext type. This is required for import operations when
the type is not specified by user.
VALID
VALUES
Accepts multiple strings as values. Must be a valid IdContext type.
DEFAULT
VALUES
None.
SCOPE
Site preference.
Alt_id_default_identifier_type
DESCRIPTION
Specifies a default Identifier type. This is required for import operations when the
type is not specified by a user.
VALID
VALUES
Accepts multiple strings as values. Must be a valid Identifier type.
DEFAULT
VALUES
None.
SCOPE
Site preference.
GMS_UID_mapping_dbname_index
DESCRIPTION
Lists the databases for remote Teamcenter Enterprise sites involved in data
exchange. The indices of the databases specified are used for generating unique
object UIDs in PLM XML.

VALID
VALUES
Enter values as instance-name:dbname1, dbname2, for example, svli60:sum501a.
To determine these values, search the Teamcenter Enterprise fmsmaster.xml file for
the accesson id value, for example, accesson id = “rhgtpqksvli60sum501a-aaG”.
Split this value as follows:
1. Drop the last three characters (aaG).
2. In the remaining string, record the last eight characters (ignore any hyphens)
as the dbname value, for this example, sum501a.
3. Record the next six characters as the instance name, for this example, svli60.
DEFAULT
VALUES
None.
SCOPE
Site preference.
GMS_UID_mapping_remote_site_index
DESCRIPTION
Lists the index mapping for remote Teamcenter Enterprise sites involved in data
exchange. The indexes are used for generating unique object UIDs in PLM XML.
VALID
VALUES
Enter values as instance-name:index1, for example, svli60:1. To determine the
instance name, see GMS_UID_mapping_dbname_index.
DEFAULT
VALUES
None.
SCOPE
Site preference.
GS_USER_NAME
DESCRIPTION
Identifies the user permitted logon access to Global Services.
VALID
VALUES
Accepts a single string as a value. Must be a valid user name.
DEFAULT
VALUES
GlobalServicesAdmin
SCOPE
Site preference.

GS_USER_PASSWORD
DESCRIPTION
Identifies the user password required to log onto Global Services.
VALID
VALUES
DEFAULT
VALUES
GlobalServicesAdmin
SCOPE
Site preference.
PDX_pkg_file_name
DESCRIPTION
Specifies the format for the name of the PDX package file when exported from
Teamcenter. The format of the preference value is (all values are optional):
PDX-string:ItemId:RevId:ItemName:TargetSite:TimeStamp
Note
You can use the following keywords in this preference.
• ItemId
• ItemName
• RevId
• TargetSite
• TimeStamp
VALID
VALUES
PDX-string PDX-string is a string constant prefixed to the package file
name of each exported package. You can use this to identify the
package as desired, such as by the originating site.
ItemId Includes the item ID of the exported object as part of the
package file name.
ItemName Includes the item name of the exported object as part of the
package file name.
RevId Includes the revision ID of the exported object as part of the
package file name.
TargetSite Includes the site name the object exported to as part of the
package file name.

TimeStamp Includes the time stamp information at the time the object is
exported as part of the package file name.
Any combination of values is valid. The following are a few examples:
PDX:ItemId:RevId:ItemName:TargetSite
PDX:ItemId:ItemName:TargetSite
ItemId:RevId:ItemName
PDX:ItemId:RevId:ItemName:TargetSite:TimeStamp
Note
Based on the last example, the package file name for the 000303/A Mem_Assy
object package, exported to the Zurich site is:
PDX_00001_A_Mem_Assy_Zurick_4-Feb-2008_18-14-00.pdx
DEFAULT
VALUES
If no value is set, the package file name is based on the ItemName attribute.
For example, for the 000303/A Mem_Assy object package the file name is
Mem_Assy.pdx.
SCOPE
Site preference.
RESTRICTIONS
The keywords are case sensitive and the only keywords supported. Any other values
are treated as constants.
SRM_host_port
DESCRIPTION
Specifies the host and port on which SRMConnect is running.
SRMConnect is part of supplier relationship management data sharing.
VALID
VALUES
Hostname:portnumber
DEFAULT
VALUES
localhost:3000
SCOPE
Site preference.
TC_default_gms_site
DESCRIPTION
Determines the name of the Data Exchange site to be used as the default target site
when performing a remote export. If this preference is not defined, the system uses
the first Data Exchange site found in the database. If no such sites are defined,
the request returns an error.

VALID
VALUES
Accepts a single string as a value. Must be the name of a valid Data Exchange site.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_default_gms_transfer_mode
DESCRIPTION
Defines the default PLM XML transfer mode used for Data Exchange operations.
VALID
VALUES
Accepts a single string as a value. Must be a valid PLM XML transfer mode.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_gms_import_default_transfermode
DESCRIPTION
Specifies the transfer mode used when performing a PLM XML import.
VALID
VALUES
Accepts a single string as a value. Must be a valid PLM XML import transfer mode.
DEFAULT
VALUES
TIEImportDefault
SCOPE
Site preference.
TC_gms_enable_immediate_option
DESCRIPTION
Determines whether users can schedule a Data Exchange request for immediate
execution. (By default, the system schedules requests based on load conditions.) This
is a role-based preference; you can use it to enable the option for users based on role.
VALID
VALUES
TRUE The Immediate check box appears in the various Data
Exchange import and export dialog boxes.
FALSE The Immediate check box does not appear.

DEFAULT
VALUES
FALSE
SCOPE
Role preference.
TC_gms_export_default_transfermode
DESCRIPTION
Specifies the PLM XML transfer mode used when exporting from Briefcase.
VALID
VALUES
Accepts a single string as a value. Must be a valid PLM XML import transfer mode.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_gms_export_transfermode_for_<site_name>
DESCRIPTION
Specifies the export transfer mode for a specific site. If this preference is not set,
the transfer mode specified by the TC_gms_export_default_transfermode
preference is used.
VALID
VALUES
Accepts a single string as a value. Must be a valid PLM XML transfer mode.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_gms_gs_bos_service_url
DESCRIPTION
Specifies the URL for the Global Services business object server.
VALID
VALUES
Accepts a single string as a value. Must be a valid URL.
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_gms_gs_server_url
DESCRIPTION
Specifies the URL of the Global Services Web server location.
VALID
VALUES
Accepts a single string as a value. Must be a valid Web server location.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_gms_gs_uri
DESCRIPTION
Specifies the URI Global Services uses for SOA envelopes.
VALID
VALUES
Accepts a single string as a value. Must be a valid URI.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_gms_monitoring_gui_total_number_of_steps_for_transfer
DESCRIPTION
Specifies the number of steps in the Data Exchange data transfer process. The
progress monitor uses this value to determine the percentage of progress to display.
The standard process has five steps. If the transfer options include notification,
Teamcenter increments the value by 1 to account for the extra step. If you add
custom steps to the process, you must update this value to allow the progress
monitor to display the correct progress percentage.
VALID
VALUES
Any integer.
DEFAULT
VALUES
5
SCOPE
Site preference.

TC_gms_sso_enabled
DESCRIPTION
Determines whether Global Services uses Security Services to provide single sign-on
(SSO) capability. If this preference is not set to true, the following preferences must
be set to provide user credentials for Global Services:
• GS_USER_NAME
• GS_USER_PASSWORD
VALID
VALUES
true SSO is enabled for Global Services.
false SSO is not enabled for Global Services. User ID and password
preferences must be defined so that users can log onto Global
Services.
DEFAULT
VALUES
true
SCOPE
Site preference.
TIE_allow_import_with_different_SML
DESCRIPTION
Specifies whether Teamcenter allows importing a TC XML file that contains a
different site master language from the site master language at importing site.
VALID
VALUES
true or ON Allows import.
false or OFF Does not allow import.
DEFAULT
VALUE
false
SCOPE
Site preference.
NOTES
When this preference is set to true, after import, non-localized attributes in the
importing system can be in languages other than the importing system site master
language.
TIE_exp_pending_object
DESCRIPTION
Determines whether to export a pending object as a full replica or as a stub. When
Data Exchange is performing an export, it sets an export lock for the affected objects

at the beginning of the transfer. If a second export is initiated while a previous

export that contains the same object is pending, the object lock is still set by the
pending transfer. If this preference is set to export pending objects as a stub, it
causes Data Exchange to export the object as a POM_stub object containing only
the object’s identifying information.
Caution
If this preference is set to false (or not set), a pending object that is exported as
a stub can cause a transfer to be incomplete or to fail. To avoid this problem,
set the preference to true.
VALID
VALUES
true Exports the object as a full replica.
false Exports the object as stub.
DEFAULT
VALUE
false
SCOPE
Site preference.
TIE_reference_objects_list
DESCRIPTION
Specifies list of object names and attributes to be processed as reference objects. TC
XML import does not import organizational objects such as User, Group, Role and
Project objects that used for reference purposes only. These objects are searched by
the Data Exchange importer and their values are set in objects created by importer.
For example, the owning_user attribute in the WorkspaceObject object refers to
a User object with a particular ID or name.
VALID
VALUES
Strings delimited by a commas in the following format:
TIE_reference_objects_list=bo_name,bo_attr_name,ref_attr_name
bo_name Name of a Teamcenter business object.

bo_attr_name Name of the attribute on the business object that the importer
must lookup.
ref_attr_name Name of the attribute that references the business object.
For example, to get owning_user and owning_group attribute references:
TIE_reference_objects_list=
User,user_id,owning_user
Group,name,owning_group
DEFAULT
VALUE
None.
SCOPE
Site preference.

TIE_validate_against_xsd
DESCRIPTION
Determines whether the system validates the XML output file against the
Teamcenter PLM XML schema.
VALID
VALUES
true The system validates the XML output file against the
false The system does not validate the XML output file against the
DEFAULT
VALUES
false
SCOPE
Site preference.
PLM XML preferences

Teamcenter uses the PLM XML schema to import and export data in a standard XML
file format. PLM XML provides a solution for exchanging data with applications that
support the PLM XML schema.
Use the following preferences to modify the behavior of Teamcenter import and
export functions for PLM XML data.
PIE_<transfer_mode_name>_process_in_chunks
DESCRIPTION
Specifies which objects unload in batches. Users can set this preference to unload
objects they no longer need in memory to improve performance. This preference
is used in conjunction with the PIE_<transfer_mode_name>_unload_objects
preference.
Users must create a preference for each transfer mode type from which they want
to unload objects, and set the preference with values specifying which object types
are unloaded in batches. For example:
PIE_sampleExport_unload_objects=
all
VALID
VALUES
Accepts the following object types as values. Alternatively, users can
specify all to indicate that all objects defined in the corresponding
PIE_<transfer_mode_name>_unload_objects preference are unloaded in
batches. Value entries are case-sensitive.
ImanItemBOPLine
BOMLine
Item

ItemRevision
Form
Dataset
RecordObject
DEFAULT
VALUES
None.
SCOPE
User preference.
PIE_<transfer_mode_name>_unload_objects
DESCRIPTION
Specifies which objects to unload from memory and in what order. Users can set this
preference to unload objects they no longer need in memory to improve performance.
Caution
If users unload objects, such as BOM lines, needed by other rich client
functions or features, errors might occur. Ensure all objects are saved to the
database before unloading.
Users must create a preference for each transfer mode type from which they want
to unload objects, and set the preference with values specifying object types are
to be unloaded. For example:
PIE_sampleExport_unload_objects=
ImanItemBOPLine
BOMLine
Item
ItemRevision
Caution
These preferences define the processing order of the specified objects and
the forced unloading of the same objects. (The first object listed as a value,
is processed first, the second is processed second, and so on.) If objects are
unloaded in an improper order, the existence of dependent objects cannot be
translated and their child objects are bypassed, even if closure rules specify
traversal of these objects. Users must know which objects can be processed
and unloaded first, and list the objects in the correct order, or errors will occur.
VALID
VALUES
Accepts the following object types as values. Value entries are case-sensitive.
ImanItemBOPLine
BOMLine
Item
ItemRevision
Form
Dataset
RecordObject

DEFAULT
VALUES
None.
SCOPE
User preference.
PIE_allow_import_with_different_sml
DESCRIPTION
Controls the import behavior when the site master language of the exporting site
does not match that of the importing site. By default, if the site master language
in the .xml file does not match the importing site’s site master language, the PLM
XML import is allowed. To deny the import, set the preference value to false.
VALID
VALUES
True Allows PLM XML import if the site master language in the
.xml file does not match the importing site’s site master
language.
False Prohibits PLM XML import if the site master language in
the .xml file does not match the importing site’s site master
language.
DEFAULT
VALUES
True
SCOPE
Site preference.
PIE_Extra_Error_Info_to_Xml
DESCRIPTION
Determines whether to throw an exception on the client side with the body
containing the errors logged in the PLM XML import/export (PIE) log file. Set this to
YES if you want to see the results of a PLM XML import using AIWS.
VALID
VALUES
YES Throws an exception on the client side with the body of the
exception containing the errors logged in the PLM XML
import/export (PIE) log file.
SUCCESS Adds the success elements to the log file in addition to any
errors.
NO Does not log errors or successes.
DEFAULT
VALUES
NO
SCOPE
All.

PIE_IMF_FOR_CAD
DESCRIPTION
Determines whether PLM XML import/export functionality uses the IMF ITK
function, or the ug_clone utility to import/export CAD files from ImanVolume.
VALID
VALUES
YES Uses the IMF ITK function to import/export CAD data files.
NO Uses the ug_clone utility to import/export the following
dataset types: UGMASTER, UGPART, UGALTREP,
UGSCENARIO, and NXSIMULATION.
DEFAULT
VALUES
YES
SCOPE
Site preference.
PIE_transfermode_languages
DESCRIPTION
Specifies a default list of languages that are associated with a transfer mode. These
languages are included when the associated transfer mode is used for export, unless
otherwise excluded by the user.
VALID
VALUES
Values should be organized in the following format:
<TransferMode_name><:><language1, language2, …>.
The language must follow the standard Java locale naming conventions: the locale
2letterlanguage_2LETTERAREA.
For example:
ConfiguredDataExportDefault: en_US, fr_FR
BOMWriterExport: en_US, de_DE, zh_CN
DEFAULT
VALUES
None.
SCOPE
RESTRICTIONS
This preference is valid only during export, so the preference value should only
specify export transfer modes.

PLMXML_continue_on_error
DESCRIPTION
Determines whether import and export operations continue after an error has
occurred.
VALID
VALUES
TRUE The import or export operation continues when there is an
import or export error.
FALSE The import or export operation aborts when there is an import
or export error.
DEFAULT
VALUES
FALSE
SCOPE
User preference.
PLMXML_export_packed_bom_<transfer-mode-name>
DESCRIPTION
Determines whether the assembly should be unpacked before a PLM XML export
using the transfer mode specified in the preference name.
Warning
When you export a packed BOM, you may lose data in the exported XML file.
Therefore, do not import an XML file with a packed BOM into Teamcenter.
Change this preference value only if you plan to use the XML file in a
third-party application and want to improve export performance.
VALID
VALUES
TRUE The assembly remains packed for the PLM XML export.
FALSE The assembly is unpacked before the PLM XML export.
DEFAULT
VALUES
FALSE
SCOPE
User preference.
PLMXML_import_default_password
DESCRIPTION
Defines the password used while importing a new user using PLM XML.
For security reasons, PLM XML does not export passwords to XML files. By default,
during import, new users are created with the user name and password the same.
If strong password preferences are set at the target site, importing users may fail.

If your site uses strong password rules, define the value of this preference with a
password that satisfies your site’s rules. The system imports all user objects with
the password defined by this preference.
Note
Each new user should change their password upon initial logon.
VALID
VALUES
Accepts a single string as a value. Must be a password that meets the importing
site’s password rules.
DEFAULT
VALUES
None.
SCOPE
Site preference.
PLMXML_log_file_content
DESCRIPTION
Determines the amount of information added to the PLM XML translation log.
During large PLM XML translations, full logging can consume significant resources
and generates a large memory footprint. Optimize performance by tuning the log
file behavior through this preference.
Note
The PLM XML translation log is always generated, enabling analysis of
translation performance, and signaling you when the translation is complete.
The minimum amount of information you can tune the system to provide is
the translation header and a list of any errors generated.
VALID
VALUES
basic Logs the translation header and a list of any errors generated.
This setting generates the least overhead for translation
reporting.
summary Logs the translation header, summary, warnings, and a list of

any errors generated.
detailed Logs the translation header, summary, warning, errors, and a

closure rule analysis report. This setting generates the most
overhead for translation reporting.
DEFAULT
VALUES
summary
SCOPE
Site preference.

PLMXML_overwrite_objects_on_import
DESCRIPTION
Determines whether an imported object overwrites an existing version of the same
object at the local site. Only writable properties of the object is overwritten when this
preference is set to YES. The user requires write access for an overwrite to occur.
VALID
VALUES
TRUE The import or export operation continues when there is an
import or export error.
FALSE The import or export operation aborts when there is an import
or export error.
DEFAULT
VALUES
FALSE
SCOPE
User preference.
PLMXML_put_objects_in_newstuff_on_import
DESCRIPTION
Determines whether data imported via PLM XML is automatically stored in the
Newstuff folder.
VALID
VALUES
TRUE After a successful PLM XML import, a folder is created in
the Newstuff folder using the name of the imported .xml
file. The imported objects are copied to that folder. Only the
root objects represented by the traverseRootRefs attribute
of the Header element in the PLM XML file are copied. For
example, when the following test.xml file is imported, objects
pointed to by id2 are copied to the folder named test.xml in
the NewStuff folder:
<Header id="id1" traverseRootRefs="#id2"
transferContext="TestTransferMode"></Header>
FALSE Data imported via PLM XML is not stored in the Newstuff
folder. Data is located using the Search command.
DEFAULT
VALUES
None.
SCOPE
User preference.

PLMXML_put_pie_log_in_syslog
DESCRIPTION
Specifies whether the contents of the PLM XML import/export (PIE) log file is copied
to the syslog file or not. This PIE log file is in the same location as the PLM XML
file of the same name and contains the results of any PLM XML import or export
transaction.
VALID
VALUES
TRUE All messages that are printed to the PLM XML import/export
(PIE) log file are also recorded in the syslog file.
FALSE All messages that are printed to the PLM XML import/export
(PIE) log file are not recorded in the syslog file.
DEFAULT
VALUES
FALSE
SCOPE
User preference.
PLMXML_sdk_threshold
DESCRIPTION
Defines the number of live PLM XML objects that exist at one time before
serialization of the objects occurs. Serialization writes the objects to the disk
then loads them back on command. Because excessive serialization can degrade
performance, Siemens PLM Software recommends you enable serialization only for
larger structures (exceeding a 3 GB process limit) to optimize performance.
VALID
VALUES
Any positive integer, for example, 100000 or 1000000.
DEFAULT
VALUES
None. (No serialization.)
SCOPE
User preference.
PLMXML_use_pre_plm_appname
DESCRIPTION
Determines the Teamcenter product name used during PLM XML export. Use this
preference when exporting PLM XML data between Teamcenter 2007 (or later) and
earlier versions of Teamcenter.
Teamcenter 2007 (or later) PLM XML data writes the product name as Teamcenter
and earlier versions writes the product name as TcEng. During PLM XML export,
the product name is identified for each transfer mode and thus the product name
written for any given transfer mode differs with product versions.

Use this preference to list the transfer modes to be exported to earlier versions of
Teamcenter. The product name will be written as TcEng for the transfer modes
specified as values of this preference, allowing Teamcenter 2007 PLM XML data to
be exported to earlier Teamcenter versions.
For more information about using transfer modes and PLM XML export functionality,
see the PLM XML Export Import Administration Guide.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid transfer mode
name.
DEFAULT
VALUES
None. (The product name is written as Teamcenter during PLM XML export.)
SCOPE
User preference.
TC_export_child_groups
DESCRIPTION
Determines whether child groups are exported along with the selected group during
PLM XML export. Set this preference to OFF to improve performance if groups at
your site contain a large number of child groups.
VALID
VALUES
ON Enables export of child groups when exporting groups using
PLM XML.
OFF Disables export of child groups when exporting groups using
PLM XML.
DEFAULT
VALUES
ON
SCOPE
Site preference.
TC_export_parent_groups
DESCRIPTION
Determines whether parent groups are exported along with the selected group
during PLM XML export. Set this preference to OFF to improve performance when
groups at your site have a large number of parent groups.
VALID
VALUES
ON Enables export of parent groups when exporting groups using
PLM XML.
OFF Disables export of parent groups when exporting groups using
PLM XML.

DEFAULT
VALUES
ON
SCOPE
Site preference.
STEP Translator preferences

The Standard for the Exchange of Product Model Data (STEP) is a platform
independent (neutral) mechanism for representing product information throughout
its entire life cycle.
The Teamcenter/STEP Translator allows you to import product information into the
Teamcenter database and to export Teamcenter data via STEP-compliant physical
files.
Use the following preferences with the optional Information Manager Standard
for the Exchange of Product Model Data Interface (Teamcenter/STEP Translator).
User preferences can be set in Teamcenter’s Options dialog box or via the Export
Object to STEP dialog box.
STEP_<relation_type>
DESCRIPTION
Supports only the STEP AP214. These preferences have names of the relation types
as their values. These values represent a relation type and are used to determine
the Teamcenter and user-defined relation types from the relation_type part of the
preference.
VALID
VALUES
One or more strings; each string must be a valid relation type.
DEFAULT
VALUES
IMAN_specification
SCOPE
Site preference.
STEP_approved_status
DESCRIPTION
Supports only STEP AP214. Sets the defined item type as approved. 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.
VALID
VALUES
One or more strings.
DEFAULT
VALUES
approved

SCOPE
Site preference.
STEP_default_BOMView_type
DESCRIPTION
Serves as an error recovery mechanism that allows assembly import when the
BOMView type cannot be determined because either the frame_of_reference field
has no meaningful name or the name is not in the set of view names.
The STEP processor uses the product_definition_context_frame_of_reference
field to determine the BOMView type.
If the frame_of_reference field has no meaningful name (it is either blank or empty
string), the translator fails to create the BOM view, and the assembly structure is
lost. If the frame_of_reference field entry is a name that is not in the set of view
names and the user does not have permission to create a new view name, the BOM
view and its attendant assembly structure is dropped. In these circumstances, use
this preference to allow the assembly to be imported.
VALID
VALUES
DEFAULT
VALUES
used
SCOPE
STEP_default_datasettype
DESCRIPTION
Supports only STEP AP214. Used to retrieve the default dataset type name when
it cannot be obtained from the Teamcenter database via the dataset tool tag or
inferred from the file extension.
VALID
VALUES
One or more strings; each string must be a valid Teamcenter dataset type name.
DEFAULT
VALUES
Text
SCOPE
Site preference.
STEP_default_item_type
DESCRIPTION
Obtains the default Teamcenter item type. Used as an argument to create an item
entity of Teamcenter, in the database.

VALID
VALUES
DEFAULT
VALUES
Item
SCOPE
Site preference.
STEP_design_specification_pref
DESCRIPTION
Maps Teamcenter dataset types to the STEP design specification classification.
VALID
VALUES
DEFAULT
VALUES
Text
SCOPE
Site preference.
STEP_drawing_pref
DESCRIPTION
Maps Teamcenter dataset types to the STEP drawing classification.
VALID
VALUES
DEFAULT
VALUES
UGPART
SCOPE
Site preference.
STEP_cad_filename_pref
DESCRIPTION
Maps Teamcenter dataset types to the STEP CAD file classification.
VALID
VALUES
DEFAULT
VALUES
UGMASTER
SCOPE
Site preference.

STEP_export_data_format
DESCRIPTION
Sets STEP data format used for this export operation.
VALID
VALUES
AP203
AP214
DEFAULT
VALUES
None.
SCOPE
Site preference.
STEP_export_directory
DESCRIPTION
Sets export (destination) directory when exporting data via the Teamcenter/STEP
Translator. This is where the STEP physical file is written.
VALID
VALUES
Single string; must be the full operating system path to the directory.
DEFAULT
VALUES
Current working directory.
SCOPE
STEP_FILETYPE_2_DATATYPE
DESCRIPTION
Serves as an error recovery mechanism when a dataset cannot be created because the
descriptive_representation_item field either does not contain the name of a tool
in the list of Teamcenter tools, or the named tool is not associated to a dataset type.
Pre-V7.0.2, the STEP AP214 processor used the descriptive_representation_item
field to determine which dataset type is associated to external files. If this field
did not contain the name of a tool in the list of tools, or if the named tool was not
associated to a dataset type, the dataset is not created and the external file is
dropped. In these circumstances, use this preference as an error recovery method.
If the STEP AP214 translator cannot find an appropriate tool, it try to infer the
correct tool from the file extension. Use this preference to define a list of file types
and tool names that the AP214 translator use to assign the appropriate tool and
dataset type.
VALID
VALUES
One or more strings, in the following format:
extension_name1 whitespace tool_name1


extension_name* is a file extension without the dot character, whitespace is any

amount of space without a new line character, and tool_name is a valid Teamcenter
tool that is associated with a dataset type.
The string NULL_EXTENSION is a special extension name and is reserved for files
that may not have an extension. For example:
STEP_FILETYPE_2_DATATYPE=
doc Text
model CATIA_Part
prt UGMASTER
NULL_EXTENSION UGPART
DEFAULT
VALUES
SCOPE
Site preference.
STEP_DMI_markup
DESCRIPTION
Maps Teamcenter dataset types to the STEP DMI_markup classification.
VALID
VALUES
DEFAULT
VALUES
Markup
SCOPE
Site preference.
STEP_IMAN_master_data
DESCRIPTION
Maps Teamcenter dataset types to the STEP IMAN_master_data file classification.
VALID
VALUES
DEFAULT
VALUES
Mdata
SCOPE
Site preference.
STEP_IMAN_specification
DESCRIPTION
Maps Teamcenter dataset types to the STEP IMAN_specification file classification.

VALID
VALUES
DEFAULT
VALUES
Specs
SCOPE
Site preference.
STEP_IMAN_manifestation
DESCRIPTION
Maps Teamcenter dataset types to the STEP IMAN_manifestation file
classification.
VALID
VALUES
DEFAULT
VALUES
Manif
SCOPE
Site preference.
STEP_IMAN_requirement
DESCRIPTION
Maps Teamcenter dataset types to the STEP IMAN_requirement file classification.
VALID
VALUES
DEFAULT
VALUES
Requi
SCOPE
Site preference.
STEP_IMAN_reference
DESCRIPTION
Maps Teamcenter dataset types to the STEP IMAN_reference file classification.
VALID
VALUES
DEFAULT
VALUES
Refer

SCOPE
Site preference.
STEP_IMAN_UG_altrep
DESCRIPTION
Maps Teamcenter dataset types to the STEP IMAN_UG_altrep classification.
VALID
VALUES
DEFAULT
VALUES
Altrep
SCOPE
Site preference.
STEP_IMAN_UG_scenario
DESCRIPTION
Maps Teamcenter dataset types to the STEP IMAN_UG_scenario classification.
VALID
VALUES
DEFAULT
VALUES
Scena
SCOPE
Site preference.
STEP_import_directory
DESCRIPTION
Sets location of STEP physical file when importing data via the Teamcenter/STEP
Translator.
VALID
VALUES
Single string; must be the full operating system path to the directory.
DEFAULT
VALUES
Current working directory.

SCOPE
STEP_informative_doc_role
DESCRIPTION
Supports only STEP AP214. Determines the document role of the dataset based on
its defined relation type to the specified item revision. The default role is obligatory
if the relation type is not listed under this preference.
VALID
VALUES
One or more strings; each string must be a valid informative relation type (for
example, IMAN_reference).
DEFAULT
VALUES
IMAN_specification
SCOPE
Site preference.
STEP_make_or_buy_attr
DESCRIPTION
Defines the item revision master attribute that stores the STEP make_or_buy
value for item revisions imported via the Teamcenter/STEP Translator.
VALID
VALUES
Single string; must be a valid item revision master attribute.
DEFAULT
VALUES
None.
SCOPE
Site preference.
STEP_material_specification_pref
DESCRIPTION
Maps Teamcenter dataset types to the STEP material specification classification.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.

STEP_not_yet_approved_status
DESCRIPTION
Supports only STEP AP214. Sets the item type as not yet approved. Use this
preference to import not yet approved STEP data into Teamcenter as working data.
Do this by defining a list of strings that, when detected during import, denote not yet
approved status.
VALID
VALUES
One or more strings.
DEFAULT
VALUES
not_yet_approved
SCOPE
Site preference.
STEP_part_items
DESCRIPTION
Defines the Teamcenter item type as a member of the STEP part classification.
VALID
VALUES
One or more strings; each string must be a valid item type name.
DEFAULT
VALUES
item
SCOPE
Site preference.
STEP_process_specification_pref
DESCRIPTION
Maps Teamcenter dataset types to the STEP process specification classification.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.

STEP_surface_finish_specification_pref
DESCRIPTION
Maps Teamcenter dataset types to the STEP surface finish specification
classification.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_organization_id
DESCRIPTION
Defines an organizational identifier for your enterprise.
VALID
VALUES
Single string as value; string must be a valid organization ID.
DEFAULT
VALUES
None.
SCOPE
Site preference.

Chapter
19 Product structure and Repeatable

Digital Validation preferences
Appearance Configuration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

APPR_allow_separate_spatial_processing . . . . . . . . . . . . . . . . . . . . . . . . 19-1
APPR_max_appearances_per_process . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
TC_allow_appr_checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
TC_appr_checking_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
TC_allow_appr_query_auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
TC_prevent_appr_query_on_corrupt_root . . . . . . . . . . . . . . . . . . . . . . . . 19-4
TC_appr_allow_remote_query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
TC_appr_remote_query_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Background appearance update preferences . . . . . . . . . . . . . . . . . . . . . . 19-5
APPR_allow_background_updates . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
APPR_background_updater_admin_email_address . . . . . . . . . . . . . . . 19-6
APPR_background_updater_auditing_enabled . . . . . . . . . . . . . . . . . . 19-7
APPR_background_updater_email_interval_for_different_package . . . 19-7
APPR_background_updater_email_interval_for_same_package . . . . . . 19-7
APPR_background_updater_gap_between_tries . . . . . . . . . . . . . . . . . 19-8
APPR_background_updater_interval . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
APPR_background_updater_max_num_failures . . . . . . . . . . . . . . . . . 19-8
APPR_background_updater_max_num_heartbeats . . . . . . . . . . . . . . . 19-9
APPR_background_updater_max_num_records . . . . . . . . . . . . . . . . . 19-9
APPR_background_updater_max_num_tries . . . . . . . . . . . . . . . . . . . 19-9
DesignContext preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10

DesignContext product item preferences . . . . . . . . . . . . . . . . . . . . . . . . 19-10
PortalDesignContextProductItemProperties . . . . . . . . . . . . . . . . . . 19-10
PortalDesignContextProductItemProperties.<attribute-value> . . . . . 19-11
PortalDesignContextProductItemColumnsShownPref . . . . . . . . . . . . 19-12
PortalDesignContextProductItemColumnsShownPrefWidth . . . . . . . 19-12
PortalDesignContextProductItemColumnsHiddenPref . . . . . . . . . . . 19-13
PortalDesignContextProductItemColumnsHiddenPrefWidth . . . . . . . 19-15
DesignContextRDVContextObject AddToECObjectPseudo
FolderPreference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-16
DesignContext product context preferences . . . . . . . . . . . . . . . . . . . . . . 19-17
DesignContextLoadRDVContextObjectMode . . . . . . . . . . . . . . . . . . 19-17
DesignContextPickUpNewBackgroundAppearance . . . . . . . . . . . . . . 19-17
RDVLoadAppearanceGroupMode . . . . . . . . . . . . . . . . . . . . . . . . . . 19-18
PortalDesignContextProductContextProperties . . . . . . . . . . . . . . . . 19-18
PortalDesignContextProductContextColumnsShownPref . . . . . . . . . 19-19
PortalDesignContextProductContextColumnsShownPrefWidth . . . . . 19-19
PortalDesignContextProductContextColumnsHiddenPref . . . . . . . . . 19-20

PortalDesignContextProductContextColumnsHiddenPrefWidth . . . . 19-22
DesignContext context definition preferences . . . . . . . . . . . . . . . . . . . . 19-24
DesignContextShowClearanceDBMenu . . . . . . . . . . . . . . . . . . . . . . 19-24
PortalDesignContextProductItemQuery . . . . . . . . . . . . . . . . . . . . . 19-24
PortalDesignContextECObject.TYPE . . . . . . . . . . . . . . . . . . . . . . . 19-25
PortalDesignContextECObject.WorkPartProperties . . . . . . . . . . . . . 19-25
PortalDesignContextECObject.WorkPartRelationships . . . . . . . . . . . 19-26
PortalDesignContextExcludedWorkPart.Types . . . . . . . . . . . . . . . . . 19-26
PortalDesignContextAllowNoWorkParts . . . . . . . . . . . . . . . . . . . . . 19-26
PortalDesignContextWIPRevRule . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
PortalDesignContextIsInstallationAssemblyMethod . . . . . . . . . . . . . 19-28
PortalDesignContextIsInstallation
AssemblyMethod.hasIRType.Type . . . . . . . . . . . . . . . . . . . . . . . . 19-28
PortalDesignContextIsInstallationAssemblyMethod.has_bomline_prop.name . . 19-29
PortalDesignContextIsInstallationAssemblyMethod.has_bomline_prop.value . . 19-29
PortalDesignContextFindInstallationTreeWalkIncrement . . . . . . . . . 19-30
PortalDesignContextSupportInstallationAssemblySelection . . . . . . . 19-30
PortalDesignContextUseUnconfigurableSearchResults . . . . . . . . . . . 19-30
DesignContext filter configuration preferences . . . . . . . . . . . . . . . . . . . . 19-31
PortalDesignContextAttributeSchemaSuppressedAttributes . . . . . . . 19-31
PortalDesignContextQPLServers . . . . . . . . . . . . . . . . . . . . . . . . . . 19-31
PortalDesignContextSearchEnginePreference . . . . . . . . . . . . . . . . . 19-31
DesignContextIncludeSubComponentsForSpatialSearch . . . . . . . . . . 19-32
DesignContext_ItemID_Query_lookup_string . . . . . . . . . . . . . . . . . 19-32
DesignContextMaximumShownTabs . . . . . . . . . . . . . . . . . . . . . . . . 19-33
PortalDesignContextAlwaysResetFilterConfigurationPanel . . . . . . . . 19-33
DesignContextPreciseRevRule . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-34
DesignContext interoperability preferences . . . . . . . . . . . . . . . . . . . . . . 19-34
PortalDesignContextCADbookmarkType . . . . . . . . . . . . . . . . . . . . . 19-34
PortalDesignContextVISbookmarkType . . . . . . . . . . . . . . . . . . . . . 19-35
DesignContext_PSE_Synchronization . . . . . . . . . . . . . . . . . . . . . . . 19-36
TC_show_open_in_nx_button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-36
DesignContext performance tuning preferences . . . . . . . . . . . . . . . . . . . 19-37
RDVClearanceProxyServers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-37
PortalDesignContextMaxMatchingObjects . . . . . . . . . . . . . . . . . . . . 19-37
PortalDesignContextMaxMatchingBOMLines . . . . . . . . . . . . . . . . . 19-38
PortalDesignContextSetVariantRulesMaxTargetAppearances . . . . . . 19-38
Using DesignContext composite properties . . . . . . . . . . . . . . . . . . . . . . 19-39
Multi-Structure Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-40

ALLOC_Group_Allocation_Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-40
ALLOC_Product_Representation_Types . . . . . . . . . . . . . . . . . . . . . . . . 19-41
ALLOC_Target_Occurrence_Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-41
ALLOC_Source_Occurrence_Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-42
ALLOC_source_target_cardinality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-42
ALLOC_map_copy_allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-43
Default_StructureContext_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-44
Structure Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-44

Structure Manager behavior preferences . . . . . . . . . . . . . . . . . . . . . . . . 19-44
BOM_objects_excluded_from_split . . . . . . . . . . . . . . . . . . . . . . . . . 19-45
CFM_ITEM_TYPE_RULE_INCLUDE_SUB_TYPES . . . . . . . . . . . . 19-45
GDE_objects_with_integer_quantity . . . . . . . . . . . . . . . . . . . . . . . . 19-46
PSE_check_read_access_for_Rev_Rule_entry . . . . . . . . . . . . . . . . . . 19-46

PSE_default_view_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-46
PSE_Display_Pending_Edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-47
PSE_expand_on_open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-47
PSE_ROLL_UP_TEMPLATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-48
ROLL_UP_QUANTITY_FLAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-48
PSEshowToolBar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-48
PS_Find_Number_Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-49
PS_new_seqno_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-49
PS_replace_with_substructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-50
PS_wu_configd_imprecise_only . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-50
PUBLISH_AlignableSourceTypes . . . . . . . . . . . . . . . . . . . . . . . . . . 19-51
PUBLISH_AlignableTargetTypes . . . . . . . . . . . . . . . . . . . . . . . . . . 19-51
TC_BOM_Precision_Preference . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-52
TC_show_open_in_pse_button . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-52
TC_config_rule_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-52
Vis_InterOptWithProductViewDataset . . . . . . . . . . . . . . . . . . . . . . 19-53
VISTopLevelRef_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . 19-53
Structure Manager column preferences . . . . . . . . . . . . . . . . . . . . . . . . . 19-53
PortalPSEColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-54
PortalPSEShownColumnsWidthPref . . . . . . . . . . . . . . . . . . . . . . . . 19-54
PSESearchColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-55
PSESearchShownColumnWidthsPref . . . . . . . . . . . . . . . . . . . . . . . 19-55
variant_item_column_width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-56
variant_option_column_width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-56
variant_description_column_width . . . . . . . . . . . . . . . . . . . . . . . . . 19-56
variant_value_column_width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-57
variant_state_column_width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-57
variant_values_column_width . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-57
vrule_reln_column_width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-58
Structure Manager display preferences . . . . . . . . . . . . . . . . . . . . . . . . . 19-58
application name.ic_icon_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-58
application name.ic_show_remove_icons . . . . . . . . . . . . . . . . . . . . . 19-59
BOMCompareVisibleModes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-59
BOM_MARKUP_ADD_FONT_STYLE . . . . . . . . . . . . . . . . . . . . . . 19-60
BOM_MARKUP_ADD_FOREGROUND . . . . . . . . . . . . . . . . . . . . . 19-60
BOM_MARKUP_STRIKE_FOREGROUND . . . . . . . . . . . . . . . . . . . 19-61
IC_baseline_carry_forward_active_changes . . . . . . . . . . . . . . . . . . . 19-61
IC_baseline_carry_forward_status . . . . . . . . . . . . . . . . . . . . . . . . . 19-62
ICPanelBomChangeDefs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-62
ICPanelBomChangeWidths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-62
ICPanelAttachChangeDefs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-63
ICPanelAttachChangeWidths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-63
ICPanelOccAttrChangeDefs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-64
ICPanelOccAttrChangeWidths . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-64
Incremental_Change_Management . . . . . . . . . . . . . . . . . . . . . . . . . 19-65
MoveICCreationToMenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-66
New_Ic_Dialog_last_ic_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-66
PSEDisplayTypePref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-66
PSEoccnotesnocopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-67
PSE_icon_placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-67
PSE_show_option_family_prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-67
PSE_show_option_item_prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-68
PSEPreciseColorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-68
PSEImpreciseColorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-69

PSESubstituteColorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-69
PSEAutoPackPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-69
PSEShowSubstitutesPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-70
PSE_enable_related_substitutes . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-70
PSEAdditionColorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-70
PSEChangedColorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-71
PSEIsNewVILinkedToModule . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-71
PSEVariantRuleDialogTableSort . . . . . . . . . . . . . . . . . . . . . . . . . . 19-71
TC_ExportConfigUGNXAssembly . . . . . . . . . . . . . . . . . . . . . . . . . . 19-72
Structure Manager assembly preferences . . . . . . . . . . . . . . . . . . . . . . . 19-72
PSEVariantsMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-73
PSEShowUnconfigdVarPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-73
PSEShowUnconfigdEffPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-74
PSEEnableFilteringUnconfigdDueToClassicVariantsPref . . . . . . . . . 19-75
ConfigureToLoadEnableDefaultVariantConfig . . . . . . . . . . . . . . . . . 19-75
CFMOccEffMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-76
TC_ValidApprovedStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-76
AbsOccGrmCopyRules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-77
PSEIsNewVIisLinkedToModule . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-78
PSEAllowLegacyVICreation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-78
PSEBypassVISearch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-79
PSECreateVISameType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-79
ShowModuleIcons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-80
ShowViIcons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-80
PSEAutoViCreateEmptyVI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-81
PSEAutoViStopVICreationForUnconfiguredModule . . . . . . . . . . . . . 19-81
PSEAutoViNewItemPopup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-82
PSEAutoViNamePrefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-82
PSM_classic_variants_text_families . . . . . . . . . . . . . . . . . . . . . . . . 19-82
PSM_classic_variants_numeric_families . . . . . . . . . . . . . . . . . . . . . 19-84
TC_CFG_PRODUCTS_USE_VARIABILITY . . . . . . . . . . . . . . . . . . 19-85
TCEnforceSingleType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-87
TCAllowedChildTypes_<ItemTypeOrGDEType> . . . . . . . . . . . . . . . 19-87
TCAllowedParentTypes_itemtype . . . . . . . . . . . . . . . . . . . . . . . . . . 19-88
PSM_global_option_item_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-88
PSESavedConfigRelationTypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-89
BOM_Enable_Ref_Designator_Value_Packing . . . . . . . . . . . . . . . . . 19-89
BOM_Additional_Packing_Criteria . . . . . . . . . . . . . . . . . . . . . . . . . 19-90
BOM_Additional_Ref_Designator_Search_Criteria . . . . . . . . . . . . . . 19-90
PS_Reference_Designator_Validation . . . . . . . . . . . . . . . . . . . . . . . 19-91
BOM_Enable_Quantity_Validation_Against_Ref_Designator . . . . . . . 19-91
PS_Duplicate_FindNo_Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-92
BOMExcludeFromPackCheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-92
TC_JT_voxel_size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-93
JT_File_OverrideChildren_Refsets . . . . . . . . . . . . . . . . . . . . . . . . . 19-93
JT_File_Priority_Refsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-94
JT_File_Excluded_Refsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-95
JTContentBomLineProperties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-95
JTContentHintPropertyPolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-96
PSE_prompt_for_remote_import . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-96
RAC_expand_below_batch_size . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-96
Structure Manager transform preferences . . . . . . . . . . . . . . . . . . . . . . . 19-97
PS_assume_old_transform_format . . . . . . . . . . . . . . . . . . . . . . . . . 19-97
PS_assume_legacy_transform_units . . . . . . . . . . . . . . . . . . . . . . . . 19-98

PS_allow_plmxml_transforms_with_no_legacy_factor . . . . . . . . . . . . 19-98
PS_convert_legacy_transform_to_plmxml . . . . . . . . . . . . . . . . . . . . 19-99
Product structure synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-99
PS_structure_change_condition . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-99
TC_BVRSYNCFORM_DELEGATE . . . . . . . . . . . . . . . . . . . . . . . . 19-101
BOM grading preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-101
CondValData.CREATERENDERING . . . . . . . . . . . . . . . . . . . . . . 19-101
CondValData.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . 19-102
CondValDataCreate.CREATE_REGISTEREDTO . . . . . . . . . . . . . . 19-102
CondValdataRevSummary.SUMMARY_REGISTEREDTO . . . . . . . 19-102
CondValDataRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . 19-102
CondValDataRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . 19-103
CondValDataRevision.SUMMARYRENDERING . . . . . . . . . . . . . . 19-103
CondValDataSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . 19-103
CondValResult.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . 19-104
CondValResultSummary.SUMMARY_REGISTEREDTO . . . . . . . . . 19-104
CondValidation_NoData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-104
CONDVALIDATION_Keep_PrevRev_Result . . . . . . . . . . . . . . . . . 19-105
ConditionValidationResultColumnPreferences . . . . . . . . . . . . . . . . 19-105
ConditionValidationResultColumnWidthPreferences . . . . . . . . . . . 19-106
Platform Designer preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-106

<Architecture_Type>_generic_id_mapping . . . . . . . . . . . . . . . . . . . . . 19-106
ArchitectureModeler_add_design_business_rule_check . . . . . . . . . . . . . 19-107
ArchitectureModeler_add_design_occurrence_business_rule_check . . . . 19-107
ArchitectureModeler_locking_retry_count . . . . . . . . . . . . . . . . . . . . . . 19-108
ArchitectureModeler_multiple_installation_assemblies_condition . . . . . 19-108
ArchitectureModeler_part_solution_properties . . . . . . . . . . . . . . . . . . 19-109
ArchitectureModeler_remove_design_business_rule_check . . . . . . . . . . 19-109
ArchitectureModeler_RemoveDesign_Max . . . . . . . . . . . . . . . . . . . . . . 19-109
ArchitectureModeler_remove_design_occurrence_business_rule_check . . 19-110
ArchitectureModeler_replace_design_business_rule_check . . . . . . . . . . 19-110
ArchitectureModeler_replace_design_occurrence_business_rule_check . . 19-111
ArchitectureModeler_update_designs_business_rule_check . . . . . . . . . . 19-111
ArchitectureModeler_update_design_occurrences_business_rule_check . . 19-112
ArchitectureModeler_use_all_installation_assemblies . . . . . . . . . . . . . 19-112
RDV_platformdesigner_assign_bulk_variability . . . . . . . . . . . . . . . . . . 19-113
RDV preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-113

EPM_tessellation_target_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-113
EPM_tessellation_servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-114
LOU_display_name_properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-114
PortalDesignContextProcess.WorkPartProperties . . . . . . . . . . . . . . . . . 19-114
PortalDesignContextProcess.WorkPartOrChangeAttachmentTypes . . . . 19-115
RDV_audit_report_usage_attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 19-115
RDV_audit_report_occurrence_attributes . . . . . . . . . . . . . . . . . . . . . . 19-116
RDV_authoring_override_user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-118
RDV_auto_functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-118
RDV_auto_populate_occ_notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-118
RDV_build_intent_atth_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-119
RDVCreateSCOForClearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-119
RDV_Create_SCO_WITHOUT_APN . . . . . . . . . . . . . . . . . . . . . . . . . . 19-120
RDV_copied_occurrence_notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-120
RDV_default_Architecture_Breakdown_RevRule . . . . . . . . . . . . . . . . . 19-120

RDV_enable_product_lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-121
RDV_export_nve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-121
RDVIgnoreErrorConnectReleasedPartsServer . . . . . . . . . . . . . . . . . . . 19-121
RDV_install_configuration_rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-122
RDV_occurrence_business_rule_check . . . . . . . . . . . . . . . . . . . . . . . . . 19-122
RDV_part_business_rule_check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-123
RDV_partnumber_validation_rule . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-123
RDV_part_occ_note_mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-123
RDV_product_code_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-124
RDVReleasedPartsProcessAssemType . . . . . . . . . . . . . . . . . . . . . . . . 19-124
RDVReleasedPartsCollectorServer . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-125
RDV_show_itemid_prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-125
RDV_show_lou_prop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-125
RDV_turn_audit_logging_on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-126
RDV_uneditable_part_occ_notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-126
RDV_usage_attribute_set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-127
RDV_usage_occurrence_notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-127
RDV_valid_partnumber_rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-127
RDV_variant_expression_overlap_checking_mode . . . . . . . . . . . . . . . . 19-128
RDV_variant_overlays_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-128
RDV_variant_overlays_uses_true_availability . . . . . . . . . . . . . . . . . . . 19-129
BOMWriterDirectModelRelationType . . . . . . . . . . . . . . . . . . . . . . . . . 19-129
BOMWriterNoDescendantsInPLMXML . . . . . . . . . . . . . . . . . . . . . . . 19-130
BOMWriterNoDirectParents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-130
Quick spatial search preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-131

QS_QSEARCH_ENABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-131
QSEARCH_update_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-132
QS_SPATIAL_ENABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-132
QS_TRUSHAPE_GENERATION_ENABLED . . . . . . . . . . . . . . . . . . . 19-132
QS_BBOX_GENERATION_ENABLED . . . . . . . . . . . . . . . . . . . . . . . . 19-133
QS_BBOX_GENERATION_FROM_NX_ENABLED . . . . . . . . . . . . . . . 19-134
QS_MAX_QUERY_EXECUTION_TIME_FOR_BOTTOMUP . . . . . . . . . 19-134
RDV_QSEARCH_REFINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-134
RDV_QSEARCH_REVISION_RULE_NAMES . . . . . . . . . . . . . . . . . . . 19-135
RDV_QSEARCH_STREAMING_MODE . . . . . . . . . . . . . . . . . . . . . . . 19-135

Chapter
19 Product structure and Repeatable

Digital Validation preferences
Teamcenter product configuration and Repeatable Digital Validation applications

include Structure Manager, DesignContext, Appearance Configuration,
Multi-Structure Manager, and Platform Designer. These applications enable you
configure, classify, and display assembly data.
Use product structure preferences to enable and modify the behavior of these
applications.
Appearance Configuration preferences

Appearance functionality allows you to cache a configured product structure,
permitting faster searching of the structure for components configured at a specific
date or unit. The appearance cache allows users to perform spatial searches, for
example, to find all components within one centimeter of a selected part. Users
can combine appearance searches with other queries, for example, queries for item
revision master attributes, Classification attributes, or occurrence notes.
Use Appearance Configuration preferences to configure appearance validation
functionality.
Note
If you are using an appearance cache, you must also set the
PS_assume_legacy_transform_units site preference. By default, this
preference is set to Unknown and you must set it to your chosen unit of
measure (Inches or Millimeters).
APPR_allow_separate_spatial_processing
DESCRIPTION
Determines whether spatial data is processed by the same update package as
structure data or in a separate package. If you manage your spatial and structure
data separately, there may be a performance advantage in using separate update
packages.
For more information regarding appearances functionality and setting appearance
preferences, see the Appearance Configuration Guide.

Chapter 19 Product structure and Repeatable Digital Validation preferences
VALID
VALUES
true Spatial processing is processed in a separate package.
false Spatial processing is not processed in a separate package.
DEFAULT
VALUES
false
SCOPE
Site preference.
APPR_max_appearances_per_process
DESCRIPTION
Determines the maximum number of appearance sets the system processes at a
given time. If you process very large appearance sets, the server may run out of
memory. Use this preference to avoid memory errors.
For more information regarding appearances functionality and setting appearance
preferences, see the Appearance Configuration Guide.
VALID
VALUES
Accepts a single string as a value. Must be a non-negative integer. 0 assigns no limit
to the number of appearance sets processed.
DEFAULT
VALUES
0
SCOPE
Site preference.
TC_allow_appr_checking
DESCRIPTION
Enables automatic validation of appearances. Use this functionality to automatically
validate appearances and detect any inconsistencies. The system performs this
validation offline with the same mechanism as appearance update.
For more information regarding automatic validation of appearances, see the
Appearance Configuration Guide.
If you do not enable validation, you can still validate appearances manually.
Tip
This preference requires that the TC_allow_appr_query_auditing
preference is enabled before it takes effect.
Use this preference with the TC_appr_checking_interval preference, which

specifies how frequently to validate appearances.

Product structure and Repeatable Digital Validation preferences
VALID
VALUES
true or on or yes Enables automatic validation of appearances.
or 1
false or off or no Disables automatic validation of appearances.
or 0
DEFAULT
VALUES
false
SCOPE
All.
TC_appr_checking_interval
DESCRIPTION
Specifies (in hours) how frequently the system performs automatic appearance
validation. The more frequently you run the validation, the more quickly any
inconsistency is detected. However, there is a performance consideration as these
packages are run on the same queue as the appearance update packages.
Use this preference with the TC_allow_appr_checking preference, which enables
automatic validation of appearances.
VALID
VALUES
Accepts a single string as a value. Can be any positive integer.
DEFAULT
VALUES
2.0
SCOPE
All.
TC_allow_appr_query_auditing
DESCRIPTION
Determines whether the system audits the querying of appearances. When this
preference is enabled, the system creates a record in the database whenever a user
performs a Structure Manager search that drives the appearance checker.
Tip
This preference must be enabled before the TC_allow_appr_checking
preference can take effect.

VALID
VALUES
true or on or yes The system audits the querying of appearances.
or 1
false or off or no The system does not audit the querying of appearances.
or 0
DEFAULT
VALUES
false
SCOPE
All.
TC_prevent_appr_query_on_corrupt_root
DESCRIPTION
Determines whether to allow the querying of appearances associated with a corrupt
appearance root. Corruption is an indication that the appearances are inconsistent
with the structure which they represent, so a query may produce misleading results.
If you activate this feature and an appearance root is marked as inconsistent,
users cannot perform searches on that appearance root. In this way, they receive
immediate feedback that the appearance set has a problem and know they cannot
rely on the results.
VALID
VALUES
true or on or yes The system audits the querying of appearances.
or 1
false or off or no The system does not audit the querying of appearances.
or 0
DEFAULT
VALUES
false
SCOPE
All.
TC_appr_allow_remote_query
DESCRIPTION
Determines whether to allow querying for remote appearances. Remote appearances
are appearances which have been associated with a remote published appearance
root.
Note
To publish an appearance root, ensure that AppearanceRoot is a value for
the TC_publishable_classes site preference.

You use appearances in a Multi-Site Collaboration environment (allowing users at

remote sites to perform appearance searches) by maintaining an appearance cache
at a single master site. All users perform appearance queries on that cache.
For more information about using Multi-Site Collaboration with appearances, see
the Appearance Configuration Guide.
VALID
VALUES
true or on or yes The system allows querying for remote appearances.
or 1
false or off or no The system does not allow querying for remote appearances.
or 0
DEFAULT
VALUES
false
SCOPE
All.
TC_appr_remote_query_timeout
DESCRIPTION
Specifies (in seconds) the time out period for remote appearance queries.
Use this preference with the TC_appr_allow_remote_query preference, which
enables querying for remote appearances. Remote appearances are appearances
which have been associated with a remote published appearance root.
Note
To publish an appearance root, ensure that AppearanceRoot is a value for
the TC_publishable_classes site preference.
VALID
VALUES
Accepts a single string as a value. Can be any positive integer.
DEFAULT
VALUES
60
SCOPE
All.
Background appearance update preferences

You can use the following Appearance Configuration preferences to configure an
alternative, non-supported, method of appearance updating. This alternative
method:
• Runs in the background.
• Does not require the Update Manager. Rather, it uses either UNIX crons, or
Windows Task Scheduler.

• Stores update scheduling and progress information in the database. Anticipated

(scheduled) update data can be easily compared with actual update data.
• Replaces the use of sockets/handles by calls to set/ask database information.
Note
Background appearance update functionality is currently not supported.
APPR_allow_background_updates
DESCRIPTION
Determines whether the appearance_updater utility can perform background
updates, using the -background option.
VALID
VALUES
True The appearance_updater utility can perform background
False The appearance_updater utility cannot perform background
DEFAULT
VALUES
False
SCOPE
Site preference.
APPR_background_updater_admin_email_address
DESCRIPTION
Defines the user to which e-mail is sent, notifying the user of failure to process an
appearance update package in background mode.
VALID
VALUES
$USER The user logged into the appearance_updater utility is
notified.
$OSUSER The operating system user running the appearance_updater
utility is notified.
DEFAULT
VALUES
$OSUSER
SCOPE
Site preference.

APPR_background_updater_auditing_enabled
DESCRIPTION
Determines whether to create audit records when the appearance_updater utility
performs background updates.
VALID
VALUES
True Audit records are created when the appearance_updater
utility performs background updates.
False Audit records are created not when the appearance_updater
utility performs background updates.
DEFAULT
VALUES
False
SCOPE
Site preference.
APPR_background_updater_email_interval_for_different_package
DESCRIPTION
Determines the minimum time interval (in minutes) to allow the sending of e-mail
regarding the failure of the appearance_updater utility to process any appearance
package in background mode.
VALID
VALUES
DEFAULT
VALUES
10
SCOPE
Site preference.
APPR_background_updater_email_interval_for_same_package
DESCRIPTION
Determines the minimum time interval (in minutes) to allow the sending of e-mail
regarding the failure of the appearance_updater utility to process a particular
appearance package in background mode.
VALID
VALUES
DEFAULT
VALUES
10
SCOPE
Site preference.

APPR_background_updater_gap_between_tries
DESCRIPTION
Determines the minimum time interval (in seconds) a background updates must
wait between processing attempts.
VALID
VALUES
DEFAULT
VALUES
2
SCOPE
Site preference.
APPR_background_updater_interval
DESCRIPTION
Determines the time interval between background updates. Define this time interval
by setting this preference to the number of minutes you expect a background update
to run. When a new package is placed in the update queue and background updates
have been configured, the system checks whether a background update has been run
within the time limit set by this preference. If not, an e-mail is sent to the recipient
specified by the APPR_background_updater_admin_email_address preference.
VALID
VALUES
DEFAULT
VALUES
5
SCOPE
Site preference.
APPR_background_updater_max_num_failures
DESCRIPTION
Determines how many background update failures to allow for a particular
update package. Once the number of failures exceeds the value set in this
preference, background updates are disabled by changing the setting of the
APPR_allow_background_updates preference to False.
VALID
VALUES
DEFAULT
VALUES
5
SCOPE
Site preference.

APPR_background_updater_max_num_heartbeats
DESCRIPTION
Determines how many heartbeat records to keep per machine. A heartbeat record
indicates that a single background appearance update has been run.
VALID
VALUES
DEFAULT
VALUES
2
SCOPE
Site preference.
APPR_background_updater_max_num_records
DESCRIPTION
Determines how many records to keep about the appearance updater’s background
activity.
VALID
VALUES
DEFAULT
VALUES
109
SCOPE
Site preference.
APPR_background_updater_max_num_tries
DESCRIPTION
Determines how many tries an individual background update process should look
for packages to process before exiting.
VALID
VALUES
DEFAULT
VALUES
10
SCOPE
Site preference.

DesignContext preferences
DesignContext enables you to quickly focus on a particular work part and any other
parts affected within the context of a change to that part. Use this application to
select a product item and configure revisions of components, configure variants of
the assembly, review the set of components, retrieve the components, and initialize
their display in a CAD application or a visualization application.
Use DesignContext preferences to define the standard for identifying a product item,
the value of an attribute and modify the application interface.
DesignContext product item preferences

The preferences in this section control DesignContext product items.
PortalDesignContextProductItemProperties
DESCRIPTION
Specifies the standard for identifying a product item, that is, the top-level item of
the assembly structure from a product perspective. The product item represents
a long-term engineering project, for example, a washing machine or refrigerator
program.
The DesignContext application displays items matching all
PortalDesignContextProductItemProperties in the Product Items table in the
Context Definition pane, if a searchable cache (for example, an appearance set or a
QPL build) exits, the Platform Designer application filters the result of the saved
query specified with the PortalDesignContextProductItemQuery preference
down to those items matching all PortalDesignContextProductItemProperties.
Setting this preference is required.
Note
For each composite property specified in the list, you must also set a
PortalDesignContextProductItemProperties.property-value preference.
VALID
VALUES
Any composite property. For examples of composite properties, see the default
values for the PortalDesignContextProductItemColumnsShownPref and
PortalDesignContextProductItemColumnsHiddenPref preferences.
Other valid properties, such as properties on item or item revision master forms,
may depend on customization at your site.
In the following example, the setting item_master_tag:Project_ID is a composite
property:
PortalDesignContextProductItemProperties=
object_type
item_master_tag:Project_ID
PortalDesignContextProductItemProperties.object_type=
Product
PortalDesignContextProductItemProperties.item.master_tag:Project_ID=
Approved

In the following example, specifying process_stage implies that a workflow

process was started on the product item based on a process template named
ProductProcess. Specifying owning_group implies the owning group of the item
is Product Group.
process_stage_list
owning_group
PortalDesignContextProductItemProperties.process_stage_list=
ProductProcess
PortalDesignContextProductItemProperties.owning_group=
Product Group
DEFAULT
VALUES
object_type
object_desc
Item
PortalDesignContextProductItemProperties.object_desc=
Product
The default values dictate that an item is considered a product item if it has the
type Item and a description of Product.
SCOPE
All.
PortalDesignContextProductItemProperties.<attribute-value>
DESCRIPTION
Identifies the value of an attribute specified as a product item property on the
PortalDesignContextProductItemProperties preference.
Setting this preference is required. You must set one of these preferences for each
attribute specified for the product item.
For example:
FM0_Vehicle
PortalDesignContextProductItemProperties.process_stage=
RDV/Vehicle
PortalDesignContextProductItemProperties.owning_group=
Vehicle
PortalDesignContextProductItemProperties.object_type.item_master_tag:Project_ID=
RDV Assembly
VALID
VALUES
.
DEFAULT
VALUES
object_type=Item
object_desc=Product

SCOPE
All.
PortalDesignContextProductItemColumnsShownPref
DESCRIPTION
Specifies the list of attributes displayed in DesignContext and the order in which
they are displayed in the table displaying selected product items.
VALID
VALUES
Composite properties on product item objects. Composite properties accept
any attribute that the Java API getProperty method on the rich client
IMANComponent class accepts.
For standard Teamcenter, the valid values are the default values shown in the
following example. Other valid attributes, such as attributes on Item Master Forms,
depend on the attributes your site exposes in UID files.
DEFAULT
VALUES
Item.object_string
Item.object_name
Item.object_desc
Item.process_stage
Item.process_stage_list
Item.current_job
Item.object_type
Item.owning_user
Item.owning_group
SCOPE
All
PortalDesignContextProductItemColumnsShownPrefWidth
DESCRIPTION
Specifies the widths of the columns for the product item properties defined with the
PortalDesignContextProductItemColumnsShownPref preference.
VALID
VALUES
Any positive integer representing the number of characters that are
visible (assuming an average character width). Each value defined in this
preference corresponds with a product item property value defined in the
PortalDesignContextProductItemColumnsShownPref preference.
DEFAULT
VALUES
15
10
8
10
13

8
4
16
8
SCOPE
All
PortalDesignContextProductItemColumnsHiddenPref
DESCRIPTION
Specifies the hidden product item properties.
VALID
VALUES
Composite properties on product item revision objects. Composite properties
accept any attribute that the Java API getProperty method on the rich client
For standard Teamcenter the valid values are the default values shown in the
example below. Other valid attributes, such as attributes on item revision master
forms, depend on the attributes your site exposes in UID files.
DEFAULT
VALUES
Item.creation_date
Item.item_id
Item.owning_site
Item.archive_date
Item.backup_date
Item.based_on
Item.checked_out
Item.configuration_object_tag
Item.date_released
Item.expl_checkout
Item.export_sites
Item.has_variants
Item.ics_classified
Item.ics_subclass_name
Item.is_frozen
Item.is_modifiable
Item.last_mod_date
Item.last_mod_user
Item.last_release_status
Item.bom_view_tags
Item.IMAN_master_form
Item.item_master_tag
Item.IMAN_manifestation
Item.IMAN_reference
Item.IMAN_Rendering
Item.IMAN_requirement
Item.protection
Item.publication_sites
Item.release_status_list

Item.release_statuses
Item.reservation
Item.revision_list
ItemRevision.revision_list:object_string
ItemRevision.revision_list:object_desc
ItemRevision.revision_list:object_name
ItemRevision.revision_list:object_type
ItemRevision.revision_list:owning_user
ItemRevision.revision_list:owning_group
ItemRevision.revision_list:process_stage
ItemRevision.revision_list:process_stage_list
ItemRevision.revision_list:current_job
ItemRevision.revision_list:item_revision_id
ItemRevision.revision_list:release_status_list
ItemRevision.revision_list:release_statuses
ItemRevision.revision_list:structure_revisions
ItemRevision.revision_list:item_master_tag
ItemRevision.revision_list:date_released
ItemRevision.revision_list:IMAN_master_form_rev
ItemRevision.revision_list:creation_date
ItemRevision.revision_list:based_on
ItemRevision.revision_list:owning_site
ItemRevision.revision_list:backup_date
ItemRevision.revision_list:archive_date
ItemRevision.revision_list:checked_out
ItemRevision.revision_list:expl_checkout
ItemRevision.revision_list:export_sites
ItemRevision.revision_list:has_variants
ItemRevision.revision_list:ics_classified
ItemRevision.revision_list:ics_subclass_name
ItemRevision.revision_list:IMAN_specification
ItemRevision.revision_list:IMAN_manifestation
ItemRevision.revision_list:IMAN_reference
ItemRevision.revision_list:IMAN_Rendering
ItemRevision.revision_list:IMAN_requirement
ItemRevision.revision_list:IMAN_UG_altrep
ItemRevision.revision_list:IMAN_UG_expression
ItemRevision.revision_list:IMAN_UG_promotion
ItemRevision.revision_list:IMAN_UG_scenario
ItemRevision.revision_list:IMAN_UG_udf
ItemRevision.revision_list:IMAN_UG_wave_geometry
ItemRevision.revision_list:IMAN_UG_wave_part_link
ItemRevision.revision_list:IMAN_UG_wave_position
ItemRevision.revision_list:is_frozen
ItemRevision.revision_list:is_modifiable
ItemRevision.revision_list:last_mod_date
ItemRevision.revision_list:last_mod_user
ItemRevision.revision_list:last_release_status
ItemRevision.revision_list:protection
ItemRevision.revision_list:publication_sites
ItemRevision.revision_list:reservation
SCOPE
All

PortalDesignContextProductItemColumnsHiddenPrefWidth
DESCRIPTION
Specifies the widths of the columns for the hidden product item properties defined in
the PortalDesignContextProductItemColumnsHiddenPref preference.
VALID
VALUES
Any positive integer representing the number of characters that are visible
(assuming an average character width). Each value defined in this preference
corresponds with a hidden product item property value defined in the
PortalDesignContextProductItemColumnsHiddenPref preference.
DEFAULT
VALUES
12
6
8
9
11
7
3
16
10
19
8
6
10
10
7
9
12
13
14
11
10
12
10
10
11
10
12
10
10
12
8
17
26
29
28
28
32
29
27

26
25
26
30
29
29
27
30
31
30
28
29
30
28
26
26
25
26
26
30
33
30
26
28
28
30
30
31
30
25
34
31
33
23
25
27
27
30
31
27
25
SCOPE
User preference.
DesignContextRDVContextObject AddToECObjectPseudo FolderPreference

DESCRIPTION
Specifies the pseudofolder used to add a structure context object to an Engineering
Change item revision.
Structure context objects created in a DesignContext session are added to the
Engineering Change item revisions and process objects currently active in the

DesignContext session by placing them in the pseudofolder defined by this

preference. The contents of this pseudofolder can be viewed in My Teamcenter.
VALID
VALUES
Valid Teamcenter pseudofolder name.
DEFAULT
VALUES
IMAN_reference
SCOPE
User preference.
DesignContext product context preferences
DesignContextLoadRDVContextObjectMode
DESCRIPTION
Specifies the mode DesignContext uses to evaluate a structure context object (SCO),
either static mode or dynamic mode. When evaluating an SCO in static mode, the
existing results are returned. When evaluating an SCO in dynamic mode, the results
are updated against the current data and modified as necessary.
VALID
VALUES
0 Static mode. Returns the results already stored in the SCO.
1 Reevaluates the stored results against current data and
updates the SCO with new results.
DEFAULT
VALUES
1
SCOPE
All.
DesignContextPickUpNewBackgroundAppearance
DESCRIPTION
Determines whether unselected background appearances data is stored with the
structure context object data during the save operation.
VALID
VALUES
TRUE Saves unselected background appearances data with the
structure context object data during the save operation.
FALSE Does not save unselected background appearances data with
the structure context object data during the save operation.
DEFAULT
VALUES
FALSE
SCOPE
User preference.

RDVLoadAppearanceGroupMode
DESCRIPTION
Determines how an appearance group is loaded in the viewer. Appearance groups
contain references to search criteria objects and contain MEAppearancePathNodes
as attachments. The items corresponding to the MEAppearancePathNodes are
loaded in the viewer based on this preference. Three loading methods are used
when items are loaded.
VALID
VALUES
1 The child item of the first occurrence, based on date, is loaded.
2 The child item of the last created occurrence, based on date,
is loaded.
3 The child item of the occurrence configured to the default
revision rule is loaded.
DEFAULT
VALUES
3
SCOPE
User preference.
PortalDesignContextProductContextProperties
DESCRIPTION
Specifies the standard for identifying the product context: the item revisions of a
DesignContext product item that represent the same generic product structure.
Ideally this is one item revision. This item revision, or set of item revisions, is input
to configure the harvester_jt.pl script.
Values are entered as a list of attributes. All item revisions sharing the same values
on all product context attributes form one product context.
VALID
VALUES
Any attribute that the Java API getProperty method on the rich
client IMANComponent class accepts. For standard Teamcenter, the
list of valid values is a combination of the default values listed for
the PortalDesignContextProductContextColumnsShownPref and
PortalDesignContextProductContextColumnsHiddenPref preferences.
Other valid attributes, such as attributes on item or item revision master forms,
Note
You can specify a composite property.
For more information about composite properties, see Using DesignContext
composite properties.

DEFAULT
VALUES
ItemRevision.object_name
SCOPE
User preference.
PortalDesignContextProductContextColumnsShownPref
DESCRIPTION
Specifies the list of attributes DesignContext displays in the table of selected
product contexts and the order of display. Typically, this preference lists a
combination of attributes of the item revision and item revision master form.
Users can set this preference from the rich client interface by choosing the
Edit→Options→DesignContext→ProductContext command.
Siemens PLM Software recommends that you start with the list of properties defined
for the portaldesigncontextproductcontextproperties preference.
VALID
VALUES
Composite properties on product item objects. Composite properties accept
any attribute that the Java API getProperty method on the rich client
For more information about composite properties, see Structure Manager preferences.
example below. Other valid attributes, such as attributes on item master forms,
DEFAULT
VALUES
These values are composite properties.
ItemRevision.object_string
ItemRevision.object_name
ItemRevision.object_desc
ItemRevision.based_on
ItemRevision.items_tag
ItemRevision.creation_date
ItemRevision.date_released
ItemRevision.last_mod_user
ItemRevision.last_mod_date
SCOPE
User preference.
PortalDesignContextProductContextColumnsShownPrefWidth
DESCRIPTION
Specifies the widths of the columns for the product context properties.
For more information, see
PortalDesignContextProductContextColumnsShownPref.

VALID
VALUES
(assuming an average character width).
DEFAULT
VALUES
18
10
10
15
16
12
12
10
10
SCOPE
User preference.
PortalDesignContextProductContextColumnsHiddenPref
DESCRIPTION
Specifies the widths of the columns for the product context properties.
VALID
VALUES
Composite properties on product item revision objects. Composite properties
accept any attribute that the Java API getProperty method on the rich client
For more information about composite properties, see Structure Manager preferences.
example below. Other valid attributes, such as attributes on item revision master
forms, depend on the attributes your site exposes in UID files.
DEFAULT
VALUES
ItemRevision.IMAN_specification
ItemRevision.IMAN_master_form_rev
ItemRevision.item_revision_id
ItemRevision.archive_date
ItemRevision.backup_date
ItemRevision.checked_out
ItemRevision.current_job
ItemRevision.expl_checkout
ItemRevision.export_sites
ItemRevision.has_variants
ItemRevision.ics_classified
ItemRevision.ics_subclass_name
ItemRevision.IMAN_requirement
ItemRevision.IMAN_manifestation

ItemRevision.IMAN_reference
ItemRevision.IMAN_Rendering
ItemRevision.IMAN_UG_altrep
ItemRevision.IMAN_UG_expression
ItemRevision.IMAN_UG_promotion
ItemRevision.IMAN_UG_scenario
ItemRevision.IMAN_UG_udf
ItemRevision.IMAN_UG_wave_geometry
ItemRevision.IMAN_UG_wave_part_link
ItemRevision.IMAN_UG_wave_position
ItemRevision.is_frozen
ItemRevision.is_modifiable
ItemRevision.item_master_tag
ItemRevision.last_release_status
ItemRevision.object_type
ItemRevision.owning_group
ItemRevision.owning_site
ItemRevision.owning_user
ItemRevision.process_stage
ItemRevision.process_stage_list
ItemRevision.protection
ItemRevision.publication_sites
ItemRevision.release_status_list
ItemRevision.release_statuses
ItemRevision.reservation
ItemRevision.structure_revisions
Item.items_tag:object_desc
Item.items_tag:object_name
Item.items_tag:object_string
Item.items_tag:object_type
Item.items_tag:owning_group
Item.items_tag:owning_site
Item.items_tag:owning_user
Item.items_tag:archive_date
Item.items_tag:backup_date
Item.items_tag:based_on
Item.items_tag:checked_out
Item.items_tag:configuration_object_tag
Item.items_tag:creation_date
Item.items_tag:current_job
Item.items_tag:date_released
Item.items_tag:expl_checkout
Item.items_tag:export_sites
Item.items_tag:has_variants
Item.items_tag:ics_classified
Item.items_tag:ics_subclass_name
Item.items_tag:is_frozen
Item.items_tag:is_modifiable
Item.items_tag:item_id
Item.items_tag:last_mod_date
Item.items_tag:last_mod_user
Item.items_tag:last_release_status
Item.items_tag:bom_view_tags
Item.items_tag:IMAN_manifestation

Item.items_tag:IMAN_master_form
Item.items_tag:IMAN_reference
Item.items_tag:IMAN_Rendering
Item.items_tag:IMAN_requirement
Item.items_tag:item_master_tag
Item.items_tag:process_stage
Item.items_tag:process_stage_list
Item.items_tag:protection
Item.items_tag:publication_sites
Item.items_tag:release_status_list
Item.items_tag:release_statuses
Item.items_tag:reservation
Item.items_tag:revision_list
SCOPE
User preference.
PortalDesignContextProductContextColumnsHiddenPrefWidth
DESCRIPTION
Specifies the widths of the columns for the hidden product context properties.
VALID
VALUES
(assuming an average character width).
DEFAULT
VALUES
15
14
6
10
12
4
10
19
9
6
9
13
9
10
8
11
6
11
10
9
7
13

13
13
6
9
11
15
8
10
8
16
10
14
12
10
10
12
8
14
18
19
19
18
20
18
19
18
19
16
18
25
19
18
20
20
18
19
19
24
16
19
16
19
20
24
20
23
22
20
21
22
21
19
23
16

21
23
21
17
20
SCOPE
User preference.
DesignContext context definition preferences

The preferences in this section control DesignContext context definition.
DesignContextShowClearanceDBMenu
DESCRIPTION
Determines whether the Clearance DB menu displays in the third window of
DesignContext.
VALID
VALUES
true The Clearance DB menu displays in the third window of
DesignContext.
false The Clearance DB menu does not display in the third window
of DesignContext.
DEFAULT
VALUES
false
SCOPE
All.
PortalDesignContextProductItemQuery
DESCRIPTION
Specifies the name of a saved query that allows a DesignContext user to find product
items based on site-specific criteria. You can use Teamcenter’s Query Builder to
create and save this query.
DesignContext displays all available product items in a table. If the number of
available product items exceeds the number of items that can be displayed per page,
Siemens PLM Software recommends that you expose fewer attributes on this query.
For example, create a query by Item Name with a built-in constraint on Item Type.
VALID
VALUES
Name of any saved query. Use Query Builder to list available saved queries.
DEFAULT
VALUES
Item Revision
SCOPE
User preference.

PortalDesignContextECObject.TYPE
DESCRIPTION
Specifies the workspace object type used to authorize design changes. Typically this
is an Change Item type, but this preference also allows you to integrate custom
change strategies, for example, using a form to authorize design changes.
If the type corresponds to objects extending from the item revision class, the primary
property displayed in DesignContext is the item ID that has an input field for the
item revision ID. In all other cases, the primary property is the name of the object.
VALID
VALUES
Any Teamcenter object type.
DEFAULT
VALUES
EngChange Revision
SCOPE
All.
PortalDesignContextECObject.WorkPartProperties
DESCRIPTION
Specifies a list of change object relationship properties for finding associated
work parts when a user adds or selects a new change object. Work parts are the
components the user intends to modify or to be the focus of a design session. The list
should specify all properties referencing related work parts that are to be added or
selected in the Work Parts list.
VALID
VALUES
Any property on the change object specified in the
PortalDesignContextECObject.TYPE preference, typically,
relationships available as properties. The relationships specified on
this preference are often the same as the properties specified on the
PortalDesignContextECObject.WorkPartRelationships preference. This is not
true, however, for the standard Change Viewer module.
DEFAULT
VALUES
solution_items
problem_items
affected_items
reference_items
addressed_by
SCOPE
All.

PortalDesignContextECObject.WorkPartRelationships
DESCRIPTION
Specifies Teamcenter relationships between work parts and the change objects that
authorize changes on these work parts. These relationships are used to find the
change objects when users add or select work parts.
VALID
VALUES
Any relationships on the change object specified in the
PortalDesignContextECObject.TYPE preference that reference work parts. The
relationships specified in this preference are often the same as the properties
specified on the PortalDesignContextECObject.WorkPartProperties
preference. This is not true, however, for the standard Change Viewer module.
DEFAULT
VALUES
EC_affected_item_rel
EC_solution_item_rel
EC_problem_item_rel
EC_reference_item_rel
EC_addressed_by_rel
SCOPE
All.
PortalDesignContextExcludedWorkPart.Types
DESCRIPTION
Specifies the item types excluded from the Work Part list in DesignContext. For sites
that have not yet migrated to Teamcenter Change Viewer, Siemens PLM Software
recommends excluding EngChange items.
VALID
VALUES
Any Teamcenter item type.
DEFAULT
VALUES
EngChange
SCOPE
All.
PortalDesignContextAllowNoWorkParts
DESCRIPTION
Specifies whether DesignContext requires users to enter at least one work part in
the Work Part list in the Context Definition window before displaying the Context
Configuration window.

When DesignContext is used only for modifying assemblies or components, you may
want to require users to have at least one work part in the Context Definition window
before the Context Configuration window displays; this may help inexperienced
users to work with the application.
Experienced users may use DesignContext for design review sessions of large pieces
of the product model or for product model reviews. This requires users to use filters
to configure a product context on the second window that they have yet to specify on
the third window.
VALID
VALUES
0 Requires at least one work part in the Work Parts list to
continue. DesignContext displays a warning that no work
parts are provided and displays the initial window again.
1 Allows users to continue to the Context Configuration window
without work parts in the Work Parts list.
DEFAULT
VALUES
1
SCOPE
All.
PortalDesignContextWIPRevRule
DESCRIPTION
Associates revision rules for which QPL builds exist to Work-In-Process (WIP)
revision rules. Creating this association activates WIP selection boxes on the
DesignContext Filter Configuration window.
VALID
VALUES
The syntax for this preference is:
PortalDesignContextWIPRevRule.rule-name.suffix=rule-name
rule-name is the name of any valid revision rule for which a QPL build exists and
suffix is one of the following constants:
MY_WIP
Specifies a revision rule that configures a WIP revision for rules the user owns.
This value activates the My WIP selection box.
GROUP_WIP
Specifies a revision rule that configures a WIP revision for rules the user’s group
owns. This value activates the Group WIP selection box.
WIP
Specifies a general revision rule. This value activates the WIP selection box.
DEFAULT
VALUES
PortalDesignContextWIPRevRule.Working; Any Status.WIP=
Latest Working

SCOPE
All.
PortalDesignContextIsInstallationAssemblyMethod
DESCRIPTION
Specifies the standard for identifying an installation assembly, that is, the assembly
that defines the existence and purpose of a component in a product structure. Each
appearance of a part can be defined in only one installation assembly at a time.
The values specify the name of a Teamcenter Java API method for the
DesignContextApplication class. The standard methods are listed below. Your
enterprise can create custom Java methods for use with this preference.
Siemens PLM Software recommends setting this preference.
VALID
VALUES
hasIRType
Returns the closest parent assembly up the tree that has a specific item type.
If you specify this value, you must also specify the required item type using the
PortalDesignContextIsInstallationAssemblyMethod.hasIRType.Type
preference.
has_bomline_prop
Returns the closes parent assembly up the tree that has a BOM line property.
isPrecise
Returns the first assembly down the path, beginning at the product item that has
a precise BOM View revision.
transformsComponents
Returns the first assembly down the path, beginning at the product item that
transforms components below it into product space.
DEFAULT
VALUES
hasIRType
SCOPE
All.
PortalDesignContextIsInstallationAssemblyMethod.hasIRType.Type
DESCRIPTION
Specifies the item type used to identify an installation assembly using the
hasIRType method.
For more information about using the hasIRType, see the description of the
PortalDesignContextIsInstallationAssemblyMethod preference.
For information about item types, see the Business Modeler IDE Guide.
Setting this preference is required when using the hasIRType method.

VALID
VALUES
Accepts a single string as a value. Can be any valid Teamcenter item type.
DEFAULT
VALUES
ItemRevision
SCOPE
All.
PortalDesignContextIsInstallationAssemblyMethod.has_bomline_prop.name
DESCRIPTION
Specifies the BOM line property name used to identify an installation assembly
using the has_bomline_prop method. Use this preference with the
PortalDesignContextIsInstallationAssemblyMethod.has_bomline_prop.value
preference to identify installation assemblies by BOM line name and value.
VALID
VALUES
Accepts a single string as a value. Can be any valid property name or runtime
property name on a BOM line.
DEFAULT
VALUES
None.
SCOPE
Site preference.
PortalDesignContextIsInstallationAssemblyMethod.has_bomline_prop.value
DESCRIPTION
Specifies the BOM line property value used to identify an installation assembly
using the has_bomline_prop method. Use this preference with the
PortalDesignContextIsInstallationAssemblyMethod.has_bomline_prop.name
preference to identify installation assemblies by BOM line name and value.
VALID
VALUES
Accepts a single string as a value. Can be any valid property value or runtime
property value on a BOM line.
DEFAULT
VALUES
None.
SCOPE
Site preference.

PortalDesignContextFindInstallationTreeWalkIncrement
DESCRIPTION
Specifies the direction the tree is maneuvered through to find the installation
assembly for the specified BOM line.
VALID
VALUES
-1 Traverses down from the top of the tree towards the BOM line.
1 Traverses up from the BOM line towards the root.
DEFAULT
VALUES
-1
SCOPE
All.
PortalDesignContextSupportInstallationAssemblySelection
DESCRIPTION
Determines whether installation assemblies can be selected from search results.
VALID
VALUES
TRUE Installation assemblies can be selected from search results.
FALSE Installation assemblies cannot be selected from search results.
DEFAULT
VALUES
FALSE
SCOPE
All.
PortalDesignContextUseUnconfigurableSearchResults
DESCRIPTION
Determines whether unconfigurable search results display in search results.
Unconfigurable search results always prompt an error message (such as No revision
found for current revision rule). This preference determines whether, after the error
message displays, the unconfigurable search results display in the search results list.
VALID
VALUES
TRUE Unconfigurable search results display.
FALSE Unconfigurable search results do not display.
DEFAULT
VALUES
FALSE
SCOPE
All.

DesignContext filter configuration preferences

The preferences in this section control DesignContext filter configuration.
PortalDesignContextAttributeSchemaSuppressedAttributes
DESCRIPTION
Specifies QPL attributes to suppress in the DesignContext interactive filters. Some
QPL attributes may not be required for interactive filters. You can reduce the
number of attributes listed in the filter user interface by listing these attributes
on this preference.
VALID
VALUES
Any QPL-provided attribute name.
DEFAULT
VALUES
UGOCC_SUBFILEID
UGOCC_SFID
UGOCC_XFM
UGOCC_TREE_L
UGOCC_TREE_R
UGOCC_PARENT
UGOCC_PATH
UGOCC_JTFILE
SCOPE
Site preference.
PortalDesignContextQPLServers
DESCRIPTION
Defines the global QPL servers. If the same application is used in multiple QPL
servers, the first match in this list is used for searching DesignContext.
VALID
VALUES
Valid host name and port number. The host name must be the machine on which
the QPL server runs. The port number must be the port that listens to the QPL
server request.
DEFAULT
VALUES
None.
SCOPE
Site preference.
PortalDesignContextSearchEnginePreference
DESCRIPTION
Specifies the search engine referenced by DesignContext.

VALID
VALUES
QPLSearchEngineFactory
QPLJTSearchEngineFactory
AppearanceSearchEngineFactory
CachelessSearchEngineFactory
Note
The value must match one of the keywords defined in the
\com.teamcenter.rac.tcapps\com\teamcenter\rac\designcontext\
designcontext.properties file. If the value set for this preference is not
found in the designcontext.properties file, the default value for this
preference is used.
DEFAULT
VALUES
QPLSearchEngineFactory
SCOPE
All.
DesignContextIncludeSubComponentsForSpatialSearch
DESCRIPTION
Determines whether to inherit the geometry of subcomponents when searching the
vicinity of assemblies. Set this preference to FALSE to search for nearby parts in
the vicinity of geometry at the assembly level, for example, when working with
wire harnesses.
VALID
VALUES
TRUE Includes subcomponents when searching the vicinity of
assemblies.
FALSE Does not include subcomponents when searching the vicinity of
assemblies. Use this setting when searching for nearby parts
at the assembly level.
DEFAULT
VALUES
TRUE
SCOPE
All.
DesignContext_ItemID_Query_lookup_string
DESCRIPTION
Determines the I18n key used to retrieve the internationalized name of the saved
query used to find work parts. DesignContext evaluates this preference when the
PortalDesignContextProductItemQuery preference is not set or points to an
inaccessible query.

VALID
VALUES
Accepts a single string as a value. Must be a valid user entry name which matches
the internationalized name for the ItemID lookup key.
DEFAULT
VALUES
k_find_item_name
This key maps to ItemID in the English locale.
SCOPE
All.
DesignContextMaximumShownTabs
DESCRIPTION
Determines the maximum number of search tabs which are stored and display in the
Filter Configuration window of DesignContext.
VALID
VALUES
Single, positive integer.
DEFAULT
VALUES
5
SCOPE
User preference.
PortalDesignContextAlwaysResetFilterConfigurationPanel
DESCRIPTION
Determines whether the third window is always reset when transitioning from
the second window of DesignContext.
VALID
VALUES
TRUE The third window is always reset when transitioning from the
second window.
FALSE The third window is not reset when transitioning from the
second window.
DEFAULT
VALUES
TRUE
SCOPE
All.

DesignContextPreciseRevRule
DESCRIPTION
Enables searching the product structure based on precise revision rules when
an appearance set is not available for the required precise revision rule, but an
appearance set is available for a similar revision rule containing all the same clauses
except the precise clause.
The search is performed upon a product configuration similar, but not identical to,
the product configuration configured in DesignContext.
Use this method when the difference between the two revision rules only affects
piece part revisions that are very similar in form, fit and function.
When the difference between the two revision rules affect assembly revisions,
consider that different assembly revisions may define different structures and/or
different component positions. In this case, enabling this preference can cause the
search to return misleading results.
Set this preference using the following format:
DesignContextPreciseRevRule.rule-name.suffix
rule-name is the name of the similar revision rule containing all the same clauses
except the precise clause and suffix is PRECISE. For example:
DesignContextPreciseRevRule.Alpha Best_App.PRECISE=
Alpha Best
VALID
VALUES
Accepts a single string as a value. Must be the name of a valid revision rule.
DEFAULT
VALUES
PRECISE
SCOPE
User preference.
DesignContext interoperability preferences

The preferences in this section control DesignContext interoperability.
PortalDesignContextCADbookmarkType
DESCRIPTION
Specifies a bookmark type for the CAD application used with DesignContext.
Users can view this preference and set it for their environments using the
Edit→Options→DesignContext menu command.
VALID
VALUES
1 Generates a bookmark file that can be read by a CAD
application.

2 Generates a bookmark that can be read by both a CAD

application and a visualization application. This setting
expands the entire assembly structure into the bookmark,
but marks all but the selected BOM lines with the
VISUALIZE=NO flag.
16 Generates a bookmark that can be read by a visualization
application and contains only the selected BOM lines and
traverses the entire assembly but adds the children of selected
assemblies to the bookmark for display by the visualization
application. Use this bookmark type for visualizing very large
assemblies. You can use OR 16 with 2.
32 Generates a bookmark that excludes children of explicitly
selected children in a visualization application. The
visualization application displays a tree that does not have
the children of the selected subassemblies. If 32 is specified
without 16, 32 is ignored. You can use OR 32 with 18.
64 Generates a bookmark that includes the children of explicitly
selected assemblies but marks them with the VISUALIZE=NO
flag so they are not loaded in the visualization application.
DEFAULT
VALUES
50
Derived from 2 + 16 + 32.
SCOPE
User.
PortalDesignContextVISbookmarkType
DESCRIPTION
Specifies a bookmark type for the visualization application used with DesignContext.
Users can view this preference and set it for their environments using the
Edit→Options→DesignContext→General menu command.
VALID
VALUES
1 Generates a bookmark file that can be read by a CAD
application.
2 Generates a bookmark that can be read by both a CAD
application and a visualization application. This setting
expands the entire assembly structure into the bookmark,
but marks all but the selected BOM lines with the
VISUALIZE=NO flag.
16 Generates a bookmark that can be read by a visualization
application and contains only the selected BOM lines and
traverses the entire assembly but adds the children of selected
assemblies to the bookmark for display by the visualization
application. Use this bookmark type for visualizing very large
assemblies. You can use OR 16 with 2.

32 Generates a bookmark that excludes children of explicitly

selected children in a visualization application. The
visualization application displays a tree that does not have
the children of the selected subassemblies. If 32 is specified
without 16, 32 is ignored. You can use OR 32 with 18.
64 Generates a bookmark that includes the children of explicitly
selected assemblies but marks them with the VISUALIZE=NO
flag so they are not loaded in the visualization application.
DEFAULT
VALUES
50
Derived from 2 + 16 + 32.
SCOPE
User.
DesignContext_PSE_Synchronization
DESCRIPTION
Determines whether DesignContext search results are automatically synchronized
with Structure Manager, in which case the resulting BOM lines are automatically
selected in Structure Manager.
VALID
VALUES
TRUE DesignContext search results are automatically synchronized
with Structure Manager. The BOM lines returned in the search
results are automatically selected in Structure Manager.
FALSE DesignContext search results are not automatically
synchronized with Structure Manager. No BOM lines are
selected in Structure Manager.
DEFAULT
VALUES
FALSE
SCOPE
User preference.
TC_show_open_in_nx_button
DESCRIPTION
Specifies whether the Open in NX button is displayed for interoperation with NX.
VALID
VALUES
true Displays the Open in NX button in DesignContext.
false Does not display the Open in NX button in DesignContext.
DEFAULT
VALUES
false

SCOPE
User preference.
DesignContext performance tuning preferences

The preferences in this section control the tuning of DesignContext performance.
RDVClearanceProxyServers
DESCRIPTION
Specifies the database connection used by the clearance proxy server to connect to
the clearance database.
VALID
VALUES
DATASOURCE=<System-running-clearanceDB-proxy>:
<Port-for-clearanceDB-proxy-server>:CONNECT_DATA=<Oracle-connection-name>:
FILTER_NAME=<blank>
An example value is cleardb:7206:CLDB:xyzFilter.
DEFAULT
VALUES
None.
SCOPE
Site preference.
NOTES
• The FILTER_NAME field is optional and specifies the clearance calculator in
the clearance database.
• Multiple values may be entered if the site has multiple proxies.

For more information, see the Clearance Database Administrator’s Guide in the
Lifecycle Visualization library.
RESTRICTIONS
This preference must be set to use the integrated clearance management feature
in DesignContext.
PortalDesignContextMaxMatchingObjects
DESCRIPTION
Specifies the maximum number of components that a query can match (for example,
work parts, change items, or CR jobs). Input the user provides in the DesignContext
Context Definition pane may cause new Teamcenter objects to be loaded.
Note
If the user enters wildcards in any fields of the Context Definition pane, or
while executing the product item query, response times may be unacceptable.
If the number of matching components exceeds the limit, DesignContext displays

a warning, and users can provide more restrictive search criteria. Users

can view this preference and set it for their environments by choosing the
VALID
VALUES
Accepts any positive integer. Siemens PLM Software recommends using the default
initially and not exceeding 1000.
DEFAULT
VALUES
40
SCOPE
User preference.
PortalDesignContextMaxMatchingBOMLines
DESCRIPTION
Specifies the maximum search limit for searches in DesignContext’s Filter
Configuration pane. If the number of matches exceed this number a confirmation
window appears. The user can cancel or proceed at this point. Use this preference is
to avoid long searches that accidentally match a very large number of components.
If the number of matching components exceeds the limit, DesignContext displays
a confirmation message allowing users to either continue or cancel the query.
Users can view this preference and set it for their environments by choosing the
VALID
VALUES
Accepts any positive integer. Siemens PLM Software recommends using the default
initially and not exceeding 1000.
DEFAULT
VALUES
300
SCOPE
User preference.
PortalDesignContextSetVariantRulesMaxTargetAppearances
DESCRIPTION
Specifies the maximum number of target appearances for the Valid Overlays
Only button on the DesignContext Filter Configuration window, thus limiting
the processing time spent determining and evaluating the set of variant rules
configuring a set of target appearances.
Users can view this preference and set it for their environments choosing the

Note
The setting of this preference may affect the behavior
of the RDV_variant_overlays_mode preference. The
RDV_variant_overlays_mode preference defines the algorithm
used to determine valid overlay only (VOO) in DesignContext’s Filter
Configuration pane. When the RDV_variant_overlays_mode preference is
set to 2, it uses dynamic mode.
VALID
VALUES
Any positive integer; integers higher than 1000 are unlikely. Siemens PLM Software
recommends using the default initially.
DEFAULT
VALUES
5
SCOPE
User preference.
Using DesignContext composite properties

A composite property of an object defines a path to associated objects, resulting
in the evaluation of a property on the associated objects. Each step in the chain
de-references the next related object in the path.
The syntax for defining composite properties is:
[object-type-name.][reference-property
[(criteria-property=criteria-value
[,criteria-property=criteria-value]):]
[reference-property[(criteria-property=criteria-value
[, criteria-property=criteria-value])]:]]property
object-type-name
Specifies a Teamcenter object type name.
reference-property
Specifies a typed reference, untyped reference, typed relation, or untyped
relation.
criteria-property
Specifies any valid composite property (implemented using recursion). It is a
criteria list in case the reference-property value is ambiguous.
property
Specifies any property that the Java API getProperty method on the rich client
The following example evaluates the product_year attribute on the item revision
master of an item revision:
item_master_tag:product_year
The following example evaluates the Project_ID attribute on the item master of the
item of an item revision:

item_tag:item_master_tag:Project_ID
The following example evaluates the MyCustomProperty attribute of all objects

in the IMAN_master_form pseudofolder of the item of an item revision that
have the MyCustomItemForm object type. The example returns all values in a
comma-separated list:
item_tag:IMAN_master_form:(object_type=MyCustomItemFor:MyCustomProperty
The following example evaluates the Project_ID property on each item revision
of a specified item:
ItemRevision Master.revision_list:item_master_tag:Project_ID
Note
If three item revisions share the same Project_ID of 3200, the duplicated
values are shown as 3200(x3). A list of values is separated by the substring
comma (,). The item revision master prefix specifies that the physical property
is on an object of type item revision master.
Multi-Structure Manager preferences

The collaboration context feature allows Teamcenter to share data with another
application. The shared data can be managed or modified by either application and
changes are available in both environments. This functionality allows you to manage
any of the structure types compatible with Teamcenter, including product structures
and manufacturing process structures.
Allocations are one aspect of collaboration context. Allocations represent a
directional relationship between specific instances of an item revision in one product
structure and an item revision in a related structure. Typically you relate the
functional structure to the logical structure or the logical structure to the physical
structure. These relationships may span multiple configurations and revisions of
both structures. They may change according to the overall configurations or the
specific revisions that are configured into the structures. Since allocations are
specific to a particular context, all associated allocations are collected in a set called
an allocation context. An allocation context consists of an allocation map object that
is a subclass of an item. Administrators specify different types of allocation map
objects representing different business intents.
Use allocation preferences to determine allocation behavior such as how allocations
are treated during the revision process and to specify permitted allocation
components.
ALLOC_Group_Allocation_Types
DESCRIPTION
For use with allocation functionality. Specifies the allocation types that can be used
in the specified allocation map. For example, ensure the Allocation_One allocation
type is created only in association with the AllocationMap_one allocation map
by setting this preference to:
AllocationMap_one:Allocation_One

For more information about working with allocation maps, see the Multi-Structure
Manager Guide.
VALID
VALUES
Allocation map type:Allocation type,Allocation type
Where Allocation map type is a valid Teamcenter allocation map type, and all
Allocation type entries are valid Teamcenter allocation types.
DEFAULT
VALUES
AllocationMap:Allocation
SCOPE
Site preference.
ALLOC_Product_Representation_Types
DESCRIPTION
For use with allocation functionality. Specifies which BOM view types can be used to
create allocations in the specified allocation map. For example, ensure allocations
are created only between MEProcess and View types for the AllocationMap_one
allocation context by setting this preference to:
AllocationMap_one:MEProcess,View
For more information about working with allocation maps, see the Multi-Structure
Manager Guide.
VALID
VALUES
Allocation map type:View type1,View type2
Where Allocation map type is a valid Teamcenter allocation map type, and all View
type entries are valid subtypes of Teamcenter views.
DEFAULT
VALUES
AllocationMap:view,CAEAnalysis,MEProcess,MESetup
SCOPE
Site preference.
ALLOC_Target_Occurrence_Types
DESCRIPTION
For use with allocation functionality. Specifies which components can be used as
target components for a given allocation type.
For more information about working with source and target components for
allocations, see the Multi-Structure Manager Guide.
VALID
VALUES
Allocation type::Target component type

Where Allocation type is a valid Teamcenter allocation type, and Target component
type is a valid Teamcenter object type used in a product structure.
DEFAULT
VALUES
Allocation:Item,PSConnection,PSSignal,RouteLocation,GeneralDesign Element,
GeneralDesignElementLink
SCOPE
Site preference.
ALLOC_Source_Occurrence_Types
DESCRIPTION
For use with allocation functionality. Specifies the components that can be used as
source components for a given allocation type.
For more information about working with source and target components for
allocations, see the Multi-Structure Manager Guide.
VALID
VALUES
Allocation type::Source component type
Where Allocation type is a valid Teamcenter allocation type, and Source component
type is a valid Teamcenter object type used in a product structure.
DEFAULT
VALUES
Allocation:Item,PSConnection,PSSignal,RouteLocation,GeneralDesign Element,
GeneralDesignElementLink
SCOPE
Site preference.
ALLOC_source_target_cardinality
DESCRIPTION
For use with allocation functionality. Specifies the cardinality permitted between a
given allocation type and other product structure object types.
Note
Specify valid target components for a particular allocation type
using the ALLOC_Target_Occurrence_Types preference. Specify
valid source components for a particular allocation type using the
ALLOC_Source_Occurrence_Types preference.
The system supports multiple sources and targets for allocation using cardinality
functionality. The system supports the following allocation relationships:
One-to-one
Many-to-one
One-to-many
Many-to-many

Example
For example, you can use this preference to enforce a cardinality allowing the
Network_Port type allocation to participate only in one-to-one relationships.
Allocations using this type can contain only a single source and a single
target. To do so, set this preference to:
Network_Port::1,1
For more information about working with cardinality of allocations, see the
Multi-Structure Manager Guide.
VALID
VALUES
Allocation subtype::1,1 Where Allocation subtype specifies the allocation type; this
specified allocation type can only be used in one-to-one
relationships.
Allocation subtype::1,n Where Allocation subtype is a valid Teamcenter object
type; this specified object type can be used in one-to-many
relationships.
Allocation subtype::n,1 Where Allocation subtype is a valid Teamcenter object
type; this specified object type can be used in many-to-one
relationships.
Allocation subtype::n,n Where Allocation subtype is a valid Teamcenter object type;
this specified object type can be used in many-to-many
relationships.
DEFAULT
VALUES
Allocation::n,n
SCOPE
Site preference.
ALLOC_map_copy_allocations
DESCRIPTION
For use with allocation functionality. Determines whether the allocation set is
carried forward when the allocation map is saved as a new allocation map, or revised.
By default, the allocation set is carried forward during either of these actions.
Prevent the allocation set from being carried forward by setting this preference with
the names of the revision action (saveAs, or Revise) which you do not want to
carry forward the allocation set.
For more information about working with allocations, see the Multi-Structure
Manager Guide.
VALID
VALUES
saveAs The allocation set is not carried forward when the allocation
map is saved as a new allocation map.
Revise The allocation set is not carried forward when the allocation
map is revised.

DEFAULT
VALUES
saveAs
Revise
SCOPE
Site preference.
Default_StructureContext_Type
DESCRIPTION
Determines which type of structure context is created when saving a loaded object
as a context.
For more information, see the Multi-Structure Manager Guide.
VALID
VALUES
Accepts one or more strings as values; each string must be a valid type and be of the
following format:
item_type:structure_context_type
DEFAULT
VALUES
MEProcess:MEProcessContext
MEOP:MEProcessContext
MEWorkarea:MEPlantContext
Item:MEProductContext
SCOPE
Site preference.
Structure Manager preferences

Structure Manager allows you to create generic product structures that can be
configured to show the product structure that is in production, the product structure
that was effective on a certain date, a particular customer variant, and so on. This is
the basis of the Teamcenter configuration functionality. By creating a single generic
structure that can be configured according to a particular user’s needs, you can avoid
duplicating assembly structure, with all the associated problems of maintenance,
redundant information, and complexity of where-used searches.
Structure Manager behavior preferences

Use Structure Manager behavior preferences to customize the application’s behavior.
These preference are typically implemented as site preferences or group preferences.

BOM_objects_excluded_from_split
DESCRIPTION
Contains a list of object types and subtypes that are excluded from a Split
Occurrence operation.
VALID
VALUES
object type or subtype.
DEFAULT
VALUES
Connection
Signal
Software
SCOPE
Site preference.
CFM_ITEM_TYPE_RULE_INCLUDE_SUB_TYPES
DESCRIPTION
Determines whether an assembly containing subtypes can be configured based on
the base type’s revision rule.
For example, given the following type hierarchy
PART
HYD_PART
ELE_PART
PUMP_PART
when the following revision rule is applied

has item type (PART) { AP status, by unit #}
the revision rule for the item type PART applies to the base type and all its subtypes
if this preference is set to true.
VALID
VALUES
true Allows users to configure assemblies when the base item types
(item type of each line in the assembly), or one of the subtypes
matches the Has Item Type revision rule entry.
false Allows user to configure assemblies only when the base item
types (item type of each line in the assembly) matches the Has
Item Type revision rule entry.
DEFAULT
VALUES
false
SCOPE
Site preference.

GDE_objects_with_integer_quantity
DESCRIPTION
Contains a list of general design element (GDE) objects or subclasses for which the
user can specify only an integer value as the quantity.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid GDE object or
subclass.
DEFAULT
VALUES
Interface
SCOPE
Site preference.
PSE_check_read_access_for_Rev_Rule_entry
DESCRIPTION
Determines if Teamcenter evaluates revision rules according to the user’s read
access, allowing the optional display of the first configured entry to which the user
has access.
VALID
VALUES
true Revision rules are evaluated according to read access and
Teamcenter displays the first accessible revision. If no revisions
are accessible, Teamcenter displays an UNREADABLE tag.
false Revision rules are not evaluated according to read access. If
the first configured revision is not accessible, Teamcenter
displays it as UNREADABLE.
DEFAULT
VALUES
False
SCOPE
Site preference.
NOTES
This preference only affects the evaluation of imprecise entries, not precise entries.
Only Working, Status, Latest and Override revision rule entries return
read-accessible item revisions.
PSE_default_view_type
DESCRIPTION
Determines which view type preference DesignContext and Structure Manager
queries use. By default, the system uses the TC_NX_View_Type preference, which
in turn, is set to view by default.

VALID
VALUES
A single string as a value; the string must be a valid Teamcenter preference, set to a
valid query type.
DEFAULT
VALUES
TC_NX_View_Type
SCOPE
All.
PSE_Display_Pending_Edits
DESCRIPTION
Determines whether pending edit markup functionality is enabled for editing actions
such as adding, deleting, or modifying property attributes. These pending edits can
be saved to the database, cancelled, or reversed.
Note
This editing mode is not available when an absolute occurrence or incremental
change context is set. BOM compares cannot be run on objects containing
pending edits.
VALID
VALUES
true Pending edit markup is enabled for editing actions.
false Pending edit markup is not enabled for editing actions.
DEFAULT
VALUES
false
SCOPE
All.
PSE_expand_on_open
DESCRIPTION
Determines whether the root node of an assembly is expanded when opened in
Structure Manager, Manufacturing Process Planner, and Multi-Structure Manager.
VALID
VALUES
0 The root node of an assembly is not expanded when opened
in Structure Manager, Manufacturing Process Planner, and
Multi-Structure Manager.
1 The root node of an assembly is expanded when opened in
Structure Manager, Manufacturing Process Planner, and
DEFAULT
VALUES
1

SCOPE
Site preference.
PSE_ROLL_UP_TEMPLATES
DESCRIPTION
Determines which rollup templates are kept as user favorites. This preference is set
automatically when a user selects favorites using the Roll Up Templates Manager.
VALID
VALUES
The system automatically adds values to this preference when a user selects
favorites using the Roll Up Templates Manager.
DEFAULT
VALUES
None.
SCOPE
User preference.
ROLL_UP_QUANTITY_FLAG
DESCRIPTION
Determines if the BOM properties rollup feature includes the root line quantity in
the calculation when rolling up property values in a structure.
VALID
VALUES
true Teamcenter does not include the root line quantity value when
performing rollup calculations.
false Teamcenter includes the root line quantity value when
performing rollup calculations.
DEFAULT
VALUES
true
SCOPE
Site or user logical preference.
PSEshowToolBar
DESCRIPTION
Controls the default setting of the Display→Show Toolbar menu command.
VALID
VALUES
YES Displays the toolbar.
NO Does not display the toolbar.
DEFAULT
VALUES
YES

SCOPE
User.
PS_Find_Number_Validation
DESCRIPTION
Determines whether the system validates find numbers. If validation is enabled
with this preference, an error displays when the find number is zero or is not unique
within the parent structure.
A find number is a unique number assigned to each line in the product structure.
When users add an item to the product structure, the line receives the next available
find number in the defined sequence. Users can rearrange the structure in find
numbers by clicking the Find Number column header. This rearrangement persists
for future Structure Manager sessions.
VALID
VALUES
true The system validates the Find Number.
false The system does not validate the Find Number.

DEFAULT
VALUES
false
SCOPE
Site preference.
PS_new_seqno_mode
DESCRIPTION
Determines how new find numbers are allocated when items are inserted into a
BOM view or BOM view revision.
VALID
VALUES
new Every item is given a new find number within the current
BOM view, starting with 10 and increasing by 10.
existing If an item of the same ID already exists in the BOM view, the
inserted item is given the same find number. If not, the item is
given a new find number as above.
none No find number is allocated to items inserted into a BOM view;

users can add their own later.
DEFAULT
VALUES
new
SCOPE
Site

PS_replace_with_substructure
DESCRIPTION
Determines whether substructures below the selected node can be replaced, along
with the selected node.
Users can replace an item representing a node in the structure with another item.
All data associated with the original node is preserved. This preference determines
whether substructures can also be replaced.
For more information about replacing nodes in product structures, see the Structure
Manager Guide.
VALID
VALUES
true The selected node and its entire substructure (if any) are
replaced without prompting.
false If the selected node contains a substructure, the system
displays an error message and does not complete the
replacement action.
DEFAULT
VALUES
false
SCOPE
All.
PS_wu_configd_imprecise_only
DESCRIPTION
Determines whether parent item revisions are included in Where Used search
results, regardless of whether they are configured by the revision rule.
Where Used search results are 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.
VALID
VALUES
true Search results omit parent item revision objects that are not
configured by the revision rule. This may occur if the specified
revision rule contains only non-precise entries.
Note
This setting is equivalent to the default behavior in
Teamcenter Engineering 9.1 and earlier releases.

false Search results include all parent item revision objects,

regardless of whether they are configured by the revision rule.
For example, use this setting to make a where-used query
on Part1–A to identify every occurrence where Part1 is
used with A as its configured revision. You obtain the same
results whether you query one level at a time or all levels
simultaneously, including with mixed precise and imprecise
structures. You do not find any imprecise parent assemblies
that are not configured by the selected revision rule.
DEFAULT
VALUES
false
SCOPE
Site preference.
PUBLISH_AlignableSourceTypes
DESCRIPTION
Determines which types are PublishLink sources. A PublishLink copies
information from a source occurrence to a target occurrence. For example, transform
data is copied from a design occurrence to a part occurrence.
VALID
VALUES
Accepts multiple strings values. Each string must be a valid item type. The string
can also contain subtypes of the item. For example:
Item,Design
DEFAULT
VALUES
Item,Design
SCOPE
Site preference.
PUBLISH_AlignableTargetTypes
DESCRIPTION
Determines which types are PublishLink targets. A PublishLink copies
information from a source occurrence to a target occurrence. For example, transform
data is copied from a design occurrence to a part occurrence.
VALID
VALUES
Accepts multiple strings values. Each string must be a valid item type. The string
can also contain subtypes of the item. For example:
Item,Part
DEFAULT
VALUES
Item,Part

SCOPE
Site preference.
TC_BOM_Precision_Preference
DESCRIPTION
Determines whether a new BOM view or BOM view revision should be precise or
imprecise. The Add Design To Product wizard creates new occurrences based on
this preference setting.
This preference can be set in the Options dialog box of either the rich client or the
thin client.
VALID
VALUES
Precise New BOM views and BOM view revisions are created precise.
Imprecise New BOM views and BOM view revisions are created
imprecise.
DEFAULT
VALUES
Imprecise
SCOPE
User preference.
TC_show_open_in_pse_button
DESCRIPTION
Determines whether the Open in Structure Manager button displays in the toolbar.
VALID
VALUES
true Displays the button in the toolbar.
false Does not display the button in the toolbar.
DEFAULT
VALUES
false
SCOPE
Group preference.
TC_config_rule_name
DESCRIPTION
Specifies the default revision rule used when selecting the product context based on
the chosen product item. If not defined, Latest Working/Any Release Status is
used.
VALID
VALUES
One or more strings as values; each string must be a valid revision rule.

DEFAULT
VALUES
Latest Working
SCOPE
Group preference.
Vis_InterOptWithProductViewDataset
DESCRIPTION
Determines whether product view datasets associated with item revisions and BOM
views are sent to Teamcenter’s lifecycle visualization along with the item revisions
and BOM views.
VALID
VALUES
TRUE Product view datasets associated with item revisions and BOM
views are sent to Teamcenter’s lifecycle visualization along
FALSE Product view datasets associated with item revisions and BOM
views are not sent to Teamcenter’s lifecycle visualization along
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
VISTopLevelRef_relation_primary
DESCRIPTION
Contains a list of valid primary object types for the VISTopLevelRef relation.
VALID
VALUES
SnapshotViewData3D product view object types are valid for this relation.
DEFAULT
VALUES
SnapshotViewData
SCOPE
Site preference.
Structure Manager column preferences

Use Structure Manager column preferences to customize the number of Structure
Manager columns displayed to the user and the order that they appear. These
preferences are typically implemented as user preferences or group preferences.

PortalPSEColumnsShownPref
DESCRIPTION
Specifies the list of Structure Manager columns displayed from left-to-right.
To display the Explore Checked Out property, add the bl_rev_expl_checkout
value to this list.
VALID
VALUES
Accepts multiple strings as values. It must be a valid BOM line property.
DEFAULT
VALUES
bl_indented_title
bl_item_object_type
bl_config_string
bl_sequence_no
bl_part_source
bl_uom
bl_ref_designator
bl_all_notes
bl_variant_state
bl_rev_has_variants
bl_variant_condition
bl_is_occ_configured
bl_has_date_effectivity
bl_rev_checked_out
fnd0bl_has_active_markup
SCOPE
Site preference.
PortalPSEShownColumnsWidthPref
DESCRIPTION
PortalPSEColumnsShownPref preference.
VALID
VALUES
Accepts multiple strings as values. Each value must be a positive integer, and align,
in order, with a value defined in the PortalPSEColumnsShownPref preference.
DEFAULT
VALUES
41
15
18
16
9
5
3

9
19
4
4
16
4
4
SCOPE
Site preference.
PSESearchColumnsShownPref
DESCRIPTION
Determines which columns are displayed in the search results table, in left-to-right
order. Column width is defined using the PSESearchShownColumnWidthsPref
preference.
VALID
VALUES
One or more strings as values; each string must be a valid Structure Manager
attribute.
DEFAULT
VALUES
bl_item_object_name
bl_item_item_id
bl_item_object_desc
bl_formatted_parent_name
bl_formatted_ancestor_name
bl_appearance_validity_in
bl_appearance_validity_out
SCOPE
User preference.
PSESearchShownColumnWidthsPref
DESCRIPTION
Determines column width for each column defined in the
PSESearchColumnsShownPref preference.
VALID
VALUES
One or more integers as values; each integer determines the column width in
characters. The first value listed in this preference determines the column width
of the first column defined in the preference, PSESearchColumnsShownPref
and so on.
DEFAULT
VALUES
30
20

30
32
32
20
20
SCOPE
User preference.
variant_item_column_width
DESCRIPTION
Determines the width of the item column in the Variant Rule dialog box. There is
no mechanism to reorder the columns.
VALID
VALUES
A positive integer.
DEFAULT
VALUES
20
SCOPE
User preference.
variant_option_column_width
DESCRIPTION
Determines the width of the option column in the Variant Rule dialog box. There is
VALID
VALUES
A positive integer.
DEFAULT
VALUES
24
SCOPE
User preference.
variant_description_column_width
DESCRIPTION
Determines the width of the description column in the Variant Rule dialog box.
There is no mechanism to reorder the columns.
VALID
VALUES
A positive integer.

DEFAULT
VALUES
20
SCOPE
User preference.
variant_value_column_width
DESCRIPTION
Determines the width of the value column in the Variant Rule dialog box. There is
VALID
VALUES
A positive integer.
DEFAULT
VALUES
25
SCOPE
User preference.
variant_state_column_width
DESCRIPTION
Determines the width of the state column in the Variant Rule dialog box. There is
VALID
VALUES
A positive integer.
DEFAULT
VALUES
30
SCOPE
User preference.
variant_values_column_width
DESCRIPTION
Determines the width of the values column in the Variant Rule dialog box. There is
VALID
VALUES
A positive integer.
DEFAULT
VALUES
30

SCOPE
User preference.
vrule_reln_column_width
DESCRIPTION
Determines the width of the variant rule release column in the Variant Rule dialog
box. There is no mechanism to reorder the columns.
VALID
VALUES
A positive integer.
DEFAULT
VALUES
20
SCOPE
User preference.
Structure Manager display preferences

Use Structure Manager display preferences to customize the appearance of Structure
Manager. These preferences are typically implemented as user preferences or
group preferences.
Valid values for color preferences are limited to the colors defined for your system
at the X-Window System level.
application name.ic_icon_level
DESCRIPTION
Determines which incremental change (IC) context icons, if any, are displayed.
Display of IC context icons can be determined for various rich client applications,
such as Structure Manager, Manufacturing Process Planner, and Multi-Structure
Manager.
Siemens PLM Software recommends setting this preference by selecting the Display
Icons option from the Incremental Change command in the Tools menu of the
relevant application. Check the level to which you want icons displayed. The rich
client automatically inserts the name of the application at the beginning of the
preference name.
VALID
VALUES
None Displays no context icons.
All Displays all context icons.
Current Displays icons for only the context currently being edited.
DEFAULT
VALUES
All

SCOPE
User preference.
application name.ic_show_remove_icons
DESCRIPTION
Determines whether the Remove incremental change icon is displayed. Display
of this icon can be determined for various rich client applications, such as Structure
Manager, Manufacturing Process Planner, and Multi-Structure Manager.
Siemens PLM Software recommends setting this preference by selecting the
Display Icons option from the Incremental Change command in the Tools menu
of the relevant application. Check the Hide Remove Icons entry. The rich client
automatically inserts the name of the application at the beginning of the preference
name.
VALID
VALUES
True Displays the Remove incremental change icon in the BOM lines of the
specified application.
False Does not display the Remove incremental change icon in the BOM lines
of the specified application.
DEFAULT
VALUES
All
SCOPE
User preference.
BOMCompareVisibleModes
DESCRIPTION
Determines which compare modes display in the BOM Compare dialog box and
are returned by the BOM_compare_ask_modes ITK function. If this preference
is removed, the default setting is used.
For more information about comparing product structures, see the Structure
Manager Guide.
VALID
VALUES
IMAN_bcm_single_level_seq
IMAN_bcm_single_level
IMAN_bcm_var_level_seq
IMAN_bcm_var_level
IMAN_bcm_ext_var_level_seq
IMAN_bcm_ext_var_level
IMAN_bcm_lowest_level_seq
IMAN_bcm_lowest_level
IMAN_bcm_every_level
Use the following compare modes for item-based logical BOM (LBOM) compares:

IMAN_lbcm_var_level
IMAN_lbcm_single_level
IMAN_lbcm_lowest_level
Use the following compare modes for occurrence-based logical BOM (LBOM)
compares:
IMAN_lbcm_var_level_occ
IMAN_lbcm_single_level_occ
Note
Any custom compare mode must also be listed as a value in order for the mode
to display in the BOM Compare dialog box.
DEFAULT
VALUES
IMAN_bcm_single_level_seq
IMAN_bcm_single_level
IMAN_bcm_var_level_seq
IMAN_bcm_var_level
IMAN_bcm_lowest_level
IMAN_lbcm_single_level_occ
SCOPE
User preference.
BOM_MARKUP_ADD_FONT_STYLE
DESCRIPTION
Specifies the text font style when a user adds a markup to a BOM line.
VALID
VALUES
0 (plain text)
1 (bold text)
2 (italic text)
3 (bold and italic text)
DEFAULT
VALUES
0
SCOPE
Site preference.
BOM_MARKUP_ADD_FOREGROUND
DESCRIPTION
Specifies the color of the markup text added to a BOM line by a user.
VALID
VALUES
Specifies three color values in order of precedence in the format N1,N2,N3, where
each value is an integer in the range 0 to 255. Enter color values in red, green,

blue (RGB) code, where, for example, 0, 0, 0 represents the color black and 0, 255,
255 represents the color aqua.
DEFAULT
VALUES
0, 255, 0
SCOPE
Site preference.
BOM_MARKUP_STRIKE_FOREGROUND
DESCRIPTION
Specifies the color of the strikethrough marking if a user deletes a BOM line or
edits a property.
VALID
VALUES
Specify three color values in order of precedence in the format N1,N2,N3, where
each value is an integer in the range 0 to 255. Enter color values in red, green,
blue (RGB) code, where, for example, 0, 0, 0 represents the color black and 0, 255,
255 represents the color aqua.
DEFAULT
VALUES
0, 255, 0
SCOPE
Site preference.
IC_baseline_carry_forward_active_changes
DESCRIPTION
Determines if active changes are carried forward when the user creates an
incremental change baseline. An active change is one which is currently effective or
may be effective in the future.
VALID
VALUES
True Carry over active changes when creating an incremental change baseline.
False Do not carry over active changes when creating an incremental change
baseline.
DEFAULT
VALUE
False
SCOPE
Site preference.

IC_baseline_carry_forward_status
DESCRIPTION
Specifies status names Teamcenter considers if active changes are carried forward
when the user creates an incremental change baseline. An active change is one
which is currently effective or may be effective in the future.
VALID
VALUES
Any valid status name.
DEFAULT
VALUE
Pending
SCOPE
Site preference.
ICPanelBomChangeDefs
DESCRIPTION
Determines column order in the tree of the IC Data Panel window for the columns
listing the incremental changes made to the BOM line. Rearranging columns in the
IC Data Panel window automatically sets/resets the values of this preference.
VALID
VALUES
Arrays containing all of the following strings, in any order:
type
icContext
icRelStat
icEffectivity
icIntent
icConfiguredBy
DEFAULT
VALUES
type
icContext
icRelStat
icEffectivity
icIntent
icConfiguredBy
SCOPE
All.
ICPanelBomChangeWidths
DESCRIPTION
Determines column width in the tree of the IC Data Panel window for the columns
listing the incremental changes made to the BOM line.

VALID
VALUES
Arrays of integers of length six.
DEFAULT
VALUES
None.
SCOPE
All.
ICPanelAttachChangeDefs
DESCRIPTION
listing the incremental changes made to attachments to the BOM line. Rearranging
columns in the IC Data Panel window automatically sets/resets the values of this
preference.
VALID
VALUES
type
icContext
icRelStat
icEffectivity
icIntent
icConfiguredBy
line
relation
absocc_rootline
DEFAULT
VALUES
type
icContext
icRelStat
icEffectivity
icIntent
icConfiguredBy
line
relation
absocc_rootline
SCOPE
All.
ICPanelAttachChangeWidths
DESCRIPTION
listing the incremental changes made to attachments to the BOM line.

VALID
VALUES
Arrays of integers of length nine.
DEFAULT
VALUES
None.
SCOPE
All.
ICPanelOccAttrChangeDefs
DESCRIPTION
listing the incremental changes made to occurrence attributes. Rearranging columns
in the IC Data Panel window automatically sets/resets the values of this preference.
VALID
VALUES
type
icContext
icRelStat
icEffectivity
icIntent
icConfiguredBy
attribute
attr_value
absocc_rootline
DEFAULT
VALUES
type
icContext
icRelStat
icEffectivity
icIntent
icConfiguredBy
attribute
attr_value
absocc_rootline
SCOPE
All.
ICPanelOccAttrChangeWidths
DESCRIPTION
listing the incremental changes made to occurrence attributes.

VALID
VALUES
Arrays of integers of length nine.
DEFAULT
VALUES
None.
SCOPE
All.
Incremental_Change_Management
DESCRIPTION
Enables incremental change functionality and reveals the relevant menu commands.
By default, this functionality is disabled.
Enabling incremental change using the site preference activates this functionality in
all applications where it is available, including Structure Manager, Manufacturing
Process Planner, Part Planner, and Multi-Structure Manager. Individual users
can use the corresponding user preference to hide the incremental change menu
commands.
An incremental change groups multiple structure changes to a given component
(such adding a component, removing a component, modifying attachments, and
so on). You can then apply effectivity to this incremental change to configure
the associated changes. This change control method allows several independent
structure changes to be made concurrently, including the addition or removal
of unrelated components. Those changes can be implemented in any sequence.
This method is suitable for large, flat structures without nested subassemblies
or components. Teamcenter’s other change control method (revisioning) is not
suitable for this type of structure, as a separate revision would be required for every
permutation of change.
For information about creating incremental changes, see the Structure Manager
Guide.
VALID
VALUES
true Enables incremental change functionality and reveals the
menu commands.
false Disables incremental change functionality and hides the menu
commands.
DEFAULT
VALUES
false
SCOPE
Site or user preference.

MoveICCreationToMenu
DESCRIPTION
Determines whether the Create IC Object button is displayed on the incremental
change toolbar or the Tools→Incremental Change→Create command is displayed in
the main toolbar. (This command may be suppressed with Command Suppression if
your site restricts the ability of users to create incremental changes.)
VALID
VALUES
true The Tools→Incremental Change→Create command is
displayed and the Create IC Object button is hidden.
false The Tools→Incremental Change→Create command is hidden
and the Create IC Object button is displayed.
DEFAULT
VALUES
false
SCOPE
Site preference.
New_Ic_Dialog_last_ic_type
DESCRIPTION
Ensures the change type last used in the New Incremental Change dialog box is
set by default when the dialog box is next used. The default setting is only for
convenience and can be changed in the dialog box.
VALID
VALUES
The system sets this preference automatically the first time a user makes a change
type selection in the New Incremental Change dialog box.
The latest value selected in the dialog box is defined in this preference by the system
as different change types are selected within the dialog box. If the preference is
not set (in other words, the first time the dialog box is used) the dialog box selects
the first change type in the list.
DEFAULT
VALUES
None.
SCOPE
All.
PSEDisplayTypePref
DESCRIPTION
Specifies the Structure Manager graphical display format.
VALID
VALUES
1 Vertical tree.

2 Horizontal tree.
3 Indented BOM.
DEFAULT
VALUES
3
SCOPE
User preference.
PSEoccnotesnocopy
DESCRIPTION
Determines which occurrence notes are not copied when users copy and paste a
PSOccurrence.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid occurrence note.
DEFAULT
VALUES
None.
SCOPE
Site preference.
PSE_icon_placement
DESCRIPTION
Determines the location of icons within Structure Manager.
VALID
VALUES
1 Above.
2 Right.
3 Below.
4 Left.
DEFAULT
VALUES
4
SCOPE
User preference.
PSE_show_option_family_prefix
DESCRIPTION
Determines if the Variant Formula BOM line property cell suppresses the
variant option family when the value is unique in the viewed context. If the top
level item revision declares only a single variant option family with a value of

(for example) StereoCD, the Variant Formula property suppresses the family
name when displaying variant condition formulae in this BOM window. Thus,
[ItemID]Model = Model_X & [ItemID]Engine = V6 becomes Model_X & V6. if the
PSE_show_option_item_prefix preference is also set to OFF.
VALID
VALUES
TRUE A unique variant option family is not suppressed in the Variant
Formula BOM line property cell.
FALSE A unique variant option family is suppressed in the Variant
Formula BOM line property cell.
DEFAULT
VALUES
TRUE
SCOPE
All.
PSE_show_option_item_prefix
DESCRIPTION
Determines whether the item ID displays as a prefix before the option name.
VALID
VALUES
0 Does not display the item ID before the option name. For
example, if the option color is defined on item 000101, the
option displays as:
color
1 Displays the item ID before the option name. For example, if
the option color is defined on item 000101, the option displays
as:
[000101]color
DEFAULT
VALUES
1
SCOPE
All.
PSEPreciseColorPref
DESCRIPTION
Determines the display color for precise BOM view revisions.
VALID
VALUES
Single string as a value; must be a valid color defined by your system at the
X-Window System level.

DEFAULT
VALUES
seagreen
SCOPE
User preference.
PSEImpreciseColorPref
DESCRIPTION
Determines the display color for imprecise BOM view revisions.
VALID
VALUES
DEFAULT
VALUES
slate gray
SCOPE
User preference.
PSESubstituteColorPref
DESCRIPTION
Determines the display color for substitutes.
VALID
VALUES
DEFAULT
VALUES
blue
SCOPE
User preference.
PSEAutoPackPref
DESCRIPTION
Determines whether to place all occurrences on a single line.
For more information on packing occurrences, see the Structure Manager Guide.
VALID
VALUES
0 Does not pack identical occurrences on a single line.
1 Packs identical occurrences on a single line.
DEFAULT
VALUES
1

SCOPE
User preference.
PSEShowSubstitutesPref
DESCRIPTION
Determines whether to display substitutes.
VALID
VALUES
0 Does not display substitutes.
1 Displays substitutes.
DEFAULT
VALUES
1
SCOPE
User preference.
PSE_enable_related_substitutes
DESCRIPTION
Determines whether the Related Substitutes menu command displays in Structure
Manager. Substitute part relationships are used to manage dependencies between
substitute part selections. When there are dependencies between substitute part
selections, you can relate the substitute part of one occurrence with substitute parts
of the other occurrence. You can define these relationships for any occurrence in
any BOM view revision.
VALID
VALUES
True The Related Substitutes menu command displays in Structure
Manager.
False The Related Substitutes menu command does not display in
Structure Manager.
DEFAULT
VALUES
False
SCOPE
All.
PSEAdditionColorPref
DESCRIPTION
Determines the highlight color of an occurrence that has been added when displaying
BOM compare results.

VALID
VALUES
DEFAULT
VALUES
red
SCOPE
User preference.
PSEChangedColorPref
DESCRIPTION
Determines the highlight color of an occurrence that has been changed when
displaying BOM compare results.
VALID
VALUES
DEFAULT
VALUES
orange
SCOPE
User preference.
PSEIsNewVILinkedToModule
DESCRIPTION
Determines if variant items are linked to the generic component.
VALID
VALUES
true (variant items are linked to the generic component by default).
false (variant items are not linked to the generic component by default).
DEFAULT
VALUES
true
SCOPE
User preference.
PSEVariantRuleDialogTableSort
DESCRIPTION
Determines the order in which specified columns in the Variant Rule dialog window
are sorted.

VALID
VALUES
The preference must contain two entries:
• The name of one or more columns, for example:
Item
Option
Desc
Value
State
• The sort order of the specified columns, either 1 for an ascending sort and -1
for a descending sort.
DEFAULT
VALUES
All five columns are sorted in descending order.
SCOPE
User preference.
TC_ExportConfigUGNXAssembly
DESCRIPTION
Determines whether the Tools→Export NX Configured Assembly command
displays in Structure Manager.
VALID
VALUES
TRUE The Tools→Export NX Configured Assembly command
displays in Structure Manager. Use this setting only if NX is
installed on the client machine.
FALSE The Tools→Export NX Configured Assembly command does
not display in Structure Manager.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
Structure Manager assembly preferences

Assemblies are a group of parts and subassemblies. In their designs, engineers
group parts together in assemblies to allow reuse of the same assemblies elsewhere
in the product or in other products. An assembly can contain components that are
piece parts or other assemblies. In this way, users can model a complete product
structure as a hierarchy of single-level assemblies. In Teamcenter, piece parts and
assemblies are both represented by items, and each item has at least one revision.
Users create assemblies using the Structure Manager application. They can display
an assembly or subassembly with Lifecycle Visualization by clicking its BOM line in
the Structure Manager tree. If there is a JT file associated with that BOM line (if the
item revision corresponding to that BOM line has a DirectModel dataset containing

a JT file) then that JT file is displayed in Lifecycle Visualization. Any descendents of

that BOM line containing JT files are also displayed.
Use Structure Manager assembly preferences to configure how assemblies compile
and display.
PSEVariantsMode
DESCRIPTION
Determines which mode of variants functionality is used: modular, legacy, or a
hybrid of both modes.
The legacy variants functionality does not provide all the encapsulation advantages
that the modular variants functionality enforces, nor is it possible to create variant
items within a structure containing legacy variants.
The hybrid mode allows legacy variants to be displayed, edited and configured using
the modular variants dialog boxes. This is the recommended mode during migration
from legacy to modular variants functionality. Once the migration is complete, this
preference setting should be changed to modular.
VALID
VALUES
modular Modular variant functionality is used. Legacy variant data
cannot be viewed, edited, or configured.
hybrid A hybrid of modular and legacy variant functionality is used,
allowing variant modules to be defined in structures containing
legacy variant data.
legacy Legacy variant functionality is used.
DEFAULT
VALUES
hybrid
SCOPE
All.
PSEShowUnconfigdVarPref
DESCRIPTION
Determines whether to display BOM lines containing variant conditions that are
not configured for the current variant rule, by default, when a structure is opened
in Structure Manager. This preference is relevant for both modular and legacy
variant functionality.
This site preference has a corresponding user preference of the same name. Users
can set the user preference through the View→Show Unconfigured Variants menu
command. The first time a user selects this option, a PSEShowUnconfigdVarPref
user preference is created and stored in the user’s BLOB file. User preferences
take precedence over site preferences.
For more information regarding precedence, see Preference precedence.

There are some cases where you may want BOM lines to display at your site
regardless of whether their variant conditions are configured for the current variant
rule, and yet you want to determine whether a given BOM line is configured. To do
so, set the following properties in the Properties table as indicated to display an
unconfigured BOM line:
bl_is_variant is set to Y
bl_variant_state is blank
VALID
VALUES
true BOM lines are displayed regardless of whether their variant
conditions are configured for the current variant rule. For
example, use this setting when you want to write the entire
Structure Manager window to a tab-delimited file in order to
import the BOM into an Excel spreadsheet.
false BOM lines are hidden if their variant conditions are not
configure for the current variant rule.
DEFAULT
VALUES
true
SCOPE
Site preference.
PSEShowUnconfigdEffPref
DESCRIPTION
Determines whether to display BOM lines containing effectivity data that do not
match the current revision rule, by default, when a structure is opened in Structure
Manager.
This site preference has a corresponding user preference of the same name.
Users can set this user preference through the View→Show Unconfigured By
Occurrence Effectivity menu command. The first time a user selects this option, a
PSEShowUnconfigdEffPref user preference is created and stored in the user’s
BLOB file. User preferences take precedence over site preferences.
For more information regarding precedence, see Preference precedence.
There are some cases where you may want BOM lines to display at your site
regardless of whether their variant conditions match the current variant rule, and
yet you want to determine whether a given BOM line is configured. To do so, set the
following properties in the Properties table as indicated to display an unconfigured
BOM line:
bl_is_variant is set to Y
bl_variant_state is blank
VALID
VALUES
true BOM lines are displayed regardless of whether their occurrence
date effectivity data matches the current revision rule.
false BOM lines are hidden if their occurrence date effectivity data
does not match the current revision rule.

DEFAULT
VALUES
true
SCOPE
Site preference.
PSEEnableFilteringUnconfigdDueToClassicVariantsPref
DESCRIPTION
Enables or disables the configure to load feature in Structure Manager. The user
can change the value set in this preference using the View→Enable Classic Variant
Configure to Load menu command in Structure Manager or from the Options dialog
box in the rich client. When this feature is enabled, the Filter unconfigured BOM
lines due to Classic Variants check box in the Variant Rule or Configure dialog
box is enabled.
VALID
VALUES
True Enables the configure to load feature in Structure Manager.
The Tools→Show Unconfigured Variants command is
disabled.
False Disables the configure to load feature in Structure Manager.
The Tools→Show Unconfigured Variants command is enabled.
INITIAL
VALUE
False
SCOPE
User preference.
NOTE
This preference is not included in the default tc_preferences.xml file, but is created
when you first run the system.
ConfigureToLoadEnableDefaultVariantConfig
DESCRIPTION
Enables or disables the Do not show this dialog automatically when opening BOM
check box in the Variant Rule or Configure dialog box in Structure Manager. The
selected BOM line must also have at least one child line and classic variants defined
to enable the check box. This check box is displayed only if you have enabled the
configure to load feature.
VALID
VALUES
True Hides the Do not show this dialog automatically when
opening BOM check box in Structure Manager.
False Shows the Do not show this dialog automatically when
opening BOM check box in Structure Manager.
INITIAL
VALUE
False

SCOPE
All.
NOTES
This preference is not included in the default tc_preferences.xml file, but is created
when you first run the system.
You can set this preference to true by selecting the Do not show this dialog
automatically when opening BOM check box or from the Options dialog box in the
rich client. You can only set it to false from the Options dialog box in the rich client.
CFMOccEffMode
DESCRIPTION
Determines which occurrence effectivity mode is used.
VALID
VALUES
legacy Enables the legacy (date-based) mode for all occurrence
effectivity data.
maintenance Newly created occurrence effectivities use the current (date
or unit) mode, existing occurrence effectivities use the legacy
(date-based) mode.
upgrade Existing occurrence effectivities are upgraded to the current
(date or unit) mode when they are modified.
DEFAULT
VALUES
legacy
SCOPE
Site preference.
TC_ValidApprovedStatus
DESCRIPTION
Determines the valid approved status of an item revision. Use this preference to
determine whether occurrences within an item revision can be updated when a
new item revision is created in precise mode. Users update such occurrences by
selecting a BOM line and choosing Edit→Show Superseded. All children revisions
containing a status specified by this preference are updated. A symbol next to each
child line indicates the update.
VALID
VALUES
Accepts multiple strings as values. Each value must be a valid Teamcenter status.
DEFAULT
VALUES
None.
SCOPE
Site preference.

AbsOccGrmCopyRules
DESCRIPTION
Determines system behavior when revising a BOM view revision that is copying
forward GRMs. Use this preference to specify the class of the GRM, the class of the
secondary object, the relation, and the action taken during the revision.
If you are using the Wiring Harness Design Tools Integration and have installed
KBL functionality, see the Wiring Harness Design Tools Integration Guide for
additional required values.
Tip
When adding new values (copy rules) to this preference, verify the rule by
revising it at least once, then checking the system log to confirm no errors
were recorded while reading the preference. Testing this preference requires
an assembly containing absOcc attachments.
VALID
VALUES
Accepts multiple strings as values. Strings are case sensitive and trailing blanks
are not allowed. Each string is a concatenation of class, relation, and action values
which must be in the following format:
class.AbsOccGrmAnchor:Class Name 2:Relation:Relation Type:Action
class.AbsOcc Specifies the class of the primary object. This class name must
GrmAnchor: always be class.AbsOccGrmAnchor:.
Class Name 2 Specifies the class of the secondary object. This value must be
either class.Form or class.Dataset, or * to indicate either the
form or dataset class.
Note
This functionality accepts only forms and datasets as
secondary objects. If any other objects are defined, the
system will apply the Reference action.
Relation The relation must always be Relation. All other types are
ignored.
Relation Type Specifies the relation type used when applying the action.
Must be a valid relation type.
Action Specifies the action is performed on the secondary object. Must
be one of the following values:
Clone Creates a new GRM that points to the
copied form or dataset.
Ignore The GRM is not copied to the new BOM
view revision.
Reference Creates a new GRM that points to the
old form or dataset. (This is the system’s
default behavior.)

The following example specifies that a new GRM points to a form copied using the
TC_Feature_Form_Relation:
class.AbsOccGrmAnchor:class.Form:Relation.TC_Feature_Form_Relation:Clone
The following example specifies that a new GRM points to a form copied using the
IMAN_master_form relation:
class.AbsOccGrmAnchor:class.Form:Relation.IMAN_master_form:Clone
The following example specifies that the is not copied to the new BOM view revision:
class.AbsOccGrmAnchor:*:Relation.IMAN_Rendering:Ignore
DEFAULT
VALUES
class.AbsOccGrmAnchor:class.Form:Relation.TC_Feature_Form_Relation:Clone
class.AbsOccGrmAnchor:class.Form:Relation.IMAN_master_form:Clone
class.AbsOccGrmAnchor:*:Relation.IMAN_Rendering:Ignore
SCOPE
Site preference.
PSEIsNewVIisLinkedToModule
DESCRIPTION
Determines whether a component reuse is automatically linked to its module during
creation. By default, the system does not link a component reuse (also known as a
variant item, or VI) to the module from which it was instantiated upon creation.
Set this preference to false if users at your site frequently want to create VIs as a
starting point, and thus do not need them linked to the module from which they
were instantiated.
If this preference is removed from the database, the system behaves as if it were set
to true.
VALID
VALUES
true Allows users to link VIs to its module.
false VIs are not linked to its module.
DEFAULT
VALUES
false
SCOPE
Site preference.
PSEAllowLegacyVICreation
DESCRIPTION
Determines whether variant items can be created using legacy variant options,
and whether variant items can be created for non-modules. Additionally, if this
preference and the PSEVariantsMode preference are both set to true, the Create
VI button displays in the rich client toolbar.

VALID
VALUES
true Allows variant items to be created with legacy variant options.
Allows variant items creation for non-modules.
false Does not allow variant items to be created with legacy variant
options. Does not allow variant items creation for non-modules.
DEFAULT
VALUES
false
SCOPE
Site preference.
PSEBypassVISearch
DESCRIPTION
Determines whether the Create VI button appears in the Configure dialog box in the
rich client. If this preference is set to true, the button displays as soon as a value
is set for each option, allowing users to bypass the manual search for similarly
configured variant items before creating a new variant item.
Triggers an alternative variant item creation process, useful if Business Modeler
IDE rules prevent normal variant item creation.
VALID
VALUES
true Bypasses the manual search for similarly configured variant
items before creating a new variant item.
false Requires the manual search for similarly configured variant
items before creating a new variant item.
DEFAULT
VALUES
false
SCOPE
Site preference.
PSECreateVISameType
DESCRIPTION
Determines whether variant items are always created as the same type as the
parent, using the SaveAs creation method.
Triggers an alternative variant item creation process, useful if Business Modeler
IDE rules prevent normal variant item creation.
VALID
VALUES
true Automatically creates variant items as the same type as the

false Does not provide an alternative item creation process. Does

not automatically create variant items as the same type as the
DEFAULT
VALUES
false
SCOPE
Site preference.
ShowModuleIcons
DESCRIPTION
Determines whether modular variants are indicated in item and item revision
icons. If set to true, the icon of items and item revisions containing a module are
displayed in gray scale.
Setting this preference to true impacts performance. Siemens PLM Software
recommends that if modular variants are not used at your site, the default setting is
kept.
For information about indicating if an item or item revision is a variant item in item
and item revision icons, see the ShowViIcons preference.
VALID
VALUES
true Displays icons of items and item revision containing modular
variants in gray scale.
false Does not display icons of items and item revision containing
modular variants in gray scale.
DEFAULT
VALUES
false
SCOPE
All.
ShowViIcons
DESCRIPTION
Determines whether variant items are indicated in item and item revision icons. If
set to true, the icon of items and item revisions that are variant items are displayed
in gray scale with a V overlay.
Setting this preference to true impacts performance. Siemens PLM Software
recommends that if variant items are not used at your site, the default setting is kept.
For information about indicating modular variance in item and item revision icons,
see the ShowModuleIcons preference.
VALID
VALUES
true Displays icons of items and item revisions which are variant
items in gray scale with a V overlay.

false Does not display icons of items and item revisions which are
variant items in gray scale with a V overlay.
DEFAULT
VALUES
false
SCOPE
All.
PSEAutoViCreateEmptyVI
DESCRIPTION
Determines whether a variant item is created when a non-module is encountered
during automatic variant item creation.
VALID
VALUES
true A variant item is created for a given BOM line when a
non-module is encountered. The system continues to the
bottom of the generic structure, assigning empty variant items
(variant items with no variant configuration) for each item
that is not a module.
false A variant item is not created for a given BOM line when a
non-module is encountered.
DEFAULT
VALUES
false
SCOPE
User preference.
PSEAutoViStopVICreationForUnconfiguredModule
DESCRIPTION
Determines whether automatic variant item creation stops when the system
encounters an unconfigured module.
VALID
VALUES
true The system stops when it encounters an unconfigured module.
false The system continues to the bottom of the generic structure,
displaying warning messages for each unconfigured module
encountered.
Note
This is the best practice for most business environments.
DEFAULT
VALUES
true

SCOPE
User preference.
PSEAutoViNewItemPopup
DESCRIPTION
Determines whether users are prompted for an item identifier, item revision
identifier and item name each time the automatic creation process creates a variant
item.
VALID
VALUES
true Users are prompted for this information each time a variant
item is created via the Item Creation dialog box.
false The system automatically assigns values according to
predefined numbering and naming schemes. For example,
if you have a generic item called 00100/A Generic Wheel,
Teamcenter creates a generic item called 00200/A VI_Generic
Wheel.
DEFAULT
VALUES
false
SCOPE
User preference.
PSEAutoViNamePrefix
DESCRIPTION
If the PSEAutoViNewItemPopup preference is set to false, this preference defines
the naming prefix scheme used for automatic variant item creation.
VALID
VALUES
Accepts a single string as a value. The value is used as the prefix of the automatically
created variant item. For example, if you set this preference to VI_, when users
create a generic item called Wheel, the name of the variant item is VI_Wheel.
DEFAULT
VALUES
None.
SCOPE
User preference.
PSM_classic_variants_text_families
DESCRIPTION
Manually controls variant option value mode detection for specific variant option
families when you use classic variant configuration. By default, a classic variant
option family is considered a text family if at least one value is nonnumeric. A value
is considered numeric if it begins with the following pattern:

[{+|-}] digits [.digits] [{e|E} [{+|-}] digits]
You can use the ISO C standard function strtod() to convert the value to a number,
so that the unit of measure trailer does not conflict for any value in this family.
For example:
Family Values Value Mode Notes

Engine 110 H.P. Numeric Matching unit of
measure trailer
95 H.P. H.P.
Engine 110 Numeric Unit of measure
trailers are not in
95 H.P. conflict.
trailers are not in
95 conflict.
Engine 80.9 kW Lexicographic Unit of measure
trailer H.P.
95 H.P. conflicts with kW.
In some circumstances, the system may detect the wrong mode. For example:
Unit of
Numeric measure
Family Values value trailer Conflict
FAM1 1D0 1.0 ““ No
1D2 100.0 ““ No
1D4 10000.0 ““ No
1M6 1.0 M6 No
1E2 100.0 ““ No
In this example, the following expressions evaluate to TRUE because all elemental
expressions are identical.
[SCOPE]FAM1 = 1D0 & [SCOPE]FAM1 = 1.0 & [SCOPE]FAM1 = 1 & [SCOPE]FAM1 = 1M6
[SCOPE]FAM1 = 1D2 & [SCOPE]FAM1 = 100.0 & [SCOPE]FAM1 = 100 & [SCOPE]FAM1 = 1E2
Use the PSM_classic_variants_text_families preference to avoid incorrect value

mode by listing variant families that should be forced to text value mode. In this
example, you should set this preference to [SCOPE]FAM1 and [SCOPE]FAM2.
If the preference ends with a single period (.), the list is considered to be exhaustive,
that is, the list contains all nonnumeric values. Any other value is then forced to be
numeric.
If you attempt to use a nonnumeric value in a family that is forced to be numeric
causes an error.
See also the PSM_classic_variants_numeric_families preference.
VALID
VALUES
Accepts multiple values in the format:

[owning option item id]option family name
For example:
[10001C2C61]AHV
.
If the preference ends with a single period ., the list is considered to be exhaustive,
that is, the list contains all nonnumeric values. Any other value is then forced to be
numeric.
DEFAULT
VALUES
None.
SCOPE
Site preference.
PSM_classic_variants_numeric_families
DESCRIPTION
Manually controls variant option value mode detection for specific variant option
families when you use classic variant configuration. By default, a classic variant
option family is considered a numeric family if all values are numeric. A value is
considered numeric if it begins with the following pattern:
[{+|-}] digits [.digits] [{e|E} [{+|-}] digits]
You can use the ISO C standard function strtod() to convert the value to a number,
so that the unit of measure trailer does not conflict for any value in this family.
For example:
Family Values Value Mode Notes

Engine 110 H.P. Numeric Matching unit of
measure trailer
95 H.P. H.P.
trailers are not in
95 H.P. conflict.
trailers are not in
95 conflict.
Engine 80.9 kW Lexicographic Unit of measure
trailer H.P.
95 H.P. conflicts with kW.
In some circumstances, the system may detect the wrong mode. For example:

Unit of
Numeric measure
Family Values value trailer Conflict
FAM1 1D0 1.0 ““ No
1D2 100.0 ““ No
1D4 10000.0 ““ No
1M6 1.0 M6 No
1E2 100.0 ““ No
In this example, the following expressions evaluate to TRUE because all elemental
expressions are identical.
[SCOPE]FAM1 = 1D0 & [SCOPE]FAM1 = 1.0 & [SCOPE]FAM1 = 1 & [SCOPE]FAM1 = 1M6
[SCOPE]FAM1 = 1D2 & [SCOPE]FAM1 = 100.0 & [SCOPE]FAM1 = 100 & [SCOPE]FAM1 = 1E2
Use the PSM_classic_variants_numeric_families preference to avoid incorrect

value mode by listing variant families that should be forced to numeric value mode.
If the preference ends with a single period (.), the list is considered to be exhaustive,
that is, the list contains all numeric values. For example, if you set this preference to
[SCOPE]FAM3 and [SCOPE]FAM3, any other value such as [SCOPE]FAM3 is
then forced to be nonnumeric.
If you attempt to use a nonnumeric value in a family that is forced to be numeric
causes an error.
See also the PSM_classic_variants_text_families preference.
VALID
VALUES
Accepts multiple values in the format:
[owning option item id]option family name
For example:
[10001C2C61]AHV
.
If the preference ends with a single period ., the list is considered to be exhaustive,
that is, the list contains all numeric values. Any other value is then forced to be
nonnumeric.
DEFAULT
VALUES
None.
SCOPE
User preference.
TC_CFG_PRODUCTS_USE_VARIABILITY
DESCRIPTION
Manually enforces or disables the evaluation of RDV variability allocation statements
if they exist for a given item revision. RDV variability allocation statements allow

Teamcenter to import only some of the values of a variant option family in a product.
This preference is only relevant when you use classic variant configuration.
If you leave this preference unset, Teamcenter dynamically determines this
configuration setting.
You can view and manage variability allocation statements
in Platform Designer. Technically, RDV variability allocation
statements are specialized VariantExpression objects using the
BOM_variant_operator_assy_uses+BOM_variant_op_rhs_is_string = 1002 operator code.
For more information about these objects, see the
$TC_INCLUDE/bom/bom_tokens.h file.
If an item revision has RDV variability allocation statements and their evaluation is
not disabled, the variant configurators recognize only explicitly allocated variant
option values. Otherwise, they recognize all variant option values that exist on the
declared variant option family revision.
Setting this preference is recommended, but not required. If you are unsure, set
this preference to TRUE.
VALID
VALUES
Effect on
Effect on item item revisions
Effect on revisions with without RDV
classic variant RDV variability variability
configurator allocation allocation
Preference value initialization statements statements
TRUE No database query Classic variant Classic variant
is executed when configurators configurators
initializing a recognize only recognize all
classic variant allocated variant variant option
configurator. option values. values of all
declared variant
option families.
FALSE No database query Classic variant Classic variant
is executed when configurators configurators
initializing a recognize all recognize all
classic variant variant option variant option
configurator. values of all values of all
declared variant declared variant
option families. option families.
unset A database query Classic variant Classic variant
is executed once configurators configurators
when initializing recognize only recognize all
a classic variant allocated variant variant option
configurator. option values. values of all
declared variant
option families.
DEFAULT
VALUES
None.

If the preference is left unset, Teamcenter dynamically determines the configuration

setting by executing a database query when initializing the classic variant
configurator.
SCOPE
Site preference.
TCEnforceSingleType
DESCRIPTION
Determines whether items in a structure are restricted to a single item or GDE type,
thus determining whether structures must be homogeneous, or can be heterogeneous.
Note
GDEs are general design elements used to model electrical interfaces.
VALID
VALUES
true Items in a structure are restricted to a single item or GDE
type. Users can only create homogeneous structures; any
children added must be the same type as the parent.
Note
When this preference is set to true, the values of the
TCAllowedChildTypes_<ItemTypeOrGDEType>
preference are ignored.
false Items in a structure are not restricted to a single item or GDE

type. The system restricts item/GDE types to the types defined
in the TCAllowedChildTypes_<ItemTypeOrGDEType>
preference.
DEFAULT
VALUES
false
SCOPE
Site preference.
TCAllowedChildTypes_<ItemTypeOrGDEType>
DESCRIPTION
Defines the item and/or GDE types permitted in a parent structure. This preference
is valid only when the TCEnforceSingleType preference has been set to false.
Teamcenter checks this preference when child items or occurrences are added to a
BVR in Structure Manager. If you want to add restricted item types to the parent
BVR with a different relation (for example, references), they should be specified
in this preference.
Note
GDEs are general design elements used to model electrical interfaces.

VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter item
type or GDE type.
DEFAULT
VALUES
TCAllowedChildTypes_CPPackageItem=CPPackageItem
TCAllowedChildTypes_CPArtwork=CPGraphicElement, CPCopy, CPDieLline
TCAllowedChildTypes_CPCopy=CPCopyElement
TCAllowedChildTypes_CPFinishProduct=CPFinishProduct, CPPackageItem, CPGFormulaMaster, Part
SCOPE
Site preference.
TCAllowedParentTypes_itemtype
DESCRIPTION
Indicates the list of valid parent item types for a given child type.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid Teamcenter class.
DEFAULT
VALUES
TCAllowedParentTypes_CPGraphicElement=CPArtwork
TCAllowedParentTypes_CPCopy=CPArtwork
TCAllowedParentTypes_CPDieLine=CPArtwork
TCAllowedParentTypes_CPCopyElement=CPCopy
TCAllowedParentTypes_CPFinishProduct=CPFinishProduct
TCAllowedParentTypes_CPGFormulaMater=CPFinishProduct, CPGFormulaMater
SCOPE
Site preference.
PSM_global_option_item_id
DESCRIPTION
Specifies a list of item IDs that contain global option definitions. These definitions
can be reused when authoring variant modules. In the rich client, you can drop these
global options into the module for which they are required. Set this preference by
listing the IDs of all items that contain global options. For example:
PSM_global_option_item_id=
000400
000410
000420
VALID
VALUES
Valid Teamcenter item IDs that contain global options.

DEFAULT
VALUES
None.
SCOPE
User preference.
PSESavedConfigRelationTypes
DESCRIPTION
Determines the relation type available when saving an option set or variant
configuration to the module being configured. (Users can choose to save option
sets/variant configurations to the Home folder, the Newstuff folder, or to the module
being configured. This preference affects the final method.)
VALID
VALUES
Valid Teamcenter reference type.
DEFAULT
VALUES
IMAN_specification
IMAN_manifestation
ImanRelation
SCOPE
All.
BOM_Enable_Ref_Designator_Value_Packing
DESCRIPTION
Determine whether the system packs reference designator values when packing
lines.
Setting this preference to true allows you to pack or unpack product structure lines
that include reference designators. For example, if you pack six occurrences of the
same part with different reference designators, the Ref Designator property column
shows a concatenated set of reference designators. Thus, if reference designator
values are C1, C2, C3, C6, C12, C13, they will be packed to C1-C3,C6,C12-C13.
For more information about packing or unpacking lines with reference designators,
see the Structure Manager Guide.
Note
• You cannot edit the reference designators of packed lines.
• After modifying this preference, you must restart both the rich client and
Structure Manager.
VALID
VALUES
true The system packs reference designator values.
false The system does not pack reference designator values.

DEFAULT
VALUES
true
SCOPE
Site preference.
BOM_Additional_Packing_Criteria
DESCRIPTION
Determines which properties users can add to the pack criteria. Users can add any
properties defined by this preference to the pack criteria.
VALID
VALUES
Accepts one or more strings as values. Strings must be entered in one of the
following three formats:
Property-name-only Lines with the same value of the property are packed. For
example, use the following value to pack all lines containing
the same value for the bl_ref_designator property:
bl_ref_designator
Property-name: When the specified property has the specified value, the line
property-value is not packed. For example, use the following value to ensure
that lines containing the NoLoad property with the value of
True are not packed:
NoLoad:True
Property-name: When the specified property is empty, the line is not packed.
<blank-value> For example, use the following value to ensure that lines
containing the bl_ref_designator property with an empty
value are not packed:
bl_ref_designator:
DEFAULT
VALUES
empty
SCOPE
Site preference.
BOM_Additional_Ref_Designator_Search_Criteria
DESCRIPTION
Determines which properties users can add to the search criteria for the reference
designator, within the same parent. Users can add any properties defined by this
preference to search criteria within the same parent.

VALID
VALUES
Accepts one or more strings as values. Each string must be a valid BOM line
property name.
DEFAULT
VALUES
empty
SCOPE
Site preference.
PS_Reference_Designator_Validation
DESCRIPTION
Determines whether the system performs special reference designator validation.
If enabled, the format and uniqueness of the values of the reference designator is
verified. Packed lines cannot be modified.
For validation, all reference designators must be in the format prefix number, where
prefix is a string of one or more uppercase letters and number is an integer. For
example, C1, TS105, or CK109TS43). Formats such as c1 and %O are not valid.
VALID
VALUES
true Special reference designator validation is enabled.
false Special reference designator validation is not enabled.
DEFAULT
VALUES
false
SCOPE
Site preference.
BOM_Enable_Quantity_Validation_Against_Ref_Designator
DESCRIPTION
Verifies whether the quantity is blank or 1 when the reference designator is assigned.

VALID
VALUES
true Verifies that when a reference designator value is assigned,
the quantity is either blank or 1. Verifies that when a quantity
that is neither blank nor 1 is to be set, the reference designator
value of the line is not assigned. An error appears when the
values do not comply.
For example, when the reference designator is C1 and a user
changes the quantity to 3, an error appears. Or, if the quantity
is 3 and a user sets the reference designator to C1, an error
appears.
false The system does not validate reference designator values.
DEFAULT
VALUES
false
SCOPE
Site preference.
PS_Duplicate_FindNo_Update
DESCRIPTION
Determines whether duplicate find numbers of the same item are updated.
VALID
VALUES
true Duplicate find numbers of the same item are updated.
false Duplicate find numbers of the same item are not updated.
DEFAULT
VALUES
true
SCOPE
Site preference.
BOMExcludeFromPackCheck
DESCRIPTION
Defines which attributes are ignored during the default pack check. For example,
set this preference to seqno to allow the exclusion of find numbers from the BOM
line pack check.
VALID
VALUES
seqno Excludes find numbers from the BOM line pack check. Allows
BOM lines with distinct find numbers to be packed.

none No attributes are ignored during the default pack check. BOM
lines must have the same part number and the find number
to be packed.
DEFAULT
VALUES
none
SCOPE
Site preference.
TC_JT_voxel_size
DESCRIPTION
Specifies the size of the voxels, in millimeters, used to save the spatial representation
of the product when spatial data is generated from JT files.
Users should base this setting upon their knowledge of the model’s geometry.
Smaller values provide a higher quality of results with less false positives but
increase disk space requirements and may increase search times. Larger values
improve performance but can degrade quality.
Appearance spatial cache supports mixed-size components spatial maps. Users must
modify this value depending upon actual geometry size.
VALID
VALUES
A positive real number.
DEFAULT
VALUES
12.75
SCOPE
Site preference.
JT_File_OverrideChildren_Refsets
DESCRIPTION
Specifies the naming convention used for reference sets and JT files. For example,
clicking a BOM line displays its corresponding JT file. If there is no JT file, Lifecycle
Visualization displays all of its immediate children. This is done recursively down
each branch of the product structure until a JT file is found. That JT file is then
be displayed. However, if that JT file is in the preference list, none of its children
are displayed.
VALID
VALUES
Valid NX reference set names.
DEFAULT
VALUES
None.
SCOPE
User preference.

JT_File_Priority_Refsets
DESCRIPTION
Determines the load order of NX reference sets contained within DirectModel files.
NX reference sets enable you to display different geometry configurations within
the context of a single assembly.
DirectModel support of NX reference sets can take two forms:
• DirectModel datasets created prior to Teamcenter 8, which consist of multiple
JT files named according to the available reference sets
• DirectModel datasets created using Teamcenter 8 or later, which may consist

of a single JT file that contains all of the information necessary to define the
geometry configurations for each reference set
Note
• Values specified for the JT_File_Priority_Refsets preference are case
sensitive.
• By default, the JT_File_Priority_Refsets preference is applicable

only for the viewers embedded within Teamcenter applications such as
Structure Manager and My Teamcenter. For the Lifecycle Viewer to use
the reference set loading order specified with this preference, select the
Teamcenter Reference Set settings take precedence check box in the
Lifecycle Viewer 3D Loader Preferences.
VALID
VALUES
For a mixture of
For DirectModel For DirectModel DirectModel datasets
datasets created using datasets created prior created using different
Teamcenter 8 or later to Teamcenter 8 releases
$EMPTY EMPTY $EMPTY
$ENTIREPART ENTIREPART EMPTY
$LASTSAVED LASTSAVED $ENTIREPART
$MODEL MODEL ENTIREPART
[user-defined] [user-defined] $LASTSAVED
LASTSAVED
$MODEL
MODEL
[user-defined]
DEFAULT
VALUES
$LASTSAVED
$ENTIREPART
$MODEL
$EMPTY
SCOPE
User preference.

JT_File_Excluded_Refsets
DESCRIPTION
Specifies JT files you do not want Lifecycle Visualization to load, for example, empty.
VALID
VALUES
Valid NX reference set names.
DEFAULT
VALUES
None.
SCOPE
User preference.
JTContentBomLineProperties
DESCRIPTION
Specifies which attributes from JT content hint forms are included as BOM line
properties when a structure is expanded.
Note
JT content hint information is returned for all BOM lines when the object
property policy for BOM lines is set to return the bl_JTHint_Contents
property.
Setting this preference allows the client to recognize specified types of content in
the corresponding JT files without having to download and examine the files. The
client uses this information to optimize performance when downloading JT files. By
determining which JT files contain content of interest, a smaller number of JT files
are retrieved from the server when expanding a structure.
When this preference is not set, JT content information is not added to BOM line
properties and JT files must be downloaded, opened, and read to determine if they
contain data of interest.
VALID
VALUES
Accepts one or more strings as values. Each string must be attribute names on JT
content hint forms. Any strings that are not valid attributes of JT content hint
forms are ignored.
DEFAULT
VALUES
None.
SCOPE
All.

JTContentHintPropertyPolicy
DESCRIPTION
Lists those attributes that may be in JT Content Hint forms that are to be included
in the JTContentHint BOMLine property. Values are not case sensitive. Any
invalid values are ignored.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
All.
PSE_prompt_for_remote_import
DESCRIPTION
When users select a BOM line for import containing a child line which is a stub
reference to an item in another database, this preference determines whether the
system automatically asks if users want to import the referenced item.
VALID
VALUES
true The system automatically asks if users want to import the
referenced item.
false The system does not prompt users to import the referenced
item.
DEFAULT
VALUES
false
SCOPE
All.
RAC_expand_below_batch_size
DESCRIPTION
Determines the batch size in which BOM lines are processed when users click
View→Expand Below. The selected BOM lines are expanded in levels of batches, the
maximum size of each batch is the size set by this preference.
VALID
VALUES
Accepts a single integer as a value. A positive integer defines the number of lines
processed per batch. Use -1 to indicate no maximum size, in which case all lines in a
single level are processed in a single batch.

DEFAULT
VALUES
1000
SCOPE
All.
Structure Manager transform preferences

Teamcenter uses transform data to position components in an assembly. The system
creates transform data for each component in an assembly. When an Teamcenter
assembly is opened in NX via Teamcenter Integration for NX, it interprets the
transform data to reconstruct the assembly. Teamcenter Integration for NX provides
several options for managing Teamcenter transform data.
For more information, see Teamcenter Integration for NX Guide.
Teamcenter and Teamcenter Integration for NX transform data is currently written
in an PLM XML format, which uses metres as its unit of measure. Legacy transform
data was written in millimeters and inches.
Note
Do not combine legacy and current transform measurements.
For more information about updating transform data using the
ugmanager_refile utility, see the NX Help Library.
PS_assume_old_transform_format
DESCRIPTION
Determines how Teamcenter interprets the format of legacy transform data.
VALID
VALUES
In_Legacy_Format
Assumes all legacy transforms are in the same format as legacy NX transforms.
Written_By_UG
Assumes all old transforms are in the same format as legacy NX transforms.
Assumes all old transforms were written by Teamcenter Integration for NX. The
PS_convert_legacy_transform ITK routine attempts to obtain the parent’s unit
information when converting transforms to eXT format.
Unknown
No assumptions made. Use this setting when the transform data was written by an
application other than Teamcenter Integration for NX.
DEFAULT
VALUES
Unknown
SCOPE
Site preference.

PS_assume_legacy_transform_units
DESCRIPTION
Determines how Teamcenter interprets the unit of measure for legacy transform
data. Teamcenter and NX currently use meters for transform units of measure;
legacy measurements were in inches or millimeters. This preference affects all data
using legacy transforms which have no database-resident indication of the unit
measurement with which they were stored.
If the PS_assume_old_transform_format preference is set to Written_By_UG,
the PS_convert_legacy_transform ITK routine attempts to obtain the unit of
the parent NX part from this preference.
VALID
VALUES
Inches Assumes transform data is measured in inches.
Millimeters Assumes transform data is measured in millimeters.
Unknown No assumption made. Use this setting when transform data is
in mixed units, for example, when transform data from NX is
in both millimeters and inches.
DEFAULT
VALUES
Unknown
SCOPE
Site preference.
PS_allow_plmxml_transforms_with_no_legacy_factor
DESCRIPTION
Allows Teamcenter to use the PS_set_plmxml_transform ITK call to set PLM
XML transform data without first having to define a legacy transform factor via the
PS_set_legacy_transform_factor ITK call. Use this preference when you have
a new set up of Teamcenter with no legacy data, and thus no need to convert to
or from legacy transform data.
VALID
VALUES
Yes Ignores the legacy factor.
No Requires the legacy factor.
DEFAULT
VALUES
Yes
SCOPE
Site preference.

PS_convert_legacy_transform_to_plmxml
DESCRIPTION
Allows Teamcenter to display legacy transforms in a PLM XML format. This
preference is only effective if a legacy transform exists and no PLM XML transform
is assigned.
VALID
VALUES
true Teamcenter tries to convert the legacy transform to PLM XML
format for display purposes only.
false Teamcenter displays the legacy transform as is.
DEFAULT
VALUE
false
SCOPE
All.
Product structure synchronization

Structure Manager can synchronize dataset and BOM view revision changes by
comparing the time listed in the last_struct_mod_date field of the BVRSyncInfo
form, attached as a named reference to UGMASTER datasets, with the
struct_last_mod_date field of the BOM view revision. The struct_last_mod_date
field is only updated when a significant change occurs to the BOM view revision.
Use the PS_structure_change_condition preference to define what constitutes a
significant change.
Each time Teamcenter Integration for NX opens a dataset, these two fields
are compared. When the date of the struct_last_mod_date field is later,
Teamcenter Integration for NX synchronizes its internal structure. Synchronization
behavior is determined by two Teamcenter Integration for NX preferences:
UGMGR_StructureUpdateOnLoad and UGMGR_StructureUpdateOnSave.
For information about these preferences, see Teamcenter Integration for NX Guide.
PS_structure_change_condition
DESCRIPTION
Determines which changes to a BOM view revision are considered significant,
and thus noted in the struct_last_mod_date field of the BOM view revision.
Changes to any of the attributes listed as a value of this preference updates the
struct_last_mod_date field.

Note
The following note types must be used with this preference to ensure correct
synchronization with Teamcenter Integration for NX:
NoteType:UG NAME
NoteType:UG GEOMETRY
NoteType:UG REF SET
NoteType:UG ENTITY HANDLE
NoteType:UG ALTREP
VALID
VALUES
Transform
Any change to the transform updates the struct_last_mod_date field.
SequenceNumber
Any change to the sequence number updates the struct_last_mod_date field.
Quantity
Any change to the quantity updates the struct_last_mod_date field.
PreferredAlternate
Setting the preferred alternate on the occurrence updates the struct_last_mod_date
field.
NoteType:note type name
Any changes to the specified note types updates the struct_last_mod_date field.
The note types listed above must be used with this preference to ensure correct
synchronization with Teamcenter Integration for NX.
ClientData:attribute name
Any changes to client data on the occurrence updates the struct_last_mod_date
field.
DEFAULT
VALUES
Transform
SequenceNumber
Quantity
PreferredAlternate
NoteType:UG NAME
NoteType:UG GEOMETRY
NoteType:UG REF SET
NoteType:UG ENTITY HANDLE
NoteType:UG ALTREP
SCOPE
Site preference.

TC_BVRSYNCFORM_DELEGATE
DESCRIPTION
Determines whether the BVRSYNCFORM named reference inherits delegated
write access from the UGMASTER dataset.
VALID
VALUES
true The BVRSYNCFORM named reference inherits the write
access privilege from the UGMASTER dataset.
false The BVRSYNCFORM named reference does not inherit the
write access privilege from the UGMASTER dataset.
DEFAULT
VALUES
true
SCOPE
Site preference.
BOM grading preferences

Teamcenter allows you validate that the design represented by the product structure
contains only approved parts. This process is sometimes called BOM grading. Parts
approved for use in one project or locale may not be approved for another project
or locale. For example, a part may comply with a European standard but not a
U.S. standard.
Grading results are stored in a structure context associated with the validated
product or assembly and may be retrieved when required.
The grading process checks that each part is valid under the selected condition. If
the structure contains subassemblies, it checks that each subassembly is valid and
then checks each part in the context of each subassembly.
For more information about the use of this feature, see the Structure Manager Guide.
For more information about configuring this feature, see the Business Modeler IDE
Guide.
CondValData.CREATERENDERING
DESCRIPTION
Registers a data creation style sheet for CondValData item objects. The
CondValData object contains verification rules that are used by the Validation
Manager checker.
DEFAULT
VALUES
CondValDataCreate
SCOPE
Site preference.

CondValData.SUMMARYRENDERING
DESCRIPTION
Registers a summary style sheet for CondValData item objects. The CondValData
object contains verification rules that are used by the Validation Manager checker.
DEFAULT
VALUES
CondValDataSummary
SCOPE
Site preference.
CondValDataCreate.CREATE_REGISTEREDTO
DESCRIPTION
Indicates the business object type to which the CondValData item creation style
sheet can be applied. The CondValData object contains verification rules that are
used by the Validation Manager checker.
DEFAULT
VALUES
CondValData
SCOPE
Site preference.
CondValdataRevSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business object type to which the CondValDataRevision summary
style sheet can be applied. The CondValDataRevision object is a specific revision
of the CondValData object that contains verification rules used by the Validation
Manager checker.
DEFAULT
VALUES
CondValDataRevision
SCOPE
Site preference.
CondValDataRevision.REGISTEREDTO
DESCRIPTION
Indicates the business object type to which the CondValDataRevision style
sheet can be applied. The CondValDataRevision object is a specific revision of
the CondValData object that contains verification rules used by the Validation
Manager checker.

DEFAULT
VALUES
CondValDataRevision
SCOPE
Site preference.
CondValDataRevision.RENDERING
DESCRIPTION
Registers the properties style sheet for CondValDataRevision objects. The
CondValDataRevision object is a specific revision of the CondValData object that
contains verification rules used by the Validation Manager checker.
DEFAULT
VALUES
CondValDataRevision
SCOPE
Site preference.
CondValDataRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for CondValDataRevision objects. The
CondValDataRevision object is a specific revision of the CondValData object that
contains verification rules used by the Validation Manager checker.
DEFAULT
VALUES
CondValDataRevSummary
SCOPE
Site preference.
CondValDataSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business object types to which the CondValData summary style sheet
can be applied. The CondValData object contains verification rules that are used by
the Validation Manager checker.
DEFAULT
VALUES
CondValData
SCOPE
Site preference.

CondValResult.SUMMARYRENDERING
DESCRIPTION
Defines the name of the summary style sheet for CondValResult objects. The
CondValData object contains verification rules that are used by the Validation
Manager checker. The setting determines how detail information about the BOM
grading result displays in the Detail Information pane in Structure Manager.
DEFAULT
VALUES
CondValResultSummary
SCOPE
Site preference.
CondValResultSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the business object type to which the CondValResult summary style
sheet can be applied. The CondValData object contains verification rules that
are used by the Validation Manager checker. The setting determines how detail
information about the BOM grading result displays in the Detail Information pane
in Structure Manager.
DEFAULT
VALUES
CondValResult
SCOPE
Site preference.
CondValidation_NoData
DESCRIPTION
Defines your company policy on the handling of no-data results in condition
validation results.
VALID
VALUES
PASS Passes no-data results.
FAIL Fails no-data results.
NODATA Reports the results as having no data.

DEFAULT
VALUES
NODATA
SCOPE
Site preference.

CONDVALIDATION_Keep_PrevRev_Result
DESCRIPTION
Controls whether Teamcenter keeps BOM grading results generated by previous
checker revisions when a checker runs.
VALID
VALUES
TRUE BOM results generated by an earlier revision of a checker are
not deleted when the BOM is validated against a later revision
of the same checker.
FALSE BOM results generated by an earlier revision of a checker are
deleted when the BOM is validated against a later revision of
the same checker.
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
ConditionValidationResultColumnPreferences
DESCRIPTION
Specifies the columns displayed in the validation results Detail Information pane
in Structure Manager. You can remove columns from this preference but not add
columns. Use the ConditionValidationResultColumnWidthPreferences
preference to set the widths of the specified columns.
VALID
VALUES
CondValResult.validation_target, CondValResult.valdata_revision,
CondValResult.condition_name,
CondValResult.validation_date,
CondValResult.validation_result,
CondValResult.override_to_state,
CondValResult.override_request_state
DEFAULT
VALUES
CondValResult.validation_target, CondValResult.valdata_revision,
CondValResult.condition_name,
CondValResult.validation_date,
CondValResult.validation_result,
CondValResult.override_to_state,
CondValResult.override_request_state
SCOPE
Site preference.

ConditionValidationResultColumnWidthPreferences
DESCRIPTION
Specifies the widths of the columns displayed in the validation results Detail
Information pane in Structure Manager. The widths are specified in the same order
as the columns are listed in the ConditionValidationResultColumnPreferences
preference.
VALID
VALUES
Any valid numerical value.
DEFAULT
VALUES
30
20
20
20
15
20
35
SCOPE
Site preference.
Platform Designer preferences

Platform Designer enables you 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 using architecture breakdowns.
Use Platform Designer preferences to modify application behavior, such as
pre-populating data fields based on preference settings.
<Architecture_Type>_generic_id_mapping
DESCRIPTION
Determines whether to prepopulate the Architecture Element ID field with the data
defined by this preference.
VALID
VALUES
Requires creating a composite preference name concatenating the desired
architecture type with _generic_id_mapping, then setting the preference with a
string. The string must be define valid Teamcenter data. For example:
Physical_generic_id_mapping=
IMAN_master_form_rev:Unit_No
This example prepopulates the Architecture Element ID field with the contents of
the Unit No field in the revision master form of the item revision selected to be
added as a solution to the physical architecture breakdown.

DEFAULT
VALUES
None.
SCOPE
Site preference.
ArchitectureModeler_add_design_business_rule_check
DESCRIPTION
Specifies the process template used to perform the business rule check for compliance
to standards. The system checks this preference value before adding a design to a
product. The business rule check process has the following elements as targets:
Architecture Revision
Architecture Breakdown
Product Item
Add Design
The workflow process for this template is initiated before the edit takes place, causing
the operation to cancel out if the workflow process cannot complete successfully
(subject to workflow handlers configured for this workflow process template).
VALID
VALUES
Accepts a single string as a value. Must be a valid process template.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ArchitectureModeler_add_design_occurrence_business_rule_check
DESCRIPTION
to occurrence standards. The system checks this preference value before adding a
design occurrence. The business rule check process has the following elements as
targets:
Product Item
Installation Assembly
The workflow process for this template is initiated after the edit takes place, causing
the operation to roll back if the workflow process cannot complete successfully
VALID
VALUES

DEFAULT
VALUES
None.
SCOPE
Site preference.
ArchitectureModeler_locking_retry_count
DESCRIPTION
Determines the number of times the system attempts to explicitly lock the system
for edits (such as Add, Remove, Replace).
When changing product architecture data in Platform Designer, multiple users
might attempt to save changes simultaneously. Such simultaneous saves are
serialized by locking the common product. If a save is blocked because the product is
already locked, Platform Designer makes as many additional attempts to lock the
product as specified in this preference.
VALID
VALUES
Accepts a positive integer as a value.
DEFAULT
VALUES
3
SCOPE
Site preference.
ArchitectureModeler_multiple_installation_assemblies_condition
DESCRIPTION
Determines the behavior of the
ArchitectureModeler_use_all_installation_assemblies preference.
VALID
VALUES
NONE The system refers to the value of the
ArchitectureModeler_use_all_installation_assemblies
preference.
Warning The system refers to the value of the
preference. If more than one installation assembly is found, a
warning displays to the user.
Error If more than one installation assembly is found, the system
stops searching and displays an error to the user.
DEFAULT
VALUES
Warning
SCOPE
Site preference.

ArchitectureModeler_part_solution_properties
DESCRIPTION
Lists all line of usage (LOU) occurrence notes and properties that Teamcenter
aggregates and displays in the architecture breakdown element (ABE). Users can
then view properties of an LOU associated with an ABE without viewing the actual
LOU object.
VALID
VALUES
bl_lou_usage_partnumber
bl_lou_usage_quantity
bl_lou_usage_architecture_id
DEFAULT
VALUES
None.
SCOPE
Site preference.
ArchitectureModeler_remove_design_business_rule_check
DESCRIPTION
to standards. The system checks this preference value before removing a design from
a product. The business rule check process has the following elements as targets:
Product Item
Remove Design
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ArchitectureModeler_RemoveDesign_Max
DESCRIPTION
Determines the maximum number of designs which can be removed at one time from
a product assembly using the RDV Remove Action command.

VALID
VALUES
DEFAULT
VALUES
30
SCOPE
User preference.
ArchitectureModeler_remove_design_occurrence_business_rule_check
DESCRIPTION
to occurrence standards. The system checks this preference value before removing a
targets:
Product Item
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ArchitectureModeler_replace_design_business_rule_check
DESCRIPTION
to standards. The system checks this preference value before replacing a design in a
product. The business rule check process has the following elements as targets:
Product Item
Replace Design

VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ArchitectureModeler_replace_design_occurrence_business_rule_check
DESCRIPTION
to occurrence standards. The system checks this preference value before replacing a
targets:
Product Item
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ArchitectureModeler_update_designs_business_rule_check
DESCRIPTION
to standards. The system checks this preference value before updating a design from
a product. The business rule check process has the following elements as targets:
Product Item
Remove Design

VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ArchitectureModeler_update_design_occurrences_business_rule_check
DESCRIPTION
to occurrence standards. The system checks this preference value before updating a
targets:
Product Item
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
DESCRIPTION
Determines whether the system stops at the first installation assembly found, or
continues walking up the tree, searching for additional installation assemblies.
VALID
VALUES
TRUE System continues searching for additional installation
assemblies.
FALSE System does not continue searching for additional installation
assemblies.
DEFAULT
VALUES
TRUE

SCOPE
Site preference.
RDV_platformdesigner_assign_bulk_variability
DESCRIPTION
Determines if the user can add and remove variability on the product context in
bulk with Platform Designer.
VALID
VALUES
true The user can add and remove variability on the product context
in bulk.
false The user cannot add and remove variability on the product
context in bulk.
DEFAULT
VALUES
true
SCOPE
Site preference.
RDV preferences
Repeatable Digital Validation (RDV) consists of software and processes that enable
on-demand digital mockups displayed in context for use throughout the product
development life cycle. RDV components include the DesignContext application,
assembly search engines, tessellation functionality, workflow handlers and change
management functionality. RDV enables on demand digital mockups for use
throughout the product development life cycle, providing the ability to visualize a
virtually configured product structure.
Use RDV preferences to modify tessellation processes.
EPM_tessellation_target_type
DESCRIPTION
Identifies potential NX datasets for tessellation as part of a workflow process. The
EPM-tessellation-handler handler compares the targets set in this preference
with the targets identified for the workflow process.
VALID
VALUES
Valid NX dataset types.
DEFAULT
VALUES
UGMASTER
UGALTREP
SCOPE
Site preference.

EPM_tessellation_servers
DESCRIPTION
Used by the EPM-tessellation-handler handler to connect to the tessellation
server. The handler sends messages to the server running on the specified host/port,
the server processes each of the messages to perform tessellations. Setting this
preference to None indicates there is no tessellation server and that tessellation
occurs on the client itself.
By default, the handler attempts to perform client-side tessellation.
VALID
VALUES
Valid port host name and port number.
DEFAULT
VALUES
None.
SCOPE
Site preference.
LOU_display_name_properties
DESCRIPTION
Determines the display name of the LOU node in the NVE tree. Applies if you use
the Replace Design in Product feature in Platform Designer, Structure Manager,
and My Teamcenter.
VALID
VALUES
Accepts a list of valid BOM line properties. The LOU node name is a concatenation
of the values listed in this preference.
DEFAULT
VALUES
None.
SCOPE
User.
PortalDesignContextProcess.WorkPartProperties
DESCRIPTION
Specifies a list of properties for finding associated work parts related to a workflow
process. If the object in process is added to the RDV context, the associated work
parts are automatically added to the RDV context. Engineering change requests are
automatically added if they are attached as reference attachments.
VALID
VALUES
Valid Teamcenter properties.
DEFAULT
VALUES
root-task:root_target_attachments

root-task:root_reference_attachments
SCOPE
Site preference.
PortalDesignContextProcess.WorkPartOrChangeAttachmentTypes
DESCRIPTION
Specifies a list of properties for finding workflow processes related to a workflow
process or engineering change being added to the RDV context. If the workflow
process is related to the work part or engineering change via one of the listed
references, and it is not yet complete, it is automatically added to the RDV context.
Workflow processes and their work part or engineering change objects can be
automatically added using this preference.
VALID
VALUES
Valid EPM attachment types, indicated by a specific integer as follows:
1 EPM_target_attachment
3 EPM_reference_attachment
4 EPM_signoff_attachment
5 EPM_release_status_attachment
6 EPM_comment_attachment
7 EPM_instruction_attachment
1000 EPM_user_attachment
DEFAULT
VALUES
1
3
SCOPE
Site preference.
RDV_audit_report_usage_attributes
DESCRIPTION
Defines which occurrence notes display in the usage audit report. Users create
the audit report by selecting an installation assembly (or any other higher level
assembly in the product structure) and generating an audit report.
VALID
VALUES
occurrence note.
DEFAULT
VALUES
Plant Cost Form
USAGE_Partnumber
USAGE_Quantity

USAGE_UPCFNA
USAGE_DLS
USAGE_PLS
USAGE_UPC
USAGE_FNA
USAGE_ModelCode
USAGE_FNM
USAGE_HandCode
USAGE_UOM
USAGE_Status
USAGE_LessFinishIndicator
USAGE_StockDisposition
USAGE_Key
USAGE_Torque1
USAGE_Torque2
USAGE_ServiceStockDisp
USAGE_EWO
USAGE_EWOStatus
USAGE_MOS01
USAGE_Product
USAGE_ModelYear
USAGE_EngineerCode
USAGE_EngineerName
USAGE_ActivityCode
USAGE_SDC
USAGE_VPPS
USAGE_SMT
USAGE_BasePart
USAGE_FirstUsedYear
USAGE_EGM
USAGE_SMTMgr
USAGE_MathStatus
USAGE_NewCO
USAGE_PADNumber
USAGE_PADSubItemNumber
USAGE_UPCOld
USAGE_FNAOld
USAGE_QuantityOld
USAGE_ModelCodeOld
SCOPE
All.
RDV_audit_report_occurrence_attributes
DESCRIPTION
Defines which occurrence notes display in the occurrence audit report. Users create
the audit report by selecting any level of an architecture breakdown and generating
an audit report.

VALID
VALUES
occurrence note.
DEFAULT
VALUES
Plant Cost Form
USAGE_Partnumber
USAGE_Quantity
USAGE_UPCFNA
USAGE_DLS
USAGE_PLS
USAGE_UPC
USAGE_FNA
USAGE_ModelCode
USAGE_FNM
USAGE_HandCode
USAGE_UOM
USAGE_Status
USAGE_LessFinishIndicator
USAGE_StockDisposition
USAGE_Key
USAGE_Torque1
USAGE_Torque2
USAGE_ServiceStockDisp
USAGE_EWO
USAGE_EWOStatus
USAGE_MOS01
USAGE_Product
USAGE_ModelYear
USAGE_EngineerCode
USAGE_EngineerName
USAGE_ActivityCode
USAGE_SDC
USAGE_VPPS
USAGE_SMT
USAGE_BasePart
USAGE_FirstUsedYear
USAGE_EGM
USAGE_SMTMgr
USAGE_MathStatus
USAGE_NewCO
USAGE_PADNumber
USAGE_PADSubItemNumber
USAGE_UPCOld
USAGE_FNAOld
USAGE_QuantityOld
USAGE_ModelCodeOld
SCOPE
All.

RDV_authoring_override_user
DESCRIPTION
Specifies the Teamcenter user ID required when adding components to installation
assemblies, or when modifying existing components in product structure using any
of the following wizards. Any defined workflow rule checks are performed against
this user.
Add Design To Product wizard
Replace Design In Product wizard
Remove Design From Product wizard

VALID
VALUES
Accepts one or more strings; each string must be a valid Teamcenter user ID. If
unset, the system processes the current user’s ID.
DEFAULT
VALUES
None.
SCOPE
Site preference.
RDV_auto_functionality
DESCRIPTION
Enables the Audit Report menu command in Structure Manager when set to True.
VALID
VALUES
True Enables the Audit Report menu command in Structure
Manager.
False Disables the Audit Report menu command in Structure
Manager.
DEFAULT
VALUES
False.
SCOPE
All.
NOTES
Values are case sensitive. Any invalid values are ignored.
RDV_auto_populate_occ_notes
DESCRIPTION
Specifies a multi-value property that contains the lists of note types that are
pre-populated in the Enter Part Data step of the Add Part to Product wizard or the
Replace Part in Product wizard.

VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
All.
NOTES
RDV_build_intent_atth_type
DESCRIPTION
Defines the attachment type for the build intent of a CORP_Build object when a
new version of a Tracking vehicle definition is imported. Tracking vehicle definitions
are imported as CORP_Build objects with an attached saved variant rule which
contains all the set option values. This rule is attached with a specification relation
to the CORP_Build revision. Tracking vehicle information is imported in the form
of a PLM XML file.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter relation
type.
DEFAULT
VALUES
IMAN_manifestation
SCOPE
All.
RDVCreateSCOForClearance
DESCRIPTION
Defines if real-time clearance analysis results are stored for subsequent retrieval.
VALID
VALUES
TRUE An SCO (structure context object) containing clearance
analysis results is created after real-time analysis is complete.
FALSE An SCO is not created after real-time analysis is complete.

DEFAULT
VALUES
TRUE.
SCOPE
Site preference.

RDV_Create_SCO_WITHOUT_APN
DESCRIPTION
Defines if the structure context objects (SCOs) created in DesignContext include
appearance path nodes (APNs) for the BOM lines. This preference does not affect
SCOs created in other applications.
VALID
VALUES
TRUE Each SCO is created without APNs for the BOM lines.
FALSE Each SCO is created with APNs for the BOM lines.
DEFAULT
VALUES
TRUE if you install the GM Overlay.
FALSE if you do not install the GM Overlay.
SCOPE
All.
RDV_copied_occurrence_notes
DESCRIPTION
Specifies the note types whose values are copied from the instance of the associated
part solution when present, that is, sharing the same named variant expression, to
the occurrence of the design solution in Structure Manager. This list must match
that in the RDV_usage_occurrence_notes preference.
VALID
VALUES
occurrence note.
DEFAULT
VALUES
None.
SCOPE
All.
RDV_default_Architecture_Breakdown_RevRule
DESCRIPTION
Defines the default revision rule the Platform Designer application uses to open an
architecture breakdown.
VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter revision rule.
DEFAULT
VALUES
Latest Released

SCOPE
All.
RDV_enable_product_lock
DESCRIPTION
Allows the rdv_import_usage utility to obtain locks on the product revision or
top-level architecture node if they are held by other nonsystem administration
processes.
VALID
VALUES
TRUE Allows the utility to obtain the necessary locks if they are held
by other processes.
FALSE Does not allow the utility to obtain the necessary locks if they
are held by other processes.
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
RDV_export_nve
DESCRIPTION
Determines whether named variant expressions (NVEs) are exported during a
multisite replication session.
NVEs are referenced by various variant expression blocks (VEBs). Because any
VEBs included in an architecture structure own the NVEs, these NVEs only need to
be exported during architecture export, not during the export of other assemblies.
Use this preference to allow users to determine the export of NVEs in a given session.
VALID
VALUES
TRUE NVEs are exported during multisite replication sessions.
FALSE NVEs are not exported during multisite replication sessions.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
RDVIgnoreErrorConnectReleasedPartsServer
DESCRIPTION
Determines whether the EPM-add-released-parts-queue workflow handler
checks if the Released Parts Collector server is running.

VALID
VALUES
True Allows the EPM-add-released-parts-queue workflow
handler to check if the Released Parts Collector server is
running. If the server is running, the item types defined in
the RDVReleasedPartsProcessAssemType preference are
released. If the server is not running, the item types are not
released.
False The item types defined in the
RDVReleasedPartsProcessAssemType preference are
released, regardless of whether the Released Parts Collector
server is running.
DEFAULT
VALUES
None.
SCOPE
Site preference.
RDV_install_configuration_rules
DESCRIPTION
Defines the revision rules used to configure the installation assembly in a product.
The Add Design To Product wizard creates new occurrences in the Installation
Assembly revision that is configured by the revision rule defined in this preference.
If your site chooses to grant write access only to Work In Process (WIP) revisions
this would be a WIP revision rule. For example, Latest Working. This includes
user-defined revision rules set with the RDV_authoring_override_user
preference.
VALID
VALUES
Accepts one or more strings; each string must be a valid Teamcenter revision rule.
DEFAULT
VALUES
Latest Working
SCOPE
User preference.
RDV_occurrence_business_rule_check
DESCRIPTION
Defines the list of process templates used to implement business rule checks for
occurrences of the part.
VALID
VALUES
Accepts one or more strings; each string must be a valid Teamcenter process
template.

DEFAULT
VALUES
None.
SCOPE
Site preference.
RDV_part_business_rule_check
DESCRIPTION
Defines the list of process templates used to implement business rule checks for
individual parts.
VALID
VALUES
Accepts one or more strings; each string must be a valid Teamcenter process
template.
DEFAULT
VALUES
None.
SCOPE
Site preference.
RDV_partnumber_validation_rule
DESCRIPTION
Specifies a single-value property that determines if a design solution has a valid part
number. A naming rule has to be created in Business Modeler IDE and the pattern
specified for this naming rule determines what is a valid part number. The name of
this naming rule must be set in this preference.
VALID
VALUES
Accepts a string as a value. This string represents the name of the naming rule.
DEFAULT
VALUES
None.
SCOPE
All.
NOTES
RDV_part_occ_note_mappings
DESCRIPTION
Specifies a multivalue property that contains the lists of values that prepopulate
the notes displayed in the Enter Part Data step of the Add Part to Product
wizard or the Replace Part in Product wizard. The note types are specified in
RDV_auto_populate_occ_notes preference.

VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
All.
NOTES
RDV_product_code_mapping
DESCRIPTION
Specifies a single-value mapping property that contains the value to prepopulate
the Usage_Product note displayed in the Enter Part Data pane of the Add Part
to Product wizard.
VALID
VALUES
Accepts a string as a value.
DEFAULT
VALUES
Items_tag:item_id
SCOPE
All.
NOTES
RDVReleasedPartsProcessAssemType
DESCRIPTION
Defines the Item types which can be processed during the structure update process.
When an installation assembly is modified and released, it is added to the queue and
updated asynchronously. The system uses the EPM-add-released-parts-queue
workflow handler to pass the installation assembly to the list of assemblies for
processing. This preference determines which Item types the handler is allowed to
process.
VALID
VALUES
type. For example:
RDVReleasedPartsProcessAssemType=
CORP_Install
DEFAULT
VALUES
None.

SCOPE
Site preference.
RDVReleasedPartsCollectorServer
DESCRIPTION
Defines the host name and port number of the machine on which the Released Parts
Collector server is running.
VALID
VALUES
Accepts a single string as a value. Must define the host name and port number
in the following format:
host name:port number
For example:
trysun12:1551
DEFAULT
VALUES
None.
SCOPE
Site preference.
RDV_show_itemid_prefix
DESCRIPTION
Determines if the XO chart headers of the Replace Design in Product feature include
the item ID. This feature is available in Platform Designer, Structure Manager,
and My Teamcenter.
VALID
VALUES
TRUE The XO chart headers include the item ID.
FALSE The XO chart headers do not include the item ID.
DEFAULT
VALUES
None.
SCOPE
Site.
RDV_show_lou_prop
DESCRIPTION
Registers new property columns and adds them to the Available Properties list in
Structure Manager and Platform Designer. The user can then add any of these
columns by right-clicking and choosing Insert Column from the list. Teamcenter
shows the properties of the configured part solutions of an architecture breakdown
element (ABE), as a comma-separated string on the ABE itself.

VALID
VALUES
Any valid property name prefixed with bl_lou_.
DEFAULT
VALUES
None.
SCOPE
User preference.
RDV_turn_audit_logging_on
DESCRIPTION
Determines whether audit logging for global RDV is enabled. These audit logs
contain information about the changes in the vehicle assembly structure (VAS) over
a period of time, including logging changes to the assembly structure from sources
other than Teamcenter (such as NX or other CAD application integrations).
VALID
VALUES
true The audit log file is updated whenever the Replace Design in
Product wizard and the Add design to Product wizard are
run by users.
false The audit log file is not updated.
DEFAULT
VALUES
false
SCOPE
Site preference.
RDV_uneditable_part_occ_notes
DESCRIPTION
Specifies the occurrence notes that are not editable in the Enter Part Data screen of
the Add Part to Product wizard or the Replace Part in Product wizard.
VALID
VALUES
Accepts multiple strings as values.
DEFAULT
VALUES
Usage_product
SCOPE
All.
NOTES

RDV_usage_attribute_set
DESCRIPTION
Defines the list of attributes applied when a usage record is imported for the first
time.
A ArchPartUsage occurrence type is created under the Top Level Architecture
node. This occurrence points to the CORP_Part object if a CORP_Part object
with the corresponding part number exists. (If not, a placeholder CORP_Part
object is created with an alphanumeric ID and attached to the occurrence.) Which
attributes are imported into Teamcenter as part of the Usage Record are specified
by this preference. Corresponding occurrence note names are specified by the
RDV_usage_occurrence_notes preference.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter attribute.
DEFAULT
VALUES
None.
SCOPE
All.
RDV_usage_occurrence_notes
DESCRIPTION
Defines the occurrence note names that are displayed in the Enter Part Data step
of the Add Part to Product wizard or the Replace Part in Product wizard. The
corresponding attribute names are defined in the RDV_usage_attribute_set
preference.
VALID
VALUES
occurrence note.
DEFAULT
VALUES
Usage_Product, Usage_PartNumber, Usage_Quantity.
SCOPE
All.
NOTES
Values are case sensitive.
Any invalid values are ignored.
RDV_valid_partnumber_rule
DESCRIPTION
Defines the naming rule used for part number validation.

VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter naming rule.
For more information regarding naming rules, see the Business Modeler IDE Guide.
DEFAULT
VALUES
null
SCOPE
All.
RDV_variant_expression_overlap_checking_mode
DESCRIPTION
Determines the mode used to check overlap between variant expressions.
Architecture breakdown structures may be configured to check for named variant
expression (NVE) consistency. This consistency check rejects NVEs that overlap
with other NVEs.
VALID
VALUES
1 The system assumes an unlimited continuum of values in
the product variability. For example, the system assumes an
unlimited number of intermediate values between Length = 2
meter and Length = 3 meter, such as a length of 2.50 meters.
2 The system uses the defined variability, with exactly and only
those values allocated.
5 Same as setting 1, but NVEs are permitted on architecture
elements even when they go beyond the variability specified
for this element.
6 Same as setting 2, but NVEs are permitted on architecture
elements even when they go beyond the variability specified
for this element.
DEFAULT
VALUES
1
SCOPE
All.
RDV_variant_overlays_mode
DESCRIPTION
Defines the algorithm used to determine valid overlay only (VOO) in DesignContext’s
Filter Configuration pane.
VALID
VALUES
0 Dynamic mode.

1 (static mode) Uses the static subset of all variant rules available for the
top-level for which at least one target BOM line configures.
This is useful when the set of saved variant rules covers all
valid option value combinations. In this case, static overlay
variant rules produce acceptable results without the need to
have rule checks managed in Structure Manager.
The list of relevant product variants (or variant families) is a
subset of saved variant rules associated to the product (top
level). Results are typically faster then dynamic mode, but
still acceptable if the number of saved variant rules covers
all relevant product variants.
2 (hybrid mode) Uses dynamic mode unless the number of variable options is
greater than the preset value.
4 (bit pattern mode) Uses a bit pattern transformation of the variant model to
calculate variant rules. (This method is similar to the X-O
charts used in Platform Designer.)
DEFAULT
VALUES
0
SCOPE
All.
RDV_variant_overlays_uses_true_availability
DESCRIPTION
Determines whether rule checks and variability are evaluated in the variants overlay
only (VOO) analysis when using RDV.
VALID
VALUES
TRUE Expands conditions into True Availability statements.
May slow VOO analysis. Only available when the
RDV_variant_overlays_mode preference is set to 4.
FALSE Conditions are not expanded.
DEFAULT
VALUES
FALSE
SCOPE
All.
BOMWriterDirectModelRelationType
DESCRIPTION
Used with the bomwriter utility. The system searches the direct model based on
the relation type specified in this preference.

The bomwriter utility’s PLM XML file outputs direct model (JT) information
available in the product structure. The system retrieves this information based on
the relation type specified in this preference.
VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter relation type.
DEFAULT
VALUES
IMAN_Rendering
SCOPE
Site preference.
BOMWriterNoDescendantsInPLMXML
DESCRIPTION
Used with the bomwriter utility. Controls export of descendants (children and
grandchildren) of selected BOM lines when Teamcenter’s lifecycle visualization or
NX is launched from the Teamcenter rich client.
This preference determines whether the bomwriter utility generates PLM XML
files which include descendants of the selected BOM lines.
Set this preference to TRUE (suppressing descendants) if the application for which
the PLM XML file is intended supports navigating Teamcenter structures (such as
NX). If the file is intended for other applications (such as Teamcenter’s lifecycle
visualization mockup) you may want to include descendents as they cannot load
substructures on demand.
VALID
VALUES
TRUE Descendents of selected BOM lines are not exported in the
PLM XML file, and are not displayed in Teamcenter’s lifecycle
visualization or NX.
FALSE Descendents of selected BOM lines are exported in the
PLM XML file, and are displayed in Teamcenter’s lifecycle
visualization or NX.
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
BOMWriterNoDirectParents
DESCRIPTION
Used with the bomwriter utility. Controls export of predecessors (parents and
grandparents) of selected BOM lines when Teamcenter’s lifecycle visualization or
NX is launched from the Teamcenter rich client.
This preference determines whether the bomwriter utility generates PLM XML
files which include predecessors of the selected BOM lines.

VALID
VALUES
TRUE Predecessors of selected BOM lines (except the root node) are
not exported in the PLM XML file, and are not displayed in
Teamcenter’s lifecycle visualization or NX.
FALSE Predecessors of selected BOM lines (except the root node)
are exported in the PLM XML file, and are displayed in
Teamcenter’s lifecycle visualization or NX.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
Quick spatial search preferences

The quick spatial search mechanism is used by several applications including
Structure Manager and DesignContext to allow searches of configured product
structures without the need to maintain secondary data caches.
QS_QSEARCH_ENABLED
DESCRIPTION
Enables or disables the cacheless search mechanism.
VALID
VALUES
true Enables the cacheless search mechanism with attribute
searches in Structure Manager.
false Disables the cacheless search mechanism. Select this value if
you use appearance searches.
DEFAULT
VALUES
true
SCOPE
Site preference.
NOTES
During installation, you can choose to deactivate the cacheless search mechanism.
Enabling this mechanism incurs a processing overhead while Teamcenter creates
the necessary secondary data. If you have a large amount of legacy data, creation
may take an appreciable time.
RESTRICTIONS
If this mechanism is disabled during upgrade, Teamcenter does not generate the
secondary data and users are unable to perform cacheless spatial searches.

QSEARCH_update_enabled
DESCRIPTION
Enables or disables the automatic updating of indexes used by the cacheless spatial
search mechanism.
VALID
VALUES
true Enables automatic updates of spatial search indexes. The
spatial index box data needed for spatial searches is generated
for modified parts.
false Disables automatic updates of spatial search indexes. Spatial
index box data is not generated when parts are modified;
spatial searches are unavailable due to lack of spatial data.
DEFAULT
VALUES
false
SCOPE
Site preference.
QS_SPATIAL_ENABLED
DESCRIPTION
Enables or disables spatial searches (for example, proximity or box searches) within
the cacheless search mechanism. If spatial searches are disabled, the user can still
make attribute searches.
VALID
VALUES
true Enables spatial searches.
false Disables spatial searches.
DEFAULT
VALUES
false
SCOPE
Site preference.
QS_TRUSHAPE_GENERATION_ENABLED
DESCRIPTION
Enables or disables the generation of TruShape data needed by the cacheless spatial
search mechanism. This preference is initially set by the Teamcenter Environment
Manager (TEM) during installation, according to the cacheless search options
selected.
VALID
VALUES
true Enables the generation of TruShape data needed by the
cacheless spatial search mechanism.

false Disables the generation of TruShape data needed by the

DEFAULT
VALUES
false
SCOPE
Site preference.
NOTES
During installation, you can choose to deactivate the generation of TruShape data.
Enabling generation incurs a processing overhead while Teamcenter creates the
necessary secondary data. If you have a large amount of legacy data, creation may
take an appreciable time.
This preference should be set to False if you use the Teamcenter Integration for
NX, as TruShape files are automatically saved in the NX datasets. (You must also
explicitly configure NX to save TruShape data.)
RESTRICTIONS
If creation is disabled during upgrade, Teamcenter does not generate the secondary
data and users are unable to perform cacheless spatial searches. Warning messages
may also be generated during other types of search.
QS_BBOX_GENERATION_ENABLED
DESCRIPTION
Enables or disables the generation of bounding box data needed by the cacheless
spatial search mechanism. This preference is initially set by the Teamcenter
Environment Manager (TEM) during installation, according to the cacheless search
options selected.
VALID
VALUES
true Enables the generation of bounding box data needed by the
false Disables the generation of bounding box data needed by the

DEFAULT
VALUES
false
SCOPE
Site preference.
NOTES
During installation, you can choose to deactivate the generation of bounding box
data. Enabling generation incurs a processing overhead while Teamcenter creates
the necessary secondary data. If you have a large amount of legacy data, creation
may take an appreciable time.
This preference should be set to False if you use the Teamcenter Integration for NX,
as bounding boxes are automatically generated from the NX bounding box forms.

RESTRICTIONS
If creation is disabled during upgrade, Teamcenter does not generate the secondary
data and users are unable to perform cacheless spatial or box zones searches.
Warning messages may also be generated during other types of search.
QS_BBOX_GENERATION_FROM_NX_ENABLED
DESCRIPTION
Enables or disables the generation of bounding box data from the UGPART-BBOX
form of an NX dataset.
VALID
VALUES
true Enables the generation of bounding box data needed by the
false Disables the generation of bounding box data needed by the
DEFAULT
VALUES
false
SCOPE
Site preference.
QS_MAX_QUERY_EXECUTION_TIME_FOR_BOTTOMUP
DESCRIPTION
Defines a maximum time for each query to execute and return results. This
preference is effective only when you use bottom-up searches. Set a value that
prevents slow queries from adversely affecting system performance.
VALID
VALUES
Any value in milliseconds.
DEFAULT
VALUE
500
SCOPE
Site preference.
RDV_QSEARCH_REFINE
DESCRIPTION
Enables the use of TruShape data to refine DesignContext searches. This preference
applies only if you use the cacheless search engine. Users can select the Refine
Cacheless Search→Use True Shape Search user option to change this setting
for their own searches.

VALID
VALUES
true Spatial searches in DesignContext use TruShape and bounding
box data.
false Spatial searches in DesignContext use bounding box data, not
TruShape data.
DEFAULT
VALUES
false
SCOPE
All.
RDV_QSEARCH_REVISION_RULE_NAMES
DESCRIPTION
Specifies the names of preferred revision rules for DesignContext searches. This
preference applies only if you use the cacheless search engine.
VALID
VALUES
Accepts a single string as a value. The string contains one or more valid revision
rule names.
DEFAULT
VALUES
None
SCOPE
All.
RDV_QSEARCH_STREAMING_MODE
DESCRIPTION
Specifies how the third screen of DesignContext is updated with search results. This
preference applies only if you use the cacheless search engine.
VALID
VALUES
true Teamcenter updates the tables in streaming mode. The user
can interrupt the update process at any time.
false Teamcenter updates the tables only when all the search results
are available. The user cannot interrupt the update process.
DEFAULT
VALUES
false
SCOPE
Site preference.

Chapter
20 Teamcenter’s manufacturing
process management preferences
General manufacturing preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Baseline_omitted_occurrence_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
controllingOccsForProcessConfiguration . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
MEAlignedPropertiesList . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
MEAlignedPropertiestoExcludeFromDetection . . . . . . . . . . . . . . . . . . . . 20-3
MEAlignedPropertiestoExcludeFromInitialization . . . . . . . . . . . . . . . . . . 20-3
MEAlignedPropertiestoExcludeFromSync . . . . . . . . . . . . . . . . . . . . . . . . 20-4
MEAlignmentCheckReportLocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
MEAlignmentCheckReportDefinition . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
MEAlignmentCheckReportStylesheet . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
TC_CRF_overwrite_existing_dataset_content . . . . . . . . . . . . . . . . . . . . . 20-5
MEManufacturingDefaultBVR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
MEAssignCustomizedOccurrenceType . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
MEOccTypeConsumed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7
MSE_ICS_default_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7
MRMPropagationRevisionRule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7
IPADefaultEmailMessage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8
MPP_DefaultCandidateSearchCriteria . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8
MPP_BrokenLinkSearchCriteriaList . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
NX_supported_operation_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
TC_NX_FileNewPAXFiles_NX<version> . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
ReportXMLGenerationRules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10
2D_Viewer_default_load_relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-12
MELineLinkedIconsProperty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-12
GDEOcc_display_instance_num_for_types . . . . . . . . . . . . . . . . . . . . . . 20-13
FindCheckedOutColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13
FindCheckedOutColumnsShownWidthPref . . . . . . . . . . . . . . . . . . . . . . 20-14
TC_show_checkout_objects_on_exit . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-14
MERelationTypeUsedEquipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
MERelationTypePartsAssigned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
MERelationTypePartsConsumed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
MERelationTypePartsHandled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16
MERelationTypePartsAssembled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16
MERelationTypePartsDisassembled . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16
MERelationTypePartsOtherAssigned . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
MERelationTypePartsFeature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
MESecondStructurePosition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
MEDataPanelPosition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-18
MEExpandFirstLevelOnLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-18
MEExpandToSelection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-18

MEBlankDisplayTypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-19
MSE_load_related_product_process_plant . . . . . . . . . . . . . . . . . . . . . . . 20-20
MEHideChangesIconsForAttributes . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-20
MECopyIdInContextToAssignedLine . . . . . . . . . . . . . . . . . . . . . . . . . . 20-21
MECopyIdInContextLowerLevels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-21
MEMFGDisplayName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-22
MRMItemTypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-22
MEConsiderFlowsOnReSequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-23
Cloning preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-23

Product.Template.Cloning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-23
Product.Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-24
Plant.Template.Cloning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-24
Plant.Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-25
Process.Template.Mapping_Consumes . . . . . . . . . . . . . . . . . . . . . . . . . 20-25
Process.Template.Referencing_Consumes . . . . . . . . . . . . . . . . . . . . . . . 20-26
Process.Template.Ignoring_Consumes . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
Process.Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
Clone_Pending_Release_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-28
Clone_Secured_Release_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-28
PERT chart preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-29

PertChart.<object_type>.GColor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-29
PertChart.<object_type>.Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-29
PertChart.AutoSizeMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-30
PertChart.BoxAutoSizeMaxWidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-31
PertChart.BoxDefaultWidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-31
PertChart.BoxDefaultHeight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-32
PertChartCreationLayout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-32
Accountability check preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-32

DefaultAccountabilityCheckProperties . . . . . . . . . . . . . . . . . . . . . . . . . 20-33
AdditionalAccountabilityCheckProperties . . . . . . . . . . . . . . . . . . . . . . . 20-33
AccountabilityCheckReportStylesheetName . . . . . . . . . . . . . . . . . . . . . 20-34
MEAccountabilityCheckSourceStructureExpansionFilterRules . . . . . . . . 20-35
MEAccountabilityCheckTargetStructureExpansionFilterRules . . . . . . . . 20-35
MEAccountabilityCheckEnableFilteringRules . . . . . . . . . . . . . . . . . . . . 20-36
MEAccountabilityCheckEnableNetEffectivity . . . . . . . . . . . . . . . . . . . . 20-36
MEResultViewSourceColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . 20-36
MEResultViewSourceColumnsShownWidthPref . . . . . . . . . . . . . . . . . . 20-37
MEResultViewTargetColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . 20-37
MEResultViewTargetColumnsShownWidthPref . . . . . . . . . . . . . . . . . . . 20-38
Time management preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-38

MEAvailableTimeUnits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-38
MECurrentTimeUnit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-39
METimeTabFilteredComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-39
MEOperationActivitiesFilteredComponents . . . . . . . . . . . . . . . . . . . . . 20-40
MEActivityTypeColors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-40
MEDefaultActivityType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-41
METimesActivityShownColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-41
METimesActivityShownColumnWidths . . . . . . . . . . . . . . . . . . . . . . . . 20-41
METimeAnalysisReportDefinitionID . . . . . . . . . . . . . . . . . . . . . . . . . . 20-42
MEAllocatedTimeReportDefinitionID . . . . . . . . . . . . . . . . . . . . . . . . . . 20-42

METimeAnalysisReportStylesheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-43
MEAllocatedTimeReportStylesheet . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-43
METimeDataCardPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-43
METimeDataCardConversionFactor . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-44
METIMEAllocatedTimePopulationMode . . . . . . . . . . . . . . . . . . . . . . . . 20-44
METIMEPopulateAllocatedTimeUsedSources . . . . . . . . . . . . . . . . . . . . 20-45
METIMEPopulateAllocatedTimeUpToLevelEnabled . . . . . . . . . . . . . . . 20-46
METIMEPopulateAllocatedTimeUpToLevel . . . . . . . . . . . . . . . . . . . . . 20-46
METIMEPopulateAllocatedTimeZeroValuesEnabled . . . . . . . . . . . . . . . 20-46
Publishing preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 20-47

AppInterface_TCPublishingTechnicalPortfolio_default_relation . . . . . .. 20-47
AppInterface_TCPublishingTechnicalPortfolio_shown_relations . . . . . .. 20-48
IMAN_PublishingPageAssetContext_relation_primary . . . . . . . . . . . . .. 20-48
IMAN_TCPublishedPortfolio_relation_primary . . . . . . . . . . . . . . . . . .. 20-48
ItemRevision_TCPublishingPage_default_relation . . . . . . . . . . . . . . . .. 20-49
<TC Publishing Technical Portfolio type>_DefaultChildProperties . . . . .. 20-49
<TC Publishing Page type>_DefaultChildProperties . . . . . . . . . . . . . . .. 20-50
TCPublishing_Aliases.IMAN_MEWorkInstruction . . . . . . . . . . . . . . . .. 20-50
TCPublishing_Default_Alias_File . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 20-50
TCPublishing_Activities_Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 20-51
TCPublishing_Aliases.Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 20-51
IMAN_PortfolioConfiguredPage_relation_primary . . . . . . . . . . . . . . . .. 20-52
IMAN_PortfolioPage_relation_primary . . . . . . . . . . . . . . . . . . . . . . . .. 20-52
TechnicalPortfolioRoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 20-52
TechnicalPortfolioTransferMode_IMAN_MEWorkInstruction . . . . . . . .. 20-53
IMAN_MEWorkInstruction_relation_primary . . . . . . . . . . . . . . . . . . .. 20-53
VisAssetPopulatedByEndobj_relation_primary . . . . . . . . . . . . . . . . . .. 20-54
TCPublish_managed_asset_properties . . . . . . . . . . . . . . . . . . . . . . . .. 20-54
TCPublish_synchronized_asset_relations . . . . . . . . . . . . . . . . . . . . . .. 20-54
TCPUBLISH_BATCH_ROLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 20-55
TCPUBLISH_BATCH_<role>_TEMPLATES . . . . . . . . . . . . . . . . . . . .. 20-55
TCPUBLISH_BATCH_<role>_PAGE_TEMPLATE_FAVORITES . . . . . .. 20-55
TCPUBLISH_BATCH_<role>_PORTFOLIO_TEMPLATE_FAVORITES . . 20-56
TCPUBLISH_BATCH_CLASSES . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 20-56
PAD preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-56

MEPSDTableShownColumnWidthsPref . . . . . . . . . . . . . . . . . . . . . . . . 20-57
MEPSDTableColumnsShownPref.SORTING_COLUMN . . . . . . . . . . . . . 20-57
MEPADChildTypesPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-58
MEPSDTableColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-58
Manufacturing search preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-58

ME_Proximity_search_result_occ_type . . . . . . . . . . . . . . . . . . . . . . . . . 20-59
ME_Proximity_search_result_occ_group_type . . . . . . . . . . . . . . . . . . . . 20-59
ME_Proximity_search_result_root_name . . . . . . . . . . . . . . . . . . . . . . . 20-59
ME_Proximity_FilteredIPA_suffix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-60
MEAdvancedSearchResultsViewColumnsShownPref . . . . . . . . . . . . . . . 20-60
MEAdvancedSearchResultsViewColumnsShownWidthPref . . . . . . . . . . . 20-60
MEAPCSearchType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-61
Enterprise BOP preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-62

MEGenericBopContextColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . 20-62
MEGenericBopContextColumnsShownWidthsPref . . . . . . . . . . . . . . . . . 20-62

MEProductBopContextColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . 20-62
MEProductBopContextColumnsShownWidthsPref . . . . . . . . . . . . . . . . . 20-63
MEGenericBopContextPartitionColumnsShownPref . . . . . . . . . . . . . . . 20-63
MEGenericBopContextPartitionColumnsShownWidthsPref . . . . . . . . . . 20-64
MEProductBopContextPartitionColumnsShownPref . . . . . . . . . . . . . . . 20-64
MEProductBopContextPartitionColumnsShownWidthsPref . . . . . . . . . . 20-64
MEAssignmentsViewColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . 20-65
MEAssignmentsViewColumnsShownWidthPref . . . . . . . . . . . . . . . . . . . 20-65
MELogicalDesignatorFormNameSuffix . . . . . . . . . . . . . . . . . . . . . . . . . 20-66
MELogicalDesignatorDelimiter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-66
GenericBOPTemplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-67
ProductBOPTemplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-67
GenericBOPAllowedTemplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-68
ProductBOPAllowedTemplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-68
MEGenericBOP.MEGenericBOP.PasteDuplicateTemplate . . . . . . . . . . . . 20-69
MEGenericBOP.MEProductBOP.PasteDuplicateTemplate . . . . . . . . . . . . 20-69
MEProductBOP.MEProductBOP.PasteDuplicateTemplate . . . . . . . . . . . 20-70
MEProductBOP.MEGenericBOP.PasteDuplicateTemplate . . . . . . . . . . . . 20-71
PasteDuplicateTemplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-71
GANTT chart viewer preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-72

MEGANTTElementHeight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-72
MEGANTTElementRGBfillColor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-72
MEGANTTDefaultDisplayMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-73
MEGANTTDefaultDurationTimeMode . . . . . . . . . . . . . . . . . . . . . . . . . 20-73
MEGANTTDefaultEditMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-73
MEGANTTDefaultMarkedColor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-74
MEGANTTDefaultDurationTimeColor . . . . . . . . . . . . . . . . . . . . . . . . . 20-74
MEGANTTDefaultFlowColor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-74
MEGANTTMarkedFlowColor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-75
MEGANTTimplicitFlowColor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-75
MEGANTTPropagateDurationUpToLevel . . . . . . . . . . . . . . . . . . . . . . . 20-75
MEGANTTPropagateDurationUpToLevelEnabled . . . . . . . . . . . . . . . . . 20-76
Manufacturing features preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-76

MEImportMFGsPartIdAttributeName . . . . . . . . . . . . . . . . . . . . . . . . . 20-77
MEImportMFGsManufacturingFeatureIdAttributeName . . . . . . . . . . . . 20-77
MENEWMFG_DefaultJTDatasetName . . . . . . . . . . . . . . . . . . . . . . . . . 20-77
MENEWMFG_DeffaultJTFileName . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-78
MENEWMFG_LastJTFilePathBrowsed . . . . . . . . . . . . . . . . . . . . . . . . 20-78
MEMFGViewColumnShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-78
MEMFGViewShownColumnWidthsPref . . . . . . . . . . . . . . . . . . . . . . . . 20-79
MEShowWeldPointsConnectedToConfiguredOutParts . . . . . . . . . . . . . . 20-79
MEMFGViewSubPanelColumnShownPref . . . . . . . . . . . . . . . . . . . . . . . 20-80
MEMFGViewSubPanelShownColumnWidthsPref . . . . . . . . . . . . . . . . . 20-80
MEMFGView_AssignmentFilterDefaultValue . . . . . . . . . . . . . . . . . . . . 20-80
Standard text preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-81

MEWiWorkInstructionTemplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-81
MEWiStandardTextTemplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-81
MEWiPreviewFormat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-82
MEWiDcdNotEditableProperties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-82
Process Simulate preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-83

MEDataSetsToBeCheckoutForProcessSimulate . . . . . . . . . . . . . . . . . . . 20-83
MEFormsToBeCheckoutForProcessSimulate . . . . . . . . . . . . . . . . . . . . . 20-84
MEReportColumnsForProcessSimulate . . . . . . . . . . . . . . . . . . . . . . . . . 20-84
MEReportColumnWidthForProcessSimulate . . . . . . . . . . . . . . . . . . . . . 20-85
PLMXML_pre_expand_bop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-85
PLMXML_pre_expand_max_line_limit . . . . . . . . . . . . . . . . . . . . . . . . . 20-86
PLMXML_pre_expand_batch_size . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-86

Chapter
20 Teamcenter’s manufacturing
process management preferences
The suite of Teamcenter’s manufacturing process management applications provides

an environment that allows engineering and manufacturing teams to synchronize
design data, share design models in workflow-driven processes, and collaborate
across a fully digital environment. Combining these capabilities can improve product
quality, reduce time and cost to manufacture, and accelerate the product life cycle.
Manufacturing Process Management preferences modify the display and behavior of
the Manufacturing Process Management applications. Many of the manufacturing
preferences begin with the ME prefix. This stands for Manufacturing Environment.
General manufacturing preferences

Use these preferences to configure a variety of features within the manufacturing
applications, such as incremental change, EBOM MBOM alignment, and broken
links reconciliation.
Baseline_omitted_occurrence_types
DESCRIPTION
Determines which BOM lines display when building a manufacturing baseline. BOM
lines containing occurrence notes defined in this preference are omitted.
Manufacturing baselines are a convenient method of releasing composition/process
structures whose contents do not change over time.
For more information, see Getting Started with Manufacturing.
VALID
VALUES
Accepts multiple strings as values; each string must be a valid occurrence type.

Chapter 20 Teamcenter’s manufacturing process management preferences
DEFAULT
VALUES
MEResource
Omits all BOM lines containing MEResource occurrence notes from a
manufacturing baseline.
SCOPE
Site preference.
controllingOccsForProcessConfiguration
DESCRIPTION
Controls automatic configuration of operations and processes. If no value is set, the
configuration of operations is not affected by the configuration of consumed items.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid occurrence type.
DEFAULT
VALUES
MEConsumed
SCOPE
Site preference.
MEAlignedPropertiesList
DESCRIPTION
Defines a base list of BOM line properties that Teamcenter considers during the
initialization, comparison, and synchronization of aligned occurrences in the EBOM
and MBOM. Only property values that are available in the current context of the
BOM line are considered; that is, they may be override values.
VALID
VALUES
Any valid BOM line properties.
DEFAULT
VALUES
bl_plmxml_abs_xform
bl_quantity
bl_uom
bl_all_notes
bl_occurrence_type
bl_part_source
SCOPE
Site preference.
NOTES
If Teamcenter should consider all occurrence notes, specify the bl_all_notes
property.
The bl_child_item and bl_substitute_list properties may also be specified.

Teamcenter’s manufacturing process management preferences
RESTRICTIONS
Teamcenter uses the properties specified in this preference during synchronization
actions. Any property that Teamcenter cannot set in the BOM Line column may not
synchronize correctly. The bl_child_item and bl_substitute_list properties are
exceptions to this restriction.
MEAlignedPropertiestoExcludeFromDetection
DESCRIPTION
Defines a list of BOM line properties that are not compared when aligning
occurrences in the EBOM and MBOM.
VALID
VALUES
DEFAULT
VALUES
bl_uom
bl_all_notes
bl_part_source
SCOPE
Site preference.
NOTES
If Teamcenter should exclude all occurrence notes, specify the bl_all_notes property.
MEAlignedPropertiestoExcludeFromInitialization
DESCRIPTION
Defines a list of BOM line properties that are not copied to the aligned target
occurrence during initialization.
VALID
VALUES
DEFAULT
VALUES
bl_uom
occ_type
SCOPE
Site preference.
NOTES
If a property is not specified in the MEAlignedPropertiesList preference, it is
ignored.
RESTRICTIONS
Teamcenter uses the ChildItem property during the creation of the target
occurrence, even it is listed in this preference for inclusion.

MEAlignedPropertiestoExcludeFromSync
DESCRIPTION
Defines a list of BOM line properties that are not copied to the aligned target
occurrence during synchronization.
VALID
VALUES
DEFAULT
VALUES
bl_uom
bl_all_notes
bl_part_source
occ_type
SCOPE
Site preference.
NOTES
MEAlignmentCheckReportLocation
DESCRIPTION
Defines if a persisted EBOM-MBOM alignment report is stored in a dataset in
the My Teamcenter Newstuff folder or if it is attached to the item revision of the
top line of the target window.
VALID
VALUES
0 The alignment check report is stored in the Newstuff folder.
1 The alignment check report is stored on the item revision of
the top line of the target window.
DEFAULT
VALUE
0
SCOPE
User preference.
MEAlignmentCheckReportDefinition
DESCRIPTION
Contains the name of the report definition that controls the creation of the
EBOM-MBOM alignment check report. A default report definition is provided but
you can supply a custom report definition if necessary.
VALID
VALUES
A single character string that contains the name of an existing report definition
object.

DEFAULT
VALUE
AlignmentCheckReportDefinition
SCOPE
Site preference.
MEAlignmentCheckReportStylesheet
DESCRIPTION
Contains the name of the Microsoft Excel style sheet on which the EBOM-MBOM
alignment check report is based. A default style sheet is provided, but you can
supply a custom style sheet if necessary.
VALID
VALUES
A single character string that contains the name of an existing Microsoft Excel
style sheet.
DEFAULT
VALUE
AlignmentCheckReport.xls
SCOPE
Site preference.
TC_CRF_overwrite_existing_dataset_content
DESCRIPTION
Determines if a newly generated report, such as the EBOM-MBOM alignment check
report or the time analysis report, replaces the existing contents of the dataset or
if it is appended.
VALID
VALUES
true The newly generated report replaces the existing contents of
the dataset.
false The newly generated check report is appended to the dataset.
DEFAULT
VALUE
true
SCOPE
Site preference.
MEManufacturingDefaultBVR
DESCRIPTION
Determines which BOM view revision is opened in Manufacturing Process Planner
and Part Planner when more than one BOM view revision is defined in the related
product. If not defined, the BOM view revision first created for the product is opened.

VALID
VALUES
Accepts a single string as value. The string must be a valid BOM view revision.
For example:
Manufacturing
DEFAULT
VALUES
None.
SCOPE
All.
MEAssignCustomizedOccurrenceType
DESCRIPTION
By default, if a relation (occurrence) type is defined for a BOM line and you
assign the BOM line to a process or operation, Teamcenter uses the same relation
(occurrence) type. Use this preference to configure a different relation (occurrence)
type to apply to assignment, paste, and drag-and-drop actions.
VALID
VALUES
The value format is A.B:C, where:
• A is the item type of a process or operation.
• B is the item type of the assigned BOM line that possesses the occurrence type.
• C is the occurrence type to be used instead.
For example:
MEAssignCustomizedOccurrenceType=
MEProcess.WeldPoint:MEConsumed
MEProcess.DatumPoint:MEConsumed
MEOP.WeldPoint:MEConsumed
MEOP.DatumPoint:MEConsumed
MEMachining.WeldPoint:MEConsumed
MEMachining.DatumPoint:MEConsumed
DEFAULT
VALUES
MEProcess.WeldPoint:MEWeldPoint
MEProcess.DatumPoint:MEConsumed
MEOP.WeldPoint:MEWeldPoint
MEOP.DatumPoint:MEConsumed
MEMachining.WeldPoint:MEConsumed
MEMachining.DatumPoint:MEConsumed
MEProcess.MEWorkarea:MEWorkArea
MEOP.MEWorkarea:MEWorkArea
MEMachining.MEWorkarea:MEWorkArea
MEProcess.Item:MEConsumed
MEOP.Item:MEConsumed
MEProcess.AppearanceGroup:MEWorkpiece
MEOP.AppearanceGroup:MEWorkpiece
MEProcess.All:MEConsumed

MEOP.All:MEConsumed
MEProcess.MEProcess:Empty
MEProcess.MEOP:Empty
All.All:Empty
SCOPE
User preference.
MEOccTypeConsumed
DESCRIPTION
Specifies valid relation (occurrence) types for consumed relations.
VALID
VALUES
An array of strings, where each string represents a relation (occurrence) type.
DEFAULT
VALUES
MEConsumed
UserConsumed
SCOPE
Site preference.
MSE_ICS_default_type
DESCRIPTION
Indicates the default occurrence type when adding resources to processes or
operations. In the Classification Search Dialog, on selection of a classified item, the
system tries to identify the appropriate occurrence type using the source and target
types and referring to the MEAssignCustomizedOccurrenceType preference. If,
for any reason (for example, multiple items selected), the system fails to resolve the
occurrence type to use, it refers to this preference to set the occurrence type.
VALID
VALUES
Accepts a single string as value. The string must be a valid PSEoccurrence type,
such as MEResource, METool, MEConsumed, or MEOther.
DEFAULT
VALUES
None.
SCOPE
Site preference.
MRMPropagationRevisionRule
DESCRIPTION
Determines the revision rule used during the propagation of attributes. For example,
when the user saves a resource assembly and there is a propagation start point
(PSP) defined in the assembly, the system propagates the attribute values to the

assembly level. The specified revision rule configures the component revisions that
are used during this propagation.
VALID
VALUES
Accepts a single string as value. The string must be a valid revision rule defined in
the database, such as Latest Working or Latest by Alpha Rev Order.
DEFAULT
VALUES
Latest Working
SCOPE
Site preference.
IPADefaultEmailMessage
DESCRIPTION
Specifies the customized e-mail content sent, if users choose to have the system send
e-mail notification after completion of an in-process assembly (IPA).
For more information about how users request e-mail notification, see the
Manufacturing Process Planner Guide.
VALID
VALUES
Accepts a single string of text. The text must include {0}, which is replaced with
the actual process name. For example:
IPA generation/update for process {0} completed.
DEFAULT
VALUES
IPA generation/update for process {0} completed
SCOPE
All.
MPP_DefaultCandidateSearchCriteria
DESCRIPTION
Specifies a default list of properties used to determine candidates containing broken
links that need to be repaired. Candidates are those for which the values of the
specified properties match the values of the broken link’s properties.
For more information about reconciling broken links, see the Manufacturing Process
Planner Guide.
VALID
VALUES
logical.property
logical Specifies whether the match is mandatory or optional, meaning
that at least one of the optional property values must match.
Valid values are Mandatory or Optional.

property Specifies any BOM line property.

DEFAULT
VALUES
Mandatory.bl_item_item_id
SCOPE
Site preference.
MPP_BrokenLinkSearchCriteriaList
DESCRIPTION
Specifies a list of preferences that define candidate search criteria.
VALID
VALUES
Accepts one or more strings as values, each string must be a valid preference name.
DEFAULT
VALUES
MPP_DefaultCandidateSearchCriteria
SCOPE
Site preference.
NX_supported_operation_types
DESCRIPTION
Determines which defined operation types are supported by the NX CAM Integration.
Manufacturing engineers use the Part Planner application to outline the fabrication
process plans necessary to manufacture components. The individual process
planning operations are part of the fabrication process of a component. By default,
the Teamcenter’s manufacturing process management – NX CAM Integration uses
the MENCMachining operation type to support the NX CAM integration. Use this
preference to define additional operation types to be supported by the integration.
VALID
VALUES
operation type.
DEFAULT
VALUES
MENCMachining
SCOPE
Site preference.
TC_NX_FileNewPAXFiles_NX<version>
DESCRIPTION
Specifies the item IDs of the PAX files pointing to different NX versions of CAM
templates. This preference must be suffixed by the version number of the NX

installation from which you are importing the templates. For example, if you import
templates from NX 7.5, name this preference TC_NX_FileNewPAXFiles_NX75.
For more information, see the Getting Started with Manufacturing.
VALID
VALUES
Accepts one or more Teamcenter item IDs. Each item comprises a text dataset
containing an imported PAX file.
DEFAULT
VALUES
None.
SCOPE
All.
NOTES
By default, this preference is not found in the database. You must enter it manually.
ReportXMLGenerationRules
DESCRIPTION
Defines the specific components of a BOM to be included or excluded in an XML
report.
VALID
VALUES
The preference syntax contains the following four fields. The primary, secondary,
and relation fields accept an asterisk (*) as a wildcard.
primary: secondary: relation: action
These fields must be set in the following format:
class.name/type.name : class.name/type.name : relation.name/attribute.name :
Ignore/PublishCurrent/PublishChildren/PublishBOM
Latter fields are subservient to former fields, allowing specific primary rules to
override general rules set using wildcards.
The relation.name/attribute.name specification must be one of the following:
• Teamcenter relation type: either a wildcard or a Teamcenter relation type name.
• BOM structure occurrence type: either a wildcard, null entry (for no occurrence
type), or the occurrence type name.
• Folder content: specified with the string contents.
The action setting must be one of the following:

• Ignore: does not publish the specified component.
• PublishCurrent: publishes only the current BOM line or attachment.
• PublishChildren: publishes only the current BOM line or attachment and

its respective children.

• PublishBOM: publishes the entire BOM structure defined by the default

revision rule, with the current component as the top line.
The following examples illustrate valid settings for this preference:
• Publish the entire BOM structure:

*:*:OccType.*:PublishChildren:
• Publish the entire, current, BOM structure, except for any BOM lines containing
the MEConsumed and MEResource occurrence types (The specific rules of the
first two lines override the general rule of the third line.):
*:*:OccType.MEConsumed:PublishCurrent
*:*:OccType.MEResource:PublishCurrent
*:*:OccType.*:PublishChildren
• Publish the entire attachment structure:

*:*:Relation.*:PublishChildren
• Publish the entire attachment structure, except any attachment with a

IMAN_METarget orIMAN_MEWorkArea relation. In the first case, publish
the entire BOM structure with the defined attachment as the top line of the
structure. In the second case, publish only the current attachment without
its children. (The specific rules of the first two lines override the general rule
of the third line):
*:*:Relation.IMAN_METarget:PublishBOM
*:*:Relation.IMAN_MEWorkArea:PublishCurrent
• Publish the entire attachment structure, and ignore the

TC_NX_nonps_occurrence relation.
*:*:Relation.TC_NX_nonps_occurrence:Ignore
Note
Using this avoids the problem where the PS - BOM
Structure report fails to expand subassemblies. Add the
*:*:Relation.TC_NX_nonps_occurrence:Ignore rule before the
*:*:Relation.*:PublishChildren rule.
DEFAULT
VALUES
*:*:Relation.TC_based_on:Ignore
*:*:Relation.IMAN_RES_checkout:Ignore
*:*:OccType.MEConsumed:PublishCurrent
*:*:OccType.MEResource:PublishCurrent
*:*:OccType.*:PublishChildren
*:*:Relation.IMAN_METarget:PublishChildren
*:*:Relation.IMAN_MEWorkArea:PublishChildren
SCOPE
Site preference.

2D_Viewer_default_load_relation
DESCRIPTION
Defines the relation type to be used to locate the default 2D dataset to be loaded in
the 2D Viewer tab if multiple 2D datasets exist.
VALID
VALUES
Relation type names, not display names.
DEFAULT
VALUES
None.
SCOPE
All.
NOTES
If this preference is not set, the 2D dataset loaded by default is the first 2D dataset
in the attachment list associated with the selected BOM line. If multiple 2D datasets
have this relationship, then the first 2D dataset returned is loaded by default.
MELineLinkedIconsProperty
DESCRIPTION
Specifies whether the manufacturing applications display a symbol beside a linked
structure line in a product (when linked as MEConsumed) or for a linked line in
a work area (for all occurrence types).
VALID
VALUES
No value.
The linked symbols are not displayed.
fnd0bl_assigned_as
The linked symbols are displayed in a reference pane (product or work area),
indicating that a product component or work area object is linked (for example,
consumed or used) in a process pane.
Note
Assigning a value to this preference slows the product/process structure
loading.
DEFAULT
VALUES
None.
SCOPE
All.
NOTES
This preference replaces the Show_ME_line_linked_icons preference for
Teamcenter 8.3 and later. When upgrading to one of these versions, you must
migrate the Show_ME_line_linked_icons preference as follows:

If Show_ME_line_linked_icons was set to true, set

MELineLinkedIconsProperty to fnd0bl_assigned_as.
If Show_ME_line_linked_icons was set to false, leave

MELineLinkedIconsProperty with no value assigned.
GDEOcc_display_instance_num_for_types
DESCRIPTION
Determines which GDE types an instance number on the GDEOccurrence. (Some,
but not all, GDEOccurrence objects related to interfaces require the display of
the instance numbers.) The GDE types specified in this preference will display in
a structure with an instance number included with the GDEOccurrence title
and name.
For more information regarding the use of this preference with the wiring harness
integration, see Wiring Harness Design Tools Integration Guide.
VALID
VALUES
Accepts multiple strings as values. Each value must be a valid Teamcenter GDE
type.
KBL (KabelBaumListe – wire harness description list) is a standard for wiring
models that enhances the STEP AP212 model. The KBL object model provides
high-level components that represent wires, harnesses, and parts in a vehicle that
hosts the harness. This model is a subset of AP212 model and models represent wire
harness data in a similar way. If KBL functionality has been installed, the following
KBL type names must be defined.
HRN_Core
HRN_Cavity
HRN_Slot
DEFAULT
VALUES
Interfaces
SCOPE
All.
FindCheckedOutColumnsShownPref
DESCRIPTION
Defines the columns displayed in the Find Checked Out Objects dialog box.
VALID
VALUES
Accepts multiple strings as values; each string must be a valid column name.
DEFAULT
VALUES
object_string
object_type

checked_out_change_id
checked_out_date
SCOPE
All.
FindCheckedOutColumnsShownWidthPref
DESCRIPTION
Defines the width of the columns displayed in the dialog of the Find Checked Out
Objects command, as defined by the FindCheckedOutColumnsShownPref
preference.
VALID
VALUES
Accepts positive integers. The number of values should be the same as the number
of values in the FindCheckedOutColumnsShownPref preference.
DEFAULT
VALUES
22
18
22
18
SCOPE
All.
TC_show_checkout_objects_on_exit
DESCRIPTION
Specifies if the Find Checked Out Objects dialog box is displayed when exiting
Teamcenter. The dialog box displays all objects checked out to the user in the
database.
VALID
VALUES
True The Find Checked Out Objects dialog box is displayed when
exiting Teamcenter.
False The Find Checked Out Objects dialog box is not displayed
when exiting Teamcenter.
DEFAULT
VALUES
False
SCOPE
All.

MERelationTypeUsedEquipment
DESCRIPTION
Defines the relation (occurrence) types that Teamcenter interprets as tool or
equipment assignments to operations or processes.
VALID
VALUES
DEFAULT
VALUE
METool
MEResource
SCOPE
Site preference.
MERelationTypePartsAssigned
DESCRIPTION
Defines the relation (occurrence) types that Teamcenter interprets as product
assignments to processes.
VALID
VALUES
DEFAULT
VALUE
MEAssign
SCOPE
Site preference.
MERelationTypePartsConsumed
DESCRIPTION
Defines the relation (occurrence) types that Teamcenter interprets as part
consumptions by operations and processes.
VALID
VALUES
DEFAULT
VALUE
MEConsumed
SCOPE
Site preference.

MERelationTypePartsHandled
DESCRIPTION
Defines the relation (occurrence) types that Teamcenter interprets as part handling
during an operation.
VALID
VALUES
DEFAULT
VALUE
MEHandle
SCOPE
Site preference.
MERelationTypePartsAssembled
DESCRIPTION
Defines the relation (occurrence) types that Teamcenter interprets as part assembly
during an operation or process.
VALID
VALUES
DEFAULT
VALUE
MEAssemble
SCOPE
Site preference.
MERelationTypePartsDisassembled
DESCRIPTION
Defines the relation (occurrence) types that Teamcenter interprets as part
disassembly during an operation or process.
VALID
VALUES
DEFAULT
VALUE
MEDisassemble
SCOPE
Site preference.

MERelationTypePartsOtherAssigned
DESCRIPTION
Defines the relation (occurrence) types that Teamcenter interprets as other
product actions; that is, actions other than consumption, handling, assembly, and
disassembly for operations and assignment for processes.
VALID
VALUES
DEFAULT
VALUE
MEOther
METarget
SCOPE
Site preference.
MERelationTypePartsFeature
DESCRIPTION
Defines the relation that indicates a consumed item is a manufacturing feature,
for example, a weld point. You can add custom relations to this preference if you
create them.
VALID
VALUES
DEFAULT
VALUE
MEFeatureAssign
MEWeldPoint
SCOPE
Site preference.
MESecondStructurePosition
DESCRIPTION
Specifies which alignment of the second structure position to use, either to the right
or on the bottom.
VALID
VALUES
right Displays the second structure on the right.
bottom Displays the second structure on the bottom.
DEFAULT
VALUES
right
SCOPE
All.

MEDataPanelPosition
DESCRIPTION
Specifies where to open the data pane of a structure, either to the right of the
structure or below the structure.
VALID
VALUES
right Displays the data pane to the right of the structure.
bottom Displays the data pane below the structure.
DEFAULT
VALUES
bottom
SCOPE
All.
MEExpandFirstLevelOnLoad
DESCRIPTION
Specifies whether the root node of a structure (product, process or plant) is expanded
to the first level when it is opened in Manufacturing Process Planner.
VALID
VALUES
true The root node is expanded when opened in Manufacturing
Process Planner.
false The root node is not expanded when opened in Manufacturing
Process Planner.
DEFAULT
VALUES
true
SCOPE
Site preference.
NOTES
You can also set this preference by selecting the Expand First Level On Load check
box in the preferences Options pane.
MEExpandToSelection
DESCRIPTION
Specifies the behavior of the selection synchronization in manufacturing
applications. Depending on the value of this preference, when using commands such
as Find in other structure, Teamcenter expands the other hierarchy and highlights
the selection.
VALID
VALUES
true The synchronizing view partially expands to the selected line
and highlights it.

false The synchronizing view highlights the selected line only if it is

currently expanded. If a hierarchy was previously expanded
and then collapsed, Teamcenter considers it collapsed. If the
structure is collapsed, nothing is highlighted.
DEFAULT
VALUES
false
SCOPE
Site preference.
NOTES
You can also set this preference by selecting the Expand to Selection check box in
the preferences Options pane.
MEBlankDisplayTypes
DESCRIPTION
Stores commonly used types (item, plant, and occurrence) that you want to
display or blank using the Display by Type or Blank by Type commands in
Manufacturing Process Planner, Part Planner, or Plant Designer. The values
you list in this preference appear in the list of available types in the menu
command. You can also set this preference in the rich client interface by choosing
Edit→Options→Manufacturing and clicking the Graphics tab.
For more information, see the Manufacturing Process Planner Guide.
VALID
VALUES
Accepts a list of string values. Each entry in the list must be of the following format:
structure-type:type-name
For example:
Product:Item
Product:WeldPoint
Plant:MEWorkArea
Occurrence:MEConsumed
DEFAULT
VALUES
Product:Item, Product:Part,
Product:WeldPoint, Plant:MEWorkarea,
Plant:MEPlant, Plant:MESite,
Plant:MELine, Occurrence:MEWeldPoint,
Occurrence:MEConsumed, Occurrence:MEOther,
Product:ManufacturerPart, Product:CommercialPart,
Product:ArcWeld, Product:DatumPoint,
Product:PSConnection, Plant:MEDepartment,
Plant:MEStation, Plant:MEProductLocation,
Occurrence:MEAssemble, Occurrence:MEAssign,
Occurrence:MEFeatureAssign, Occurrence:MEHandle,
Occurrence:MEMachineTool, Occurrence:MEResource,

Occurrence:METool, Occurrence:MEWorkArea,
Occurrence:MEWorkPiece
SCOPE
User preference.
MSE_load_related_product_process_plant
DESCRIPTION
Automatically loads related structures (product, plant or process) when a product,
plant or process is opened in Manufacturing Process Planner.
VALID
VALUES
true Related structures are automatically loaded when opening a
structure in Manufacturing Process Planner.
false Related structures are not loaded when opening a structure in
Manufacturing Process Planner.
DEFAULT
VALUES
true
SCOPE
Site preference.
NOTES
You can also set this preference by selecting the Load Related Structures for
Plant/Process/Product check box in the preferences Options pane.
MEHideChangesIconsForAttributes
DESCRIPTION
Controls the display of the incremental change and the in-context edit symbols
on the BOM structure. By default, symbols appear for all attribute changes in a
structure. Adding an attribute to this list eliminates the display of the change
symbols for this attribute. The changes are still recorded (either in the incremental
change or the context) but the symbols are not displayed.
VALID
VALUES
Valid property names for structure data overrides, for example, bl_sequence_no.
DEFAULT
VALUES
MEUILocation
SCOPE
Site preference.

MECopyIdInContextToAssignedLine
DESCRIPTION
Determines if the in-context ID is copied to the assigned line during an assignment
operation. When this preference is set to True, you do not have to expand a target
structure before performing an accountability check or when using the Find in Other
Panel menu command.
For more information about performing an accountability check, see the
For more information about using the Find in Other Panel menu command, see the
VALID
VALUES
True The in-context ID is copied to the assigned line during
an assignment operation. If no in-context ID is present,
Teamcenter creates one and then copies it.
False The in-context ID is not copied (even if one is present) to the
assigned line during an assignment operation.
DEFAULT
VALUES
False
SCOPE
Site preference.
MECopyIdInContextLowerLevels
DESCRIPTION
Determines if the in-context ID is copied to the assigned line for the subprocesses
and suboperations during an assignment operation.
See also the MECopyIdInContextToAssignedLine preference.
VALID
VALUES
True The in-context ID is copied only for the items that are assigned
to the subprocesses and suboperations during an assignment
operation. The in-context ID of the subprocess or suboperation
is not copied.
False The in-context ID is not copied to the assigned line for
the subprocesses and suboperations during an assignment
operation.
DEFAULT
VALUES
False
SCOPE
Site preference.

MEMFGDisplayName
DESCRIPTION
Defines the customized display name in the tree structure for weld points, arc welds,
and datum points.
For more information about creating weld points, see the Manufacturing Process
Planner Guide.
VALID
VALUES
Accepts the five following Teamcenter properties.
bl_item_item_id
bl_item_object_name
bl_rev_object_name
bl_occurrence_name
You can use multiple properties, for example:
bl_item_item_id
bl_item_object_name
The weld point display name is then 000171;WP1
DEFAULT
VALUES
bl_occurrence_name
SCOPE
Site preference.
MRMItemTypes
DESCRIPTION
Specifies what item type is selected as default based on the currently selected class
in the New Resource dialog box in the Resource Manager application. This item
type is used for the specified class and all its child classes. You can overwrite the
item type in child classes.
For more information about creating new resources, see the Resource Manager Guide.
VALID
VALUES
Accepts one or more pairs of strings as values. In each string pair, the first value
must be a valid Classification class ID, and the second value must be a valid
business object (type).
DEFAULT
VALUES
MRM
Mfg0MEResource
MACHINES
Mfg0MEMachine
TOOLS
Mfg0MENCTool

SCOPE
All.
MEConsiderFlowsOnReSequence
DESCRIPTION
Specifies the default state of the Consider flows check box in the Re-sequence
dialog box in Manufacturing Process Planner and Part Planner. After the first time
you open the dialog box, the check box state is stored in a cookie.
For more information, see the Manufacturing Process Planner Guide or the Part
Planner Guide.
VALID
VALUES
true The Consider flows check box is selected.
false The Consider flows check box is cleared.
DEFAULT
VALUES
true
SCOPE
Site preference.
Cloning preferences
You can create a new process, product, or plant structure from a template, if your
system includes templates for these structures. Cloning rules may be defined that
determine the actions taken when you create a new structure from a template. By
applying the relevant cloning rules when you create the structure, Teamcenter maps
occurrences in the template to absolute occurrences in the reference structure.
For more information about using templates to clone structures, see the
Product.Template.Cloning
DESCRIPTION
Defines the action rules used in creating a product structure from a product
template. Product templates are available from Manufacturing Process Planner,
Part Planner, and Multi-Structure Manager.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter naming
rule. Naming rules are created in Business Modeler IDE.
DEFAULT
VALUES
*:*:Attribute.items_tag:Clone
*:*:Attribute.structure_revisions:Clone

*:*:Attribute.bom_view:Clone
*:*:Attribute.parent_item:Clone
*:*:Attribute.variant_expression_block:Clone
*:*:OccType.Null:Clone
*:*:OccType.*:Reference
*:*:Relation.IMAN_Rendering:Clone
*:*:Relation.IMAN_specification:Clone
*:*:Relation.IMAN_3D_snap_shot:Clone
*:*:Relation.VisTopLevelRef:Clone
class.Folder:*:Attribute.contents:Reference
SCOPE
Site preference.
Product.Template
DESCRIPTION
Defines the product templates used in creating a product structure. Each product
template contains the action rules used in creating a product structure from the
product template. Product templates are available from Manufacturing Process
Planner, Part Planner, and Multi-Structure Manager.
Note
Definition of individual templates must be created first via
Product.Template.template name preferences. For example, the
Product.Template.Cloning preference. These preferences define the action
rules used in creating the product structure from the product template.
VALID
VALUES
Accepts multiple strings as values. Each string must be the template name suffix of
each Product.Template.template name preference name.
DEFAULT
VALUES
Cloning
SCOPE
All.
Plant.Template.Cloning
DESCRIPTION
Defines the action rules used in creating a plant from a plant template. Plant
templates are available from Manufacturing Process Planner, Part Planner, and
Plant Designer.
VALID
VALUES


DEFAULT
VALUES
SCOPE
All.
Plant.Template
DESCRIPTION
Defines the plant templates used in creating a plant. Each plant template
contains the action rules used in creating a plant from the plant template. Plant
templates are available from Manufacturing Process Planner, Part Planner, and
Note
Definition of individual templates must be created first via
Plant.Template.template name preferences. For example, the
Plant.Template.Cloning preference. These preferences define the action
rules used in creating the product structure from the product template.
VALID
VALUES
each Plant.Template.template name preference name.
DEFAULT
VALUES
Cloning
SCOPE
All.
Process.Template.Mapping_Consumes
DESCRIPTION
Defines the action rules used in creating a process structure from a process template
by mapping the MEConsumed and MEWorkArea product elements. When
creating a new process structure, the mapped product elements must share the same
absolute occurrence or ID of absolute occurrence with the product template.

VALID
VALUES
DEFAULT
VALUES
*:*:OccType.MEConsumed:Map.Reference
*:*:OccType.MEWorkArea:Map.Reference
*:class.MEActivity:Relation.IMAN_MEFolder:Clone
class.MEActivity:*:Attribute.contents:Clone
MapLD.Ignore
MapAOID.Ignore
MapAOID.Reference
SCOPE
All.
Process.Template.Referencing_Consumes
DESCRIPTION
Defines the action rules used in creating a process structure from a process template
by referencing MEConsumed product elements. When creating a new process
structure, the referenced product elements need to share the same absolute
occurrence or ID of absolute occurrence with the product template.
VALID
VALUES
DEFAULT
VALUES
*:*:OccType.MEConsumed:Reference

SCOPE
All.
Process.Template.Ignoring_Consumes
DESCRIPTION
Defines the action rules used in creating a process structure from a process template,
ignoring any MEConsumed product elements. Typically, when creating a new
process structure, the mapped product elements need to share the same absolute
occurrence or ID of absolute occurrence with the product template.
VALID
VALUES
DEFAULT
VALUES
*:*:OccType.MEConsumed:Ignore
SCOPE
All.
Process.Template
DESCRIPTION
Defines the process templates used in creating a process structure. Each process
template contains the action rules used in creating a process structure from the
process template.

Note
Definition of individual templates must be created first
using the Process.Template.Mapping_Consumes,
Process.Template.Referencing_Consumes, and
Process.Template.Ignoring_Consumes preferences.
VALID
VALUES
each Process.Template.template name preference name.
DEFAULT
VALUES
Mapping_Consumes
Referencing_Consumes
Ignoring_Consumes
SCOPE
All.
Clone_Pending_Release_Status
DESCRIPTION
Specifies the release status type that will be assigned to any newly created
incremental change revisions during cloning.
VALID
VALUES
Accepts a string representing a valid release status type.
DEFAULT
VALUES
Pending
SCOPE
Site preference.
Clone_Secured_Release_Status
DESCRIPTION
Lists all release status types that should be considered secured (no longer modifiable)
when cloning incremental change revisions. Any statuses listed are cloned as ICRev
with a Clone_Pending_Release_Status value.
For more information, see Getting Started with Manufacturing.
VALID
VALUES
Accepts one or more strings representing valid release status types.
DEFAULT
VALUES
None.

SCOPE
Site preference.
PERT chart preferences

The PERT chart is a graphical representation of process flow. You can edit and
manipulate the process flow in this graphical environment.
For more information about using the PERT chart, see the Manufacturing Process
Planner Guide.
PertChart.<object_type>.GColor
DESCRIPTION
Defines the background color of the PERT nodes by defining the R, G, and B values
of the background boxes in the PERT chart. Object_type refers to an operation,
activity, or plant business object (type), such as MEOP, MEProcess, MEActivity,
or MEPrStation.
VALID
VALUES
Any valid RGB values.
DEFAULT
VALUES
You can define a general entry in the preference file that defines the background
color for nodes per PERT chart type. Those entries are:
• PertChart.NodeDefault.GColor=220,120,0
Defines the background color for nodes in Process/Station Flow PERT chart that
do not have an explicit background color definition.
• PertChart.ActivityDefault.GColor=0,120,120
Defines the background color for nodes in the Activity PERT chart that do not
have an explicit background color definition.
If the PERT module cannot find any background color definition for a specific node, it
uses gray (128, 128, 128).
SCOPE
User, group, or site preference.
PertChart.<object_type>.Text
DESCRIPTION
Defines the text to be displayed in the PERT node by specifying which node fields
appear. Object_type refers to an operation, activity, or plant business object (type),
such as MEOP, MEProcess, MEActivity, or MEPrStation.
VALID
VALUES
<free-text>[property-name]<free-text>... where:

<free-text> Any text except square parentheses [ ].

Any property name. Must be wrapped
[property-name] by square parentheses, for example:
[object_name].
You can select the fields from the activity attributes.

For example:
PertChart.MEOP.Text=Revision: [bl_bomview_rev] Class: [bl_line_object_class]
Causes the PERT chart to display the operation node text as follows:
Revision: 00000000 Class: MEOP Revision
Causes the PERT chart to display the activity node text as follows:
PertChart.MEActivity.Text=Name: [object_name] Desc: [object_desc]
Name: act1 Desc: act1 description

You can define default entries for any types that are not explicitly defined, for
example:
Used for all types derived from
PertChart.NodeDefault.Text= operation/process and work area class.
PertChart.ActivityDefault.Text= Used for all types derived from activity
class.
Special cases — The following are special cases regarding the formula definition:
• If the property name does not exist for the specified object, an empty value is
displayed in the node text. No error message is displayed.
If the following formula is defined in the preference file for operations:
PertChart.MEOP.Text=Name: [object_name] NAN: [bbb]
The following text is displayed in the node—assuming the operation is named

op1:
Name: op1 NAN:
• In the case of incorrect formula format, the application tries to display the
correct section of the formula. No error message is displayed.
DEFAULT
VALUES
None.
SCOPE
PertChart.AutoSizeMode
DESCRIPTION
Enables or disables auto-size in the PERT chart. When auto-size is off, the size of
the all newly created PERT nodes is uniform. When auto-size is on, the size of the

newly created PERT nodes is automatically fitted to the displayed text, including
allowing for multiple lines.
VALID
VALUES
yes Enables auto-size.
no Disables auto-size.
DEFAULT
VALUES
yes
SCOPE
PertChart.BoxAutoSizeMaxWidth
DESCRIPTION
If PertChart.AutoSizeMode is on, configures the maximal width to be used when
new PERT nodes are created.
VALID
VALUES
A positive integer.
If the PERT node text is larger than 250 pixels, the application splits the text into
multiple lines as needed.
DEFAULT
VALUES
None.
SCOPE
PertChart.BoxDefaultWidth
DESCRIPTION
If PertChart.AutoSizeMode is off, configures the default width to be used when
new PERT nodes are created. The value is common for all PERT chart types; for
example, once it is defined in the Process PERT chart, the Activity Flow chart and
Station Flow chart use this value to define the width of newly created PERT nodes.
VALID
VALUES
A positive integer indicating the number of pixels.
DEFAULT
VALUES
None.
If no values are entered, the node is 110 pixels wide.
SCOPE

PertChart.BoxDefaultHeight
DESCRIPTION
If PertChart.AutoSizeMode is off, configures the default height to be used when
new PERT nodes are created. The value is common for all PERT chart types; for
example, once it is defined in the Process PERT chart, the Activity Flow chart and
Station Flow chart use this value to define the height of newly created PERT nodes.
VALID
VALUES
A positive integer indicating the number of pixels.
DEFAULT
VALUES
None.
If no value is entered, the node is 20 pixels high.
SCOPE
PertChartCreationLayout
DESCRIPTION
Defines where newly created nodes are placed in the PERT chart. If the value is
Horizontal, all newly created nodes are put at the top right corner; otherwise,
they are placed at the bottom left corner.
For more information about using the PERT chart, see the Manufacturing Process
Planner Guide.
VALID
VALUES
Horizontal All newly created nodes are placed at the top right corner of
the PERT chart.
Vertical All newly created nodes are placed at the bottom left corner of
the PERT chart.
DEFAULT
VALUES
Vertical
SCOPE
All.
Accountability check preferences

Using the accountability check feature, you can compare two structures to ensure
all lines in the source structure are consumed in the target structure. For example,
you can compare the product structure and the process structure to ensure that all
occurrences of product components and features are used in the process structure
as consumed items. You can compare the entire assembly or only a subassembly
to the selected process.

For more information about the accountability check feature, see the Manufacturing
Process Planner Guide.
DefaultAccountabilityCheckProperties
DESCRIPTION
Determines which properties the system checks by default when performing an
accountability check.
An accountability check compares a bill of materials (BOM) with a bill of process
(BOP) to ensure all lines in the source BOM are consumed in the target BOP. This
allows you to ensure that all occurrences of product components and features are
used in the process structure as consumed items. You can compare the entire
assembly or only a subassembly to the selected process.
For more information about using accountability checks, see the Manufacturing
If the Compare additional properties option in the Accountability Checkbox dialog
box is not selected, the values defined in this preference are the only properties upon
which the accountability check is performed.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid item property.
DEFAULT
VALUES
bl_item_item_id
SCOPE
Site preference.
AdditionalAccountabilityCheckProperties
DESCRIPTION
Determines the additional properties the system checks when performing an
accountability check.
The system checks this preference when the Compare additional properties option
in the Accountability Checkbox dialog box is selected. Any properties defined by
this preference are included in the accountability check.

VALID
VALUES
Accepts multiple strings as values. Each string must be a valid property of the
selected BOM line.
DEFAULT
VALUES
bl_rev_object_name
bl_rev_object_type
bl_plmxml_abs_xform
bl_quantity
bl_sequence_no
bl_abs_occ_id
bl_jt_refsetname
SCOPE
By default, this is a site preference. If any changes are made to the default values,
the changes are stored as user preference values.
AccountabilityCheckReportStylesheetName
DESCRIPTION
Determines which XSL style sheet of the report definition should be used to generate
the accountability check report.
A user can add more than one XSL style sheet to the report definition. If this
preference is defined and a style sheet with this name is found, the accountability
check report is generated by using the style sheet that is found. Otherwise, the
default style sheet is used.
VALID
VALUES
Accepts strings as value. Each string must be a valid style sheet name from the
accountability check report definition.
DEFAULT
VALUES
In case the preference is not found or the style sheet defined in the preference is not
found, acc_chk_rpt_excel.xsl is taken.
SCOPE
User preference.

MEAccountabilityCheckSourceStructureExpansionFilterRules
DESCRIPTION
Provides a list of closure rule names to be used for source structure traversal for
the accountability check.
For more information about filtering the structures for an accountability check, see
the Manufacturing Process Planner Guide.
VALID
VALUES
Accepts a list of closure rule names that exist in the database to be used for traversal
of the source structure.
DEFAULT
VALUES
AccountabilityLeavesOnly
AccountabilityAll
AccountabilityLinkedAssmOrLeaves
AccountabilityProcessLeavesOnly
AccountabilityProcessAll
SCOPE
Site preference.
MEAccountabilityCheckTargetStructureExpansionFilterRules
DESCRIPTION
Provides a list of closure rule names to be used for the target structure traversal for
the accountability check.
VALID
VALUES
Accepts a list of closure rule names that exist in the database to be used for traversal
of the target structure.
DEFAULT
VALUES
AccountabilityAll
AccountabilityLeavesOnly
AccountabilityLinkedAssmOrLeaves
AccountabilityProcessConsumption
AccountabilityProcessAssignments
AccountabilityProcessAllNoAssign
AccountabilityProcessAll
SCOPE
Site preference.

MEAccountabilityCheckEnableFilteringRules
DESCRIPTION
Determines whether the Expand Below by Filter Rule menu command for the
filtering rule verification is enabled.
VALID
VALUES
true The Expand Below by Filter Rule menu command is available.
false The Expand Below by Filter Rule menu command is hidden.
DEFAULT
VALUES
false
SCOPE
Site preference.
MEAccountabilityCheckEnableNetEffectivity
DESCRIPTION
Specifies whether the net effectivities are compared when the accountability check
tests for a partial match.
VALID
VALUES
true Net effectivities are checked.
false Net effectivities are not checked.
DEFAULT
VALUES
false
SCOPE
Site preference.
MEResultViewSourceColumnsShownPref
DESCRIPTION
Defines the columns to display in the Accountability Check view source table.
For more information about working with this view, see the Manufacturing Process
Planner Guide.
VALID
VALUES
Accepts valid Teamcenter internal property names in the order the columns should
appear in the table.
DEFAULT
VALUES
bl_indented_title
bl_item_object_type
bl_item_object_desc

SCOPE
Site preference.
MEResultViewSourceColumnsShownWidthPref
DESCRIPTION
Defines the width of the columns displayed in the Accountability Check view source
table as defined by the MEResultViewSourceColumnsShownPref preference.
Planner Guide.
VALID
VALUES
Accepts an integer value representing the width in pixels of the column.
DEFAULT
VALUES
50
50
50
SCOPE
Site preference.
NOTES
The values of this preference are set automatically by Teamcenter through
interaction with the user interface. You do not need to change these manually.
MEResultViewTargetColumnsShownPref
DESCRIPTION
Defines the columns to display in the Accountability Check view target table.
Planner Guide.
VALID
VALUES
Accepts valid Teamcenter internal property names in the order the columns should
appear in the table.
DEFAULT
VALUES
bl_indented_title
bl_item_object_type
bl_item_object_desc
SCOPE
Site preference.

MEResultViewTargetColumnsShownWidthPref
DESCRIPTION
Defines the width of the columns displayed in the Accountability Check view target
table as defined by the MEResultViewTargetColumnsShownPref preference.
Planner Guide.
VALID
VALUES
Accepts an integer value representing the width in pixels of the column.
DEFAULT
VALUES
50
50
50
SCOPE
Site preference.
NOTES
The values of this preference are set automatically by Teamcenter through
interaction with the user interface. You do not need to change these manually.
Time management preferences

You can store individual times for each activity, operation, or process in a process
structure. These times are managed in the Times pane. This pane provides
information specific to the process or operation so that its appearance varies
depending on which of these you have selected.
For more information about managing time, see the Manufacturing Process Planner
Guide.
MEAvailableTimeUnits
DESCRIPTION
Defines the list of customized (additional) available time units. Each value contains
a unique unit ID in English and a multiplier to convert from this unit to seconds
(default unit).
VALID
VALUES
Accepts one or more strings as values, each string must be formatted as follows:
unitID:multiplierToSeconds
For example:
myTimeUnitID:112.25
DEFAULT
VALUES
None.

SCOPE
Site preference.
RESTRICTIONS
The time unit ID must be unique and in English.
MECurrentTimeUnit
DESCRIPTION
Defines the ID of the time unit (as defined in the MEAvailableTimeUnits
preference) in which all new time data is displayed. Set this value using the Time
pane in the ME section of the preferences interface for the change to take effect
without restarting the application.
VALID
VALUES
Accepts a string as value that must be one of the out of the box time unit IDs listed
below or one of the IDs from the MEAvailableTimeUnits preference. This value
must be in English.
second
minute
10th_min
100th_min
1000th_min
hour
day
TMU
MOD
FAC
DEFAULT
VALUES
second
SCOPE
User preference.
METimeTabFilteredComponents
DESCRIPTION
Defines which objects are filtered out in the Activities section on the Time pane.
VALID
VALUES
Accepts any general object type, such as Form or Dataset, or a specific type such as
AllocationMap Master. You cannot filter out an activity. If an activity is listed in
this preference, it is ignored.
DEFAULT
VALUES
Form
Dataset
Folder

SCOPE
All.
MEOperationActivitiesFilteredComponents
DESCRIPTION
Defines which objects are filtered out in the Operation Activities pane.
VALID
VALUES
Accepts any general object type, such as Form or Dataset, or a specific type such as
AllocationMap Master. You cannot filter out an activity. If an activity is listed in
this preference, it is ignored.
DEFAULT
VALUES
Form
Dataset
Folder
SCOPE
All.
MEActivityTypeColors
DESCRIPTION
Specifies the colors associated with the types of activities, as defined in the
time_system_category property of the MEActivity class. A color is represented
by a string composed of the red, green, and blue values of the color, separated by a
decimal point.
VALID
VALUES
Accepts one or more strings as a value. Each string must have the following format:
type;color
type is a value of the time_system_category property and color is the red, green,
and blue values of the corresponding color, separated by decimal point.
DEFAULT
VALUES
VA;0.128.0
NVA;255.0.0
NVABR;255.165.0
SCOPE
RESTRICTIONS
The values of this preference should be set by the site manager.

MEDefaultActivityType
DESCRIPTION
Specifies the default type of a new activity created in the Activity section in the
operation Times pane in Manufacturing Process Planner.
VALID
VALUES
Accepts a string as a value. The value must be MEActivity or the name of a derived
class.
DEFAULT
VALUES
MEActivity
SCOPE
Site preference.
METimesActivityShownColumns
DESCRIPTION
Lists the column names of the attributes that are shown in the Activity table in the
operation Times pane in Manufacturing Process Planner.
VALID
VALUES
Accepts one or more strings as values; each string must be a valid property of
CfgActivityLine.
DEFAULT
VALUES
me_cl_display_string
al_activity_time_system_code
al_activity_time_system_unit_time
al_activity_time_system_frequency
al_activity_work_time
al_activity_time_system_category
al_activity_time_system_description
SCOPE
NOTES
The values should not be modified directly, but by inserting, reordering, and
removing columns in the table.
METimesActivityShownColumnWidths
DESCRIPTION
Lists the widths of columns that appear in the Activity section of the operation
Times pane in Manufacturing Process Planner.

VALID
VALUES
One or more positive integers.
DEFAULT
VALUES
20
10
10
10
10
20
SCOPE
NOTES
You should not modify the values directly. Set these values by resizing columns
in the table.
RESTRICTIONS
The number of entries must match the entries of the
METimesActivityShownColumns preference.
METimeAnalysisReportDefinitionID
DESCRIPTION
Specifies the ID for the Time Analysis report.
VALID
VALUES
Accepts a valid report ID string.
DEFAULT
VALUES
TC_TIME_ANALYSIS_REPORT
SCOPE
Site preference.
NOTES
You can also set this preference in the Time Reports section of the Time pane in the
Manufacturing section of the preferences Options dialog box.
MEAllocatedTimeReportDefinitionID
DESCRIPTION
Specifies the ID for the Allocated Time report.
VALID
VALUES
Accepts a valid report ID string.
DEFAULT
VALUES
TC_ALLOCATED_TIME_REPORT

SCOPE
Site preference.
NOTES
METimeAnalysisReportStylesheet
DESCRIPTION
Specifies the name of the XSL style sheet used for the Time Analysis report.
VALID
VALUES
Accepts a valid style sheet name.
DEFAULT
VALUES
TimeAnalysisReport.xls
SCOPE
Site preference.
NOTES
MEAllocatedTimeReportStylesheet
DESCRIPTION
Specifies the name of the XSL style sheet used for the Allocated Time report.
VALID
VALUES
A file name.
DEFAULT
VALUES
AllocatedTimeReport.xsl
SCOPE
Accepts a valid style sheet name.
NOTES
METimeDataCardPath
DESCRIPTION
Specifies the location of the data card as URI. Use the goto protocol to navigate to
an MTM data card, and the file protocol to navigate to a custom HTMLdata card.
VALID
VALUES
A character string.

DEFAULT
VALUES
goto://MTMDataCard.eng
SCOPE
NOTES
You can also set this preference by typing a path name in the Data Card Location box
on the Time pane in the Manufacturing section of the preferences Options dialog box.
METimeDataCardConversionFactor
DESCRIPTION
Specifies the factor to convert from data card time units to seconds. It is applied to
time values from a data card. The standard MTM data cards hold times in TMU.
For more information about using MTM data cards, see the Manufacturing Process
Planner Guide.
VALID
VALUES
A character string.
DEFAULT
VALUES
goto://MTMDataCard.eng
SCOPE
NOTES
You can also set this preference by typing a path name in the Time Unit Factor box
on the Time pane in the Manufacturing section of the preferences Options dialog box.
METIMEAllocatedTimePopulationMode
DESCRIPTION
Specifies which mode is used in the Populate allocated time command in the Time
pane.
For more information about working with allocated time, see the Manufacturing
VALID
VALUES
0
Estimated time
1
Simulated time
2
Time analysis duration
3
Customized

DEFAULT
VALUES
0
SCOPE
RESTRICTIONS
METIMEPopulateAllocatedTimeUsedSources
DESCRIPTION
Specifies which time sources are used in which order when using the custom
allocated time population mode in the Time pane. The order of sources in this
preference defines the precedence in which they are used.
VALID
VALUES
A list of strings containing the used sources for population of allocated time. The list
can contain any of the following.
0
Allocated time
1
Simulated time
2
Time analysis duration
3
Estimated time
DEFAULT
VALUES
0
1
2
3
SCOPE
RESTRICTIONS

METIMEPopulateAllocatedTimeUpToLevelEnabled
DESCRIPTION
Specifies whether the option to update the allocated time to a certain level (Populate
up to level) is active in the Populate Allocated Time dialog box in the Time pane.
VALID
VALUES
True
The Populate up to level option is available.
False
The Populate up to level option is not available.
DEFAULT
VALUES
False
SCOPE
RESTRICTIONS
METIMEPopulateAllocatedTimeUpToLevel
DESCRIPTION
Specifies the level to which the Populate Allocated Time command should be
executed.
VALID
VALUES
An integer value greater than or equal to 0. Setting this preference to 0 indicates
that all levels are populated.
DEFAULT
VALUES
0
SCOPE
RESTRICTIONS
METIMEPopulateAllocatedTimeZeroValuesEnabled
DESCRIPTION
Specifies whether zero values are populated while executing the Populate Allocated
Time command in the Time pane.

VALID
VALUES
True
Zero values are populated.
False
Zero values are not populated.
DEFAULT
VALUES
False
SCOPE
RESTRICTIONS
Publishing preferences
You can create publishing pages in the embedded viewer and collect them into
portfolios. A typical publishing page is a work instruction document, and a portfolio
may contain all the work instructions needed at a particular assembly station. In
the manufacturing environment, work instructions and product manuals are the
only default types of publishing page provided, although your system may include
other types of publishing pages.
For more information about publishing pages, see the Manufacturing Process
Planner Guide.
AppInterface_TCPublishingTechnicalPortfolio_default_relation
DESCRIPTION
Used for configuring Teamcenter’s manufacturing process management
technical portfolios. Defines the default relation used when a
TCPublishingTechnicalPortfolio dataset is pasted under an intermediate data
capture (IDC) while creating technical portfolios.
VALID
VALUES
DEFAULT
VALUES
IMAN_TCPublishedPortfolio
SCOPE
All.

AppInterface_TCPublishingTechnicalPortfolio_shown_relations
DESCRIPTION
technical portfolios. Defines the relations available when pasting a
TCPublishingTechnicalPortfolio dataset under an intermediate data capture
(IDC) while creating technical portfolios.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid
Teamcenter relation and it must include the value set for the
AppInterface_TCPublishingTechnicalPortfolio_default_relation preference.
DEFAULT
VALUES
SCOPE
All.
IMAN_PublishingPageAssetContext_relation_primary
DESCRIPTION
technical portfolios. Defines which Teamcenter objects can be used with a
IMAN_PublishingPageAssetContext relation.
Note
The default value of this preference should not be changed.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter object.
DEFAULT
VALUES
SCOPE
All.
IMAN_TCPublishedPortfolio_relation_primary
DESCRIPTION
Used for configuring Teamcenter’s manufacturing process management technical
portfolios. Defines which Teamcenter objects are used as primary objects with a
IMAN_TCPublishedPortfolio relation.
VALID
VALUES

DEFAULT
VALUES
TCPublishingTechnicalPortfolio
AppInterface
SCOPE
All.
ItemRevision_TCPublishingPage_default_relation
DESCRIPTION
portfolios. Defines the default relation created when a publishing page is pasted
within an item revision.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter relation.
DEFAULT
VALUES
SCOPE
All.
<TC Publishing Technical Portfolio type>_DefaultChildProperties

DESCRIPTION
portfolios. Determines which properties are children of the indicated technical
portfolio type. Each type requires its own preference. The format for each preference
is:
Technical-Portfolio-type-name_DefaultChildProperties=Teamcenter property
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter property.
DEFAULT
VALUES
IMAN_PortfolioPage
IMAN_PortfolioConfiguredPage
SCOPE
All.

<TC Publishing Page type>_DefaultChildProperties

DESCRIPTION
portfolios. Determines which properties are children of the indicated publishing page
type. Each type requires its own preference. The format for each preference is:
Publishing-Page-type-name_DefaultChildProperties=Teamcenter property
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter property.
DEFAULT
VALUES
IMAN_PublishingPageAssetContext
VisAssetPopulatedByEndobj
SCOPE
All.
TCPublishing_Aliases.IMAN_MEWorkInstruction
DESCRIPTION
portfolios. Defines which alias datasets display when loading alias files for
IMAN_MEWorkInstruction pages. If not configured, all alias files are listed.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter alias
dataset.
DEFAULT
VALUES
Installed Aliases
SCOPE
All.
TCPublishing_Default_Alias_File
DESCRIPTION
portfolios. Defines the default alias file loaded when a new publishing page is viewed.
Warning
The default alias file is automatically loaded by the system. This file is subject
to update in the future. Do not change the default setting. Create your own
alias files using the TechnicalPortfolioRoles preference.

VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter alias
dataset.
DEFAULT
VALUES
Installed Aliases
SCOPE
All.
TCPublishing_Activities_Role
DESCRIPTION
Determines the role of all publishing page datasets attached to activities used in
Manufacturing Process Planner. The role also determines the name displayed on
the publishing page tab. Users use this tab to create published pages containing
manufacturing data.
VALID
VALUES
Accepts a single string as a value. Must be a valid relation type used to define the
role of publishing page datasets.
DEFAULT
VALUES
Note
If this value is changed, a closure rule and transfer mode is required to generate
portfolios. Define the desired transfer mode using the transfer mode defined
by the TechnicalPortfolioTransferMode_IMAN_MEWorkInstruction
preference as a template, creating a new preference pointing to the transfer
node. Define the role using the TechnicalPortfolioRoles preference.
SCOPE
All.
TCPublishing_Aliases.Activities
DESCRIPTION
Determines which alias file dataset names appear when users load alias files for
activity pages. If left undefined, all alias files appear. This preference is used for
Manufacturing Process Planner.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid alias file dataset.
DEFAULT
VALUES
Installed Aliases

SCOPE
All.
IMAN_PortfolioConfiguredPage_relation_primary
DESCRIPTION
IMAN_PortfolioConfiguredPage relation.
Note
VALID
VALUES
DEFAULT
VALUES
SCOPE
All.
IMAN_PortfolioPage_relation_primary
DESCRIPTION
IMAN_PortfolioPage relation.
Note
VALID
VALUES
DEFAULT
VALUES
SCOPE
All.
TechnicalPortfolioRoles
DESCRIPTION
portfolios. Use this preference to define the roles of technical portfolios. You can

create custom alias files, which are tracked by the system on a per-role basis. Alias
files accept a single named reference.
VALID
VALUES
DEFAULT
VALUES
SCOPE
All.
TechnicalPortfolioTransferMode_IMAN_MEWorkInstruction
DESCRIPTION
portfolios. Defines the transfer mode of the specified technical portfolio.
TransferMode objects control the related data exported into a PLM XML document.
VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter TransferMode
object.
DEFAULT
VALUES
ConfiguredDataExportDefault
SCOPE
All.
IMAN_MEWorkInstruction_relation_primary
DESCRIPTION
Defines which Teamcenter objects are used as primary objects with a
IMAN_MEWorkInstruction relation.
VALID
VALUES
DEFAULT
VALUES
ItemRevision
AppearanceGroup
PSOccurrence
SCOPE
All.

VisAssetPopulatedByEndobj_relation_primary
DESCRIPTION
Defines primary objects permitted for VisAssetPopulatedByEndobj relations.
VALID
VALUES
Object type names.
DEFAULT
VALUES
TCPublishingPage
SCOPE
All.
TCPublish_managed_asset_properties
DESCRIPTION
Defines alias path element attributes that are to be stored as asset properties
in publishing page files.
VALID
VALUES
Any string identifier.
DEFAULT
VALUES
createRelation
SCOPE
All.
NOTES
Teamcenter stores as a property of an asset any path element attributes with the
names that are specified in the alias alternate that is used to populate or update
the asset. The property is stored internally in the VTP file, not in the Teamcenter
metadata.
TCPublish_synchronized_asset_relations
DESCRIPTION
Defines names of relation types that link parent publishing page datasets with other
objects, where the links in Teamcenter must match those stored as asset properties
via the createRelation path element attribute in the alias definition. Causes the
relations to be created and removed in Teamcenter to match what is saved in the
dataset.
VALID
VALUES
Relation type names.
DEFAULT
VALUES
VisAssetPopulatedByEndobj

SCOPE
All.
NOTES
Relations not in this list are not removed if an asset is deleted or repopulated.
TCPUBLISH_BATCH_ROLE
DESCRIPTION
Defines a role relation between the publishing page and its owning object.
VALID
VALUES
Accepts any string identifier.
DEFAULT
VALUES
TC_MEProductManual
SCOPE
All.
TCPUBLISH_BATCH_<role>_TEMPLATES
DESCRIPTION
Lists templates that are associated with Teamcenter classes. These templates are
used for the create task.
VALID
VALUES
The IDs of the templates in the database separated by a comma.
DEFAULT
VALUES
None.
SCOPE
All.
TCPUBLISH_BATCH_<role>_PAGE_TEMPLATE_FAVORITES
DESCRIPTION
Stores a list of template favorites for the publish batch process.
VALID
VALUES
The IDs of the templates in the database separated by a comma.
DEFAULT
VALUES
None.
SCOPE
All.

TCPUBLISH_BATCH_<role>_PORTFOLIO_TEMPLATE_FAVORITES
DESCRIPTION
Stores a list of template favorites for the batch updating of portfolios.
VALID
VALUES
The IDs of the portfolio templates in the database separated by a comma.
DEFAULT
VALUES
None.
SCOPE
All.
TCPUBLISH_BATCH_CLASSES
DESCRIPTION
Defines the list of Teamcenter classes to use on the TC Publish Batch Select Types
and Templates wizard page.
VALID
VALUES
Accepts any valid Teamcenter class.
DEFAULT
VALUES
ItemRevision
MEProcessRevision
MEOPRevision
MEActivity
SCOPE
Site preference.
PAD preferences
The Process Assembly Document (PAD) user interface in Manufacturing Process
Planner is a tool to define and document a product-oriented bill of process. The
product-oriented bill of process holds the value-added operations required to
assemble the product. These operations are independent of the plant they will be
executed in. The tool enables assigning of product, resource, illustrations, quality,
and time information to the operations and outputs a sophisticated report.
For more information about the process assembly document feature, see the

MEPSDTableShownColumnWidthsPref
DESCRIPTION
Specifies the column widths for the columns (identified by
MEPSDTableColumnsShownPref) that are used in the MEPSD table section of
the PAD user interface at the MEPAD level.
VALID
VALUES
Positive whole numbers.
DEFAULT
VALUES
36
19
25
25
36
SCOPE
Site preference.
NOTES
When a user modifies the preference, a user-level preference gets generated.
RESTRICTIONS
The value of this preference is to be set by the site manager only.
MEPSDTableColumnsShownPref.SORTING_COLUMN
DESCRIPTION
Specifies the column that is used for sorting table data in the MEPSD table section
of the PAD user interface at the MEPAD level.
VALID
VALUES
Accepts only one string as a valid value.
DEFAULT
VALUES
bl_sequence_no.true
SCOPE
Site preference.
NOTES
When a user modifies the preference, a user level preference gets generated.
RESTRICTIONS

MEPADChildTypesPref
DESCRIPTION
Specifies the default child types to be displayed in the MEPSD table section of the
PAD user interface at the MEPAD level.
VALID
VALUES
Accepts only one string as a valid value.
DEFAULT
VALUES
*:MEPSD
SCOPE
Site preference.
NOTES
RESTRICTIONS
MEPSDTableColumnsShownPref
DESCRIPTION
Specifies the list of column names that will be displayed in the MEPSD table section
of the PAD user interface at the MEPAD level.
VALID
VALUES
The values should be valid column names.
DEFAULT
VALUES
BOMLine.bl_indented_title
BOMLine.bl_sequence_no
BOMLine.bl_rev_object_name
BOMLine.bl_rev_object_desc
BOMLine.bl_variant_condition
SCOPE
Site preference.
NOTES
RESTRICTIONS
Manufacturing search preferences

Use these preferences to configure the advanced manufacturing (cacheless) search
feature provided in Teamcenter’s manufacturing process management. You can

use manufacturing searches to locate objects by proximity and properties in IPAs

(in-process assemblies) and BOP structures.
ME_Proximity_search_result_occ_type
DESCRIPTION
Defines the occurrence type that represents a proximity search result collection in
the process structure.
VALID
VALUES
Accepts a single string as value. The string must be a valid occurrence type.
DEFAULT
VALUE
MEFilteredIPA
SCOPE
Site preference.
ME_Proximity_search_result_occ_group_type
DESCRIPTION
Defines the occurrence group type that represents a proximity search result
collection in the process structure.
VALID
VALUES
Accepts a single string as value. The string must be a valid occurrence group type.
DEFAULT
VALUE
MEProximityResult
SCOPE
Site preference.
ME_Proximity_search_result_root_name
DESCRIPTION
Defines the name of the flat list collection that holds all the proximity search result
groups.
VALID
VALUES
Accepts a single string as value. The string must be a valid occurrence group type.
DEFAULT
VALUE
Proximity_Search_Results
SCOPE
Site preference.

ME_Proximity_FilteredIPA_suffix
DESCRIPTION
Defines the suffix of the filtered IPA names when the occurrence group holds
proximity search result.
VALID
VALUES
Accepts a single string as value.
DEFAULT
VALUE
_fipa
SCOPE
Site preference.
MEAdvancedSearchResultsViewColumnsShownPref
DESCRIPTION
Specifies the list of the columns displayed in the advanced manufacturing search
results pane.
VALID
VALUES
The system name of each column in the order you want them to appear, that is,
value_1, value_2 and so on.
DEFAULT
VALUE
bl_indented_title
bl_item_object_type
bl_item_object_desc
SCOPE
Site preference.
MEAdvancedSearchResultsViewColumnsShownWidthPref
DESCRIPTION
Specifies the width of the columns displayed in the advanced manufacturing
search results pane. This setting affects each column defined in the
MEAdvancedSearchResultsViewColumnsShownPref preference.
VALID
VALUES
Integers that define the number of characters permitted in each
column. There should be one value for each column defined
in the MEAdvancedSearchResultsViewColumnsShownPref
preference, and the values are applied in the same order (that is,
the first value in this preference is applied to the first column in the
MEAdvancedSearchResultsViewColumnsShownPref and so on).

DEFAULT
VALUE
50
50
50
SCOPE
Site preference.
MEAPCSearchType
DESCRIPTION
Defines the type of the parts that are searched by the Auto Weld Part Connector
dialog box.
For more information about working with weld points, see the Manufacturing
VALID
VALUES
Accepts a strings as value. The string must be a valid Teamcenter type.
DEFAULT
VALUES
Item
SCOPE
Site preference.

Enterprise BOP preferences

Use these preferences to configure the Enterprise BOP feature provided in
Teamcenter’s manufacturing process management. You can use Enterprise BOP to
create and manage generic BOPs, product BOPs and partitions.
MEGenericBopContextColumnsShownPref
DESCRIPTION
Specifies the list of the columns displayed in the base view of the generic BOP.
VALID
VALUES
DEFAULT
VALUE
bl_indented_title
bl_item_object_desc
logical_designator
SCOPE
All.
MEGenericBopContextColumnsShownWidthsPref
DESCRIPTION
Specifies the width of the columns displayed in the base view of
the generic BOP. This setting affects each column defined in the
MEGenericBopContextColumnsShownPref preference.
VALID
VALUES
column. There should be one value for each column defined in the
MEGenericBopContextColumnsShownPref preference, and the values are
applied in the same order (that is, the first value in this preference is applied to the
first column in the MEGenericBopContextColumnsShownPref and so on).
DEFAULT
VALUE
25
25
25
SCOPE
All.
MEProductBopContextColumnsShownPref
DESCRIPTION
Specifies the list of the columns displayed in the base view of the product BOP.

VALID
VALUES
DEFAULT
VALUE
bl_indented_title
bl_item_object_desc
logical_designator
SCOPE
All.
MEProductBopContextColumnsShownWidthsPref
DESCRIPTION
Specifies the width of the columns displayed in the base view of
the product BOP. This setting affects each column defined in the
MEProductBopContextColumnsShownPref preference.
VALID
VALUES
MEProductBopContextColumnsShownPref preference, and the values are
first column in the MEProductBopContextColumnsShownPref and so on).
DEFAULT
VALUE
25
25
25
SCOPE
All.
MEGenericBopContextPartitionColumnsShownPref
DESCRIPTION
Specifies the list of the columns displayed in the Partitions pane of the generic BOP.
VALID
VALUES
DEFAULT
VALUE
bl_indented_title
bl_item_object_desc
Mfg0ld_representation
SCOPE
All.

MEGenericBopContextPartitionColumnsShownWidthsPref
DESCRIPTION
Specifies the width of the columns displayed in the Partitions tab
of the generic BOP. This setting affects each column defined in the
MEGenericBopContextPartitionColumnsShownPref preference.
VALID
VALUES
in the MEGenericBopContextPartitionColumnsShownPref
MEGenericBopContextPartitionColumnsShownPref and so on).
DEFAULT
VALUE
25
25
50
SCOPE
All.
MEProductBopContextPartitionColumnsShownPref
DESCRIPTION
Specifies the list of the columns displayed in the Partitions pane of the product BOP.
VALID
VALUES
DEFAULT
VALUE
bl_indented_title
bl_item_object_desc
Mfg0ld_representation
SCOPE
All.
MEProductBopContextPartitionColumnsShownWidthsPref
DESCRIPTION
Specifies the width of the columns displayed in the Partitions tab
of the product BOP. This setting affects each column defined in the
MEProductBopContextPartitionColumnsShownPref preference.

VALID
VALUES
in the MEProductBopContextPartitionColumnsShownPref
MEProductBopContextPartitionColumnsShownPref and so on).
DEFAULT
VALUE
25
25
50
SCOPE
All.
MEAssignmentsViewColumnsShownPref
DESCRIPTION
Specifies the list of the columns displayed in the Assignments view.
VALID
VALUES
DEFAULT
VALUE
bl_indented_title
bl_item_object_type
bl_item_object_desc, bl_occ_type
SCOPE
All.
MEAssignmentsViewColumnsShownWidthPref
DESCRIPTION
Specifies the width of the columns displayed in the Assignments view. This setting
affects each column defined in the MEAssignmentsViewColumnsShownPref
preference.
VALID
VALUES
MEAssignmentsViewColumnsShownPref preference, and the values are applied
in the same order (that is, the first value in this preference is applied to the first
column in the MEAssignmentsViewColumnsShownPref and so on).
DEFAULT
VALUE
50

50
50
50
SCOPE
All.
MELogicalDesignatorFormNameSuffix
DESCRIPTION
Specifies the suffix to the logical designator form. The form name for operations or
processes is:
item_id-this_preference_value
The form name for partitions is:
partition_name-this_preference_value
VALID
VALUES
Any string.
DEFAULT
VALUE
LD
SCOPE
All.
MELogicalDesignatorDelimiter
DESCRIPTION
Specifies the delimiter in the displayed name of the logical designator form. The
format is:
value_1this_preference_value....value_nthis_preference_value
VALID
VALUES
Any character.
DEFAULT
VALUE
;
SCOPE
All.

GenericBOPTemplate
DESCRIPTION
Defines the action rules when using a generic BOP as the template for the creation
of a product BOP. Generic BOP templates are available in Manufacturing Process
Planner.
VALID
VALUES
DEFAULT
VALUES
*:*:Relation.Mfg0METraceOriginRel:EBOPCreate
*:*:Relation.Mfg0MELogicalDesignatorRel:Clone
SCOPE
All.
NOTES
• Product assignments are not mapped.
• The logical designator form is cloned with the process or operation.
• The partition structure (if any) is cloned.
ProductBOPTemplate
DESCRIPTION
Defines the action rules when using a product BOP as the template for creating
another product BOP. Product BOP templates are available in Manufacturing
Process Planner.
VALID
VALUES

DEFAULT
VALUES
*:*:Relation.Mfg0METraceOriginRel:EBOPReference
*:*:Relation.IMAN_MEView:Clone
SCOPE
All.
GenericBOPAllowedTemplates
DESCRIPTION
Defines the cloning rules available when using a generic BOP as a template for
the creation of a product BOP. The rules in this preference are displayed in the
Cloning Rule menu of the Configuration pane of the Enter Template Information
step in the New Product BOP wizard.
VALID
VALUES
Accepts a list of names of cloning rules.
DEFAULT
VALUES
GenericBOPTemplate
SCOPE
All.
ProductBOPAllowedTemplates
DESCRIPTION
Defines the cloning rules available when using a product BOP as a template for the
creation of another product BOP. The rules in this preference are displayed in the
Cloning Rule menu of the Configuration pane of the Enter Template Information
step in the New Product BOP wizard.
VALID
VALUES
Accepts a list of names of cloning rules.

DEFAULT
VALUES
ProductBOPTemplate
SCOPE
All.
MEGenericBOP.MEGenericBOP.PasteDuplicateTemplate
DESCRIPTION
Defines the default cloning rule used when the Paste Duplicate command is executed
between one generic BOP context and another generic BOP context.
VALID
VALUES
DEFAULT
VALUES
*:*:Relation.Mfg0METraceOriginRel:Ignore
SCOPE
All.
MEGenericBOP.MEProductBOP.PasteDuplicateTemplate
DESCRIPTION
between a generic BOP context and a product BOP context.
VALID
VALUES

DEFAULT
VALUES
SCOPE
All.
MEProductBOP.MEProductBOP.PasteDuplicateTemplate
DESCRIPTION
between a product BOP context and another product BOP context.
VALID
VALUES
DEFAULT
VALUES

SCOPE
All.
MEProductBOP.MEGenericBOP.PasteDuplicateTemplate
DESCRIPTION
between a product BOP context and a generic BOP context.
VALID
VALUES
DEFAULT
VALUES
SCOPE
All.
PasteDuplicateTemplates
DESCRIPTION
Defines the list of cloning rules that are considered by the Paste Duplicate command.
Teamcenter chooses the appropriate rule by matching the type names that are used
as the rule name prefixes with the type names of the contexts participating in the
Paste Duplicate operation.
VALID
VALUES
Accepts the names of cloning rules in the format
SourceContextType.TargetContextType.RuleName.
DEFAULT
VALUES
MEGenericBOP.MEProductBOP.PasteDuplicateTemplate

MEProductBOP.MEProductBOP.PasteDupilcateTemplate
MEProductBOP.MEGenericBOP.PasteDuplicateTemplate
MEGenericBOP.MEGenericBOP.PasteDuplicateTemplate
SCOPE
All.
GANTT chart viewer preferences

The Gantt chart allows you to view the schedule by week, month, quarter, or year.
The Gantt chart provides a visual representation of a project’s tasks. It also shows
the dependency relationships between the elements.
MEGANTTElementHeight
DESCRIPTION
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).
VALID
VALUES
Positive integers.
DEFAULT
VALUES
14
SCOPE
All.
MEGANTTElementRGBfillColor
DESCRIPTION
Specifies the default fill color of the elements in red, green blue (RGB) code. For
example, 0;0;0 represents the color black and 0;255;255 represents the color aqua.
VALID
VALUES
String of the format int;int;int with int:=0|1|2|..|255.
DEFAULT
VALUES
149;202;255
SCOPE
All.

MEGANTTDefaultDisplayMode
DESCRIPTION
Specifies the default display mode is used on startup of a Gantt chart viewer.
VALID
VALUES
show_calculated_duration_time
Displays the calculated startup time of a Gantt chart viewer using the calculated
duration bar that appears on top of the duration bar of each level that has
descendants.
hide_calculated_duration_time
Hides the calculated startup time of a Gantt chart viewer. The calculated duration
bar does not appear.
DEFAULT
VALUES
hide_calculated_duration_time
SCOPE
All.
MEGANTTDefaultDurationTimeMode
DESCRIPTION
Specifies the default duration time mode is used on startup of a Gantt chart viewer.
VALID
VALUES
allocated_Time Specifies the startup time allocated for the Gantt chart viewer.
Allocated time is the official duration time of an operation.
estimated_Time Specifies the estimated time allocated for the Gantt chart
viewer. Estimated time is useful for early planning stages.
DEFAULT
VALUES
allocated_Time
SCOPE
All.
MEGANTTDefaultEditMode
DESCRIPTION
Specifies the default edit mode used on startup of a Gantt chart viewer.
VALID
VALUES
full_edit_mode
Specifies the full edit mode to be used on startup of a Gantt chart viewer. In the
full edit mode, you can use the toolbar buttons to edit the elements in the Gantt
chart viewer.

restricted_edit_mode
Specifies the restricted edit mode to be used on startup of a Gantt chart viewer. In
the restricted edit mode, you can still change the duration of an element using the
context menu of the element.
DEFAULT
VALUES
full_edit_mode
SCOPE
All.
MEGANTTDefaultMarkedColor
DESCRIPTION
Specifies the default color a marked element has in the representation area of the
Gantt chart viewer. For example, 0;0;0 represents the color black and 0;255;255
represents the color aqua.
VALID
VALUES
DEFAULT
VALUES
255;255;255
SCOPE
All.
MEGANTTDefaultDurationTimeColor
DESCRIPTION
Specifies the default color the duration time bar has in the representation area of
the Gantt chart viewer. For example, 0;0;0 represents the color black and 0;255;255
VALID
VALUES
DEFAULT
VALUES
0;255;255
SCOPE
All.
MEGANTTDefaultFlowColor
DESCRIPTION
Specifies the default color a flow has in the representation area of the Gantt chart
viewer. For example, 0;0;0 represents the color black and 0;255;255 represents
the color aqua.

VALID
VALUES
DEFAULT
VALUES
0;255;255
SCOPE
All.
MEGANTTMarkedFlowColor
DESCRIPTION
Specifies the default color a marked flow has in the representation of the Gantt chart
viewer. For example, 0;0;0 represents the color black and 0;255;255 represents
the color aqua.
VALID
VALUES
DEFAULT
VALUES
0;255;255
SCOPE
All.
MEGANTTimplicitFlowColor
DESCRIPTION
Specifies the default color an implicit flow has in the representation area of the
Gantt chart viewer. For example, 0;0;0 represents the color black and 0;255;255
VALID
VALUES
DEFAULT
VALUES
0;255;255
SCOPE
All.
MEGANTTPropagateDurationUpToLevel
DESCRIPTION
Specifies the level up to which the duration propagation is executed in the Gantt
chart when running the Propagate Calculated Duration command. The number of
levels is counted from the top level object downwards.

This value is only used if the MEGANTTPropagateDurationUpToLevelEnabled

preference is set to True, otherwise, Teamcenter propagates to level 0.
For more information about working with the Gantt chart, see the Manufacturing
VALID
VALUES
A positive integer number (including 0). Setting this value to 0 indicates that all
levels are propagated up.
DEFAULT
VALUES
0
SCOPE
RESTRICTIONS
MEGANTTPropagateDurationUpToLevelEnabled
DESCRIPTION
Specifies if the Propagate up to level option is enabled in the Duration
Propagation dialog box in the Gantt view and whether the value of
the MEGANTTPropagateDurationUpToLevel preference is used.
In other words, if this preference is set to False, and the value of
MEGANTTPropagateDurationUpToLevel is set to 3, Teamcenter propagates up
to level 0, as it ignores the value set in MEGANTTPropagateDurationUpToLevel.
For more information about working with the Gantt chart, see the Manufacturing
VALID
VALUES
True
The Propagate up to level option is enabled in the Duration Propagation dialog box.
False
The Propagate up to level option is not enabled in the Duration Propagation dialog
box.
DEFAULT
VALUES
False
SCOPE
RESTRICTIONS
Manufacturing features preferences

Teamcenter allows you to define features that represent design or manufacturing
features that are not defined as part of the physical structure in the BOM.

Manufacturing process management supports several feature types, including weld

points, datums, ports, mating relationships, and connections. Instances of features
are added to an MBOM structure when the structure is imported from NX.
For more information about using features, see the Manufacturing Process Planner.
MEImportMFGsPartIdAttributeName
DESCRIPTION
Specifies which BOM line property is used as the part ID when importing weld
points from an external system.
For more information about importing weld points, see the Manufacturing Process
Planner Guide.
VALID
VALUES
Any valid occurrence note.
DEFAULT
VALUES
None.
SCOPE
Site preference.
MEImportMFGsManufacturingFeatureIdAttributeName
DESCRIPTION
Specifies which BOM line property is used as the feature ID when importing weld
points from an external system.
For more information about importing weld points, see the Manufacturing Process
Planner Guide.
VALID
VALUES
Any valid occurrence note.
DEFAULT
VALUES
None.
SCOPE
Site preference.
MENEWMFG_DefaultJTDatasetName
DESCRIPTION
Specifies the name of the JT dataset that is attached by default to every newly
created manufacturing feature.
VALID
VALUES
A single character string that represents the name of a dataset that contains a JT
file of the same name.

DEFAULT
VALUES
rswp_2t
SCOPE
Site preference.
MENEWMFG_DeffaultJTFileName
DESCRIPTION
Specifies the file name that Teamcenter uses to create the default JT dataset that
represents a manufacturing feature. The file must reside in the folder pointed to by
the TC_DATA environment variable.
VALID
VALUES
A single character string that represents the name of a JT file.
DEFAULT
VALUES
rswp_2t.jt
SCOPE
Site preference.
MENEWMFG_LastJTFilePathBrowsed
DESCRIPTION
Specifies the path to which a user previously browsed to find the custom JT file to
associate with a manufacturing feature.
VALID
VALUES
An operating system path.
DEFAULT
VALUES
None.
SCOPE
Site preference.
MEMFGViewColumnShownPref
DESCRIPTION
Specifies the list of the columns displayed in the MFG View pane.
VALID
VALUES
DEFAULT
VALUE
bl_indented_title
Mfg0designation

description
SCOPE
Site preference.
MEMFGViewShownColumnWidthsPref
DESCRIPTION
Specifies the width of the columns displayed in the MFG View. This setting affects
each column defined in the MEMFGViewColumnShownPref preference.
VALID
VALUES
Integers that define the number of characters permitted in each column. There should
be one value for each column defined in the MEMFGViewColumnShownPref
preference, and the values are applied in the same order (that is, the first value in this
preference is applied to the first column in the MEMFGViewColumnShownPref
and so on).
DEFAULT
VALUE
40
20
30
SCOPE
Site preference.
MEShowWeldPointsConnectedToConfiguredOutParts
DESCRIPTION
Enables the display of weld points when connected parts are configured out, in
the manufacturing applications.
For more information about working with weld points, see the Manufacturing
VALID
VALUES
True Teamcenter displays weld points even if their connected parts
are configured out.
False Teamcenter hides weld points if at least one of the connected
parts is configured out.
DEFAULT
VALUES
False
SCOPE
Site preference.

MEMFGViewSubPanelColumnShownPref
DESCRIPTION
Specifies the columns displayed in the Connected Parts section of the MFG View.
For more information about using the MFG View, see the Manufacturing Process
Planner Guide.
VALID
VALUES
Accepts any valid column name.
DEFAULT
VALUE
bl_indented_title
description
SCOPE
Site preference.
MEMFGViewSubPanelShownColumnWidthsPref
DESCRIPTION
Specifies the width of the columns displayed in the Connected Parts
section of the MFG View. This setting affects each column defined in the
MEMFGViewSubPanelColumnShownPref preference.
VALID
VALUES
MEMFGViewSubPanelColumnShownPref preference, and the values are
first column in the MEMFGViewSubPanelColumnShownPref and so on).
DEFAULT
VALUE
40
50
SCOPE
Site preference.
MEMFGView_AssignmentFilterDefaultValue
DESCRIPTION
Defines the filter type to be used when opening an assignment filter in the MFG
View. The value of the filter type previously selected by the user in the MFG View is
stored in the preference for the next session.
VALID
VALUES
ASSIGNED The MFG View opens in assigned mode.
UNASSIGNED The MFG View opens in unassigned mode.

DEFAULT
VALUE
ASSIGNED
SCOPE
Site preference.
Standard text preferences

Teamcenter enables creating work instruction text documents from standard text
elements. These documents are associated with operations or processes in the
Manufacturing Process Planner process structure. A librarian creates a library
of standard text elements that are made available to a planner to create work
instructions.
For more information about creating a standard text library and using it to create
work instructions, see the Manufacturing Process Planner Guide.
MEWiWorkInstructionTemplate
DESCRIPTION
Specifies a name of a specification template that contains a Microsoft Word document
used as a work instruction template. The template is used as a starting point for
work instruction documents.
For more information about creating work instructions using the standard text
library, see the Manufacturing Process Planner Guide.
VALID
VALUES
Accepts a valid Teamcenter specification template name.
DEFAULT
VALUES
Work Instruction Template
SCOPE
Site preference.
NOTES
When creating your own work instruction template, it is advisable to duplicate the
Work Instruction Template template provided by Teamcenter, and then modify it
to suit your needs.
MEWiStandardTextTemplate
DESCRIPTION
Specifies a name of a specification template that contains a Microsoft Word document
used as a standard text template. The template is used as a starting point for
standard text documents.

VALID
VALUES
Accepts a valid Teamcenter specification template name.
DEFAULT
VALUES
Standard Text Template
SCOPE
Site preference.
NOTES
When creating your own standard text template, it is advisable to duplicate the
Standard Text Template template provided by Teamcenter, and then modify it
to suit your needs.
MEWiPreviewFormat
DESCRIPTION
Specifies the available file types for the format of the preview files created in the
standard text editor and in the work instruction editor. Teamcenter creates a
document of the file type specified by the first string.
VALID
VALUES
Accepts one of the following file formats supported by the Word Save As command:
pdf
mht
docx
rtf
DEFAULT
VALUES
pdf
SCOPE
Site preference.
MEWiDcdNotEditableProperties
DESCRIPTION
Specifies the list of data collection properties (DCDs) that cannot be edited in the
Properties dialog box of the Work Instructions view.
VALID
VALUES
Accepts strings of the following format:
DCD_type:att1,att2,…

DCD_type is a descendant type of the DCD base form.

DEFAULT
VALUES
Mes0MEIntegerDCDForm:Mes0ValuePlaceholder
Mes0MERealDCDForm:Mes0ValuePlaceholder
Mes0MEStringDCDForm:Mes0ValuePlaceholder
Mes0MEBooleanDCDForm:Mes0ValuePlaceholder
Mes0METimeDCDForm:Mes0ValuePlaceholder
Mes0MEEndTimeDCDForm:Mes0ValuePlaceholder
Mes0MEBuyoffDCDForm:Mes0ValuePlaceholde
Mes0MEDurationDCDFrm:Mes0ValuePlaceholder
SCOPE
Site preference.
NOTES
You can define a list either for a basic DCD type or a derived customized type.
Process Simulate preferences

The Process Simulate application allows you to design, analyze, simulate, and
optimize manufacturing processes from the factory level down to lines and
workcells. It provides optional advanced capabilities that are not available in other
Teamcenter’s manufacturing process management applications. Process Simulate is
fully integrated into Teamcenter, and you can send data to it from Manufacturing
Process Planner.
For more information about using Process Simulate, see the Manufacturing Process
Planner Guide.
MEDataSetsToBeCheckoutForProcessSimulate
DESCRIPTION
Indicates which datasets to check out when running any of the scenarios that include
datasets. It stores pairs of dataset types and relations.
VALID
VALUES
Accepts string values with the following format:
Dataset type:Relation
DEFAULT
VALUES
ProcessSimulateSceneDetails:IMAN_specification
ProcessSimulateSimDetails:IMAN_specification
ProcessSimulate3DRep:IMAN_specification
ProcessSimulateSceneDetails:IMAN_reference
ProcessSimulateSimDetails:IMAN_reference
ProcessSimulate3DRep:IMAN_reference
ProcessSimulateSceneDetails:ProcessSimulate_Details
ProcessSimulateSimDetails:ProcessSimulate_Details

ProcessSimulate3DRep:ProcessSimulate_Details
Kinematics:KinematicsRelation
ProcessSimulateCompDetails:ProcessSimulate_Details
SCOPE
Site preference.
NOTES
Specifying the wildcard, *, as the relation includes all possible relations for that
dataset type.
MEFormsToBeCheckoutForProcessSimulate
DESCRIPTION
Indicates which forms to check out. It stores pairs of form types and the relation.
VALID
VALUES
Accepts string values with the following format:
Type:Relation
DEFAULT
VALUES
ProcessSimulateActivity:*
SCOPE
Site preference.
NOTES
Specifying the wildcard, *, as the relation includes all possible relations. In other
words, this type of form is always checked out.
MEReportColumnsForProcessSimulate
DESCRIPTION
Indicates the ordered list of column names displayed in the report for failed checkout
objects in the Process Simulate Check-Out menu command.
VALID
VALUES
Accepts valid column names in the order you want them to appear:
value_1, value_2, ...
DEFAULT
VALUES
object_string
object_type
checked_out_user
object_desc
SCOPE
Site preference.

MEReportColumnWidthForProcessSimulate
DESCRIPTION
Specifies the widths for the columns displayed in the report for failed checkout
objects in the Process Simulate Check-Out menu command, as defined in the
MEReportColumnsForProcessSimulate preference.
VALID
VALUES
Accepts integer values. The number of integers must match the number of columns
described in the MEReportColumnsForProcessSimulate preference.
DEFAULT
VALUES
22
18
22
18
SCOPE
Site preference.
PLMXML_pre_expand_bop
DESCRIPTION
Specifies whether or not to pre-expand structures within Teamcenter before running
the PLM XML expand operation. This reduces the time it takes to send data from
Teamcenter to Process Simulate.
If the value of the PLMXML_pre_expand_max_line_limit preference is set to 0
and this preference value is set to TRUE, the structure is pre-expanded, meaning
that the PLMXML_pre_expand_batch_size preference is set to its maximum
value and the value of the PLMXML_pre_expand_max_line_limit preference is
disregarded.
Setting this preference can affect the performance of other PLM XML exports of
structures from manufacturing applications.
VALID
VALUES
TRUE The structure is pre-expanded.
FALSE The structure is not pre-expanded.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.

PLMXML_pre_expand_max_line_limit
DESCRIPTION
Sets the maximum number of lines in a structure that are to be expanded prior to
running the PLM XML expand operation. Structures that are a target for export
can be fully expanded prior to their export step, which provides a performance
improvement. However, there are memory concerns with large structures whereby
a full expansion may take more than the available memory of the system. This
preference sets a limit.
VALID
VALUES
0 No lines are pre-expanded.
-1 There is no limit on the number of lines to pre-expand.
DEFAULT
VALUES
0
SCOPE
Site preference.
PLMXML_pre_expand_batch_size
DESCRIPTION
Sets batch size for each single expansion of a structure prior to running the PLM
XML expand operation. Structures that are a target for export can be fully expanded
prior to their export step, which provides a performance improvement. However,
there are memory concerns with large structures whereby a full expansion may take
more than the available memory of the system. This preference sets a limit. Values
must be greater than 0. The smaller the batch size, the more likely that the value
set in the PLMXML_pre_expand_max_line_limit preference will not be exceeded
but at the cost of less performance gain.
VALID
VALUES
Accepts any integer value greater than 0.
DEFAULT
VALUES
1000
SCOPE
Site preference.

Chapter
21 Visualization preferences
3DMarkup_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
DMI_markup_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
INTEROP_ExtraPLMXMLInstanceAttributes . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Interop_Vis_Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
Interop_Vis_Attributes_Admin_Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4
ItemRevision_DirectModel3DMarkup_default_relation . . . . . . . . . . . . . . . . . 21-4
ItemRevision_Vis_Session_default_relation . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
MetaDataStamp_template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
PLM_End_Item_Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6
SecondaryVMUDatasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7
TC_DIS_2D_named_ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7
TC_DIS_3D_named_ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
TC_DIS_Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
TC_Schematic_BOMView_Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
TC_show_open_in_vmu_button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
VIS_multi_file_datasettypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
VisMarkup_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
VisSession_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-10
VMU_Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-10
VMU_FileSearchOrder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-11
VMU_RelationSearchOrder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-12

Chapter
21 Visualization preferences
Use the visualization preferences to modify how the stand-alone viewer, the Lifecycle
Viewer, and the embedded viewers that are located within Teamcenter applications
such as My Teamcenter and the Structure Manager interact with Teamcenter.
3DMarkup_relation_primary
DESCRIPTION
Indicates the list of valid primary object types for the 3Dmarkup relation. These
are the dataset types that you can mark up with the 3D markup tools. The format
is relation-name_relation_primary=List of valid primary object types. This
preference is applicable for the stand-alone viewer and the Lifecycle Viewer.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter dataset type.
DEFAULT
VALUES
DirectModel
DirectModelAssembly
SCOPE
Site preference.
DMI_markup_relation_primary
DESCRIPTION
Indicates the list of valid primary object types for the DMI_markup relation.
These are the dataset types that you can mark up with the 2D markup tools. The
format is relation-name_relation_primary=List of valid primary object types. This
preference is applicable for the stand-alone viewer and the Lifecycle Viewer.
VALID
VALUES
DEFAULT
VALUES
DirectModel
DrawingSheet
Image
SCOPE
Site preference.

Chapter 21 Visualization preferences
INTEROP_ExtraPLMXMLInstanceAttributes
DESCRIPTION
Determines the mapping of Structure Manager BOM line attributes to Lifecycle
Visualization attributes.
Note
• This preference is applicable only for PLM XML generated by the
BOMWriter. For the SOA-based Teamcenter integration with Lifecycle
Visualization 8 and later, use the Interop_Vis_Attributes and
Interop_Vis_Attributes_Admin_Filter preferences.
• This preference works only with stand-alone Lifecycle Visualization and

the Lifecycle Viewer.
VALID
VALUES
Accepts multiple string pairs as values. Each group of strings must be in the
following format:
target:root/part/instance/occurrence
key:Lifecycle Visualization attribute name
prop:BOM line property
|propuid:bomline property tag value converted to UID
|literal: literal string
|attr:attribute name
target:root writes user attributes to the ProductRevisionView element of the top

BOM line item revision in the generated PLM XML file.
target:part writes user attributes to all ProductRevisionView elements in the
generated PLM XML file.
target:instance writes user attributes to all Instance elements in the generated
PLM XML file.
target:occurrence writes user attributes to all Occurrence elements in the
generated PLM XML file.
For example, the following values create the following mappings:
target:Occurrence
key:USER_DATA_1
prop:bl_ItemRevision Master_user_data_1
target:Instance
key:COMMENTS
prop:bl_ItemRevision Master_item_comment
key:CATEGORY
literal:CRITICALPART
target:Part
key:BOM_VIEW_TAG
propuid:bl_bomview

Visualization preferences
Maps the user_data_1 attribute from the child Item Revision Master form to the
USER_DATA_1 Lifecycle Visualization attribute. This mapping is written on all
Occurrence elements.
Maps the comments attribute from the child Item Revision Master form to the
COMMENTS Lifecycle Visualization attribute. This mapping is written on all
Instance elements.
Maps the CRITICALPART (literal string) to the CATEGORY Lifecycle
Visualization attribute. This mapping is written on all Instance elements.
Maps the bl_bomview (UID value) to the BOM_VIEW_TAG Lifecycle Visualization
attribute. This mapping is written on all ProductRevisionView elements.
DEFAULT
VALUES
None.
SCOPE
Site preference.
Interop_Vis_Attributes
DESCRIPTION
Indicates which Teamcenter attributes are displayed in Lifecycle Visualization.
The Lifecycle Visualization Teamcenter Integration Preferences dialog box
(File→Preferences→Teamcenter Integration→Attributes) provides a convenient
user interface for managing this preference.
The Interop_Vis_Attributes preference corresponds to the right column in the
Teamcenter Integration Preferences dialog box as shown.
VALID
VALUES
A list of Teamcenter BOM line attributes. If
Interop_Vis_Attributes_Admin_Filter is set, Interop_Vis_Attributes must
be a subset of it.
DEFAULT
VALUES
None.
SCOPE
Can be set in any scope. The Lifecycle Visualization Teamcenter Integration
Preferences dialog box writes Interop_Vis_Attributes in user scope.

Interop_Vis_Attributes_Admin_Filter
DESCRIPTION
Indicates which Teamcenter attributes are presented to users in the
Lifecycle Visualization Teamcenter Integration Preferences dialog box
(File→Preferences→Teamcenter Integration→Attributes). Those presented are
the ones that users can then display (see the Interop_Vis_Attributes preference
description).
The Interop_Vis_Attributes_Admin_Filter preference corresponds to the left
column in the Teamcenter Integration Preferences dialog box as shown.
If there is no setting for the Interop_Vis_Attributes_Admin_Filter preference,

the left column lists all BOM line attributes as candidates for users to select display
(that is, candidates to move to right column).
VALID
VALUES
A list of Teamcenter BOM line attributes. If
Interop_Vis_Attributes_Admin_Filter is set, Interop_Vis_Attributes must
be a subset of it.
DEFAULT
VALUES
None.
SCOPE
Can be set in any scope.
ItemRevision_DirectModel3DMarkup_default_relation
DESCRIPTION
Specifies the relation that has to be created when a DirectModel3DMarkup
dataset is pasted under an item revision. The relation specified for this preference is
the default relation that is created between the DirectModel3DMarkup dataset
and the target item revision. This preference is applicable for the stand-alone viewer
and the Lifecycle Viewer.
Warning
This preference is set automatically by the application and must not be
modified.

VALID
VALUES
A valid Teamcenter relation.
DEFAULT
VALUES
VisMarkup
SCOPE
Site preference.
ItemRevision_Vis_Session_default_relation
DESCRIPTION
Specifies the relation that has to be created when a Vis_Session dataset is pasted
under an item revision. The relation specified for this preference is the default
relation that is created between the Vis_Session dataset and the target item
revision. This preference is applicable for the stand-alone viewer and the Lifecycle
Viewer.
Warning
modified.
VALID
VALUES
A valid Teamcenter relation.
DEFAULT
VALUES
VisSession
SCOPE
Site preference.
MetaDataStamp_template
DESCRIPTION
Specifies the item ID of the item revision that provides the MetaDataStamp
template dataset. The MetaDataStamp template drives the formatting styles used
in rendering the text and watermark stamp content.
The default MDS_default_styles_template.mds template file is located in the
$TC_DATA directory in the RAC; it is imported to the database as a dataset called
MDS_default_styles_template.

Note
To replace the default template, do one of the following:
• Delete the Item containing the MetaDataStamp Template dataset from
the database. Place the custom MDS_default_styles_template file
inside the $TC_DATA folder and run the add_mds_template import
script to add the new template to the database. Note that the template file
must be named MDS_default_styles_template.
• In the rich client, perform a search to locate the

MDS_default_styles_template dataset. Right-click the dataset, choose
Named References, and then delete the existing dataset and re-import
the new one.
VALID
VALUES
The item ID of the item revision that contains the MetaDataStamp template
dataset.
DEFAULT
VALUES
MDS_default_styles_template
SCOPE
Site preference.
PLM_End_Item_Key
DESCRIPTION
Indicates which Teamcenter occurrence note (BOM line attribute key/name) is used
to identify an occurrence as an end item. If the identified occurrence note exists on
an occurrence and has a value of True, that occurrence is treated as an end item
by the viewer.
For information on using end items to control the scope of clearance analysis, see
Working with 3D Models.
VALID
VALUES
A string representing the key/name of the corresponding Teamcenter occurrence
note.
DEFAULT
VALUES
None.
SCOPE
Can be set to any scope.

SecondaryVMUDatasets
DESCRIPTION
Defines the dataset types, connected using a secondary relationship, used to search
for files in ambiguous conditions. Ambiguous conditions result from performing
file operations on objects or datasets.
These are the non-VMU dataset types that can contain VMU datasets. VMU
datasets are datasets that can be directly launched from the rich client or the thin
client into the Lifecycle Viewer or a stand-alone viewer.
VALID
VALUES
The existing NX dataset values.
DEFAULT
VALUES
UGMASTER
UGPART
UGALTREP
SCOPE
Site preference.
TC_DIS_2D_named_ref
DESCRIPTION
Defines the possible reference names of 2D file types that are capable of 2D markups.
This preference is applicable for the Lifecycle Viewer and the viewers embedded in
Teamcenter applications such as My Teamcenter and Structure Manager.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter reference
name.
DEFAULT
VALUES
Quickshade-Image
PLT
BMP
CAL
TIFF
Graphics-Interface
Sheet
PDF
JPEG
TIF
SCOPE
Site preference.

TC_DIS_3D_named_ref
DESCRIPTION
Defines the possible reference names of 3D file types that are capable of 3D markups.
This preference is applicable for the Lifecycle Viewer and the viewers embedded in
Teamcenter applications such as My Teamcenter and Structure Manager.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter reference
name.
DEFAULT
VALUES
ConfiguredAssembly
UGPART
IMAGE
SCOPE
Site preference.
TC_DIS_Search
DESCRIPTION
The search schemas used when searches are performed from the file dialogs within
the stand-alone viewers and the Lifecycle Viewer.
VALID
VALUES
One or more strings as values; each string must be an existing Teamcenter search
schema.
DEFAULT
VALUES
Dataset…
Item…
Item Revision…
Part
SCOPE
User preference.
TC_Schematic_BOMView_Types
DESCRIPTION
Determines whether Lifecycle Visualization is used in schematic mode or 3D mode.
If left unset, Lifecycle Visualization is used in 3D mode.
VALID
VALUES
Takes multiple strings as values. Each value must be a set of BOM View types. It is
intended that the types represent logical BOMs. For example:
Piping System View

Electrical System View
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_show_open_in_vmu_button
DESCRIPTION
Specifies whether the Start/Open in Lifecycle Visualization button is displayed in
the rich client and the View→Teamcenter Visualization menu command is displayed
in the thin client.
VALID
VALUES
DEFAULT
VALUES
false
SCOPE
User preference.
VIS_multi_file_datasettypes
DESCRIPTION
Specifies the visualization dataset types that can contain more than one named
reference. Users can view the selected named reference in the My Teamcenter
embedded viewer.
VALID
VALUES
DEFAULT
VALUES
DirectModel
DrawingSheet
SCOPE
Site preference.
VisMarkup_relation_primary
DESCRIPTION
Indicates the valid primary object type for the Visualization 3DMarkup relation.
The format is relation-name_relation_primary=valid primary object type. This
preference is applicable for the stand-alone viewers and the Lifecycle Viewer.

Warning
modified.
VALID
VALUES
A valid Teamcenter dataset type.
DEFAULT
VALUES
ItemRevision
SCOPE
Site preference.
VisSession_relation_primary
DESCRIPTION
Indicates the valid primary object type for the Visualization Session relation.
The format is relation-name_relation_primary=valid primary object type. This
preference is applicable for the stand-alone viewers and the Lifecycle Viewer.
Warning
modified.
VALID
VALUES
A valid Teamcenter dataset type.
DEFAULT
VALUES
ItemRevision
SCOPE
Site preference.
VMU_Datasets
DESCRIPTION
Determines the datasets that can be directly launched in Teamcenter’s lifecycle
visualization using the File→Open in VMU command in the rich client, or using the
View link from a dataset page in the thin client. To open files such as .tiff files and
PDF files, the dataset types used to manage these files must be appended to the
existing values for this preference. You must also add the custom reference names
within these custom dataset types to the VMU_FileSearchOrder preference.
VALID
VALUES
DEFAULT
VALUES
ClearanceDBConnection

ClearanceDBReport
ClearanceResults
ClearanceResultsFilter
DirectModel
DirectModel3DMarkup
DirectModelAnimation
DirectModelAssembly
DirectModelFlowChart
DirectModelIllustrationBook
DirectModelIllustrationSheet
DirectModelMarkup
DirectModelMotion
DirectModelSession
DrawingSheet
ECADDFX
Image
JtSimplification
Markup
Nastran
PADImage
PADReport
PCBFATF
PCBMarkup
SCHFATF
SnapShotViewData
Text
VisJackEnvironment
VisJackFigure
VisJackPosture
VisJackPsurf
VisMovieCapture
VisPublishGeometryAsset
VisPublishTechnicalIllustration
VisPublishTechnicalPortfolio
VisPublishVisioStencil
VisPublishVisioTemplate
VisQualityCluster
Vis_Session
VSAProcessDoc
VSAMeasurementDoc
Zone
SCOPE
Site preference.
VMU_FileSearchOrder
DESCRIPTION
Defines the order that reference names are used to search for files in ambiguous
conditions. Ambiguous conditions result from performing file operations on objects or
datasets. Add your custom dataset types to the VMU_Datasets preference to launch

them in Teamcenter’s lifecycle visualization. You must also add the custom reference
names within these custom dataset types to the VMU_FileSearchOrder preference.
VALID
VALUES
One or more strings as a values; each string must be a named reference that exists
within datasets that can be loaded in Teamcenter’s lifecycle visualization mockup.
DEFAULT
VALUES
Markup
Image
JTPART
JTSESSION
Package
ConfiguredAssembly
3DModel
Quickshade-Image
PLT
BMP
CAL
TIFF
Graphics-Interface
Sheet
Process
Measurement
FlowChart
Animation
Motion
IllustrationBook
IllustrationSheet
SCOPE
Site preference.
VMU_RelationSearchOrder
DESCRIPTION
Defines the ordered list of relations used for searching relations between
visualization datasets and items or item revisions. New relations must be added to
the list.
VALID
VALUES
One or more strings; each string must be a valid Teamcenter relation.
DEFAULT
VALUES
IMAN_Rendering
IMAN_specification
IMAN_MOTION
IMAN_3D_snap_shot
IMAN_manifestation
TC_Attaches

SCOPE
Site preference.

Chapter
22 Solution-specific preferences
Aerospace and Defense preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

ADSDrawing_Revision_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1
ADS_Lists_DrawingRevisions_relation_primary . . . . . . . . . . . . . . . . . . . 22-1
ADS_Lists_PartRevisions_relation_primary . . . . . . . . . . . . . . . . . . . . . . 22-2
ADS_Lists_Parts_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
ADSTechDocument Revision_DefaultChildProperties . . . . . . . . . . . . . . . . 22-3
ADSTechDocument Revision_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . . 22-3
TC_customization_libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
TC_LAST_USED_PATTERNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Consumer Packaged Goods preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4

TC_Interspec_URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Teamcenter Automotive Edition preferences . . . . . . . . . . . . . . . . . . . . . . . . . 22-4

EngChange Revision_<Change_Type>_Revise_no_copy . . . . . . . . . . . . . . 22-5
EngChange Revision_<Change_Type>_SaveAs_no_copy . . . . . . . . . . . . . . 22-5
GMO_GRP_show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-6
GMO_GRP_hostname_default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7
GMO_GRP_browser_default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7
GMO_GRP_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7
GMO_GRP_req_ir_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
GMO_GRP_edit_prop_mapping_default . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
GMO_GRP_req_edit_props_default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
TCAE_autogen_name_form_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-9
RDV_build_intent_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
RDV_default_options_for_tracking_vehicle . . . . . . . . . . . . . . . . . . . . . . 22-10
RDV_default_option_values_for_tracking_vehicle . . . . . . . . . . . . . . . . . 22-11
RDV_product_obsoletion_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-11
RDV_usage_synchronized_architecture_type . . . . . . . . . . . . . . . . . . . . . 22-12
GMO_RDV_enable_audit_criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-12
GMO_enable_new_pnum_match_criteria . . . . . . . . . . . . . . . . . . . . . . . 22-12
IPVBOM_build_intent_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-13
TC_external_system_item_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-13
TC_external_system_bom_attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 22-14
TC_external_system_attr_value_separator . . . . . . . . . . . . . . . . . . . . . . 22-14
TC_send_to_external_system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-15
TC_external_system_url . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-15
TC_external_system_url_value_name . . . . . . . . . . . . . . . . . . . . . . . . . . 22-16
TC_Configuration_File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-16
IPVBOM_compare_mode_var_level_RevisionCompare_ItemTypes . . . . . . 22-16
IPVBOM_compare_mode_var_level_Occurrence_Notes . . . . . . . . . . . . . . 22-17
IPVBOM_UPCFNA_OccNoteName . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-18
TCAE_installation_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-18

TAE_Powertrain_site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-19
Plant_Cost_Form_Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-19
ISS_Cost_Form_Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-20
QR_Cost_Form_Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-20
ME_Cost_Form_Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-20
Piece_Cost_Form_Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-21
Investment_Cost_Form_Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-21
GMO_MATFORM_AUTOCREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-22
Teamcenter’s mechatronics process management preferences . . . . . . . . . . . . 22-22

Connected_ToRules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-22
Implemented_ByRules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-23
Realized_ByRules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-24
APN_absolute_path_name_separator . . . . . . . . . . . . . . . . . . . . . . . . . . 22-24
GDE_exclude_list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-25
GDELink_default_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-25
TC_releasable_logical_types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-25
ESM_Software_Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-26
ESM_<Category>_Software_Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-27
ESM_Processor_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-27
ESM_processor_direct_child_of_hardware . . . . . . . . . . . . . . . . . . . . . . . 22-28
ESM_Processor_is_gateway_attr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-28
ESM_Processor_linked_attr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-29
ESM_Processor_programmableInService_attr . . . . . . . . . . . . . . . . . . . . 22-29
ESM_Processor_memoryType_attr . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-29
ESM_Processor_byteOrder_attr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-30
ESM_Processor_architecture_attr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-30
ESM_HW_Compatibility_Report_TransferMode . . . . . . . . . . . . . . . . . . 22-30
ESM_SW_Compatibility_Report_TransferMode . . . . . . . . . . . . . . . . . . . 22-31
ESM_HW_Compatibility_Report_HTML_StyleSheet_Dataset . . . . . . . . . 22-31
ESM_SW_Compatibility_Report_HTML_StyleSheet_Dataset . . . . . . . . . 22-32
ESM_HW_Compatibility_Report_Excel_StyleSheet_Dataset . . . . . . . . . . 22-32
ESM_SW_Compatibility_Report_Excel_StyleSheet_Dataset . . . . . . . . . . 22-32
ESM_Compatibility_Report_Excel_Template_Dataset . . . . . . . . . . . . . . 22-33
ParmDefIntRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-33
datasetParmDefIntRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . 22-33
ParmDefDblRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-34
datasetParmDefDblRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . 22-34
ParmDefStrRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-34
datasetParmDefStrRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . 22-35
ParmDefBoolRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-35
datasetParmDefBoolRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . 22-35
ParmDefDateRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . 22-36
datasetParmDefDateRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . 22-36
ParmDefHexRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-36
datasetParmDefHexRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . 22-37
ParmDefSEDRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . 22-37
datasetParmDefSEDRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . 22-37
ParmDefBCDRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . 22-38
datasetParmDefBCDRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . 22-38
ParmGrpValRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-38
datasetParmGrpValRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . 22-39
ParmDefBitDefRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . 22-39
datasetParmDefBitDefRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . 22-39

ParmGrpDef.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-40
datasetParmGrpDef.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . . . . . 22-40
ParmDef.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-40
datasetParmDef.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-41
ParmGrpDefRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-41
datasetParmGrpDefRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . 22-41
ProductVariant.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-42
datasetProductVariant.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . . . 22-42
ProductVariant.CREATERENDERING . . . . . . . . . . . . . . . . . . . . . . . . . 22-42
datasetProductVariantCreate.REGISTEREDTO . . . . . . . . . . . . . . . . . . 22-43
ProductVariantIntent.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-43
datasetProductVariantIntent.REGISTEREDTO . . . . . . . . . . . . . . . . . . 22-43
ProductVariantIntent.CREATERENDERING . . . . . . . . . . . . . . . . . . . . 22-44
datasetProductVariantIntentCreate.REGISTEREDTO . . . . . . . . . . . . . . 22-44
Ccd0ColumnPreference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-44
CCDM_grp_rev_val . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-45
HRN_wire_length_data_relation_primary . . . . . . . . . . . . . . . . . . . . . . . 22-45
HRN_associated_part_relation_secondary . . . . . . . . . . . . . . . . . . . . . . . 22-46
HRN_node_referenced_component_relation_secondary . . . . . . . . . . . . . . 22-46
HRN_part_data_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-47
HRN_fixing_assignment_relation_primary . . . . . . . . . . . . . . . . . . . . . . 22-48
SIG_asystem_source_rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-48
SIG_asystem_target_rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-49
SIG_asystem_transmitter_rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-49
SIG_pvariable_rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-50
SIG_redundant_rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-50
Vendor management preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-51

BidPackageLineItem_default_relation . . . . . . . . . . . . . . . . . . . . . . . . . 22-51
BidPackageLineItem_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . 22-51
BidPackageLineItem_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-51
BidPackageRevision_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . 22-52
BidPackageRevision_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-52
CommercialPart_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . 22-53
CommercialPart_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-53
CompanyLocation_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . 22-54
CompanyLocation_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-54
ContactInCompany_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . 22-54
LocationInCompany_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . 22-55
ManufacturerPart_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . 22-55
ManufacturerPart_DefaultPSEProperties . . . . . . . . . . . . . . . . . . . . . . . 22-56
ManufacturerPart_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-56
ManufacturerPartRevision.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . 22-56
ManufacturerPart Revision.RENDERING . . . . . . . . . . . . . . . . . . . . . . . 22-57
ManufacturerPart Revision.SUMMARYRENDERING . . . . . . . . . . . . . . 22-57
ManufacturerPartRevSummary.SUMMARY_REGISTEREDTO . . . . . . . 22-57
ManufacturerPart.REGISTEREDTO . . . . . . . . . . . . . . . . . . . . . . . . . . 22-58
ManufacturerPart.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-58
ManufacturerPart.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . 22-58
ManufacturerPartSummary.SUMMARY_REGISTEREDTO . . . . . . . . . . 22-59
ProvidedFrom_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-59
PseudoFolder.ContactInCompany_ColumnPreferences . . . . . . . . . . . . . . 22-60
PseudoFolder.lineitems_ColumnPreferences . . . . . . . . . . . . . . . . . . . . . 22-60
PseudoFolder.LocationInCompany_ColumnPreferences . . . . . . . . . . . . . 22-60

PseudoFolder.ProvidedFrom_ColumnPreferences . . . .. . . . . . . . . . . . . . 22-61
PseudoFolder.TC_part_quote_rel_ColumnPreferences . . . . . . . . . . . . . . 22-61
Quote_DefaultChildProperties . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-62
Restricted_Vendor_Part_Statuses . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-62
Restricted_Vendor_Statuses . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-62
TC_Distributor_info_form . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-63
TC_Manufacturer_info_form . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-63
TC_part_quote_rel_relation_primary . . . . . . . . . . . .. . . . . . . . . . . . . . 22-63
TC_Quality_Document_relation_primary . . . . . . . . .. . . . . . . . . . . . . . 22-63
TC_Supplier_info_form . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-64
TC_vendor_part_rel_relation_primary . . . . . . . . . . .. . . . . . . . . . . . . . 22-64
Vendor_DefaultChildProperties . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-64
Vendor_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-65
VendorRevision_DefaultChildProperties . . . . . . . . . .. . . . . . . . . . . . . . 22-65
VendorRevision_PseudoFolder . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-66
VMRepresents_relation_primary . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-67
VMS_Maintain_Vendor_History . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-67
VMS_vendor_part_selection_rule . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 22-67
MRO core preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-68

HierarchicalWSO_HierarchicalWSO_default_relation . . . . . . . . . . . . . . 22-68
Item_CharacteristicDefinition_default_relation . . . . . . . . . . . . . . . . . . . 22-68
ItemRevision_CharacteristicDefinition_default_relation . . . . . . . . . . . . . 22-68
LogBook_PhysicalPart_default_relation . . . . . . . . . . . . . . . . . . . . . . . . 22-69
LogBook_WorkspaceObject_default_relation . . . . . . . . . . . . . . . . . . . . . 22-69
Lot.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-69
Lot_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-70
MRONeutralColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-70
MRONeutralShownColumnWidthsPref . . . . . . . . . . . . . . . . . . . . . . . . . 22-70
ManufacturingIdCharsForPhysicalPartIdPref . . . . . . . . . . . . . . . . . . . . 22-71
MROAlternateColorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-71
MRODeviatedColorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-72
MROExtraToDesignColorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-72
MROMissingColorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-73
MROSubstituteColorPref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-73
PartLogisticsForm.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . 22-73
PartNumberCharsForPhysicalPartIdPref . . . . . . . . . . . . . . . . . . . . . . . 22-74
PhysicalContext_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-74
PhysicalElement_Company_default_relation . . . . . . . . . . . . . . . . . . . . . 22-74
PhysicalPart_Company_default_relation . . . . . . . . . . . . . . . . . . . . . . . . 22-75
PhysicalPart_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . . . . 22-75
PhysicalPartRelationsToExport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-76
PhysicalPart.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . . . . . 22-76
PhysicalPartRevision_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . 22-76
PhysicalPartRevision.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . 22-77
PhysicalRealization_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . . 22-77
SerialNumberCharsForPhysicalPartIdPref . . . . . . . . . . . . . . . . . . . . . . 22-77
SerialNumberGenerator_DefaultChildProperties . . . . . . . . . . . . . . . . . . 22-78
SerialNumberGenerator.SUMMARYRENDERING . . . . . . . . . . . . . . . . 22-78
UtilizationViewColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-78
As-Built Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-79

AsBuiltManagerColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-79
AsBuiltManagerShownColumnWidthsPref . . . . . . . . . . . . . . . . . . . . . . 22-79

DefaultAsBuiltCompareProperties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-80
AdditionalAsBuiltCompareProperties . . . . . . . . . . . . . . . . . . . . . . . . . . 22-80
DefaultAsBuiltAccCheckProperties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-81
AdditionalAsBuiltAccCheckProperties . . . . . . . . . . . . . . . . . . . . . . . . . 22-81
Service Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-81

As-Maintained preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-82
AdditionalAsMaintainedAccCheckProperties . . . . . . . . . . . . . . . . . . 22-82
AdditionalAsMaintainedCompareProperties . . . . . . . . . . . . . . . . . . 22-82
DefaultAsMaintainedAccCheckProperties . . . . . . . . . . . . . . . . . . . . 22-82
DefaultAsMaintainedCompareProperties . . . . . . . . . . . . . . . . . . . . 22-83
MroConfigRuleName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-83
MRODefaultLocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-83
PhysicalLocation_CompanyLocation_default_relation . . . . . . . . . . . . 22-84
PhysicalLocationContainsColumnsShownPref . . . . . . . . . . . . . . . . . 22-84
PhysicalLocation_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . 22-84
ServiceManagerAssetGroupColumnsShownPref . . . . . . . . . . . . . . . . 22-85
ServiceManagerAssetGroupColumnWidthsPref . . . . . . . . . . . . . . . . 22-85
ServiceManagerColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . 22-86
ServiceManagerShownColumnWidthsPref . . . . . . . . . . . . . . . . . . . . 22-86
ServiceManagerPhysicalLocationColumnsShownPref . . . . . . . . . . . . 22-87
ServiceManagerPhysicalLocationColumnWidthsPref . . . . . . . . . . . . 22-87
Service event management preferences . . . . . . . . . . . . . . . . . . . . . . . . . 22-87
ActivityCost.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-88
ActivityCost.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . . 22-88
ActivityEntryValue.MROCREATERENDERING . . . . . . . . . . . . . . . 22-88
ActivityEntryValue.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . 22-89
ActivityEntryValue.SUMMARYRENDERING . . . . . . . . . . . . . . . . . 22-89
FaultCode.MROCREATERENDERING . . . . . . . . . . . . . . . . . . . . . . 22-89
FaultCode.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-89
FaultCode.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . . . . 22-90
MRODefaultLogBook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-90
PartMovement_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . 22-90
PartMovement.ENABLE_PROPERTIES_EDIT . . . . . . . . . . . . . . . . 22-91
PartMovement.MROCREATERENDERING . . . . . . . . . . . . . . . . . . 22-91
PartMovement.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-91
PartMovement.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . 22-92
ServiceAction.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-92
ServiceAction.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . 22-92
ServiceDiscrepancy_DefaultChildProperties . . . . . . . . . . . . . . . . . . 22-92
ServiceDiscrepancy.ENABLE_PROPERTIES_EDIT . . . . . . . . . . . . . 22-93
ServiceDiscrepancy_FaultCode_default_relation . . . . . . . . . . . . . . . 22-93
ServiceDiscrepancy.MROCREATERENDERING . . . . . . . . . . . . . . . 22-93
ServiceDiscrepancy.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . 22-94
ServiceDiscrepancy_ServiceEvent_default_relation . . . . . . . . . . . . . 22-94
ServiceDiscrepancy_ServiceGroup_default_relation . . . . . . . . . . . . . 22-94
ServiceDiscrepancy.SUMMARYRENDERING . . . . . . . . . . . . . . . . . 22-95
ServiceEvent_DefaultChildProperties . . . . . . . . . . . . . . . . . . . . . . . 22-95
ServiceEvent.ENABLE_PROPERTIES_EDIT . . . . . . . . . . . . . . . . . 22-95
ServiceEvent.MROCREATERENDERING . . . . . . . . . . . . . . . . . . . . 22-96
ServiceEvent.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-96
ServiceEvent.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . 22-96
ServiceGroup.ENABLE_PROPERTIES_EDIT . . . . . . . . . . . . . . . . . 22-96
ServiceGroup.MROCREATERENDERING . . . . . . . . . . . . . . . . . . . 22-97

ServiceGroup.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-97
ServiceGroup.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . . 22-97
TransactionElement.COLUMNS_SHOW . . . . . . . . . . . . . . . . . . . . . 22-98
TransactionElement.COLUMNS_WIDTH . . . . . . . . . . . . . . . . . . . . 22-98
TransactionElement_DefaultChildProperties . . . . . . . . . . . . . . . . . . 22-98
TransactionElement_Document_default_relation . . . . . . . . . . . . . . . 22-99
TransactionElement_DocumentRevision_default_relation . . . . . . . . . 22-99
TransactionElement_PhysicalElement_default_relation . . . . . . . . . . 22-99
TransactionElement_PhysicalElementRevision_default_relation . . . . 22-99
Service Request Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-100

ActivityCost.MROCREATERENDERING . . . . . . . . . . . . . . . . . . . . . . 22-100
ActivityCost_SRP0RqstActivityRevision.MROCREATERENDERING . . 22-100
ActivityCost_SRP0ServiceOffering.MROCREATERENDERING . . . . . . 22-101
ActivityCost_SRP0ServiceRequest.MROCREATERENDERING . . . . . . 22-101
CM_SRP0DgSrvRequestRevision_displayed_pseudofolders . . . . . . . . . . 22-101
CM_SRP0PrSrvRequestRevision_displayed_pseudofolders . . . . . . . . . . 22-102
CM_SRP0RqstActivityRevision_displayed_pseudofolders . . . . . . . . . . . 22-102
CompanyContact.MROCREATERENDERING . . . . . . . . . . . . . . . . . . 22-103
CompanyLocation.MROCREATERENDERING . . . . . . . . . . . . . . . . . . 22-103
SR_CHANGE_HOME_SITE_PREFERENCE . . . . . . . . . . . . . . . . . . . 22-103
SRP0DgSrvRequest.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . 22-104
SRP0DgSrvRequestRevision.MROCREATERENDERING . . . . . . . . . . 22-104
SRP0DgSrvRequestRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . 22-104
SRP0DgSrvRequestRevision.SUMMARYRENDERING . . . . . . . . . . . . 22-105
SRP0DgSrvRequestRevision_DefaultChildProperties . . . . . . . . . . . . . . 22-105
SRP0PrSrvRequest.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . 22-105
SRP0PrSrvRequestRevision.MROCREATERENDERING . . . . . . . . . . . 22-106
SRP0PrSrvRequestRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . 22-106
SRP0PrSrvRequestRevision.SUMMARYRENDERING . . . . . . . . . . . . . 22-106
SRP0PrSrvRequestRevision_DefaultChildProperties . . . . . . . . . . . . . . 22-106
SRP0RequalifyRqstActivityRevision.MROCREATERENDERING . . . . . 22-107
SRP0RqstActivity.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . . . 22-107
SRP0RqstActivityRevision.MROCREATERENDERING . . . . . . . . . . . . 22-107
SRP0RqstActivityRevision.RENDERING . . . . . . . . . . . . . . . . . . . . . . 22-108
SRP0RqstActivityRevision.SUMMARYRENDERING . . . . . . . . . . . . . . 22-108
SRP0RqstActivityRevision_DefaultChildProperties . . . . . . . . . . . . . . . 22-108
SRP0RqstActivityRevision_ServiceDiscrepancy_default_relation . . . . . . 22-109
SRP0ServiceCatalog.MROCREATERENDERING . . . . . . . . . . . . . . . . 22-109
SRP0ServiceCatalog.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-109
SRP0ServiceCatalog.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . 22-110
SRP0ServiceCatalog_DefaultChildProperties . . . . . . . . . . . . . . . . . . . 22-110
SRP0ServiceCatalog_HWSOStructure_default_relation . . . . . . . . . . . . 22-110
SRP0ServiceCatalog_PseudoFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-111
SRP0ServiceCatalog_SRP0ProductCatalog_default_relation . . . . . . . . . 22-111
SRP0ServiceDiscrepancy.MROCREATERENDERING . . . . . . . . . . . . . 22-111
SRP0ServiceOffering.MROCREATERENDERING . . . . . . . . . . . . . . . . 22-112
SRP0ServiceOffering.RENDERING . . . . . . . . . . . . . . . . . . . . . . . . . . 22-112
SRP0ServiceOffering.SUMMARYRENDERING . . . . . . . . . . . . . . . . . . 22-112
SRP0ServiceOffering_ActivityCost_default_relation . . . . . . . . . . . . . . . 22-112
SRP0ServiceOffering_DefaultChildProperties . . . . . . . . . . . . . . . . . . . 22-113
SRP0ServiceOffering_HWSOStructure_default_relation . . . . . . . . . . . . 22-113
SRP0ServiceOffering_SRP0ServiceCatalog_default_relation . . . . . . . . . 22-113
SRP0ServiceOfferingTable_ColumnPreferences . . . . . . . . . . . . . . . . . . 22-114

SRP0StatusViewColumnsShownPref . . . . . . . . . . . . . . . . . . . . . . . . . 22-114

Chapter
22 Solution-specific preferences
Solution-specific preferences modify the functionality or appearance of Teamcenter’s

solution-specific applications, such as Teamcenter Automotive Edition.
Aerospace and Defense preferences

Aerospace and Defense preferences can only be used if the Aerospace and Defense
template has been purchased and installed. Use these preference to configure and
modify the behavior of the template.
ADSDrawing_Revision_PseudoFolder
DESCRIPTION
Determines which properties are displayed as pseudo folders within an
ADSDrawing Revision object.
VALID
VALUES
Accepts one or more strings as values, each string must be a Teamcenter property.
DEFAULT
VALUES
ADS_Lists_DrawingRevisions
SCOPE
Site preference.
ADS_Lists_DrawingRevisions_relation_primary
DESCRIPTION
Determines the valid primary object types for the
ADS_Lists_DrawingRevisions_relation_primary relation. All ADS drawings
created for a given ADSTechDocument are associated to that ADSTechDocument
Revision with the ADS_Lists_DrawingRevisions_relation_primary relation.

Chapter 22 Solution-specific preferences
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid Teamcenter object.
DEFAULT
VALUES
ADSTechDocument Revision
SCOPE
Site preference.
ADS_Lists_PartRevisions_relation_primary
DESCRIPTION
Determines the valid primary object types for the ADS_Lists_PartRevisions
relation. All ADS part and ADS design revisions created on a given
ADSTechDocument are associated to that ADSTechDocument Revision with
the ADS_Lists_PartRevisions relation.
VALID
VALUES
DEFAULT
VALUES
SCOPE
Site preference.
ADS_Lists_Parts_relation_primary
DESCRIPTION
Determines the valid primary object types for the
ADS_Lists_Parts_relation_primary relation. All ADS part and ADS design
revisions created on a source document other than an assembly are termed
foreign components. When a foreign component is added to an assembly, the
ADS_Lists_Parts relation is created between the source document revision of the
assembly, and the item corresponding to the foreign component.
VALID
VALUES
DEFAULT
VALUES
SCOPE
Site preference.

Solution-specific preferences
ADSTechDocument Revision_DefaultChildProperties
DESCRIPTION
Determines which properties can be used as children of the selected
ADSTechDocument Revision type.
VALID
VALUES
property.
DEFAULT
VALUES
ADS_Lists_PartRevisions
ADS_Lists_Parts
SCOPE
Site preference.
ADSTechDocument Revision_PseudoFolder
DESCRIPTION
Determines which properties are displayed as pseudo folders within a
ADSTechDocument Revision object.
VALID
VALUES
property.
DEFAULT
VALUES
ADS_Lists_PartRevisions
ADS_Lists_Parts
SCOPE
Site preference.
TC_customization_libraries
DESCRIPTION
Initializes the vendor management and product structure and parts list (PSPL)
customization libraries that assist in the storage of executable codes.
VALID
VALUES
Accepts one or more strings as values, each string must be a valid library name.
DEFAULT
VALUES
libvm
libpspl

SCOPE
Site preference.
TC_LAST_USED_PATTERNS
DESCRIPTION
Stores the last selected naming pattern for a given business object property.
VALID
VALUES
Accepts one or more strings as values, each string must be a valid naming pattern.
DEFAULT
VALUES
None.
SCOPE
User preference.
Consumer Packaged Goods preferences

Consumer Packaged Goods preferences can only be used if the Consumer Packaged
Goods solution has been purchased and installed. Use these preference to configure
and modify the behavior of the solution.
TC_Interspec_URL
DESCRIPTION
Stores the base URL of the Interspec thin client. It is used to launch the Interspec
thin client from Teamcenter.
VALID
VALUES
Accepts one string as a value and the string must be a valid URL. For example:
http://Hostname/SpecificationModule.version/Site/Login/Login.aspx
Contact the Interspec administrator for the exact URL value.

DEFAULT
VALUES
None.
SCOPE
All.
Teamcenter Automotive Edition preferences

The Teamcenter Automotive Edition package offers robust assembly configuration
and design functionality relevant to variability-intensive industries such as
automotive design and manufacture.

Use these preferences to determine such behavior as how item revisions are revised
and what types of relations are created when using the Teamcenter Automotive
Edition package.
EngChange Revision_<Change_Type>_Revise_no_copy
DESCRIPTION
Specifies objects that are not copied forward to a new item revision when an change
object of the specified type is revised or saved as a new revision.
This preference is inserted into the database only upon installation of Teamcenter
Automotive Edition.
VALID
VALUES
Set this preference with a combination of the preference name EngChange
Revision_Change-Type_Revise_no_copy where Change-Type is a valid Teamcenter
change type, plus one or more values. Accepts one or more strings as a values; each
string must be a valid Teamcenter object.
DEFAULT
VALUES
EngChange Revision_PWT Common Change_Revise_no_copy=
EC_affected_item_rel:*
EC_solution_item_rel:*
EC_problem_item_rel:*
EC_reference_item_rel:*
EC_addressed_by_rel:*
IMAN_specification:Business Case Form
IMAN_specification:CRB Form
IMAN_specification:Change Service Form
EngChange Revision_PWT Stop Change_Revise_no_copy=

SCOPE
Site preference.
EngChange Revision_<Change_Type>_SaveAs_no_copy
DESCRIPTION
Specifies objects that are not copied forward to a new item revision when an change
object of the specified type is saved as a new revision.

Automotive Edition.
VALID
VALUES
Set this preference with a combination of the preference name EngChange
Revision_Change-Type_SaveAs_no_copy where Change-Type is a valid
Teamcenter change type, plus one or more values. Accepts one or more strings as a
values; each string must be a valid Teamcenter object.
DEFAULT
VALUES
EngChange Revision_PWT Common Change_SaveAs_no_copy=
EngChange Revision_PWT Stop Change_SaveAs_no_copy=

SCOPE
Site preference.
GMO_GRP_show
DESCRIPTION
Determines whether the Global Part Reuse Project (GRP) buttons and menu
commands display in the My Teamcenter and Structure Manager toolbars.
VALID
VALUES
TRUE The Global Part Reuse Project (GRP) buttons and menu
commands display in the My Teamcenter and Structure
Manager toolbars.
FALSE The Global Part Reuse Project (GRP) buttons and menu
commands do not display in the My Teamcenter and Structure
Manager toolbars.
DEFAULT
VALUES
FALSE

SCOPE
Site preference.
GMO_GRP_hostname_default
DESCRIPTION
Specifies the host name of the Web server connected to via the GRP-I2 code.
VALID
VALUES
Accepts a single string as a value. Must be the host name of a valid Web server.
DEFAULT
VALUES
None.
SCOPE
Site preference.
GMO_GRP_browser_default
DESCRIPTION
Specifies the browser used by the Global Part Reuse Project (GRP) code.
VALID
VALUES
Accepts a single string as a value. Must be the absolute path and executable name of
the browser.
DEFAULT
VALUES
None.
SCOPE
Site preference.
GMO_GRP_port
DESCRIPTION
Specifies the port number to be used to connect to the Global Part Reuse Project
(GRP) server.
VALID
VALUES
Accepts a single string as a value. Must be a valid port name.
DEFAULT
VALUES
7101
SCOPE
Site preference.

GMO_GRP_req_ir_types
DESCRIPTION
Specifies the list of item revision types for which the Global Part Reuse Project
(GRP) functionality is required. Allows users to edit and validate the item revision
types specified in this preference.
VALID
VALUES
Accepts multiple strings as values. Must be a valid Teamcenter item revision type.
DEFAULT
VALUES
CORP_Part Revision
SCOPE
Site preference.
GMO_GRP_edit_prop_mapping_default
DESCRIPTION
Specifies the Global Part Reuse Project (GRP) mapping values for Teamcenter’s
Automotive Edition–GM Overlay–Teamcenter property names. The Teamcenter’s
Automotive Edition–GM Overlay–Teamcenter property names and the GRP property
names are separated by the ~ delimiter.
VALID
VALUES
Accepts multiple strings values. Each string must contain a valid Teamcenter’s
Automotive Edition–GM Overlay–Teamcenter property name and a valid GRP
property name, separated by the ~ delimiter. For example:
GMO_GRP_edit_prop_mapping_default=
items_tag~Part
project_id~DLS
DEFAULT
VALUES
items_tag~Part
project_id~DLS
SCOPE
Site preference.
GMO_GRP_req_edit_props_default
DESCRIPTION
Specifies the item revision (and item revision-related) properties whose values are
extracted. The Global Part Reuse Project (GRP) code uses composite property syntax
to retrieve these values. Thus, the values for this preference must follow this syntax.

VALID
VALUES
Accepts multiple strings values. Each string must obey composite property syntax.
The composite property of an object defines a path to associated objects, with
potential multiple levels of direction, resulting in an evaluation of a regular property
on that or these associated objects. Each step in this chain references the next
related objects in the path and is specified with the following components:
typed_reference
untyped_reference
typed_relation
untyped_relation
The syntax of a composite property is:

objectTypeName.referenceProperty[(criteriaProperty=criteriaValue
[,criteriaProperty=criteriaValue]:referenceProperty
[(criteriaProperty=criteriaValue[,criteriaProperty=criteriaValue]):property
objectTypeName is a Teamcenter object type name (such as UGMASTER).
referenceProperty is either a typed_reference, untyped_reference,
typed_relation, or untyped_relation.
criteriaProperty can be any valid composite property (recursion).
For example:
GMO_GRP_req_edit_props_default=
ItemRevision.item_master_tag:dls
DEFAULT
VALUES
ItemRevision.item_master_tag:dls
SCOPE
Site preference.
TCAE_autogen_name_form_types
DESCRIPTION
Allows automatic generation of form names when a specified form type is created and
attached to an item revision. The name is concatenated from the item ID/revision ID.
VALID
VALUES
Accepts multiple strings as values. Each value must be a valid Teamcenter form type.
DEFAULT
VALUES
Plant Cost Form
ISS Cost Form
QR Cost Form

ME Cost Form
Investment Cost Form
Piece Cost Form
Program Date Form
PWT Revision Form
CORP Part Mass Form
Material
PWT Drawing Form
PWT Part Form
GM Build Intent Form
SCOPE
Site preference.
RDV_build_intent_status
DESCRIPTION
Defines the release status applied on the CORP_Build object when a new version of
a Tracking Vehicle definition is imported. Tracking Vehicle definitions are imported
as CORP_Build objects with an attached Saved Variant rule which contains all
the set option values. This rule is attached with a specification relation to the
CORP_Build revision. Tracking vehicle information is imported in the form of
an PLM XML file.
If the CORP_Build object already exists in the Teamcenter database, and this
preference is set to obsolete, the latest revision of the CORP_Build object is
assigned obsolete status and a new revision is created.
VALID
VALUES
Accepts a single string as a value. Must be a valid release status.
DEFAULT
VALUES
Obsolete
SCOPE
All.
RDV_default_options_for_tracking_vehicle
DESCRIPTION
Defines the options created for a saved variant rule when creating a tracking vehicle.
Tracking vehicle definitions are imported as CORP_Build objects with an attached
saved variant rule which contains all the set option values. This rule is attached with
a specification relation to the CORP_Build revision. Tracking vehicle information
is imported in the form of an PLM XML file; options defined in the PLM XML file are
also applied to the saved variant rule.
VALID
VALUES
Accepts multiple strings as values. Each value must be a valid option defined for
the given vehicle assembly structure.

DEFAULT
VALUES
ProductionUsage
ServiceUsage
SCOPE
Site preference.
RDV_default_option_values_for_tracking_vehicle
DESCRIPTION
Defines the values for the options created via the
RDV_default_options_for_tracking_vehicle preference.
Tracking vehicle definitions are imported as CORP_Build objects with an attached
saved variant rule which contains all the set option values. This rule is attached with
a specification relation to the CORP_Build revision. Tracking vehicle information
is imported in the form of an PLM XML file; options defined in the PLM XML file are
also applied to the saved variant rule.
VALID
VALUES
Accepts multiple strings as values. The values are applied to the options created in
the RDV_default_options_for_tracking_vehicle preference.
DEFAULT
VALUES
Y
N
SCOPE
Site preference.
RDV_product_obsoletion_status
DESCRIPTION
Defines the release status used to sunset a vehicle assembly structure (VAS). When
the release status defined in this preference is assigned to the VAS, no further usage
data are imported on the daily import cycle.
A VAS is updated with usage data only if it has been registered. A VAS is registered
by attaching a CORP_Vehicle_Revision_Master_Form form to the top-level item
revision of the VAS, the CORP_Vehicle_Revision.
VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter status name.
DEFAULT
VALUES
unset
SCOPE
All.

RDV_usage_synchronized_architecture_type
DESCRIPTION
Determines which architecture breakdown elements are created while importing
usages with the RDV_import_usage utility.
VALID
VALUES
Accepts multiple strings as values. It must be one or more of the following
architecture breakdown types:
UPCFNA
Architecture
DEFAULT
VALUES
UPCFNA
SCOPE
All.
GMO_RDV_enable_audit_criteria
DESCRIPTION
Defines which candidate lines are considered for audit. Set this preference to TRUE
for all occurrences within the vehicle assembly structure (VAS) to be audited.
VALID
VALUES
TRUE All occurrences within the vehicle assembly structure (VAS)
are audited.
FALSE Only type CORP_Part occurrences that are children of a
CORP_Install type are audited.
DEFAULT
VALUES
FALSE
SCOPE
All.
GMO_enable_new_pnum_match_criteria
DESCRIPTION
Determines whether the system checks for EWO_status during an audit. If a
U-Link usage is assigned a Red part number match by any criteria, its attributes
are given an additional check for EWO_status. If the status is new, the part number
match is changed from fail to partial pass.
VALID
VALUES
TRUE The system performs the additional check.
FALSE The system does not perform the additional check.

DEFAULT
VALUES
FALSE
SCOPE
All.
IPVBOM_build_intent_status
DESCRIPTION
Lists the statuses of a build intent to be skipped when exporting the build intent
using the gmo_ipvbom_export utility.
Use the utility to export the build intent itself, all the build intents in the Teamcenter
database, specific build intents along with partial builds, or the full BOM export
with the delta export.
For more information about using the utility, see the Utilities Reference.
VALID
VALUES
Accepts multiple strings as values. Each value must be a valid Teamcenter status.
DEFAULT
VALUES
pulled
cancelled
SCOPE
Site preference.
TC_external_system_item_type
DESCRIPTION
Determines the behavior of the Send to External System command on the Tools
menu in Structure Manager. When this menu command is selected, the system
sends calibration information generated from the selected installation assembly to a
URL (defined via the TC_external_system_url preference). An external system
can then access this information from a Web browser.
The calibration information is generated by sending the installation assembly to
Structure Manager, where the values are obtained from the attributes of whichever
item type is specified in this preference. Typically, a Teamcenter Automotive
Edition-specific item type is specified, such as the CORP_Software item type.
VALID
VALUES
Accepts a single string as a value. Must be a valid Teamcenter item type. For
example, CORP_Software or CORP_Software.
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_external_system_bom_attributes
DESCRIPTION
The calibration information is generated by sending the installation assembly to
Structure Manager, where the values are obtained from the attributes of the item
type defined in the TC_external_system_item_type preference. Which attributes
are generated as calibration information is determined by this preference.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter BOM
attribute. For example:
bl_item_item_id
bl_rev_object_desc
bl_abs_occ_id
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_external_system_attr_value_separator
DESCRIPTION
The calibration information is generated by sending the installation assembly
to PSE, where the values are obtained from the attributes of the item
type defined in the TC_external_system_item_type preference. Which
attributes are generated as calibration information is determined by the
TC_external_system_bom_attributes preference. How the system concatenates
the attribute values is determined by this preference. For example:
part#,itemrev,partdesc,upc/fna
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid separator. For
example:
-
,

DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_send_to_external_system
DESCRIPTION
Determines whether the Send to External System command displays on the Tools
menu in Structure Manager. This menu command allows the system to send
calibration information generated from the selected installation assembly to a URL
(defined via the TC_external_system_url preference). An external system can
then access this information from a Web browser.
VALID
VALUES
ON The Send to External System command displays on the Tools
menu in Structure Manager.
OFF The Send to External System command does not display on
the Tools menu in Structure Manager.
DEFAULT
VALUES
OFF
Note
If the Teamcenter Automotive Edition is installed, the default setting is ON.
SCOPE
Site preference.
TC_external_system_url
DESCRIPTION
sends calibration information generated from the selected installation assembly to
a URL. An external system can then access this information from a Web browser.
The locator is defined via this preference.
VALID
VALUES
Accepts a single string as a value. Must be a valid URL.
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_external_system_url_value_name
DESCRIPTION
Determines the name tag of the information posted to the URL defined in the
TC_external_system_url preference. The cgi-bin/server script uses this name
tag to search for the posted data.
VALID
VALUES
Accepts a single string as a value. Must be a valid name tag.
DEFAULT
VALUES
None.
SCOPE
Site preference.
TC_Configuration_File
DESCRIPTION
Determines the configuration file used to convert an input file. Conversion is based
on the arguments within the configuration file. By default, the configuration file is
the bintool_config.txt file. Its default location is the temp folder (Windows) or
the user’s home folder (UNIX).
The configuration file contains the conversion arguments and output filename/type
separated by the | separator. After the input file is converted into the output format
as specified by the user successfully, it is imported as a named reference to the
Software dataset. (The old named reference to the same dataset is deleted.) A new
dataset version is created and associates the converted file to the dataset as its
named reference.
If the file conversion fails, the import process is terminated and an error message
appears.
VALID
VALUES
Accepts multiple strings as values. Each string must be the name of a valid
configuration file.
DEFAULT
VALUES
bintool_config.txt
SCOPE
Site preference.
IPVBOM_compare_mode_var_level_RevisionCompare_ItemTypes
DESCRIPTION
Compares the revision IDs of two selected BOM lines via the custom comparator.
When two BOM lines are selected for comparison, the custom comparator can use
the item ID of the selected item to determine adds/deletes between the two BOM

lines. Thus, for example, when a vehicle assembly structure (VAS) is configured
based on a given build intent, it is possible to export only newly added (or newly
deleted) CORP_Part revisions to the VAS, compared to the previously exported
configuration. Set this preference to the item type whose IDs you want to be
compared.
Use this functionality when working with build intent processes.
Use the gmo_ipvbom_export utility to export the build intent itself, all the build
intents in the Teamcenter database, specific build intents along with partial builds,
or the full BOM export with the delta export.
For more information about using the utility, see the Utilities Reference manual.
VALID
VALUES
Accepts multiple strings as values. Each value must be a valid Teamcenter item
type. For example:
IPVBOM_compare_mode_var_level_RevisionCompare_ItemTypes=
CORP_Part
In this example, the item revision IDs higher up in the VAS (such as
CORP_Proc_Plan and CORP_Install would be ignored in the comparison. Only
revision changes of parts would be highlighted.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IPVBOM_compare_mode_var_level_Occurrence_Notes
DESCRIPTION
Compares quantity and variant condition differences of two selected BOM lines
via the custom comparator. When two BOM lines are selected for comparison, the
custom comparator can use the sequence number to determine adds/deletes between
the two BOM lines. Thus, for example, when a vehicle assembly structure (VAS) is
configured based on a given build intent, it is possible to export only newly added (or
newly deleted) quantity changes to the VAS, compared to the previously exported
configuration. Set this preference to the occurrence notes you want to be compared.
Use this functionality when working with build intent processes.
Use the gmo_ipvbom_export utility to export the build intent itself, all the build
intents in the Teamcenter database, specific build intents along with partial builds,
or the full BOM export with the delta export.
For more information about using the utility, see the Utilities Reference manual.
VALID
VALUES
Accepts multiple strings as values. Each value must be a valid Teamcenter
occurrence note type. For example:
IPVBOM_compare_mode_var_level_Occurrence_Notes=
@UPCFN001_01
@Qnty001_01

@UOMNm001_01
@Torq001_01
In this example, any changes in the occurrence notes between the compared BOM
lines would be highlighted.
DEFAULT
VALUES
None.
SCOPE
Site preference.
IPVBOM_UPCFNA_OccNoteName
DESCRIPTION
Defines which occurrence notes are used with iPVBOM functionality. This
functionality allows pulled part information to be imported from the downstream
EMS purchasing system to Teamcenter. Subsequent full, partial, and incremental
BOM exports filter out parts that have been pulled.
VALID
VALUES
UPC
FNA
DEFAULT
VALUES
UPC
FNA
SCOPE
Site preference.
TCAE_installation_level
DESCRIPTION
Determines whether to check for Teamcenter Automotive Edition and GM Overlay
licenses.
Automotive Edition. After installing Teamcenter Automotive Edition, set this
preference to either 2 or 3 to match your license level.
VALID
VALUES
1 No license.
2 Teamcenter Automotive Edition license.
3 Teamcenter Automotive Edition-GM Overlay.

DEFAULT
VALUES
1
SCOPE
Site preference.
TAE_Powertrain_site
DESCRIPTION
Determines which groups can view Powertrain data. Limiting access to necessary
groups improves performance.
VALID
VALUES
0 No users can view Powertrain forms or the enhanced New Item
dialog box. Use when no users at your site are members of a
Powertrain group and viewing this data is not required.
1 Only members of Powertrain groups can view Powertrain forms
and the enhanced New Item dialog box. Use when not all users
at your site are members of a Powertrain group and you want
only Powertrain groups to have access to Powertrain data.
2 All members of Powertrain groups can view Powertrain forms
and the enhanced New Item dialog box. Use when all users at
your site are members of Powertrain groups, and you want all
users to have access to Powertrain data.
DEFAULT
VALUES
0
SCOPE
Site preference.
Plant_Cost_Form_Elements
DESCRIPTION
Determines which cost types display in the Plant Cost form.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter cost
type. The order of the values in the preference determine the order of the cost type
columns (from left to right) in the form.
DEFAULT
VALUES
In House Tools Costs
Operations Costs
Startup Pre-Productions Costs
Scrap Costs
Cancellation Costs

SCOPE
Site preference.
ISS_Cost_Form_Elements
DESCRIPTION
Determines which cost types display in the ISS Cost form.
VALID
VALUES
DEFAULT
VALUES
Operations Costs
Scrap Costs
Cancellation Costs
SCOPE
Site preference.
QR_Cost_Form_Elements
DESCRIPTION
Determines which cost types display in the QR Cost form.
VALID
VALUES
DEFAULT
VALUES
Operations Costs
Scrap Costs
Cancellation Costs
SCOPE
Site preference.
ME_Cost_Form_Elements
DESCRIPTION
Determines which cost types display in the ME Cost form.

VALID
VALUES
DEFAULT
VALUES
Operations Costs
Scrap Costs
Cancellation Costs
SCOPE
Site preference.
Piece_Cost_Form_Elements
DESCRIPTION
Determines which cost types display in the Piece Cost form.
VALID
VALUES
DEFAULT
VALUES
Operations Costs
Scrap Costs
Cancellation Costs
SCOPE
Site preference.
Investment_Cost_Form_Elements
DESCRIPTION
Determines which cost types display in the Investment Cost form.
VALID
VALUES
DEFAULT
VALUES

Operations Costs
Scrap Costs
Cancellation Costs
SCOPE
Site preference.
GMO_MATFORM_AUTOCREATE
DESCRIPTION
Determines whether the system automatically creates a Material form in
Teamcenter and attaches it to the CORP_Part revision (if one is not already
attached) when a user saves a UGMaster dataset in NX containing material part
attributes.
VALID
VALUES
TRUE The system automatically creates a Material form in
Teamcenter and attaches it to the CORP_Part revision (if
one is not already attached) when a user saves a UGMaster
dataset in NX containing material part attributes.
FALSE The system does not create a Material form in Teamcenter
and attaches it to the CORP_Part revision (if one is not
already attached) when a user saves a UGMaster dataset in
NX containing material part attributes.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
Teamcenter’s mechatronics process management preferences

The Teamcenter’s mechatronics process management package is a tool for designing
complex electromechanical structures.
Use Teamcenter’s mechatronics process management preferences to determine such
behavior as business rule implementation within the Teamcenter’s mechatronics
process management package.
Connected_ToRules
DESCRIPTION
Defines any constraints on the valid primary/secondary object combination allowed
for the Connected_To Generic Relationship Management (GRM) relation. GRM
rules contain a primary type, a relation type, and multiple secondary types. If no
constraint is defined for a given primary object or its superTypes, then there is no

constraint on the combination of secondary objects allowed for the Connected_To

relationship with the given primary object.
For more information about GRM rule construction and management, see the
Business Modeler IDE Guide.
VALID
VALUES
Constraints are defined in the following format:
primaryObjectType:secondaryObjectType1,secondaryObjectType2
primaryObjectType is any type or subtype of PSConnection or GDELink
class/subclass, and secondaryObjectType is any valid ImanType type.
DEFAULT
VALUES
Connection:Network_Port,Connection_Terminal
TC_Link:Network_Port,Connection_Terminal
WeldPoint:Item
DatumPoint:Item
SCOPE
Site preference.
Implemented_ByRules
DESCRIPTION
for the Implemented_By Generic Relationship Management (GRM) relation.
GRM rules contain a primary type, a relation type, and multiple secondary
types. If no constraint is defined for a given primary object or its superTypes,
there is no constraint on the combination of secondary objects allowed for the
Implemented_By relationship with the given primary object.
VALID
VALUES
The object types are any valid ImanType type.
DEFAULT
VALUES
Connection_Terminal:Item
Connection:Item
SCOPE
Site preference.

Realized_ByRules
DESCRIPTION
for the Realized_By Generic Relationship Management (GRM) relation. GRM
rules contain a primary type, a relation type, and multiple secondary types. If no
constraint is defined for a given primary object or its superTypes, there is no
constraint on the combination of secondary objects allowed for the Realized_By
relationship with the given primary object.
VALID
VALUES
The object types are any valid ImanType type.
DEFAULT
VALUES
Interfaces:Interfaces
SCOPE
Site preference.
APN_absolute_path_name_separator
DESCRIPTION
Defines the separator used between the parentNodeName and the
childNodeName while displaying the absolute path name for a given
AppearancePathNode.
VALID
VALUES
Accepts a single string as a value. The following special characters are recommended
values:
.
,
;
/
#
DEFAULT
VALUES
->
SCOPE
Site preference.

GDE_exclude_list
DESCRIPTION
Defines the hierarchical object types and subtypes the system excludes when
generating a list of types to display in the Item Element creation dialog box. Any
valid Teamcenter’s mechatronics process management general design elements
(GDE) type defined in this preference will not display in the drop-down list of
possible types to create.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid, domain-specific
Teamcenter GDE type.
DEFAULT
VALUES
InterfaceDefinition
ProcessVariable
SCOPE
Site preference.
GDELink_default_type
DESCRIPTION
Defines the default general design element (GDE) type used when creating a new
connection when a user does not specify a GDE type during creation.
VALID
VALUES
Accepts a single string as a value. Must be a valid, Teamcenter GDE type.
DEFAULT
VALUES
TC_Link
SCOPE
Site preference.
TC_releasable_logical_types
DESCRIPTION
Specifies which releasable logical types are displayed in the Process Selector dialog
box. The dialog box lists unreleased logical components of a selected assembly.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid release type.
DEFAULT
VALUES
PSConnectionRevision
PSSignalRevision
GeneralDesignElement

SCOPE
Site preference.
ESM_Software_Categories
DESCRIPTION
Used for the Embedded Software Manager (ESM). Defines the different categories of
software in use at the site. The default software categories are automatically defined
during installation of the Embedded Software Manager when the option to install
default software categories is taken. If the option to install the defaults is not taken
during installation, this preference must be set manually.
For every software category defined in this preference, a corresponding
ESM_Category_Software_Types preference must be created. For example, if the
values of the ESM_Software_Categories preference are:
ESM_Software_Categories=
PrimeBootloader
SecBootLoader
Application
Calibration
Config
The following three preferences must be created:
ESM_Bootloader_Software_Types=
Bootloader
ESM_Calibration_Software_Types=
Calibration_Type_1
Calibration_Type_2
ESM_Application_Software_Types=
Strategy
VALID
VALUES
Accepts multiple strings as values. Each string must be a category of software.
DEFAULT
VALUES
If the option to install default software categories is taken during installation, the
default values are:
Bootloader
Calibration
Strategy
SCOPE
Site preference.

ESM_<Category>_Software_Types
DESCRIPTION
Used for the Embedded Software Manager (ESM). Defines the different types used to
describe the related software category defined in the ESM_Software_Categories
preference. The default software types are automatically defined during installation
of the Embedded Software Manager when the option to install default software
categories and types is taken. If the option to install the defaults is not taken during
installation, this preference must be set manually.
For every software category defined in the ESM_Software_Categories preference,
a corresponding ESM_Category_Software_Types preference must be created. For
example, if the values of the ESM_Software_Categories preference are:
ESM_Software_Categories=
Bootloader
Calibration
Application
The following three ESM software types preferences must be created:

ESM_Bootloader_Software_Types=
Bootloader
ESM_Calibration_Software_Types=
Calibration_Type_1
Calibration_Type_2
ESM_Application_Software_Types=
Application
VALID
VALUES
type (or subtype) corresponding to that category of the software.
DEFAULT
VALUES
If the option to install default software categories is taken during installation, a
preference for each category is created, containing the values of the corresponding
category type.
SCOPE
Site preference.
ESM_Processor_Type
DESCRIPTION
Used for the Embedded Software Manager (ESM). Defines the processor types used
to represent the ECU hardware processor.
VALID
VALUES
Accepts a single value. Must be a valid Teamcenter item type (or item subtype).

DEFAULT
VALUES
If the option to implement a default processor is taken during installation, the
default value is:
Proccessor
SCOPE
Site preference.
ESM_processor_direct_child_of_hardware
DESCRIPTION
Used for the Embedded Software Manager (ESM). Specifies the number of levels a
ESM processor is located below the hardware in a BOM structure.
VALID
VALUES
TRUE Indicates the processor is one level below the hardware.
FALSE Indicates the processor is more than one level below hardware.
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
ESM_Processor_is_gateway_attr
DESCRIPTION
Used for the Embedded Software Manager (ESM). Defines the existing processor’s
Revision Master form’s logical attribute. This attribute determines whether the
processor is a Gateway processor or not.
VALID
VALUES
Accepts a single value. Must represent the logical attribute on the Revision Master
form of the item type defined in the ESM_Processor_Type preference.
DEFAULT
VALUES
If the option to implement a default processor is taken during installation, the
default value is:
is_gateway
SCOPE
Site preference.

ESM_Processor_linked_attr
DESCRIPTION
Used for the Embedded Software Manager (ESM). Defines the name of the existing
processor revision master form’s logical attribute that determines whether the
processor is linked. This attribute specifies whether the processor is linked to the
network.
VALID
VALUES
Accepts a single value. Must be an existing item types’s revision master form’s
logical attribute representing if a processor is linked.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ESM_Processor_programmableInService_attr
DESCRIPTION
processor revision master form’s logical attribute that determines whether the
processor is programmable while in service.
VALID
VALUES
Accepts a single value. Must be an existing item types’s revision master form’s
logical attribute representing whether a processor is programmable in service.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ESM_Processor_memoryType_attr
DESCRIPTION
processor revision master form’s string attribute that determines the memory type
attribute of the processor.
VALID
VALUES
Accepts a single value. Must be an existing item types’s revision master form’s string
attribute representing the processor’s memory type.
DEFAULT
VALUES
None.

SCOPE
Site preference.
ESM_Processor_byteOrder_attr
DESCRIPTION
processor revision master form’s string attribute that determines the processor’s
byte order.
VALID
VALUES
attribute representing the byte order used by the processor.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ESM_Processor_architecture_attr
DESCRIPTION
processor revision master form’s string attribute that determines the processor’s
architecture.
VALID
VALUES
attribute representing the architecture (32-bit or 64-bit) used by the processor.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ESM_HW_Compatibility_Report_TransferMode
DESCRIPTION
Used for the Embedded Software Manager (ESM). Determines the transfer mode used
while generating the PLM XML file containing the compatibility reports of software
for a selected hardware. Depending on the transfer mode, you may have to modify the
corresponding ESM_HW_Compatibility_Report_HTML_StyleSheet_Dataset
style sheet preference so that, if the transfer mode generates more information, the
style sheet displays it correctly.
Transfer mode objects combine rules and property sets to define the context of the
PLM XML import or export operation. These objects are presented as context options
when you import or export objects or system data using the Teamcenter applications.

For more information, see the PLM XML Export Import Administration Guide.
VALID
VALUES
Accepts a single value. Must be a valid Teamcenter transfer mode.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ESM_SW_Compatibility_Report_TransferMode
DESCRIPTION
Used for the Embedded Software Manager (ESM). Determines the transfer mode used
while generating the PLM XML file containing the compatibility reports of hardware
for a selected software. Depending on the transfer mode, you may have to modify the
corresponding ESM_SW_Compatibility_Report_HTML_StyleSheet_Dataset
style sheet preference so that, if the transfer mode generates more information, the
style sheet displays it correctly.
Transfer mode objects combine rules and property sets to define the context of the
PLM XML import or export operation. These objects are presented as context options
when you import or export objects or system data using the Teamcenter applications.
For more information, see the PLM XML Export Import Administration Guide.
VALID
VALUES
Accepts a single value. Must be a valid Teamcenter transfer mode.
DEFAULT
VALUES
None.
SCOPE
Site preference.
ESM_HW_Compatibility_Report_HTML_StyleSheet_Dataset
DESCRIPTION
Used for the Embedded Software Manager (ESM). Determines the name of the
dataset containing the style sheet used to display the compatible software of a given
hardware in HTML format.
VALID
VALUES
Accepts a single value. Must be a valid Teamcenter dataset.
DEFAULT
VALUES
None.
SCOPE
Site preference.

ESM_SW_Compatibility_Report_HTML_StyleSheet_Dataset
DESCRIPTION
dataset containing the style sheet used to display the compatible hardware of a
given software in HTML format.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ESM_HW_Compatibility_Report_Excel_StyleSheet_Dataset
DESCRIPTION
dataset containing the style sheet used to display the compatible software of a given
hardware in Excel format.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ESM_SW_Compatibility_Report_Excel_StyleSheet_Dataset
DESCRIPTION
dataset containing the style sheet used to display the compatible hardware of a
given software in Excel format.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.

ESM_Compatibility_Report_Excel_Template_Dataset
DESCRIPTION
dataset containing the Excel template used to display the hardware-software and
software-hardware compatibility reports.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
ParmDefIntRevision.RENDERING
DESCRIPTION
Sets the rendering component for ParmDefIntRevision business object and all its
children. The value of this preference is a dataset name that contains the XML style
sheet used for rendering the components of this type.
VALID
VALUES
Dataset name containing the custom style sheet.
DEFAULT
VALUES
datasetParmDefIntRevision
SCOPE
Site preference.
datasetParmDefIntRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmdefIntRevision properties style sheet can be
applied.
VALID
VALUES
DEFAULT
VALUES
ParmDefIntRevision
SCOPE
Site preference.

ParmDefDblRevision.RENDERING
DESCRIPTION
Sets the rendering component for ParmDefDblRevision business object and all its
VALID
VALUES
DEFAULT
VALUES
datasetParmDefDblRevision
SCOPE
Site preference.
datasetParmDefDblRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmDefDblRevision properties style sheet can
be applied.
VALID
VALUES
DEFAULT
VALUES
ParmDefDblRevision
SCOPE
Site preference.
ParmDefStrRevision.RENDERING
DESCRIPTION
Sets the rendering component for ParmDefStrRevision business object and all of
VALID
VALUES
DEFAULT
VALUES
datasetParmDefStrRevision
SCOPE
Site preference.

datasetParmDefStrRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmDefStrRevision properties style sheet can be
applied.
VALID
VALUES
DEFAULT
VALUES
ParmDefStrRevision
SCOPE
Site preference.
ParmDefBoolRevision.RENDERING
DESCRIPTION
Sets the rendering component for ParmDefBoolRevision business object and all
its children. The value of this preference is a dataset name that contains the XML
style sheet used for rendering the components of this type.
VALID
VALUES
DEFAULT
VALUES
datasetParmDefBoolRevision
SCOPE
Site preference.
datasetParmDefBoolRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmDefBoolRevision properties style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ParmDefBoolRevision
SCOPE
Site preference.

ParmDefDateRevision.RENDERING
DESCRIPTION
Sets the rendering component for ParmDefDateRevision business object and all
VALID
VALUES
DEFAULT
VALUES
datasetParmDefDateRevision
SCOPE
Site preference.
datasetParmDefDateRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmDefDateRevision properties style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ParmDefDateRevision
SCOPE
Site preference.
ParmDefHexRevision.RENDERING
DESCRIPTION
Sets the rendering component for ParmDefHexRevision business object and all its
VALID
VALUES
DEFAULT
VALUES
datasetParmDefHexRevision
SCOPE
Site preference.

datasetParmDefHexRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which theParmDefHexRevision properties style sheet can
be applied.
VALID
VALUES
DEFAULT
VALUES
ParmDefHexRevision
SCOPE
Site preference.
ParmDefSEDRevision.RENDERING
DESCRIPTION
Sets the rendering component for ParmDefSEDRevision business object and all its
VALID
VALUES
DEFAULT
VALUES
datasetParmDefSEDRevision
SCOPE
Site preference.
datasetParmDefSEDRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmDefSEDRevision properties style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ParmDefSEDRevision
SCOPE
Site preference.

ParmDefBCDRevision.RENDERING
DESCRIPTION
Sets the rendering component for ParmDefBCDRevision business object and all
VALID
VALUES
DEFAULT
VALUES
datasetParmDefBCDRevision
SCOPE
Site preference.
datasetParmDefBCDRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmDefBCDRevision properties style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ParmDefBCDRevision
SCOPE
Site preference.
ParmGrpValRevision.RENDERING
DESCRIPTION
Sets the rendering component for ParmDefGrpValRevision business object and all
VALID
VALUES
DEFAULT
VALUES
datasetParmGrpValRevision
SCOPE
Site preference.

datasetParmGrpValRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmGrpValRevision properties style sheet can
be applied.
VALID
VALUES
DEFAULT
VALUES
ParmGrpValRevision
SCOPE
Site preference.
ParmDefBitDefRevision.RENDERING
DESCRIPTION
Sets the rendering component for ParmDefBitDefRevision business object and all
VALID
VALUES
DEFAULT
VALUES
datasetParmDefBitDefRevision
SCOPE
Site preference.
datasetParmDefBitDefRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmDefBitDefRevision properties style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ParmDefBitDefRevision
SCOPE
Site preference.

ParmGrpDef.RENDERING
DESCRIPTION
Sets the rendering component for ParmGrpDef business object and all its children.
The value of this preference is a dataset name that contains the XML style sheet
used for rendering the components of this type.
VALID
VALUES
DEFAULT
VALUES
datasetParmGrpDef
SCOPE
Site preference.
datasetParmGrpDef.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmGrpDef properties style sheet can be applied.
VALID
VALUES
DEFAULT
VALUES
ParmGrpDef
SCOPE
Site preference.
ParmDef.RENDERING
DESCRIPTION
Sets the rendering component for ParmDef business object and all its children. The
value of this preference is a dataset name that contains the XML style sheet used for
rendering the components of this type.
VALID
VALUES
DEFAULT
VALUES
datasetParmDef
SCOPE
Site preference.

datasetParmDef.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmDef properties style sheet can be applied.
VALID
VALUES
DEFAULT
VALUES
ParmDef
SCOPE
Site preference.
ParmGrpDefRevision.RENDERING
DESCRIPTION
Sets the rendering component for GrpDefRevision business object and all its
VALID
VALUES
DEFAULT
VALUES
datasetParmGrpDefRevision
SCOPE
Site preference.
datasetParmGrpDefRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ParmGrpDefRevision properties style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ParmGrpDefRevision
SCOPE
Site preference.

ProductVariant.RENDERING
DESCRIPTION
Sets the rendering component for ProductVariant business object and all its
VALID
VALUES
DEFAULT
VALUES
datasetProductVariant
SCOPE
Site preference.
datasetProductVariant.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ProductVariant properties style sheet can be
applied.
VALID
VALUES
DEFAULT
VALUES
ProductVariant
SCOPE
Site preference.
ProductVariant.CREATERENDERING
DESCRIPTION
Registers the create stylesheet for ProductVariant objects.
VALID
VALUES
DEFAULT
VALUES
datasetProductVariantCreate
SCOPE
Site preference.

datasetProductVariantCreate.REGISTEREDTO
DESCRIPTION
Indicates the types to which the ProductVariantCreate properties style sheet
can be applied.
VALID
VALUES
DEFAULT
VALUES
ProductVariant
SCOPE
Site preference.
ProductVariantIntent.RENDERING
DESCRIPTION
Sets the rendering component for the ProductVariantIntent business object and
all its children. The value of this preference is a dataset name that contains the
XML style sheet used for rendering the components of this type.
VALID
VALUES
DEFAULT
VALUES
datasetProductVariantIntent
SCOPE
Site preference.
datasetProductVariantIntent.REGISTEREDTO
DESCRIPTION
Sets the rendering component for ProductVariantIntent business object and all its
VALID
VALUES
DEFAULT
VALUES
ProductVariantIntent
SCOPE
Site preference.

ProductVariantIntent.CREATERENDERING
DESCRIPTION
Registers the create stylesheet for ProductVariantIntent objects.
VALID
VALUES
DEFAULT
VALUES
datasetProductVariantIntent
SCOPE
Site preference.
datasetProductVariantIntentCreate.REGISTEREDTO
DESCRIPTION
Sets the rendering component for ProductVariantIntentCreate business object
and all its children. The value of this preference is a dataset name that contains the
XML style sheet used for rendering the components of this type.
VALID
VALUES
DEFAULT
VALUES
ProductVariantIntent
SCOPE
Site preference.
Ccd0ColumnPreference
DESCRIPTION
Lists the names of the attributes which needs to be shown in the Group Value
Parameter table in addition to the ones already displayed by default. By default, the
following attributes are displayed in the table:
object_name
object_type
minValues
maxValues
intialvalues
To add attributes in addition to the default attributes, the attribute names need to
be specified as value of this preference. For example:
size
sizeUnits

Refer to the data model to know what attributes of ParmDefRevision or its

subclass can be used to specify as values for this preference.
VALID
VALUES
object_name
object_type
minValues
maxValues
intialvalues
size
sizeUnits
comments
Other custom attributes.

DEFAULT
VALUES
To be filled by users. It should be the property names of the
ParmDefGrpValRevision business object.
SCOPE
CCDM_grp_rev_val
DESCRIPTION
Adds parameter group type entries to this preference if you want to restrict adding
any group value to specific types of group. This preference is not created in COTS.
You need to create this preference if you want this functionality.
VALID
VALUES
Organization group
Packetted group
Parameter breakdown
Parameter group
Parameter dictionary
Any other custom group type
DEFAULT
VALUES
To be created and filled by users. Valid group type represents attribute of the
ParmDefGrpRevision business object.
SCOPE
Site preference.
HRN_wire_length_data_relation_primary
DESCRIPTION
Some occurrences in the HRN model may have a wire length type and wire length
value associated with them. More than one wire length object may be associated
to these occurrences. This preference determines the primary object types whose

occurrences can participate in the HRN_wire_length_data relation that associates

the primary object with a wire length object.
VALID
VALUES
Do not delete this preference.
DEFAULT
VALUES
HRN_Core
HRN_GeneralWire
SCOPE
Site preference.
HRN_associated_part_relation_secondary
DESCRIPTION
A cavity in a harness assembly may be associated with occurrences that fill
the cavity space. These occurrences are associated to the cavity with the
HRN_associated_part relation. This preference determines the KBL types whose
occurrences can be associated with the cavity in a harness assembly.
KBL (KabelBaumListe – wire harness description list) is a standard for wiring
models that enhances the STEP AP212 model. The KBL object model provides
high-level components that represent wires, harnesses, and parts in a vehicle that
hosts the harness. This model is a subset of AP212 model and models represent wire
harness data in a similar way. If KBL functionality has been installed, the following
KBL type names must be defined.
VALID
VALUES
DEFAULT
VALUES
HRN_CavityPlug
HRN_CavitySeal
HRN_GenTerminal
SCOPE
Site preference.
HRN_node_referenced_component_relation_secondary
DESCRIPTION
A node object may have referenced components located at the node. These referenced
components are occurrences that are associated with the node object by the

HRN_node_referenced_component relation. This preference determines the

permitted secondary object types whose occurrences can be attached to the node as
referenced components.
VALID
VALUES
DEFAULT
VALUES
HRN_Accessory
HRN_Fixing
HRN_AssemblyPart
HRN_ConHousing
HRN_GenTerminal
HRN_WireProtect
SCOPE
Site preference.
HRN_part_data_relation_primary
DESCRIPTION
Some occurrences in a harness assembly may have instance data set on them,
for example, id and alias_id. This data is attached to the instance with the
HRN_part_instance_data relation. This preference determines the object types
whose occurrences can participate as primary types in the association with instance
data.
VALID
VALUES
DEFAULT
VALUES
HRN_Accessory
HRN_AssemblyPart
HRN_GenTerminal
HRN_Fixing
HRN_CoPackPart
SCOPE
Site preference.

HRN_fixing_assignment_relation_primary
DESCRIPTION
A fixing occurrence or an accessory occurrence may be associated with a segment
object as a fixing assignment. This preference determines the permitted object
types whose occurrences may be associated with the segment object by the
HRN_fixing_assignment relation.
VALID
VALUES
DEFAULT
VALUES
HRN_Accessory
HRN_Fixing
SCOPE
Site preference.
SIG_asystem_source_rules
DESCRIPTION
Defines which Teamcenter types and/or classes can be associated with a frame or
a signal as a source system. When a class is specified, subtypes are included. If
this preference is not set, users can associate a frame or signal to any Teamcenter
object that can participate in a relation.
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter class or
type. Values are set in the following format:
frame or signal: class or type
For example:
Frame:Item
Signal:Interfaces
DEFAULT
VALUES
Frame:Item
Signal:Interfaces
SCOPE
Site preference.

SIG_asystem_target_rules
DESCRIPTION
Defines which Teamcenter types can be associated with the signal as a target
system. If this preference is not set, users can associate a signal to any Teamcenter
VALID
VALUES
Accepts multiple strings as values. Each string must be a valid Teamcenter type
corresponding to the secondary object for the desired association. For example, to
restrict valid targets for a frame to item and its subtypes, and for the signal to
Interfaces and its subtypes, set the values as:
Frame:Item
Signal:Interfaces
DEFAULT
VALUES
Frame:Item
Signal:Interfaces
SCOPE
Site preference.
SIG_asystem_transmitter_rules
DESCRIPTION
Defines which Teamcenter types can be associated with the signal as a transmitter
system. If this preference is not set, users can associate a signal to any Teamcenter
VALID
VALUES
restrict valid transmitters for a PSSignal subtype or subclass to PSConnection
and its subtypes, set the values as:
PSSignal:Connection
DEFAULT
VALUES
PSSignal:PSConnection
SCOPE
Site preference.

SIG_pvariable_rules
DESCRIPTION
Defines which Teamcenter types can be associated with the signal as a process
variable. If this preference is not set, users can associate a signal to any Teamcenter
VALID
VALUES
restrict valid process variables for a signal or subtype to ProcessVariable and
its subtypes, set the values as:
Signal:ProcessVariable
DEFAULT
VALUES
Signal:ProcessVariable
SCOPE
Site preference.
SIG_redundant_rules
DESCRIPTION
Defines which Teamcenter types can be associated with the signal as a redundant
signals (or frames) type. If this preference is not set, users can associate a signal to
any Teamcenter object that can participate in a relation.
VALID
VALUES
restrict valid redundants for a frame and its subtypes to Frame and its subtypes,
and valid redundants for a signal and its subtypes to Signal and its subtypes, set
the values as:
Frame:Frame
Signal:Signal
DEFAULT
VALUES
Frame:Frame
Signal:Signal
SCOPE
Site preference.

Vendor management preferences

Teamcenter vendor management lets you model vendor contributions to a product by
letting you capture information about the vendors and the vendor parts they provide
to satisfy the form, fit, and function of commercial parts.
Use these preferences to determine such behavior as how item revisions are revised
and what types of relations are created.
BidPackageLineItem_default_relation
DESCRIPTION
Specifies the object default paste relation.
VALID
VALUES
Accepts a single string value; it must be a valid type name.
DEFAULT
VALUES
TC_part_quote_rel
SCOPE
Site preference.
BidPackageLineItem_DefaultChildProperties
DESCRIPTION
Specifies the list of properties that can be displayed as children of bid package line
items.
VALID
VALUES
Accepts one or more strings as values; each must be a valid property name.
DEFAULT
VALUES
TC_part_quote_rel
SCOPE
Site preference.
BidPackageLineItem_PseudoFolder
DESCRIPTION
Specifies the list of properties that can be displayed as a pseudo folder under a
node for BidPackageLineItem objects.
Note
Modify to apply a style sheet to a new type.
VALID
VALUES

DEFAULT
VALUES
TC_part_quote_rel
SCOPE
Site preference.
BidPackageRevision_DefaultChildProperties
DESCRIPTION
Specifies the list of properties that can be displayed as children of the BidPackage
revision node.
VALID
VALUES
DEFAULT
VALUES
bom_view_tags
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEView
IMAN_vi_sos
IMAN_specification
TC_WorkContext_Relation
TC_AuditLog
lineitems
SCOPE
Site preference.
BidPackageRevision_PseudoFolder
DESCRIPTION
Specifies the list of properties that can be displayed as a pseudo folder under a node
for the BidPackageRevision object.
VALID
VALUES
DEFAULT
VALUES
lineitems
SCOPE
Site preference.

CommercialPart_DefaultChildProperties
DESCRIPTION
Enables the viewing of the specified relation types for commercial parts.
VALID
VALUES
DEFAULT
VALUES
IMAN_master_form
bom_view_tags
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEView
IMAN_vi_sos
TC_AuditLog
vendors
vendorparts
SCOPE
All.
CommercialPart_PseudoFolder
DESCRIPTION
Specifies the list of properties that can be displayed as a pseudo folder under a node
for a CommercialPart object.
Note
The preference must be enabled to let the user view and manage the dataset
associated with a commercial part.
VALID
VALUES
DEFAULT
VALUES
vendors
vendorparts
SCOPE
All.

CompanyLocation_DefaultChildProperties
DESCRIPTION
Enables viewing of specified relation types for vendor parts.
VALID
VALUES
Accepts one or more strings as values; each string must be a VendorLocation
property.
DEFAULT
VALUES
ContactInCompany
SCOPE
All.
CompanyLocation_PseudoFolder
DESCRIPTION
Specifies the list of properties displayed as a pseudo folder under a node for a
CompanyLocation object.
VALID
VALUES
Accepts one or more strings as values; each string must be a VendorLocation
property.
DEFAULT
VALUES
ContactInCompany
SCOPE
Site preference.
ContactInCompany_relation_primary
DESCRIPTION
Enables the ContactInCompany relation for the specified business objects.
VALID
VALUES
Accepts one or more strings as values, each string must be a valid type.
DEFAULT
VALUES
Item
ItemRevision
CompanyLocation
SCOPE
All.

LocationInCompany_relation_primary
DESCRIPTION
Enables the LocationInCompany relation for the specified business objects.
VALID
VALUES
Accepts one or more strings as values, each string must be any type.
DEFAULT
VALUES
Item
ItemRevision
SCOPE
All.
ManufacturerPart_DefaultChildProperties
DESCRIPTION
Enables viewing of specified relation types for vendor parts.
VALID
VALUES
Accepts one or more strings as values; each string must be a property of
ManufacturerPart.
DEFAULT
VALUES
IMAN_master_form
bom_view_tags
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEView
IMAN_vi_sos
TC_AuditLog
vendors
commercialparts
TC_Quality_Document
ProvidedFrom
SCOPE
All.

ManufacturerPart_DefaultPSEProperties
DESCRIPTION
Enables viewing of the related properties for vendor parts in Structure Manager.
VALID
VALUES
ManufacturerPart or a property of the VMRepresents relation.
DEFAULT
VALUES
item_id
vendor_part_num
object_name
vendor_id
vendor_name
TC_Location
preferred_status
SCOPE
Site preference.
ManufacturerPart_PseudoFolder
DESCRIPTION
node for ManufacturerPart objects.
VALID
VALUES
ManufacturerPart.
DEFAULT
VALUES
vendors
commercialparts
TC_Quality_Document
ProvidedFrom
SCOPE
All.
ManufacturerPartRevision.REGISTEREDTO
DESCRIPTION
Indicates the types to which the vendor part revision properties style sheet can be
applied.
Note

VALID
VALUES
DEFAULT
VALUES
SCOPE
Site preference.
ManufacturerPart Revision.RENDERING
DESCRIPTION
Registers the properties style sheet for vendor part revision objects.
Note
Modify to use a new style sheet.
VALID
VALUES
Accepts one string as a value; it must be a valid dataset name.
DEFAULT
VALUES
ManufacturerPartRevision
SCOPE
Site preference.
ManufacturerPart Revision.SUMMARYRENDERING
DESCRIPTION
Registers the summary styles sheet for vendor part revision objects.
VALID
VALUES
DEFAULT
VALUES
ManufacturerPartRevSummary
SCOPE
Site preference.
ManufacturerPartRevSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the types to which the vendor part revision summary style sheet can be
applied.

Note
VALID
VALUES
DEFAULT
VALUES
SCOPE
Site preference.
ManufacturerPart.REGISTEREDTO
DESCRIPTION
Indicates the types to which the vendor part properties style sheet can be applied.
VALID
VALUES
DEFAULT
VALUES
ManufacturerPart
SCOPE
Site preference.
ManufacturerPart.RENDERING
DESCRIPTION
Registers the properties style sheet for vendor part objects.
Note
VALID
VALUES
DEFAULT
VALUES
ManufacturerPart
SCOPE
Site preference.
ManufacturerPart.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for vendor part objects.

Note
VALID
VALUES
DEFAULT
VALUES
ManufacturerPartSummary
SCOPE
Site preference.
ManufacturerPartSummary.SUMMARY_REGISTEREDTO
DESCRIPTION
Indicates the types to which the vendor part summary style sheet can be applied.
Note
VALID
VALUES
DEFAULT
VALUES
ManufacturerPart
SCOPE
Site preference.
ProvidedFrom_relation_primary
DESCRIPTION
Enables the ProvdedFrom relation for the specified business objects.
VALID
VALUES
Accepts one or more strings as values; each string must be a valid type.
DEFAULT
VALUES
ManufacturerPart
SCOPE
All.

PseudoFolder.ContactInCompany_ColumnPreferences
DESCRIPTION
Specifies the list of properties that can be displayed when a ContactInCompany
pseudo folder is selected in the Details view.
VALID
VALUES
Accepts one or more strings as values; each string must be a valid property name.
DEFAULT
VALUES
CompanyContact.object_string
CompanyContact.title
CompanyContact.first_name
CompanyContact.last_name
CompanyContact.phone_business
CompanyContact.fax_number
CompanyContact.email_address
SCOPE
Site preference.
PseudoFolder.lineitems_ColumnPreferences
DESCRIPTION
Specifies the list of properties that can be displayed when the BidpackageLineItems
VALID
VALUES
Accepts one or more strings as values; each must be a valid type.property name.
DEFAULT
VALUES
PseudoFolder.object_string
BidPackageLineItem.object_type
BidPackageLineItem.quantity
BidPackageLineItem.cust_line_item_attrs
BidPackageLineItem.configuration_context
BidPackageLineItem.part
SCOPE
Site preference.
PseudoFolder.LocationInCompany_ColumnPreferences
DESCRIPTION
Specifies the list of properties that can be displayed when a LocationInCompany
VALID
VALUES

DEFAULT
VALUES
CompanyLocation.object_string
CompanyLocation.street
CompanyLocation.city
CompanyLocation.state_province
CompanyLocation.postal_code
CompanyLocation.country
SCOPE
Site preference.
PseudoFolder.ProvidedFrom_ColumnPreferences
DESCRIPTION
Specifies the list of properties that can be displayed when a ProvidedFrom pseudo
folder is selected in the Details view.
VALID
VALUES
DEFAULT
VALUES
CompanyLocation.object_string
CompanyLocation.street
CompanyLocation.city
CompanyLocation.state_province
CompanyLocation.postal_code
CompanyLocation.country
SCOPE
Site preference.
PseudoFolder.TC_part_quote_rel_ColumnPreferences
DESCRIPTION
Specifies the list of properties that can be displayed when a Quotes pseudo folder
is selected in the Details view.
VALID
VALUES
DEFAULT
VALUES
PseudoFolder.object_string
Quote.object_type
Quote.currency
Quote.quoted_quantity
Quote.tooling_cost
Quote.vendor
Quote.unit_price
relation

SCOPE
Site preference.
Quote_DefaultChildProperties
DESCRIPTION
Specifies the list of properties that can be displayed as children of quotes.
VALID
VALUES
DEFAULT
VALUES
vendor
SCOPE
Site preference.
Restricted_Vendor_Part_Statuses
DESCRIPTION
Defines the list of restricted vendor part revision release statuses with which users
cannot associate commercial part/revisions with vendor parts.
VALID
VALUES
Accepts one or more strings as values; each string must be a status type.
DEFAULT
VALUES
Obsolete
SCOPE
Site preference.
Restricted_Vendor_Statuses
DESCRIPTION
Defines the list of restricted vendor release statuses with which users cannot
associate vendor parts with vendors.
VALID
VALUES
Accepts one or more strings as values; each string must be a status type.
DEFAULT
VALUES
Obsolete
SCOPE
Site preference.

TC_Distributor_info_form
DESCRIPTION
Specifies the Distributor role default form type.
VALID
VALUES
Accepts a single string value; it must be a valid form type name.
DEFAULT
VALUES
DistributorInfo
SCOPE
Site preference.
TC_Manufacturer_info_form
DESCRIPTION
Specifies the Manufacturer role default form type.
VALID
VALUES
DEFAULT
VALUES
ManufacturerInfo
SCOPE
Site preference.
TC_part_quote_rel_relation_primary
DESCRIPTION
Specifies the primary type for the TC_part_quote_rel relation.
VALID
VALUES
DEFAULT
VALUES
BidPackageLineItem
SCOPE
Site preference.
TC_Quality_Document_relation_primary
DESCRIPTION
Enables the TC_Quality_Document relation for the specified business objects.

VALID
VALUES
Accepts one or more strings as values; each string must be a valid type.
DEFAULT
VALUES
Vendor
VendorRevision
ManufacturerPart
SCOPE
All.
TC_Supplier_info_form
DESCRIPTION
Specifies the Supplier role default form type.
VALID
VALUES
DEFAULT
VALUES
SupplierInfo
SCOPE
Site preference.
TC_vendor_part_rel_relation_primary
DESCRIPTION
Indicates the list of valid primary object types for the TC_vendor_part_rel relation.
VALID
VALUES
DEFAULT
VALUES
Item
SCOPE
Site preference.
Vendor_DefaultChildProperties
DESCRIPTION
Enables viewing of the specified relation types for vendors.
VALID
VALUES
Accepts one or more strings as values; each string must be a property of Vendor.

DEFAULT
VALUES
IMAN_master_form
bom_view_tags
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEView
IMAN_vi_sos
TC_AuditLog
vendorparts
commercialparts
LocationInCompany
ContactInCompany
TC_Quality_Document
SCOPE
All.
Vendor_PseudoFolder
DESCRIPTION
node for a Vendor object.
VALID
VALUES
Accepts one or more strings as values; each string must be a property of Vendor.
DEFAULT
VALUES
vendorparts
commercialparts
LocationInCompany
ContactInCompany
TC_Quality_Document
SCOPE
All.
VendorRevision_DefaultChildProperties
DESCRIPTION
Enables viewing of specified relation types for vendor revisions.
VALID
VALUES
VendorRevision.

DEFAULT
VALUES
bom_view_tags
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEView
IMAN_vi_sos
IMAN_specification
TC_AuditLog
release_status_list
LocationInCompany
ContactInCompany
TC_Quality_Document
vendor_role_info
SCOPE
All.
VendorRevision_PseudoFolder
DESCRIPTION
node for VendorRevision objects.
VALID
VALUES
VendorRevision.
DEFAULT
VALUES
LocationInCompany
ContactInCompany
TC_Quality_Document
CAEAnalysis
MEProcess
MESetup
view
interpart_equations
mating_constraints
geometric_interfaces
interpart_links
parametric_interfaces
SCOPE
All.

VMRepresents_relation_primary
DESCRIPTION
Indicates the list of valid primary object types for the VMRepresents relation.
VALID
VALUES
DEFAULT
VALUES
Item
ItemRevision
SCOPE
Site preference.
VMS_Maintain_Vendor_History
DESCRIPTION
Controls whether the system moves or copies data during change vendor operations.
VALID
VALUES
TRUE If the preference is set to TRUE, the system copies the vendor
data.
FALSE If the preference is set to FALSE, the system moves the
vendor data.
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
VMS_vendor_part_selection_rule
DESCRIPTION
Stores the active condition name corresponding to current vendor part selection rule.
VALID
VALUES
Accepts one or more strings as values; each string must be a valid condition.
DEFAULT
VALUES
showAllVendorParts
SCOPE
• Site preference.
• User preference.

MRO core preferences

Maintenance, Repair, and Overhaul (MRO) preferences are available with MRO
solutions as part of the mrocore template. Use these preferences to configure and
modify the behavior of MRO solutions.
HierarchicalWSO_HierarchicalWSO_default_relation
DESCRIPTION
Specifies the default relation between two hierarchical workspace objects.
VALID
VALUES
Accepts one or more strings as a value. Each string must be a valid Teamcenter
object.
DEFAULT
VALUES
HWSOStructure
SCOPE
Site preference.
Item_CharacteristicDefinition_default_relation
DESCRIPTION
Specifies the default relation created when a characteristics definition object is
pasted under an item object.
VALID
VALUES
object.
DEFAULT
VALUES
NeutralCharacteristics
SCOPE
Site preference.
ItemRevision_CharacteristicDefinition_default_relation
DESCRIPTION
Specifies the default relation created when a characteristics definition object is
pasted under an item revision object. The default value for this preference is
InvalidRelation to disallow creating a relation between an item revision object
and a characteristics definition object.
VALID
VALUES
object.

DEFAULT
VALUES
InvalidRelation
SCOPE
Site preference.
LogBook_PhysicalPart_default_relation
DESCRIPTION
Defines the default relationship between a log book and a physical part.
VALID
VALUES
object.
DEFAULT
VALUES
physicalAssetTag
SCOPE
Site preference.
LogBook_WorkspaceObject_default_relation
DESCRIPTION
Defines the default relationship created when workspace object is pasted under a
log book. The default value of this preference is InvalidRelation to disallow the
creation of any relation with a log book.
VALID
VALUES
object.
DEFAULT
VALUES
InvalidRelation
SCOPE
Site preference.
Lot.SUMMARYRENDERING
DESCRIPTION
Specifies the lot objects summary stylesheet registry.
VALID
VALUES
Accepts a single string as a value, which must be a valid dataset name.
DEFAULT
VALUES
LotSummary

SCOPE
Site preference.
Lot_DefaultChildProperties
DESCRIPTION
Specifies a list of properties that can be used for Lot children.
VALID
VALUES
Accepts one or more stings as values. Each string must be a valid Teamcenter
relation object.
DEFAULT
VALUES
designItemTag
SCOPE
Site preference.
MRONeutralColumnsShownPref
DESCRIPTION
Specifies the columns displayed in the MRO neutral item structure table.
VALID
VALUES
Accepts one or more stings as values. Each string must be a valid neutral BOM
line property.
DEFAULT
VALUES
bl_indented_title
bl_item_object_type
bl_occurrence_name
bl_quantity
bl_uom
npbl_is_item_serialized
npbl_is_item_lot
npbl_is_item_traceable
npbl_preserve_quantity
npbl_is_item_rotable
npbl_is_item_consumable
SCOPE
Site preference.
MRONeutralShownColumnWidthsPref
DESCRIPTION
Specifies the column widths displayed in the MRO neutral item structure table.

VALID
VALUES
in the MRONeutralColumnsShownPref user preference, and so forth.
DEFAULT
VALUES
20
15
12
10
10
10
10
10
10
10
10
SCOPE
Site preference.
ManufacturingIdCharsForPhysicalPartIdPref
DESCRIPTION
Specifies the number of characters to use from the manufacturing ID when
generating the physical part item ID. The physical part item ID is a combination
of characters from part number, serial number, and manufacturing ID properties.
The total number of characters for the physical part item ID should not exceed 128
characters. The first entry in the preference is the number of characters to use from
the manufacturing ID property for the physical part item ID. The second entry in
the preference indicates whether to use the characters from the beginning of the
manufacturing ID (a value of 0) or from the end of the part number (a value of 1).
If this preference is not found, the last 40 characters of the manufacturing ID are
used.
VALID
VALUES
Any positive integers.
DEFAULT
VALUES
40
1
SCOPE
Site preference.
MROAlternateColorPref
DESCRIPTION
Specifies the color to use when displaying an alternate physical part.

VALID
VALUES
The value can be a standard supported string, an octal number, or a hexadecimal
number. The standard strings supported are black, white, lightGray, gray,
darkGray, red, pink, orange, yellow, green, magenta, cyan, and blue. An
example of a hexadecimal number is #50b080, which represents sea green.
DEFAULT
VALUES
cyan
SCOPE
Site preference.
MRODeviatedColorPref
DESCRIPTION
Specifies the color to use when displaying a deviated physical part.
VALID
VALUES
DEFAULT
VALUES
yellow
SCOPE
Site preference.
MROExtraToDesignColorPref
DESCRIPTION
Specifies the color to use when displaying a physical part that is extra to design.
VALID
VALUES
DEFAULT
VALUES
orange
SCOPE
Site preference.

MROMissingColorPref
DESCRIPTION
Specifies the color to use when displaying a missing physical part.
VALID
VALUES
DEFAULT
VALUES
red
SCOPE
Site preference.
MROSubstituteColorPref
DESCRIPTION
Specifies the color to use when displaying a substitute physical part.
VALID
VALUES
DEFAULT
VALUES
blue
SCOPE
Site preference.
PartLogisticsForm.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for part logistics form objects.
VALID
VALUES
Accepts a string as a value. Each string must be a valid style sheet dataset object
name.
DEFAULT
VALUES
PartLogisticsFormSummary
SCOPE
Site preference.

PartNumberCharsForPhysicalPartIdPref
DESCRIPTION
Specifies the number of characters to use from the part number when generating the
physical part item ID. The physical part item ID is a combination of characters from
part number, serial number, and manufacturing ID properties. The total number
of characters for the physical part item ID should not exceed 128 characters. The
first entry in the preference is the number of characters to use from the part number
property for the physical part item ID. The second entry in the preference indicates
whether to use the characters from the beginning of the part number (a value of 0) or
from the end of the part number (a value of 1).
If this preference is not found, the last 40 characters of the part number are used.
VALID
VALUES
DEFAULT
VALUES
40
1
SCOPE
Site preference.
PhysicalContext_relation_primary
DESCRIPTION
Specifies the valid primary object types list for the physical context relation.
VALID
VALUES
Accepts one or more stings as values. Each string must be a valid Teamcenter object.
DEFAULT
VALUES
PhysicalPartRevision
SCOPE
Site preference.
PhysicalElement_Company_default_relation
DESCRIPTION
Defines the default relationship created when company object is pasted under a
physical element class object.
VALID
VALUES
object.

DEFAULT
VALUES
PhysicalElementOwner
SCOPE
Site preference.
PhysicalPart_Company_default_relation
DESCRIPTION
Defines the default relationship created when company object is pasted under a
physical part.
VALID
VALUES
object.
DEFAULT
VALUES
PhysicalPartManufacturer
SCOPE
Site preference.
PhysicalPart_DefaultChildProperties
DESCRIPTION
Defines the list of properties that can be displayed as children of a physical part.
VALID
VALUES
property name.
DEFAULT
VALUES
AllowedDeviation
IMAN_master_form
bom_view_tags
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEView
IMAN_vi_sos
PhysicalPartManufacturer
TC_AuditLog
TC_sst_record
SCOPE
Site preference.

PhysicalPartRelationsToExport
DESCRIPTION
Defines the relations that are exported with a physical part when the physical part
is secondary in the relation.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid relation class
name.
DEFAULT
VALUES
Values are added by dependent templates.
The asmaintained template adds the following value:
AssetContains
SCOPE
Site preference.
PhysicalPart.SUMMARYRENDERING
DESCRIPTION
Determines the registration for the physical part object’s summary style sheet.
VALID
VALUES
DEFAULT
VALUES
PhysicalPartSummary
SCOPE
Site preference.
PhysicalPartRevision_DefaultChildProperties
DESCRIPTION
Determines the properties that can be used as children for the indicated type.
VALID
VALUES
relation object.
DEFAULT
VALUES
PhysicalContext
PhysicalRealization
SCOPE
Site preference.

PhysicalPartRevision.SUMMARYRENDERING
DESCRIPTION
Registers the physical part revision object’s summary stylesheet.
VALID
VALUES
DEFAULT
VALUES
PhysicalPartRevisionSummary
SCOPE
Site preference.
PhysicalRealization_relation_primary
DESCRIPTION
Specifies the valid primary object types list for the physical realization relation.
VALID
VALUES
Accepts one or more stings as values. Each string must be a valid Teamcenter object.
DEFAULT
VALUES
PhysicalPartRevision
SCOPE
Site preference.
SerialNumberCharsForPhysicalPartIdPref
DESCRIPTION
Specifies the number of characters to use from the serial number when generating
the physical part item ID. The physical part item ID is a combination of characters
from part number, serial number, and manufacturing ID properties. The total
number of characters for the physical part item ID should not exceed 128 characters.
The first entry in the preference is the number of characters to use from the serial
number property for the physical part item ID. The second entry in the preference
indicates whether to use the characters from the beginning of the part number (a
value of 0) or from the end of the serial number (a value of 1).
If this preference is not found, the last 40 characters of the serial number are used.
VALID
VALUES
DEFAULT
VALUES
40
1

SCOPE
Site preference.
SerialNumberGenerator_DefaultChildProperties
DESCRIPTION
Specifies the properties list that can be used as children for the indicated type.
VALID
VALUES
relation object.
DEFAULT
VALUES
designItemTag
SCOPE
Site preference.
SerialNumberGenerator.SUMMARYRENDERING
DESCRIPTION
Registers the serial number generator objects’ summary stylesheet.
VALID
VALUES
DEFAULT
VALUES
SerialNumberGeneratorSummary
SCOPE
Site preference.
UtilizationViewColumnsShownPref
DESCRIPTION
Specifies the columns displayed in the Utilization view in left to right order.
VALID
VALUES
Accepts one or more strings as values. The strings are property names from the
utilization object.
DEFAULT
VALUES
util_characteristic_name
util_unit
util_time_since_new
util_last_value
util_last_recorded_date
The asmaintained template adds the following value:

util_time_on_parent
The serviceeventmanagement template adds the following values:
util_time_since_repair
util_time_since_overhaul
SCOPE
Site preference.
As-Built Manager preferences

As-Built Manager and Maintenance, Repair, and Overhaul (MRO) preferences can
only be used if the MRO template has been purchased and installed. Use these
preference to configure and modify the behavior of the template.
AsBuiltManagerColumnsShownPref
DESCRIPTION
Specifies the columns displayed in the As-Built structure table.
VALID
VALUES
Accepts one or more stings as values. Each string must be a valid BOM line property
and a valid As-Built BOM line property.
DEFAULT
VALUES
bl_indented_title
bl_item_object_type
phbl_part_used_is
phbl_part_usage_name
phnl_serial_number
phbl_lot_number
phbl_part_number
phbl_installation_time
phbl_mfg_date
phbl_mfgr_org_id
phbl_physical_quantitiy
phbl_physical_uid
bl_item_item_id
SCOPE
Site preference.
AsBuiltManagerShownColumnWidthsPref
DESCRIPTION
Specifies the column widths displayed in the As-Built structure table.

VALID
VALUES
in the AsBuiltManagerShownColumnWidthsPref user preference, and so forth.
DEFAULT
VALUES
20
10
10
10
10
10
10
15
15
10
10
15
10
SCOPE
Site preference.
DefaultAsBuiltCompareProperties
DESCRIPTION
Specifies the default As-Built compare properties.
VALID
VALUES
DEFAULT
VALUES
phbl_part_number
SCOPE
Site preference.
AdditionalAsBuiltCompareProperties
DESCRIPTION
Specifies the default As-Built compare properties.
VALID
VALUES

DEFAULT
VALUES
phbl_part_used_is
SCOPE
Site preference.
DefaultAsBuiltAccCheckProperties
DESCRIPTION
Specifies the default As-Built accountability check properties.
VALID
VALUES
DEFAULT
VALUES
phbl_part_number
phbl_part_used_is
SCOPE
Site preference.
AdditionalAsBuiltAccCheckProperties
DESCRIPTION
Specifies the additional As-Built accountability check properties.
VALID
VALUES
DEFAULT
VALUES
SCOPE
Site preference.
Service Manager preferences

Service Manager preferences are available in various template documents that
are installed as part of the Service Manager installation. These preferences have
precedence over Teamcenter preferences. The preferences available with Service
Manager allow you to configure many aspects of the behavior of the application, such
as the way part data is displayed in the rich client and the relationships between
Service Manager objects.
You can access preferences in the Teamcenter interface by choosing Edit→Options to
open the Options dialog box. Click the Index link at the lower left of the Options
dialog box to access all preferences available for your installation of Teamcenter.

Preferences controlling Service Manager are listed in the MRO category. You can
search for preferences, set preference values, create new preferences, and remove
existing preferences.
As-Maintained preferences
As-Maintained preferences are available with Service Manager as part of the
asmaintained template. Use these preference to configure and modify the behavior
of the Service Manager As-Maintained management functionality.
AdditionalAsMaintainedAccCheckProperties
DESCRIPTION
Specifies the additional as-maintained accountability check properties.
VALID
VALUES
and a valid as-maintained BOM line property.
DEFAULT
VALUES
SCOPE
Site preference.
AdditionalAsMaintainedCompareProperties
DESCRIPTION
Specifies the default as-maintained compare properties.
VALID
VALUES
and a valid as-maintained BOM line property.
DEFAULT
VALUES
phbl_part_used_is
SCOPE
Site preference.
DefaultAsMaintainedAccCheckProperties
DESCRIPTION
Specifies the default as-maintained accountability check properties.
VALID
VALUES
Accepts one or more stings as values. Each string must be a valid neutral BOM line
property and a valid as-maintained BOM line property.

DEFAULT
VALUES
phbl_part_number
phbl_part_used_is
SCOPE
Site preference.
DefaultAsMaintainedCompareProperties
DESCRIPTION
Specifies the default as-maintained compare properties.
VALID
VALUES
Accepts one or more stings as values. Each string must be a valid neutral BOM line
property and a valid as-maintained BOM line property.
DEFAULT
VALUES
phbl_part_number
SCOPE
Site preference.
MroConfigRuleName
DESCRIPTION
Specifies the default configuration rule to use when opening as-maintained physical
part revisions. If this rule does not exist, the system defaults to Today Serviceable.
VALID
VALUES
Accepts a string as a value. Each string must be a valid as-maintained revision
rule name.
DEFAULT
VALUES
Today Serviceable
SCOPE
Site preference.
MRODefaultLocations
DESCRIPTION
Specifies the default locations to use for the Generate As-Maintained Structure and
Un-Install Physical Part actions.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid location name
from the physical location object.

DEFAULT
VALUES
None.
SCOPE
Site preference.
PhysicalLocation_CompanyLocation_default_relation
DESCRIPTION
Defines the default relationship between a company location and a physical location.
VALID
VALUES
object.
DEFAULT
VALUES
PhysicalLocationDetails
SCOPE
Site preference.
PhysicalLocationContainsColumnsShownPref
DESCRIPTION
Specifies the columns displayed in the Contains view when the selected component
is a physical location.
VALID
VALUES
Accepts one or more stings as values.
DEFAULT
VALUES
partNumber
serialNumber
lotNumber
manufacturerOrgId
manufacturingDate
SCOPE
Site preference.
PhysicalLocation_DefaultChildProperties
DESCRIPTION
Defines the default child properties for a physical location.
VALID
VALUES
property name.

DEFAULT
VALUES
IMAN_master_form
bom_view_tags
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEView
IMAN_vi_sos
PhysicalLocationDetails
SCOPE
Site preference.
ServiceManagerAssetGroupColumnsShownPref
DESCRIPTION
Specifies the list of columns displayed for an asset group in Service Manager in
left to right order.
VALID
VALUES
Accepts one or more strings as values. Each string must be a valid asset group
property.
DEFAULT
VALUES
object_name
object_desc
SCOPE
Site preference.
ServiceManagerAssetGroupColumnWidthsPref
DESCRIPTION
Specifies the column widths displayed for an asset group in Service Manager in
VALID
VALUES
in the ServiceManagerAssetGroupColumnsShownPref user preference and
so forth.
DEFAULT
VALUES
20
20

SCOPE
Site preference.
ServiceManagerColumnsShownPref
DESCRIPTION
Specifies the columns displayed for physical parts opened in Service Manager in
VALID
VALUES
Accepts one or more stings as values. Each string must be a valid as-maintained
BOM line property.
DEFAULT
VALUES
bl_indented_title
bl_item_object_type
phbl_part_used_is
phnl_serial_number
phbl_lot_number
phbl_part_number
phbl_installation_time
phbl_mfg_date
phbl_mfgr_org_id
phbl_physical_quantity
phbl_physical_uid
bl_item_item_id
SCOPE
Site preference.
ServiceManagerShownColumnWidthsPref
DESCRIPTION
Specifies the column widths displayed for physical parts in Service Manager in
VALID
VALUES
in the ServiceManagerShownColumnWidthsPref user preference and so forth.
DEFAULT
VALUES
20
10
10
10
10
10
10

15
15
10
10
15
10
SCOPE
Site preference.
ServiceManagerPhysicalLocationColumnsShownPref
DESCRIPTION
Specifies the columns displayed for a physical location.
VALID
VALUES
Accepts one or more stings as values. Each string must be a valid as-maintained
BOM line property.
DEFAULT
VALUES
plbl_location_name
plbl_location_description
plbl_location_type
SCOPE
Site preference.
ServiceManagerPhysicalLocationColumnWidthsPref
DESCRIPTION
Specifies the column widths displayed for the physical location in left to right order.
VALID
VALUES
in the ServiceManagerPhysicalLocationColumnWidthsPref user preference
and so forth.
DEFAULT
VALUES
20
20
20
SCOPE
Site preference.
Service event management preferences

Service event management preferences are available with the Service
Event Management extension for Service Manager as part of the
serviceeventmanagement template. Use these preferences to configure and

modify the behavior of the Service Event Management extension for Service
Manager.
ActivityCost.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for activity cost objects.
VALID
VALUES
DEFAULT
VALUES
ActivityCost
SCOPE
Site preference.
ActivityCost.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for activity cost objects.
VALID
VALUES
DEFAULT
VALUES
ActivityCostSummary
SCOPE
Site preference.
ActivityEntryValue.MROCREATERENDERING
DESCRIPTION
Determines the registration of the create style sheet for activity entry value objects.
VALID
VALUES
DEFAULT
VALUES
ActivityEntryValueCreate
SCOPE
Site preference.

ActivityEntryValue.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for activity entry value objects.
VALID
VALUES
DEFAULT
VALUES
ActivityEntryValue
SCOPE
Site preference.
ActivityEntryValue.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for activity entry value
objects.
VALID
VALUES
DEFAULT
VALUES
ActivityEntryValueSummary
SCOPE
Site preference.
FaultCode.MROCREATERENDERING
DESCRIPTION
Determines the registration of the create style sheet for fault code objects.
VALID
VALUES
DEFAULT
VALUES
FaultCodeCreate
SCOPE
Site preference.
FaultCode.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for fault code objects.

VALID
VALUES
DEFAULT
VALUES
FaultCode
SCOPE
Site preference.
FaultCode.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for fault code objects.
VALID
VALUES
DEFAULT
VALUES
FaultCodeSummary
SCOPE
Site preference.
MRODefaultLogBook
DESCRIPTION
Determines the registration of the create style sheet for service discrepancy objects.
VALID
VALUES
DEFAULT
VALUES
ServiceLogBook
SCOPE
Site preference.
PartMovement_DefaultChildProperties
DESCRIPTION
Defines the default child properties for part movement objects.
VALID
VALUES
DEFAULT
VALUES
MovedPart

SCOPE
Site preference.
PartMovement.ENABLE_PROPERTIES_EDIT
DESCRIPTION
Allows edits to the part movement properties. To allow edits, set the value to false.
VALID
VALUES
DEFAULT
VALUES
false
SCOPE
Site preference.
PartMovement.MROCREATERENDERING
DESCRIPTION
Determines the registration of the summary style sheet for part movement objects.
VALID
VALUES
DEFAULT
VALUES
PartMovementCreate
SCOPE
Site preference.
PartMovement.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for part movement objects.
VALID
VALUES
DEFAULT
VALUES
PartMovement
SCOPE
Site preference.

PartMovement.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for part movement objects.
VALID
VALUES
DEFAULT
VALUES
PartMovementSummary
SCOPE
Site preference.
ServiceAction.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for service action objects.
VALID
VALUES
DEFAULT
VALUES
ServiceAction
SCOPE
Site preference.
ServiceAction.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for service action objects.
VALID
VALUES
DEFAULT
VALUES
ServiceActionSummary
SCOPE
Site preference.
ServiceDiscrepancy_DefaultChildProperties
DESCRIPTION
Defines the default child properties for service discrepancy objects.

VALID
VALUES
DEFAULT
VALUES
CorrectiveAction
InProgress
fault_code
SCOPE
Site preference.
ServiceDiscrepancy.ENABLE_PROPERTIES_EDIT
DESCRIPTION
Allows edits to the service discrepancy properties. To allow edits, set the value
to true.
VALID
VALUES
DEFAULT
VALUES
false
SCOPE
Site preference.
ServiceDiscrepancy_FaultCode_default_relation
DESCRIPTION
Defines the relationship between a service discrepancy and a fault code.
VALID
VALUES
DEFAULT
VALUES
fault_code
SCOPE
Site preference.
ServiceDiscrepancy.MROCREATERENDERING
DESCRIPTION
Determines the registration of the create style sheet for service discrepancy objects.
VALID
VALUES

DEFAULT
VALUES
ServiceDiscrepancyCreate
SCOPE
Site preference.
ServiceDiscrepancy.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for service discrepancy objects.
VALID
VALUES
DEFAULT
VALUES
ServiceDiscrepancy
SCOPE
Site preference.
ServiceDiscrepancy_ServiceEvent_default_relation
DESCRIPTION
Defines the relationship between a service discrepancy and a service event.
VALID
VALUES
DEFAULT
VALUES
CorrectiveAction
SCOPE
Site preference.
ServiceDiscrepancy_ServiceGroup_default_relation
DESCRIPTION
Defines the relationship between a service discrepancy and a service group.
VALID
VALUES
DEFAULT
VALUES
InvalidRelation
SCOPE
Site preference.

ServiceDiscrepancy.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for service discrepancy
objects.
VALID
VALUES
DEFAULT
VALUES
ServiceDiscrepancySummary
SCOPE
Site preference.
ServiceEvent_DefaultChildProperties
DESCRIPTION
Defines the default child properties for service event objects.
VALID
VALUES
DEFAULT
VALUES
Completed
InProgress
CorrectiveAction
HMSOStructure
activity_entry_value
SCOPE
Site preference.
ServiceEvent.ENABLE_PROPERTIES_EDIT
DESCRIPTION
Allows edits to the service event properties. To allow edits, set the value to true.
VALID
VALUES
DEFAULT
VALUES
false
SCOPE
Site preference.

ServiceEvent.MROCREATERENDERING
DESCRIPTION
Determines the registration of the create style sheet for service event objects.
VALID
VALUES
DEFAULT
VALUES
ServiceEventCreate
SCOPE
Site preference.
ServiceEvent.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for service event objects.
VALID
VALUES
DEFAULT
VALUES
ServiceEvent
SCOPE
Site preference.
ServiceEvent.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for service event objects.
VALID
VALUES
DEFAULT
VALUES
ServiceEventSummary
SCOPE
Site preference.
ServiceGroup.ENABLE_PROPERTIES_EDIT
DESCRIPTION
Allows edits to the service group properties. To allow edits, set the value to true.

VALID
VALUES
DEFAULT
VALUES
false
SCOPE
Site preference.
ServiceGroup.MROCREATERENDERING
DESCRIPTION
Determines the registration of the create style sheet for service group objects.
VALID
VALUES
DEFAULT
VALUES
ServiceGroupCreate
SCOPE
Site preference.
ServiceGroup.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for service group objects.
VALID
VALUES
DEFAULT
VALUES
ServiceGroup
SCOPE
Site preference.
ServiceGroup.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for service group objects.
VALID
VALUES
DEFAULT
VALUES
ServiceGroupSummary

SCOPE
Site preference.
TransactionElement.COLUMNS_SHOW
DESCRIPTION
Determines which columns are displayed in the transaction element structure in
VALID
VALUES
DEFAULT
VALUES
object_name
transaction_id
SCOPE
Site preference.
TransactionElement.COLUMNS_WIDTH
DESCRIPTION
Determines the widths for the columns displayed in the transaction element
structure in left to right order.
VALID
VALUES
DEFAULT
VALUES
20
20
SCOPE
Site preference.
TransactionElement_DefaultChildProperties
DESCRIPTION
Defines the default child properties for transaction element objects.
VALID
VALUES
DEFAULT
VALUES
InProgress
HWSOStructure
SCOPE
Site preference.

TransactionElement_Document_default_relation
DESCRIPTION
Defines the relationship between a transaction element and a document.
VALID
VALUES
DEFAULT
VALUES
IMAN_reference
SCOPE
Site preference.
TransactionElement_DocumentRevision_default_relation
DESCRIPTION
Defines the relationship between a transaction element and a document revision.
VALID
VALUES
DEFAULT
VALUES
IMAN_reference
SCOPE
Site preference.
TransactionElement_PhysicalElement_default_relation
DESCRIPTION
Defines the relationship between a transaction element and a physical element.
VALID
VALUES
DEFAULT
VALUES
InProgress
SCOPE
Site preference.
TransactionElement_PhysicalElementRevision_default_relation
DESCRIPTION
Defines the relationship between a transaction element and a physical element
revision.

VALID
VALUES
DEFAULT
VALUES
InvalidRelation
SCOPE
Site preference.
Service Request Manager preferences

Service Request Manager extends the Teamcenter product lifecycle management
capability by letting service providers manage and track customer requests
for service from initiation through completion. Use Service Request Manager
preferences to modify the behavior and appearance of the application. You can
modify aspects of the application behavior, such as the child relationships for a
particular Service Request Manager object, or modify the appearance of a particular
Service Request Manager dialog box using XML style sheets.
For information about customizing the displays using XML style sheets, see the Rich
Client Customization Programmer’s Guide.
For more information about Service Request Manager, see the Service Request
Manager Guide.
ActivityCost.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for an activity cost.
VALID
VALUES
DEFAULT
VALUES
ActivityCostCreate
SCOPE
Site preference.
ActivityCost_SRP0RqstActivityRevision.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for an activity cost that is created from a requested
activity.
VALID
VALUES

DEFAULT
VALUES
ActivityCost_SRP0RqstActivityRevisionCreate
SCOPE
Site preference.
ActivityCost_SRP0ServiceOffering.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for an activity cost that is created from a service
offering.
VALID
VALUES
DEFAULT
VALUES
ActivityCost_SRP0ServiceOfferingCreate
SCOPE
Site preference.
ActivityCost_SRP0ServiceRequest.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for an activity cost that is created from a service
request.
VALID
VALUES
DEFAULT
VALUES
ActivityCost_SRP0ServiceRequestCreate
SCOPE
Site preference.
CM_SRP0DgSrvRequestRevision_displayed_pseudofolders
DESCRIPTION
Defines the list of pseudofolders and their corresponding relationships for a
delegated service request revision.
VALID
VALUES
Valid relations that display as pseudofolders for a delegated service request revision.
DEFAULT
VALUES
MROProductFolder/SRP0MROProduct
CMSolutionItems/CMHasSolutionItem

PerformsFolder/SRP0Performs
CustomerContactFolder/SRP0CustomerContact
LocationInCompanyFolder/LocationInCompany
SCOPE
Site preference.
CM_SRP0PrSrvRequestRevision_displayed_pseudofolders
DESCRIPTION
Defines the list of pseudofolders and their corresponding relations for a primary
service request revision.
VALID
VALUES
Valid relations that display as pseudofolders for a primary service request revision.
DEFAULT
VALUES
IncludesActivityFolder/SRP0IncludesActivity
PerformsFolder/SRP0Performs
DelegatesToFolder/SRP0DelgatesTo
CustomerContactFolder/SRP0CustomerContact
LocationInCompanyFolder/LocationInCompany
SCOPE
Site preference.
CM_SRP0RqstActivityRevision_displayed_pseudofolders
DESCRIPTION
Defines the list of pseudofolders and their corresponding relations for a requested
activity revision.
VALID
VALUES
Valid relations that display as pseudofolders for a requested activity revision.
DEFAULT
VALUES
CMImpactedItems/CMHasImpactedItem
CMProblemItems/CMHasProblemItem
ActivityDiscrepancyFolder/SRP0ActivityDiscrepancy
SCOPE
Site preference.

CompanyContact.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for a company contact.
VALID
VALUES
DEFAULT
VALUES
SRP0CompanyContactCreate
SCOPE
Site preference.
CompanyLocation.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for a company location.
VALID
VALUES
DEFAULT
VALUES
SRP0CompanyLocationCreate
SCOPE
Site preference.
SR_CHANGE_HOME_SITE_PREFERENCE
DESCRIPTION
Lists the system-defined saved searches currently located in the Request Home
view. Click the Manage Request Home saved searches button in the Request
Home view to manage the values of this site preference.
VALID
VALUES
The system-defined saved searches currently located in the Request Home view.
DEFAULT
VALUES
My Open Requests/1/My Open
Requests/NO_QUERY_CRITERIA_OR_VALUE,
/NO_QUERY_CRITERIA_OR_VALUE,/NOT_SAVED_SEARCH/
SCOPE
Site preference.

SRP0DgSrvRequest.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for a delegated service request. The summary
VALID
VALUES
DEFAULT
VALUES
SRP0DgSrvRequestSummary
SCOPE
Site preference.
SRP0DgSrvRequestRevision.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for a delegated service request revision.
VALID
VALUES
DEFAULT
VALUES
SRP0DgSrvRequestRevisionCreate
SCOPE
Site preference.
SRP0DgSrvRequestRevision.RENDERING
DESCRIPTION
Registers the viewer style sheet for a delegated service request revision.
VALID
VALUES
DEFAULT
VALUES
SRP0DgSrvRequestRevision
SCOPE
Site preference.

SRP0DgSrvRequestRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for a delegated service request revision. The
VALID
VALUES
DEFAULT
VALUES
SRP0DgSrvRequestRevisionSummary
SCOPE
Site preference.
SRP0DgSrvRequestRevision_DefaultChildProperties
DESCRIPTION
Determines which properties are children of a delegated service request revision.
VALID
VALUES
A valid list of default child properties for a delegated service request revision.
DEFAULT
VALUES
MROProductFolder
CMHasSolutionItem
PerformsFolder
CustomerContactFolder
LocationInCompanyFolder
SCOPE
Site preference.
SRP0PrSrvRequest.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for a primary service request. The summary
VALID
VALUES
DEFAULT
VALUES
SRP0PrSrvRequestSummary
SCOPE
Site preference.

SRP0PrSrvRequestRevision.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for a primary service request revision.
VALID
VALUES
DEFAULT
VALUES
SRP0PrSrvRequestRevisionCreate
SCOPE
Site preference.
SRP0PrSrvRequestRevision.RENDERING
DESCRIPTION
Registers the viewer style sheet for a primary service request revision.
VALID
VALUES
DEFAULT
VALUES
SRP0PrSrvRequestRevision
SCOPE
Site preference.
SRP0PrSrvRequestRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for a primary service request revision. The
VALID
VALUES
DEFAULT
VALUES
SRP0PrSrvRequestRevisionSummary
SCOPE
Site preference.
SRP0PrSrvRequestRevision_DefaultChildProperties
DESCRIPTION
Determines which properties are children of a primary service request revision.

VALID
VALUES
A valid list of default child properties for a primary service request revision.
DEFAULT
VALUES
MROProductFolder
CMHasSolutionItem
IncludesActivityFolder
PerformsFolder
DelegatesToFolder
CustomerContactFolder
LocationInCompanyFolder
SCOPE
Site preference.
SRP0RequalifyRqstActivityRevision.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for a requalified requested activity revision.
VALID
VALUES
DEFAULT
VALUES
SRP0RequalifyRqstActivityRevisionCreate
SCOPE
Site preference.
SRP0RqstActivity.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for a requested activity. The summary style sheet
is used for the Summary tab.
VALID
VALUES
DEFAULT
VALUES
SRP0RqstActivitySummary
SCOPE
Site preference.
SRP0RqstActivityRevision.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for a requested activity revision.

VALID
VALUES
DEFAULT
VALUES
SRP0RqstActivityRevisionCreate
SCOPE
Site preference.
SRP0RqstActivityRevision.RENDERING
DESCRIPTION
Registers the viewer style sheet for a requested activity revision.
VALID
VALUES
DEFAULT
VALUES
SRP0RqstActivityRevision
SCOPE
Site preference.
SRP0RqstActivityRevision.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for a requested activity revision. The summary
VALID
VALUES
DEFAULT
VALUES
SRP0RqstActivityRevisionSummary
SCOPE
Site preference.
SRP0RqstActivityRevision_DefaultChildProperties
DESCRIPTION
Determines which properties are children of a requested activity revision.
VALID
VALUES
A valid list of default child properties for a requested activity revision.
DEFAULT
VALUES
MROProductFolder

CMHasImpactedItem
CMHasProblemItem
CMHasSolutionItem
ActivityDiscrepancyFolder
SCOPE
Site preference.
SRP0RqstActivityRevision_ServiceDiscrepancy_default_relation
DESCRIPTION
Determines the default relation between a requested activity revision and a service
discrepancy.
VALID
VALUES
DEFAULT
VALUES
SRP0ActivityDiscrepancy
SCOPE
Site preference.
SRP0ServiceCatalog.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for a service catalog.
VALID
VALUES
DEFAULT
VALUES
SRP0ServiceCatalogCreate
SCOPE
Site preference.
SRP0ServiceCatalog.RENDERING
DESCRIPTION
Registers the viewer style sheet for a service catalog.
VALID
VALUES
DEFAULT
VALUES
SRP0ServiceCatalog

SCOPE
Site preference.
SRP0ServiceCatalog.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for a service catalog. The summary style sheet
VALID
VALUES
DEFAULT
VALUES
SRP0ServiceCatalogSummary
SCOPE
Site preference.
SRP0ServiceCatalog_DefaultChildProperties
DESCRIPTION
Determines which properties are children of a service catalog.
VALID
VALUES
A valid list of default child properties for a service catalog.
DEFAULT
VALUES
SRP0ProductCatalog
HWSOStructure
SCOPE
Site preference.
SRP0ServiceCatalog_HWSOStructure_default_relation
DESCRIPTION
Determines the default relation between a service catalog and a hierarchical
workspace object.
VALID
VALUES
DEFAULT
VALUES
HWSOStructure
SCOPE
Site preference.

SRP0ServiceCatalog_PseudoFolder
DESCRIPTION
Defines the list of pseudofolders and their corresponding relations for a service
catalog.
VALID
VALUES
Valid relations that will display as pseudofolders for a service catalog.
DEFAULT
VALUES
SRP0ProductCatalog
HWSOStructure
SCOPE
Site preference.
SRP0ServiceCatalog_SRP0ProductCatalog_default_relation
DESCRIPTION
Determines the default relation between a service catalog and a product catalog.
VALID
VALUES
DEFAULT
VALUES
SRP0ServiceCatalog
SCOPE
Site preference.
SRP0ServiceDiscrepancy.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for a service discrepancy.
VALID
VALUES
DEFAULT
VALUES
SRP0ServiceDiscrepancyCreate
SCOPE
Site preference.

SRP0ServiceOffering.MROCREATERENDERING
DESCRIPTION
Registers the create style sheet for a service offering.
VALID
VALUES
DEFAULT
VALUES
SRP0ServiceOfferingCreate
SCOPE
Site preference.
SRP0ServiceOffering.RENDERING
DESCRIPTION
Registers the viewer style sheet for a service offering.
VALID
VALUES
DEFAULT
VALUES
SRP0ServiceOffering
SCOPE
Site preference.
SRP0ServiceOffering.SUMMARYRENDERING
DESCRIPTION
Registers the summary style sheet for a service offering. The summary style sheet
VALID
VALUES
DEFAULT
VALUES
SRP0ServiceOfferingSummary
SCOPE
Site preference.
SRP0ServiceOffering_ActivityCost_default_relation
DESCRIPTION
Determines the default relation between a service offering and an activity cost.

VALID
VALUES
DEFAULT
VALUES
ActivityCost
SCOPE
Site preference.
SRP0ServiceOffering_DefaultChildProperties
DESCRIPTION
Determines which properties are children of a service offering.
VALID
VALUES
A valid list of default child properties for a service offering.
DEFAULT
VALUES
SRP0ServiceOffering
HWSOStructure
SCOPE
Site preference.
SRP0ServiceOffering_HWSOStructure_default_relation
DESCRIPTION
Determines the default relation between a service offering and a hierarchical
workspace object.
VALID
VALUES
DEFAULT
VALUES
HWSOStructure
SCOPE
Site preference.
SRP0ServiceOffering_SRP0ServiceCatalog_default_relation
DESCRIPTION
Determines the default relation between a service offering and a service catalog.
VALID
VALUES

DEFAULT
VALUES
HWSOStructure
SCOPE
Site preference.
SRP0ServiceOfferingTable_ColumnPreferences
DESCRIPTION
Determines the service offering property names to appear as columns in the service
offering search results table.
VALID
VALUES
A valid property name of a service offering.
DEFAULT
VALUES
object_string
SRP0ServiceCode
SRP0ServiceOfferingNumber
SRP0Narrative
srp0ServiceCatalog
object_type
SCOPE
Site preference.
SRP0StatusViewColumnsShownPref
DESCRIPTION
Determines the list of the property names to appear as columns in the Service
Request Manager Status view.
VALID
VALUES
A valid property name from a primary or delegated service request or requested
activity to appear as a column in the Service Request Manager Status view.
DEFAULT
VALUES
object_string
object_type
srp0ParentRequest
CMClosure
CMDisposition
CMMaturity
SRPoInitializationDate
SRP0NeededByDate
SCOPE
Site preference.

Chapter
23 Integration preferences
Application Integration Environment (AIE) preferences . . . . . . . . . . . . . . . . . 23-1

AIE_overwrite_default_import_item_type . . . . . . . . . . . . . . . . . . . . . . . . 23-1
AIE_no_BVR_edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
AIE_POST_EXPORT_SCRIPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
AIE_PRE_IMPORT_SCRIPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-3
Application Response Measurement (ARM) integration preferences . . . . . . . . 23-4

ARM_tcfs_open_close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-5
ARM_tcfs_export_file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
ARM_tcfs_import_file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
ARM_ods_remote_find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
ARM_ods_publish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-7
ARM_ods_unpublish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-8
ARM_idsm_import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-8
ARM_tcsync_update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-9
ARM_tcsync_object_file_transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-10
ARM_idsm_version_check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-10
ARM_archive_operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-11
ARM_restore_operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-11
ARM_session_login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-12
ARM_session_logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-12
ARM_expand_object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-13
ARM_create_item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-13
ARM_create_itemrev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-14
ARM_create_dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-14
ARM_import_dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-15
ARM_export_dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-15
ARM_where_used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-16
ARM_where_referenced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-16
ARM_search_object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-17
ARM_acquire_license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-17
ARM_saveas_item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-18
ARM_open_dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-18
ARM_display_prop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-19
ARM_update_prop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-19
ARM_display_form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-20
ARM_update_form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-20
ARM_cut_objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-21
ARM_copy_objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-21
ARM_paste_objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-22
ARM_checkout_objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-22
ARM_checkin_objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-23
ARM_delete_objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-23

ARM_print_file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-24
ARM_load_lov . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-24
ARM_launch_mynavigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-25
ARM_expand_bomview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-25
ARM_expandbelow_bomview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-26
ARM_save_bomview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-26
ARM_bom_compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-27
ARM_open_inbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-27
ARM_open_task2track . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-28
ARM_open_task2perform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-28
ARM_initiate_process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-29
ARM_perform_signoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-29
ARM_create_changeitem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-30
ARM_display_changeitem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-30
ARM_create_supersedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-31
ARM_display_genealogy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-31
Teamcenter Integration for AutoCAD preferences . . . . . . . . . . . . . . . . . . . . 23-32

ACAD_COMPONENT_ONLY_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . 23-32
Configuring computer aided engineering preferences . . . . . . . . . . . . . . . . . . 23-32

Computer aided engineering preferences . . . . . . . . . . . . . . . . . . . . . . . . 23-33
CAELoadItemRevision Master_viewerprops . . . . . . . . . . . . . . . . . . 23-33
CAEBCItemRevision Master_viewerprops . . . . . . . . . . . . . . . . . . . . 23-33
CAEConnItemRevision Master_viewerprops . . . . . . . . . . . . . . . . . . 23-34
CAEAnalysisRevision Master_viewerprops . . . . . . . . . . . . . . . . . . . 23-34
CAE_batch_meshing_tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-35
CAE_default_batch_meshing_tool . . . . . . . . . . . . . . . . . . . . . . . . . . 23-36
CAE_batch_meshing_root_dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-36
CAE_pre_processor_tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-36
CAE_post_processor_tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-37
CAE_solver_tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-37
CAE_pre_processor_startup_scripts . . . . . . . . . . . . . . . . . . . . . . . . 23-37
CAE_post_processor_startup_scripts . . . . . . . . . . . . . . . . . . . . . . . . 23-38
CAE_solver_startup_scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-38
CAE_pre_processor_primary_input . . . . . . . . . . . . . . . . . . . . . . . . . 23-38
CAE_post_processor_primary_input . . . . . . . . . . . . . . . . . . . . . . . . 23-39
CAE_solver_primary_input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-39
CAE_pre_processor_alternate_input . . . . . . . . . . . . . . . . . . . . . . . . 23-39
CAE_pre_processor_primary_output . . . . . . . . . . . . . . . . . . . . . . . . 23-40
CAE_post_processor_primary_output . . . . . . . . . . . . . . . . . . . . . . . 23-40
CAE_solver_primary_output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-40
CAE_pre_processor_additional_output . . . . . . . . . . . . . . . . . . . . . . 23-41
CAE_post_processor_additional_output . . . . . . . . . . . . . . . . . . . . . . 23-41
CAE_solver_additional_output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-42
CAE_dataMapping_file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-42
CAE_structure_map_dataset_type . . . . . . . . . . . . . . . . . . . . . . . . . 23-42
CAE_startup_scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-43
CAE_meshing_params_criteria_source . . . . . . . . . . . . . . . . . . . . . . 23-43
CAE_batch_meshing_import_file_extensions . . . . . . . . . . . . . . . . . . 23-44
CAE_input_geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-44
CAE_always_remesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-44
CAE_batch_meshing_always_create_new . . . . . . . . . . . . . . . . . . . . 23-45
CAE_batch_meshing_attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-45

CAE_simulation_tool_config_dsname . . . . . . . . . . . . . . . . . . . . . . . 23-46
Teamcenter Integration for NX I-deas preferences . . . . . . . . . . . . . . . . . . . . 23-46

IDEAS_manager_library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-46
TC_SHOW_OPEN_IN_IDEAS_BUTTON . . . . . . . . . . . . . . . . . . . . . . . 23-46
Mentor Graphics Integration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . 23-47

MGCItemRevision_shown_relations . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-47
MGCItemRevision_relations_as_folders . . . . . . . . . . . . . . . . . . . . . . . . 23-47
IMAN_MGC_Viewpoint_relation_primary . . . . . . . . . . . . . . . . . . . . . . . 23-48
IMAN_MGC_Component_relation_primary . . . . . . . . . . . . . . . . . . . . . . 23-48
IMAN_MGC_Design_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . 23-48
ERP Connect to SAP preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-49

TC_ERP_mapping_files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-49
TC_ERP_current_schema_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-49
TC_SAP_alt_bomview_file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-50
TC_ERP_uom_mapping_file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-50
TC_ERP_rellog_file_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-50
TC_SAP_cad_tables_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-51
TC_SAP_sapcad_dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-51
IMAN_SAP_sideinfo_file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-51
TC_ERP_dataset_types_to_transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-52
ODBC Driver preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-52

TC_ODBC_release_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-52
ClearCase Integration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-53

SCM_ClearCase_Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-53
SCM_ClearCase_UNCO_Keep_Version . . . . . . . . . . . . . . . . . . . . . . . . . 23-54
SCM_CheckIn_Identical_Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-54

Chapter
23 Integration preferences
Integration preferences modify the functionality or appearance of a rich client

integration with third-party software such as STEP or Mentor Graphics Integration.
Application Integration Environment (AIE) preferences

Application Integration Environment (AIE) provides the framework and common
functions required to integrate applications with Teamcenter. This framework
consists of three components: Encapsulation Manager, Remote Manager, and
Supplier Manager.
Use AIE preferences to modify the integration’s behavior.
AIE_overwrite_default_import_item_type
DESCRIPTION
Determines whether users importing non-NX files from a directory can choose from
among all the item types available to the data model service (DMS) or is restricted to
default item type defined by the system administrator.
VALID
VALUES
ON The user can choose from all item type listed in the DMS,
whether selecting new files to be imported or previously
exported files.
OFF The user cannot chose from any item type; the first item type
defined in the data model service is used as the default item
type. Previously exported files revert to their existing item type
and new files are imported using the default item type only.
DEFAULT
VALUES
OFF
SCOPE
User preference.

Chapter 23 Integration preferences
AIE_no_BVR_edit
DESCRIPTION
Determines whether a particular BOM view revision is changed during an AIE
import operation from defined CAD system. If any dataset types defined in this
preference appears together with a dataset type registered with AIE (for example,
with ACADDWG specifying AutoCAD Manager, or SE Part specifying Specification
Manager), then the BOM view revision is not changed during the AIE import.
VALID
VALUES
Accepts any or all of the dataset types defined by default by the system. This
preference is defined during AIE installation.
DEFAULT
VALUES
UGPART
UGMASTER
UGALTREP
UGSCENARIO
SCOPE
Site preference.
AIE_POST_EXPORT_SCRIPT
DESCRIPTION
Determines whether to execute a user-written script or program after exporting
registered datasets via your CAD integration. This allows you to perform custom
actions during the export phase (such as mapping attributes, or running utilities
and applications). On export, the CAD files and other associated files (based on your
configuration) are exported to the connection directory. The script is started after
the AIE export with the IXF file name as argument.
The following is an example script run on Windows:
set XFILE_ARG=%1
echo ixf=%XFILE_ARG%
pause
The following is an example script run on UNIX:

#!/bin/ksh
export MY_ARGS=$1
echo $MY_ARGS >> /scratch/log/export_log
echo $PATH >> /scratch/log/export_log
If left unset, the system does not execute the script. If set with a value, the system
will attempt to run the script. The value must be the full path to the script.

Integration preferences
Note
In case of access error (for example, the current user does not have the
privilege to execute the script, or the script is not available at the location
specified) or if the script returns a negative number, the errors will be logged.
The already completed export operation will not be undone or rolled back.
VALID
VALUES
Accepts a single string as a value. Must be the full qualified path to the script.
The path cannot contain spaces.
DEFAULT
VALUES
None.
SCOPE
Site preference.
AIE_PRE_IMPORT_SCRIPT
DESCRIPTION
Determines whether to execute a user-written script or program before importing
registered datasets via your CAD integration. This allows you to perform custom
actions during the import phase (such as mapping attributes, or running utilities and
applications). The CAD files and other associated files (based on your configuration)
are imported from the connection directory.
The following is an example script run on Windows:
set XFILE_ARG=%1
echo ixf=%XFILE_ARG%
pause
The following is an example script run on UNIX:

#!/bin/ksh
import MY_ARGS=$1
echo $MY_ARGS >> /scratch/log/import_log
echo $PATH >> /scratch/log/import_log
If left unset, the system does not execute the script. If set with a value, the system
will attempt to run the script. The value must be the full path to the script.
Note
In case of access error (for example, the current user does not have the
privilege to execute the script, or the script is not available at the location
specified) or if the script returns a negative number the import operation is
cancelled and no files will be imported.
VALID
VALUES
Accepts a single string as a value. Must be the full qualified path to the script.
The path cannot contain spaces.

DEFAULT
VALUES
None.
SCOPE
Site preference.
Application Response Measurement (ARM) integration preferences

The Teamcenter/ARM integration monitors transaction performance, particularly in
client/server applications.
ARM transactions use API calls to start and stop transaction functions. Additional
metrics or data can be supplied with these ARM function calls. By default, a dummy
logging agent is supplied with Teamcenter that recognizes all ARM function calls but
does not perform an action. If a commercial logging agent is used, transaction data
is captured and stored for use later by a performance profiler. All ARM transactions
log success or error status. Transactions implemented in Teamcenter File Services
also log the IP address of the client workstation.
Note
Preference settings are established when a process is started. Therefore, to
enable or disable an ARM preference for a specific process, the preference
must be set in the file used by the process, and the process restarted.
A variety of commercial products exist that support collection of the transaction

information reported via the ARM API. These products install a sharable image
(libarm.sl on UNIX platforms and libarm32.dll on Windows NT/2000) that provide
entry points for the ARM API functions.
It is important to understand the impact that these products can have on the system
and network on which they are installed.
Teamcenter provides a default sharable libarm image file for all
Teamcenter-supported platforms. This file is used to satisfy ARM API function
references. The installation of a commercial product requires adjustment to locate
the sharable libarm image file provided by the commercial product. For example, it
may be necessary to copy the file to a system bin directory, redefine the system path
environment variable, or define a shareable library path environment variable.
Note
Although the ARM API is standardized, the collection and interpretation of
data is at the discretion of the vendor of the commercialized product. For
example, MeasureWare from Hewlett-Packard does not log each individual
transaction, rather it averages transactions within a defined period of time
and then logs a single entry. As such, any reported string metrics are
discarded and numeric entries averaged with high and low values maintained.
When using a commercial agent, you can review the actual ARM transactions that
have been logged. However, there may be a delay if transaction data is averaged
over a particular period of time before an entry is made. If using MeasureWare
on Windows NT/2000, you can use the MeasureWare Agent utility to review the
transactions that have been logged, as follows.

1. From the Start menu, choose Programs→RPM Tools→MeasureWare Agent.
2. Choose Export from the Log File menu. The system displays the Export Log File
Data dialog box.
3. Enter a name for the output file.
4. Choose Transaction and Transaction Summary from the Available Data Types
list.
5. Set start/end date and time in the Log File Data Range field to define the time
window during which transaction data is exported.
6. Click the Export Data button. The Processing Data Summary dialog box
displays the export operation.
7. Click the Close button to return to the Export Log File Data dialog box.
8. Click the Examine Data button. The system displays the Select Output File
to Examine dialog box.
9. Locate and select the output file. Alternatively, enter the name of the output file
in the File Name field.
10. Click the Open button.

The transaction file displays in a text editor window. Look for ARM transaction
names. For example, thetcserver IDSM remote import transaction has an
application transaction name such astc/tcserver-annpc25_idsm_import.
ARM_tcfs_open_close
DESCRIPTION
Enables or suppresses performance monitoring of FMS file open and close operations
in the Teamcenter server.
VALID
VALUES
ON Enables performance monitoring of FMS file open and close
operations in the Teamcenter server.
OFF Suppresses performance monitoring of FMS file open and close

operations in the Teamcenter server.
DEFAULT
VALUES
OFF
SCOPE
All.

ARM_tcfs_export_file
DESCRIPTION
Enables or suppresses performance monitoring of FMS file export operations in the
Teamcenter server only.
VALID
VALUES
ON Enables performance monitoring of FMS file export operations
in the Teamcenter server only.
OFF Suppresses performance monitoring of FMS file export
operations in the Teamcenter server only.
DEFAULT
VALUES
OFF
SCOPE
All.
ARM_tcfs_import_file
DESCRIPTION
Enables or suppresses performance monitoring of FMS file import operations in the
Teamcenter server only.
VALID
VALUES
ON Enables performance monitoring of FMS file import operations
in the Teamcenter server only.
OFF Suppresses performance monitoring of FMS file import
operations in the Teamcenter server only.
DEFAULT
VALUES
OFF
SCOPE
All.
ARM_ods_remote_find
DESCRIPTION
Enables or suppresses performance monitoring for the Multi-Site Collaboration
remote find function in both the Teamcenter server and the ODS service.
For client processes, the transaction reports the duration of time required to perform
a remote find operation for the published objects that match the query parameters.
For the ODS process, the time required to perform the remote find operation on the
objects that match the query parameters is reported.
The following metrics can also be reported for both the client and server processes:

• Operation status or error code
• Number of objects returned
• ID of the requesting site
• IP address of the requesting client
VALID
VALUES
ON Enables performance monitoring for the Multi-Site
Collaboration remote find function in both the Teamcenter
server and the ODS service.
OFF Suppresses performance monitoring for the Multi-Site
Collaboration remote find function in both the Teamcenter
DEFAULT
VALUES
OFF
SCOPE
Site preference.
ARM_ods_publish
DESCRIPTION
Enables or suppresses performance monitoring of the Multi-Site Collaboration
publish object function in both the Teamcenter server and the ODS service.
a publish object operation on the selected objects.
For ODS processes, the transaction reports the time required to create the
publication records for the objects and to report operation status back to the
requesting client process.
The following metrics can also be reported for both client and server processes:
• ID of the client site
VALID
VALUES
ON Enables performance monitoring of the Multi-Site
Collaboration publish object function in both the Teamcenter
OFF Suppresses performance monitoring of the Multi-Site
Collaboration publish object function in both the Teamcenter
DEFAULT
VALUES
OFF

SCOPE
Site preference.
ARM_ods_unpublish
DESCRIPTION
unpublish object function in both the Teamcenter server and the ODS service.
an unpublish object operation on the selected objects.
For ODS processes, the transaction reports the time required to remove the
publication records for the objects and to report operation status back to the
requesting client process.
Operation status or error code metrics can also be reported for both client and
server processes.
VALID
VALUES
Collaboration unpublish object function in both the Teamcenter
Collaboration unpublish object function in both the Teamcenter
DEFAULT
VALUES
OFF
SCOPE
Site preference.
ARM_idsm_import
DESCRIPTION
Enables or suppresses performance monitoring of the Teamcenter remote import
function.
a remote import operation on the selected objects.
For ODS processes, the transaction reports the time required to locate and transfer
the selected remote objects and to report operation status back to the requesting
client process.
• Number of I/O requests to transfer imported objects
• Total number of bytes transferred

• Object ID of the first object in the imported object list
• IP address of the client
• Number of files in cache directory
• Size, in bytes, of files in the cache directory
• Object ID of the first object in the exported object list
• IP address of the client site

VALID
VALUES
ON Enables performance monitoring of the Teamcenter remote
import function.
OFF Suppresses performance monitoring of the Teamcenter remote
import function.
DEFAULT
VALUES
OFF
SCOPE
All.
ARM_tcsync_update
DESCRIPTION
Enables or suppresses performance monitoring of the Multi-Site Collaboration object
update function by the tc_sync utility.
For the tc_sync process, the transaction reports the duration of time required to
synchronize each modified, published object from the client node operation to the
selected sites. There is no corresponding server-side transaction.
The following metrics can also be reported for the tc_sync process:
• Object ID
• Number of files in the cache directory

VALID
VALUES
Collaboration object update function by the tc_sync utility.

DEFAULT
VALUES
OFF
SCOPE
All.
ARM_tcsync_object_file_transfer
DESCRIPTION
Enables or suppresses performance monitoring of the Multi-Site Collaboration object
update function by the tc_sync utility.
Object file transfer is a subtransaction of the ARM tc_sync update transaction. This
transaction reports the duration of time required to transfer the files associated with
a remote object to a specific site. There is no corresponding server-side transaction.
The following metrics can also be reported:
• Object ID
• Number of files in the cache directory

VALID
VALUES
DEFAULT
VALUES
OFF
SCOPE
All.
ARM_idsm_version_check
DESCRIPTION
internal version check function.
For the client process, the transaction reports the duration of time required to
perform a version request of the IDSM server at a remote node.
For the IDSM process, the transaction reports the time required to respond to the
version check request.
The following metrics can also be reported:

• IDSM version reported
VALID
VALUES
Collaboration internal version check function.
Collaboration internal version check function.
DEFAULT
VALUES
OFF
SCOPE
All.
ARM_archive_operation
DESCRIPTION
Determines whether performance monitoring of archive operations is available.
VALID
VALUES
ON Enables performance monitoring of archive operations.
OFF Disables performance monitoring of archive operations.
DEFAULT
VALUES
OFF
SCOPE
All.
ARM_restore_operation
DESCRIPTION
Determines whether performance monitoring of restore operations is available.
VALID
VALUES
ON Enables performance monitoring of restore operations.
OFF Disables performance monitoring of restore operations.
DEFAULT
VALUES
OFF
SCOPE
All.

ARM_session_login
DESCRIPTION
Determines whether to enable or suppress the logon performance transaction.
System administrators can set this preference from the Performance Monitor panel
of the Options dialog box; the preference is set in the system administrator’s user
preference file. System administrators can also set this preference site-wide by
adding it to the site preference file, however, individual user settings override the
site setting.
Users without administrative privileges can set this preference by manually
modifying their user preference files.
VALID
VALUES
ON Enables performance monitoring of the logon performance
transaction.
OFF Suppresses performance monitoring of the logon performance
transaction.
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_session_logout
DESCRIPTION
Determines whether to enable or suppress the log off performance transaction.
adding it to the site preference file, however, individual user settings override the
site setting.
Users without administrative privileges can set this preference by manually
modifying their user preference files.
VALID
VALUES
ON Enables performance monitoring of the log off performance
transaction.
OFF Suppresses performance monitoring of the log off performance
transaction.
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_expand_object
DESCRIPTION
Determines whether to enable or suppress the Expand Object performance
transaction.
adding it to the site preference file; however, individual user settings override the
site setting.
VALID
VALUES
ON Enables performance monitoring of the expand folder
performance transaction.
OFF Suppresses performance monitoring of the expand folder
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_create_item
DESCRIPTION
Determines whether to enable or suppress the create item performance transaction.
site setting.
VALID
VALUES
ON Enables performance monitoring of the create item
OFF Suppresses performance monitoring of the create item
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_create_itemrev
DESCRIPTION
Determines whether to enable or suppress the create item revision performance
transaction.
site setting.
VALID
VALUES
ON Enables performance monitoring of the create item revision
OFF Suppresses performance monitoring of the create item revision
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_create_dataset
DESCRIPTION
Determines whether to enable or suppress the create dataset performance
transaction.
site setting.
VALID
VALUES
ON Enables performance monitoring of the create dataset
OFF Suppresses performance monitoring of the create dataset
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_import_dataset
DESCRIPTION
Determines whether to enable or suppress the import dataset performance
transaction.
site setting.
VALID
VALUES
ON Enables performance monitoring of the import dataset
OFF Suppresses performance monitoring of the import dataset
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_export_dataset
DESCRIPTION
Determines whether to enable or suppress the export dataset performance
transaction.
site setting.
VALID
VALUES
ON Enables performance monitoring of the export dataset
OFF Suppresses performance monitoring of the export dataset
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_where_used
DESCRIPTION
Determines whether to enable or suppress the where-used performance transaction.
site setting.
VALID
VALUES
ON Enables performance monitoring of the where-used
OFF Suppresses performance monitoring of the where-used
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_where_referenced
DESCRIPTION
Determines whether to enable or suppress the where-referenced performance
transaction.
site setting.
VALID
VALUES
ON Enables performance monitoring of the where-referenced
OFF Suppresses performance monitoring of the where-referenced
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_search_object
DESCRIPTION
Determines whether to enable or suppress the systems search performance
transaction. Measures elapsed time from search request to display of search results.
site setting.
VALID
VALUES
ON Enables performance monitoring of the search performance
transaction.
OFF Suppresses performance monitoring of the search performance

transaction.
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_acquire_license
DESCRIPTION
Determines whether to enable or suppress the system’s license acquisition
performance transaction. Measures elapsed time from the request to the FLEXlm
sever to the return of the license key.
site setting.
VALID
VALUES
ON Enables performance monitoring of the license acquisition
OFF Suppresses performance monitoring of the license acquisition

DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_saveas_item
DESCRIPTION
Determines whether to enable or suppress Teamcenter’s Save As performance
transaction. Measures elapsed time from beginning of operation to the display of
all objects.
site setting.
VALID
VALUES
ON Enables performance monitoring of the Save As performance
transaction.
OFF Suppresses performance monitoring of the Save As
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_open_dataset
DESCRIPTION
Determines whether to enable or suppress the system’s open dataset performance
all objects.
site setting.
VALID
VALUES
ON Enables performance monitoring of the open dataset
OFF Suppresses performance monitoring of the open dataset
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_display_prop
DESCRIPTION
Determines whether to enable or suppress the system’s display of object properties
performance transaction. Measures elapsed time from beginning of operation to
the display of all objects.
site setting.
VALID
VALUES
ON Enables performance monitoring of the display object
properties performance transaction.
OFF Suppresses performance monitoring of the display object
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_update_prop
DESCRIPTION
Determines whether to enable or suppress the system’s update of object properties
the display of all objects.
site setting.
VALID
VALUES
ON Enables performance monitoring of the update object
OFF Suppresses performance monitoring of the update object
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_display_form
DESCRIPTION
Determines whether to enable or suppress the system’s display form performance
all objects.
site setting.
VALID
VALUES
ON Enables performance monitoring of the display form
OFF Suppresses performance monitoring of the display form
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_update_form
DESCRIPTION
Determines whether to enable or suppress the system’s update form performance
all objects.
site setting.
VALID
VALUES
ON Enables performance monitoring of the update form
OFF Suppresses performance monitoring of the update form
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_cut_objects
DESCRIPTION
Determines whether to enable or suppress the system’s cut objects performance
remaining objects.
site setting.
VALID
VALUES
ON Enables performance monitoring of the cut objects performance
transaction.
OFF Suppresses performance monitoring of the cut objects
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_copy_objects
DESCRIPTION
Determines whether to enable or suppress the system’s copy objects performance
all objects.
site setting.
VALID
VALUES
ON Enables performance monitoring of the copy objects
OFF Suppresses performance monitoring of the copy objects
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_paste_objects
DESCRIPTION
Determines whether to enable or suppress the system’s paste objects performance
all objects.
site setting.
VALID
VALUES
ON Enables performance monitoring of the paste objects
OFF Suppresses performance monitoring of the paste objects
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_checkout_objects
DESCRIPTION
Determines whether to enable or suppress the system’s check out objects
when all objects are checked out.
site setting.
VALID
VALUES
ON Enables performance monitoring of the check out objects
OFF Suppresses performance monitoring of the check out objects
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_checkin_objects
DESCRIPTION
Determines whether to enable or suppress the system’s check in objects performance
transaction. Measures elapsed time from beginning of operation to when all objects
are checked in.
site setting.
VALID
VALUES
ON Enables performance monitoring of the check in objects
OFF Suppresses performance monitoring of the check in objects
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_delete_objects
DESCRIPTION
Determines whether to enable or suppress the system’s delete objects performance
transaction. Measures elapsed time from beginning of operation to when all objects
are deleted.
site setting.
VALID
VALUES
ON Enables performance monitoring of the delete objects
OFF Suppresses performance monitoring of the delete objects
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_print_file
DESCRIPTION
Determines whether to enable or suppress the Print File performance transaction.
Measures time elapsed between selecting the Print command to the appearance
of the Print dialog box.
site setting.
VALID
VALUES
ON Enables performance monitoring of the print file performance
transaction.
OFF Suppresses performance monitoring of the print file
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_load_lov
DESCRIPTION
Determines whether to enable or suppress Portal’s load LOV performance
transaction. Measures elapsed time from selecting an LOV to the display of all
objects in the list.
site setting.
VALID
VALUES
ON Enables performance monitoring of the load LOV performance
transaction.
OFF Suppresses performance monitoring of the load LOV
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_launch_mynavigator
DESCRIPTION
Determines whether to enable or suppress the rich client’s launch My Teamcenter
performance transaction. Measures elapsed time for loading the My Teamcenter
application.
site setting.
VALID
VALUES
ON Enables performance monitoring of the launch My
Teamcenter performance transaction.
OFF Suppresses performance monitoring of the launch My
Teamcenter performance transaction.
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_expand_bomview
DESCRIPTION
Determines whether to enable or suppress the BOM view expansion performance
transaction. Measures elapsed time between the beginning of the operation and the
display of top-level components.
site setting.
VALID
VALUES
ON Enables performance monitoring of the BOM view expansion
OFF Suppresses performance monitoring of the BOM view
expansion performance transaction.
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_expandbelow_bomview
DESCRIPTION
Determines whether to enable or suppress the BOM view expansion all components
performance transaction. Measures elapsed time between the beginning of the
operation and the display of all components.
site setting.
VALID
VALUES
ON Enables performance monitoring of the BOM view expansion
OFF Suppresses performance monitoring of the BOM view
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_save_bomview
DESCRIPTION
Determines whether to enable or suppress the save BOM view performance
completion of the save operation.
site setting.
VALID
VALUES
ON Enables performance monitoring of the save BOM view
OFF Suppresses performance monitoring of the save BOM view
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_bom_compare
DESCRIPTION
Determines whether to enable or suppress the BOM compare performance
completion of the comparison.
site setting.
VALID
VALUES
ON Enables performance monitoring of the BOM compare
OFF Suppresses performance monitoring of the BOM compare

DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_open_inbox
DESCRIPTION
Determines whether to enable or suppress the open inbox performance transaction.
Measures elapsed time to open a user inbox.
site setting.
VALID
VALUES
ON Enables performance monitoring of the open inbox performance
transaction.
OFF Suppresses performance monitoring of the open inbox

DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_open_task2track
DESCRIPTION
Determines whether to enable or suppress the opening the Tasks to Track folder
performance transaction. Measures elapsed time to expand the folder.
site setting.
VALID
VALUES
ON Enables performance monitoring of the Tasks to Track folder
OFF Suppresses performance monitoring of the Tasks to Track
folder expansion performance transaction.
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_open_task2perform
DESCRIPTION
Determines whether to enable or suppress the opening the Tasks to Perform folder
performance transaction. Measures elapsed time to expand the folder.
site setting.
VALID
VALUES
ON Enables performance monitoring of the Tasks to Perform
OFF Suppresses performance monitoring of the Tasks to Perform
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_initiate_process
DESCRIPTION
Determines whether to enable or suppress the process initiation performance
transaction. Measures elapsed time from beginning of the operation to the insertion
of the initial task into all target inboxes.
site setting.
VALID
VALUES
ON Enables performance monitoring of the process initiation
OFF Suppresses performance monitoring of the process initiation
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_perform_signoff
DESCRIPTION
Determines whether to enable or suppress the perform signoff performance
transaction. Measures elapsed time from performance of the signoff to the insertion
of the process’s next task into all target inboxes.
site setting.
VALID
VALUES
ON Enables performance monitoring of the perform signoff
OFF Suppresses performance monitoring of the perform signoff
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_create_changeitem
DESCRIPTION
Determines whether to enable or suppress the create change object performance
transaction. Measures elapsed time from beginning of the operation to the insertion
of the initial task into all target inboxes; this action occurs only when the Start
Process On Create option is checked while creating a new change.
site setting.
VALID
VALUES
ON Enables performance monitoring of the create change
OFF Suppresses performance monitoring of the create change
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_display_changeitem
DESCRIPTION
Determines whether to enable or suppress Portal’s display change object performance
transaction. Measures elapsed time from beginning of the operation to the display of
all change folders.
site setting.
VALID
VALUES
ON Enables performance monitoring of the display change
OFF Suppresses performance monitoring of the display change
DEFAULT
VALUES
OFF
SCOPE
User preference.

ARM_create_supersedure
DESCRIPTION
Determines whether to enable or suppress the Create Supersedure performance
transaction. Measures elapsed time from beginning of the operation to the display of
the supersedure.
site setting.
VALID
VALUES
ON Enables performance monitoring of the create supersedure
OFF Suppresses performance monitoring of the create supersedure
DEFAULT
VALUES
OFF
SCOPE
User preference.
ARM_display_genealogy
DESCRIPTION
Determines whether to enable or suppress the display genealogy performance
transaction. Measures elapsed time from the selection of the superseded item to
when the genealogy is displayed.
site setting.
VALID
VALUES
ON Enables performance monitoring of the display genealogy
OFF Suppresses performance monitoring of the display genealogy
DEFAULT
VALUES
OFF
SCOPE
User preference.

Teamcenter Integration for AutoCAD preferences

Teamcenter Integration for AutoCAD enables you to use Teamcenter to manage your
files from within the AutoCAD application.
Use the Teamcenter Integration for AutoCAD preference to modify the integration’s
behavior with Teamcenter.
ACAD_COMPONENT_ONLY_MODE
DESCRIPTION
Specifies whether to use component-only mode in open and save operations.
VALID
VALUES
Accepts a single logical value.
TRUE
Specifies the following:
1. Cross-references are not downloaded in assembly download scenarios.
2. BOM information is ignored during any open or save operation.
FALSE
Specifies the following:
1. Cross-references are downloaded in assembly download scenarios.
2. BOM information is updated during save operations.
DEFAULT
VALUES
FALSE
SCOPE
Site preference.
Configuring computer aided engineering preferences

A computer aided engineering (CAE) integration integrates CAE results with the
Encapsulation of CAE analysis tools for process automation requires that the
following preferences are created by a system administrator. Once created, the
default values set by the system administrator are enforced until new values are
defined by general users. General users change the values from the Analysis view in
the Options dialog box accessed from the Edit menu.
For information about using this dialog box, see Getting Started with Teamcenter.
For information about configuring Teamcenter for Simulation, see the Teamcenter
for Simulation Guide.

Computer aided engineering preferences
CAELoadItemRevision Master_viewerprops
DESCRIPTION
Determines how the properties of the CAELoadItemRevision Master form display.
This preference’s values determine the order in which form properties display, and
whether the corresponding field displayed in the form is enabled/disabled, and
optional/mandatory.
VALID
VALUES
Accepts multiple line statements, in the following format:
property-name, O|M, E|D where O = Optional, M = Mandatory, E = Enabled, D =
Disabled. Each property-name entry must be a valid Teamcenter property.
DEFAULT
VALUES
CAELoadItemRevision Master_viewerprops=
load_id,O,E
load_desc,O,E
load_type,O,E
geometry,O,E
load_component_type,O,E
load_component_value,O,E
load_rev_id,O,D
load_rev_name,O,D
load_vault_mode,O,D
load_eint_form_type,O,D
load_link_path,O,D
SCOPE
Site preference.
CAEBCItemRevision Master_viewerprops
DESCRIPTION
Determines how the properties of the CAEBCItemRevision Master form display.
optional/mandatory.
VALID
VALUES
DEFAULT
VALUES
CAEBCItemRevision Master_viewerprops=
bc_id,O,E

bc_desc,O,E
bc_type,O,E
geometry,O,E
constaint_type,O,E
coord_type,O,E
components,O,E
magnitude,O,E
bc_rev_id,O,D
bc_rev_name,O,D
bc_vault_mode,O,D
bc_eint_form_type,O,D
bc_link_path,O,D
SCOPE
Site preference.
CAEConnItemRevision Master_viewerprops
DESCRIPTION
Determines how the properties of the CAEConnItemRevision Master form display.
optional/mandatory.
VALID
VALUES
DEFAULT
VALUES
CAEConnItemRevision Master_viewerprops=
conn_id,O,E
conn_desc,O,E
conn_type,O,E
geometry,O,E
conn_links,O,E
strength,O,E
conn_rev_id,O,D
conn_rev_name,O,D
SCOPE
Site preference.
CAEAnalysisRevision Master_viewerprops
DESCRIPTION
Determines how the properties of the CAEAnalysisRevision Master form display.


optional/mandatory.
VALID
VALUES
DEFAULT
VALUES
CAEAnalysisRevision Master_viewerprops=
analysis_id,O,E
analysis_desc,O,E
analysis_type,O,E
analysis_rev_id,O,D
analysis_rev_name,O,D
SCOPE
Site preference.
CAE_batch_meshing_tools
DESCRIPTION
Defines the list of available batch meshing tools used with the
EPM-batch-meshing-handler handler to create CAE meshes from the identified
targets of a workflow process. Targets must be UGMASTER datasets.
The system uses the value specified for this preference to locate various components
required to run the tool. The system assumes a setup file exists in the TC_DATA
directory for each meshing tool defined in this preference, that each file name
matches a meshing tool defined, and that the file name ends with the .setup
extension.
Each setup file must contain the OS path of the script to be run to execute the tool,
and the file name extension of the meshing results file that the tool creates.
The values defined in this preference determine the valid values of the
CAE_default_batch_meshing_tool preference.
VALID
VALUES
Accepts multiple strings as values; each string must be a valid batch meshing tool.
For example:
CAE_batch_meshing_tools=
a_batch_meshing_tool
another_batch_meshing_tool
DEFAULT
VALUES
None.
SCOPE
Site preference.

CAE_default_batch_meshing_tool
DESCRIPTION
Defines the default batch meshing tool used with the EPM-batch-meshing-handler
handler.
VALID
VALUES
Accepts a single string as a value. Must be a valid batch meshing tool, and defined in
the CAE_batch_meshing_tools preference. For example:
CAE_default_batch_meshing_tool=
a_batch_meshing_tool
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_batch_meshing_root_dir
DESCRIPTION
Defines the root directory under which batch meshing is performed. For each
batch meshing job, the batch meshing interface creates a unique working directory
under this root directory. This keeps all files related to a specific batch meshing
job separate and easy to locate.
VALID
VALUES
Valid directory to which server machine has read/write access.
DEFAULT
VALUES
Value of the TC_TMP_DIR environment variable. If this environment variable is
not set, the default value is C:\Temp on Windows, and /tmp on UNIX.
SCOPE
All.
CAE_pre_processor_tools
DESCRIPTION
Specifies a list of preprocessor tools. Each value in the list represents a preprocessor
tool.
VALID
VALUES
DEFAULT
VALUES
None.

SCOPE
Site preference.
CAE_post_processor_tools
DESCRIPTION
Specifies a list of postprocessor tools. Each value in the list represents a
postprocessor tool.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_solver_tools
DESCRIPTION
Specifies a list of solver tools. Each value in the list represents a solver tool.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_pre_processor_startup_scripts
DESCRIPTION
Specifies a mapping of the preprocessor tool and startup script. It provides the
physical location of a startup script that launches the preprocessor tool.
VALID
VALUES
tool-name::startup-script
DEFAULT
VALUES
None.
SCOPE

CAE_post_processor_startup_scripts
DESCRIPTION
Specifies a mapping of the postprocessor tool and startup script. It provides the
physical location of a startup script that launches the postprocessor tool.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
CAE_solver_startup_scripts
DESCRIPTION
Specifies a mapping of the solver tool and startup script. It provides the physical
location of a startup script that launches the solver tool.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
CAE_pre_processor_primary_input
DESCRIPTION
Specifies a mapping of the preprocessor tool, item type, and primary reference. It
provides values that represent the authoring tool primary input for the preprocessor
tool.
VALID
VALUES
Accepts multiple string values in the following format:
tool-name::item-type::reference-type
DEFAULT
VALUES
None.
SCOPE
Site preference.

CAE_post_processor_primary_input
DESCRIPTION
Specifies a mapping of the postprocessor tool, item type, and primary reference. It
provides values that represent the authoring tool primary input for the postprocessor
tool.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_solver_primary_input
DESCRIPTION
Specifies a mapping of the solver tool, item type, and primary reference. It provides
values that represent the authoring tool primary input for the solver tool.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_pre_processor_alternate_input
DESCRIPTION
Specifies a mapping of the preprocessor tool, dataset type, and primary reference. If
a primary input is not defined for the preprocessor tools, this preference provides
values to describe the alternate input.
VALID
VALUES
tool-name::alternate-dataset-type::reference-type
DEFAULT
VALUES
None.

SCOPE
Site preference.
CAE_pre_processor_primary_output
DESCRIPTION
Specifies a mapping of the preprocessor tool, reference type, file extension, and
relation type. It provides values that represent the authoring tool primary output for
the preprocessor tool. You can use this preference to import the primary output data
generated by the preprocessor tool back in to Teamcenter.
VALID
VALUES
tool-name::reference-type::file-extension::relation-type
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_post_processor_primary_output
DESCRIPTION
Specifies a mapping of the postprocessor tool, reference type, file extension, and
relation type. It provides values that represent the authoring tool primary output
for the postprocessor tool. You can use this preference to import the primary output
data generated by the postprocessor tool back in to Teamcenter.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_solver_primary_output
DESCRIPTION
Specifies a mapping of the postprocessor tool, reference type, file extension, and
relation type. It provides values that represent the authoring tool primary output
for the solver tool. You can use this preference to import the primary output data
generated by the solver tool back in to Teamcenter.

VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_pre_processor_additional_output
DESCRIPTION
Specifies a mapping of the preprocessor tool, dataset type, reference type, file
extension, and relation type. It provides values that represent the authoring tool
additional output for the preprocessor tool. You can use this preference to import the
additional output data generated by the preprocessor tool back in to Teamcenter.
VALID
VALUES
tool-name::dataset-type::reference-type::file-extension::relation-type
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_post_processor_additional_output
DESCRIPTION
Specifies a mapping of the postprocessor tool, dataset type, reference type, file
extension, and relation type. It provides values that represent the authoring tool
additional output for the postprocessor tool. You can use this preference to import
the additional output data generated by the postprocessor tool back in to Teamcenter.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.

CAE_solver_additional_output
DESCRIPTION
Specifies a mapping of the solver tool, dataset type, reference type, file extension,
and relation type. It provides values that represent the authoring tool additional
output for the solver tool. You can use this preference to import the additional output
data generated by the solver tool back in to Teamcenter.
VALID
VALUES
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_dataMapping_file
DESCRIPTION
Defines the file name containing a set of data mapping rules.
VALID
VALUES
Accepts a single string value.
DEFAULT
VALUES
None.
SCOPE
Site preference.
CAE_structure_map_dataset_type
DESCRIPTION
Defines allowable dataset types that can be used as a structure map.
VALID
VALUES
Accepts multiple string values.
DEFAULT
VALUES
CAEStructureMap
SCOPE
Site preference.

CAE_startup_scripts
DESCRIPTION
Specifies the location of the startup script for each batch meshing tool. For this
preference, it is recommended that you add only one value for each batch meshing
tool. Adding multiple values does not result in an error; however, Teamcenter takes
only one value for the batch meshing feature.
sample_batchmesher_script.bat, a sample startup script file, is provided in the
TC_DATA folder in your Teamcenter installation directory and is available only
after you install the product.
VALID
VALUES
Accepts multiple string values in the format:
tool-name::script-name
DEFAULT
VALUES
None.
SCOPE
CAE_meshing_params_criteria_source
DESCRIPTION
Defines the parameter and criteria files for each batch meshing tool. This is an
optional preference. You can add multiple values to this preference for each batch
meshing tool.
Note
Teamcenter executes the batch meshing feature even if you leave this
preference undefined. The software uses the default values for the parameter
and criteria files from the batch meshing tool.
VALID
VALUES
tool-name::item-id::revision-id::dataset-name::item-id::revision-id::dataset-name
DEFAULT
VALUES
None.
SCOPE
Site and user preference (optional).

CAE_batch_meshing_import_file_extensions
DESCRIPTION
Defines the file extensions for the output files imported in to Teamcenter as named
references for the CAEMesh dataset.
You can enter one or multiple output file extensions to define this preference.
When you enter multiple file extensions, ensure that you enter the file extensions
without spaces and insert a comma between them. For example, fem,sim. For this
preference, it is recommended that you add only one value for each batch meshing
tool. Adding multiple values does not result in an error; however, Teamcenter takes
only one value for the batch meshing feature.
VALID
VALUES
tool-name::extension::dataset-type::reference-type::relation-type
DEFAULT
VALUES
None.
SCOPE
CAE_input_geometry
DESCRIPTION
Defines the dataset type that holds the input geometry required for the batch
meshing feature. For this preference, it is recommended that you add only one value
for each batch meshing tool. Adding multiple values does not result in an error;
however, Teamcenter takes only one value for the batch meshing feature. You can
define a primary or an alternate input geometry for each batch meshing tool. If the
primary input geometry is not defined for the dataset type, Teamcenter sequentially
searches for the alternate input geometry.
VALID
VALUES
tool-name::dataset-type::reference-type
DEFAULT
VALUES
None.
SCOPE
CAE_always_remesh
DESCRIPTION
Verifies that the CAE geometry is up-to-date and meshes it regardless of its meshing
status. This is an optional preference.

VALID
VALUES
True
False
DEFAULT
VALUES
False.
SCOPE
CAE_batch_meshing_always_create_new
DESCRIPTION
Determines whether a new CAEModel item is created or an existing CAEModel
item is reused. This is an optional preference. If you set this preference to True, the
system performs a reuse check over the existing CAEModel item.
VALID
VALUES
True The system creates a new CAEModel item to contain the
batch meshing output.
False The system performs a reuse check over an existing
CAEModel item. If appropriate, it uses the CAEModel item
to contain the batch meshing output.
DEFAULT
VALUES
False.
SCOPE
CAE_batch_meshing_attribute
DESCRIPTION
Defines the attribute values for the CAEModel item or item revision. This is an
optional preference.
VALID
VALUES
tool-name::attribute::value
DEFAULT
VALUES
None.
SCOPE

CAE_simulation_tool_config_dsname
DESCRIPTION
Defines the dataset name where the simulation tool configuration is stored in XML
format as a named reference.
VALID
VALUES
Use the default value unless it violates any customer-defined business rules for
dataset names. Any unique value that meets the business rules for dataset names
is valid.
DEFAULT
VALUES
TCCAESimToolConfig102009
SCOPE
Site preference.
Teamcenter Integration for NX I-deas preferences

Teamcenter Integration for NX I-deas integrates Teamcenter and I-deas to provide a
single data management environment for users.
Use the following preferences to implement this integration.
IDEAS_manager_library
DESCRIPTION
Specifies the name of the Teamcenter Integration for NX I-deas server-side shared
library.
VALID
VALUES
Accepts a single string as a value. Must be a valid server-side shared library name.
DEFAULT
VALUES
None.
SCOPE
Group, role, or user preference.
TC_SHOW_OPEN_IN_IDEAS_BUTTON
DESCRIPTION
Specifies whether the Open in I-deas button is displayed on the Structure Manager
application toolbar.
VALID
VALUES
true Displays the Open in I-deas button is displayed on the
Structure Manager application toolbar.

false Does not display the Open in I-deas button is displayed on the
Structure Manager application toolbar.
DEFAULT
VALUES
false
SCOPE
Group, role, or user preference.
Mentor Graphics Integration preferences

The Mentor Graphics Integration allows you to store and manage Mentor Graphics
Design Manager objects in Teamcenter.
Use Mentor Graphics Integration preferences define how Mentor Graphics
Integration handles Teamcenter product structure data.
MGCItemRevision_shown_relations
DESCRIPTION
Determines which item relations are shown for the MGCItemRevision type.
VALID
VALUES
PSBOMViewRevision
IMAN_master_form
IMAN_MGC_Design
IMAN_MGC_Component
IMAN_MGC_Viewpoint
Valid Item Relations
DEFAULT
VALUES
None.
SCOPE
Site preference.
MGCItemRevision_relations_as_folders
Description
Determines which item relations are shown as folders for the MGCItemRevision
type.
Valid Values
PSBOMViewRevision
IMAN_master_form
IMAN_MGC_Design
IMAN_MGC_Component
IMAN_MGC_Viewpoint
Valid Item Relations

Default Values
None.
Scope
Site preference.
IMAN_MGC_Viewpoint_relation_primary
DESCRIPTION
Sets primary object types for the viewpoint relation.
VALID
VALUES
One or more strings as values; each string must be a valid Teamcenter object type.
DEFAULT
VALUES
None. The ItemRevision setting must be uncommented.
SCOPE
Site preference.
IMAN_MGC_Component_relation_primary
DESCRIPTION
Sets primary object types for the component relation.
VALID
VALUES
DEFAULT
VALUES
SCOPE
Site preference.
IMAN_MGC_Design_relation_primary
DESCRIPTION
Sets primary object types for the design relation.
VALID
VALUES
DEFAULT
VALUES
SCOPE
Site preference.

ERP Connect to SAP preferences

The ERP Connect to SAP integration transfers product information in a controlled
and auditable manner.
Use the following preferences to define mapping files, schema, log file locations,
and the like.
TC_ERP_mapping_files
DESCRIPTION
Defines the mapping file used.
More than one mapping file can be listed. This is especially useful for displaying
old form types. Used in this way the schema should have a different ID to avoid
ambiguity during workflow processes.
Note
If more than one mapping file is listed, the same Form Type cannot be listed
multiple times. This causes silent initialization errors.
VALID
VALUES
$TC_DATA/erp/sample_map_file.txt
DEFAULT
VALUES
SCOPE
Site preference.
TC_ERP_current_schema_name
DESCRIPTION
Defines the schema to be used and is referenced by the workflow handlers, for
example:
Default setting is SAP_R3
Note
Only one schema can referenced. This is not a site preference; users can
specify a schema that is different from that used for the site. This is helpful
when testing the interface to a new version of the ERP system or possibly
transferring to a different ERP system.
VALID
VALUES
Accepts a single string as a value. Must be a valid schema name.
DEFAULT
VALUES
None.
SCOPE
Site preference.

TC_SAP_alt_bomview_file
DESCRIPTION
Points to the directory containing the viewtype_mapping.dat file.
VALID
VALUES
Accepts a single string as a value. Must be the full path name of the directory.
DEFAULT
VALUES
$TC_DATA/erp/viewtype_mapping.dat
SCOPE
Site preference.
TC_ERP_uom_mapping_file
DESCRIPTION
Points to the directory containing the uom_mapping.dat file.
VALID
VALUES
DEFAULT
VALUES
$TC_DATA/erp/uom_mapping.dat
SCOPE
Site preference.
TC_ERP_rellog_file_path
DESCRIPTION
Determines the directory to which the log file is written by the SAP upload program.
This file is imported to Teamcenter as the log file dataset attached to the process,
allowing users to view the file. This directory should be purged regularly.
VALID
VALUES
DEFAULT
VALUES
$TC_TMP_DIR
SCOPE
Site preference.

TC_SAP_cad_tables_path
DESCRIPTION
Specifies the location of the SAP CAD table configuration files, as produced in setting
up the SAP CAD dialog interface.
VALID
VALUES
DEFAULT
VALUES
$TC_TMP_DIR
SCOPE
Site preference.
TC_SAP_sapcad_dir
DESCRIPTION
Points to a directory containing the caddialog.ini configuration file.
Note
If individual users have their own logon to SAP, the preference points to the
user’s home directory or wherever they store their caddialog.ini file.
VALID
VALUES
DEFAULT
VALUES
$TC_DATA/erp
SCOPE
Site preference.
IMAN_SAP_sideinfo_file
DESCRIPTION
Points to the sideinfo communication file.
VALID
VALUES
Accepts a single string as a value. Must be the full path name and file name of
the file.
DEFAULT
VALUES
$TC_DATA/erp/sideinfo
SCOPE
Site preference.

TC_ERP_dataset_types_to_transfer
DESCRIPTION
Defines the dataset types to be transferred (using ERP document transfer) and the
associated file format (named reference type).
For example:
TC_ERP_dataset_types_to_transfer=
UGMASTER/Shaded-Image
UGPART/Shaded-Image
Text/TXT
VALID
VALUES
DEFAULT
VALUES
UGMASTER/Shaded-Image
UGPART/Shaded-Image
Text/TXT
SCOPE
Site preference.
ODBC Driver preferences

The ODBC Driver allows ODBC-compliant applications such as Actuate Report
Writer, Crystal Reports, Microsoft Excel and Access to extract data from a
Teamcenter database for building reports.
Use ODBC Driver preference to modify the integration’s behavior with Teamcenter.
TC_ODBC_release_status
DESCRIPTION
This file can be found in the /vobs/src/tc/data/teamcenter_env_wnt.default
directory.
This is a file that the tc_preferences.xml preference file links to for a Windows-only
application. Before starting the application, set the option to ALL or LATEST
to retrieve either all the release statuses or the latest release status in the list,
respectively.
There is a new preference file in the \vobs\src\tc\data_odbc_exclude_tcbomlist
directory. Before starting the application, move the columns you do not want to see
in the BOM table in this file. The format of the file is as follows:
EXCLUDED_LIST_START
bl_formatted_title
bl_indended_title
#bl_line_name
#bl_config_string
#bl_variant_state

Each line contains the name of a column (a BOM property). Remove the comment
symbol (#) to add the name. Add the query criteria Parent_Item_Rev_Id like xxx
after specifying the Parent_Item_Id criteria, using the standard query interface
in the application.
The WhereUsed table in the table list, has six column attributes for a user to report.
The columns are:
Child_Item_Id
Child_Item_Rev_Id
level_of_search
item_id
item_rev_id
object_name
Add Child_Item_Id criteria and after that, add Child_Item_Rev_Id criteria, using
the standard query interface in the application.
VALID
VALUES
ALL
Outputs all in the release status list.
LATEST
Outputs the latest one in the release status list.
DEFAULT
VALUES
LATEST
SCOPE
Site preference.
ClearCase Integration preferences

The ClearCase Integration allows you to integrate IBM’s software configuration
management tool with Teamcenter’s product data management functionality.
For more information about this integration, see the ClearCase Integration Guide.
Use ClearCase Integration preferences to implement the installation of the
integration, and modify the integration behavior.
SCM_ClearCase_Server
DESCRIPTION
Establishes and verifies the connection with the ClearCase server. Populate this
preference during the integration server installation. Add all the ClearCase servers
you want to configure with Teamcenter to this preference.
VALID
VALUES
Accepts multiple string values. Must be the address of the ClearCase server.
DEFAULT
VALUES
None.

SCOPE
Site preference.
SCM_ClearCase_UNCO_Keep_Version
DESCRIPTION
Determines whether .keep files are preserved in ClearCase when users use the
uncheckout command.
VALID
VALUES
true Any .keep files are preserved in ClearCase when users use
the uncheckout command.
false Any .keep files are not preserved in ClearCase when users use
the uncheckout command.
DEFAULT
VALUES
true
SCOPE
User preference.
SCM_CheckIn_Identical_Version
DESCRIPTION
Determines whether Teamcenter invokes the SCM checkin command when the
checkedout version is identical to the previous version of the element.
VALID
VALUES
False Teamcenter does not invoke the SCM checkin command and
instead invokes the SCM command to cancel the checkedout
version.
True Teamcenter invokes the SCM checkin command which checks
in the element, provided the SCM environment rules allow
checkin of identical versions. It should be set to true only
if there is no Clearcase trigger set which would stop the
operation.
DEFAULT
VALUES
False
SCOPE
Site preference.

Chapter
24 EDA preferences
EDA_AddSchematicItemToCCABOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1
EDA_BOMTemplate_pcb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1
EDA_BOMTemplate_sch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2
EDA_CCABaseItemTypeDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2
EDA_CCAItemTypeDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2
EDA_CheckInOptionDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3
EDA_CheckComponentExistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3
EDA_CombinedBOMOptionDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3
EDA_CombinedViewableOptionDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-4
EDA_ComponentItemTypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-4
EDA_DefinePWBWith . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-5
EDA_DerivedDataConfigDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-5
EDA_DesignReviseSync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-5
EDA_FutureVariantName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-6
EDA_PcbBOMOptionDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-6
EDA_PcbLockingDynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-7
EDA_PcbViewableOptionDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-7
EDA_PreferredLocalTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-7
EDA_PWBItemTypeDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-8
EDA_SaveAsFolderDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-8
EDA_SaveIntermediateDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-8
EDA_SchematicBOMOptionDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-9
EDA_SchematicItemTypeDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-9
EDA_SchematicLockingDynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-9
EDA_SchematicViewableOptionDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-10
EDA_SimulationLockingDynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-10
EDA_ViewType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-10
EDA_ReconcilePartsRevRule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-11
EDA_CCAVariantItemTypeDefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-11

Chapter
24 EDA preferences
Use the following preferences to determine EDA behavior.
EDA_AddSchematicItemToCCABOM
DESCRIPTION
Controls the addition of a schematic design item to an associated CCA(s) BVR when
a schematic design is created or copied.
VALID
VALUES
True
False
DEFAULT
VALUES
False
SCOPE
Site preference.
EDA_BOMTemplate_pcb
DESCRIPTION
Defines a file to be used as the PCB BOM template.
Note
This preference is created for the user as per requirement.
VALID
VALUES
A string containing a fully qualified path to the PCB BOM template file.
DEFAULT
VALUES
Undefined, which defaults to
%TCEDAECAD_ROOT%/Cadence/pcb/tcedaPcbTemplate.bom.
SCOPE
User preference.

Chapter 24 EDA preferences
EDA_BOMTemplate_sch
DESCRIPTION
Defines a file to be used as a schematic BOM template.
Note
Note
This preference is used only by the EDA Cadence Schematic tool integration.
VALID
VALUES
A string containing a fully qualified path to the schematic BOM template file.
DEFAULT
VALUES
Undefined, which defaults to
%TCEDAECAD_ROOT%/Cadence/sch/tcedaSchTemplate.bom.
SCOPE
User preference.
EDA_CCABaseItemTypeDefault
DESCRIPTION
Represents the default UI item type used for CCABase item creation.
VALID
VALUES
String. Teamcenter EDACCABase item type or a valid subtype.
DEFAULT
VALUES
EDACCABase
SCOPE
All.
EDA_CCAItemTypeDefault
DESCRIPTION
Represents the default UI item type used for CCA item creation.
VALID
VALUES
String. Any valid Teamcenter item type.
DEFAULT
VALUES
Item
SCOPE
All.

EDA preferences
EDA_CheckInOptionDefault
DESCRIPTION
Defines the default checkin option value. This preference preselects the Check-In
option on the Save As and Save dialogs if set to true.
Note
VALID
VALUES
true
false
DEFAULT
VALUES
false
SCOPE
User preference.
EDA_CheckComponentExistence
DESCRIPTION
Defines whether to check for components in Teamcenter before saving a design. Set
to 1 (true) to check if prerequisite components exist on the server. If components
do not exist in Teamcenter, then the save is aborted. If this preference is set to 0
(false), then any components that do not exist in Teamcenter are created as empty
items during the save.
VALID
VALUES
1
0
DEFAULT
VALUES
1
SCOPE
Site preference.
EDA_CombinedBOMOptionDefault
DESCRIPTION
Specifies the default value for the following combined ECAD design tool actions:
• Check-In
• Save
• Save As

Note
This preference replaces all combined ECAD design tool-specific BOM option
preferences.
VALID
VALUES
FromPCB
FromSchematic
WithoutBOM
DEFAULT
VALUES
FromPCB
SCOPE
All.
EDA_CombinedViewableOptionDefault
DESCRIPTION
Defines the Generate Viewables option value for the ECAD combined design tool.
If set to true, this preference preselects the Generate Viewables check box on the
Save and Save As dialog boxes.
VALID
VALUES
FromPCB
FromSchematic
WithoutViewable
DEFAULT
VALUES
FromPCB
SCOPE
All.
EDA_ComponentItemTypes
DESCRIPTION
Represents the complete set of all Teamcenter base types that should be supported
by EDA as components.
Note
If EDA library is installed, the default view contains both EDAComp and
EDAComPart.
VALID
VALUES
String. Any valid Teamcenter electrical component type used in ECAD designs.
DEFAULT
VALUES
EDAComp

EDA preferences
SCOPE
Site preference.
EDA_DefinePWBWith
DESCRIPTION
Specifies that the printed wire board should be defined as part of the schematic or
PCB Save As operation.
VALID
VALUES
Schematic
PCB
DEFAULT
VALUES
Schematic
SCOPE
Site preference.
EDA_DerivedDataConfigDefault
DESCRIPTION
Defines a default EDA derived data configuration for use by the Teamcenter EDA
when ECAD designs are saved.
An administrator can create derived data configurations using the Business Modeler
IDE. After a configuration is created, the administrator must set this preference to
the name of the derived data configuration. There may be multiple configurations
created in the Business Modeler IDE, but an administrator can point to only one of
them through this preference.
VALID
VALUES
A string containing the name of an EDA derived data configuration created in the
Business Modeler IDE.
DEFAULT
VALUES
edaDefaultConfig
SCOPE
All.
EDA_DesignReviseSync
DESCRIPTION
Specifies that both CCA items or EDACCABase and EDASchem are to be revised
together during a Save As operation.
VALID
VALUES
True

False
DEFAULT
VALUES
False
SCOPE
Site preference.
EDA_FutureVariantName
DESCRIPTION
Represents the name used for the future variant when a variant design is created
and no variants are defined by the ECAD designs.
VALID
VALUES
String. Any valid EDA CCA variant name.
DEFAULT
VALUES
futureVariant
SCOPE
Site preference.
EDA_PcbBOMOptionDefault
DESCRIPTION
Specifies the default value for the following ECAD PCB design tool actions:
• Check-In
• Save
• Save As
Note
This preference replaces all ECAD design tool-specific PCB BOM option
preferences.
VALID
VALUES
WithBOM
WithoutBOM
DEFAULT
VALUES
WithBOM
SCOPE
All.

EDA preferences
EDA_PcbLockingDynamic
DESCRIPTION
Enables dynamic locking of CCA BVR(s) during a PCB design checkout.
VALID
VALUES
True
False
DEFAULT
VALUES
True
SCOPE
Site preference.
EDA_PcbViewableOptionDefault
DESCRIPTION
Specifies the Generate Viewables option value for the ECAD PCB design tool. If
set to true, this preference preselects the Generate Viewables check box on the
Save, and Save As dialog boxes.
VALID
VALUES
WithViewable
WithoutViewable
DEFAULT
VALUES
WithViewable
SCOPE
All.
EDA_PreferredLocalTS
DESCRIPTION
Defines whether the EDA integration should prefer to run the ECAD translation
locally on the same machine as the EDA client.
VALID
VALUES
1 Specifies local translation.
0 Specifies remote translation.
DEFAULT
VALUES
1
SCOPE
Site preference.

EDA_PWBItemTypeDefault
DESCRIPTION
Represents the default UI item type used for PWB item creation.
VALID
VALUES
String. A valid Teamcenter item type.
DEFAULT
VALUES
Item
SCOPE
All.
EDA_SaveAsFolderDefault
DESCRIPTION
Defines the default Teamcenter folder when saving new CCAs, schematics, and
PCB designs.
Note
VALID
VALUES
A valid Teamcenter folder name.
DEFAULT
VALUES
Undefined; no default
SCOPE
All.
EDA_SaveIntermediateDS
DESCRIPTION
Defines whether to save the schematic or PCB intermediate dataset used by ECAD
translation to generate the XFATF or XSCH neutral viewable files.
VALID
VALUES
1 Indicates the intermediate file is saved.
0 Indicates the intermediate file is not saved.
DEFAULT
VALUES
0
SCOPE
Site preference.

EDA preferences
EDA_SchematicBOMOptionDefault
DESCRIPTION
Specifies the default value for the following ECAD schematic design tool actions:
• Check-In
• Save
• Save As
Note
This preference replaces all ECAD design tool-specific schematic BOM option
preferences.
VALID
VALUES
WithBOM
WithoutBOM
DEFAULT
VALUES
WithBOM
SCOPE
All.
EDA_SchematicItemTypeDefault
DESCRIPTION
Represents the default UI item type used for schematic item creation.
VALID
VALUES
String. Teamcenter EDASchem item type or a valid subtype.
DEFAULT
VALUES
EDASchem
SCOPE
All.
EDA_SchematicLockingDynamic
DESCRIPTION
Enables dynamic locking of CCA BVRs during a schematic design checkout.
VALID
VALUES
True
False

DEFAULT
VALUES
False
SCOPE
Site preference.
EDA_SchematicViewableOptionDefault
DESCRIPTION
Defines the Generate Viewables option value for the ECAD schematic design tool.
If set to true, this preference preselects the Generate Viewables check box on the
Save, and Save As dialog boxes.
VALID
VALUES
WithViewable
WithoutViewable
DEFAULT
VALUES
WithViewable
SCOPE
All.
EDA_SimulationLockingDynamic
DESCRIPTION
Enables dynamic locking of CCA BVRs during a simulation design checkout.
VALID
VALUES
True
False
DEFAULT
VALUES
True
SCOPE
Site preference.
EDA_ViewType
DESCRIPTION
Specifies the BOM view type that Teamcenter EDA uses to read and write product
structure information.
VALID
VALUES
A single string that is a valid Teamcenter BOM view type

EDA preferences
DEFAULT
VALUES
Product structure default view type that is specified by an empty value
SCOPE
Site preference.
EDA_ReconcilePartsRevRule
DESCRIPTION
Specifies the revision rule to be used by ECAD BOM compare, when expanding the
corresponding Teamcenter CCA item revision first level children of an ECAD design.
VALID
VALUES
Any valid Structure Manager revision rule name.
DEFAULT
VALUES
Any Status; No Working
SCOPE
Site preference.
EDA_CCAVariantItemTypeDefault
DESCRIPTION
Specifies the default user interface item type that Teamcenter EDA uses for CCA
variant item creation on the EDA Save As Variant Page.
VALID
VALUES
Item or a valid Teamcenter item subtype.
DEFAULT
VALUES
Item
SCOPE
All.

Chapter
25 Quality data preferences
DPVAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1
DPVClusterGroup Revision_DefaultChildProperties . . . . . . . . . . . . . . . . . . . 25-1
DPVClusterGroup Revision_shown_relations . . . . . . . . . . . . . . . . . . . . . . . . 25-2
DPVClusterGroupContent_relation_primary . . . . . . . . . . . . . . . . . . . . . . . . . 25-3
DPV_ccuaservice_url . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-4
DPV_logdatapurge_days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-4
DPV_rawdata_location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-5

Chapter
25 Quality data preferences
Tecnomatix Dimensional Planning and Validation (DPV) is a quality management

solution you can easily integrate into your Teamcenter environment. DPV enables
the extended enterprise to collect, manage, dimensionally analyze, and report on
quality measurement information. This report generation solution provides rapid
access to design and manufacturing information that directly influence’s your
enterprise’s quality targets.
Use DPV preferences to modify DPV behavior.
For more information about DPV, see Getting Started with Dimensional Planning
and Validation and the Dimensional Planning and Validation Administration Guide.
DPVAdmin
DESCRIPTION
By default, in DPV Measurements, all users can change the activation state of
measurement data events (deactivate or activate them). To protect your data,
define DPVAdmin to hold the names of the groups of users who can change the
activation state. Groups not in DPVAdmin can read the events but they cannot
their activation state. If no preference is defined, all users have the privilege to
change the activation state.
Note
VALID
VALUES
string Group or groups who can deactivate/activate data. Separate
each group with a comma.
SCOPE
Site preference.
DPVClusterGroup Revision_DefaultChildProperties
DESCRIPTION
Specifies whether a specific relationship between two item revisions is listed
when you select the Paste Special command. For DPV, the relationship

Chapter 25 Quality data preferences
DPVCLUSTERGROUPCONTENT is defined between clusters and cluster groups.

Therefore, select this value to have this relationship appear in the Paste Special
command in Teamcenter.
VALID
VALUES
One of the following relationships. To show the DPV cluster/cluster group
relationship, select DPVClusterGroupContent.
TC_Generic_Architecture
structure_revisions
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_UG_udf
IMAN_UG_altrep
IMAN_UG_scenario
IMAN_Simulation
IMAN_Rendering
IMAN_Motion
IMAN_3D_snap_shot
view
release_status_list
representation_for
TC_ProductManua
BOM_Rollup
TC_Attaches
TC_sst_record
ProcessSimulate_Details
KinematicsRelation
DPVClusterGroupContent
DEFAULT
VALUES
The values listed under Valid Values.
SCOPE
Site preference.
DPVClusterGroup Revision_shown_relations
DESCRIPTION

Quality data preferences
VALID
VALUES
One of the following relationships. To show the DPV cluster/cluster group
relationship, select DPVClusterGroupContent.
PSBOMViewRevision
IMAN_specification
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_UG_udf
IMAN_UG_altrep
IMAN_UG_scenario
IMAN_Simulation
IMAN_Rendering
IMAN_Motion
IMAN_MEMfgModel
IMAN_snapshot
IMAN_3D_snap_shot
TC_ProductManual
BOM_Rollup
TC_Attaches
ProcessSimulate_Details
IMAN_MEFeature
Site Specific
Corporate Specific
DPVClusterGroupContent
DEFAULT
VALUES
The values listed under Valid Values.
SCOPE
Site preference.
DPVClusterGroupContent_relation_primary
DESCRIPTION

Chapter 25 Quality data preferences
VALID
VALUES
DPVClusterGroup
DPVClusterGroup Revision
DEFAULT
VALUES
DPVClusterGroup
DPVClusterGroup Revision
SCOPE
Site preference.
DPV_ccuaservice_url
DESCRIPTION
Specifies the URL for the Custom Cache Updating Application (CCUA) Service
used in the triggers functionality.
For more information, see the Dimensional Planning and Validation Administration
Guide.
VALID
VALUES
Set the URL, such as http://pni6w032/CCUATrigger/CCUA.asmx.
DEFAULT
VALUES
None.
SCOPE
Site preference.
DPV_logdatapurge_days
DESCRIPTION
Sets the number of days to retain log data.
Guide.
INTEGER
Specify the number of days to retain the log data. If it is set to x, log data that is
more than x days old is deleted automatically (no other user action is required).
DEFAULT
VALUES
None.
SCOPE
Site preference.

Quality data preferences
DPV_rawdata_location
DESCRIPTION
Specifies where the measurement data is stored, either in Teamcenter or an external
measurement database.
Guide.
VALID
VALUES
0 The measurement data is stored within Teamcenter.
1 The measurement data is stored in an external measurement
database.
SCOPE
Site preference.

Chapter
26 ADA License preferences
ADA_license_administration_privilege . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1
ADA_enable_subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1

Chapter
26 ADA License preferences
The ADA License application allows you to manage ADA licenses. Use the ADA
License application preferences to configure access to the ADA License application.
For more information about the ADA License application, see the Authorized Data
Access License Guide.
ADA_license_administration_privilege
DESCRIPTION
Specifies the privilege required to perform actions in the ADA License application,
attach or detach license from workspace objects in My Teamcenter, or view audit logs
of license activity from the ADA License application.
Note
If a user is not authorized access through a group or role membership, the
application opens in read-only mode for that user. Authorization is configured
using the Authorization application.
VALID
VALUES
ITAR_ADMIN Allows users with the ITAR Admin privilege access to the
ADA License application.
IP_ADMIN Allows user with the IP Admin privilege access to the
Authorized Data Access application.
Administer_ADA_ Allows users with the Administer ADA Licenses privilege
Licenses access to the ADA License application.
DEFAULT
VALUE
ITAR_ADMIN
SCOPE
Site preference.
ADA_enable_subgroups
DESCRIPTION
Specifies whether or not subgroup members of the top-level groups can be authorized
access to workspace objects with attached licenses when the top-level group is not
authorized access. In Teamcenter versions prior to 8.1L, only top-level groups can be

Chapter 26 ADA License preferences
authorized due to a limit on the length of the string that passes the authorization
information. This allows access to all subgroups of the top-level group in prior
versions. Therefore, if your environment shares license information among sites that
are on versions prior to 8.1L, this must be set to false to prevent data loss.
VALID
VALUES
true Allows subgroups of groups authorized access to objects with
attached licenses to access the objects. If you set the value to
true, all Teamcenter sites that share data in your environment
must be upgraded to Teamcenter 8.1L to prevent data loss.
false Does not allow subgroups of groups to be granted authorized
access to objects with attached licenses from accessing the
objects.
DEFAULT
VALUE
false
SCOPE
Site preference.

Appendix
A Glossary

Appendix
A Glossary
access control list (ACL)

Access Manager component that contains a list of accessors and the privileges
granted, denied, and not set for each accessor.
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).
action handler
Handler used to extend and customize 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.
action rule
Business rule that defines the actions required in different time phases (precondition,
preaction, and postaction) for create, save as, and delete operations. Action rules are
applied to item, item revision, and dataset.
active mode
Management of application files in a way that allows their use by both an application
and Teamcenter. There are two categories of active interaction between Teamcenter
and an application: encapsulation and Integration. Compare with passive mode.
AM
See Access Manager (AM).
AP212
See STEP AP212.
appearance
Sequence of occurrences that describes a unique path through an exploded structure.
An appearance corresponds to a unique instance of the component that is referenced
by the leaf node of the path within the top-level assembly. An appearance may have
spatial data associated with it, allowing spatial searches.
PLM00026 F Preferences and Environment Variables Reference A-1

Appendix A Glossary
Appearance Configuration
Teamcenter application used to configure the use of appearance:
• Defining the appearance sets for which the site tracks appearances.
• Configuring the mapping of occurrence notes into appearance attributes.
appearances
Cache of configured BOM lines in the context of a specific top-line item. Appearances
are created to allow quick searches of the entire structure.
appearance set
Collection of appearances created for an appearance root and updated each time a
part is released within the root product with the appropriate release status.
Application Integration Environment

Teamcenter component for managing the import and export of documents into
Teamcenter. Application Integration Environment is a common component across
integrations that include applications in fields such as CAE and ME.
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.
architecture breakdown
Structure used to lay out, plan, and control evolution of product structures. An
architecture breakdown displays product information in terms of engineering
content and product variability, including variant options and values and defining
variant conditions for occurrences.
architecture element
Element contained within the architecture structure, including occurrences, BOM
view revisions, ME appearance path nodes, and so on.
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.
assigned FSC
FMS server cache assigned as the volume or cache server for an FMS client cache.
Each FMS client cache requires an assigned FSC to provide it with access to files. An
assigned FSC is typically the FSC nearest to the client host. In small deployments,
an assigned FSC can also serve as the parent FSC.
attribute
Named storage variable that describes an object and is stored with the object. Users
can search the database for objects using the object’s attributes.
In an object, an attribute is a name/value pair; in the database, an attribute is a field.
Audit Manager
Teamcenter application that enables a system administrator to define audit
definition objects, enable/disable audit trail logging, and control audit log access.
A-2 Preferences and Environment Variables Reference PLM00026 F

Glossary
Audit definition objects create audit logs that users can view from Teamcenter
applications. Users can audit any Teamcenter object and event type with an audit
definition.
Authorization
Teamcenter application that enables access control of administrative applications
and utilities.
baseline
Collection of items and the relationships between the items that is established to
ensure their continued existence. It enables their configuration to be reconstructed
and audited. Baselines are often created to preserve the state of a design at a
particular checkpoint. You can baseline precise or imprecise structures.
blobby volume
Alternate volume used to store data while backing up volumes and databases. The
blobby volume provides continuous Teamcenter availability.
BOM
Bill of materials. See also design bill of materials and manufacturing bill of
materials.
BOM view
Teamcenter object used to manage product structure information for an item.
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.
Business Modeler IDE

Teamcenter application that enables a customer to define the following data model
objects: business objects, classes, attributes, lists of values, and rules.
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.

Appendix A Glossary
change type
Template of a change process. Change types are created by a system administrator
using the Business Modeler IDE.
Change Viewer
Teamcenter application used to manage the process of controlling changes to a
product’s definition and configuration. Change Viewer provides an auditable history
of the objects used in a process, making an object’s uses traceable. A site can use
Change Viewer to propose, incorporate, review, and approve changes. Change
Viewer can also be used to track and report change history and to notify members of
changes to their organization.
class
Set of objects that share the same list of attributes but distinguishable by the value
the attributes acquire for specific objects. For example, the Automobile class can be
defined by the brand, color, and price, but each car associated to the Automobile
class has a different brand, color, and price combination.
Classification
Teamcenter application that utilizes a classification hierarchy to categorize product
data.
Classification Administration
Teamcenter application that enables a system administrator to define the groups,
classes, subclasses, and views that form the Classification hierarchy.
classification hierarchy tree

Display of the classification structure—groups, classes, subclasses, and views—in a
tree-like structure to maintain context during use of Classification Administration.
clearance database
Teamcenter database that stores the results of clearance analyses performed on
assemblies in the rich client DesignContext, Structure Manager, and Multi-Structure
Manager applications.
clearance database server

Server required to enable users to perform clearance analysis in the rich client
DesignContext, Structure Manager, and Multi-Structure Manager applications. A
batch process performs a clearance analysis on an assembly and Teamcenter stores
the results in the clearance database.
Client
Role played by a software component of a system when it requests particular services
be performed on its behalf by another entity, a server. See also server.
client tier
Teamcenter architectural tier that comprises the Teamcenter clients, Teamcenter
integrations with third-party applications, such as Teamcenter’s Integration for
Microsoft Office and Teamcenter Engineering 2007 Integration for AutoCAD, and
the third-party applications themselves, such as Microsoft Office and AutoCAD.
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

Glossary
the relationships of interest and the actions to occur when these relationships are
encountered.
component
Objects used to build up an assembly or subassembly.
configuration context
In Appearance Configuration, a revision rule used to configure the structure.
Configuration context can contain only release status entries.
Data Integration Services Adapter

Teamcenter software component that integrates Teamcenter’s lifecycle visualization
with both the thin client and the rich client.
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.
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. Deep copy rules can be applied to save-as and revise item revisions.
delivery unit
Subassembly that is manufactured separately and delivered to the assembly plant
as a consumed part. One of the operations in the assembly process uses the delivery
unit as a consumed part. The components of a delivery unit are not consumed in
any of the operations.
design bill of materials

List of components and subassemblies used to define an assembly structure, and
the representation of the assembly structure. Compare with manufacturing bill
of materials.
DesignContext
Teamcenter application that enables users to quickly focus on a particular work part
and any parts affected within the context of a change to that part. Users can select
a product item and configure revisions of components, configure variants of the
assembly, review the set of components, retrieve the components, and initialize their
display in a CAD application or a visualization application.
direct model dataset

Dataset containing a JT (visualization) file.
effectivity
Identification of the valid use of an aspect of product data tracked by date, event,
unit, or other scheme. You can specify a start definition, end definition, or both for
a particular effectivity.

Appendix A Glossary
effectivity rule
Rule used to set effective dates on released products and processes with a released
status.
eIntegrator Admin
Teamcenter application that provides a simple integration mechanism you can use
to integrate external data with Teamcenter. eIntegrator Admin maps external data
systems into equivalent objects in its database. The data can then be imported into
the database as forms.
Embedded Software Solutions

Optional extension to Structure Manager and My Teamcenter that allows you to
manage embedded software binaries as part of the product structure.
encapsulation
Active-mode relationship between an application and Teamcenter in which the
application is brought into the Teamcenter environment. Encapsulation allows you
to launch the application using a Teamcenter dataset object, export data to the
application, work in the application, and import data back into the Teamcenter
database during a session. The import and export operations between Teamcenter
and the encapsulated application are executed from within Teamcenter and
the actual transfer of files is transparent to the user. See also active mode and
Integration.
environment variables script

Teamcenter script (tc_profilevars) that sets variables for the Teamcenter
environment. This script sets all Teamcenter environment variables except
TC_ROOT and TC_DATA.
ERP Connect to SAP

Teamcenter integration that allows the controlled, auditable transfer of product
information from Teamcenter to SAP.
FCC
See FMS client cache (FCC).
FCC configuration file

File that configures an individual FMS client cache (fcc.xml). The FCC configuration
file defines such values as the parent FMS server cache location and the location and
size of the client caches. Values defined in the FCC configuration file can override
default values defined in the FSC configuration file.
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

Glossary
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.
find number
Number that identifies individual occurrences (or groups of occurrences) within a
single-level assembly. Components are ordered by find number within an assembly.
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’s 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 type
Special type of the general POM Form class, which can have its own set of properties
(attributes) associated.

Appendix A Glossary
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 timeout value. It can also
define default values for FCCs and other FSCs.
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.
Global Services Foundation

Web application that enables your enterprise to access information stored in
virtually any type of electronic data source that manages your enterprise data.
Running on a standard commercial Web application server, the server components
of Global Services Foundation enable communication among the data sources and
between users and the data sources. All components of Global Services Foundation
use standard Web technology: Extensible Markup Language (XML), Extensible
Stylesheet Language (XSL), and the Sun Java programming language. Users access
Global Services Foundation from a commercial Web browser using the standard
technologies of Web browsers, primarily support for HyperText Markup Language
(HTML) forms and small Java applets.
group
Type of class that does not have a list of attributes associated with it; highest level
in the classification hierarchy.
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.
I-deas
Siemens PLM Software’s integrated CAD/CAM/CAE solution that is used to design,
analyze, test, and manufacture products.

Glossary
IDSM server
Integrated Distributed Services Manager, a network node that runs a daemon process
to handle the transfer of data objects among sites in a Multi-Site Collaboration
network. One IDSM server node must be designated for each Teamcenter database
from which objects are published; each server node can act for one database only.
incremental change
Engineering change that collects several individual changes to components or
attachments in a structure, allowing them to be released simultaneously. An
incremental change is released and effectivity is applied to it by attaching an
appropriate release status.
Integration
Active-mode relationship between an application and Teamcenter in which
Teamcenter is brought into the application. The application drives Teamcenter
to provide the functionality, such as implicit checkout when data is modified, and
reading and writing data directly from Teamcenter in a secured way. Data is
exported (pushed) and imported (pulled) as needed.
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 relation

Description of an association between a Teamcenter item revision and a piece of
information that describes or is related to the item revision.
JT cache
Data Integration Services Adapter cache of JT files managed by the JT cache service
and accessible to Teamcenter’s lifecycle visualization users. See also world access
cache and limited access cache.
JT cache populator
Stand-alone Data Integration Services Adapter utility that prepopulates the JT
cache with JT part and assembly files.
Lifecycle Visualization
Siemens PLM Software suite that provides enterprise-wide product visualization
capabilities. Lifecycle Visualization can be configured for use with both the
Teamcenter rich client and thin client as a stand-alone application.
The software suite includes Teamcenter’s lifecycle visualization base, Teamcenter’s
lifecycle visualization standard, Teamcenter’s lifecycle visualization professional,
and Teamcenter’s lifecycle visualization mockup.

Appendix A Glossary
limited access cache

Data Integration Services Adapter cache of JT files that are accessible only to
privileged users. The limited access cache is managed by the JT cache service.
Permission checks are performed when a user accesses a file from the limited access
cache. Compare with world access cache.
manufacturing bill of materials

Defines how the product is manufactured, rather than how it is designed. Compare
with design bill of materials.
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.
Mechatronics
Integration of mechanical engineering with electronics and intelligent computer
control in the design and manufacture of products and processes.
Mentor Graphics Integration

Teamcenter integration that allows users to store and manage Mentor Graphics
Design Manager objects in Teamcenter.
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.
Multi-Structure Manager
Teamcenter application that enables users to view and manipulate data in a specific
context.
My Teamcenter
Teamcenter rich client application that is the main access point for managing
product information. My Teamcenter provides the functionality for creating objects
in the Teamcenter database, querying the database for objects, checking in and
checking out objects, and managing tasks. Users can also open objects, automatically
launching the related application.
Each user has a personal My Teamcenter window that displays product information
as graphical objects. Although users share product information across the enterprise,
they organize this information individually in personal workspaces.

Glossary
named ACL
Named group of access controls. See also access control list (ACL).
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.
NX
Siemens PLM Software’s next-generation digital product development system that
helps companies transform the product life cycle. It provides the complete life cycle
of development processes in product design, manufacturing, and simulation.
NX Integration
Integration between Teamcenter and NX. NX Integration users have full access
to the Teamcenter user interface from NX, and they can also access NX from the
Teamcenter user interface.
Teamcenter Integration for NX and NX Integration have the identical user
interface in NX. The difference between the two products is the level of Teamcenter
functionality available. Teamcenter Integration for NX excludes certain Teamcenter
functionality, such as workflow and product structure editing.
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 launcher
Launches another Teamcenter product from a linked object. Each Teamcenter
product has an object launcher. See also remote workflow.

Appendix A Glossary
occurrence
Hierarchical structure relationship between the immediate parent assembly and
its child component item or item revision in a precise assembly. Sometimes called
relative occurrence.
occurrence effectivity
Method of configuring the occurrences in a structure with effectivity. See also
effectivity.
ODBC driver
Teamcenter integration that allows ODBC-compliant applications such as Actuate
Report Writer, Crystal Reports, Microsoft Excel, and Access to extract data from a
Teamcenter database for building reports.
ODS server
See object directory services server.
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.
passive mode
Management of application files from outside an application. Users do not have
access to Teamcenter while running the application in passive mode. Data must be
exported (pushed) from Teamcenter to the application before it can be worked on
and then imported (pulled) into Teamcenter after it has been modified. Compare
with active mode.
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.
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.

Glossary
POM
See persistent object manager (POM).
port
Occurrence of an interface port that represents the access point of a functional
module in a given context, for example, a USB 2.0 port on a computer processor.
preference
Configuration variable stored in a Teamcenter database and read when a Teamcenter
session is initiated. Preferences allow administrators and users to configure many
aspects of a session, such as user logon names and the columns displayed by default
in a properties table.
preference scope
Hierarchical range for which a Teamcenter preference can be set. The scope of a
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
Automation of a business procedure, describing the individual tasks and task
sequences required to complete a business procedure.
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.
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 team member

Team member who does not have privileges to assign objects to or remove objects
from their projects. Compare with privileged team member.
properties
Keys and values that specify the configuration settings for an application in the
Teamcenter rich client.
RDV
See Repeatable Digital Validation.
relation
Description of an association between a Teamcenter object and a piece of information
that describes or is related to the object.

Appendix A Glossary
release status
Status associated with a workspace object when it is released through a workflow
process.
remote workflow
Teamcenter component that enables users to create links between Teamcenter
objects and objects in other Teamcenter products, such as Teamcenter’s portfolio,
program and project management. Users can then launch the linked Teamcenter
product from within either the rich client or the thin client.
Repeatable Digital Validation

Combination of software and processes that enables on-demand digital mockups for
use throughout the product development lifecycle. Repeatable Digital Validation
services are required for using QPL-based DesignContext.
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.
rich client framework

Component of the rich client that integrates and runs various applications from a
common platform. These applications can be off-the-shelf applications such as NX
CAD/CAM/CAE, Microsoft Office, custom applications, and Java plug-ins.
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
Object that models the type of work a user is expected to perform in a group.
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.
role preference
Teamcenter preference applying to an entire role.
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.

Glossary
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.
server
System software component that performs a specifically defined set of software
services on behalf of one or more clients. In a typical Teamcenter installation,
servers are centralized on dedicated hosts that support a large number of clients.
Clients are distributed on hosts connected to the servers via various networking
techniques. See also Client.
single sign-on
Mechanism that allows a user to log on once to multiple services. Following a single
sign-on to Teamcenter, the user is connected to multiple services without logging
in to each service.
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.
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.
Solid Edge Manager

Teamcenter integration that enables users to use Teamcenter to manage files from
within Solid Edge.
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.

Appendix A Glossary
STEP Translator
Teamcenter application that enables users to import product information into a
Teamcenter database and to export Teamcenter data via STEP-compliant physical
files.
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.
subassembly
Assembly that is built into the assembly structure of another assembly or intended
for that use. In a manufacturing view, either a delivery unit or a workpiece. See
also delivery unit and workpiece.
subscription
Combination of a workspace object and event to 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.
Subscription Monitor
Teamcenter application that enables a system administrator to query subscriptions
created in the database, to monitor and delete subscription events and actions,
and to generate statistical reports in either text or bar chart format regarding
subscriptions, events, and actions.
supersedure
Manually created relation that graphically displays deleted components and the
components that replace them. A supersedure is always created in the context of a
parent assembly. Thus a single component can be used in more than one supersedure
if it is used in different parent assemblies. A supersedure can be created for changes
of part number or of quantity, but not for changes in a part revision.
system administrator
Teamcenter user who is a member of the system administration group.
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.
Teamcenter’s Integration for Microsoft Office

Teamcenter integration that enables users to browse Teamcenter directly and create
objects in Teamcenter, check objects in and out of Teamcenter, and save files in

Glossary
Teamcenter. The Teamcenter’s Integration for Microsoft Office consists of ActiveX

controls plugged into Microsoft Office.
Teamcenter’s manufacturing process management

Teamcenter manufacturing process design and management system. Teamcenter’s
manufacturing process management comprises several user applications, for
example, Plant Designer, Manufacturing Process Planner, Part Planner, Report
Generator, and Resource Manager.
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 Integration for NX

NX-based entry-level set of Teamcenter data management functions, such as
vaulting, checking in, checking out, revision management, attribute synchronization,
and searching CAD data. Teamcenter Integration for NX manages NX files and
their data without exposing the user to full Teamcenter functionality. Teamcenter
Integration for NX users have only limited access to the Teamcenter user interface.
Teamcenter Integration for NX and NX Integration have the identical user
interface in NX. The difference between the two products is the level of Teamcenter
functionality available. Teamcenter Integration for NX excludes certain Teamcenter
functionality, such as workflow and product structure editing.
Teamcenter Integration for NX I-deas

Product that integrates Teamcenter and I-deas to provide a single data management
environment for users. Teamcenter Integration for NX I-deas users author their
data in I-deas and manage the data in Teamcenter. Teamcenter Integration for NX
I-deas includes the My Teamcenter user interface and the I-deas Data Services (IDS)
and Team Data Sharing (TDS) modules. See also I-deas.
tessellation
Process that translates a CAD file to a visualization file.
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.
transient volume
Operating system directory controlled by Teamcenter and used to store temporary
data for transport of reports, PLM XML, and other nonvolume data between the Web
tier and client tier in a deployment of the Teamcenter four-tier architecture.
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.

Appendix A Glossary
variant condition
Rules applicable to one component in a product structure.
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).
volume
Operating system directory controlled by Teamcenter and used to store the files
managed by Teamcenter. When a user performs an action that causes Teamcenter
to create a file, the file is created in the Teamcenter volume. Users cannot directly
access the files in Teamcenter volumes; they must do so via a Teamcenter session.
Web Browser
Teamcenter application that provides access to Internet Web pages from within
the rich client framework. The Web browser is a rich client window that acts as a
Web browser, enabling you to navigate and view Web pages within the rich client
rather than switching to a separate Web browser. The 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.
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.
workpiece
Intermediate state of the product during the manufacturing process. In each step
of the manufacturing process, the workpiece is positioned in the work area and the
work instructions are performed. The resulting workpiece then flows to the next
operation in the sequence, where the next operation is performed.
world
All users regardless of group or role.
world access cache

Data Integration Services Adapter cache of JT files that are accessible to all users.
The world access cache is managed by the JT cache service. No permission checks
are performed when a user accesses a file from the world access cache. Compare
with limited access cache.

Glossary
XML object list

Data Integration Services Adapter file that is formatted in XML and provides a list
of the parts and assemblies to be populated into the JT cache.

Index
Numerics/Symbols ActivityEntryValue.SUMMARYRENDERING
2D_Viewer_default_load_relation preference . . . . . . . . . . . . . . . . . . . . 22-89
preference . . . . . . . . . . . . . . . . . . . . 20-12 ActivityEntryValue.RENDERING
3DMarkup_relation_primary preference . . . . . . . . . . . . . . . . . . . . 22-89
preference . . . . . . . . . . . . . . . . . . . . . 21-1 ADA License preferences . . . . . . . . . . . 26-6
ADA_enable_subgroups . . . . . . . . . . 26-1
ADA_license_administration_
A
privilege . . . . . . . . . . . . . . . . . . . 26-1
AbsOccGrmCopyRules preference . . . . 19-77 ADA_allow_license_propagation . . . . . . 5-11
ACAD_COMPONENT_ONLY_MODE ADA_enabled preference . . . . . . . . . . . 5-12
preference . . . . . . . . . . . . . . . . . . . . 23-32 ADA_license_administration_privilege
Access Manager preferences . . . . . . . . 6-126 preference . . . . . . . . . . . . . . . . . . . . . 26-1
ADA_license_administration_ ADA_saveas_propagated_license_types
privilege . . . . . . . . . . . . . . . . . . . 26-1 preference . . . . . . . . . . . . . . . . . . . . . 5-12
AM_PROJECT_MODE . . . . . . . . . . . . 6-1 AdaptiveApplicationDisplay variable . . . 3-1
TC_project_validate_conditions . . . . . . 6-2 AdaptiveApplicationDisplayDuration
Accountability check preferences . . . . 20-32 variable . . . . . . . . . . . . . . . . . . . . . . . 3-1
AccountabilityCheckReportStylesheetName AdditionalAccountabilityCheckProperties
preference . . . . . . . . . . . . . . . . . . . . 20-34 preference . . . . . . . . . . . . . . . . . . . . 20-33
Action manager daemon preferences . . . . 9-8 AdditionalAsBuiltAccCheck
TC_actionmgrd_cloning_interval . . . . 9-10 Properties . . . . . . . . . . . . . . . . . . . . 22-81
TC_actionmgrd_general_processing_ AdditionalAsBuiltCompareProperties
hours . . . . . . . . . . . . . . . . . . . . . . 9-9 preference . . . . . . . . . . . . . . . . . . . . 22-80
TC_actionmgrd_max_actions_to_ AdditionalAsMaintainedAccCheckProperties
dispatch . . . . . . . . . . . . . . . . . . . 9-10 preference . . . . . . . . . . . . . . . . . . . . 22-82
TC_actionmgrd_max_subprocess_to_ AdditionalAsMaintainedCompareProperties
start . . . . . . . . . . . . . . . . . . . . . . 9-10 preference . . . . . . . . . . . . . . . . . . . . 22-82
TC_actionmgrd_sleep_minutes . . . . . . 9-8 Administration preferences
ActivityCost.MROCREATE RENDERING ADA_license_administration_
preference . . . . . . . . . . . . . . . . . . . 22-100 privilege . . . . . . . . . . . . . . . . . . . 26-1
ActivityCost_SRP0RqstActivityRevision. AM_PROJECT_MODE . . . . . . . . . . . . 6-1
MROCREATE RENDERING ATTRSHARING_datasource_connection_
preference . . . . . . . . . . . . . . . . . . . 22-100 details . . . . . . . . . . . . . . . . . . . . . 7-3
ActivityCost_SRP0ServiceOffering. ATTRSHARING_max_rows_
MROCREATE RENDERING expected . . . . . . . . . . . . . . . . . . . . 7-3
preference . . . . . . . . . . . . . . . . . . . 22-101 EINT_<adapter_name> . . . . . . . . . . . 7-1
ActivityCost_SRP0ServiceRequest. EINT_adapter_names . . . . . . . . . . . . 7-1
MROCREATE RENDERING EINT_copy_to_clipboard . . . . . . . . . . . 7-5
preference . . . . . . . . . . . . . . . . . . . 22-101 EINT_create_new_forms . . . . . . . . . . . 7-4
ActivityCost.SUMMARYRENDERING EINT_form_refresh_pref . . . . . . . . . . . 7-5
preference . . . . . . . . . . . . . . . . . . . . 22-88 EINT_global_services_datasource_
ActivityCost.RENDERING . . . . . . . . 22-88 names . . . . . . . . . . . . . . . . . . . . . 7-2
ActivityEntryValue. EINT_global_services_urls . . . . . . . . . 7-2
MROCREATERENDERING EINT_ibi_api_library . . . . . . . . . . . . . 7-6
preference . . . . . . . . . . . . . . . . . . . . 22-88
PLM00026 F Preferences and Environment Variables Reference Index-1

Index
EINT_import_selected_rows . . . . . . . . 7-4 AI_ignore_ic_flag_setting preference . . . 10-2

EINT_item_rev_pref . . . . . . . . . . . . . . 7-5 AI_Incremental_Export preference . . . . 10-2
EINT_max_num_rows . . . . . . . . . . . . 7-6 AI_request_no_dependancy
EINT_storage_type . . . . . . . . . . . . . . 7-3 preference . . . . . . . . . . . . . . . . . . . . . 10-2
EINT_update_on_save . . . . . . . . . . . . 7-4 AIE_no_BVR_edit preference . . . . . . . . 23-2
TC_Authorization_Mode . . . . . . . . . . . 8-1 AIE_overwrite_default_import_item_type
TC_current_role . . . . . . . . . . . . . . . . . 6-6 preference . . . . . . . . . . . . . . . . . . . . . 23-1
TC_Program_Preferred_Items_relation_ AIE_POST_EXPORT_SCRIPT
primary . . . . . . . . . . . . . . . . . . . . 6-3 preference . . . . . . . . . . . . . . . . . . . . . 23-2
TC_Project_DefaultChildProperties . . . 6-3 AIE_PRE_IMPORT_SCRIPT
TC_Project_PseudoFolder . . . . . . . . . . 6-3 preference . . . . . . . . . . . . . . . . . . . . . 23-3
TC_project_validate_conditions . . . . . . 6-2 ALLOC_Group_Allocation_Types
TC_set_current_project . . . . . . . . . . . 6-5 preference . . . . . . . . . . . . . . . . . . . . 19-40
TC_show_all_user_projects . . . . . . . . . 6-6 ALLOC_map_copy_allocations
ADS_Lists_DrawingRevisions_relation_ preference . . . . . . . . . . . . . . . . . . . . 19-43
primary . . . . . . . . . . . . . . . . . . . . . . 22-1 ALLOC_Product_Representation_Types
ADS_Lists_PartRevisions_relation_primary preference . . . . . . . . . . . . . . . . . . . . 19-41
preference . . . . . . . . . . . . . . . . . . . . . 22-2 ALLOC_Source_Occurrence_Types
ADS_Lists_Parts_relation_primary preference . . . . . . . . . . . . . . . . . . . . 19-42
preference . . . . . . . . . . . . . . . . . . . . . 22-2 ALLOC_source_target_cardinality
ADSTechDocument Revision_ preference . . . . . . . . . . . . . . . . . . . . 19-42
DefaultChildProperties preference . . . 22-3 ALLOC_Target_Occurrence_Types
ADSTechDocument Revision_PseudoFolder preference . . . . . . . . . . . . . . . . . . . . 19-41
preference . . . . . . . . . . . . . . . . . . . . . 22-3 Allow_Copy_As_Revision preference . . . 10-3
AE_dataset_default_keep_limit Alt_id_default_idContext_type
preference . . . . . . . . . . . . . . . . . . . . . 10-1 preference . . . . . . . . . . . . . . . . . . . . 18-57
AE_dataset_id_gen_by_type Alt_id_default_identifier_type
AE_dataset_id_postfix preference . . . . . 5-13 AltIdentifier_require_on_create
AE_dataset_id_prefix preference . . . . . 5-13 preference . . . . . . . . . . . . . . . . . . . . . . 5-1
AE_dataset_id_separator preference . . . 5-13 AM_BYPASS variable . . . . . . . . . . . . . . 3-1
AE_dataset_id_usage preference . . . . . 5-14 AM_MODE variable . . . . . . . . . . . . . . . 3-1
AE_dataset_id_use_rev preference . . . . 5-14 AM_PERFORMANCE_STATISTICS
Aerospace and Defense preferences . . . . 22-1 variable . . . . . . . . . . . . . . . . . . . . . . . 3-1
ADS_Lists_DrawingRevisions_relation_ AM_PROJECT_MODE preference . . . . . 6-1
primary . . . . . . . . . . . . . . . . . . . 22-1 API_ALWAYS_REFRESH variable . . . . . 3-2
ADS_Lists_PartRevisions_relation_ API_FILE_CACHE variable . . . . . . . . . . 3-2
primary . . . . . . . . . . . . . . . . . . . 22-2 API_JOURNAL environment variable . . 2-2
ADS_Lists_Parts_relation_ API_JOURNAL variable . . . . . . . . . . . . 3-2
primary . . . . . . . . . . . . . . . . . . . 22-2 API_NO_CACHING variable . . . . . . . . . 3-2
ADSDrawing_Revision_ API_SET_BYPASS variable . . . . . . . . . . 3-2
PseudoFolder . . . . . . . . . . . . . . . 22-1 API_ugpart_attr_titles preference . . . . 5-68
ADSTechDocument Revision_ APN_absolute_path_name_separator
DefaultChildProperties . . . . . . . . 22-3 preference . . . . . . . . . . . . . . . . . . . . 22-24
ADSTechDocument Revision_ appbar_title_contents preference . . . . 10-99
PseudoFolder . . . . . . . . . . . . . . . 22-3 Appearance Configuration
TC_customization_libraries preferences . . . . . . . . . . . . . . . . . . . . 19-1
preference . . . . . . . . . . . . . . . . . 22-3 APPR_allow_background_updates . . . 19-6
TC_LAST_USED_PATTERNS . . . . . 22-4 APPR_allow_separate_spatial_
TC_Program_Preferred_Items_relation_ processing . . . . . . . . . . . . . . . . . 19-1
primary . . . . . . . . . . . . . . . . . . . . 6-3 APPR_background_updateremail_interval_
TC_Project_DefaultChildProperties . . . 6-3 for_different_package . . . . . . . . . 19-7
TC_Project_PseudoFolder . . . . . . . . . . 6-3 APPR_background_updateremail_interval_
TC_set_current_project . . . . . . . . . . . 6-5 for_same_package . . . . . . . . . . . . 19-7
Index-2 Preferences and Environment Variables Reference PLM00026 F

Index
APPR_background_updater_admin_email_ ARM_create_itemrev . . . . . . . . . . . 23-14

address . . . . . . . . . . . . . . . . . . . 19-6 ARM_create_supersedure . . . . . . . . 23-31
APPR_background_updater_auditing_ ARM_cut_objects . . . . . . . . . . . . . . 23-21
enabled . . . . . . . . . . . . . . . . . . . 19-7 ARM_delete_objects . . . . . . . . . . . . 23-23
APPR_background_updater_gap_between_ ARM_display_changeitem . . . . . . . . 23-30
tries . . . . . . . . . . . . . . . . . . . . . . 19-8 ARM_display_form . . . . . . . . . . . . . 23-20
APPR_background_updater_ ARM_display_genealogy . . . . . . . . . 23-31
interval . . . . . . . . . . . . . . . . . . . 19-8 ARM_display_prop . . . . . . . . . . . . . 23-19
APPR_background_updater_max_num_ ARM_expand_bomview . . . . . . . . . . 23-25
failures . . . . . . . . . . . . . . . . . . . . 19-8 ARM_expand_object . . . . . . . . . . . . 23-13
APPR_background_updater_max_num_ ARM_expandbelow_bomview . . . . . 23-26
heartbeats . . . . . . . . . . . . . . . . . 19-9 ARM_export_dataset . . . . . . . . . . . 23-15
APPR_background_updater_max_num_ ARM_idsm_import . . . . . . . . . . 23-8–23-9
records . . . . . . . . . . . . . . . . . . . . 19-9 ARM_idsm_version_check . . . . . . . . 23-10
APPR_background_updater_max_num_ ARM_import_dataset . . . . . . . . . . . 23-15
tries . . . . . . . . . . . . . . . . . . . . . . 19-9 ARM_initiate_process . . . . . . . . . . . 23-29
APPR_max_appearances_per_ ARM_launch_mynavigator . . . . . . . 23-25
process . . . . . . . . . . . . . . . . . . . . 19-2 ARM_load_lov . . . . . . . . . . . . . . . . 23-24
TC_allow_appr_checking . . . . . . . . . 19-2 ARM_ods_publish . . . . . . . . . . . . . . 23-7
TC_allow_appr_query_auditing . . . . . 19-3 ARM_ods_remote_find . . . . . . . . . . . 23-6
TC_appr_allow_remote_query . . . . . . 19-4 ARM_ods_unpublish . . . . . . . . . . . . 23-8
TC_appr_checking_interval . . . . . . . . 19-3 ARM_open_dataset . . . . . . . . . . . . 23-18
TC_appr_remote_query_timeout . . . . 19-5 ARM_open_inbox . . . . . . . . . . . . . . 23-27
TC_prevent_appr_query_on_corrupt_ ARM_open_task2track . . . . . . . . . . 23-28
root . . . . . . . . . . . . . . . . . . . . . . 19-4 ARM_paste_objects . . . . . . . . . . . . 23-22
AppInterface_TCPublishing ARM_perform_signoff . . . . . . . . . . . 23-29
TechnicalPortfolio_default_relation ARM_print_file . . . . . . . . . . . . . . . 23-24
preference . . . . . . . . . . . . . . . . . . . . 20-47 ARM_restore_operation . . . . . . . . . 23-11
AppInterface_TCPublishingTechnical ARM_save_bomview . . . . . . . 23-26–23-27
Portfolio_shown_relations ARM_saveas_item . . . . . . . . . . . . . 23-18
preference . . . . . . . . . . . . . . . . . . . . 20-48 ARM_search_object . . . . . . . . . . . . 23-17
Application Integration Environment ARM_session_login . . . . . . . . . . . . 23-12
preferences . . . . . . . . . . . . . . . . . . . . 23-1 ARM_session_logout . . . . . . . . . . . 23-12
AIE_no_BVR_edit . . . . . . . . . . . . . . 23-2 ARM_tcfs_export_file . . . . . . . . . . . . 23-6
AIE_overwrite_default_import_item_ ARM_tcfs_import_file . . . . . . . . . . . . 23-6
type . . . . . . . . . . . . . . . . . . . . . . 23-1 ARM_tcfs_open_close . . . . . . . . . . . . 23-5
AIE_POST_EXPORT_SCRIPT . . . . . 23-2 ARM_tcsync_object_file_transfer . . . 23-10
AIE_PRE_IMPORT_SCRIPT . . . . . . 23-3 ARM_update_form . . . . . . . . . . . . . 23-20
application name.ic_icon_level ARM_update_prop . . . . . . . . . . . . . 23-19
preference . . . . . . . . . . . . . . . . . . . . 19-58 ARM_where_referenced . . . . . . . . . 23-16
application name.ic_show_remove_icons ARM_where_used . . . . . . . . . . . . . 23-16
preference . . . . . . . . . . . . . . . . . . . . 19-59 APPR_allow_background_updates
Application Response Measurement preference . . . . . . . . . . . . . . . . . . . . . 19-6
integration preferences . . . . . . . . . . . 23-4 APPR_allow_separate_spatial_processing
AARM_open_task2perform . . . . . . . 23-28 preference . . . . . . . . . . . . . . . . . . . . . 19-1
ARM_acquire_license . . . . . . . . . . . 23-17 APPR_background_updateremail_interval_
ARM_archive_operation . . . . . . . . . 23-11 for_different_package preference . . . . . 19-7
ARM_bom_compare . . . . . . . . . . . . 23-27 APPR_background_updateremail_interval_
ARM_checkin_objects . . . . . . . . . . . 23-23 for_same_package preference . . . . . . . 19-7
ARM_checkout_objects . . . . . . . . . . 23-22 APPR_background_updater_admin_email_
ARM_copy_objects . . . . . . . . . . . . . 23-21 address preference . . . . . . . . . . . . . . . 19-6
ARM_create_changeitem . . . . . . . . 23-30 APPR_background_updater_auditing_enabled
ARM_create_dataset . . . . . . . . . . . 23-14 preference . . . . . . . . . . . . . . . . . . . . . 19-7
ARM_create_item . . . . . . . . . . . . . 23-13

Index
APPR_background_updater_gap_between_ ARM_archive_operation preference . . . 23-11

tries preference . . . . . . . . . . . . . . . . . 19-8 ARM_bom_compare preference . . . . . . 23-27
APPR_background_updater_interval ARM_checkin_objects preference . . . . 23-23
preference . . . . . . . . . . . . . . . . . . . . . 19-8 ARM_checkout_objects preference . . . 23-22
APPR_background_updater_max_num_ ARM_copy_objects preference . . . . . . . 23-21
failures preference . . . . . . . . . . . . . . . 19-8 ARM_create_changeitem preference . . 23-30
APPR_background_updater_max_num_ ARM_create_dataset preference . . . . . 23-14
heartbeats preference . . . . . . . . . . . . 19-9 ARM_create_item preference . . . . . . . 23-13
APPR_background_updater_max_num_ ARM_create_itemrev preference . . . . . 23-14
records preference . . . . . . . . . . . . . . . 19-9 ARM_create_supersedure
APPR_background_updater_max_num_tries preference . . . . . . . . . . . . . . . . . . . . 23-31
preference . . . . . . . . . . . . . . . . . . . . . 19-9 ARM_cut_objects preference . . . . . . . . 23-21
APPR_max_appearances_per_process ARM_delete_objects preference . . . . . 23-23
preference . . . . . . . . . . . . . . . . . . . . . 19-2 ARM_display_changeitem
Architecture_Type_generic_id_mapping preference . . . . . . . . . . . . . . . . . . . . 23-30
preference . . . . . . . . . . . . . . . . . . . 19-106 ARM_display_form preference . . . . . . 23-20
ArchitectureModeler_add_design_business_ ARM_display_genealogy preference . . 23-31
rule_check preference . . . . . . . . . . 19-107 ARM_display_prop preference . . . . . . 23-19
ArchitectureModeler_add_design_occurrence_ ARM_expand_bomview preference . . . 23-25
business_rule_check preference . . . 19-107 ARM_expand_object preference . . . . . 23-13
ArchitectureModeler_locking_retry_count ARM_expandbelow_bomview
preference . . . . . . . . . . . . . . . . . . . 19-108 preference . . . . . . . . . . . . . . . . . . . . 23-26
ArchitectureModeler_multiple_installation_ ARM_export_dataset preference . . . . . 23-15
assemblies_condition preference . . . 19-108 ARM_idsm_import preference . . . . . . . 23-8
ArchitectureModeler_part_solution_properties ARM_idsm_version_check
ArchitectureModeler_remove_design_ ARM_import_dataset preference . . . . 23-15
business_rule_check preference . . . 19-109 ARM_initiate_process preference . . . . 23-29
ArchitectureModeler_remove_design_ ARM_launch_mynavigator
occurrence_business_rule_check preference . . . . . . . . . . . . . . . . . . . . 23-25
preference . . . . . . . . . . . . . . . . . . . 19-110 ARM_load_lov preference . . . . . . . . . . 23-24
ArchitectureModeler_RemoveDesign_Max ARM_ods_publish preference . . . . . . . . 23-7
preference . . . . . . . . . . . . . . . . . . . 19-109 ARM_ods_remote_find preference . . . . . 23-6
ArchitectureModeler_replace_design_ ARM_ods_unpublish preference . . . . . . 23-8
business_rule_check preference . . . 19-110 ARM_open_dataset preference . . . . . . 23-18
ArchitectureModeler_replace_design_ ARM_open_inbox preference . . . . . . . 23-27
occurrence_business_rule_check ARM_open_task2perform
ArchitectureModeler_update_design_ ARM_open_task2track preference . . . 23-28
occurrences_business_rule_check ARM_paste_objects preference . . . . . . 23-22
preference . . . . . . . . . . . . . . . . . . . 19-112 ARM_perform_signoff preference . . . . 23-29
ArchitectureModeler_update_designs_ ARM_print_file preference . . . . . . . . . 23-24
business_rule_check preference . . . 19-111 ARM_restore_operation preference . . . 23-11
ArchitectureModeler_use_all_installation_ ARM_save_bomview preference . . . . . 23-26
assemblies preference . . . . . . . . . . 19-112 ARM_saveas_item preference . . . . . . . 23-18
Archive/Restore preference ARM_search_object preference . . . . . . 23-17
Centera_Cluster_IPAddresses . . . . . . . 9-6 ARM_session_login preference . . . . . . 23-12
TC_enable_backup_modes . . . . . . . . . 9-7 ARM_session_logout preference . . . . . 23-12
TC_Store_and_Forward . . . . . . . . . . . 9-6 ARM_tcfs_export_file preference . . . . . . 23-6
TC_Store_and_Forward_Transfer_ ARM_tcfs_import_file preference . . . . . 23-6
Delay . . . . . . . . . . . . . . . . . . . . . . 9-7 ARM_tcfs_open_close preference . . . . . 23-5
Archive, restore, migration ARM_tcsync_object_file_transfer
preferences . . . . . . . . . . . . . . . . . . . . . 9-3 preference . . . . . . . . . . . . . . . . . . . . 23-10
ARM_acquire_license preference . . . . 23-17 ARM_tcsync_update preference . . . . . . 23-9

Index
ARM_update_form preference . . . . . . 23-20 ATTRSHARING_datasource_connection_

ARM_update_prop preference . . . . . . 23-19 details preference . . . . . . . . . . . . . . . . 7-3
ARM_where_referenced preference . . . 23-16 ATTRSHARING_max_rows_expected
ARM_where_used preference . . . . . . . 23-16 preference . . . . . . . . . . . . . . . . . . . . . . 7-3
As-Built Manager preferences . . . . . . 22-79 Audit Manager preferences . . . . . . . . . . 9-1
As-Built preferences TC_audit_buffer_size . . . . . . . . . . . . . 9-2
AdditionalAsBuiltAccCheck TC_audit_delimiter . . . . . . . . . . . . . . 9-3
Properties . . . . . . . . . . . . . . . . . 22-81 TC_audit_file_format . . . . . . . . . . . . . 9-3
AdditionalAsBuiltCompare TC_audit_log_dir . . . . . . . . . . . . . . . . 9-2
Properties . . . . . . . . . . . . . . . . . 22-80 TC_audit_manager . . . . . . . . . . . . . . 9-1
AsBuiltManagerColumns Authorization preferences . . . . . . . . . . . 8-6
ShownPref . . . . . . . . . . . . . . . . 22-79 TC_authorization_mode . . . . . . . . . . . 8-1
AsBuiltManagerShownColumn AUTHORIZATION_MODE variable . . . . 3-2
WidthsPref . . . . . . . . . . . . . . . . 22-79 Automotive Edition preferences . . . . . . 22-4
DefaultAsBuiltAccCheck EngChange_Revision_Change_Type_
Properties . . . . . . . . . . . . . . . . . 22-81 SaveAs_no_copy . . . . . . . . . . . . . 22-5
DefaultAsBuiltCompare EngChange_Revision_Change_Type_
Properties . . . . . . . . . . . . . . . . . 22-80 Revise_no_copy . . . . . . . . . . . . . . 22-5
As-Maintained preferences . . . . . . . . 22-82 GMO_enable_new_pnum_match_
AdditionalAsMaintainedAccCheck criteria . . . . . . . . . . . . . . . . . . . 22-12
Properties . . . . . . . . . . . . . . . . . 22-82 GMO_GRP_browser_default . . . . . . . 22-7
AdditionalAsMaintainedCompare GMO_GRP_edit_prop_mapping_
Properties . . . . . . . . . . . . . . . . . 22-82 default . . . . . . . . . . . . . . . . . . . . 22-8
DefaultAsMaintainedAccCheck GMO_GRP_hostname_default . . . . . . 22-7
Properties . . . . . . . . . . . . . . . . . 22-82 GMO_GRP_port . . . . . . . . . . . . . . . . 22-7
DefaultAsMaintainedCompare GMO_GRP_req_edit_props_
Properties . . . . . . . . . . . . . . . . . 22-83 default . . . . . . . . . . . . . . . . . . . . 22-8
MroConfigRuleName . . . . . . . . . . . 22-83 GMO_GRP_req_ir_types . . . . . . . . . . 22-8
MRODefaultLocations . . . . . . . . . . 22-83 GMO_GRP_show preference . . . . . . . 22-6
PhysicalLocation_ GMO_MATFORM_
DefaultChildProperties . . . . . . . 22-84 AUTOCREATE . . . . . . . . . . . . . 22-22
PhysicalLocationContainsColumns GMO_RDV_enable_audit_criteria . . 22-12
ShownPref . . . . . . . . . . . . . . . . 22-84 Investment_Cost_Form_
ServiceManagerAssetGroup Elements . . . . . . . . . . . . . . . . . 22-21
ColumnWidthsPref . . . . . . . . . . 22-85 IPVBOM_build_intent_status . . . . . 22-13
ServiceManagerColumns IPVBOM_compare_mode_var_level_
ShownPref . . . . . . . . . . . . . . . . 22-86 Occurrence_Notes . . . . . . . . . . . 22-17
ServiceManagerPhysicalLocation IPVBOM_compare_mode_var_level_
ColumnsShownPref . . . . . . . . . . 22-87 RevisionCompare_ItemTypes . . . 22-16
ServiceManagerPhysicalLocation IPVBOM_UPCFNA_Occ
ColumnsWidthsPref . . . . . . . . . 22-87 NoteName . . . . . . . . . . . . . . . . 22-18
ServiceManagerShownColumn ISS_Cost_Form_Elements . . . . . . . . 22-20
WidthsPref . . . . . . . . . . . . . . . . 22-86 ME_Cost_Form_Elements . . . . . . . . 22-20
AsBuiltManagerColumnsShownPref Piece_Cost_Form_Elements . . . . . . 22-21
preference . . . . . . . . . . . . . . . . . . . . 22-79 Plant_Cost_Form_Elements . . . . . . 22-19
AsBuiltManagerShownColumn QR_Cost_Form_Elements . . . . . . . . 22-20
WidthsPref . . . . . . . . . . . . . . . . . . . 22-79 RDV_build_intent_status . . . . . . . . 22-10
ASSIGNED_ITEM_ID_MODIFIABLE RDV_default_option_values_for_tracking_
preference . . . . . . . . . . . . . . . . . . . . . . 5-2 vehicle . . . . . . . . . . . . . . . . . . . 22-11
ASSIGNED_ITEM_REV_MODIFIABLE RDV_default_options_for_tracking_
preference . . . . . . . . . . . . . . . . . . . . . . 5-2 vehicle . . . . . . . . . . . . . . . . . . . 22-10
Assigning related objects to projects . . . . 6-4 RDV_product_obsoletion_status . . . 22-11
Attachment_Alias_File preference . . . . 10-3 RDV_usage_synchronized_architecture_
type . . . . . . . . . . . . . . . . . . . . . 22-12

Index
TAE_Powertrain_site . . . . . . . . . . . 22-19 Baseline_release_procedures

TC_Configuration_File . . . . . . . . . . 22-16 preference . . . . . . . . . . . . . . . . . . . . . 5-18
TC_external_system_attr_value_ Baseline_restricted_item_types
separator . . . . . . . . . . . . . . . . . 22-14 preference . . . . . . . . . . . . . . . . . . . . . 5-18
TC_external_system_bom_name. baselineDryRun preference . . . . . . . . . 5-16
attributes . . . . . . . . . . . . . . . . . 22-14 Batch_Report_Request_File
TC_external_system_item_type . . . . 22-13 preference . . . . . . . . . . . . . . . . . . . 10-133
TC_external_system_url . . . . . . . . . 22-15 BidPackageLineItem_default_relation
TC_external_system_url_value_ preference . . . . . . . . . . . . . . . . . . . . 22-51
name . . . . . . . . . . . . . . . . . . . . 22-16 BidPackageLineItem_DefaultChildProperties
TC_send_to_external_system . . . . . 22-15 preference . . . . . . . . . . . . . . . . . . . . 22-51
TC_Validation_Datasettype . . . . . . 5-116 BidPackageLineItem_PseudoFolder
TC_Validation_Utility . . . . . . . . . . 5-121 preference . . . . . . . . . . . . . . . . . . . . 22-51
TCAE_autogen_name_form_types . . . 22-9 BidPackageRevision_DefaultChildProperties
TCAE_installation_level . . . . . . . . . 22-18 preference . . . . . . . . . . . . . . . . . . . . 22-52
BidPackageRevision_PseudoFolder
B preference . . . . . . . . . . . . . . . . . . . . 22-52
blobbyVolume_NT preference . . . . . . . . 9-28
Background appearance update blobbyVolume_UNX preference . . . . . . 9-28
preferences . . . . . . . . . . . . . . . . . . . . 19-5 BMF_CUSTOM_IMPLEMENTOR_PATH
Baseline preferences preference . . . . . . . . . . . . . . . . . . . . . . 5-2
Baseline_allow_edits . . . . . . . . . . . . 5-15 BMIDE_ALLOW_DEPLOYMENT_FROM_
Baseline_allowed_baserev_ CLIENT preference . . . . . . . . . . . . . . . 5-3
statuses . . . . . . . . . . . . . . . . . . . 5-15 BMIDE_SCRIPT_ARGS . . . . . . . . . . . . 3-2
Baseline_create_snapshot_folder . . . . 5-15 BOB_property_optimizations
Baseline_dryrun_always . . . . . . . . . . 5-16 preference . . . . . . . . . . . . . . . . . . . . . 5-19
Baseline_nxmanager_refile . . . . . . . . 5-16 BOM grading preferences . . . . . . . . 19-101
Baseline_precise_bvr . . . . . . . . . . . . 5-17 ConditionValidationResult
Baseline_refile_not_required_item_ ColumnPreferences . . . . . . . . . 19-105
types . . . . . . . . . . . . . . . . . . . . . 5-17 ConditionValidationResultColumn
Baseline_refile_required_dstypes . . . . 5-18 WidthPreferences . . . . . . . . . . 19-106
Baseline_release_procedures . . . . . . . 5-18 CondValData.
Baseline_restricted_item_types . . . . . 5-18 CREATERENDERING . . . . . . 19-101
baselineDryRun . . . . . . . . . . . . . . . . 5-16 CondValData.
USER_baseline_dryrun_validator . . . 5-26 SUMMARYRENDERING . . . . 19-102
Baseline_allow_edits preference . . . . . . 5-15 CondValDataCreate.CREATE_
Baseline_allowed_baserev_statuses REGISTEREDTO . . . . . . . . . . 19-102
preference . . . . . . . . . . . . . . . . . . . . . 5-15 CondValDataRevision.
Baseline_auto_remote_checkout_allowed REGISTEREDTO . . . . . . . . . . 19-102
Baseline_create_snapshot_folder RENDERING . . . . . . . . . . . . . 19-103
Baseline_dryrun_always preference . . . 5-16 SUMMARYRENDERING . . . . 19-103
Baseline_nxmanager_refile CondValdataRevSummary.SUMMARY_
preference . . . . . . . . . . . . . . . . . . . . . 5-16 REGISTEREDTO . . . . . . . . . . 19-102
Baseline_omitted_occurrence_types CondValDataSummary.SUMMARY_
Baseline_precise_bvr preference . . . . . . 5-17 CONDVALIDATION_Keep_PrevRev_
Baseline_precondition_validation_rule Result . . . . . . . . . . . . . . . . . . 19-105
_item_revision . . . . . . . . . . . . . . . . . 5-109 CondValidation_NoData . . . . . . . . 19-104
Baseline_refile_not_required_item_types CondValResult.SUMMARY
preference . . . . . . . . . . . . . . . . . . . . . 5-17 RENDERING . . . . . . . . . . . . . 19-104
Baseline_refile_required_dstypes CondValResultSummary.SUMMARY_

Index
BOM_Additional_Packing_Criteria TYPE_DISPLAY_RULES_list_types_of_
preference . . . . . . . . . . . . . . . . . . . . 19-90 subclasses . . . . . . . . . . . . . . . . . . . 5-7
BOM_Additional_Ref_Designator_Search_ Bypass_property_rules preference . . . . . 5-3
Criteria preference . . . . . . . . . . . . . 19-90
BOM_Enable_Quantity_Validation_Against_ C
Ref_Designator preference . . . . . . . . 19-91
BOM_Enable_Ref_Designator_Value_Packing Cache purging . . . . . . . . . . . . . . . . . . 9-23
preference . . . . . . . . . . . . . . . . . . . . 19-89 Caching modes . . . . . . . . . . . . . . . . . . 9-23
BOM_MARKUP_ADD_FONT_STYLE CAE_always_remesh preference . . . . . 23-44
preference . . . . . . . . . . . . . . . . . . . . 19-60 CAE_batch_meshing_always_create_new
BOM_MARKUP_ADD_FOREGROUND preference . . . . . . . . . . . . . . . . . . . . 23-45
preference . . . . . . . . . . . . . . . . . . . . 19-60 CAE_batch_meshing_attribute
BOM_MARKUP_STRIKE_FOREGROUND preference . . . . . . . . . . . . . . . . . . . . 23-45
preference . . . . . . . . . . . . . . . . . . . . 19-61 CAE_batch_meshing_import_file_extensions
BOM_objects_excluded_from_split preference . . . . . . . . . . . . . . . . . . . . 23-44
preference . . . . . . . . . . . . . . . . . . . . 19-45 CAE_batch_meshing_root_dir
BOMCompareVisibleModes preference . . . . . . . . . . . . . . . . . . . . 23-36
preference . . . . . . . . . . . . . . . . . . . . 19-59 CAE_batch_meshing_tools
BOMExcludeFromPackCheck preference . . . . . . . . . . . . . . . . . . . . 23-35
preference . . . . . . . . . . . . . . . . . . . . 19-92 CAE_dataMapping_file preference . . . 23-42
BOMView_DefaultChildProperties CAE_default_batch_meshing_tool
BOMViewRevision_DefaultChildProperties CAE_input_geometry preference . . . . 23-44
preference . . . . . . . . . . . . . . . . . . . . 10-84 CAE_meshing_params_criteria_source
BOMWriterDirectModelRelationType preference . . . . . . . . . . . . . . . . . . . . 23-43
preference . . . . . . . . . . . . . . . . . . . 19-129 CAE_post_processor_additional_output
BOMWriterNoDescendantsInPLMXML preference . . . . . . . . . . . . . . . . . . . . 23-41
preference . . . . . . . . . . . . . . . . . . . 19-130 CAE_post_processor_primary_input
BOMWriterNoDirectParents preference . . . . . . . . . . . . . . . . . . . . 23-39
preference . . . . . . . . . . . . . . . . . . . 19-130 CAE_post_processor_primary_output
Business rules preferences . . . . . . . . . . . 5-1 preference . . . . . . . . . . . . . . . . . . . . 23-40
Business Rules preferences CAE_post_processor_startup_scripts
AltIdentifier_require_on_create . . . . . . 5-1 preference . . . . . . . . . . . . . . . . . . . . 23-38
ASSIGNED_ITEM_ID_ CAE_post_processor_tools
MODIFIABLE . . . . . . . . . . . . . . . 5-2 preference . . . . . . . . . . . . . . . . . . . . 23-37
ASSIGNED_ITEM_REV_ CAE_pre_processor_additional_output
MODIFIABLE . . . . . . . . . . . . . . . 5-2 preference . . . . . . . . . . . . . . . . . . . . 23-41
BMF_CUSTOM_IMPLEMENTOR_ CAE_pre_processor_alternate_input
PATH . . . . . . . . . . . . . . . . . . . . . . 5-2 preference . . . . . . . . . . . . . . . . . . . . 23-39
BMIDE_ALLOW_DEPLOYMENT_FROM_ CAE_pre_processor_primary_input
CLIENT . . . . . . . . . . . . . . . . . . . . 5-3 preference . . . . . . . . . . . . . . . . . . . . 23-38
Bypass_property_rules . . . . . . . . . . . . 5-3 CAE_pre_processor_primary_output
IdentifierContextPref . . . . . . . . . . . . . 5-4 preference . . . . . . . . . . . . . . . . . . . . 23-40
IdentifierLengthPref . . . . . . . . . . . . . 5-4 CAE_pre_processor_startup_scripts
ITEM_autogenerate_id . . . . . . . . . . . . 5-4 preference . . . . . . . . . . . . . . . . . . . . 23-37
METHOD_CM_execute_before_ CAE_pre_processor_tools
custom . . . . . . . . . . . . . . . . . . . . . 5-5 preference . . . . . . . . . . . . . . . . . . . . 23-36
NR_BYPASS . . . . . . . . . . . . . . . . . . . 5-5 CAE_simulation_tool_config_dsname
TC_dataset_deep_copy_rules . . . . . . . . 5-5 preference . . . . . . . . . . . . . . . . . . . . 23-46
Treat_Curr_Rev_As_Any_Rev . . . . . . . 5-6 CAE_solver_additional_output
Treat_Next_Rev_As_Any_Rev . . . . . . . 5-6 preference . . . . . . . . . . . . . . . . . . . . 23-42
TYPE_DISPLAY_RULES_list_of_primary_ CAE_solver_primary_input
types . . . . . . . . . . . . . . . . . . . . . . 5-7 preference . . . . . . . . . . . . . . . . . . . . 23-39

Index
CAE_solver_primary_output ChangeNoticeRevision.
preference . . . . . . . . . . . . . . . . . . . . 23-40 RENDERING . . . . . . . . . . . . . . . 13-3
CAE_solver_startup_scripts ChangeNoticeRevision.
preference . . . . . . . . . . . . . . . . . . . . 23-38 SUMMARYRENDERING . . . . . . 13-3
CAE_solver_tools preference . . . . . . . 23-37 ChangeNoticeRevisionSummary.
CAE_startup_scripts preference . . . . . 23-43 SUMMARY_REGISTEREDTO . . . 13-4
CAE_structure_map_dataset_type ChangeRequest.
preference . . . . . . . . . . . . . . . . . . . . 23-42 CREATERENDERING . . . . . . . . 13-4
CAEAnalysisRevision Master_viewerprops ChangeRequestCreate.CREATE_
preference . . . . . . . . . . . . . . . . . . . . 23-34 REGISTEREDTO . . . . . . . . . . . . 13-4
CAEBCItemRevision Master_viewerprops ChangeRequestRevision_
preference . . . . . . . . . . . . . . . . . . . . 23-33 DefaultChildProperties . . . . . . . . 13-4
CAEConnItemRevision Master_viewerprops ChangeRequestRevision.
preference . . . . . . . . . . . . . . . . . . . . 23-34 REGISTEREDTO . . . . . . . . . . . . 13-5
CAELoadItemRevision Master_viewerprops ChangeRequestRevision.
preference . . . . . . . . . . . . . . . . . . . . 23-33 RENDERING . . . . . . . . . . . . . . . 13-5
Categories, creating . . . . . . . . . . . . . . . 4-10 ChangeRequestRevision.
Categories, deleting . . . . . . . . . . . . . . . 4-10 SUMMARYRENDERING . . . . . . 13-6
CATIA_check_in_generate_vis_data_priority ChangeRequestRevisionSummary.
preference . . . . . . . . . . . . . . . . . . . . . 5-37 SUMMARY_REGISTEREDTO . . . 13-6
CATIA_checkin_generate_vis_data_priority CM_bomchange_formtype . . . . . . . . . 13-6
preference . . . . . . . . . . . . . . . . . . . . . 5-38 CM_change_derivations . . . . . . . . . . 13-7
CATIA_on_demand_generate_vis_data_ CM_ChangeRequestRevision_Relations_To_
priority preference . . . . . . . . . . . 5-38, 5-41 Propagate . . . . . . . . . . . . . . . . . . 13-7
CATIA_translation_service_name CM_Cm0DevRqstRevision_Relations_To_
preference . . . . . . . . . . . . . . . . . . . . . 5-37 Propagate . . . . . . . . . . . . . . . . . . 13-7
CATIA_V4_check_in_generate_vis_data_ CM_Effectivity_DefaultColumns . . . . 13-8
priority preference . . . . . . . . . . . . . . . 5-41 CM_form_relation . . . . . . . . . . . . . . 13-8
CATIA_V4_translation_service_name CM_impacted_item_relation . . . . . . . 13-9
preference . . . . . . . . . . . . . . . . . . . . . 5-40 CM_note_types_to_track . . . . . . . . . . 13-9
CATIA_work_dir preference . . . . . . . . . 5-40 CM_notehistory_extra_columns . . . 13-10
CCCompositionTypesPref preference . . 10-4 CM_ProblemReportRevision_Relations_To_
Ccd0ColumnPreference preference . . . 22-44 Propagate . . . . . . . . . . . . . . . . . 13-10
CCDM_grp_rev_val preference . . . . . . 22-45 CM_pureaddcancel_tooltip_
CCObject_default_relation properties . . . . . . . . . . . . . . . . . 13-10
preference . . . . . . . . . . . . . . . . . . . . . 10-4 CM_relation_creation_flag . . . . . . . 13-11
CCObject_DefaultChildProperties CM_solution_items_relation . . . . . . 13-11
preference . . . . . . . . . . . . . . . . . . . . 10-85 CM_supersedure_tooltip_
Centera_Cluster_IPAddresses properties . . . . . . . . . . . . . . . . . 13-12
preference . . . . . . . . . . . . . . . . . . . . . . 9-6 CM_track_variant_condition_
CFM_ITEM_TYPE_RULE_INCLUDE_SUB_ changes . . . . . . . . . . . . . . . . . . 13-12
TYPES preference . . . . . . . . . . . . . . 19-45 CM_varianthistory_extra_
CFMOccEffMode preference . . . . . . . . 19-76 columns . . . . . . . . . . . . . . . . . . 13-13
Change Manager preferences . . . . . . . 13-18 CM_work_breakdown_relation . . . . 13-13
ChangeItemRevision_ Cm0DevRqst.
DefaultChildProperties . . . . . . . . 13-1 CREATERENDERING . . . . . . . 13-15
ChangeNotice. Cm0DevRqstCreate.CREATE_
CREATERENDERING . . . . . . . . 13-1 REGISTEREDTO . . . . . . . . . . . 13-16
ChangeNoticeCreate.CREATE_ Cm0DevRqstRevision_
REGISTEREDTO . . . . . . . . . . . . 13-2 DefaultChildProperties . . . . . . . 13-16
ChangeNoticeRevision_ Cm0DevRqstRevision.
DefaultChildProperties . . . . . . . . 13-2 REGISTEREDTO . . . . . . . . . . . 13-17
ChangeNoticeRevision. Cm0DevRqstRevision.
REGISTEREDTO . . . . . . . . . . . . 13-3 RENDERING . . . . . . . . . . . . . . 13-17

Index
Cm0DevRqstRevision. ECM_note_types_to_track . . . . . . . . 12-9

SUMMARYRENDERING . . . . . 13-17 ECM_notehistory_extra_columns . . 12-10
Cm0DevRqstRevisionSummary. ECM_prev_structure_relation . . . . . 12-10
SUMMARY_ ECM_prev_structure_relation_
REGISTEREDTO . . . . . . . . . . . 13-17 name . . . . . . . . . . . . . . . . . . . . 12-11
CMHasImpactedItem_relation_ ECM_property_access . . . . . . . . . . 12-11
primary . . . . . . . . . . . . . . . . . . 13-13 ECM_property_display_names . . . . 12-11
CMHasProblemItem_relation_ ECM_property_names . . . . . . . . . . 12-12
primary . . . . . . . . . . . . . . . . . . 13-14 ECM_pseudofolder_names . . . . . . . 12-12
CMHasSolutionItem_relation_ ECM_set_genealogy . . . . . . . . . . . . 12-13
primary . . . . . . . . . . . . . . . . . . 13-14 ECM_supercedure_tooltip_
CMHasWorkBreakdown_relation_ properties . . . . . . . . . . . . . . . . . 12-13
primary . . . . . . . . . . . . . . . . . . 13-14 ECM_track_variant_condition_
CMImplements_relation_primary . . 13-15 changes . . . . . . . . . . . . . . . . . . 12-14
CMReferences_relation_primary . . . 13-15 ECM_varianthistory_extra_
Enable_Create_Classic_Change . . . 12-15 columns . . . . . . . . . . . . . . . . . . 12-14
Enable_Show_Classic_Change . . . . 12-15 EngChange Revision_
ProblemReport. DefaultChildProperties . . . . . . . 12-16
CREATERENDERING . . . . . . . 13-18 Supercedure_DefaultChild
ProblemReportCreate.CREATE_ Properties . . . . . . . . . . . . . . . . . 12-16
REGISTEREDTO . . . . . . . . . . . 13-18 TAE_CM_change_name_is_
ProblemReportRevision_ mandatory . . . . . . . . . . . . . . . . 12-17
DefaultChildProperties . . . . . . . 13-18 TAE_CM_show_task_viewer . . . . . . 12-17
ProblemReportRevision. TC_bomchange_export . . . . . . . . . . 12-17
REGISTEREDTO . . . . . . . . . . . 13-19 TC_supercedure_export . . . . . . . . . 12-18
ProblemReportRevision. Change_Search_Default preference . . . 10-5
RENDERING . . . . . . . . . . . . . . 13-19 ChangeItemRevision_DefaultChildProperties
ProblemReportRevision. preference . . . . . . . . . . . . . . . . . . . . . 13-1
SUMMARYRENDERING . . . . . 13-19 ChangeNotice.CREATERENDERING
ProblemReportRevisionSummary. preference . . . . . . . . . . . . . . . . . . . . . 13-1
SUMMARY_ ChangeNoticeCreate.CREATE_
REGISTEREDTO . . . . . . . . . . . 13-20 REGISTEREDTO preference . . . . . . . 13-2
WEB_Enable_Create_Change . . . . . 13-20 ChangeNoticeRevision_
Change Viewer preferences . . . . . . . . 12-14 DefaultChildProperties preference . . . 13-2
CM_color_of_add . . . . . . . . . . . . . . . 12-1 ChangeNoticeRevision.REGISTEREDTO
CM_color_of_cancel . . . . . . . . . . . . . 12-2 preference . . . . . . . . . . . . . . . . . . . . . 13-3
CM_color_of_common . . . . . . . . . . . . 12-2 ChangeNoticeRevision.RENDERING
CM_color_of_moved . . . . . . . . . . . . . 12-3 preference . . . . . . . . . . . . . . . . . . . . . 13-3
CM_color_of_notechange . . . . . . . . . . 12-3 ChangeNoticeRevision.
CM_color_of_quantity_change . . . . . . 12-4 SUMMARYRENDERING
CM_color_of_reshaped . . . . . . . . . . . 12-4 preference . . . . . . . . . . . . . . . . . . . . . 13-3
CM_color_of_variantchange . . . . . . . 12-5 ChangeNoticeRevisionSummary.SUMMARY_
CM_initial_position_of_sliders . . . . . 12-5 REGISTEREDTO preference . . . . . . . 13-4
CM_progression_tree_relation . . . . . . 12-5 ChangeRequest.CREATERENDERING
CM_show_common_parts . . . . . . . . . 12-6 preference . . . . . . . . . . . . . . . . . . . . . 13-4
ECM_affected_item_relations . . . . . . 12-6 ChangeRequestCreate.CREATE_
ECM_bomchange_formtype . . . . . . . . 12-7 REGISTEREDTO preference . . . . . . . 13-4
ECM_bomchange_tooltip_ ChangeRequestRevision_
properties . . . . . . . . . . . . . . . . . . 12-7 DefaultChildProperties preference . . . 13-4
ECM_change_id_modifiable . . . . . . . 12-8 ChangeRequestRevision.REGISTEREDTO
ECM_change_name_is_mandatory . . 12-8 preference . . . . . . . . . . . . . . . . . . . . . 13-5
ECM_delivered_engine_status . . . . . 12-8 ChangeRequestRevision.RENDERING
ECM_form_relation . . . . . . . . . . . . . 12-9 preference . . . . . . . . . . . . . . . . . . . . . 13-5
ECM_genealogy_expansion_rule . . . . 12-9

Index
ChangeRequestRevision. ICS_default_instance_document . . . . 17-5

SUMMARYRENDERING ICS_default_root_selector_entries . . . 17-8
preference . . . . . . . . . . . . . . . . . . . . . 13-6 ICS_enable_graphical_browser . . . . . 17-7
ChangeRequestRevisionSummary. ICS_GraphicsBuilder . . . . . . . . . . . . 17-7
SUMMARY_REGISTEREDTO ICS_hierarchy_list_icon_size . . . . . . . 17-8
preference . . . . . . . . . . . . . . . . . . . . . 13-6 ICS_hierarchy_sort_option . . . . . . . . 17-8
CheckoutOnCreatePref preference . . . . 5-19 ICS_ico_action_after_saveas . . . . . . 17-11
Class_Resource_Robot preference . . . 10-131 ICS_itemrev_master_dataset_
Class_Resource_WeldGun relation . . . . . . . . . . . . . . . . . . 17-11
preference . . . . . . . . . . . . . . . . . . . 10-131 ICS_master_datasettypes_for_
Classification administration itemrev . . . . . . . . . . . . . . . . . . 17-11
preferences . . . . . . . . . . . . . . . . . . . 16-14 ICS_max_number_of_
Classification Administration preferences components . . . . . . . . . . . . . . . 17-12
GCS_classify_type . . . . . . . . . . . . . . 16-8 ICS_presented_class_documents . . . . 17-6
ICS_allow_deprecated_lovs_on_ ICS_presented_instance_
copy . . . . . . . . . . . . . . . . . . . . . 16-10 documents . . . . . . . . . . . . . . . . . 17-4
ICS_allow_deprecated_lovs_on_ ICS_root_selector_entries . . . . . . . . . 17-9
update . . . . . . . . . . . . . . . . . . . . 16-9 ICS_search_default_revision_rule_
ICS_allow_min_max_range_ <application name> . . . . . . . . . . 17-13
override . . . . . . . . . . . . . . . . . . 16-11 ICS_search_use_revision_rule . . . . . 17-13
ICS_allow_remote_parent . . . . . . . . . 16-6 ICS_show_autofilter . . . . . . . . . . . . 17-10
ICS_attribute_displayable_ ICS_synchronize_automatically . . . . 17-14
properties . . . . . . . . . . . . . . . . . 16-12 ICS_synchronize_sites . . . . . . . . . . 17-14
ICS_available_languages . . . . . . . . . 16-2 ICS_table_header_style . . . . . . . . . 17-14
ICS_classification_master_site . . . . . 16-1 ICS_table_pagesize . . . . . . . . . . . . 17-15
ICS_copy_classid_pattern . . . . . . . . . 16-3 ICS_unit_active . . . . . . . . . . . . . . . . 16-7
ICS_enforce_min_max_constraints_on_ ICS_use_access_control . . . . . . . . . 17-15
copy . . . . . . . . . . . . . . . . . . . . . 16-11 ICS_user_defined_button_class . . . . 17-10
ICS_enforce_min_max_constraints_on_ ICS_web_preferred_jt_image . . . . . . 17-15
update . . . . . . . . . . . . . . . . . . . 16-10 MRMClassifyResource . . . . . . . . . . . 17-2
ICS_import_attribute_find_free_ MSE_ICS_default_type . . . . . . . . . . 20-7
dbindex . . . . . . . . . . . . . . . . . . . 16-9 ClearCase Integration preferences . . . 23-53
ICS_import_attribute_use_ SCM_CheckIn_Identical_Version . . . 23-54
dbindex . . . . . . . . . . . . . . . . . . . 16-8 SCM_ClearCase_Server . . . . . . . . . 23-53
ICS_mapping_target_type . . . . . . . . 16-6 SCM_ClearCase_UNCO_Keep_
ICS_migrate_classid_pattern . . . . . . 16-4 Version . . . . . . . . . . . . . . . . . . . 23-54
ICS_new_classid_pattern . . . . . . . . . 16-2 Client interface preferences . . . . . . . . . . 5-8
ICS_override_unit_definition_ Confirm_cancel_checkout_
precision . . . . . . . . . . . . . . . . . . 16-12 suppressed . . . . . . . . . . . . . . . . . . 5-8
ICS_share_related . . . . . . . . . . . . . . 16-5 Confirm_checkin_suppressed . . . . . . . 5-9
ICS_unit_default . . . . . . . . . . . . . . . 16-7 Confirm_checkout_suppressed . . . . . . . 5-9
ICS_use_view_attributes_when_moving_ Confirmation_shown_on_reservation_
icos . . . . . . . . . . . . . . . . . . . . . . 16-4 dialogs . . . . . . . . . . . . . . . . . . . . . 5-8
ICS_view_selection_order . . . . . . . . . 16-5 Form_double_click . . . . . . . . . . . . . . 5-10
Classification preferences . . . . . . . . . 17-12 Client preferences . . . . . . . . . . . . . . . . 10-1
ICS_attribute_mapping_trim_ Rich client preferences . . . . . . . . . . . 10-1
zeros . . . . . . . . . . . . . . . . . . . . . 17-1 Thin client preferences . . . . . . . . . . 10-98
ICS_classifiable_types . . . . . . . . . . . 17-1 Clone_Pending_Release_Status
ICS_classify_immediately . . . . . . . . . 17-3 preference . . . . . . . . . . . . . . . . . . . . 20-28
ICS_classify_immediately_NX . . . . . . 17-3 Clone_Secured_Release_Status
ICS_classify_new . . . . . . . . . . . . . . . 17-4 preference . . . . . . . . . . . . . . . . . . . . 20-28
ICS_classify_sendto . . . . . . . . . . . . 17-16 Cloning preferences . . . . . . . . . . . . . . 20-23
ICS_datasettype_for_class . . . . . . . . 17-4 CM_bomchange_formtype preference . . 13-6
ICS_default_class_document . . . . . . . 17-6 CM_change_derivations preference . . . . 13-7

Index
CM_ChangeRequestRevision_Relations_To_ Cm0DevRqstRevision_DefaultChildProperties
Propagate preference . . . . . . . . . . . . . 13-7 preference . . . . . . . . . . . . . . . . . . . . 13-16
CM_Cm0DevRqstRevision_Relations_To_ Cm0DevRqstRevision.REGISTEREDTO
Propagate preference . . . . . . . . . . . . . 13-7 preference . . . . . . . . . . . . . . . . . . . . 13-17
CM_color_of_add preference . . . . . . . . . 12-1 Cm0DevRqstRevision.RENDERING
CM_color_of_cancel preference . . . . . . . 12-2 preference . . . . . . . . . . . . . . . . . . . . 13-17
CM_color_of_common preference . . . . . 12-2 Cm0DevRqstRevision.
CM_color_of_moved preference . . . . . . . 12-3 SUMMARYRENDERING
CM_color_of_notechange preference . . . 12-3 preference . . . . . . . . . . . . . . . . . . . . 13-17
CM_color_of_quantity_change Cm0DevRqstRevisionSummary.SUMMARY_
preference . . . . . . . . . . . . . . . . . . . . . 12-4 REGISTEREDTO preference . . . . . . 13-17
CM_color_of_reshaped preference . . . . . 12-4 CMHasImpactedItem_relation_primary
CM_color_of_variantchange preference . . . . . . . . . . . . . . . . . . . . 13-13
preference . . . . . . . . . . . . . . . . . . . . . 12-5 CMHasProblemItem_relation_primary
CM_Effectivity_DefaultColumns preference . . . . . . . . . . . . . . . . . . . . 13-14
preference . . . . . . . . . . . . . . . . . . . . . 13-8 CMHasSolutionItem_relation_primary
CM_form_relation preference . . . . . . . . 13-8 preference . . . . . . . . . . . . . . . . . . . . 13-14
CM_impacted_item_relation CMHasWorkBreakdown_relation_primary
CM_initial_position_of_sliders CMImplements_relation_primary
CM_note_types_to_track preference . . . 13-9 CMReferences_relation_primary
CM_notehistory_extra_columns preference . . . . . . . . . . . . . . . . . . . . 13-15
preference . . . . . . . . . . . . . . . . . . . . 13-10 CommercialPart_DefaultChildProperties
CM_ProblemReportRevision_Relations_To_ preference . . . . . . . . . . . . . . . . . . . . 22-53
Propagate preference . . . . . . . . . . . . 13-10 CommercialPart_PseudoFolder
CM_progression_tree_relation preference . . . . . . . . . . . . . . . . . . . . 22-53
preference . . . . . . . . . . . . . . . . . . . . . 12-5 COMMONcatiatojt_catia_ets_nr_types
CM_pureaddcancel_tooltip_properties preference . . . . . . . . . . . . . . . . . . . . . 5-42
preference . . . . . . . . . . . . . . . . . . . . 13-10 COMMONcatiatojt_CATPart_ets_nr_types
CM_relation_creation_flag preference . . . . . . . . . . . . . . . . . . . . . 5-39
preference . . . . . . . . . . . . . . . . . . . . 13-11 COMMONcatiatojt_CATProduct_ets_nr_types
CM_show_common_parts preference . . . 12-6 preference . . . . . . . . . . . . . . . . . . . . . 5-39
CM_solution_items_relation COMMONcatiatojt_ets_ds_types
preference . . . . . . . . . . . . . . . . . . . . 13-11 preference . . . . . . . . . . . . . . . . . . . . . 5-39
CM_SRP0DgSrvRequestRevision_displayed_ COMMONcatiatojtV4_ets_ds_types
pseudofolders preference . . . . . . . . 22-101 preference . . . . . . . . . . . . . . . . . . . . . 5-42
CM_SRP0PrSrvRequestRevision_displayed_ CompanyContact.MROCREATE
pseudofolders preference . . . . . . . . 22-102 RENDERING preference . . . . . . . . 22-103
CM_SRP0RqstActivityRevision_displayed_ CompanyLocation_DefaultChildProperties
pseudofolders preference . . . . . . . . 22-102 preference . . . . . . . . . . . . . . . . . . . . 22-54
CM_supersedure_tooltip_properties CompanyLocation.MROCREATE
preference . . . . . . . . . . . . . . . . . . . . 13-12 RENDERING preference . . . . . . . . 22-103
CM_track_variant_condition_changes CompanyLocation_PseudoFolder
CM_varianthistory_extra_columns Composite properties in
preference . . . . . . . . . . . . . . . . . . . . 13-13 DesignContext . . . . . . . . . . . . . . . . 19-39
CM_work_breakdown_relation Computer aided engineering
preference . . . . . . . . . . . . . . . . . . . . 13-13 preferences . . . . . . . . . . . . . . . . . . . 23-32
Cm0DevRqst.CREATERENDERING CAE_always_remesh . . . . . . . . . . . 23-44
preference . . . . . . . . . . . . . . . . . . . . 13-15 CAE_batch_meshing_always_create_
Cm0DevRqstCreate.CREATE_ new . . . . . . . . . . . . . . . . . . . . . 23-45
REGISTEREDTO preference . . . . . . 13-16 CAE_batch_meshing_attribute . . . . 23-45

Index
CAE_batch_meshing_import_file_ CondValDataCreate.CREATE_
extensions . . . . . . . . . . . . . . . . 23-44 REGISTEREDTO preference . . . . . 19-102
CAE_batch_meshing_root_dir . . . . . 23-36 CondValDataRevision.REGISTEREDTO
CAE_batch_meshing_tools . . . . . . . 23-35 preference . . . . . . . . . . . . . . . . . . . 19-102
CAE_dataMapping_file . . . . . . . . . . 23-42 CondValDataRevision.RENDERING
CAE_default_batch_meshing_tool . . 23-36 preference . . . . . . . . . . . . . . . . . . . 19-103
CAE_input_geometry . . . . . . . . . . . 23-44 CondValDataRevision.
CAE_meshing_params_criteria_ SUMMARYRENDERING
source . . . . . . . . . . . . . . . . . . . 23-43 preference . . . . . . . . . . . . . . . . . . . 19-103
CAE_post_processor_additional_ CondValdataRevSummary.SUMMARY_
output . . . . . . . . . . . . . . . . . . . 23-41 REGISTEREDTO preference . . . . . 19-102
CAE_post_processor_primary_ CondValDataSummary.SUMMARY_
input . . . . . . . . . . . . . . . . . . . . 23-39 REGISTEREDTO preference . . . . . 19-103
CAE_post_processor_primary_ CONDVALIDATION_Keep_PrevRev_Result
output . . . . . . . . . . . . . . . . . . . 23-40 preference . . . . . . . . . . . . . . . . . . . 19-105
CAE_post_processor_startup_ CondValidation_NoData
scripts . . . . . . . . . . . . . . . . . . . 23-38 preference . . . . . . . . . . . . . . . . . . . 19-104
CAE_post_processor_tools . . . . . . . . 23-37 CondValResult.SUMMARYRENDERING
CAE_pre_processor_additional_ preference . . . . . . . . . . . . . . . . . . . 19-104
output . . . . . . . . . . . . . . . . . . . 23-41 CondValResultSummary.SUMMARY_
CAE_pre_processor_alternate_ REGISTEREDTO preference . . . . . 19-104
input . . . . . . . . . . . . . . . . . . . . 23-39 Configuration preferences . . . . . . . . . . . 5-1
CAE_pre_processor_primary_ 3DMarkup_relation_primary . . . . . . 21-1
input . . . . . . . . . . . . . . . . . . . . 23-38 ADA_allow_license_propagation . . . . 5-11
CAE_pre_processor_primary_ ADA_enabled . . . . . . . . . . . . . . . . . . 5-12
output . . . . . . . . . . . . . . . . . . . 23-40 ADA_saveas_propagated_license_
CAE_pre_processor_startup_ types . . . . . . . . . . . . . . . . . . . . . 5-12
scripts . . . . . . . . . . . . . . . . . . . 23-37 AltIdentifier_require_on_create . . . . . . 5-1
CAE_pre_processor_tools . . . . . . . . 23-36 ASSIGNED_ITEM_ID_
CAE_simulation_tool_config_ MODIFIABLE . . . . . . . . . . . . . . . 5-2
dsname . . . . . . . . . . . . . . . . . . 23-46 ASSIGNED_ITEM_REV_
CAE_solver_additional_output . . . . 23-42 MODIFIABLE . . . . . . . . . . . . . . . 5-2
CAE_solver_primary_input . . . . . . . 23-39 BMF_CUSTOM_IMPLEMENTOR_
CAE_solver_primary_output . . . . . . 23-40 PATH . . . . . . . . . . . . . . . . . . . . . . 5-2
CAE_solver_startup_scripts . . . . . . 23-38 BMIDE_ALLOW_DEPLOYMENT_FROM_
CAE_solver_tools . . . . . . . . . . . . . . 23-37 CLIENT . . . . . . . . . . . . . . . . . . . . 5-3
CAE_startup_scripts . . . . . . . . . . . 23-43 BOB_property_optimizations . . . . . . 5-19
CAE_structure_map_dataset_ Bypass_property_rules . . . . . . . . . . . . 5-3
type . . . . . . . . . . . . . . . . . . . . . 23-42 CATIA_check_in_generate_vis_data_
CAEBCItemRevision Master_ priority . . . . . . . . . . . . . . . . . . . . 5-37
viewerprops . . . . . . . . . . . . . . . 23-33 CATIA_checkin_generate_vis_data_
CAEConnItemRevision Master_ priority . . . . . . . . . . . . . . . . . . . . 5-38
viewerprops . . . . . . . . . . . . . . . 23-34 CATIA_on_demand_generate_vis_data_
CAELoadItemRevision Master_ priority . . . . . . . . . . . . . . . . . . . . 5-38
viewerprops . . . . . . . . . . . . . . . 23-33 CATIA_translation_service_name . . . 5-37
ConditionValidationResultColumnPreferences CATIA_V4_check_in_generate_vis_data_
preference . . . . . . . . . . . . . . . . . . . 19-105 priority . . . . . . . . . . . . . . . . . . . . 5-41
ConditionValidationResultColumn CATIA_V4_on_demand_generate_vis_data_
WidthPreferences preference . . . . . 19-106 priority . . . . . . . . . . . . . . . . . . . . 5-41
CondValData.SUMMARYRENDERING CATIA_V4_translation_service_
preference . . . . . . . . . . . . . . . . . . . 19-102 name . . . . . . . . . . . . . . . . . . . . . 5-40
CondValData.CREATERENDERING CATIA_work_dir . . . . . . . . . . . . . . . 5-40
preference . . . . . . . . . . . . . . . . . . . 19-101 CheckoutOnCreatePref . . . . . . . . . . . 5-19

Index
COMMONcatiatojt_catia_ets_nr_ IMAN_Drawing_relation_primary . . . 5-48

types . . . . . . . . . . . . . . . . . . . . . 5-42 IMAN_external_appl_reg_url . . . . . . 5-94
COMMONcatiatojt_CATPart_ets_nr_ INTEROP_Extra
types . . . . . . . . . . . . . . . . . . . . . 5-39 PLMXMLInstanceAttributes . . . . 21-2
COMMONcatiatojt_CATProduct_ets_nr_ Interop_Vis_Attributes . . . . . . . . . . . 21-3
types . . . . . . . . . . . . . . . . . . . . . 5-39 Interop_Vis_Attributes_Admin_
COMMONcatiatojt_ets_ds_types . . . . 5-39 Filter . . . . . . . . . . . . . . . . . . . . . 21-4
COMMONcatiatojtV4_ets_ds_ IP_level_list_ordering . . . . . . . . . . . . 5-20
types . . . . . . . . . . . . . . . . . . . . . 5-42 ITAR_level_list_ordering . . . . . . . . . 5-21
Confirm_cancel_checkout_ ITEM_autogenerate_id . . . . . . . . . . . . 5-4
suppressed . . . . . . . . . . . . . . . . . . 5-8 ITEM_baseline_rev_msg . . . . . . . . . . 5-21
Confirm_checkin_suppressed . . . . . . . 5-9 ItemRevision_DirectModel3DMarkup_
Confirm_checkout_suppressed . . . . . . . 5-9 default_relation . . . . . . . . . . . . . 21-4
Confirmation_shown_on_reservation_ ItemRevision_Vis_Session_default_
dialogs . . . . . . . . . . . . . . . . . . . . . 5-8 relation . . . . . . . . . . . . . . . . . . . 21-5
DISPATCHER_CLIENT_ LDAP_admin_dn . . . . . . . . . . . . . . . 5-97
INSTALLED . . . . . . . . . . . . . . . . 5-26 LDAP_admin_pw . . . . . . . . . . . . . . . 5-98
DMI_markup_relation_primary . . . . 21-1 LDAP_attribute_mapping . . . . . . . . 5-105
ETS_available . . . . . . . . . . . . . . . . . 5-27 LDAP_base_dn . . . . . . . . . . . . . . . 5-106
ETS_home . . . . . . . . . . . . . . . . . . . . 5-27 LDAP_cert_db_path . . . . . . . . . . . . . 5-97
ETS_released_status_type_names . . . 5-30 LDAP_group_attr_mapping . . . . . . 5-103
ETS_trans_rqst_referenced_dataset_ LDAP_group_base_dn . . . . . . . . . . 5-102
types . . . . . . . . . . . . . . . . . . . . . 5-29 LDAP_group_object_class . . . . . . . . 5-103
ETS_trans_rqst_user_exit_states . . . 5-30 LDAP_group_query_filter . . . . . . . . 5-102
ETS_update_state_delay . . . . . . . . . 5-29 LDAP_ignore_users . . . . . . . . . . . . 5-107
ETS.PROVIDERS . . . . . . . . . . . . . . 5-28 LDAP_member_list_attr . . . . . . . . . 5-101
ETS.Repeating_UI.<ProviderName>. LDAP_member_type_attr . . . . . . . . 5-101
<ServiceName> . . . . . . . . . . . . . . 5-27 LDAP_object_type_attr . . . . . . . . . . 5-101
ETS.TRANSLATORS. LDAP_person_attr_mapping . . . . . . 5-108
<ProviderName> . . . . . . . . . . . . . 5-28 LDAP_port_number . . . . . . . . . . . . . 5-96
ETS.VALIDATE.<ProviderName>. LDAP_role_attr_mapping . . . . . . . . 5-105
<ServiceName> . . . . . . . . . . . . . . 5-28 LDAP_role_object_class . . . . . . . . . 5-104
Folder_mail_properties . . . . . . . . . . . 5-65 LDAP_role_query_filter . . . . . . . . . 5-104
Form_double_click . . . . . . . . . . . . . . 5-10 LDAP_service_hosts . . . . . . . . . . . . . 5-96
IDEAS_check_in_generate_vis_data_ LDAP_sync_group_flags . . . . . . . . . . 5-99
priority . . . . . . . . . . . . . . . . . . . . 5-35 LDAP_sync_member_flags . . . . . . . . 5-99
IDEAS_import_from_tdm_default_gen_vis_ LDAP_sync_role_flags . . . . . . . . . . 5-100
data_priority . . . . . . . . . . . . . . . . 5-34 LDAP_sync_user_flags . . . . . . . . . . . 5-98
IDEAS_import_from_tdm_gen_vis_data_ LDAP_use_ssl . . . . . . . . . . . . . . . . . 5-96
display . . . . . . . . . . . . . . . . . . . . 5-33 LDAP_user_object_class . . . . . . . . . 5-107
IDEAS_import_from_tdm_gen_vis_data_ LDAP_user_query_filter . . . . . . . . . 5-107
input . . . . . . . . . . . . . . . . . . . . . 5-34 license_warning_level . . . . . . . . . . . . 5-22
IDEAS_import_from_tdm_options_default_ Mail_OSMail_activated . . . . . . . . . . 5-67
gen_vis_data_priority . . . . . . . . . 5-35 Mail_server_charset . . . . . . . . . . . . . 5-66
IDEAS_import_translation_service_ Mail_server_name . . . . . . . . . . . . . . 5-66
name . . . . . . . . . . . . . . . . . . . . . 5-31 Mail_server_port . . . . . . . . . . . . . . . 5-66
IDEAS_on_demand_generate_vis_data_ MetaDataStamp_template . . . . . . . . 21-5
priority . . . . . . . . . . . . . . . . . . . . 5-36 METHOD_CM_execute_before_
IDEAS_translation_dataset_type_ custom . . . . . . . . . . . . . . . . . . . . . 5-5
names . . . . . . . . . . . . . . . . . . . . 5-32 NR_BYPASS . . . . . . . . . . . . . . . . . . . 5-5
IDEAS_translation_service_name . . . 5-31 NX_on_demand_generate_vis_data_
IdentifierContextPref . . . . . . . . . . . . . 5-4 priority . . . . . . . . . . . . . . . . . . . . 5-43
IdentifierLengthPref . . . . . . . . . . . . . 5-4 NX_tocgm_on_demand_generate_vis_data_
IMAN_capture_relation_primary . . . . 5-36 priority . . . . . . . . . . . . . . . . . . . . 5-44

Index
NX_tocgm_translation_service_ PASSWORD_special_characters . . . . 5-89

name . . . . . . . . . . . . . . . . . . . . . 5-43 PLM_End_Item_Key . . . . . . . . . . . . 21-6
NX_translation_service_name . . . . . . 5-42 Pro/ENGINEER_on_demand_generate_vis_
NXCheckMate. data_priority . . . . . . . . . . . . . . . . 5-49
CREATERENDERING . . . . . . . 5-109 Pro/ENGINEER_translation_service_
NXCheckMate. name . . . . . . . . . . . . . . . . . . . . . 5-49
SUMMARYRENDERING . . . . . 5-110 search_automatic_wildcard . . . . . . . . 5-51
NXCheckMateCreate. CREATE_ SecondaryVMUDatasets . . . . . . . . . . 21-7
REGISTEREDTO . . . . . . . . . . . 5-109 SOA_MaxOperationBracket
NXCheckMateRevision. InactiveTime . . . . . . . . . . . . . . . 5-91
SUMMARYRENDERING . . . . . 5-110 SOA_MaxOperationBracketTime . . . 5-91
NXCheckMateRevSummary. SUMMARY_ SOACAD_checkout_required . . . . . . . 5-22
REGISTEREDTO . . . . . . . . . . . 5-110 TC_ALLOW_ADHOC_
NXCheckMateSummary. SUMMARY_ VALIDATIONS . . . . . . . . . . . . . 5-116
REGISTEREDTO . . . . . . . . . . . 5-111 TC_check_object_before_create . . . . . 5-22
NXCMValData. TC_dataset_deep_copy_rules . . . . . . . . 5-5
CREATERENDERING . . . . . . . 5-111 TC_Dataset_Import_Exclude_
NXCMValData. Wildcard . . . . . . . . . . . . . . . . . . . 5-23
SUMMARYRENDERING . . . . . 5-112 TC_DIS_2D_named_ref . . . . . . . . . . 21-7
NXCMValDataCreate. CREATE_ TC_DIS_3D_named_ref . . . . . . . . . . 21-8
REGISTEREDTO . . . . . . . . . . . 5-111 TC_DIS_Search . . . . . . . . . . . . . . . . 21-8
NXCMValDataRevision. TC_external_application_names . . . . 5-94
SUMMARYRENDERING . . . . . 5-112 TC_external_application_types . . . . . 5-95
NXCMValDataRevSummary. SUMMARY_ TC_external_local_app_guid . . . . . . . 5-92
REGISTEREDTO . . . . . . . . . . . 5-112 TC_external_proxiable_objects . . . . . 5-92
NXCMValDataSummary. SUMMARY_ TC_external_proxiable_objects_
REGISTEREDTO . . . . . . . . . . . 5-113 props . . . . . . . . . . . . . . . . . . . . . 5-93
NXRDDV. TC_external_Requirements_proxy_props_
SUMMARYRENDERING . . . . . 5-114 external . . . . . . . . . . . . . . . . . . . 5-94
NXRDDVRevision. TC_external_Requirements_proxy_props_
SUMMARYRENDERING . . . . . 5-113 internal . . . . . . . . . . . . . . . . . . . 5-93
NXRDDVRevSummary. SUMMARY_ TC_fts_aci_port . . . . . . . . . . . . . . . . 5-52
REGISTEREDTO . . . . . . . . . . . 5-113 TC_fts_database_name . . . . . . . . . . . 5-52
NXRDDVSummary. SUMMARY_ TC_fts_default_language_type . . . . . 5-53
REGISTEREDTO . . . . . . . . . . . 5-114 TC_fts_engine . . . . . . . . . . . . . . . . . 5-53
NXRDDVValData. TC_fts_fsf_host . . . . . . . . . . . . . . . . 5-54
SUMMARYRENDERING . . . . . 5-115 TC_fts_fsf_port . . . . . . . . . . . . . . . . 5-54
NXRDDVValDataRevision. TC_fts_host . . . . . . . . . . . . . . . . . . . 5-55
SUMMARYRENDERING . . . . . 5-114 TC_fts_index_port . . . . . . . . . . . . . . 5-55
NXRDDVValDataRevSummary. TC_fts_index_retries . . . . . . . . . . . . 5-56
SUMMARY_ TC_fts_index_timeout . . . . . . . . . . . 5-56
REGISTEREDTO . . . . . . . . . . . 5-115 TC_fts_indexed_types . . . . . . . . . . . . 5-56
NXRDDVValDataSummary. SUMMARY_ TC_fts_indexing_wait_timeout . . . . . 5-57
REGISTEREDTO . . . . . . . . . . . 5-115 TC_fts_max_results . . . . . . . . . . . . . 5-57
OCS_company_email_domain . . . . . . 5-10 TC_fts_query_port . . . . . . . . . . . . . . 5-57
OCS_use_email_property . . . . . . . . . 5-10 TC_fts_real_time_indexing . . . . . . . . 5-58
OCS_use_presence_display . . . . . . . . 5-11 TC_fts_service_port . . . . . . . . . . . . . 5-58
PASSWORD_minimum_alpha . . . . . . 5-91 TC_language_data_entry . . . . . . . . . 5-59
PASSWORD_minimum_ TC_language_default . . . . . . . . . . . . 5-61
characters . . . . . . . . . . . . . . . . . 5-89 TC_language_localization_display . . . 5-62
PASSWORD_minimum_digits . . . . . . 5-90 TC_language_localized_property_value_
PASSWORD_minimum_special_ display . . . . . . . . . . . . . . . . . . . . 5-62
chars . . . . . . . . . . . . . . . . . . . . . 5-90 TC_language_localized_property_value_
PASSWORD_mixed_case_required . . 5-90 entry . . . . . . . . . . . . . . . . . . . . . 5-63

Index
TC_language_search . . . . . . . . . . . . 5-64 UGSnxtopvdirect_ets_ds_types . . . . . 5-47

TC_mail_interval . . . . . . . . . . . . . . . 5-67 UGSnxtopvdirect_UGALTREP_ets_nr_
TC_multi_site_ada_license_user_ types . . . . . . . . . . . . . . . . . . . . . 5-46
bypass . . . . . . . . . . . . . . . . . . . . 5-25 UGSnxtopvdirect_UGMASTER_ets_nr_
TC_project_bom_2nd_level_ types . . . . . . . . . . . . . . . . . . . . . 5-47
propagate . . . . . . . . . . . . . . . . . . . 6-4 UGSnxtopvdirect_UGPART_ets_nr_
TC_register_internal_service_ types . . . . . . . . . . . . . . . . . . . . . 5-47
modules . . . . . . . . . . . . . . . . . . . 5-30 UGSproetojt_ets_ds_types . . . . . . . . 5-50
TC_session_clearance . . . . . . . . . . . . 5-25 UGSproetojt_ProPrt_ets_nr_types . . . 5-50
TC_show_open_in_vmu_button . . . . . 21-9 VALIDATION_APPLICATIONS . . . 5-124
TC_use_tc_alias_in_pa8 . . . . . . . . . . 5-67 ValidationAgentRevision_
TC_VALIDATION_FILE_TYPES . . 5-117 DefaultChildProperties . . . . . . . 5-123
TC_VALIDATION_mandatory_ checkers_ ValidationAgentRevision_Folder_ default_
required . . . . . . . . . . . . . . . . . . 5-117 relation . . . . . . . . . . . . . . . . . . 5-123
TC_Validation_relation_primary . . . 5-118 ValidationAgentRevision_ValData_ default_
TC_VALIDATION_RESULT_ALLOW_ relation . . . . . . . . . . . . . . . . . . 5-124
REPLICA_OBJECT . . . . . . . . . . 5-118 ValidationMasterForm
TC_VALIDATION_run_validation_hidden_ ColumnPreferences . . . . . . . . . . 5-124
agents . . . . . . . . . . . . . . . . . . . 5-119 ValidationMasterFormColumn
TC_VALIDATION_TIMESTAMP_ WidthPreferences . . . . . . . . . . . 5-125
NREFS . . . . . . . . . . . . . . . . . . 5-120 ValToolAgentRevision_
TC_VALIDATION_ViewValidation DefaultChildProperties . . . . . . . 5-126
WithRuleSetColumnPreferences . . 5-122 ValToolAgentRevision_Tool_ default_
TC_VALIDATION_ViewValidation relation . . . . . . . . . . . . . . . . . . 5-126
WithRuleSetColumn Width VIS_multi_file_datasettypes . . . . . . . 21-9
Preferences . . . . . . . . . . . . . . . . 5-122 VIS_simpgen_admin_group . . . . . . . 5-51
TCCheckoutReserveOnly . . . . . . . . . 5-23 VisMarkup_relation_primary . . . . . . 21-9
TCDefaultKeepLimit . . . . . . . . . . . . 5-24 VisSession_relation_primary . . . . . . 21-10
TCDefaultKeepLimitByType . . . . . . . 5-24 VMU_Datasets . . . . . . . . . . . . . . . 21-10
Treat_Curr_Rev_As_Any_Rev . . . . . . . 5-6 VMU_FileSearchOrder . . . . . . . . . . 21-11
Treat_Next_Rev_As_Any_Rev . . . . . . . 5-6 VMU_RelationSearchOrder . . . . . . 21-12
TYPE_DISPLAY_RULES_list_of_primary_ ConfigurationContext_DefaultChildProperties
types . . . . . . . . . . . . . . . . . . . . . . 5-7 preference . . . . . . . . . . . . . . . . . . . . 10-85
TYPE_DISPLAY_RULES_list_types_of_ ConfigureToLoadEnableDefault VariantConfig
subclasses . . . . . . . . . . . . . . . . . . . 5-7 preference . . . . . . . . . . . . . . . . . . . . 19-75
<TypeName>_indexed_properties . . . 5-58 Confirm_cancel_checkout_suppressed
UGMASTER_DefaultChild preference . . . . . . . . . . . . . . . . . . . . . . 5-8
Properties . . . . . . . . . . . . . . . . . . 5-48 Confirm_checkin_suppressed
UGPART_DefaultChildProperties . . . 5-48 preference . . . . . . . . . . . . . . . . . . . . . . 5-9
UGSideastojt_IdeasAssembly_ets_nr_ Confirm_checkout_suppressed
types . . . . . . . . . . . . . . . . . . . . . 5-32 preference . . . . . . . . . . . . . . . . . . . . . . 5-9
UGSideastojt_IdeasDrawing_ets_nr_ Confirmation_shown_on_reservation_dialogs
types . . . . . . . . . . . . . . . . . . . . . 5-33 preference . . . . . . . . . . . . . . . . . . . . . . 5-8
UGSideastojt_IdeasPart_etsnr_ Connected_ToRules preference . . . . . . 22-22
types . . . . . . . . . . . . . . . . . . . . . 5-33 Consumer Packaged Goods
UGSnxtocgmdirect_ets_ds_types . . . . 5-46 preferences . . . . . . . . . . . . . . . . . . . . 22-4
UGSnxtocgmdirect_UGALTREP_etsnr_ TC_Interspec_URL . . . . . . . . . . . . . 22-4
types . . . . . . . . . . . . . . . . . . . . . 5-44 ContactInCompany_relation_primary
UGSnxtocgmdirect_UGMASTER_ets_nr_ preference . . . . . . . . . . . . . . . . . . . . 22-54
types . . . . . . . . . . . . . . . . . . . . . 5-45 controllingOccsForProcessConfiguration
UGSnxtocgmdirect_UGPART_ets_nr_ preference . . . . . . . . . . . . . . . . . . . . . 20-2
types . . . . . . . . . . . . . . . . . . . . . 5-45 Conventions
UGSnxtocgmdirect_UGSCENARIO_ets_nr_ Syntax definitions . . . . . . . . . . . . . . . 1-1
types . . . . . . . . . . . . . . . . . . . . . 5-45 copyPasteChunkNumber preference . . . 10-5

Index
cost_default_currency preference . . . . . 15-2 ADA_saveas_propagated_license_

CPDesignBriefRevision_ types . . . . . . . . . . . . . . . . . . . . . 5-12
DefaultChildProperties preference . . 10-86 AE_dataset_id_gen_by_type . . . . . . . 5-13
CPMarketingBriefRevision_ AE_dataset_id_postfix . . . . . . . . . . . 5-13
DefaultChildProperties preference . . 10-86 AE_dataset_id_prefix . . . . . . . . . . . . 5-13
CPTechnicalBriefRevision_ AE_dataset_id_separator . . . . . . . . . 5-13
DefaultChildProperties preference . . 10-86 AE_dataset_id_usage . . . . . . . . . . . . 5-14
CPThemeBoardRevision_ AE_dataset_id_use_rev . . . . . . . . . . . 5-14
DefaultChildProperties preference . . 10-86 Baseline_allow_edits . . . . . . . . . . . . 5-15
CR_allow_alternate_procedures Baseline_allowed_baserev_
preference . . . . . . . . . . . . . . . . . . . . . 11-2 statuses . . . . . . . . . . . . . . . . . . . 5-15
Create_<business_object>_default_type Baseline_create_snapshot_folder . . . . 5-15
preference . . . . . . . . . . . . . . . . . . . . . 10-5 Baseline_dryrun_always . . . . . . . . . . 5-16
Create_WorkspaceObject_mru_list Baseline_nxmanager_refile . . . . . . . . 5-16
preference . . . . . . . . . . . . . . . . . . . . . 10-6 Baseline_precise_bvr . . . . . . . . . . . . 5-17
Create_WorkspaceObject_mru_max Baseline_refile_not_required_item_
preference . . . . . . . . . . . . . . . . . . . . . 10-6 types . . . . . . . . . . . . . . . . . . . . . 5-17
Baseline_refile_required_dstypes . . . . 5-18
D Baseline_release_procedures . . . . . . . 5-18
Baseline_restricted_item_types . . . . . 5-18
Data Exchange baselineDryRun . . . . . . . . . . . . . . . . 5-16
GMS_UID_mapping_remote_site_ BOB_property_optimizations . . . . . . 5-19
index . . . . . . . . . . . . . . . . . . . . 18-58 CheckoutOnCreatePref . . . . . . . . . . . 5-19
Data Exchange preferences . . . . . . . . 18-57 IP_level_list_ordering . . . . . . . . . . . . 5-20
Alt_id_default_idContext_type . . . . 18-57 ITAR_level_list_ordering . . . . . . . . . 5-21
Alt_id_default_identifier_type . . . . . 18-57 ITEM_baseline_rev_msg . . . . . . . . . . 5-21
GMS_UID_mapping_dbname_ SOACAD_checkout_required . . . . . . . 5-22
index . . . . . . . . . . . . . . . . . . . . 18-57 TC_check_object_before_create . . . . . 5-22
GS_USER_NAME . . . . . . . . . . . . . 18-58 TC_Dataset_Import_Exclude_
GS_USER_PASSWORD . . . . . . . . . 18-59 Wildcard . . . . . . . . . . . . . . . . . . . 5-23
TC_default_gms_site . . . . . . . . . . . 18-60 TC_language_search . . . . . . . . . . . . 5-64
TC_default_gms_transfer_mode . . . 18-61 TC_multi_site_ada_license_user_
TC_gms_enable_immediate_ bypass . . . . . . . . . . . . . . . . . . . . 5-25
option . . . . . . . . . . . . . . . . . . . . 18-61 TC_project_bom_2nd_level_
TC_gms_export_default_ propagate . . . . . . . . . . . . . . . . . . . 6-4
transfermode . . . . . . . . . . . . . . 18-62 TC_session_clearance . . . . . . . . . . . . 5-25
TC_gms_export_transfermode_for_<site_ TCCheckoutReserveOnly . . . . . . . . . 5-23
name> . . . . . . . . . . . . . . . . . . . 18-62 TCDefaultKeepLimit . . . . . . . . . . . . 5-24
TC_gms_gs_bos_service_url . . . . . . 18-62 TCDefaultKeepLimitByType . . . . . . . 5-24
TC_gms_gs_server_url . . . . . . . . . . 18-63 USER_baseline_dryrun_validator . . . 5-26
TC_gms_gs_uri . . . . . . . . . . . . . . . 18-63 Data sharing
TC_gms_import_default_ GMS_UID_mapping_remote_site_
transfermode . . . . . . . . . . . . . . 18-61 index . . . . . . . . . . . . . . . . . . . . 18-58
TC_gms_monitoring_gui_total_number_of_ PDX_pkg_file_name . . . . . . . . . . . . 18-59
steps_for_transfer . . . . . . . . . . . 18-63 TC_disallow_release_status_on_
TC_gms_sso_enabled . . . . . . . . . . . 18-64 replica . . . . . . . . . . . . . . . . . . . 18-29
TIE_allow_import_with_different_ TC_follow_ownership_chain_max_site_
SML . . . . . . . . . . . . . . . . . . . . . 18-64 count . . . . . . . . . . . . . . . . . . . . 18-32
TIE_exp_pending_object . . . . . . . . . 18-64 TC_force_remote_sites_exclude_
TIE_reference_objects_list . . . . . . . 18-65 files . . . . . . . . . . . . . . . . . . . . . 18-32
TIE_validate_against_xsd . . . . . . . . 18-66 TC_master_locale_<site_name> . . . 18-37
Data management preferences . . . . . . . 5-11 TC_on_demand_sync_broadcast_
ADA_allow_license_propagation . . . . 5-11 mode . . . . . . . . . . . . . . . . . . . . 18-40
ADA_enabled . . . . . . . . . . . . . . . . . . 5-12 TC_Populate_FSC_Server_Targets . . 9-36

Index
TC_stub_dataset_files_after_ownership_ ITEM_relation_types_update_
transfer . . . . . . . . . . . . . . . . . . 18-52 lmd . . . . . . . . . . . . . . . . . . . . . 18-15
TC_validate_stub_tickets . . . . . . . . 18-56 Multi-Site Collaboration
Data sharing preferences . . . . . . . . . . 18-16 preferences . . . . . . . . . . . . . . . . . 18-1
Alt_id_default_idContext_type . . . . 18-57 ODS_multiprocess_idle_subprocess_
Alt_id_default_identifier_type . . . . . 18-57 timeout . . . . . . . . . . . . . . . . . . 18-15
Baseline_auto_remote_checkout_ ODS_multiprocess_initial_subprocess_
allowed . . . . . . . . . . . . . . . . . . . . 18-1 count . . . . . . . . . . . . . . . . . . . . 18-16
GMS_UID_mapping_dbname_ ODS_multiprocess_max_subprocess_
index . . . . . . . . . . . . . . . . . . . . 18-57 count . . . . . . . . . . . . . . . . . . . . 18-16
GS_USER_NAME . . . . . . . . . . . . . 18-58 ODS_multiprocess_mode . . . . . . . . 18-16
GS_USER_PASSWORD . . . . . . . . . 18-59 ODS_permitted_sites . . . . . . . . . . . 18-17
HUB_no_export_record_transfer_site_ ODS_proxy_server_type . . . . . . . . . 18-17
list . . . . . . . . . . . . . . . . . . . . . . . 18-2 ODS_publication_sites . . . . . . . . . . 18-18
IDSM_Compression . . . . . . . . . . . . . 18-3 ODS_restricted_sites . . . . . . . . . . . 18-18
IDSM_Compression_Type . . . . . . . . . 18-3 ODS_searchable_sites . . . . . . . . . . 18-18
IDSM_do_not_resend_up_to_date_ ODS_searchable_sites_excluded . . . 18-19
file . . . . . . . . . . . . . . . . . . . . . . . 18-4 ODS_site . . . . . . . . . . . . . . . . . . . . 18-19
IDSM_dsa_notification_email_ ODS_suppress_pubrec_if_no_
address . . . . . . . . . . . . . . . . . . . 18-5 access . . . . . . . . . . . . . . . . . . . . 18-19
IDSM_dsa_sites_permitted_to_push_ SRM_host_port . . . . . . . . . . . . . . . 18-60
admin_data . . . . . . . . . . . . . . . . 18-4 TC_<daemon name>_<site ID>_prog_
IDSM_exclude_unpublished_ number . . . . . . . . . . . . . . . . . . 18-23
components . . . . . . . . . . . . . . . . 18-5 TC_<daemon name>_<site name>_port_
IDSM_ft_buffer_kb . . . . . . . . . . . . . 18-6 number . . . . . . . . . . . . . . . . . . 18-23
IDSM_ft_client_timeout . . . . . . . . . . 18-6 TC_<daemon name>_<site name>_prog_
IDSM_ft_port_get_number_from_ number . . . . . . . . . . . . . . . . . . 18-24
services . . . . . . . . . . . . . . . . . . . 18-6 Tc_allow_users_edit_pfdata_
IDSM_ft_port_number . . . . . . . . . . . 18-7 options . . . . . . . . . . . . . . . . . . . 18-24
IDSM_ft_server_timeout . . . . . . . . . . 18-7 TC_altrep_update_lmd . . . . . . . . . . 18-25
IDSM_ft_use_rpc_mode . . . . . . . . . . 18-8 TC_appref_registry_site . . . . . . . . . 18-25
IDSM_permitted_checkout_sites . . . . 18-8 TC_assembly_xml_relation . . . . . . . 18-25
IDSM_permitted_checkout_users_from_ TC_background_object_export_
site_sitename . . . . . . . . . . . . . . . 18-8 dir . . . . . . . . . . . . . . . . . . . . . . 18-26
IDSM_permitted_sites . . . . . . . . . . . 18-9 TC_bom_level_export . . . . . . . . . . . 18-26
IDSM_permitted_transfer_sites . . . . 18-9 TC_check_remote_user_priv_from_
IDSM_permitted_transfer_users_from_site_ sites . . . . . . . . . . . . . . . . . . . . . 18-27
sitename . . . . . . . . . . . . . . . . . . 18-9 TC_dataset_vers_export . . . . . . . . . 18-28
IDSM_permitted_users_from_site_ TC_default_gms_site . . . . . . . . . . . 18-60
sitename . . . . . . . . . . . . . . . . . 18-10 TC_default_gms_transfer_mode . . . 18-61
IDSM_proxy_client_alternate_proxy_host_ TC_directly_transferable_classes . . . 18-29
for . . . . . . . . . . . . . . . . . . . . . . 18-10 TC_disallowed_replica_relations . . . 18-29
IDSM_proxy_server_type . . . . . . . . 18-11 TC_do_not_insert_imported_objects_into_
IDSM_restricted_sites . . . . . . . . . . 18-11 folder . . . . . . . . . . . . . . . . . . . . 18-30
ITEM_autopublish . . . . . . . . . . . . . 18-11 TC_EMAIL_AFTER_BACKGROUND_
ITEM_autopublish_ignore_errors . . 18-12 REMOTE_IMPORT . . . . . . . . . . 18-31
ITEM_autopublish_sites . . . . . . . . . 18-13 Tc_export_pfmember_replica . . . . . . 18-31
ITEM_id_allow_if_registry_down . . 18-13 TC_external_app_reg_url . . . . . . . . 18-31
ITEM_id_always_register_on_ TC_gms_enable_immediate_
creation . . . . . . . . . . . . . . . . . . 18-13 option . . . . . . . . . . . . . . . . . . . . 18-61
ITEM_id_registry . . . . . . . . . . . . . . 18-14 TC_gms_export_default_
ITEM_id_registry_site . . . . . . . . . . 18-14 transfermode . . . . . . . . . . . . . . 18-62
ITEM_id_unregister_on_delete . . . . 18-14 TC_gms_export_transfermode_for_<site_
name> . . . . . . . . . . . . . . . . . . . 18-62

Index
TC_gms_gs_bos_service_url . . . . . . 18-62 TC_use_group_admin_as_default_replica_

TC_gms_gs_server_url . . . . . . . . . . 18-63 owner . . . . . . . . . . . . . . . . . . . . 18-56
TC_gms_gs_uri . . . . . . . . . . . . . . . 18-63 TIE_allow_import_with_different_
TC_gms_import_default_ SML . . . . . . . . . . . . . . . . . . . . . 18-64
transfermode . . . . . . . . . . . . . . 18-61 TIE_exp_pending_object . . . . . . . . . 18-64
TC_gms_monitoring_gui_total_number_of_ TIE_reference_objects_list . . . . . . . 18-65
steps_for_transfer . . . . . . . . . . . 18-63 TIE_validate_against_xsd . . . . . . . . 18-66
TC_gms_sso_enabled . . . . . . . . . . . 18-64 Dataset ID preferences
TC_hub_groups . . . . . . . . . . . . . . . 18-33 AE_dataset_id_gen_by_type . . . . . . . 5-13
TC_idsm_client_def_timeout . . . . . . 18-35 AE_dataset_id_postfix . . . . . . . . . . . 5-13
TC_idsm_client_initial_timeout . . . . 18-35 AE_dataset_id_prefix . . . . . . . . . . . . 5-13
TC_idsm_proxy_server_site_table . . 18-36 AE_dataset_id_separator . . . . . . . . . 5-13
TC_ie_error_report . . . . . . . . . . . . . 18-36 AE_dataset_id_usage . . . . . . . . . . . . 5-14
TC_modified_only_export . . . . . . . . 18-37 AE_dataset_id_use_rev . . . . . . . . . . . 5-14
TC_multi_site_project_member_ APPR_allow_separate_spatial_
bypass . . . . . . . . . . . . . . . . . . . . . 6-5 processing . . . . . . . . . . . . . . . . . 19-1
TC_ods_client_def_timeout . . . . . . . 18-39 APPR_max_appearances_per_
TC_ods_client_extra_attributes . . . . 18-38 process . . . . . . . . . . . . . . . . . . . . 19-2
TC_ods_client_initial_timeout . . . . . 18-40 <DATASET TYPE>_saveas_pattern
TC_ods_proxy_server_site_table . . . 18-40 preference . . . . . . . . . . . . . . . . . . . . . 5-73
TC_ownership_export . . . . . . . . . . . 18-41 Dataset_DefaultChildProperties
TC_post_export_script . . . . . . . . . . 18-42 preference . . . . . . . . . . . . . . . . . . . . 10-84
TC_pre_import_script . . . . . . . . . . . 18-43 <dataset_name>.CREATE_REGISTEREDTO
Tc_preserve_replica_pfmember_ preference . . . . . . . . . . . . . . . . . . . . . 10-7
ownership . . . . . . . . . . . . . . . . . 18-43 <dataset_name>.FORM_REGISTEREDTO
Tc_publish_pfdata_with_ preference . . . . . . . . . . . . . . . . . . . . . 10-7
assemblies . . . . . . . . . . . . . . . . 18-44 <dataset_name>.REGISTEREDTO
Tc_publish_pfmembers_with_ preference . . . . . . . . . . . . . . . . . . . . . 10-8
pftemplate . . . . . . . . . . . . . . . . 18-44 <dataset_name>.SUMMARY_
Tc_publish_pftemplate_with_ REGISTEREDTO preference . . . . . . . 10-9
pfmember . . . . . . . . . . . . . . . . . 18-45 DATASET_object_columns_hidden
TC_publishable_classes . . . . . . . . . 18-45 preference . . . . . . . . . . . . . . . . . . . . 10-10
TC_reference_update_lmd . . . . . . . 18-46 DATASET_object_columns_shown
TC_relation_export_on_transfer . . . 18-47 preference . . . . . . . . . . . . . . . . . . . . 10-10
TC_relation_required_on_export . . . 18-47 DATASET_object_widths_hidden
TC_relation_required_on_ preference . . . . . . . . . . . . . . . . . . . . 10-11
transfer . . . . . . . . . . . . . . . . . . 18-48 DATASET_object_widths_shown
TC_remote_checkin_assy_option . . . 18-48 preference . . . . . . . . . . . . . . . . . . . . 10-11
TC_remote_checkin_exclude_ DATASET_saveas_allow_duplicates
relations . . . . . . . . . . . . . . . . . . 18-49 preference . . . . . . . . . . . . . . . . . . . . . 5-69
TC_remote_checkin_preserve_replica_ DATASET_saveas_allow_name_modification
owning_user_and_group . . . . . . 18-50 preference . . . . . . . . . . . . . . . . . . . . . 5-69
TC_remote_checkin_relation_send_as_ DATASET_saveas_always_copy
replica . . . . . . . . . . . . . . . . . . . 18-51 preference . . . . . . . . . . . . . . . . . . . . . 5-70
TC_rendering_update_lmd . . . . . . . 18-46 DATASET_saveas_force_name_validation
TC_replica_volume . . . . . . . . . . . . . 18-51 preference . . . . . . . . . . . . . . . . . . . . . 5-70
TC_replication_exclude_types . . . . . 18-51 DATASET_saveas_never_copy
TC_retain_group_on_import . . . . . . 18-52 preference . . . . . . . . . . . . . . . . . . . . . 5-71
TC_subscribable_replica_classes . . . 18-53 DATASET_saveas_owner preference . . . 5-71
TC_sync_max_assy_level . . . . . . . . 18-53 DATASET_saveas_pattern
TC_sync_revision_rules . . . . . . . . . 18-54 preference . . . . . . . . . . . . . . . . . . . . . 5-72
TC_transfer_area . . . . . . . . . . . . . . 18-54 datasetParmDef.REGISTEREDTO
TC_truncate_file_name . . . . . . . . . . 18-55 preference . . . . . . . . . . . . . . . . . . . . 22-41

Index
datasetParmDefBCDRevision. DefaultAsBuiltCompareProperties
REGISTEREDTO preference . . . . . . 22-38 preference . . . . . . . . . . . . . . . . . . . . 22-80
datasetParmDefBitDefRevision. DefaultAsMaintainedAccCheckProperties
datasetParmDefBoolRevision. DefaultAsMaintainedCompareProperties
datasetParmDefDateRevision. DesignContext composite properties . . 19-39
REGISTEREDTO preference . . . . . . 22-36 DesignContext context definition
datasetParmDefDblRevision. preferences . . . . . . . . . . . . . . . . . . . 19-24
REGISTEREDTO preference . . . . . . 22-34 DesignContext filter configuration
datasetParmDefHexRevision. preferences . . . . . . . . . . . . . . . . . . . 19-31
REGISTEREDTO preference . . . . . . 22-37 DesignContext interoperability
datasetParmDefIntRevision. preferences . . . . . . . . . . . . . . . . . . . 19-34
REGISTEREDTO preference . . . . . . 22-33 DesignContext performance tuning
datasetParmDefSEDRevision. preferences . . . . . . . . . . . . . . . . . . . 19-37
REGISTEREDTO preference . . . . . . 22-37 DesignContext preferences . . . . . 19-9–19-10
datasetParmDefStrRevision. DesignContext_ItemID_Query_lookup_
REGISTEREDTO preference . . . . . . 22-35 string . . . . . . . . . . . . . . . . . . . . 19-32
datasetParmGrpDef. REGISTEREDTO DesignContext_PSE_
preference . . . . . . . . . . . . . . . . . . . . 22-40 Synchronization . . . . . . . . . . . . 19-36
datasetParmGrpDefRevision. DesignContextIncludeSub
REGISTEREDTO preference . . . . . . 22-41 ComponentsForSpatialSearch . . 19-32
datasetParmGrpValRevision. DesignContextLoadRDV
REGISTEREDTO preference . . . . . . 22-39 ContextObjectMode . . . . . . . . . . 19-17
datasetProductVariant. REGISTEREDTO DesignContextMaximum
preference . . . . . . . . . . . . . . . . . . . . 22-42 ShownTabs . . . . . . . . . . . . . . . . 19-33
datasetProductVariantCreate. DesignContextPickUp
REGISTEREDTO preference . . . . . . 22-43 NewBackgroundAppearance . . . . 19-17
datasetProductVariantIntent. DesignContextPreciseRevRule . . . . 19-34
REGISTEREDTO preference . . . . . . 22-43 DesignContextRDVContextObject
datasetProductVariantIntentCreate. AddToECObjectPseudoFolder
REGISTEREDTO preference . . . . . . 22-44 Preference . . . . . . . . . . . . . . . . 19-16
DATASETTYPE_object_columns_hidden DesignContextShow
preference . . . . . . . . . . . . . . . . . . . . 10-12 ClearanceDBMenu . . . . . . . . . . 19-24
DATASETTYPE_object_columns_shown PortalDesignContext
preference . . . . . . . . . . . . . . . . . . . . 10-12 AllowNoWorkParts . . . . . . . . . . 19-26
DATASETTYPE_object_widths_hidden PortalDesignContext
preference . . . . . . . . . . . . . . . . . . . . 10-12 CADbookmarkType . . . . . . . . . . 19-34
DATASETTYPE_object_widths_shown PortalDesignContext
preference . . . . . . . . . . . . . . . . . . . . 10-13 ExcludedWorkPart.Types . . . . . . 19-26
DatasetTypesPref preference . . . . . . . 10-13 PortalDesignContext
Default_Base_Calendar_Preference MaxMatchingBOMLines . . . . . . 19-38
preference . . . . . . . . . . . . . . . . . . . . . 15-3 PortalDesignContext
Default_StructureContext_Type MaxMatchingObjects . . . . . . . . . 19-37
preference . . . . . . . . . . . . . . . . . . . . 19-44 PortalDesignContext
Default_Transient_Server preference . . 9-32 SearchEnginePreference . . . . . . 19-31
Default_Transient_Volume_Id PortalDesignContext
preference . . . . . . . . . . . . . . . . . . . . . 9-32 VISbookmarkType . . . . . . . . . . . 19-35
DefaultAccountabilityCheckProperties PortalDesignContext
preference . . . . . . . . . . . . . . . . . . . . 20-33 WIPRevRule . . . . . . . . . . . . . . . 19-27
DefaultActualToSystemDate PortalDesignContextAlways
preference . . . . . . . . . . . . . . . . . . . . . 15-2 ResetFilterConfigurationPanel . . 19-33
DefaultAsBuiltAccCheckProperties . . . 22-81 PortalDesignContextAttributeSchema
SuppressedAttributes . . . . . . . . 19-31

Index
PortalDesignContextECObject DesignContext_ItemID_Query_lookup_string
.WorkPartRelationships . . . . . . . 19-26 preference . . . . . . . . . . . . . . . . . . . . 19-32
PortalDesignContextECObject DesignContext_PSE_Synchronization
WorkPartProperties . . . . . . . . . . 19-25 preference . . . . . . . . . . . . . . . . . . . . 19-36
PortalDesignContextECObject. DesignContextIncludeSubComponents
TYPE . . . . . . . . . . . . . . . . . . . . 19-25 ForSpatialSearch preference . . . . . . . 19-32
PortalDesignContextFindInstallation DesignContextLoadRDVContextObjectMode
TreeWalkIncrement . . . . . . . . . . 19-30 preference . . . . . . . . . . . . . . . . . . . . 19-17
PortalDesignContextIs DesignContextMaximumShownTabs
InstallationAssemblyMethod.has_ preference . . . . . . . . . . . . . . . . . . . . 19-33
bomline_prop.value . . . . . . . . . . 19-29 DesignContextPickUp
PortalDesignContextIsInstallation NewBackgroundAppearance
AssemblyMethod . . . . . . . . . . . . 19-28 preference . . . . . . . . . . . . . . . . . . . . 19-17
PortalDesignContextIsInstallation DesignContextPreciseRevRule
AssemblyMethod.has_bomline_ preference . . . . . . . . . . . . . . . . . . . . 19-34
prop.name . . . . . . . . . . . . . . . . 19-29 DesignContextRDVContextObject
PortalDesignContextIsInstallation AddToECObjectPseudo FolderPreference
AssemblyMethod.hasIRType. preference . . . . . . . . . . . . . . . . . . . . 19-16
Type . . . . . . . . . . . . . . . . . . . . 19-28 DesignContextShow ClearanceDBMenu
PortalDesignContextProduct preference . . . . . . . . . . . . . . . . . . . . 19-24
ContextProperties . . . . . . . . . . . 19-18 DirectModel_DefaultChildProperties
PortalDesignContextProduct preference . . . . . . . . . . . . . . . . . . . . 10-83
ItemProperties . . . . . . . . . . . . . 19-10 Dispatcher preferences . . . . . . . . . . . . 5-26
PortalDesignContextProductContext CATIA_check_in_generate_vis_data_
ColumnsHiddenPref . . . . . . . . . 19-20 priority . . . . . . . . . . . . . . . . . . . . 5-37
PortalDesignContextProductContext CATIA_checkin_generate_vis_data_
ColumnsHiddenPrefWidth . . . . . 19-22 priority . . . . . . . . . . . . . . . . . . . . 5-38
PortalDesignContextProductContext CATIA_on_demand_generate_vis_data_
ColumnsShownPref . . . . . . . . . . 19-19 priority . . . . . . . . . . . . . . . . . . . . 5-38
PortalDesignContextProductContext CATIA_translation_service_name . . . 5-37
ColumnsShownPrefWidth . . . . . 19-19 CATIA_V4_check_in_generate_vis_data_
PortalDesignContextProductItem priority . . . . . . . . . . . . . . . . . . . . 5-41
ColumnsHiddenPref . . . . . . . . . 19-13 CATIA_V4_on_demand_generate_vis_data_
PortalDesignContextProductItem priority . . . . . . . . . . . . . . . . . . . . 5-41
ColumnsHiddenPrefWidth . . . . . 19-15 CATIA_V4_translation_service_
PortalDesignContextProductItem name . . . . . . . . . . . . . . . . . . . . . 5-40
ColumnsShownPref . . . . . . . . . . 19-12 CATIA_work_dir . . . . . . . . . . . . . . . 5-40
PortalDesignContextProductItem COMMONcatiatojt_catia_ets_nr_
ColumnsShownPrefWidth . . . . . 19-12 types . . . . . . . . . . . . . . . . . . . . . 5-42
PortalDesignContextProductItem COMMONcatiatojt_CATPart_ets_nr_
Properties.attribute-value . . . . . 19-11 types . . . . . . . . . . . . . . . . . . . . . 5-39
PortalDesignContextProductItem COMMONcatiatojt_CATProduct_ets_nr_
Query . . . . . . . . . . . . . . . . . . . . 19-24 types . . . . . . . . . . . . . . . . . . . . . 5-39
PortalDesignContextQPLServers . . . 19-31 COMMONcatiatojt_ets_ds_types . . . . 5-39
PortalDesignContextSetVariant COMMONcatiatojtV4_ets_ds_
RulesMaxTargetAppearances . . . 19-38 types . . . . . . . . . . . . . . . . . . . . . 5-42
PortalDesignContextSupport DISPATCHER_CLIENT_
InstallationAssemblySelection . . 19-30 INSTALLED . . . . . . . . . . . . . . . . 5-26
PortalDesignContextUse ETS_available . . . . . . . . . . . . . . . . . 5-27
UnconfigurableSearchResults . . . 19-30 ETS_home . . . . . . . . . . . . . . . . . . . . 5-27
RDVLoadAppearanceGroupMode . . 19-18 ETS_released_status_type_names . . . 5-30
TC_show_open_in_nx_button . . . . . 19-36 ETS_trans_rqst_referenced_dataset_
DesignContext product item types . . . . . . . . . . . . . . . . . . . . . 5-29
preferences . . . . . . . . . . . . . . . . . . . 19-10 ETS_trans_rqst_user_exit_states . . . 5-30

Index
ETS_update_state_delay . . . . . . . . . 5-29 UGSnxtocgmdirect_UGPART_ets_nr_

ETS.PROVIDERS . . . . . . . . . . . . . . 5-28 types . . . . . . . . . . . . . . . . . . . . . 5-45
ETS.Repeating_UI.<ProviderName>. UGSnxtocgmdirect_UGSCENARIO_ets_nr_
<ServiceName> . . . . . . . . . . . . . . 5-27 types . . . . . . . . . . . . . . . . . . . . . 5-45
ETS.TRANSLATORS. UGSnxtopvdirect_ets_ds_types . . . . . 5-47
<ProviderName> . . . . . . . . . . . . . 5-28 UGSnxtopvdirect_UGALTREP_ets_nr_
ETS.VALIDATE.<ProviderName>. types . . . . . . . . . . . . . . . . . . . . . 5-46
<ServiceName> . . . . . . . . . . . . . . 5-28 UGSnxtopvdirect_UGMASTER_ets_nr_
IDEAS_check_in_generate_vis_data_ types . . . . . . . . . . . . . . . . . . . . . 5-47
priority . . . . . . . . . . . . . . . . . . . . 5-35 UGSnxtopvdirect_UGPART_ets_nr_
IDEAS_import_from_tdm_default_gen_vis_ types . . . . . . . . . . . . . . . . . . . . . 5-47
data_priority . . . . . . . . . . . . . . . . 5-34 UGSproetojt_ets_ds_types . . . . . . . . 5-50
IDEAS_import_from_tdm_gen_vis_data_ UGSproetojt_ProPrt_ets_nr_types . . . 5-50
display . . . . . . . . . . . . . . . . . . . . 5-33 DISPATCHER_CLIENT_INSTALLED
IDEAS_import_from_tdm_gen_vis_data_ preference . . . . . . . . . . . . . . . . . . . . . 5-26
input . . . . . . . . . . . . . . . . . . . . . 5-34 DMI_markup_relation_primary
IDEAS_import_from_tdm_options_default_ preference . . . . . . . . . . . . . . . . . . . . . 21-1
gen_vis_data_priority . . . . . . . . . 5-35 DPV preferences . . . . . . . . . . . . . . . . 25-12
IDEAS_import_translation_service_ DPV_ccuaservice_url . . . . . . . . . . . . 25-4
name . . . . . . . . . . . . . . . . . . . . . 5-31 DPV_logdatapurge_days . . . . . . . . . . 25-4
IDEAS_on_demand_generate_vis_data_ DPV_rawdata_location . . . . . . . . . . . 25-5
priority . . . . . . . . . . . . . . . . . . . . 5-36 DPVAdmin . . . . . . . . . . . . . . . . . . . 25-1
IDEAS_translation_dataset_type_ DPVClusterGroup Revision_
names . . . . . . . . . . . . . . . . . . . . 5-32 DefaultChildProperties . . . . . . . . 25-1
IDEAS_translation_service_name . . . 5-31 DPVClusterGroupContent_relation_
IMAN_capture_relation_primary . . . . 5-36 primary . . . . . . . . . . . . . . . . . . . 25-3
IMAN_Drawing_relation_primary . . . 5-48 DPVClusterGroupRevision_shown_
NX_on_demand_generate_vis_data_ relations . . . . . . . . . . . . . . . . . . . 25-2
priority . . . . . . . . . . . . . . . . . . . . 5-43 DPV_ccuaservice_url preference . . . . . . 25-4
NX_tocgm_on_demand_generate_vis_data_ DPV_logdatapurge_days preference . . . 25-4
priority . . . . . . . . . . . . . . . . . . . . 5-44 DPV_rawdata_location preference . . . . 25-5
NX_tocgm_translation_service_ DPVAdmin preference . . . . . . . . . . . . . 25-1
name . . . . . . . . . . . . . . . . . . . . . 5-43 DPVClusterGroup Revision_
NX_translation_service_name . . . . . . 5-42 DefaultChildProperties preference . . . 25-1
Pro/ENGINEER_on_demand_generate_vis_ DPVClusterGroupContent_relation_primary
data_priority . . . . . . . . . . . . . . . . 5-49 preference . . . . . . . . . . . . . . . . . . . . . 25-3
Pro/ENGINEER_translation_service_ DPVClusterGroupRevision_shown_relations
name . . . . . . . . . . . . . . . . . . . . . 5-49 preference . . . . . . . . . . . . . . . . . . . . . 25-2
TC_register_internal_service_ DRAG_AND_DROP_Default_dataset_type
modules . . . . . . . . . . . . . . . . . . . 5-30 preference . . . . . . . . . . . . . . . . . . . . 10-14
UGMASTER_DefaultChild DRAG_AND_DROP_file_limit
Properties . . . . . . . . . . . . . . . . . . 5-48 preference . . . . . . . . . . . . . . . . . . . . 10-14
UGPART_DefaultChildProperties . . . 5-48 DRAG_AND_DROP_SWING_dialog_enable
UGSideastojt_IdeasAssembly_ets_nr_ preference . . . . . . . . . . . . . . . . . . . . 10-15
types . . . . . . . . . . . . . . . . . . . . . 5-32 DrawingSheet_DefaultChildProperties
UGSideastojt_IdeasDrawing_ets_nr_ preference . . . . . . . . . . . . . . . . . . . . 10-84
types . . . . . . . . . . . . . . . . . . . . . 5-33
UGSideastojt_IdeasPart_ets_nr_
types . . . . . . . . . . . . . . . . . . . . . 5-33 E
UGSnxtocgmdirect_ets_ds_types . . . . 5-46
UGSnxtocgmdirect_UGALTREP_ets_nr_ ECM_affected_item_relations
types . . . . . . . . . . . . . . . . . . . . . 5-44 preference . . . . . . . . . . . . . . . . . . . . . 12-6
UGSnxtocgmdirect_UGMASTER_ets_nr_ ECM_bomchange_formtype
types . . . . . . . . . . . . . . . . . . . . . 5-45 preference . . . . . . . . . . . . . . . . . . . . . 12-7

Index
ECM_bomchange_tooltip_properties EDA_PcbViewableOptionDefault . . . . 24-7

preference . . . . . . . . . . . . . . . . . . . . . 12-7 EDA_PreferredLocalTS . . . . . . . . . . 24-7
ECM_change_id_modifiable EDA_PWBItemTypeDefault . . . . . . . 24-8
preference . . . . . . . . . . . . . . . . . . . . . 12-8 EDA_ReconcilePartsRevRule . . . . . 24-11
ECM_change_name_is_mandatory EDA_SaveAsFolderDefault . . . . . . . . 24-8
preference . . . . . . . . . . . . . . . . . . . . . 12-8 EDA_SaveIntermediateDS . . . . . . . . 24-8
ECM_delivered_engine_status EDA_
preference . . . . . . . . . . . . . . . . . . . . . 12-8 SchematicBOMOptionDefault . . . 24-9
ECM_form_relation preference . . . . . . . 12-9 EDA_SchematicItemTypeDefault . . . 24-9
ECM_genealogy_expansion_rule EDA_SchematicLockingDynamic . . . . 24-9
preference . . . . . . . . . . . . . . . . . . . . . 12-9 EDA_SchematicViewable
ECM_note_types_to_track OptionDefault . . . . . . . . . . . . . . 24-10
preference . . . . . . . . . . . . . . . . . . . . . 12-9 EDA_
ECM_notehistory_extra_columns SimulationLockingDynamic . . . . 24-10
preference . . . . . . . . . . . . . . . . . . . . 12-10 EDA_ViewType . . . . . . . . . . . . . . . 24-10
ECM_prev_structure_relation EDA_AddSchematicItemToCCABOM
ECM_prev_structure_relation_name EDA_BOMTemplate_pcb preference . . . 24-1
preference . . . . . . . . . . . . . . . . . . . . 12-11 EDA_BOMTemplate_sch preference . . . 24-2
ECM_property_access preference . . . . 12-11 EDA_CCABaseItemTypeDefault
ECM_property_display_names preference . . . . . . . . . . . . . . . . . . . . . 24-2
preference . . . . . . . . . . . . . . . . . . . . 12-11 EDA_CCAItemTypeDefault
ECM_property_names preference . . . . 12-12 preference . . . . . . . . . . . . . . . . . . . . . 24-2
ECM_pseudofolder_names EDA_CCAVariantItemTypeDefault
ECM_set_genealogy preference . . . . . 12-13 EDA_CheckComponentExistence
ECM_supercedure_tooltip_properties preference . . . . . . . . . . . . . . . . . . . . . 24-3
preference . . . . . . . . . . . . . . . . . . . . 12-13 EDA_CheckInOptionDefault
ECM_track_variant_condition_changes preference . . . . . . . . . . . . . . . . . . . . . 24-3
preference . . . . . . . . . . . . . . . . . . . . 12-14 EDA_CombinedBOMOptionDefault
ECM_varianthistory_extra_columns preference . . . . . . . . . . . . . . . . . . . . . 24-3
preference . . . . . . . . . . . . . . . . . . . . 12-14 EDA_CombinedViewable OptionDefault
EDA preferences . . . . . . . . . . . . 24-54, 24-1 preference . . . . . . . . . . . . . . . . . . . . . 24-4
EDA_ EDA_ComponentItemTypes
AddSchematicItemToCCABOM . . 24-1 preference . . . . . . . . . . . . . . . . . . . . . 24-4
EDA_BOMTemplate_pcb . . . . . . . . . 24-1 EDA_DefinePWBWith preference . . . . . 24-5
EDA_BOMTemplate_sch . . . . . . . . . 24-2 EDA_DerivedDataConfigDefault
EDA_CCABaseItemTypeDefault . . . . 24-2 preference . . . . . . . . . . . . . . . . . . . . . 24-5
EDA_CCAItemTypeDefault . . . . . . . 24-2 EDA_DesignReviseSync preference . . . . 24-5
EDA_ EDA_FutureVariantName
CCAVariantItemTypeDefault . . . 24-11 preference . . . . . . . . . . . . . . . . . . . . . 24-6
EDA_CheckComponentExistence . . . 24-3 EDA_PcbBOMOptionDefault
EDA_CheckInOptionDefault . . . . . . . 24-3 preference . . . . . . . . . . . . . . . . . . . . . 24-6
EDA_ EDA_PcbLockingDynamic
CombinedBOMOptionDefault . . . . 24-3 preference . . . . . . . . . . . . . . . . . . . . . 24-7
EDA_CombinedViewable EDA_PcbViewableOptionDefault
OptionDefault . . . . . . . . . . . . . . . 24-4 preference . . . . . . . . . . . . . . . . . . . . . 24-7
EDA_ComponentItemTypes . . . . . . . 24-4 EDA_PreferredLocalTS preference . . . . 24-7
EDA_DefinePWBWith . . . . . . . . . . . 24-5 EDA_PWBItemTypeDefault
EDA_DerivedDataConfigDefault . . . . 24-5 preference . . . . . . . . . . . . . . . . . . . . . 24-8
EDA_DesignReviseSync . . . . . . . . . . 24-5 EDA_ReconcilePartsRevRule
EDA_FutureVariantName . . . . . . . . 24-6 preference . . . . . . . . . . . . . . . . . . . . 24-11
EDA_PcbBOMOptionDefault . . . . . . 24-6 EDA_SaveAsFolderDefault
EDA_PcbLockingDynamic . . . . . . . . 24-7 preference . . . . . . . . . . . . . . . . . . . . . 24-8

Index
EDA_SaveIntermediateDS EngChange Revision_DefaultChildProperties

preference . . . . . . . . . . . . . . . . . . . . . 24-8 preference . . . . . . . . . . . . . . . 10-84, 12-16
EDA_SchematicBOMOptionDefault EngChange_Revision_Change_Type_Revise_
preference . . . . . . . . . . . . . . . . . . . . . 24-9 no_copy preference . . . . . . . . . . . . . . 22-5
EDA_SchematicItemTypeDefault EngChange_Revision_Change_Type_SaveAs_
preference . . . . . . . . . . . . . . . . . . . . . 24-9 no_copy preference . . . . . . . . . . . . . . 22-5
EDA_SchematicLockingDynamic Enterprise BOP preferences . . . . . . . . 20-62
preference . . . . . . . . . . . . . . . . . . . . . 24-9 Environment variable script files . . . . . . 2-1
EDA_SchematicViewable OptionDefault Environment variables
preference . . . . . . . . . . . . . . . . . . . . 24-10 AdaptiveApplicationDisplay . . . . . . . . 3-1
EDA_SimulationLockingDynamic AdaptiveApplicationDisplay
preference . . . . . . . . . . . . . . . . . . . . 24-10 Duration . . . . . . . . . . . . . . . . . . . 3-1
EDA_ViewType preference . . . . . . . . . 24-10 AM_BYPASS . . . . . . . . . . . . . . . . . . . 3-1
EINT_<adapter_name> preference . . . . . 7-1 AM_MODE . . . . . . . . . . . . . . . . . . . . 3-1
EINT_adapter_names preference . . . . . . 7-1 AM_PERFORMANCE_
EINT_copy_to_clipboard preference . . . . 7-5 STATISTICS . . . . . . . . . . . . . . . . . 3-1
EINT_create_new_forms preference . . . . 7-4 API_ALWAYS_REFRESH . . . . . . . . . . 3-2
EINT_form_refresh_pref preference . . . . 7-5 API_FILE_CACHE . . . . . . . . . . . . . . 3-2
EINT_global_services_datasource_names API_JOURNAL . . . . . . . . . . . . . . . . . 3-2
preference . . . . . . . . . . . . . . . . . . . . . . 7-2 API_NO_CACHING . . . . . . . . . . . . . . 3-2
EINT_global_services_urls preference . . . 7-2 API_SET_BYPASS . . . . . . . . . . . . . . . 3-2
EINT_ibi_api_library preference . . . . . . 7-6 AUTHORIZATION_MODE . . . . . . . . . 3-2
EINT_import_selected_rows BMIDE_SCRIPT_ARGS . . . . . . . . . . . 3-2
preference . . . . . . . . . . . . . . . . . . . . . . 7-4 FMS_FCCSTARTUPLOG . . . . . . . . . . 3-3
EINT_item_rev_pref preference . . . . . . . 7-5 FMS_HOME . . . . . . . . . . . . . . . . . . . 3-3
EINT_max_num_rows preference . . . . . . 7-6 FSC_HOME . . . . . . . . . . . . . . . . . . . 3-3
EINT_storage_type preference . . . . . . . . 7-3 HSM_TAKE_BACKUP . . . . . . . . . . . . 3-3
EINT_update_on_save preference . . . . . . 7-4 IMAN_SDL_MAGIC . . . . . . . . . . . . . . 3-3
eIntegrator Admin preferences . . . . . . . . 7-8 IMAN_SYS_UID_DIR . . . . . . . . . . . . 3-3
ATTRSHARING_datasource_connection_ IMAN_SYS2_UID_DIR . . . . . . . . . . . . 3-3
details . . . . . . . . . . . . . . . . . . . . . 7-3 JRE_HOME . . . . . . . . . . . . . . . . . . . 3-3
ATTRSHARING_max_rows_ KNOWLEDGEBASE_EVALUATE . . . . 3-3
expected . . . . . . . . . . . . . . . . . . . . 7-3 LANG . . . . . . . . . . . . . . . . . . . . . . . . 3-4
EINT_<adapter_name> . . . . . . . . . . . 7-1 LC_ALL . . . . . . . . . . . . . . . . . . . . . . 3-4
EINT_adapter_names . . . . . . . . . . . . 7-1 LD_LIBRARY_PATH . . . . . . . . . . . . . 3-4
EINT_copy_to_clipboard . . . . . . . . . . . 7-5 LDR_CNTRL . . . . . . . . . . . . . . . . . . . 3-4
EINT_create_new_forms . . . . . . . . . . . 7-4 LIBRARY_PATH . . . . . . . . . . . . . . . . 3-5
EINT_form_refresh_pref . . . . . . . . . . . 7-5 LOG_VOLUME_DIR . . . . . . . . . . . . . 3-5
EINT_global_services_datasource_ LOG_VOLUME_NAME . . . . . . . . . . . 3-5
names . . . . . . . . . . . . . . . . . . . . . 7-2 MB_CHARS . . . . . . . . . . . . . . . . . . . 3-5
EINT_global_services_urls . . . . . . . . . 7-2 MGC_HOME . . . . . . . . . . . . . . . . . . . 3-5
EINT_ibi_api_library . . . . . . . . . . . . . 7-6 MGC_LOCATION_MAP . . . . . . . . . . . 3-5
EINT_import_selected_rows . . . . . . . . 7-4 MGC_TC_CONFIG_FILE . . . . . . . . . . 3-6
EINT_item_rev_pref . . . . . . . . . . . . . . 7-5 MGLS_LICENSE_FILE . . . . . . . . . . . 3-6
EINT_max_num_rows . . . . . . . . . . . . 7-6 MOVE_TRANSACTIONS_COUNT . . . 3-6
EINT_storage_type . . . . . . . . . . . . . . 7-3 MOZ_PLUGIN_PATH . . . . . . . . . . . . 3-6
EINT_update_on_save . . . . . . . . . . . . 7-4 NLS_SORT . . . . . . . . . . . . . . . . . . . . 3-6
Enable_Create_Classic_Change NXMGR_allow_3_tier_interop . . . . . . . 3-6
preference . . . . . . . . . . . . . . . . . . . . 12-15 ORACLE_SERVER . . . . . . . . . . . . . . 3-6
Enable_ReportDesigner_Reports ORACLE_SID . . . . . . . . . . . . . . . . . . 3-6
preference . . . . . . . . . . . . . . . . . . . . 15-13 PATH . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Enable_Show_Classic_Change PLUGIN_LOGFILE . . . . . . . . . . . . . . 3-6
preference . . . . . . . . . . . . . . . . . . . . 12-15 POM_SCHEMA . . . . . . . . . . . . . . . . . 3-7
Enable_thumbnails preference . . . . . . 10-15 POM_TRANSMIT_DIR . . . . . . . . . . . 3-7

Index
PUBLISH_PDF_ERROR_LOG_ TC_USE_LOV_SHARED_
LOC . . . . . . . . . . . . . . . . . . . . . . . 3-7 MEMORY . . . . . . . . . . . . . . . . . . 3-14
PUBLISH_PDF_ERRORS . . . . . . . . . 3-7 TC_USE_PREFS_SHARED_
PUBLISH_PDF_INTERVAL . . . . . . . . 3-7 MEMORY . . . . . . . . . . . . . . . . . . 3-14
PUBLISH_PDF_MAX_JOBS . . . . . . . 3-8 TC_USE_TEST_ATTR_
PUBLISH_PDF_TIMEOUT . . . . . . . . 3-8 MAPPINGS . . . . . . . . . . . . . . . . 3-14
PUBLISH_PDF_VVCP_DEBUG . . . . . 3-8 TC_USER_LIB . . . . . . . . . . . . . . . . 3-14
PUBLISH_PDF_VVCP_DEBUG_ TC_USER_MSG_DIR . . . . . . . . . . . . 3-14
LOC . . . . . . . . . . . . . . . . . . . . . . . 3-8 TC_USER_TOOLS . . . . . . . . . . . . . . 3-14
PUBLISH_PDF_VVCP_TIMEOUT . . . 3-8 TC_USER_UID_DIR . . . . . . . . . . . . 3-14
ROSE . . . . . . . . . . . . . . . . . . . . . . . . 3-8 TC_WEB_NO_CACHE . . . . . . . . . . . 3-15
ROSE_DB . . . . . . . . . . . . . . . . . . . . . 3-8 TC_WSDL_MAX_PROPERTIES . . . . 3-15
SHLIB_PATH . . . . . . . . . . . . . . . . . . 3-9 TC_XML_ENCODING variable . . . . . 3-15
TAO_ROOT . . . . . . . . . . . . . . . . . . . . 3-9 TCSSO_LOGIN_SERVICE_URL . . . . 3-15
TC_APP_UID_DIR . . . . . . . . . . . . . . . 3-9 TCVIS_ALSG_ENABLED . . . . . . . . . 3-15
TC_BIN . . . . . . . . . . . . . . . . . . . . . . 3-9 TEMP_FILESEARCHPATH . . . . . . . 3-15
TC_BYPASS_CANNED_ TNS_ADMIN . . . . . . . . . . . . . . . . . . 3-15
METHODS . . . . . . . . . . . . . . . . . . 3-9 Transient_Volume_Installation_
TC_DATA . . . . . . . . . . . . . . . . . . 1-4, 3-9 Location . . . . . . . . . . . . . . . . . . . 3-15
TC_DATA_MODEL . . . . . . . . . . . . . . 3-9 UGII_APISERVER_PROGRAM . . . . 3-15
TC_DB_CONNECT . . . . . . . . . . . . . . 3-9 UGII_BASE_DIR . . . . . . . . . . . . . . . 3-15
TC_DISABLE_FLASH . . . . . . . . . . . 3-10 UGII_OPTION . . . . . . . . . . . . . . . . 3-16
TC_FS_SERVICE . . . . . . . . . . . . . . 3-10 UGII_USE_NEW_SURFACE_FILE_
TC_HANDLERS_DEBUG . . . . . . . . . 3-10 FORMAT . . . . . . . . . . . . . . . . . . 3-16
TC_HELP_FILE . . . . . . . . . . . . . . . 3-10 UGII_USERFCN . . . . . . . . . . . . . . . 3-16
TC_HTDOCS . . . . . . . . . . . . . . . . . . 3-10 UGS_LICENSE_SERVER . . . . . . . . 3-16
TC_INCLUDE . . . . . . . . . . . . . . . . . 3-10 UIL_INCLUDE . . . . . . . . . . . . . . . . 3-15
TC_INSTALL_DIR . . . . . . . . . . . . . . 3-10 XFILESEARCHPATH . . . . . . . . . . . 3-16
TC_JOURNAL . . . . . . . . . . . . . . . . . 3-10 EPM_adhoc_signoffs preference . . . . . . 11-3
TC_KEEP_SYSTEM_LOG . . . . . . . . 3-11 EPM_ARG_target_user_group_list_separator
TC_LIBRARY . . . . . . . . . . . . . . . . . 3-11 preference . . . . . . . . . . . . . . . . . . . . . 11-8
TC_LOG . . . . . . . . . . . . . . . . . . . . . 3-11 EPM_enable_apply_template_changes
TC_LOG_DIR . . . . . . . . . . . . . . . . . 3-11 preference . . . . . . . . . . . . . . . . . . . . . 11-3
TC_MSG_ROOT . . . . . . . . . . . . . . . 3-11 EPM_multiple_processes_targets
TC_no_obsolete_message . . . . . . . . . 3-11 preference . . . . . . . . . . . . . . . . . . . . . 11-6
TC_NX_DEFAULT_PART . . . . . . . . . 3-11 EPM_notify_url_format preference . . . 11-14
TC_ONLINE_HELP . . . . . . . . . . . . . 3-11 EPM_resource_pool_recipients
TC_PERFORMANCE_MONITOR . . . 3-11 preference . . . . . . . . . . . . . . . . . . . . . 11-8
TC_POM_JOURNALLING . . . . . . . . 3-12 EPM_resource_pool_restrict_subscription
TC_PRINTER . . . . . . . . . . . . . . . . . 3-12 preference . . . . . . . . . . . . . . . . . . . . . 11-8
TC_ROOT . . . . . . . . . . . . . . . . . 1-4, 3-12 EPM_sub_process_target_inheritance
TC_SLOW_SQL . . . . . . . . . . . . . . . . 3-12 preference . . . . . . . . . . . . . . . . . . . . . 11-7
TC_SOA_MAX_PROPERTIES . . . . . 3-12 EPM_tessellation_servers
TC_SQL_DEBUG . . . . . . . . . . . . . . 3-12 preference . . . . . . . . . . . . . . . . . . . 19-114
TC_SSO_APP_ID . . . . . . . . . . . . . . . 3-13 EPM_tessellation_target_type
TC_SSO_CHANGE_PASSWORD_ preference . . . . . . . . . . . . . . . . . . . 19-113
PAGE . . . . . . . . . . . . . . . . . . . . . 3-13 EPM_valid_roles_to_assign_responsible_party
TC_SSO_LOGIN_PAGE . . . . . . . . . . 3-13 preference . . . . . . . . . . . . . . . . . . . . . 11-5
TC_SSO_LOGIN_URL . . . . . . . . . . . 3-13 EPM_valid_user_to_apply_assignment_list
TC_SSO_SERVICE . . . . . . . . . . . . . 3-12 preference . . . . . . . . . . . . . . . . . . . . . 11-5
TC_TMP_DIR . . . . . . . . . . . . . . . . . 3-13 EPMDoTask_DefaultChildProperties
TC_TRACEBACK . . . . . . . . . . . . . . 3-13 preference . . . . . . . . . . . . . . . . . . . . 10-83
TC_USE_DEFAULT_EXPORT_ EPMDoTaskDefinition_
SITES . . . . . . . . . . . . . . . . . . . . 3-14 DefaultChildProperties preference . . 10-83

Index
EPMSelectSignoffTaskDefinition_ ETS_trans_rqst_referenced_dataset_types
DefaultChildProperties preference . . 10-83 preference . . . . . . . . . . . . . . . . . . . . . 5-29
EPMTask_DefaultChildProperties ETS_trans_rqst_user_exit_states
EPMTaskDefinition_DefaultChildProperties ETS_update_state_delay . . . . . . . . . . . 5-29
preference . . . . . . . . . . . . . . . . . . . . 10-83 ETS.PROVIDERS . . . . . . . . . . . . . . . . 5-28
ERP Connect to SAP preferences . . . . 23-49 ETS.Repeating_UI.<ProviderName>.
IMAN_SAP_sideinfo_file . . . . . . . . . 23-51 <ServiceName> preference . . . . . . . . . 5-27
TC_ERP_current_schema_name . . . 23-49 ETS.TRANSLATORS.
TC_ERP_dataset_types_to_ <ProviderName> . . . . . . . . . . . . . . . . 5-28
transfer . . . . . . . . . . . . . . . . . . 23-52 ETS.VALIDATE.<ProviderName>.
TC_ERP_mapping_files . . . . . . . . . 23-49 <ServiceName> . . . . . . . . . . . . . . . . . 5-28
TC_ERP_rellog_file_path . . . . . . . . 23-50
TC_ERP_uom_mapping_file . . . . . . 23-50 F
TC_SAP_alt_bomview_file . . . . . . . 23-50
TC_SAP_cad_tables_path . . . . . . . . 23-51 FaultCode.MROCREATERENDERING
TC_SAP_sapcad_dir . . . . . . . . . . . . 23-51 preference . . . . . . . . . . . . . . . . . . . . 22-89
ESM_<Category>_Software_Types . . . 22-27 FaultCode.RENDERING preference . . 22-89
ESM_Compatibility_Report_Excel_Template_ FaultCode.SUMMARYRENDERING
Dataset preference . . . . . . . . . . . . . . 22-33 preference . . . . . . . . . . . . . . . . . . . . 22-90
ESM_HW_Compatibility_Report_Excel_ File caching preferences . . . . . . . . 9-22–9-23
StyleSheet_Dataset preference . . . . . 22-32 blobbyVolume_NT . . . . . . . . . . . . . . 9-28
ESM_HW_Compatibility_Report_HTML_ blobbyVolume_UNX . . . . . . . . . . . . . 9-28
StyleSheet_Dataset preference . . . . . 22-31 Default_Transient_Server . . . . . . . . . 9-32
ESM_HW_Compatibility_Report_ Default_Transient_Volume_Id . . . . . . 9-32
TransferMode preference . . . . . . . . . 22-30 Fms_BootStrap_Urls . . . . . . . . . . . . 9-32
ESM_Processor_architecture_attr FSC_HOME . . . . . . . . . . . . . . . . . . 9-33
preference . . . . . . . . . . . . . . . . . . . . 22-30 Multisite_Ticket_Expiration_
ESM_Processor_byteOrder_attr Interval . . . . . . . . . . . . . . . . . . . 9-27
preference . . . . . . . . . . . . . . . . . . . . 22-30 TC_<file type>_Cache_Mode . . . . . . . 9-25
ESM_processor_direct_child_of_hardware TC_Cache_Allowed . . . . . . . . . . . . . 9-24
preference . . . . . . . . . . . . . . . . . . . . 22-28 TC_Cache_Dir . . . . . . . . . . . . . . . . . 9-24
ESM_Processor_is_gateway_attr TC_Cache_Mode . . . . . . . . . . . . . . . 9-25
preference . . . . . . . . . . . . . . . . . . . . 22-28 TC_Cache_Protection . . . . . . . . . . . . 9-26
ESM_Processor_linked_attr TC_Cache_Size . . . . . . . . . . . . . . . . 9-24
preference . . . . . . . . . . . . . . . . . . . . 22-29 TC_STAGING_AREA . . . . . . . . . . . . 9-26
ESM_Processor_memoryType_attr TC_System_Logging . . . . . . . . . . . . . 9-27
preference . . . . . . . . . . . . . . . . . . . . 22-29 TC_Volume_Failover_Trigger . . . . . . 9-29
ESM_Processor_programmableInService_attr TC_Volume_Failover_Volume_
preference . . . . . . . . . . . . . . . . . . . . 22-29 Name . . . . . . . . . . . . . . . . . . . . . 9-29
ESM_Processor_Type preference . . . . 22-27 TC_VOLUME_MONITOR_CRITICAL_
ESM_Software_Categories LEVEL . . . . . . . . . . . . . . . . . . . . 9-30
preferences . . . . . . . . . . . . . . . . . . . 22-26 TC_VOLUME_MONITOR_WARNING_
ESM_SW_Compatibility_Report_Excel_ LEVEL . . . . . . . . . . . . . . . . . . . . 9-30
StyleSheet_Dataset preference . . . . . 22-32 TC_Volume_Status_Resync_
ESM_SW_Compatibility_Report_HTML_ Interval . . . . . . . . . . . . . . . . . . . 9-28
StyleSheet_Dataset preference . . . . . 22-32 Ticket_Expiration_Interval . . . . . . . . 9-27
ESM_SW_Compatibility_Report_ Transient_Volume_RootDir . . . . . . . . 9-31
TransferMode preference . . . . . . . . . 22-31 UNLOAD_LOGGING_LEVEL . . . . . 9-36
ETS_available preference . . . . . . . . . . 5-27 UNLOAD_MINIMUM_LIFE . . . . . . . 9-35
ETS_home preference . . . . . . . . . . . . . 5-27 UNLOAD_TRIGGER_CEILING . . . . 9-33
ETS_released_status_type_names UNLOAD_TRIGGER_FLOOR . . . . . . 9-34
preference . . . . . . . . . . . . . . . . . . . . . 5-30 FindCheckedOutColumnsShownPref
preference . . . . . . . . . . . . . . . . . . . . 20-13

Index
FindCheckedOutColumnsShownWidthPref Full-text search preferences . . . . . . . . . 5-51

preference . . . . . . . . . . . . . . . . . . . . 20-14 search_automatic_wildcard . . . . . . . . 5-51
FLColumnCatIVFSeparatorPref
preference . . . . . . . . . . . . . . . . . . . . 10-15 G
FLColumnCatObjSeparatorPref
preference . . . . . . . . . . . . . . . . . . . . 10-16 GANTT chart viewer preferences . . . . 20-72
Fms_BootStrap_Urls preference . . . . . . 9-32 MEGANTTDefaultDisplayMode . . . 20-73
FMS_FCCSTARTUPLOG variable . . . . . 3-3 MEGANTTDefaultDurationTime
FMS_HOME variable . . . . . . . . . . . . . . 3-3 Color . . . . . . . . . . . . . . . . . . . . 20-74
Folder_ColumnPreferences MEGANTTDefaultDurationTime
preference . . . . . . . . . . . . . . . . . . . 10-121 Mode . . . . . . . . . . . . . . . . . . . . 20-73
Folder_DefaultChildProperties MEGANTTDefaultEditMode . . . . . . 20-73
preference . . . . . . . . . . . . . . . . . . . . 10-83 MEGANTTDefaultFlowColor . . . . . 20-74
Folder_mail_properties preference . . . . 5-65 MEGANTTDefaultMarkedColor . . . 20-74
FOLDER_object_columns_hidden MEGANTTElementHeight . . . . . . . 20-72
preference . . . . . . . . . . . . . . . . . . . . 10-16 MEGANTTElementRGBfillColor . . . 20-72
FOLDER_object_columns_shown MEGANTTimplicitFlowColor . . . . . 20-75
preference . . . . . . . . . . . . . . . . . . . . 10-17 MEGANTTMarkedFlowColor . . . . . 20-75
FOLDER_object_widths_hidden GCS_classify_type preference . . . . . . . . 16-8
preference . . . . . . . . . . . . . . . . . . . . 10-17 GDE_exclude_list preference . . . . . . . 22-25
FOLDER_object_widths_shown GDE_objects_with_integer_quantity
Form_DefaultChildProperties GDELink_default_type preference . . . 22-25
preference . . . . . . . . . . . . . . . . . . . . 10-84 GDEOcc_display_instance_num_for_types
Form_double_click preference . . . . . . . . 5-10 preference . . . . . . . . . . . . . . . . . . . . 20-13
FORM_object_columns_hidden GenericBOPAllowedTemplates
FORM_object_columns_shown GenericBOPTemplate preference . . . . 20-67
preference . . . . . . . . . . . . . . . . . . . . 10-19 Global_transfer_access preference . . . . 11-9
FORM_object_widths_hidden GMO_enable_new_pnum_match_criteria
FORM_object_widths_shown GMO_GRP_browser_default
FormTypesPref preference . . . . . . . . . 10-20 GMO_GRP_edit_prop_mapping_default
FSC_HOME preference . . . . . . . . . . . . 9-33 preference . . . . . . . . . . . . . . . . . . . . . 22-8
FSC_HOME variable . . . . . . . . . . . . . . . 3-3 GMO_GRP_hostname_default
Full text search preferences preference . . . . . . . . . . . . . . . . . . . . . 22-7
TC_fts_aci_port . . . . . . . . . . . . . . . . 5-52 GMO_GRP_port preference . . . . . . . . . 22-7
TC_fts_database_name . . . . . . . . . . . 5-52 GMO_GRP_req_edit_props_default
TC_fts_default_language_type . . . . . 5-53 preference . . . . . . . . . . . . . . . . . . . . . 22-8
TC_fts_engine . . . . . . . . . . . . . . . . . 5-53 GMO_GRP_req_ir_types preference . . . 22-8
TC_fts_fsf_host . . . . . . . . . . . . . . . . 5-54 GMO_GRP_show preference . . . . . . . . 22-6
TC_fts_fsf_port . . . . . . . . . . . . . . . . 5-54 GMO_MATFORM_AUTOCREATE
TC_fts_host . . . . . . . . . . . . . . . . . . . 5-55 preference . . . . . . . . . . . . . . . . . . . . 22-22
TC_fts_index_port . . . . . . . . . . . . . . 5-55 GMO_RDV_enable_audit_criteria
TC_fts_index_retries . . . . . . . . . . . . 5-56 preference . . . . . . . . . . . . . . . . . . . . 22-12
TC_fts_indexed_types . . . . . . . . . . . . 5-56 GMS_UID_mapping_dbname_
TC_fts_indexing_wait_timeout . . . . . 5-57 index . . . . . . . . . . . . . . . . . . . . . . . 18-57
TC_fts_max_results . . . . . . . . . . . . . 5-57 GMS_UID_mapping_remote_site_index
TC_fts_query_port . . . . . . . . . . . . . . 5-57 preference . . . . . . . . . . . . . . . . . . . . 18-58
TC_fts_real_time_indexing . . . . . . . . 5-58 Group object mapping preferences . . . 5-102
TC_fts_service_port . . . . . . . . . . . . . 5-58 LDAP_group_attr_mapping . . . . . . 5-103
TCG_fts_index_timeout . . . . . . . . . . 5-56 LDAP_group_base_dn . . . . . . . . . . 5-102
<TypeName>_indexed_properties . . . 5-58 LDAP_group_object_class . . . . . . . . 5-103

Index
LDAP_group_query_filter . . . . . . . . 5-102 ICPanelOccAttrChangeDefs

GROUP_object_columns_hidden preference . . . . . . . . . . . . . . . . . . . . 19-64
preference . . . . . . . . . . . . . . . . . . . . 10-20 ICPanelOccAttrChangeWidths
GROUP_object_columns_shown preference . . . . . . . . . . . . . . . . . . . . 19-64
preference . . . . . . . . . . . . . . . . . . . . 10-21 ICS_allow_deprecated_lovs_on_copy
GROUP_object_widths_hidden preference . . . . . . . . . . . . . . . . . . . . 16-10
preference . . . . . . . . . . . . . . . . . . . . 10-21 ICS_allow_deprecated_lovs_on_update
GROUP_object_widths_shown preference . . . . . . . . . . . . . . . . . . . . . 16-9
preference . . . . . . . . . . . . . . . . . . . . 10-21 ICS_allow_min_max_range_override
GS_USER_NAME preference . . . . . . . 18-58 preference . . . . . . . . . . . . . . . . . . . . 16-11
GS_USER_PASSWORD preference . . . 18-59 ICS_allow_remote_parent preference . . 16-6
ICS_attribute_displayable_properties
H preference . . . . . . . . . . . . . . . . . . . . 16-12
ICS_attribute_mapping_trim_zeros
HiddenPerspectives preference . . . . . . 10-22 preference . . . . . . . . . . . . . . . . . . . . . 17-1
HierarchicalWSO_HierarchicalWSO_default_ ICS_available_languages preference . . . 16-2
relation preference . . . . . . . . . . . . . . 22-68 ICS_classifiable_types preference . . . . . 17-1
HRN_associated_part_relation_secondary ICS_classification_master_site
HRN_fixing_assignment_relation_primary ICS_classify_immediately preference . . 17-3
preference . . . . . . . . . . . . . . . . . . . . 22-48 ICS_classify_immediately_NX
HRN_node_referenced_component_relation_ preference . . . . . . . . . . . . . . . . . . . . . 17-3
secondary preference . . . . . . . . . . . . 22-46 ICS_classify_new preference . . . . . . . . 17-4
HRN_part_data_relation_primary ICS_classify_sendto preference . . . . . . 17-16
preference . . . . . . . . . . . . . . . . . . . . 22-47 ICS_copy_classid_pattern preference . . 16-3
HRN_wire_length_data_relation_primary ICS_datasettype_for_class
HSM preference ICS_default_class_document
HSM_integration_enabled . . . . . . . . . 9-4 preference . . . . . . . . . . . . . . . . . . . . . 17-6
HSM_primary_tier_hosts . . . . . . . . . . 9-5 ICS_default_instance_document
HSM_read_thru_supported . . . . . . . . . 9-4 preference . . . . . . . . . . . . . . . . . . . . . 17-5
HSM_secondary_tier_capacity . . . . . . . 9-5 ICS_default_root_selector_entries
HSM_integration_enabled preference . . . 9-4 preference . . . . . . . . . . . . . . . . . . . . . 17-8
HSM_primary_tier_hosts preference . . . . 9-5 ICS_enable_graphical_browser
HSM_read_thru_supported preference . . 9-4 preference . . . . . . . . . . . . . . . . . . . . . 17-7
HSM_secondary_tier_capacity ICS_enforce_min_max_constraints_on_copy
preference . . . . . . . . . . . . . . . . . . . . . . 9-5 preference . . . . . . . . . . . . . . . . . . . . 16-11
HSM_TAKE_BACKUP variable . . . . . . . 3-3 ICS_enforce_min_max_constraints_on_update
HUB_no_export_record_transfer_site_list preference . . . . . . . . . . . . . . . . . . . . 16-10
preference . . . . . . . . . . . . . . . . . . . . . 18-2 ICS_GraphicsBuilder preference . . . . . 17-7
ICS_hierarchy_list_icon_size
I preference . . . . . . . . . . . . . . . . . . . . . 17-8
ICS_hierarchy_sort_option
IC_baseline_carry_forward_active_changes preference . . . . . . . . . . . . . . . . . . . . . 17-8
preference . . . . . . . . . . . . . . . . . . . . 19-61 ICS_ico_action_after_saveas
IC_baseline_carry_forward_status preference . . . . . . . . . . . . . . . . . . . . 17-11
preference . . . . . . . . . . . . . . . . . . . . 19-62 ICS_import_attribute_find_free_dbindex
ICPanelAttachChangeDefs preference . . . . . . . . . . . . . . . . . . . . . 16-9
preference . . . . . . . . . . . . . . . . . . . . 19-63 ICS_import_attribute_use_dbindex
ICPanelAttachChangeWidths preference . . . . . . . . . . . . . . . . . . . . . 16-8
preference . . . . . . . . . . . . . . . . . . . . 19-63 ICS_itemrev_master_dataset_relation
ICPanelBomChangeDefs preference . . 19-62 preference . . . . . . . . . . . . . . . . . . . . 17-11
ICPanelBomChangeWidths ICS_mapping_target_type

Index
ICS_master_datasettypes_for_itemrev IDEAS_import_translation_service_name
ICS_max_number_of_components IDEAS_manager_library preference . . 23-46
preference . . . . . . . . . . . . . . . . . . . . 17-12 IDEAS_on_demand_generate_vis_data_
ICS_migrate_classid_pattern priority preference . . . . . . . . . . . . . . . 5-36
preference . . . . . . . . . . . . . . . . . . . . . 16-4 IDEAS_translation_dataset_type_names
ICS_new_classid_pattern preference . . . 16-2 preference . . . . . . . . . . . . . . . . . . . . . 5-32
ICS_override_unit_definition_precision IDEAS_translation_service_name
ICS_presented_class_documents IDENTIFIER_idincontext preference . . 5-20
preference . . . . . . . . . . . . . . . . . . . . . 17-6 IdentifierContextPref preference . . . . . . 5-4
ICS_presented_instance_documents IdentifierContextTypeDefault
ICS_root_selector_entries preference . . 17-9 IdentifierLengthPref preference . . . . . . . 5-4
ICS_search_default_revision_rule_ IdentifierTypeDefault preference . . . . 10-25
<application name> preference . . . . . 17-13 IDSM_Compression preference . . . . . . . 18-3
ICS_search_use_revision_rule IDSM_Compression_Type preference . . 18-3
preference . . . . . . . . . . . . . . . . . . . . 17-13 IDSM_do_not_resend_up_to_date_file
ICS_share_related preference . . . . . . . . 16-5 preference . . . . . . . . . . . . . . . . . . . . . 18-4
ICS_show_autofilter preference . . . . . 17-10 IDSM_dsa_notification_email_address
ICS_synchronize_automatically preference . . . . . . . . . . . . . . . . . . . . . 18-5
preference . . . . . . . . . . . . . . . . . . . . 17-14 IDSM_dsa_sites_permitted_to_push_admin_
ICS_synchronize_sites preference . . . . 17-14 data preference . . . . . . . . . . . . . . . . . 18-4
ICS_table_header_style preference . . . 17-14 IDSM_exclude_unpublished_components
ICS_table_pagesize preference . . . . . . 17-15 preference . . . . . . . . . . . . . . . . . . . . . 18-5
ICS_unit_active . . . . . . . . . . . . . . . . . 16-7 IDSM_ft_buffer_kb preference . . . . . . . 18-6
ICS_unit_default preference . . . . . . . . . 16-7 IDSM_ft_client_timeout preference . . . . 18-6
ICS_use_access_control preference . . . 17-15 IDSM_ft_get_port_number_from_services
ICS_use_view_attributes_when_moving_icos preference . . . . . . . . . . . . . . . . . . . . . 18-6
preference . . . . . . . . . . . . . . . . . . . . . 16-4 IDSM_ft_port_number preference . . . . . 18-7
ICS_user_defined_button_class IDSM_ft_server_timeout preference . . . 18-7
preference . . . . . . . . . . . . . . . . . . . . 17-10 IDSM_ft_use_rpc_mode preference . . . . 18-8
ICS_view_selection_order preference . . 16-5 IDSM_permitted_checkout_sites
ICS_web_preferred_jt_image preference . . . . . . . . . . . . . . . . . . . . . 18-8
preference . . . . . . . . . . . . . . . . . . . . 17-15 IDSM_permitted_checkout_users_from_site_
IDCAttachmentColumnsShownPref sitename preference . . . . . . . . . . . . . . 18-8
preference . . . . . . . . . . . . . . . . . . . . 10-23 IDSM_permitted_sites preference . . . . . 18-9
IDCAttachmentColumnWidthsPref IDSM_permitted_transfer_sites
IDCStructureColumnsShownPref IDSM_permitted_transfer_users_from_site_
preference . . . . . . . . . . . . . . . . . . . . 10-24 sitename preference . . . . . . . . . . . . . . 18-9
IDCStructureColumnWidthsPref IDSM_permitted_users_from_site_sitename
IDEAS_check_in_generate_vis_data_priority IDSM_proxy_client_alternate_proxy_host_for
IDEAS_import_from_tdm_default_gen_vis_ IDSM_proxy_server_type
data_priority preference . . . . . . . . . . . 5-34 preference . . . . . . . . . . . . . . . . . . . . 18-11
IDEAS_import_from_tdm_gen_vis_data_ IDSM_restricted_sites preference . . . . 18-11
display preference . . . . . . . . . . . . . . . 5-33 Image_DefaultChildProperties
IDEAS_import_from_tdm_gen_vis_data_input preference . . . . . . . . . . . . . . . . . . . . 10-84
preference . . . . . . . . . . . . . . . . . . . . . 5-34 IMAN_3D_snap_shot_relation_primary
IDEAS_import_from_tdm_options_default_ preference . . . . . . . . . . . . . . . . . . . . 10-25
gen_vis_data_priority preference . . . . 5-35 IMAN_capture_relation_primary
preference . . . . . . . . . . . . . . . . . . . . . 5-36

Index
IMAN_customization_libraries ACAD_COMPONENT_ONLY_
preference . . . . . . . . . . . . . . . . . . . . 10-26 MODE . . . . . . . . . . . . . . . . . . . 23-32
IMAN_Drawing_relation_primary AIE_no_BVR_edit . . . . . . . . . . . . . . 23-2
preference . . . . . . . . . . . . . . . . . . . . . 5-48 AIE_overwrite_default_import_item_
IMAN_external_appl_reg_url type . . . . . . . . . . . . . . . . . . . . . . 23-1
preference . . . . . . . . . . . . . . . . . . . . . 5-94 AIE_POST_EXPORT_SCRIPT . . . . . 23-2
IMAN_FLASH_FILE preference . . . . . 10-26 AIE_PRE_IMPORT_SCRIPT . . . . . . 23-3
IMAN_MEWorkInstruction_relation_primary ARM_acquire_license . . . . . . . . . . . 23-17
preference . . . . . . . . . . . . . . . . . . . . 20-53 ARM_archive_operation . . . . . . . . . 23-11
IMAN_MGC_Component_relation_primary ARM_bom_compare . . . . . . . . . . . . 23-27
preference . . . . . . . . . . . . . . . . . . . . 23-48 ARM_checkin_objects . . . . . . . . . . . 23-23
IMAN_MGC_Design_relation_primary ARM_checkout_objects . . . . . . . . . . 23-22
preference . . . . . . . . . . . . . . . . . . . . 23-48 ARM_copy_objects . . . . . . . . . . . . . 23-21
IMAN_MGC_Viewpoint_relation_primary ARM_create_changeitem . . . . . . . . 23-30
preference . . . . . . . . . . . . . . . . . . . . 23-48 ARM_create_dataset . . . . . . . . . . . 23-14
IMAN_PortfolioConfiguredPage_relation_ ARM_create_item . . . . . . . . . . . . . 23-13
primary preference . . . . . . . . . . . . . 20-52 ARM_create_itemrev . . . . . . . . . . . 23-14
IMAN_PortfolioPage_relation_primary ARM_create_supersedure . . . . . . . . 23-31
preference . . . . . . . . . . . . . . . . . . . . 20-52 ARM_cut_objects . . . . . . . . . . . . . . 23-21
IMAN_PublishingPageAssetContext_relation_ ARM_delete_objects . . . . . . . . . . . . 23-23
primary preference . . . . . . . . . . . . . 20-48 ARM_display_changeitem . . . . . . . . 23-30
IMAN_SAP_sideinfo_file preference . . 23-51 ARM_display_form . . . . . . . . . . . . . 23-20
IMAN_SDL_MAGIC variable . . . . . . . . . 3-3 ARM_display_genealogy . . . . . . . . . 23-31
IMAN_SYS_UID_DIR variable . . . . . . . . 3-3 ARM_display_prop . . . . . . . . . . . . . 23-19
IMAN_SYS2_UID_DIR variable . . . . . . . 3-3 ARM_expand_bomview . . . . . . . . . . 23-25
IMAN_TCPublishedPortfolio_relation_ ARM_expand_object . . . . . . . . . . . . 23-13
primary preference . . . . . . . . . . . . . 20-48 ARM_expandbelow_bomview . . . . . 23-26
IMANFILE_object_columns_hidden ARM_export_dataset . . . . . . . . . . . 23-15
preference . . . . . . . . . . . . . . . . . . . . 10-26 ARM_idsm_import . . . . . . . . . . . . . . 23-8
IMANFILE_object_columns_shown ARM_idsm_version_check . . . . . . . . 23-10
preference . . . . . . . . . . . . . . . . . . . . 10-27 ARM_import_dataset . . . . . . . . . . . 23-15
IMANFILE_object_widths_hidden ARM_initiate_process . . . . . . . . . . . 23-29
preference . . . . . . . . . . . . . . . . . . . . 10-27 ARM_launch_mynavigator . . . . . . . 23-25
IMANFILE_object_widths_shown ARM_load_lov . . . . . . . . . . . . . . . . 23-24
preference . . . . . . . . . . . . . . . . . . . . 10-28 ARM_ods_publish . . . . . . . . . . . . . . 23-7
IMANTYPE_object_columns_shown ARM_ods_remote_find . . . . . . . . . . . 23-6
preference . . . . . . . . . . . . . . . . . . . . 10-28 ARM_ods_unpublish . . . . . . . . . . . . 23-8
IMANTYPE_object_widths_shown ARM_open_dataset . . . . . . . . . . . . 23-18
preference . . . . . . . . . . . . . . . . . . . . 10-29 ARM_open_inbox . . . . . . . . . . . . . . 23-27
IMANVOLUME_object_columns_hidden ARM_open_task2perform . . . . . . . . 23-28
preference . . . . . . . . . . . . . . . . . . . . 10-29 ARM_open_task2track . . . . . . . . . . 23-28
IMANVOLUME_object_columns_shown ARM_paste_objects . . . . . . . . . . . . 23-22
preference . . . . . . . . . . . . . . . . . . . . 10-30 ARM_perform_signoff . . . . . . . . . . . 23-29
IMANVOLUME_object_widths_hidden ARM_print_file . . . . . . . . . . . . . . . 23-24
preference . . . . . . . . . . . . . . . . . . . . 10-30 ARM_restore_operation . . . . . . . . . 23-11
IMANVOLUME_object_widths_shown ARM_save_bomview . . . . . . . . . . . . 23-26
preference . . . . . . . . . . . . . . . . . . . . 10-31 ARM_saveas_item . . . . . . . . . . . . . 23-18
Implemented_ByRules preference . . . . 22-23 ARM_search_object . . . . . . . . . . . . 23-17
INBOX_hide_suspended_tasks ARM_session_login . . . . . . . . . . . . 23-12
preference . . . . . . . . . . . . . . . . . . . . 11-11 ARM_session_logout . . . . . . . . . . . 23-12
Incremental_Change_Management ARM_tcfs_export_file . . . . . . . . . . . . 23-6
preference . . . . . . . . . . . . . . . . . . . . 19-65 ARM_tcfs_import_file . . . . . . . . . . . . 23-6
Integration preferences . . . . . . . . . . . . 23-1 ARM_tcfs_open_close . . . . . . . . . . . . 23-5
ARM_tcsync_object_file_transfer . . . 23-10

Index
ARM_tcsync_update . . . . . . . . . . . . . 23-9 STEP_material_specification_

ARM_update_form . . . . . . . . . . . . . 23-20 pref . . . . . . . . . . . . . . . . . . . . . 18-82
ARM_update_prop . . . . . . . . . . . . . 23-19 STEP_not_yet_approved_status . . . 18-83
ARM_where_referenced . . . . . . . . . 23-16 STEP_part_items . . . . . . . . . . . . . . 18-83
ARM_where_used . . . . . . . . . . . . . 23-16 STEP_process_specification_pref . . . 18-83
CAE_batch_meshing_root_dir . . . . . 23-36 STEP_surface_finish_specification_
CAE_batch_meshing_tools . . . . . . . 23-35 pref . . . . . . . . . . . . . . . . . . . . . 18-84
CAE_default_batch_meshing_tool . . 23-36 TC_ERP_current_schema_name . . . 23-49
CAEAnalysisRevision Master_ TC_ERP_dataset_types_to_
viewerprops . . . . . . . . . . . . . . . 23-34 transfer . . . . . . . . . . . . . . . . . . 23-52
CAEBCItemRevision Master_ TC_ERP_mapping_files . . . . . . . . . 23-49
viewerprops . . . . . . . . . . . . . . . 23-33 TC_ERP_rellog_file_path . . . . . . . . 23-50
CAEConnItemRevision Master_ TC_ERP_uom_mapping_file . . . . . . 23-50
viewerprops . . . . . . . . . . . . . . . 23-34 TC_ODBC_release_status . . . . . . . . 23-52
CAELoadItemRevision Master_ TC_organization_id . . . . . . . . . . . . 18-84
viewerprops . . . . . . . . . . . . . . . 23-33 TC_SAP_alt_bomview_file . . . . . . . 23-50
IDEAS_manager_library . . . . . . . . 23-46 TC_SAP_cad_tables_path . . . . . . . . 23-51
IMAN_MGC_Component_relation_ TC_SAP_sapcad_dir . . . . . . . . . . . . 23-51
primary . . . . . . . . . . . . . . . . . . 23-48 TC_SHOW_OPEN_IN_IDEAS_
IMAN_MGC_Design_relation_ BUTTON . . . . . . . . . . . . . . . . . 23-46
primary . . . . . . . . . . . . . . . . . . 23-48 Interface preferences
IMAN_MGC_Viewpoint_relation_ PLMXML_put_pie_log_in_syslog . . . 18-73
primary . . . . . . . . . . . . . . . . . . 23-48 PLMXML_sdk_threshold . . . . . . . . 18-73
IMAN_SAP_sideinfo_file . . . . . . . . . 23-51 INTEROP_ExtraPLMXMLInstanceAttributes
MGCItemRevision_relations_as_ preference . . . . . . . . . . . . . . . . . . . . . 21-2
folders . . . . . . . . . . . . . . . . . . . 23-47 Interop_Vis_Attributes preference . . . . 21-3
MGCItemRevision_shown_ Interop_Vis_Attributes_Admin_Filter
relations . . . . . . . . . . . . . . . . . . 23-47 preference . . . . . . . . . . . . . . . . . . . . . 21-4
SCM_CheckIn_Identical_Version . . . 23-54 Investment_Cost_Form_Elements
SCM_ClearCase_Server . . . . . . . . . 23-53 preference . . . . . . . . . . . . . . . . . . . . 22-21
SCM_ClearCase_UNCO_Keep_ IP_level_list_ordering preference . . . . . 5-20
Version . . . . . . . . . . . . . . . . . . . 23-54 IPADefaultEmailMessage preference . . 20-8
STEP_<relation_type> . . . . . . . . . . 18-75 IPVBOM_build_intent_status
STEP_approved_status . . . . . . . . . . 18-75 preference . . . . . . . . . . . . . . . . . . . . 22-13
STEP_cad_filename_pref . . . . . . . . 18-77 IPVBOM_compare_mode_var_level_
STEP_default_BOMView_type . . . . 18-76 Occurrence_Notes preference . . . . . . 22-17
STEP_default_datasettype . . . . . . . 18-76 IPVBOM_compare_mode_var_
STEP_default_item_type . . . . . . . . 18-76 level_RevisionCompare_ItemTypes
STEP_design_specification_pref . . . 18-77 preference . . . . . . . . . . . . . . . . . . . . 22-16
STEP_DMI_markup . . . . . . . . . . . . 18-79 IPVBOM_UPCFNA_OccNoteName
STEP_drawing_pref . . . . . . . . . . . . 18-77 preference . . . . . . . . . . . . . . . . . . . . 22-18
STEP_export_data_format . . . . . . . 18-78 ISS_Cost_Form_Elements
STEP_export_directory . . . . . . . . . . 18-78 preference . . . . . . . . . . . . . . . . . . . . 22-20
STEP_FILETYPE_2_DATATYPE . . 18-78 Issue Manager preferences . . . . . . . . . 14-20
STEP_IMAN_manifestation . . . . . . 18-80 ISSUE_issuelist_page_size . . . . . . . . 14-1
STEP_IMAN_master_data . . . . . . . 18-79 ISSUE_preview_image_name_
STEP_IMAN_reference . . . . . . . . . 18-80 separator . . . . . . . . . . . . . . . . . . 14-1
STEP_IMAN_requirement . . . . . . . 18-80 ISSUE_preview_image_size . . . . . . . 14-2
STEP_IMAN_specification . . . . . . . 18-79 ISSUE_preview_tooltip_properties_after_
STEP_IMAN_UG_altrep . . . . . . . . . 18-81 fix . . . . . . . . . . . . . . . . . . . . . . . 14-2
STEP_IMAN_UG_scenario . . . . . . . 18-81 ISSUE_preview_tooltip_properties_before_
STEP_import_directory . . . . . . . . . 18-81 fix . . . . . . . . . . . . . . . . . . . . . . . 14-2
STEP_informative_doc_role . . . . . . 18-82 ISSUE_review_issue_menu_items_at_
STEP_make_or_buy_attr . . . . . . . . 18-82 workflow_task . . . . . . . . . . . . . . . 14-3

Index
ISSUE_issuelist_page_size Item.SUMMARYRENDERING2007
ISSUE_preview_image_name_separator ItemMaster_DefaultChildProperties
ISSUE_preview_image_size itemrev1_itemrev2_default_relation
ISSUE_preview_tooltip_properties_after_fix ItemRevision_CharacteristicDefinition_
preference . . . . . . . . . . . . . . . . . . . . . 14-2 default_relation preference . . . . . . . . 22-68
ISSUE_preview_tooltip_properties_before_fix ItemRevision_default_relation
ISSUE_review_issue_menu_items_at_ ItemRevision_DefaultChildProperties
workflow_task preference . . . . . . . . . . 14-3 preference . . . . . . . . . . . . . . . . . . . . 10-83
ITAR_level_list_ordering preference . . . 5-21 ItemRevision_DirectModel3DMarkup_
<Item <Item type>_rev_display_all default_relation preference . . . . . . . . . 21-4
preference . . . . . . . . . . . . . . . . . . . . 10-42 ITEMREVISION_object_columns_hidden
<Item type>_rev_display_order preference . . . . . . . . . . . . . . . . . . . . 10-37
preference . . . . . . . . . . . . . . . . . . . . 10-42 ITEMREVISION_object_columns_shown
<Item type>_rev_display_rule preference . . . . . . . . . . . . . . . . . . . . 10-38
preference . . . . . . . . . . . . . . . . . . . . 10-43 ITEMREVISION_object_widths_hidden
ITEM_autogenerate_id preference . . . . . 5-4 preference . . . . . . . . . . . . . . . . . . . . 10-38
ITEM_autopublish preference . . . . . . 18-11 ITEMREVISION_object_widths_shown
ITEM_autopublish_ignore_errors preference . . . . . . . . . . . . . . . . . . . . 10-39
preference . . . . . . . . . . . . . . . . . . . . 18-12 ItemRevision_shown_relations
ITEM_autopublish_sites preference . . 18-13 preference . . . . . . . . . . . . . . . . . . . . 10-39
ITEM_baseline_rev_msg preference . . . 5-21 ItemRevision_TCPublishingPage_default_
Item_CharacteristicDefinition_default_ relation preference . . . . . . . . . . . . . . 20-49
relation preference . . . . . . . . . . . . . . 22-68 ItemRevision_thumbnail_references
Item_DefaultChildProperties preference . . . . . . . . . . . . . . . . . . . . 10-41
preference . . . . . . . . . . . . . . . . . . . . 10-82 ItemRevision_thumbnail_relations
ITEM_first_rev_id preference . . . . . . . 10-31 preference . . . . . . . . . . . . . . . . . . . . 10-40
ITEM_id_allow_if_registry_down ItemRevision_Vis_Session_default_relation
ITEM_id_always_register_on_creation ItemRevision.RENDERING
ITEM_id_postfix preference . . . . . . . . 10-32 ItemRevision.SUMMARYRENDERING
ITEM_id_prefix preference . . . . . . . . . 10-32 preference . . . . . . . . . . . . . . . . . . . . 10-36
ITEM_id_registry preference . . . . . . . 18-14
ITEM_id_registry_site preference . . . . 18-14 J
ITEM_id_unregister_on_delete
preference . . . . . . . . . . . . . . . . . . . . 18-14 JRE_HOME variable . . . . . . . . . . . . . . . 3-3
ITEM_object_columns_hidden JT_File_Excluded_Refsets
ITEM_object_columns_shown JT_File_OverrideChildren_Refsets
ITEM_object_widths_hidden JT_File_Priority_Refsets preference . . 19-94
preference . . . . . . . . . . . . . . . . . . . . 10-34 JT_WEB_UI_PREF preference . . . . . 10-100
ITEM_object_widths_shown JTContentBomLineProperties
ITEM_relation_types_update_lmd JTContentHintPropertyPolicy
Item_shown_relations preference . . . . 10-41 JTTreeTableColumnsShownPref
ITEM_smart_baseline preference . . . . 10-42 preference . . . . . . . . . . . . . . . . . . . . 10-44
Item.FilterCriteria preference . . . . . . 10-31 JTTreeTableShownColumnWidthsPref
preference . . . . . . . . . . . . . . . . . . . . 10-44

Index
K TC_language_localized_property_value_
entry . . . . . . . . . . . . . . . . . . . . . 5-63
KNOWLEDGEBASE_EVALUATE LocationInCompany_relation_primary
variable . . . . . . . . . . . . . . . . . . . . . . . 3-3 preference . . . . . . . . . . . . . . . . . . . . 22-55
Log file preferences . . . . . . . . . . . . . . . 9-37
L RECOVER_TO_UNRELEASED_
STATUS . . . . . . . . . . . . . . . . . . . 9-40
LANG variable . . . . . . . . . . . . . . . . . . . 3-4 RECOVER_TO_VOLUME . . . . . . . . 9-40
LC_ALL variable . . . . . . . . . . . . . . . . . 3-4 TC_Administration_Logging . . . . . . . 9-37
LD_LIBRARY_PATH variable . . . . . . . . 3-4 TC_allow_inherited_group_volume_
LDAP connection preferences . . . . . . . . 5-96 access . . . . . . . . . . . . . . . . . . . . . 9-38
LDAP_admin_dn preference . . . . . . . . . 5-97 TC_Application_Logging . . . . . . . . . . 9-38
LDAP_admin_pw preference . . . . . . . . 5-98 TC_Installation_Logging . . . . . . . . . 9-38
LDAP_attribute_mapping TC_Journal_Modules . . . . . . . . . . . . 9-39
preference . . . . . . . . . . . . . . . . . . . . 5-105 TC_Journalling . . . . . . . . . . . . . . . . 9-39
LDAP_base_dn preference . . . . . . . . . 5-106 TC_KEEP_SYSTEM_LOG . . . . . . . . 9-39
LDAP_cert_db_path preference . . . . . . 5-97 TC_Security_Logging . . . . . . . . . . . . 9-37
LDAP_group_attr_mapping TC_sfr_process_life_time . . . . . . . . . 9-41
preference . . . . . . . . . . . . . . . . . . . . 5-103 TC_sfr_recovery_interval . . . . . . . . . 9-41
LDAP_group_base_dn preference . . . . 5-102 TC_TMP_DIR . . . . . . . . . . . . . . . . . 9-40
LDAP_group_object_class LOG_VOLUME_DIR variable . . . . . . . . 3-5
preference . . . . . . . . . . . . . . . . . . . . 5-103 LOG_VOLUME_NAME variable . . . . . . 3-5
LDAP_group_query_filter LogBook_PhysicalPart_default_relation
LDAP_ignore_users preference . . . . . . 5-107 LogBook_WorkspaceObject_default_relation
LDAP_member_list_attr preference . . 5-101 preference . . . . . . . . . . . . . . . . . . . . 22-69
LDAP_member_type_attr Logging environment variables
preference . . . . . . . . . . . . . . . . . . . . 5-101 API_JOURNAL . . . . . . . . . . . . . . . . . 2-2
LDAP_object_type_attr preference . . . 5-101 TC_JOURNAL . . . . . . . . . . . . . . . . . . 2-2
LDAP_person_attr_mapping TC_KEEP_SYSTEM_LOG . . . . . . . . . 2-3
preference . . . . . . . . . . . . . . . . . . . . 5-108 TC_POM_JOURNALLING . . . . . . . . . 2-2
LDAP_port_number preference . . . . . . 5-96 TC_SLOW_SQL . . . . . . . . . . . . . . . . . 2-3
LDAP_role_attr_mapping TC_SQL_DEBUG . . . . . . . . . . . . . . . 2-2
preference . . . . . . . . . . . . . . . . . . . . 5-105 TC_TRACEBACK . . . . . . . . . . . . . . . 2-3
LDAP_role_object_class preference . . . 5-104 Logging files environment variables . . . . 2-1
LDAP_role_query_filter preference . . . 5-104 Lot_DefaultChildProperties
LDAP_service_hosts preference . . . . . . 5-96 preference . . . . . . . . . . . . . . . . . . . . 22-70
LDAP_sync_group_flags preference . . . 5-99 Lot.SUMMARYRENDERING
LDAP_sync_member_flags preference . . . . . . . . . . . . . . . . . . . . 22-69
preference . . . . . . . . . . . . . . . . . . . . . 5-99 LOU_display_name_properties
LDAP_sync_role_flags preference . . . . 5-100 preference . . . . . . . . . . . . . . . . . . . 19-114
LDAP_sync_user_flags preference . . . . 5-98 LOV_hide_desc preference . . . . . . . . . 10-45
LDAP_use_ssl preference . . . . . . . . . . . 5-96
LDAP_user_object_class preference . . 5-107 M
LDAP_user_query_filter preference . . 5-107
LDR_CNTRL variable . . . . . . . . . . . . . . 3-4 Mail Folder_DefaultChildProperties
LIBRARY_PATH variable . . . . . . . . . . . 3-5 preference . . . . . . . . . . . . . . . . . . . . 10-83
license_warning_level . . . . . . . . . . . . . 5-22 Mail gateway preferences . . . . . . . . . . . 5-65
Localization preferences Folder_mail_properties . . . . . . . . . . . 5-65
TC_language_data_entry . . . . . . . . . 5-59 Mail_OSMail_activated . . . . . . . . . . 5-67
TC_language_default . . . . . . . . . . . . 5-61 Mail_server_charset . . . . . . . . . . . . . 5-66
TC_language_localization_display . . . 5-62 Mail_server_name . . . . . . . . . . . . . . 5-66
TC_language_localized_property_value_ Mail_server_port . . . . . . . . . . . . . . . 5-66
display . . . . . . . . . . . . . . . . . . . . 5-62 TC_mail_interval . . . . . . . . . . . . . . . 5-67

Index
TC_use_tc_alias_in_pa8 . . . . . . . . . . 5-67 TC_Cache_Dir . . . . . . . . . . . . . . . . . 9-24

Mail_OSMail_activated preference . . . . 5-67 TC_Cache_Mode . . . . . . . . . . . . . . . 9-25
Mail_server_charset preference . . . . . . 5-66 TC_Cache_Protection . . . . . . . . . . . . 9-26
Mail_server_name preference . . . . . . . . 5-66 TC_Cache_Size . . . . . . . . . . . . . . . . 9-24
Mail_server_port preference . . . . . . . . . 5-66 TC_enable_backup_modes . . . . . . . . . 9-7
Mail_subscription_notify_sub_groups_too TC_Installation_Logging . . . . . . . . . 9-38
preference . . . . . . . . . . . . . . . . . . . . . 9-18 TC_Journal_Modules . . . . . . . . . . . . 9-39
Maintenance preferences . . . . . . . . . . . . 9-1 TC_Journalling . . . . . . . . . . . . . . . . 9-39
blobbyVolume_NT . . . . . . . . . . . . . . 9-28 TC_KEEP_SYSTEM_LOG . . . . . . . . 9-39
blobbyVolume_UNX . . . . . . . . . . . . . 9-28 TC_notification_msg_ext . . . . . . . . . . 9-13
Centera_Cluster_IPAddresses . . . . . . . 9-6 TC_refresh_notify . . . . . . . . . . . . . . 9-14
Default_Transient_Server . . . . . . . . . 9-32 TC_refresh_notify_list_maximum . . . 9-17
Default_Transient_Volume_Id . . . . . . 9-32 TC_refresh_notify_pull_time_
Fms_BootStrap_Urls . . . . . . . . . . . . 9-32 interval . . . . . . . . . . . . . . . . . . . 9-16
FSC_HOME . . . . . . . . . . . . . . . . . . 9-33 TC_refresh_notify_scope . . . . . . . . . . 9-14
HSM_integration_enabled . . . . . . . . . 9-4 TC_refresh_notify_subscribe_to_
HSM_primary_tier_hosts . . . . . . . . . . 9-5 types . . . . . . . . . . . . . . . . . . . . . 9-15
HSM_read_thru_supported . . . . . . . . . 9-4 TC_refresh_notify_timed_out . . . . . . 9-18
HSM_secondary_tier_capacity . . . . . . . 9-5 TC_Security_Logging . . . . . . . . . . . . 9-37
Mail_subscription_notify_sub_groups_ TC_sfr_process_life_time . . . . . . . . . 9-41
too . . . . . . . . . . . . . . . . . . . . . . . 9-18 TC_sfr_recovery_interval . . . . . . . . . 9-41
Multisite_Ticket_Expiration_ TC_STAGING_AREA . . . . . . . . . . . . 9-26
Interval . . . . . . . . . . . . . . . . . . . 9-27 TC_Store_and_Forward . . . . . . . . . . . 9-6
RECOVER_TO_UNRELEASED_ TC_Store_and_Forward_Transfer_
STATUS . . . . . . . . . . . . . . . . . . . 9-40 Delay . . . . . . . . . . . . . . . . . . . . . . 9-7
RECOVER_TO_VOLUME . . . . . . . . 9-40 TC_subscription . . . . . . . . . . . . . . . . 9-13
SCM_notification_history . . . . . . . . . 9-22 TC_subscription_log_event_and_action_
SCM_notification_WorkspaceObject_ status . . . . . . . . . . . . . . . . . . . . . 9-19
props . . . . . . . . . . . . . . . . . . . . . 9-22 TC_subscriptionmgrd_cloning_
TC_<file type>_Cache_Mode . . . . . . . 9-25 interval . . . . . . . . . . . . . . . . . . . 9-12
TC_actionmgrd_cloning_interval . . . . 9-10 TC_subscriptionmgrd_max_subscriptions_
TC_actionmgrd_general_processing_ to_dispatch . . . . . . . . . . . . . . . . . 9-12
hours . . . . . . . . . . . . . . . . . . . . . . 9-9 TC_subscriptionmgrd_processing_
TC_actionmgrd_max_actions_to_ hours . . . . . . . . . . . . . . . . . . . . . 9-11
dispatch . . . . . . . . . . . . . . . . . . . 9-10 TC_subscriptionmgrd_sleep_
TC_actionmgrd_max_subprocess_to_ minutes . . . . . . . . . . . . . . . . . . . 9-11
start . . . . . . . . . . . . . . . . . . . . . . 9-10 TC_System_Logging . . . . . . . . . . . . . 9-27
TC_actionmgrd_sleep_minutes . . . . . . 9-8 TC_TMP_DIR . . . . . . . . . . . . . . . . . 9-40
TC_Administration_Logging . . . . . . . 9-37 TC_Volume_Failover_Trigger . . . . . . 9-29
TC_allow_inherited_group_volume_ TC_Volume_Failover_Volume_
access . . . . . . . . . . . . . . . . . . . . . 9-38 Name . . . . . . . . . . . . . . . . . . . . . 9-29
TC_Application_Logging . . . . . . . . . . 9-38 TC_VOLUME_MONITOR_CRITICAL_
TC_audit_buffer_size . . . . . . . . . . . . . 9-2 LEVEL . . . . . . . . . . . . . . . . . . . . 9-30
TC_audit_delimiter . . . . . . . . . . . . . . 9-3 TC_VOLUME_MONITOR_WARNING_
TC_audit_file_format . . . . . . . . . . . . . 9-3 LEVEL . . . . . . . . . . . . . . . . . . . . 9-30
TC_audit_log_dir . . . . . . . . . . . . . . . . 9-2 TC_Volume_Status_Resync_
TC_audit_manager . . . . . . . . . . . . . . 9-1 Interval . . . . . . . . . . . . . . . . . . . 9-28
TC_automatic_refresh_list_ TcActionColumnPreferences . . . . . . . 9-21
maximum . . . . . . . . . . . . . . . . . . 9-18 TcActionColumnWidthPreferences . . 9-21
TC_automatic_refresh_time_ TcEventColumnPreferences . . . . . . . 9-20
interval . . . . . . . . . . . . . . . . . . . 9-17 TcEventColumnWidthPreferences . . . 9-20
TC_automatic_refresh_waiting_ TcSubscription
time . . . . . . . . . . . . . . . . . . . . . . 9-17 ColumnWidthPreferences . . . . . . 9-19
TC_Cache_Allowed . . . . . . . . . . . . . 9-24 TcSubscriptionColumnPreferences . . 9-19

Index
Ticket_Expiration_Interval . . . . . . . . 9-27 MEAccountabilityCheckSourceStructure

Transient_Volume_Installation_ ExpansionFilterRules preference . . . 20-35
Location . . . . . . . . . . . . . . . . . . . 9-31 MEAccountabilityCheckTargetStructure
Transient_Volume_RootDir . . . . . . . . 9-31 ExpansionFilterRules preference . . . 20-35
<TypeName>_subscribe_to_events . . 9-15 MEActivityTypeColors preference . . . . 20-40
UNLOAD_LOGGING_LEVEL . . . . . 9-36 MEAdvancedSearchResultsViewColumns
UNLOAD_MINIMUM_LIFE . . . . . . . 9-35 ShownPref preference . . . . . . . . . . . 20-60
UNLOAD_TRIGGER_CEILING . . . . 9-33 MEAdvancedSearchResultsViewColumns
UNLOAD_TRIGGER_FLOOR . . . . . . 9-34 ShownWidthPref preference . . . . . . . 20-60
ManufacturerPart Revision.RENDERING MEAlignedPropertiesList preference . . 20-2
preference . . . . . . . . . . . . . . . . . . . . 22-57 MEAlignedPropertiestoExclude
ManufacturerPart FromDetection preference . . . . . . . . . 20-3
Revision.SUMMARYRENDERING MEAlignedPropertiestoExclude
preference . . . . . . . . . . . . . . . . . . . . 22-57 FromInitialization preference . . . . . . . 20-3
ManufacturerPart_DefaultChildProperties MEAlignedPropertiestoExcludeFromSync
ManufacturerPart_DefaultPSEProperties MEAlignmentCheckReportStylesheet
ManufacturerPart_PseudoFolder MEAlignmentCheckReportDefinition
ManufacturerPart.REGISTEREDTO MEAlignmentCheckReportLocation
ManufacturerPart.RENDERING MEAllocatedTimeReportDefinitionID
ManufacturerPart.SUMMARYRENDERING MEAllocatedTimeReportStylesheet
ManufacturerPartRevision.REGISTEREDTO MEAPCSearchType preference . . . . . . 20-61
preference . . . . . . . . . . . . . . . . . . . . 22-56 MEAssignCustomizedOccurrenceType
ManufacturerPartRevSummary.SUMMARY_ preference . . . . . . . . . . . . . . . . . . . . . 20-6
REGISTEREDTO preference . . . . . . 22-57 MEAssignmentsViewColumnsShownPref
ManufacturerPartSummary.SUMMARY_ preference . . . . . . . . . . . . . . . . . . . . 20-65
REGISTEREDTO preference . . . . . . 22-59 MEAssignmentsViewColumns
Manufacturing features preferences . . 20-76 ShownWidthPref preference . . . . . . . 20-65
Manufacturing preferences . . . . . . . . . 20-1 MEAvailableTimeUnits preference . . . 20-38
Standard text preferences . . . . . . . . 20-81 MEBlankDisplayTypes preference . . . 20-19
Manufacturing search preferences . . . 20-58 MECollaborationContext_default_relation
ManufacturingIdCharsForPhysicalPartIdPref preference . . . . . . . . . . . . . . . . . . . . 10-45
preference . . . . . . . . . . . . . . . . . . . . 22-71 MEConsiderFlowsOnReSequence
MB_CHARS variable . . . . . . . . . . . . . . . 3-5 preference . . . . . . . . . . . . . . . . . . . . 20-23
ME_Cost_Form_Elements MECopyIdInContextLowerLevels
ME_Proximity_FilteredIPA_suffix MECopyIdInContextToAssignedLine
ME_Proximity_search_result_occ_group_type MECurrentTimeUnit preference . . . . . 20-39
preference . . . . . . . . . . . . . . . . . . . . 20-59 MEDataPanelPosition preference . . . . 20-18
ME_Proximity_search_result_occ_type MEDataSetsToBeCheckoutFor
preference . . . . . . . . . . . . . . . . . . . . 20-59 ProcessSimulate preference . . . . . . . 20-83
ME_Proximity_search_result_root_name MEDefaultActivityType preference . . . 20-41
preference . . . . . . . . . . . . . . . . . . . . 20-59 MEExpandFirstLevelOnLoad
MEAccountabilityCheckEnableFilteringRules preference . . . . . . . . . . . . . . . . . . . . 20-18
preference . . . . . . . . . . . . . . . . . . . . 20-36 MEExpandToSelection preference . . . 20-18
MEAccountabilityCheckEnableNetEffectivity MEFormsToBeCheckoutForProcessSimulate

Index
MEGANTTDefaultDisplayMode MEMFGView_AssignmentFilterDefaultValue
MEGANTTDefaultDurationTimeColor MEMFGViewColumnShownPref
MEGANTTDefaultDurationTimeMode MEMFGViewShownColumnWidthsPref
MEGANTTDefaultEditMode MEMFGViewSubPanelColumnShownPref
MEGANTTDefaultFlowColor MEMFGViewSubPanelShown
preference . . . . . . . . . . . . . . . . . . . . 20-74 ColumnWidthsPref preference . . . . . 20-80
MEGANTTDefaultMarkedColor MENEWMFG_DefaultJTDatasetName
MEGANTTElementHeight MENEWMFG_DeffaultJTFileName
MEGANTTElementRGBfillColor MENEWMFG_LastJTFilePathBrowsed
MEGANTTimplicitFlowColor Mentor Graphics Integration
preference . . . . . . . . . . . . . . . . . . . . 20-75 preferences . . . . . . . . . . . . . . . . . . . 23-47
MEGANTTMarkedFlowColor IMAN_MGC_Component_relation_
preference . . . . . . . . . . . . . . . . . . . . 20-75 primary . . . . . . . . . . . . . . . . . . 23-48
MEGANTTPropagateDurationUpToLevel IMAN_MGC_Design_relation_
MEGANTTPropagateDurationUpToLevelEnabled IMAN_MGC_Viewpoint_relation_
MEGenericBOP.MEGenericBOP. MGCItemRevision_relations_as_
PasteDuplicateTemplate folders . . . . . . . . . . . . . . . . . . . 23-47
preference . . . . . . . . . . . . . . . . . . . . 20-69 MGCItemRevision_shown_
MEGenericBOP.MEProductBOP. relations . . . . . . . . . . . . . . . . . . 23-47
PasteDuplicateTemplate MEOccTypeConsumed preference . . . . . 20-7
preference . . . . . . . . . . . . . . . . . . . . 20-69 MEOP_DefaultChildProperties
MEGenericBopContextColumnsShownPref preference . . . . . . . . . . . . . . . . . . . . 10-84
preference . . . . . . . . . . . . . . . . . . . . 20-62 MEOperationActivitiesFilteredComponents
MEGenericBopContextColumns preference . . . . . . . . . . . . . . . . . . . . 20-40
ShownWidthsPref preference . . . . . . 20-62 MEOPRevision_DefaultChildProperties
MEGenericBopContextPartition preference . . . . . . . . . . . . . . . . . . . . 10-85
ColumnsShownPref preference . . . . . 20-63 MEOPRevision_shown_relations
MEGenericBopContextPartition preference . . . . . . . . . . . . . . . . . . . . 10-46
ColumnsShownWidthsPref MEPADChildTypesPref preference . . . 20-58
preference . . . . . . . . . . . . . . . . . . . . 20-64 MEProcess_DefaultChildProperties
MEHideChangesIconsForAttributes preference . . . . . . . . . . . . . . . . . . . . 10-84
preference . . . . . . . . . . . . . . . . . . . . 20-20 MEProcessRevision_DefaultChildProperties
MEImportMFGsManufacturingFeatureId preference . . . . . . . . . . . . . . . . . . . . 10-85
AttributeName preference . . . . . . . . 20-77 MEProcessRevision_shown_relations
MEImportMFGsPartIdAttributeName preference . . . . . . . . . . . . . . . . . . . . 10-46
preference . . . . . . . . . . . . . . . . . . . . 20-77 MEProductBOP.MEGenericBOP.
MELineLinkedIconsProperty PasteDuplicateTemplate
MELogicalDesignatorDelimiter MEProductBOP.MEProductBOP.
preference . . . . . . . . . . . . . . . . . . . . 20-66 PasteDuplicateTemplate
MELogicalDesignatorFormNameSuffix preference . . . . . . . . . . . . . . . . . . . . 20-70
preference . . . . . . . . . . . . . . . . . . . . 20-66 MEProductBopContextColumnsShownPref
MEManufacturingDefaultBVR preference . . . . . . . . . . . . . . . . . . . . 20-62
preference . . . . . . . . . . . . . . . . . . . . . 20-5 MEProductBopContextColumns
MEMFGDisplayName preference . . . . 20-22 ShownWidthsPref preference . . . . . . 20-63

Index
MEProductBopContextPartition METimeDataCardConversionFactor
ColumnsShownPref preference . . . . . 20-64 preference . . . . . . . . . . . . . . . . . . . . 20-44
MEProductBopContextPartition METimeDataCardPath preference . . . 20-43
ColumnsShownWidthsPref METIMEPopulateAllocatedTimeUpToLevel
MEPSDTableColumnsShownPref METIMEPopulateAllocatedTimeUpToLevelEnabled
MEPSDTableColumnsShownPref.SORTING_ METIMEPopulateAllocatedTimeUsedSources
COLUMN preference . . . . . . . . . . . . 20-57 preference . . . . . . . . . . . . . . . . . . . . 20-45
MEPSDTableShownColumnWidthsPref METIMEPopulateAllocatedTimeZero
preference . . . . . . . . . . . . . . . . . . . . 20-57 ValuesEnabled preference . . . . . . . . 20-46
MERelationTypePartsDisassembled METimesActivityShownColumnWidths
MERelationTypePartsAssembled METimesActivityShownColumns
MERelationTypePartsAssigned METimeTabFilteredComponents
MERelationTypePartsConsumed MEWiDcdNotEditableProperties
MERelationTypePartsFeature MEWiPreviewFormat preference . . . . 20-82
preference . . . . . . . . . . . . . . . . . . . . 20-17 MEWiStandardTextTemplate
MERelationTypePartsHandled preference . . . . . . . . . . . . . . . . . . . . 20-81
preference . . . . . . . . . . . . . . . . . . . . 20-16 MEWiWorkInstructionTemplate
MERelationTypePartsOtherAssigned preference . . . . . . . . . . . . . . . . . . . . 20-81
preference . . . . . . . . . . . . . . . . . . . . 20-17 MGC_HOME variable . . . . . . . . . . . . . . 3-5
MERelationTypeUsedEquipment MGC_LOCATION_MAP variable . . . . . . 3-5
preference . . . . . . . . . . . . . . . . . . . . 20-15 MGC_TC_CONFIG_FILE variable . . . . . 3-6
MEReportColumnsForProcessSimulate MGCItemRevision_relations_as_folders
MEReportColumnWidthForProcessSimulate MGCItemRevision_shown_relations
MEResultViewSourceColumnsShownPref MGLS_LICENSE_FILE variable . . . . . . 3-6
preference . . . . . . . . . . . . . . . . . . . . 20-36 Migrate
MEResultViewSourceColumnsShownWidthPref Preferences . . . . . . . . . . . . . . . . . . . . 4-8
preference . . . . . . . . . . . . . . . . . . . . 20-37 MOVE_TRANSACTIONS_COUNT
MEResultViewTargetColumnsShownPref variable . . . . . . . . . . . . . . . . . . . . . . . 3-6
preference . . . . . . . . . . . . . . . . . . . . 20-37 MoveICCreationToMenu preference . . 19-66
MEResultViewTargetColumnsShownWidthPref MOZ_PLUGIN_PATH variable . . . . . . . . 3-6
preference . . . . . . . . . . . . . . . . . . . . 20-38 MPP_BrokenLinkSearchCriteriaList
MESecondStructurePosition preference . . . . . . . . . . . . . . . . . . . . . 20-9
preference . . . . . . . . . . . . . . . . . . . . 20-17 MPP_DefaultCandidateSearchCriteria
MEShowWeldPointsConnectedTo preference . . . . . . . . . . . . . . . . . . . . . 20-8
ConfiguredOutParts preference . . . . . 20-79 MRMClassifyResource preference . . . . . 17-2
MetaDataStamp_template MRMItemTypes preference . . . . . . . . 20-22
preference . . . . . . . . . . . . . . . . . . . . . 21-5 MRMPropagationRevisionRule
METHOD_CM_execute_before_custom preference . . . . . . . . . . . . . . . . . . . . . 20-7
preference . . . . . . . . . . . . . . . . . . . . . . 5-5 MRO preferences . . . . . . . . . . . . . . . 22-68
METIMEAllocatedTimePopulationMode As-Built preferences
preference . . . . . . . . . . . . . . . . . . . . 20-44 AdditionalAsBuiltAccCheck
METimeAnalysisReportDefinitionID Properties . . . . . . . . . . . . . 22-81
preference . . . . . . . . . . . . . . . . . . . . 20-42 AdditionalAsBuiltCompare
METimeAnalysisReportStylesheet Properties . . . . . . . . . . . . . 22-80
preference . . . . . . . . . . . . . . . . . . . . 20-43 AsBuiltManagerColumns
ShownPref . . . . . . . . . . . . . 22-79

Index
AsBuiltManagerShownColumn PartNumberCharsFor
WidthsPref . . . . . . . . . . . . . 22-79 PhysicalPartIdPref . . . . . . . . . . 22-74
DefaultAsBuiltAccCheck PhysicalContext_relation_
Properties . . . . . . . . . . . . . 22-81 primary . . . . . . . . . . . . . . . . . . 22-74
DefaultAsBuiltCompare PhysicalElement_Company_default_
Properties . . . . . . . . . . . . . 22-80 relation . . . . . . . . . . . . . . . . . . 22-74
As-Maintained preferences PhysicalLocation_CompanyLocation_
AdditionalAsMaintainedAccCheck default_relation . . . . . . . . . . . . 22-84
Properties . . . . . . . . . . . . . 22-82 PhysicalPart_Company_default_
AdditionalAsMaintainedCompare relation . . . . . . . . . . . . . . . . . . 22-75
Properties . . . . . . . . . . . . . 22-82 PhysicalPart_
DefaultAsMaintainedAccCheck DefaultChildProperties . . . . . . . 22-75
Properties . . . . . . . . . . . . . 22-82 PhysicalPart.SUMMARY
DefaultAsMaintainedCompare RENDERING . . . . . . . . . . . . . . 22-76
Properties . . . . . . . . . . . . . 22-83 PhysicalPartRelationsToExport . . . . 22-76
PhysicalLocationContainsColumns PhysicalPartRevision_
ShownPref . . . . . . . . . . . . . 22-84 DefaultChildProperties . . . . . . . 22-76
ServiceManagerAssetGroup PhysicalPartRevision.SUMMARY
ColumnsShownPref . . . . . . . 22-85 RENDERING . . . . . . . . . . . . . . 22-77
ServiceManagerAssetGroup PhysicalRealization_relation_
ColumnWidthsPref . . . . . . . 22-85 primary . . . . . . . . . . . . . . . . . . 22-77
ServiceManagerColumns SerialNumberCharsFor
ShownPref . . . . . . . . . . . . . 22-86 PhysicalPartIdPref . . . . . . . . . . 22-77
ServiceManagerPhysicalLocation SerialNumberGenerator_
ColumnsShownPref . . . . . . . 22-87 DefaultChildProperties . . . . . . . 22-78
ServiceManagerPhysicalLocation SerialNumberGenerator.SUMMARY
ColumnsWidthsPref . . . . . . 22-87 RENDERING . . . . . . . . . . . . . . 22-78
ServiceManagerShownColumn Service Request Manager preferences
WidthsPref . . . . . . . . . . . . . 22-86 ActivityCost.MROCREATE
HierarchicalWSO_HierarchicalWSO_ RENDERING . . . . . . . . . . 22-100
default_relation . . . . . . . . . . . . 22-68 ActivityCost_
Item_CharacteristicDefinition_default_ SRP0RqstActivityRevision.
relation . . . . . . . . . . . . . . . . . . 22-68 MROCREATERENDERING . . 22-100
ItemRevision_CharacteristicDefinition_ ActivityCost_SRP0ServiceOffering.
default_relation . . . . . . . . . . . . 22-68 MROCREATE
LogBook_PhysicalPart_default_ RENDERING . . . . . . . . . . 22-101
relation . . . . . . . . . . . . . . . . . . 22-69 ActivityCost_SRP0ServiceRequest.
LogBook_WorkspaceObject_default_ MROCREATE
relation . . . . . . . . . . . . . . . . . . 22-69 RENDERING . . . . . . . . . . 22-101
Lot_DefaultChildProperties . . . . . . 22-70 CM_SRP0DgSrvRequestRevision_
Lot.SUMMARYRENDERING . . . . . 22-69 displayed_pseudofolders . . 22-101
ManufacturingIdCharsFor CM_SRP0PrSrvRequestRevision_
PhysicalPartIdPref . . . . . . . . . . 22-71 displayed_pseudofolders . . 22-102
MROAlternateColorPref . . . . . . . . . 22-71 CM_SRP0RqstActivityRevision_
MRODeviatedColorPref . . . . . . . . . 22-72 displayed_pseudofolders . . 22-102
MROExtraToDesignColorPref . . . . . 22-72 CompanyContact.MROCREATE
MROMissingColorPref . . . . . . . . . . 22-73 RENDERING . . . . . . . . . . 22-103
MRONeutralColumnsShownPref . . . 22-70 CompanyLocation.MROCREATE
MRONeutralShownColumn RENDERING . . . . . . . . . . 22-103
WidthsPref . . . . . . . . . . . . . . . . 22-70 SR_CHANGE_HOME_SITE_
MROSubstituteColorPref . . . . . . . . 22-73 PREFERENCE . . . . . . . . . 22-103
PartLogisticsForm. SRP0DgSrvRequest.
SUMMARYRENDERING . . . . . 22-73 SUMMARYRENDERING . . 22-104

Index
SRP0DgSrvRequestRevision_ SRP0ServiceOffering_
DefaultChildProperties . . . 22-105 DefaultChildProperties . . . 22-113
SRP0DgSrvRequestRevision. SRP0ServiceOffering_
MROCREATERENDERING . . 22-104 HWSOStructure_default_
SRP0DgSrvRequestRevision. relation . . . . . . . . . . . . . . 22-113
RENDERING . . . . . . . . . . 22-104 SRP0ServiceOffering.
SRP0DgSrvRequestRevision. MROCREATERENDERING . . 22-112
SUMMARYRENDERING . . 22-105 SRP0ServiceOffering.
SRP0PrSrvRequest. RENDERING . . . . . . . . . . 22-112
SUMMARYRENDERING . . 22-105 SRP0ServiceOffering_
SRP0PrSrvRequestRevision_ SRP0ServiceCatalog_default_
DefaultChildProperties . . . 22-106 relation . . . . . . . . . . . . . . 22-113
SRP0PrSrvRequestRevision. SRP0ServiceOffering.
MROCREATERENDERING . . 22-106 SUMMARYRENDERING . . 22-112
SRP0PrSrvRequestRevision. SRP0ServiceOfferingTable_
RENDERING . . . . . . . . . . 22-106 ColumnPreferences . . . . . . 22-114
SRP0PrSrvRequestRevision. SRP0StatusViewColumns
SUMMARYRENDERING . . 22-106 ShownPref . . . . . . . . . . . . 22-114
SRP0RequalifyRqstActivityRevision. UtilizationViewColumnsShownPref . . 22-78
MROCREATERENDERING . . 22-107 MROAlternateColorPref preference . . 22-71
SRP0RqstActivity. MroConfigRuleName preference . . . . . 22-83
SUMMARYRENDERING . . 22-107 MRODefaultLocations preference . . . . 22-83
SRP0RqstActivityRevision_ MRODefaultLogBook preference . . . . 22-90
DefaultChildProperties . . . 22-108 MRODeviatedColorPref preference . . . 22-72
SRP0RqstActivityRevision. MROExtraToDesignColorPref
MROCREATE preference . . . . . . . . . . . . . . . . . . . . 22-72
RENDERING . . . . . . . . . . 22-107 MROMissingColorPref preference . . . . 22-73
SRP0RqstActivityRevision. MRONeutralColumnsShownPref
RENDERING . . . . . . . . . . 22-108 preference . . . . . . . . . . . . . . . . . . . . 22-70
SRP0RqstActivityRevision_ MRONeutralShownColumnWidthsPref
ServiceDiscrepancy_default_ preference . . . . . . . . . . . . . . . . . . . . 22-70
relation . . . . . . . . . . . . . . 22-109 MROSubstituteColorPref . . . . . . . . . . 22-73
SRP0RqstActivityRevision. MSE_ICS_default_type preference . . . . 20-7
SUMMARYRENDERING . . 22-108 MSE_load_related_product_process_plant
SRP0ServiceCatalog_ preference . . . . . . . . . . . . . . . . . . . . 20-20
DefaultChildProperties . . . 22-110 MSWord_DefaultChildProperties
SRP0ServiceCatalog_HWSOStructure_ preference . . . . . . . . . . . . . . . . . . . . 10-84
default_relation . . . . . . . . 22-110 Multi-Site
SRP0ServiceCatalog. Monolingual sites . . . . . . . . . . . . . . 18-37
MROCREATERENDERING . . 22-109 Populating FSC . . . . . . . . . . . . . . . . 9-36
SRP0ServiceCatalog_ Replica storage . . . . . . . . . . . . . . . 18-32
PseudoFolder . . . . . . . . . . 22-111 Stub replica files . . . . . . . . . . . . . . 18-52
SRP0ServiceCatalog. Stub tickets . . . . . . . . . . . . . . . . . . 18-56
RENDERING . . . . . . . . . . 22-109 TC_disallow_release_status_on_
SRP0ServiceCatalog_ replica . . . . . . . . . . . . . . . . . . . 18-29
SRP0ProductCatalog_default_ TC_follow_ownership_chain_max_site_
relation . . . . . . . . . . . . . . 22-111 count . . . . . . . . . . . . . . . . . . . . 18-32
SRP0ServiceCatalog. TC_force_remote_sites_exclude_
SUMMARYRENDERING . . 22-110 files . . . . . . . . . . . . . . . . . . . . . 18-32
SRP0ServiceDiscrepancy. TC_master_locale_<site_name> . . . 18-37
MROCREATERENDERING . . 22-111 TC_on_demand_sync_broadcast_
SRP0ServiceOffering_ActivityCost_ mode . . . . . . . . . . . . . . . . . . . . 18-40
default_relation . . . . . . . . 22-112 TC_Populate_FSC_Server_Targets . . 9-36

Index
TC_stub_dataset_files_after_ownership_ ODS_multiprocess_max_subprocess_
transfer . . . . . . . . . . . . . . . . . . 18-52 count . . . . . . . . . . . . . . . . . . . . 18-16
TC_validate_stub_tickets . . . . . . . . 18-56 ODS_multiprocess_mode . . . . . . . . 18-16
Multi-Site Collaboration preferences . . 9-32, ODS_permitted_sites . . . . . . . . . . . 18-17
18-1 ODS_proxy_server_type . . . . . . . . . 18-17
Baseline_auto_remote_checkout_ ODS_publication_sites . . . . . . . . . . 18-18
allowed . . . . . . . . . . . . . . . . . . . . 18-1 ODS_restricted_sites . . . . . . . . . . . 18-18
HUB_no_export_record_transfer_site_ ODS_searchable_sites . . . . . . . . . . 18-18
list . . . . . . . . . . . . . . . . . . . . . . . 18-2 ODS_searchable_sites_excluded . . . 18-19
IDSM_Compression . . . . . . . . . . . . . 18-3 ODS_site . . . . . . . . . . . . . . . . . . . . 18-19
IDSM_Compression_Type . . . . . . . . . 18-3 ODS_suppress_pubrec_if_no_
IDSM_do_not_resend_up_to_date_ access . . . . . . . . . . . . . . . . . . . . 18-19
file . . . . . . . . . . . . . . . . . . . . . . . 18-4 TC_<daemon name>_<site ID>_prog_
IDSM_dsa_notification_email_ number . . . . . . . . . . . . . . . . . . 18-23
address . . . . . . . . . . . . . . . . . . . 18-5 TC_<daemon name>_<site name>_port_
IDSM_dsa_sites_permitted_to_push_ number . . . . . . . . . . . . . . . . . . 18-23
admin_data . . . . . . . . . . . . . . . . 18-4 TC_<daemon name>_<site name>_prog_
IDSM_exclude_unpublished_ number . . . . . . . . . . . . . . . . . . 18-24
components . . . . . . . . . . . . . . . . 18-5 Tc_allow_users_edit_pfdata_
IDSM_ft_buffer_kb . . . . . . . . . . . . . 18-6 options . . . . . . . . . . . . . . . . . . . 18-24
IDSM_ft_client_timeout . . . . . . . . . . 18-6 TC_altrep_update_lmd . . . . . . . . . . 18-25
IDSM_ft_get_port_number_from_ TC_always_exclude_dataset_files_on_
services . . . . . . . . . . . . . . . . . . . 18-6 export . . . . . . . . . . . . . . . . . . . 18-22
IDSM_ft_port_number . . . . . . . . . . . 18-7 TC_appref_registry_site . . . . . . . . . 18-25
IDSM_ft_server_timeout . . . . . . . . . . 18-7 TC_assembly_xml_relation . . . . . . . 18-25
IDSM_ft_use_rpc_mode . . . . . . . . . . 18-8 TC_background_object_export_
IDSM_permitted_checkout_sites . . . . 18-8 dir . . . . . . . . . . . . . . . . . . . . . . 18-26
IDSM_permitted_checkout_users_from_ TC_bom_level_export . . . . . . 18-21, 18-26
site_sitename . . . . . . . . . . . . . . . 18-8 TC_check_remote_user_priv_from_
IDSM_permitted_sites . . . . . . . . . . . 18-9 sites . . . . . . . . . . . . . . . . . . . . . 18-27
IDSM_permitted_transfer_sites . . . . 18-9 TC_dataset_vers_export . . . . 18-20, 18-28
IDSM_permitted_transfer_users_from_site_ TC_directly_transferable_classes . . . 18-29
sitename . . . . . . . . . . . . . . . . . . 18-9 TC_disallowed_replica_relations
IDSM_permitted_users_from_site_ preference . . . . . . . . . . . . . . . . 18-29
sitename . . . . . . . . . . . . . . . . . 18-10 TC_do_not_insert_imported_objects_into_
IDSM_proxy_client_alternate_proxy_host_ folder . . . . . . . . . . . . . . . . . . . . 18-30
for . . . . . . . . . . . . . . . . . . . . . . 18-10 TC_EMAIL_AFTER_BACKGROUND_
IDSM_proxy_server_type . . . . . . . . 18-11 REMOTE_IMPORT . . . . . . . . . . 18-31
IDSM_restricted_sites . . . . . . . . . . 18-11 Tc_export_pfmember_replica . . . . . . 18-31
ITEM_autopublish . . . . . . . . . . . . . 18-11 TC_external_app_reg_url . . . . . . . . 18-31
ITEM_autopublish_ignore_errors . . 18-12 TC_hub_groups . . . . . . . . . . . . . . . 18-33
ITEM_autopublish_sites . . . . . . . . . 18-13 TC_idsm_client_def_timeout . . . . . . 18-35
ITEM_id_allow_if_registry_down . . 18-13 TC_idsm_client_initial_timeout . . . . 18-35
ITEM_id_always_register_on_ TC_idsm_proxy_server_site_table . . 18-36
creation . . . . . . . . . . . . . . . . . . 18-13 TC_ie_error_report . . . . . . . . . . . . . 18-36
ITEM_id_registry . . . . . . . . . . . . . . 18-14 TC_modified_only_export . . . 18-21, 18-37
ITEM_id_registry_site . . . . . . . . . . 18-14 TC_multi_site_project_member_
ITEM_id_unregister_on_delete . . . . 18-14 bypass . . . . . . . . . . . . . . . . . . . . . 6-5
ITEM_relation_types_update_ TC_ods_client_def_timeout . . . . . . . 18-39
lmd . . . . . . . . . . . . . . . . . . . . . 18-15 TC_ods_client_initial_timeout . . . . . 18-40
ODS_multiprocess_idle_subprocess_ TC_ods_proxy_server_site_table . . . 18-40
timeout . . . . . . . . . . . . . . . . . . 18-15 TC_ownership_export . . . . . . 18-20, 18-41
ODS_multiprocess_initial_subprocess_ TC_post_export_script . . . . . . . . . . 18-42
count . . . . . . . . . . . . . . . . . . . . 18-16 TC_pre_import_script . . . . . . . . . . . 18-43

Index
Tc_preserve_replica_pfmember_ RDV_show_itemid_prefix . . . . . . . 19-125

ownership . . . . . . . . . . . . . . . . . 18-43 MySearchHistory_Limit preference . . 10-47
Tc_publish_pfdata_with_
assemblies . . . . . . . . . . . . . . . . 18-44 N
Tc_publish_pfmembers_with_
pftemplate . . . . . . . . . . . . . . . . 18-44 New_Ic_Dialog_last_ic_type
Tc_publish_pftemplate_with_ preference . . . . . . . . . . . . . . . . . . . . 19-66
pfmember . . . . . . . . . . . . . . . . . 18-45 NLS_SORT variable . . . . . . . . . . . . . . . 3-6
TC_publishable_classes . . . . . . . . . 18-45 NR_BYPASS preference . . . . . . . . . . . . 5-5
TC_reference_update_lmd . . . . . . . 18-46 NX Integration preferences . . . . . . . . . 5-68
TC_relation_export_on_transfer . . . 18-47 NX_InterOptWithProductViewDataset
TC_relation_required_on_export . . . 18-47 preference . . . . . . . . . . . . . . . . . . . . . 5-73
TC_relation_required_on_ NX_on_demand_generate_vis_data_priority
transfer . . . . . . . . . . . . . . . . . . 18-48 preference . . . . . . . . . . . . . . . . . . . . . 5-43
TC_remote_checkin_assy_option . . . 18-48 NX_supported_operation_types
TC_remote_checkin_exclude_ preference . . . . . . . . . . . . . . . . . . . . . 20-9
relations . . . . . . . . . . . . . . . . . . 18-49 NX_tocgm_on_demand_generate_vis_data_
TC_remote_checkin_preserve_replica_ priority preference . . . . . . . . . . . . . . . 5-44
owning_user_and_group . . . . . . 18-50 NX_tocgm_translation_service_name
TC_remote_checkin_relation_send_as_ preference . . . . . . . . . . . . . . . . . . . . . 5-43
replica . . . . . . . . . . . . . . . . . . . 18-51 NX_translation_service_name
TC_rendering_update_lmd . . . . . . . 18-46 preference . . . . . . . . . . . . . . . . . . . . . 5-42
TC_replica_volume . . . . . . . . . . . . . 18-51 NXCheckMate.
TC_replication_exclude_types . . . . . 18-51 CREATERENDERING . . . . . . . . . . 5-109
TC_retain_group_on_import . . . . . . 18-52 NXCheckMate.
TC_subscribable_replica_classes . . . 18-53 SUMMARYRENDERING . . . . . . . . . 5-110
TC_sync_max_assy_level . . . . . . . . 18-53 NXCheckMateCreate. CREATE_
TC_sync_revision_rules . . . . . . . . . 18-54 REGISTEREDTO . . . . . . . . . . . . . . 5-109
TC_transfer_area . . . . . . . . . . . . . . 18-54 NXCheckMateRevision.
TC_truncate_file_name . . . . . . . . . . 18-55 SUMMARYRENDERING . . . . . . . . . 5-110
TC_use_group_admin_as_default_replica_ NXCheckMateRevSummary. SUMMARY_
owner . . . . . . . . . . . . . . . . . . . . 18-56 REGISTEREDTO . . . . . . . . . . . . . . 5-110
Multi-Site preferences NXCheckMateSummary. SUMMARY_
TC_identify_plmxml_import_ REGISTEREDTO . . . . . . . . . . . . . . 5-111
dataset . . . . . . . . . . . . . . . . . . . 18-34 NXCMValData.
TC_plmxml_import_item_filter . . . . 18-41 CREATERENDERING . . . . . . . . . . 5-111
TC_plmxml_sync_dataset . . . . . . . . 18-42 NXCMValData.
Multi-Structure Manager SUMMARYRENDERING . . . . . . . . . 5-112
preferences . . . . . . . . . . . . . . . . . . . 19-40 NXCMValDataCreate. CREATE_
ALLOC_Group_Allocation_Types . . 19-40 REGISTEREDTO . . . . . . . . . . . . . . 5-111
ALLOC_map_copy_allocations . . . . 19-43 NXCMValDataRevision.
ALLOC_Product_Representation_ SUMMARYRENDERING . . . . . . . . . 5-112
Types . . . . . . . . . . . . . . . . . . . . 19-41 NXCMValDataRevSummary. SUMMARY_
ALLOC_Source_Occurrence_ REGISTEREDTO . . . . . . . . . . . . . . 5-112
Types . . . . . . . . . . . . . . . . . . . . 19-42 NXCMValDataSummary. SUMMARY_
ALLOC_source_target_ REGISTEREDTO . . . . . . . . . . . . . . 5-113
cardinality . . . . . . . . . . . . . . . . 19-42 NXMGR_allow_3_tier_interop
ALLOC_Target_Occurrence_ variable . . . . . . . . . . . . . . . . . . . . . . . 3-6
Types . . . . . . . . . . . . . . . . . . . . 19-41 NXRDDV.
Default_StructureContext_Type . . . 19-44 SUMMARYRENDERING . . . . . . . . . 5-114
Multisite_Ticket_Expiration_Interval NXRDDVRevision.
preference . . . . . . . . . . . . . . . . . . . . . 9-27 SUMMARYRENDERING . . . . . . . . . 5-113
My Teamcenter preferences NXRDDVRevSummary. SUMMARY_
LOU_display_name_properties . . . 19-114 REGISTEREDTO . . . . . . . . . . . . . . 5-113

Index
NXRDDVSummary. SUMMARY_ ParmDefBoolRevision.RENDERING

REGISTEREDTO . . . . . . . . . . . . . . 5-114 preference . . . . . . . . . . . . . . . . . . . . 22-35
NXRDDVValData. ParmDefDateRevision.RENDERING
SUMMARYRENDERING . . . . . . . . . 5-115 preference . . . . . . . . . . . . . . . . . . . . 22-36
NXRDDVValDataRevision. ParmDefDblRevision.RENDERING
SUMMARYRENDERING . . . . . . . . . 5-114 preference . . . . . . . . . . . . . . . . . . . . 22-34
NXRDDVValDataRevSummary. SUMMARY_ ParmDefHexRevision.RENDERING
NXRDDVValDataSummary. SUMMARY_ ParmDefIntRevision.RENDERING
ParmDefSEDRevision.RENDERING
O preference . . . . . . . . . . . . . . . . . . . . 22-37
ParmDefStrRevision.RENDERING
OCS_company_email_domain preference . . . . . . . . . . . . . . . . . . . . 22-34
preference . . . . . . . . . . . . . . . . . . . . . 5-10 ParmGrpDef.RENDERING
OCS_use_email_property . . . . . . . . . . . 5-10 preference . . . . . . . . . . . . . . . . . . . . 22-40
OCS_use_presence_display . . . . . . . . . 5-11 ParmGrpDefRevision.RENDERING
ODBC Driver preferences . . . . . . . . . 23-52 preference . . . . . . . . . . . . . . . . . . . . 22-41
TC_ODBC_release_status . . . . . . . . 23-52 ParmGrpValRevision.RENDERING
ODS_multiprocess_idle_subprocess_timeout preference . . . . . . . . . . . . . . . . . . . . 22-38
preference . . . . . . . . . . . . . . . . . . . . 18-15 PartLogisticsForm.
ODS_multiprocess_initial_subprocess_count SUMMARYRENDERING . . . . . . . . . 22-73
preference . . . . . . . . . . . . . . . . . . . . 18-16 PartMovement_DefaultChildProperties
ODS_multiprocess_max_subprocess_count preference . . . . . . . . . . . . . . . . . . . . 22-90
preference . . . . . . . . . . . . . . . . . . . . 18-16 PartMovement.MROCREATERENDERING
ODS_multiprocess_mode preference . . 18-16 preference . . . . . . . . . . . . . . . . . . . . 22-91
ODS_permitted_sites preference . . . . . 18-17 PartMovement.SUMMARYRENDERING
ODS_proxy_server_type preference . . . 18-17 preference . . . . . . . . . . . . . . . . . . . . 22-92
ODS_publication_sites preference . . . . 18-18 PartMovement.ENABLE_PROPERTIES_
ODS_restricted_sites preference . . . . . 18-18 EDIT preference . . . . . . . . . . . . . . . 22-91
ODS_searchable_sites preference . . . . 18-18 PartMovement.RENDERING
ODS_searchable_sites_excluded preference . . . . . . . . . . . . . . . . . . . . 22-91
preference . . . . . . . . . . . . . . . . . . . . 18-19 PartNumberCharsForPhysicalPartIdPref
ODS_site preference . . . . . . . . . . . . . 18-19 preference . . . . . . . . . . . . . . . . . . . . 22-74
ODS_suppress_pubrec_if_no_access Password preferences . . . . . . . . . . . . . 5-88
preference . . . . . . . . . . . . . . . . . . . . 18-19 PASSWORD_minimum_alpha . . . . . . 5-91
OpenAfterCreatePref preference . . . . . 10-47 PASSWORD_minimum_
Optimizing logging files . . . . . . . . . . . . . 2-1 characters . . . . . . . . . . . . . . . . . 5-89
Options . . . . . . . . . . . . . . . . . . . . . . . . 4-1 PASSWORD_minimum_digits . . . . . . 5-90
ORACLE_SERVER variable . . . . . . . . . 3-6 PASSWORD_minimum_special_
ORACLE_SID variable . . . . . . . . . . . . . 3-6 chars . . . . . . . . . . . . . . . . . . . . . 5-90
ORG_UIF_spacing preference . . . . . . 11-11 PASSWORD_mixed_case_required . . 5-90
ORG_UIF_user_name_display PASSWORD_special_characters . . . . 5-89
preference . . . . . . . . . . . . . . . . . . . . 11-12 PASSWORD_minimum_alpha
preference . . . . . . . . . . . . . . . . . . . . . 5-91
P PASSWORD_minimum_characters
preference . . . . . . . . . . . . . . . . . . . . . 5-89
PAD preferences . . . . . . . . . . . . . . . . 20-56 PASSWORD_minimum_digits
ParmDef.RENDERING preference . . . 22-40 preference . . . . . . . . . . . . . . . . . . . . . 5-90
ParmDefBCDRevision.RENDERING PASSWORD_minimum_special_chars
ParmDefBitDefRevision. RENDERING PASSWORD_mixed_case_required

Index
PASSWORD_special_characters PhysicalPartRevision.SUMMARY
preference . . . . . . . . . . . . . . . . . . . . . 5-89 RENDERING preference . . . . . . . . . 22-77
PasteDuplicateTemplates PhysicalRealization_relation_primary
PATH variable . . . . . . . . . . . . . . . . . . . 3-6 PIE_<transfer_mode_name>_process_in_
PDX_pkg_file_name . . . . . . . . . . . . . 18-59 chunks preference . . . . . . . . . . . . . . 18-66
Person attribute mapping preferences, PIE_<transfer_mode_name>_unload_objects
LDAP_person_attr_mapping . . . . . . 5-108 preference . . . . . . . . . . . . . . . . . . . . 18-67
PERSON_object_columns_hidden PIE_allow_import_with_different_sml
PERSON_object_columns_shown PIE_Extra_Error_Info_to_Xml
PERSON_object_widths_hidden PIE_IMF_FOR_CAD preference . . . . . 18-69
preference . . . . . . . . . . . . . . . . . . . . 10-48 PIE_transfermode_languages
PERSON_object_widths_shown preference . . . . . . . . . . . . . . . . . . . . 18-69
preference . . . . . . . . . . . . . . . . . . . . 10-49 Piece_Cost_Form_Elements
PERT chart preferences . . . . . . . . . . . 20-29 preference . . . . . . . . . . . . . . . . . . . . 22-21
PertChart.<object_type>.GColor . . . . . 20-29 Plant_Cost_Form_Elements
PertChart.<object_type>.Text . . . . . . . 20-29 preference . . . . . . . . . . . . . . . . . . . . 22-19
PertChart.ActivityDefault.GColor Plant.Template preference . . . . . . . . . 20-25
preference . . . . . . . . . . . . . . . . . . . . 20-29 Plant.Template.Cloning preference . . . 20-24
PertChart.ActivityDefault.Text Platform Designer preferences . . . . . 19-106
preference . . . . . . . . . . . . . . . . . . . . 20-29 Architecture_Type_generic_id_
PertChart.AutoSizeMode mapping . . . . . . . . . . . . . . . . . 19-106
preference . . . . . . . . . . . . . . . . . . . . 20-30 ArchitectureModeler_part_solution_
PertChart.BoxAutoSizeMaxWidth properties . . . . . . . . . . . . . . . . 19-109
preference . . . . . . . . . . . . . . . . . . . . 20-31 LOU_display_name_properties . . . 19-114
PertChart.BoxDefaultHeight RDV_platformdesigner_assign_bulk_
preference . . . . . . . . . . . . . . . . . . . . 20-32 variability . . . . . . . . . . . . . . . . 19-113
PertChart.BoxDefaultWidth RDV_show_itemid_prefix . . . . . . . 19-125
preference . . . . . . . . . . . . . . . . . . . . 20-31 PLM XML preferences . . . . . . . . . . . . 18-66
PertChartCreationLayout PLM_End_Item_Key preference . . . . . . 21-6
preference . . . . . . . . . . . . . . . . . . . . 20-32 PLMXML_continue_on_error
PhysicalContext_relation_primary preference . . . . . . . . . . . . . . . . . . . . 18-70
preference . . . . . . . . . . . . . . . . . . . . 22-74 PLMXML_export_packed_bom_<transfer-
PhysicalElement_Company_default_relation mode-name> preference . . . . . . . . . . 18-70
preference . . . . . . . . . . . . . . . . . . . . 22-74 PLMXML_import_default_password
PhysicalLocation_CompanyLocation_default_ preference . . . . . . . . . . . . . . . . . . . . 18-70
relation preference . . . . . . . . . . . . . . 22-84 PLMXML_log_file_content
PhysicalLocation_DefaultChildProperties preference . . . . . . . . . . . . . . . . . . . . 18-71
preference . . . . . . . . . . . . . . . . . . . . 22-84 PLMXML_overwrite_objects_on_import
PhysicalLocationContainsColumnsShownPref preference . . . . . . . . . . . . . . . . . . . . 18-72
preference . . . . . . . . . . . . . . . . . . . . 22-84 PLMXML_pre_expand_batch_size
PhysicalPart_Company_default_relation preference . . . . . . . . . . . . . . . . . . . . 20-86
preference . . . . . . . . . . . . . . . . . . . . 22-75 PLMXML_pre_expand_bop
PhysicalPart_DefaultChildProperties preference . . . . . . . . . . . . . . . . . . . . 20-85
preference . . . . . . . . . . . . . . . . . . . . 22-75 PLMXML_pre_expand_max_line_limit
PhysicalPart.SUMMARYRENDERING preference . . . . . . . . . . . . . . . . . . . . 20-86
preference . . . . . . . . . . . . . . . . . . . . 22-76 PLMXML_put_objects_in_newstuff_on_
PhysicalPartRelationsToExport import preference . . . . . . . . . . . . . . 18-72
preference . . . . . . . . . . . . . . . . . . . . 22-76 PLMXML_put_pie_log_in_syslog
PhysicalPartRevision_DefaultChildProperties preference . . . . . . . . . . . . . . . . . . . . 18-73
preferences . . . . . . . . . . . . . . . . . . . 22-76 PLMXML_sdk_threshold
preference . . . . . . . . . . . . . . . . . . . . 18-73

Index
PLMXML_use_pre_plm_appname PortalDesignContextProductContext
preference . . . . . . . . . . . . . . . . . . . . 18-73 ColumnsHiddenPref preference . . . . 19-20
PLUGIN_LOGFILE variable . . . . . . . . . 3-6 PortalDesignContextProductContext
POM_SCHEMA variable . . . . . . . . . . . . 3-7 ColumnsHiddenPrefWidth
POM_stub object synchronization . . . . 18-56 preference . . . . . . . . . . . . . . . . . . . . 19-22
POM_TRANSMIT_DIR variable . . . . . . . 3-7 PortalDesignContextProductContext
PortalDesignContext MaxMatchingBOMLines ColumnsShownPref preference . . . . . 19-19
preference . . . . . . . . . . . . . . . . . . . . 19-38 PortalDesignContextProductContext
PortalDesignContext ColumnsShownPrefWidth
ProductContextProperties preference . . . . . . . . . . . . . . . . . . . . 19-19
preference . . . . . . . . . . . . . . . . . . . . 19-18 PortalDesignContextProductItem
PortalDesignContext SearchEnginePreference ColumnsHiddenPref preference . . . . 19-13
PortalDesignContextAllowNoWorkParts ColumnsHiddenPrefWidth
PortalDesignContextAlways PortalDesignContextProductItem
ResetFilterConfigurationPanel ColumnsShownPref preference . . . . . 19-12
PortalDesignContextAttributeSchema ColumnsShownPrefWidth
SuppressedAttributes preference . . . 19-31 preference . . . . . . . . . . . . . . . . . . . . 19-12
PortalDesignContextCADbookmarkType PortalDesignContextProductItem
preference . . . . . . . . . . . . . . . . . . . . 19-34 Properties.attribute-value
PortalDesignContextECObject preference . . . . . . . . . . . . . . . . . . . . 19-11
.WorkPartRelationships PortalDesignContextProductItemQuery
PortalDesignContextECObject PortalDesignContextQPLServers
WorkPartProperties preference . . . . . 19-25 preference . . . . . . . . . . . . . . . . . . . . 19-31
PortalDesignContextECObject.TYPE PortalDesignContextSetVariant
preference . . . . . . . . . . . . . . . . . . . . 19-25 RulesMaxTargetAppearances
PortalDesignContextExcluded preference . . . . . . . . . . . . . . . . . . . . 19-38
WorkPart.Types preference . . . . . . . 19-26 PortalDesignContextSupport
PortalDesignContextFindInstallation InstallationAssemblySelection
TreeWalkIncrement preference . . . . . 19-30 preference . . . . . . . . . . . . . . . . . . . . 19-30
PortalDesignContextIsInstallation PortalDesignContextUse
AssemblyMethod preference . . . . . . . 19-28 UnconfigurableSearchResults
PortalDesignContextIsInstallation preference . . . . . . . . . . . . . . . . . . . . 19-30
AssemblyMethod.has_bomline_prop.name PortalDesignContextVISbookmarkType
PortalDesignContextIsInstallation PortalDesignContextWIPRevRule
AssemblyMethod.has_bomline_ preference . . . . . . . . . . . . . . . . . . . . 19-27
prop.value . . . . . . . . . . . . . . . . . . . . 19-29 PortalPSEColumnsShownPref
PortalDesignContextIsInstallation preference . . . . . . . . . . . . . . . . . . . . 19-54
AssemblyMethod.hasIRType.Type PortalPSEShownColumnsWidthPref
PortalDesignContextMaxMatchingObjects Portfolio, Program and Project Management
preference . . . . . . . . . . . . . . . . . . . . 19-37 preferences
PortalDesignContextProcess TC_Project_DefaultChildProperties . . . 6-3
.WorkPartOrChangeAttachmentTypes TC_Project_PseudoFolder . . . . . . . . . . 6-3
preference . . . . . . . . . . . . . . . . . . . 19-115 TC_set_current_project . . . . . . . . . . . 6-5
PortalDesignContextProcess Preference hierarchy . . . . . . . . . . . . . . . 4-5
.WorkPartProperties preference . . . 19-114 Preferences . . . . . . . . . . . . . . . . . . . . . . 4-1
PortalDesignContextProduct ItemProperties Business rules . . . . . . . . . . . . . . . . . . 5-1
preference . . . . . . . . . . . . . . . . . . . . 19-10 Client interface preferences . . . . . . . . 5-8
Creating categories . . . . . . . . . . . . . 4-10

Index
Current values buttons . . . . . . . . . . . . 4-4 ALLOC_source_target_

Deleting categories . . . . . . . . . . . . . . 4-10 cardinality . . . . . . . . . . . . . . . . 19-42
Hierarchy . . . . . . . . . . . . . . . . . . . . . 4-5 ALLOC_Target_Occurrence_
IDENTIFIER_idincontext . . . . . . . . . 5-20 Types . . . . . . . . . . . . . . . . . . . . 19-41
Index . . . . . . . . . . . . . . . . . . . . . . . . 4-2 API_ugpart_attr_titles . . . . . . . . . . . 5-68
Migration . . . . . . . . . . . . . . . . . . . . . 4-8 application name.ic_icon_level . . . . 19-58
Options . . . . . . . . . . . . . . . . . . . . . . . 4-2 application name.ic_show_remove_
Organization . . . . . . . . . . . . . . . . . . . 4-4 icons . . . . . . . . . . . . . . . . . . . . 19-59
Search Options . . . . . . . . . . . . . . . . . 4-3 APPR_allow_background_updates . . . 19-6
TC_default_export_sites . . . . . . . . . 18-28 APPR_background_updateremail_interval_
TC_relation_export_on_transfer . . . 18-48 for_different_package . . . . . . . . . 19-7
TC_relation_required_on_ APPR_background_updateremail_interval_
transfer . . . . . . . . . . . . . . . . . . 18-47 for_same_package . . . . . . . . . . . . 19-7
TC_ugmaster_name_separator . . . . . 5-78 APPR_background_updater_admin_email_
TcUseAppLauncher . . . . . . . . . . . 10-100 address . . . . . . . . . . . . . . . . . . . 19-6
Teamcenter Integration for NX . . . . . 4-11 APPR_background_updater_auditing_
Pro/ENGINEER_on_demand_generate_vis_ enabled . . . . . . . . . . . . . . . . . . . 19-7
data_priority preference . . . . . . . . . . . 5-49 APPR_background_updater_gap_between_
Pro/ENGINEER_translation_service_name tries . . . . . . . . . . . . . . . . . . . . . . 19-8
preference . . . . . . . . . . . . . . . . . . . . . 5-49 APPR_background_updater_
ProblemReport.CREATERENDERING interval . . . . . . . . . . . . . . . . . . . 19-8
preference . . . . . . . . . . . . . . . . . . . . 13-18 APPR_background_updater_max_num_
ProblemReportCreate.CREATE_ failures . . . . . . . . . . . . . . . . . . . . 19-8
REGISTEREDTO preference . . . . . . 13-18 APPR_background_updater_max_num_
ProblemReportRevision_ heartbeats . . . . . . . . . . . . . . . . . 19-9
DefaultChildProperties preference . . 13-18 APPR_background_updater_max_num_
ProblemReportRevision.REGISTEREDTO records . . . . . . . . . . . . . . . . . . . . 19-9
preference . . . . . . . . . . . . . . . . . . . . 13-19 APPR_background_updater_max_num_
ProblemReportRevision.RENDERING tries . . . . . . . . . . . . . . . . . . . . . . 19-9
preference . . . . . . . . . . . . . . . . . . . . 13-19 Architecture_Type_generic_id_
ProblemReportRevision. mapping . . . . . . . . . . . . . . . . . 19-106
SUMMARYRENDERING ArchitectureModeler_add_design_business_
preference . . . . . . . . . . . . . . . . . . . . 13-19 rule_check . . . . . . . . . . . . . . . 19-107
ProblemReportRevisionSummary. ArchitectureModeler_add_design_
SUMMARY_REGISTEREDTO occurrence_business_rule_
preference . . . . . . . . . . . . . . . . . . . . 13-20 check . . . . . . . . . . . . . . . . . . . 19-107
Process Simulate preferences . . . . . . . 20-83 ArchitectureModeler_locking_retry_
Process.Template prereference . . . . . . 20-27 count . . . . . . . . . . . . . . . . . . . 19-108
Process.Template.Ignoring_Consumes ArchitectureModeler_multiple_installation_
preference . . . . . . . . . . . . . . . . . . . . 20-27 assemblies_condition . . . . . . . . 19-108
Process.Template.Mapping_Consumes ArchitectureModeler_remove_design_
preference . . . . . . . . . . . . . . . . . . . . 20-25 business_rule_check . . . . . . . . 19-109
Process.Template.Referencing_ ArchitectureModeler_remove_
Consumes . . . . . . . . . . . . . . . . . . . . 20-26 design_occurrence_business_rule_
Product structure and Repeatable Digital check . . . . . . . . . . . . . . . . . . . 19-110
Validation preferences . . . . . . . . . . . 19-84 ArchitectureModeler_RemoveDesign_
Product structure preferences Max . . . . . . . . . . . . . . . . . . . . 19-109
AbsOccGrmCopyRules . . . . . . . . . . 19-77 ArchitectureModeler_replace_design_
ALLOC_Group_Allocation_Types . . 19-40 business_rule_check . . . . . . . . 19-110
ALLOC_map_copy_allocations . . . . 19-43 ArchitectureModeler_replace_
ALLOC_Product_Representation_ design_occurrence_business_rule_
Types . . . . . . . . . . . . . . . . . . . . 19-41 check . . . . . . . . . . . . . . . . . . . 19-111
ALLOC_Source_Occurrence_
Types . . . . . . . . . . . . . . . . . . . . 19-42

Index
ArchitectureModeler_update_design_ DesignContextLoadRDV
occurrences_business_rule_ ContextObjectMode . . . . . . . . . . 19-17
check . . . . . . . . . . . . . . . . . . . 19-112 DesignContextMaximum
ArchitectureModeler_update_designs_ ShownTabs . . . . . . . . . . . . . . . . 19-33
business_rule_check . . . . . . . . 19-111 DesignContextPickUp
ArchitectureModeler_use_all_installation_ NewBackgroundAppearance . . . . 19-17
assemblies . . . . . . . . . . . . . . . 19-112 DesignContextPreciseRevRule . . . . 19-34
BOM_Additional_Packing_ DesignContextRDVContextObject
Criteria . . . . . . . . . . . . . . . . . . 19-90 AddToECObjectPseudoFolder
BOM_Additional_Ref_Designator_Search_ Preference . . . . . . . . . . . . . . . . 19-16
Criteria . . . . . . . . . . . . . . . . . . 19-90 DesignContextShow
BOM_Enable_Quantity_Validation_ ClearanceDBMenu . . . . . . . . . . 19-24
Against_Ref_Designator . . . . . . . 19-91 EPM_tessellation_servers . . . . . . . 19-114
BOM_Enable_Ref_Designator_Value_ EPM_tessellation_target_type . . . . 19-113
Packing . . . . . . . . . . . . . . . . . . 19-89 GDE_objects_with_integer_
BOM_MARKUP_ADD_FONT_ quantity . . . . . . . . . . . . . . . . . . 19-46
STYLE . . . . . . . . . . . . . . . . . . . 19-60 IC_baseline_carry_forward_active_
BOM_MARKUP_ADD_ changes . . . . . . . . . . . . . . . . . . 19-61
FOREGROUND . . . . . . . . . . . . 19-60 IC_baseline_carry_forward_
BOM_MARKUP_STRIKE_ status . . . . . . . . . . . . . . . . . . . . 19-62
FOREGROUND . . . . . . . . . . . . 19-61 ICPanelAttachChangeDefs . . . . . . . 19-63
BOM_objects_excluded_from_ ICPanelAttachChangeWidths . . . . . 19-63
split . . . . . . . . . . . . . . . . . . . . . 19-45 ICPanelBomChangeDefs . . . . . . . . . 19-62
BOMCompareVisibleModes . . . . . . 19-59 ICPanelBomChangeWidths . . . . . . . 19-62
BOMExcludeFromPackCheck . . . . . 19-92 ICPanelOccAttrChangeDefs . . . . . . 19-64
BOMWriterDirect ICPanelOccAttrChangeWidths . . . . 19-64
ModelRelationType . . . . . . . . . 19-129 Incremental_Change_
BOMWriterNo Management . . . . . . . . . . . . . . . 19-65
DescendantsInPLMXML . . . . . 19-130 JT_File_Excluded_Refsets . . . . . . . 19-95
BOMWriterNoDirectParents . . . . . 19-130 JT_File_OverrideChildren_
CFM_ITEM_TYPE_RULE_INCLUDE_ Refsets . . . . . . . . . . . . . . . . . . . 19-93
SUB_TYPES . . . . . . . . . . . . . . . 19-45 JT_File_Priority_Refsets . . . . . . . . 19-94
CFMOccEffMode . . . . . . . . . . . . . . 19-76 JTContentBomLineProperties . . . . . 19-95
ConfigureToLoadEnableDefault JTContentHintPropertyPolicy . . . . . 19-96
VariantConfig . . . . . . . . . . . . . . 19-75 MoveICCreationToMenu . . . . . . . . . 19-66
<DATASET TYPE>_saveas_ New_Ic_Dialog_last_ic_type . . . . . . 19-66
pattern . . . . . . . . . . . . . . . . . . . . 5-73 NX_InterOptWith
DATASET_saveas_allow_ ProductViewDataset . . . . . . . . . . 5-73
duplicates . . . . . . . . . . . . . . . . . . 5-69 PortalDesignContext
DATASET_saveas_allow_name_ AllowNoWorkParts . . . . . . . . . . 19-26
modification . . . . . . . . . . . . . . . . 5-69 PortalDesignContext
DATASET_saveas_always_copy . . . . . 5-70 CADbookmarkType . . . . . . . . . . 19-34
DATASET_saveas_force_name_ PortalDesignContext
validation . . . . . . . . . . . . . . . . . . 5-70 ExcludedWorkPart.Types . . . . . . 19-26
DATASET_saveas_never_copy . . . . . 5-71 PortalDesignContext
DATASET_saveas_owner . . . . . . . . . 5-71 MaxMatchingBOMLines . . . . . . 19-38
DATASET_saveas_pattern . . . . . . . . 5-72 PortalDesignContext
Default_StructureContext_Type . . . 19-44 MaxMatchingObjects . . . . . . . . . 19-37
DesignContext_ItemID_Query_lookup_ PortalDesignContext
string . . . . . . . . . . . . . . . . . . . . 19-32 ProductContextProperties . . . . . 19-18
DesignContext_PSE_ PortalDesignContext
Synchronization . . . . . . . . . . . . 19-36 SearchEnginePreference . . . . . . 19-31
DesignContextIncludeSub PortalDesignContext
ComponentsForSpatialSearch . . 19-32 VISbookmarkType . . . . . . . . . . . 19-35

Index
PortalDesignContext PortalDesignContextSupport
WIPRevRule . . . . . . . . . . . . . . . 19-27 InstallationAssemblySelection . . 19-30
PortalDesignContextAlways PortalDesignContextUse
ResetFilterConfigurationPanel . . 19-33 UnconfigurableSearchResults . . . 19-30
PortalDesignContextAttributeSchema PS_allow_plmxml_transforms_with_no_
SuppressedAttributes . . . . . . . . 19-31 legacy_factor . . . . . . . . . . . . . . . 19-98
PortalDesignContextECObject PS_assume_legacy_transform_
.WorkPartRelationships . . . . . . . 19-26 units . . . . . . . . . . . . . . . . . . . . 19-98
PortalDesignContextECObject PS_assume_old_transform_
WorkPartProperties . . . . . . . . . . 19-25 format . . . . . . . . . . . . . . . . . . . 19-97
PortalDesignContextECObject. PS_convert_legacy_transform_to_
TYPE . . . . . . . . . . . . . . . . . . . . 19-25 plmxml . . . . . . . . . . . . . . . . . . . 19-99
PortalDesignContextFindInstallation PS_Duplicate_FindNo_Update . . . . 19-92
TreeWalkIncrement . . . . . . . . . . 19-30 PS_Find_Number_Validation . . . . . 19-49
PortalDesignContextIs PS_new_seqno_mode . . . . . . . . . . . 19-49
InstallationAssemblyMethod.has_ PS_Reference_Designator_
bomline_prop.value . . . . . . . . . . 19-29 Validation . . . . . . . . . . . . . . . . . 19-91
PortalDesignContextIsInstallation PS_replace_with_substructure . . . . 19-50
AssemblyMethod . . . . . . . . . . . . 19-28 PS_structure_change_condition . . . . 19-99
PortalDesignContextIsInstallation PS_wu_configd_imprecise_only . . . . 19-50
AssemblyMethod.has_bomline_ PSE_check_read_access_for_Rev_Rule_
prop.name . . . . . . . . . . . . . . . . 19-29 entry . . . . . . . . . . . . . . . . . . . . 19-46
PortalDesignContextIsInstallation PSE_default_view_type . . . . . . . . . 19-46
AssemblyMethod.hasIRType. PSE_Display_Pending_Edits . . . . . . 19-47
Type . . . . . . . . . . . . . . . . . . . . 19-28 PSE_enable_related_substitutes . . . 19-70
PortalDesignContextProcess PSE_expand_on_open . . . . . . . . . . . 19-47
.WorkPartProperties . . . . . . . . 19-114 PSE_icon_placement . . . . . . . . . . . 19-67
PortalDesignContextProcess.WorkPart PSE_prompt_for_remote_import . . . 19-96
OrChangeAttachmentTypes . . . 19-115 PSE_ROLL_UP_TEMPLATES . . . . 19-48
PortalDesignContextProduct PSE_show_option_family_prefix . . . 19-67
ItemProperties . . . . . . . . . . . . . 19-10 PSE_show_option_item_prefix . . . . . 19-68
PortalDesignContextProductContext PSEAdditionColorPref . . . . . . . . . . 19-70
ColumnsHiddenPref . . . . . . . . . 19-20 PSEAllowLegacyVICreation . . . . . . 19-78
PortalDesignContextProductContext PSEAutoPackPref . . . . . . . . . . . . . 19-69
ColumnsHiddenPrefWidth . . . . . 19-22 PSEAutoViCreateEmptyVI . . . . . . . 19-81
PortalDesignContextProductContext PSEAutoViNamePrefix . . . . . . . . . . 19-82
ColumnsShownPref . . . . . . . . . . 19-19 PSEAutoViNewItemPopup . . . . . . . 19-82
PortalDesignContextProductContext PSEAutoViStopVICreation
ColumnsShownPrefWidth . . . . . 19-19 ForUnconfiguredModule . . . . . . 19-81
PortalDesignContextProductItem PSEBypassVISearch . . . . . . . . . . . 19-79
ColumnsHiddenPref . . . . . . . . . 19-13 PSEChangedColorPref . . . . . . . . . . 19-71
PortalDesignContextProductItem PSECreateVISameType . . . . . . . . . 19-79
ColumnsHiddenPrefWidth . . . . . 19-15 PSEDisplayTypePref . . . . . . . . . . . 19-66
PortalDesignContextProductItem PSEEnableFilteringUnconfigdDueTo
ColumnsShownPref . . . . . . . . . . 19-12 ClassicVariantsPref . . . . . . . . . . 19-75
PortalDesignContextProductItem PSEImpreciseColorPref . . . . . . . . . 19-69
ColumnsShownPrefWidth . . . . . 19-12 PSEIsNewVIisLinkedToModule . . . 19-78
PortalDesignContextProductItem PSEIsNewVILinkedToModule . . . . . 19-71
Properties.attribute-value . . . . . 19-11 PSEoccnotesnocopy . . . . . . . . . . . . 19-67
PortalDesignContextProductItem PSEPreciseColorPref . . . . . . . . . . . 19-68
Query . . . . . . . . . . . . . . . . . . . . 19-24 PSESavedConfigRelationTypes . . . . 19-89
PortalDesignContextQPLServers . . . 19-31 PSESearchColumnsShownPref . . . . 19-55
PortalDesignContextSetVariant PSESearchShownColumn
RulesMaxTargetAppearances . . . 19-38 WidthsPref . . . . . . . . . . . . . . . . 19-55

Index
PSEShowSubstitutesPref . . . . . . . . 19-70 RDVReleasedPartsCollector

PSEshowToolBar . . . . . . . . . . . . . . 19-48 Server . . . . . . . . . . . . . . . . . . 19-125
PSEShowUnconfigdEffPref . . . . . . . 19-74 RDVReleasedPartsProcessAssem
PSEShowUnconfigdVarPref . . . . . . 19-73 Type . . . . . . . . . . . . . . . . . . . 19-124
PSESubstituteColorPref . . . . . . . . . 19-69 ROLL_UP_QUANTITY_FLAG . . . . 19-48
PSEVariantRuleDialogTableSort . . . 19-71 ShowModuleIcons . . . . . . . . . . . . . 19-80
PSEVariantsMode . . . . . . . . . . . . . 19-73 ShowViIcons . . . . . . . . . . . . . . . . . 19-80
PSM_classic_variants_numeric_ TC_allow_appr_checking . . . . . . . . . 19-2
families . . . . . . . . . . . . . . . . . . 19-84 TC_allow_appr_query_auditing . . . . . 19-3
PSM_classic_variants_text_ TC_appr_allow_remote_query . . . . . . 19-4
families . . . . . . . . . . . . . . . . . . 19-82 TC_appr_checking_interval . . . . . . . . 19-3
PSM_global_option_item_id . . . . . . 19-88 TC_appr_remote_query_timeout . . . . 19-5
PUBLISH_AlignableSourceTypes . . 19-51 TC_BOM_Precision_Preference . . . . 19-52
PUBLISH_AlignableTargetTypes . . 19-51 TC_BVRSYNCFORM_
RAC_expand_below_batch_size . . . . 19-96 DELEGATE . . . . . . . . . . . . . . 19-101
RDV_audit_report_occurrence_ TC_CFG_PRODUCTS_USE_
attributes . . . . . . . . . . . . . . . . 19-116 VARIABILITY . . . . . . . . . . . . . 19-85
RDV_audit_report_usage_ TC_config_rule_name . . . . . . . . . . . 19-52
attributes . . . . . . . . . . . . . . . . 19-115 TC_default_part_type . . . . . . . . . . . . 5-74
RDV_authoring_override_user . . . 19-118 TC_ExportConfigUGNXAssembly . . 19-72
RDV_auto_functionality . . . . . . . . 19-118 TC_JT_voxel_size . . . . . . . . . . . . . . 19-93
RDV_auto_populate_occ_notes . . . 19-118 TC_NX_allow_attrsync_master_with_
RDV_build_intent_atth_type . . . . . 19-119 item . . . . . . . . . . . . . . . . . . . . . . 5-74
RDV_copied_occurrence_notes . . . . 19-120 TC_NX_Allow_Deepcopy . . . . . . . . . . 5-75
RDV_Create_SCO_WITHOUT_ TC_NX_ATTRIBUTES_FORM . . . . . 5-75
APN . . . . . . . . . . . . . . . . . . . . 19-120 TC_NX_DeleteMarkupsOnDrawing
RDV_default_Architecture_Breakdown_ SheetImport . . . . . . . . . . . . . . . . 5-77
RevRule . . . . . . . . . . . . . . . . . 19-120 TC_NX_DrawingSheet_Deletion_
RDV_enable_product_lock . . . . . . 19-121 Pattern . . . . . . . . . . . . . . . . . . . . 5-77
RDV_export_nve . . . . . . . . . . . . . 19-121 TC_NX_Foreign_Datasets . . . . . . . . . 5-78
RDV_install_configuration_ TC_NX_Navigator_Override_NX_Load_
rules . . . . . . . . . . . . . . . . . . . 19-122 Option . . . . . . . . . . . . . . . . . . . . 5-79
RDV_occurrence_business_rule_ TC_NX_NEW_COPY_REV . . . . . . . . 5-79
check . . . . . . . . . . . . . . . . . . . 19-122 TC_NX_NEW_NR_FORMS . . . . . . . . 5-80
RDV_part_business_rule_check . . . 19-123 TC_NX_nonmaster_additional_
RDV_part_occ_note_mappings . . . 19-123 forms . . . . . . . . . . . . . . . . . . . . . 5-80
RDV_partnumber_validation_ TC_NX_Unit_Of_Measure_As_Geometric_
rule . . . . . . . . . . . . . . . . . . . . 19-123 List . . . . . . . . . . . . . . . . . . . . . . 5-81
RDV_product_code_mapping . . . . . 19-124 TC_NX_Unit_Of_Measure_Each_
RDV_turn_audit_logging_on . . . . . 19-126 List . . . . . . . . . . . . . . . . . . . . . . 5-81
RDV_uneditable_part_occ_notes . . 19-126 TC_NX_UPDATE_ATTRIBUTES . . . 5-82
RDV_usage_attribute_set . . . . . . . 19-127 TC_NX_View_Type . . . . . . . . . . . . . 5-82
RDV_valid_partnumber_rule . . . . 19-127 TC_prevent_appr_query_on_corrupt_
RDV_variant_expression_overlap_ root . . . . . . . . . . . . . . . . . . . . . . 19-4
checking_mode . . . . . . . . . . . . 19-128 TC_Schematic_BOMView_Types . . . . 21-8
RDV_variant_overlays_mode . . . . 19-128 TC_show_open_in_nx_button . . . . . 19-36
RDV_variant_overlays_uses_true_ TC_show_open_in_pse_button . . . . . 19-52
availability . . . . . . . . . . . . . . . 19-129 TC_SPSD_FOLDER . . . . . . . . . . . . . 5-83
RDVClearanceProxyServers . . . . . . 19-37 TC_SPSD_FOLDER_PATH . . . . . . . . 5-83
RDVCreateSCOForClearance . . . . 19-119 TC_UG_save_precise_on_uprev . . . . . 5-81
RDVIgnoreErrorConnectReleased TC_USE_TEST_ATTR_
PartsServer . . . . . . . . . . . . . . 19-121 MAPPINGS . . . . . . . . . . . . . . . . 5-84
RDVLoadAppearanceGroupMode . . 19-18 TC_ValidApprovedStatus . . . . . . . . 19-76

Index
TCAllowedChildTypes_ Projects
<ItemTypeOrGDEType> . . . . . . 19-87 Assigning related objects . . . . . . . . . . 6-4
TCAllowedParentTypes_itemtype . . 19-88 Propagation rules . . . . . . . . . . . . . . . . 6-4
TCEnforceSingleType . . . . . . . . . . . 19-87 Propagation rules . . . . . . . . . . . . . . . . . 6-4
TRACE_BACK . . . . . . . . . . . . . . . . 5-87 ProvidedFrom_relation_primary
UGhookupPartDisplayPreference . . . 5-87 preference . . . . . . . . . . . . . . . . . . . . 22-59
UGhookupStructureUpdate PS_allow_plmxml_transforms_with_no_
OnLoad . . . . . . . . . . . . . . . . . . . 5-86 legacy_factor preference . . . . . . . . . . 19-98
UGhookupStructureUpdate PS_assume_legacy_transform_units
OnSave . . . . . . . . . . . . . . . . . . . 5-86 preference . . . . . . . . . . . . . . . . . . . . 19-98
UGII_KEEP_SYSTEM_LOG . . . . . . . 5-87 PS_assume_old_transform_format
UGII_OPTION . . . . . . . . . . . . . . . . 5-88 preference . . . . . . . . . . . . . . . . . . . . 19-97
UGII_TMP_DIR . . . . . . . . . . . . . . . . 5-88 PS_convert_legacy_transform_to_plmxml
UGMAN_InsertItem . . . . . . . . . . . . 5-84 preference . . . . . . . . . . . . . . . . . . . . 19-99
UGMAN_PartType . . . . . . . . . . . . . . 5-85 PS_Duplicate_FindNo_Update
UGMAN_ShowPartType . . . . . . . . . . 5-85 preference . . . . . . . . . . . . . . . . . . . . 19-92
UGMAN_UGPARTNameWRev . . . . . 5-85 PS_Find_Number_Validation
variant_description_column_ preference . . . . . . . . . . . . . . . . . . . . 19-49
width . . . . . . . . . . . . . . . . . . . . 19-56 PS_new_seqno_mode preference . . . . . 19-49
variant_item_column_width . . . . . . 19-56 PS_Reference_Designator_Validation
variant_option_column_width . . . . . 19-56 preference . . . . . . . . . . . . . . . . . . . . 19-91
variant_state_column_width . . . . . . 19-57 PS_replace_with_substructure
variant_value_column_width . . . . . 19-57 preference . . . . . . . . . . . . . . . . . . . . 19-50
variant_values_column_width . . . . . 19-57 PS_structure_change_condition
Vis_InterOptWith preference . . . . . . . . . . . . . . . . . . . . 19-99
ProductViewDataset . . . . . . . . . 19-53 PS_wu_configd_imprecise_only
VISTopLevelRef_relation_ preference . . . . . . . . . . . . . . . . . . . . 19-50
primary . . . . . . . . . . . . . . . . . . 19-53 PSBOMVIEW_object_columns_shown
vrule_reln_column_width . . . . . . . . 19-58 preference . . . . . . . . . . . . . . . . . . . . 10-50
Product structure synchronization . . . 19-99 PSBOMVIEW_object_columns_hidden
Product.Template preference . . . . . . . 20-24 preference . . . . . . . . . . . . . . . . . . . . 10-49
Product.Template.Cloning PSBOMVIEW_object_widths_hidden
ProductBOPAllowedTemplates PSBOMVIEW_object_widths_shown
ProductBOPTemplate preference . . . . 20-67 PSBOMVIEWREVISION_object_columns_
ProductVariant.CREATE RENDERING hidden preference . . . . . . . . . . . . . . 10-51
preference . . . . . . . . . . . . . . . . . . . . 22-42 PSBOMVIEWREVISION_object_columns_
ProductVariant.RENDERING shown preference . . . . . . . . . . . . . . . 10-52
preference . . . . . . . . . . . . . . . . . . . . 22-42 PSBOMVIEWREVISION_object_widths_
ProductVariantIntent. CREATERENDERING hidden preference . . . . . . . . . . . . . . 10-52
preference . . . . . . . . . . . . . . . . . . . . 22-44 PSBOMVIEWREVISION_object_widths_
ProductVariantIntent. RENDERING shown preference . . . . . . . . . . . . . . . 10-53
preference . . . . . . . . . . . . . . . . . . . . 22-43 PSE_check_read_access_for_Rev_Rule_entry
Program preferences preference . . . . . . . . . . . . . . . . . . . . 19-46
TC_Program_Preferred_Items_relation_ PSE_default_view_type preference . . . 19-46
primary . . . . . . . . . . . . . . . . . . . . 6-3 PSE_Display_Pending_Edits
TC_Project_DefaultChildProperties . . . 6-3 preference . . . . . . . . . . . . . . . . . . . . 19-47
TC_Project_PseudoFolder . . . . . . . . . . 6-3 PSE_enable_related_substitutes
TC_set_current_project . . . . . . . . . . . 6-5 preference . . . . . . . . . . . . . . . . . . . . 19-70
Project preferences PSE_expand_on_open preference . . . . 19-47
TC_current_role . . . . . . . . . . . . . . . . . 6-6 PSE_icon_placement preference . . . . . 19-67
TC_show_all_user_projects . . . . . . . . . 6-6 PSE_prompt_for_remote_import
Project propagation rules . . . . . . . . . . . . 6-4 preference . . . . . . . . . . . . . . . . . . . . 19-96

Index
PSE_ROLL_UP_TEMPLATES PseudoFolder.TC_part_quote_rel_
preference . . . . . . . . . . . . . . . . . . . . 19-48 ColumnPreferences preference . . . . . 22-61
PSE_show_option_family_prefix PSEVariantRuleDialogTableSort
PSE_show_option_item_prefix PSEVariantsMode preference . . . . . . . 19-73
preference . . . . . . . . . . . . . . . . . . . . 19-68 PSM_classic_variants_numeric_families
PSEAdditionColorPref preference . . . . 19-70 preference . . . . . . . . . . . . . . . . . . . . 19-84
PSEAllowLegacyVICreation PSM_classic_variants_text_families
PSEAutoPackPref preference . . . . . . . 19-69 PSM_global_option_item_id
PSEAutoViCreateEmptyVI preference . . . . . . . . . . . . . . . . . . . . 19-88
preference . . . . . . . . . . . . . . . . . . . . 19-81 PUBLISH_AlignableSourceTypes
PSEAutoViNamePrefix preference . . . 19-82 preference . . . . . . . . . . . . . . . . . . . . 19-51
PSEAutoViNewItemPopup PUBLISH_AlignableTargetTypes
PSEAutoViStopVICreation PUBLISH_PDF_ERROR_LOG_LOC
ForUnconfiguredModule variable . . . . . . . . . . . . . . . . . . . . . . . 3-7
preference . . . . . . . . . . . . . . . . . . . . 19-81 PUBLISH_PDF_ERRORS variable . . . . . 3-7
PSEBypassVISearch preference . . . . . 19-79 PUBLISH_PDF_INTERVAL variable . . . 3-7
PSEChangedColorPref preference . . . 19-71 PUBLISH_PDF_MAX_JOBS variable . . . 3-8
PSECreateVISameType preference . . . 19-79 PUBLISH_PDF_TIMEOUT variable . . . . 3-8
PSEDisplayTypePref preference . . . . . 19-66 PUBLISH_PDF_VVCP_DEBUG
PSEEnableFilteringUnconfigdDueTo variable . . . . . . . . . . . . . . . . . . . . . . . 3-8
ClassicVariantsPref preference . . . . . 19-75 PUBLISH_PDF_VVCP_DEBUG_LOC
PSEImpreciseColorPref preference . . . 19-69 variable . . . . . . . . . . . . . . . . . . . . . . . 3-8
PSEIsNewVIisLinkedToModule PUBLISH_PDF_VVCP_TIMEOUT
preference . . . . . . . . . . . . . . . . . . . . 19-78 variable . . . . . . . . . . . . . . . . . . . . . . . 3-8
PSEIsNewVILinkedToModule Publishing preferences . . . . . . . . . . . 20-47
preference . . . . . . . . . . . . . . . . . . . . 19-71
PSEoccnotesnocopy preference . . . . . . 19-67 Q
PSEPreciseColorPref preference . . . . . 19-68
PSESavedConfigRelationTypes QR_Cost_Form_Elements
PSESearchColumnsShownPref QRY_<query_name>_SortKeys
PSESearchShownColumnWidthsPref QRY_<query_name>_SortOrder
PSEShowSubstitutesPref QRY_dataset_display_option
PSEshowToolBar preference . . . . . . . 19-48 QRY_search_classification_hierarchy
PSEShowUnconfigdEffPref preference . . . . . . . . . . . . . . . . . . . . 10-55
preference . . . . . . . . . . . . . . . . . . . . 19-74 QRY_search_type_hierarchy
PSEShowUnconfigdVarPref preference . . . . . . . . . . . . . . . . . . . . 10-55
preference . . . . . . . . . . . . . . . . . . . . 19-73 QRYColumnsShownPref preference . . 10-53
PSESubstituteColorPref preference . . 19-69 QS_BBOX_GENERATION_ENABLED
PseudoFolder.ContactInCompany_ preference . . . . . . . . . . . . . . . . . . . 19-133
ColumnPreferences preference . . . . . 22-60 QS_BBOX_GENERATION_FROM_NX_
PseudoFolder.lineitems_ColumnPreferences ENABLED preference . . . . . . . . . . 19-134
preference . . . . . . . . . . . . . . . . . . . . 22-60 QS_MAX_QUERY_EXECUTION_TIME_
PseudoFolder.LocationInCompany_ FOR_BOTTOMUP preference . . . . . 19-134
ColumnPreferences preference . . . . . 22-60 QS_QSEARCH_ENABLED
PseudoFolder.ProvidedFrom_ preference . . . . . . . . . . . . . . . . . . . 19-131
ColumnPreferences preference . . . . . 22-61 QS_SPATIAL_ENABLED
preference . . . . . . . . . . . . . . . . . . . 19-132

Index
QS_TRUSHAPE_GENERATION_ENABLED RDV_authoring_override_user . . . 19-118

preference . . . . . . . . . . . . . . . . . . . 19-132 RDV_auto_functionality . . . . . . . . 19-118
QSEARCH_update_enabled RDV_auto_populate_occ_notes . . . 19-118
preference . . . . . . . . . . . . . . . . . . . 19-132 RDV_build_intent_atth_type . . . . . 19-119
Quality data preferences . . . . . . . . . . 25-12 RDV_copied_occurrence_notes . . . . 19-120
Quick spatial search preferences . . . 19-131 RDV_Create_SCO_WITHOUT_
Quote_DefaultChildProperties APN . . . . . . . . . . . . . . . . . . . . 19-120
preference . . . . . . . . . . . . . . . . . . . . 22-62 RDV_default_Architecture_Breakdown_
RevRule . . . . . . . . . . . . . . . . . 19-120
R RDV_enable_product_lock . . . . . . 19-121
RDV_export_nve . . . . . . . . . . . . . 19-121
RAC_expand_below_batch_size RDV_install_configuration_
preference . . . . . . . . . . . . . . . . . . . . 19-96 rules . . . . . . . . . . . . . . . . . . . 19-122
RDV preferences . . . . . . . . . . . . . . . 19-113 RDV_occurrence_business_rule_
ArchitectureModeler_add_design_business_ check . . . . . . . . . . . . . . . . . . . 19-122
rule_check . . . . . . . . . . . . . . . 19-107 RDV_part_business_rule_check . . . 19-123
ArchitectureModeler_add_design_ RDV_part_occ_note_mappings . . . 19-123
occurrence_business_rule_ RDV_partnumber_validation_
check . . . . . . . . . . . . . . . . . . . 19-107 rule . . . . . . . . . . . . . . . . . . . . 19-123
ArchitectureModeler_locking_retry_ RDV_platformdesigner_assign_bulk_
count . . . . . . . . . . . . . . . . . . . 19-108 variability . . . . . . . . . . . . . . . . 19-113
ArchitectureModeler_multiple_installation_ RDV_product_code_mapping . . . . . 19-124
assemblies_condition . . . . . . . . 19-108 RDV_show_itemid_prefix . . . . . . . 19-125
ArchitectureModeler_part_solution_ RDV_show_lou_prop . . . . . . . . . . 19-125
properties . . . . . . . . . . . . . . . . 19-109 RDV_turn_audit_logging_on . . . . . 19-126
ArchitectureModeler_remove_design_ RDV_uneditable_part_occ_notes . . 19-126
business_rule_check . . . . . . . . 19-109 RDV_usage_attribute_set . . . . . . . 19-127
ArchitectureModeler_remove_ RDV_usage_occurrence_notes . . . . 19-127
design_occurrence_business_rule_ RDV_valid_partnumber_rule . . . . 19-127
check . . . . . . . . . . . . . . . . . . . 19-110 RDV_variant_expression_overlap_
ArchitectureModeler_RemoveDesign_ checking_mode . . . . . . . . . . . . 19-128
Max . . . . . . . . . . . . . . . . . . . . 19-109 RDV_variant_overlays_mode . . . . 19-128
ArchitectureModeler_replace_design_ RDV_variant_overlays_uses_true_
business_rule_check . . . . . . . . 19-110 availability . . . . . . . . . . . . . . . 19-129
ArchitectureModeler_replace_ RDVClearanceProxyServers . . . . . . 19-37
design_occurrence_business_rule_ RDVCreateSCOForClearance . . . . 19-119
check . . . . . . . . . . . . . . . . . . . 19-111 RDVIgnoreErrorConnectReleased
ArchitectureModeler_update_design_ PartsServer . . . . . . . . . . . . . . 19-121
occurrences_business_rule_ RDVReleasedPartsCollector
check . . . . . . . . . . . . . . . . . . . 19-112 Server . . . . . . . . . . . . . . . . . . 19-125
ArchitectureModeler_update_designs_ RDVReleasedPartsProcessAssem
business_rule_check . . . . . . . . 19-111 Type . . . . . . . . . . . . . . . . . . . 19-124
ArchitectureModeler_use_all_installation_ RDV_audit_report_occurrence_attributes
assemblies . . . . . . . . . . . . . . . 19-112 preference . . . . . . . . . . . . . . . . . . . 19-116
EPM_tessellation_servers . . . . . . . 19-114 RDV_audit_report_usage_attributes
EPM_tessellation_target_type . . . . 19-113 preference . . . . . . . . . . . . . . . . . . . 19-115
PortalDesignContextProcess RDV_authoring_override_user
.WorkPartProperties . . . . . . . . 19-114 preference . . . . . . . . . . . . . . . . . . . 19-118
PortalDesignContextProcess.WorkPart RDV_auto_functionality
OrChangeAttachmentTypes . . . 19-115 preference . . . . . . . . . . . . . . . . . . . 19-118
RDV_audit_report_occurrence_ RDV_auto_populate_occ_notes . . . . . 19-118
attributes . . . . . . . . . . . . . . . . 19-116 RDV_build_intent_atth_type
RDV_audit_report_usage_ preference . . . . . . . . . . . . . . . . . . . 19-119
attributes . . . . . . . . . . . . . . . . 19-115

Index
RDV_build_intent_status RDV_variant_overlays_uses_true_availability
preference . . . . . . . . . . . . . . . . . . . . 22-10 preference . . . . . . . . . . . . . . . . . . . 19-129
RDV_copied_occurrence_notes . . . . . 19-120 RDVClearanceProxyServers
RDV_Create_SCO_WITHOUT_APN preference . . . . . . . . . . . . . . . . . . . . 19-37
preference . . . . . . . . . . . . . . . . . . . 19-120 RDVCreateSCOForClearance
RDV_default_Architecture_Breakdown_ preference . . . . . . . . . . . . . . . . . . . 19-119
RevRule preference . . . . . . . . . . . . 19-120 RDVIgnoreErrorConnectReleased PartsServer
RDV_default_option_values_for_tracking_ preference . . . . . . . . . . . . . . . . . . . 19-121
vehicle preference . . . . . . . . . . . . . . 22-11 RDVLoadAppearanceGroupMode
RDV_default_options_for_tracking_vehicle preference . . . . . . . . . . . . . . . . . . . . 19-18
preference . . . . . . . . . . . . . . . . . . . . 22-10 RDVReleasedPartsCollectorServer
RDV_enable_product_lock preference . . . . . . . . . . . . . . . . . . . 19-125
preference . . . . . . . . . . . . . . . . . . . 19-121 RDVReleasedPartsProcessAssemType
RDV_export_nve preference . . . . . . . 19-121 preference . . . . . . . . . . . . . . . . . . . 19-124
RDV_install_configuration_rules RDVThinClientBomlinePropsDisplay
preference . . . . . . . . . . . . . . . . . . . 19-122 preference . . . . . . . . . . . . . . . . . . . 10-126
RDV_occurrence_business_rule_check RDVThinClientUserProductItem . . . 10-126
preference . . . . . . . . . . . . . . . . . . . 19-122 RDVThinClientUserrevisionRule . . . 10-127
RDV_part_business_rule_check Realized_ByRules preference . . . . . . . 22-24
preference . . . . . . . . . . . . . . . . . . . 19-123 RECOVER_TO_UNRELEASED_STATUS
RDV_part_occ_note_mappings preference . . . . . . . . . . . . . . . . . . . . . 9-40
preference . . . . . . . . . . . . . . . . . . . 19-123 RECOVER_TO_VOLUME
RDV_partnumber_validation_rule . . 19-123 preference . . . . . . . . . . . . . . . . . . . . . 9-40
RDV_platformdesigner_assign_bulk_ ReferencersPane_Shown preference . . 10-56
variability preference . . . . . . . . . . . 19-113 Remote workflow preferences . . . . . . . . 5-92
RDV_product_code_mapping IMAN_external_appl_reg_url . . . . . . 5-94
preference . . . . . . . . . . . . . . . . . . . 19-124 TC_external_application_names . . . . 5-94
RDV_product_obsoletion_status TC_external_application_types . . . . . 5-95
preference . . . . . . . . . . . . . . . . . . . . 22-11 TC_external_local_app_guid . . . . . . . 5-92
RDV_QSEARCH_REFINE TC_external_proxiable_objects . . . . . 5-92
preference . . . . . . . . . . . . . . . . . . . 19-134 TC_external_proxiable_objects_
RDV_QSEARCH_REVISION_RULE_NAMES props . . . . . . . . . . . . . . . . . . . . . 5-93
preference . . . . . . . . . . . . . . . . . . . 19-135 TC_external_Requirements_proxy_props_
RDV_QSEARCH_STREAMING_MODE external . . . . . . . . . . . . . . . . . . . 5-94
preference . . . . . . . . . . . . . . . . . . . 19-135 TC_external_Requirements_proxy_props_
RDV_show_itemid_prefix internal . . . . . . . . . . . . . . . . . . . 5-93
preference . . . . . . . . . . . . . . . . . . . 19-125 Report Designer preferences . . . . . . . 15-13
RDV_show_lou_prop preference . . . . 19-125 Enable_ReportDesigner_Reports . . . 15-13
RDV_turn_audit_logging_on ReportDefinition_ColumnPreferences
RDV_uneditable_part_occ_notes ReportDefinition_ColumnWidthPreferences
RDV_usage_attribute_set ReportGenerationDlg_ColumnPreferences
RDV_usage_occurrence_notes ReportGenerationDlg_ColumnWidth
preference . . . . . . . . . . . . . . . . . . . 19-127 Preferences preference . . . . . . . . . . . 10-58
RDV_usage_synchronized_architecture_type Reporting and Analytics preferences,
preference . . . . . . . . . . . . . . . . . . . . 22-12 TC_RA_server_parameters . . . . . . . . 15-13
RDV_valid_partnumber_rule ReportXMLGenerationRules
RDV_variant_expression_overlap_checking_ REQ_object_template_folder
mode preference . . . . . . . . . . . . . . 19-128 preference . . . . . . . . . . . . . . . . . . . . . 15-1
RDV_variant_overlays_mode REQ_spec_template_folder
preference . . . . . . . . . . . . . . . . . . . 19-128 preference . . . . . . . . . . . . . . . . . . . . . 15-1

Index
Requirements Manager preferences . . . 15-1 DATASETTYPE_object_widths_

REQ_object_template_folder . . . . . . . 15-1 shown . . . . . . . . . . . . . . . . . . . 10-13
REQ_spec_template_folder . . . . . . . . 15-1 DatasetTypesPref . . . . . . . . . . . . . 10-13
RESERVATION_object_columns_hidden DRAG_AND_DROP_Default_dataset_
preference . . . . . . . . . . . . . . . . . . . . 10-59 type . . . . . . . . . . . . . . . . . . . . . 10-14
RESERVATION_object_columns_shown DRAG_AND_DROP_file_limit . . . . . 10-14
preference . . . . . . . . . . . . . . . . . . . . 10-59 DRAG_AND_DROP_SWING_dialog_
RESERVATION_object_widths_hidden enable . . . . . . . . . . . . . . . . . . . 10-15
preference . . . . . . . . . . . . . . . . . . . . 10-60 Enable_thumbnails . . . . . . . . . . . . 10-15
RESERVATION_object_widths_shown FLColumnCatIVFSeparatorPref . . . 10-15
preference . . . . . . . . . . . . . . . . . . . . 10-60 FLColumnCatObjSeparatorPref . . . 10-16
Restricted_Vendor_Part_Statuses FOLDER_object_columns_hidden . . 10-16
preference . . . . . . . . . . . . . . . . . . . . 22-62 FOLDER_object_columns_shown . . . 10-17
Restricted_Vendor_Statuses FOLDER_object_widths_hidden . . . 10-17
preference . . . . . . . . . . . . . . . . . . . . 22-62 FOLDER_object_widths_shown . . . . 10-18
ReviewTeamDefinition_ FORM_object_columns_hidden . . . . 10-18
DefaultChildProperties preference . . 10-83 FORM_object_columns_shown . . . . 10-19
Rich client interface preferences FORM_object_widths_hidden . . . . . 10-19
AE_dataset_default_keep_limit . . . . . 10-1 FORM_object_widths_shown . . . . . . 10-20
AI_ignore_ic_flag_setting . . . . . . . . . 10-2 FormTypesPref . . . . . . . . . . . . . . . 10-20
AI_Incremental_Export . . . . . . . . . . 10-2 GROUP_object_columns_hidden . . . 10-20
AI_request_no_dependancy . . . . . . . . 10-2 GROUP_object_columns_shown . . . 10-21
Allow_Copy_As_Revision . . . . . . . . . 10-3 GROUP_object_widths_hidden . . . . 10-21
Attachment_Alias_File . . . . . . . . . . . 10-3 GROUP_object_widths_shown . . . . 10-21
CCCompositionTypesPref . . . . . . . . . 10-4 HiddenPerspectives . . . . . . . . . . . . 10-22
CCObject_default_relation . . . . . . . . 10-4 IDCAttachmentColumnsShown
Change_Search_Default . . . . . . . . . . 10-5 Pref . . . . . . . . . . . . . . . . . . . . . 10-23
copyPasteChunkNumber . . . . . . . . . 10-5 IDCAttachmentColumnWidthsPref . . 10-23
Create_<business_object>_default_ IDCStructureColumnsShownPref . . 10-24
type . . . . . . . . . . . . . . . . . . . . . . 10-5 IDCStructureColumnWidthsPref . . . 10-24
Create_WorkspaceObject_mru_list . . 10-6 IdentifierContextTypeDefault . . . . . 10-25
Create_WorkspaceObject_mru_ IdentifierTypeDefault . . . . . . . . . . . 10-25
max . . . . . . . . . . . . . . . . . . . . . . 10-6 IMAN_3D_snap_shot_relation_
<dataset_name>.CREATE_ primary . . . . . . . . . . . . . . . . . . 10-25
REGISTEREDTO . . . . . . . . . . . . 10-7 IMAN_customization_registry . . . . . 10-26
<dataset_name>.FORM_ IMAN_FLASH_FILE . . . . . . . . . . . 10-26
REGISTEREDTO . . . . . . . . . . . . 10-7 IMANFILE_object_columns_
<dataset_ hidden . . . . . . . . . . . . . . . . . . . 10-26
name>.REGISTEREDTO . . . . . . . 10-8 IMANFILE_object_columns_
<dataset_name>.SUMMARY_ shown . . . . . . . . . . . . . . . . . . . 10-27
REGISTEREDTO . . . . . . . . . . . . 10-9 IMANFILE_object_widths_
DATASET_object_columns_ hidden . . . . . . . . . . . . . . . . . . . 10-27
hidden . . . . . . . . . . . . . . . . . . . 10-10 IMANFILE_object_widths_
DATASET_object_columns_ shown . . . . . . . . . . . . . . . . . . . 10-28
shown . . . . . . . . . . . . . . . . . . . 10-10 IMANTYPE_object_columns_
DATASET_object_widths_hidden . . 10-11 shown . . . . . . . . . . . . . . . . . . . 10-28
DATASET_object_widths_shown . . . 10-11 IMANTYPE_object_widths_
DATASETTYPE_object_columns_ shown . . . . . . . . . . . . . . . . . . . 10-29
hidden . . . . . . . . . . . . . . . . . . . 10-12 IMANVOLUME_object_columns_
DATASETTYPE_object_columns_ hidden . . . . . . . . . . . . . . . . . . . 10-29
shown . . . . . . . . . . . . . . . . . . . 10-12 IMANVOLUME_object_columns_
DATASETTYPE_object_widths_ shown . . . . . . . . . . . . . . . . . . . 10-30
hidden . . . . . . . . . . . . . . . . . . . 10-12 IMANVOLUME_object_widths_
hidden . . . . . . . . . . . . . . . . . . . 10-30

Index
IMANVOLUME_object_widths_ PIE_allow_import_with_different_
shown . . . . . . . . . . . . . . . . . . . 10-31 sml . . . . . . . . . . . . . . . . . . . . . 18-68
<Item type>_rev_display_all . . . . . . 10-42 PIE_Extra_Error_Info_to_Xml . . . . 18-68
<Item type>_rev_display_order . . . . 10-42 PIE_IMF_FOR_CAD . . . . . . . . . . . 18-69
<Item type>_rev_display_rule . . . . . 10-43 PIE_transfermode_languages . . . . . 18-69
ITEM_first_rev_id . . . . . . . . . . . . . 10-31 PLMXML_continue_on_error . . . . . 18-70
ITEM_id_postfix . . . . . . . . . . . . . . 10-32 PLMXML_export_packed_bom_<transfer-
ITEM_id_prefix . . . . . . . . . . . . . . . 10-32 mode-name> . . . . . . . . . . . . . . . 18-70
ITEM_object_columns_hidden . . . . . 10-33 PLMXML_import_default_
ITEM_object_columns_shown . . . . . 10-33 password . . . . . . . . . . . . . . . . . 18-70
ITEM_object_widths_hidden . . . . . . 10-34 PLMXML_log_file_content . . . . . . . 18-71
ITEM_object_widths_shown . . . . . . 10-34 PLMXML_overwrite_objects_on_
Item_shown_relations . . . . . . . . . . 10-41 import . . . . . . . . . . . . . . . . . . . 18-72
ITEM_smart_baseline . . . . . . . . . . 10-42 PLMXML_put_objects_in_newstuff_on_
Item.FilterCriteria . . . . . . . . . . . . . 10-31 import . . . . . . . . . . . . . . . . . . . 18-72
Item.SUMMARYRENDERING2007 . . 10-35 PLMXML_use_pre_plm_
itemrev1_itemrev2_default_ appname . . . . . . . . . . . . . . . . . 18-73
relation . . . . . . . . . . . . . . . . . . 10-36 PSBOMVIEW_object_columns_
ItemRevision_default_relation . . . . 10-37 hidden . . . . . . . . . . . . . . . . . . . 10-49
ITEMREVISION_object_columns_ PSBOMVIEW_object_columns_
hidden . . . . . . . . . . . . . . . . . . . 10-37 shown . . . . . . . . . . . . . . . . . . . 10-50
ITEMREVISION_object_columns_ PSBOMVIEW_object_widths_
shown . . . . . . . . . . . . . . . . . . . 10-38 hidden . . . . . . . . . . . . . . . . . . . 10-50
ITEMREVISION_object_widths_ PSBOMVIEW_object_widths_
hidden . . . . . . . . . . . . . . . . . . . 10-38 shown . . . . . . . . . . . . . . . . . . . 10-51
ITEMREVISION_object_widths_ PSBOMVIEWREVISION_object_columns_
shown . . . . . . . . . . . . . . . . . . . 10-39 shown . . . . . . . . . . . . . . . . . . . 10-52
ItemRevision_shown_relations . . . . 10-39 PSBOMVIEWREVISION_object_columns_
ItemRevision_thumbnail_ hidden . . . . . . . . . . . . . . . . . . . 10-51
references . . . . . . . . . . . . . . . . . 10-41 PSBOMVIEWREVISION_object_widths_
ItemRevision_thumbnail_ hidden . . . . . . . . . . . . . . . . . . . 10-52
relations . . . . . . . . . . . . . . . . . . 10-40 PSBOMVIEWREVISION_object_widths_
ItemRevision.RENDERING . . . . . . 10-35 shown . . . . . . . . . . . . . . . . . . . 10-53
ItemRevision.SUMMARYRENDERING . . 10-36 QRY_<query_name>_SortKeys . . . . 10-54
JTTreeTableColumnsShownPref . . . 10-44 QRY_<query_name>_SortOrder . . . 10-54
JTTreeTableShownColumn QRY_dataset_display_option . . . . . . 10-54
WidthsPref . . . . . . . . . . . . . . . . 10-44 QRY_search_classification_
LOV_hide_desc . . . . . . . . . . . . . . . 10-45 hierarchy . . . . . . . . . . . . . . . . . 10-55
MECollaborationContext_default_ QRY_search_type_hierarchy . . . . . . 10-55
relation . . . . . . . . . . . . . . . . . . 10-45 QRYColumnsShownPref . . . . . . . . . 10-53
MEOPRevision_shown_relations . . . 10-46 ReferencersPane_Shown . . . . . . . . . 10-56
MEProcessRevision_shown_ ReportDefinition_
relations . . . . . . . . . . . . . . . . . . 10-46 ColumnPreferences . . . . . . . . . . 10-56
MySearchHistory_Limit . . . . . . . . . 10-47 ReportDefinition_ColumnWidth
OpenAfterCreatePref . . . . . . . . . . . 10-47 Preferences . . . . . . . . . . . . . . . . 10-57
PERSON_object_columns_hidden . . 10-47 ReportGenerationDlg_Column
PERSON_object_columns_shown . . . 10-48 WidthPreferences . . . . . . . . . . . 10-58
PERSON_object_widths_hidden . . . 10-48 ReportGenerationDlg_
PERSON_object_widths_shown . . . . 10-49 ColumnPreferences . . . . . . . . . . 10-58
PIE_<transfer_mode_name>_process_in_ RESERVATION_object_columns_
chunks . . . . . . . . . . . . . . . . . . . 18-66 hidden . . . . . . . . . . . . . . . . . . . 10-59
PIE_<transfer_mode_name>_unload_ RESERVATION_object_columns_
objects . . . . . . . . . . . . . . . . . . . 18-67 shown . . . . . . . . . . . . . . . . . . . 10-59

Index
RESERVATION_object_widths_ TC_VALIDATION_run_validation_hidden_
hidden . . . . . . . . . . . . . . . . . . . 10-60 agents . . . . . . . . . . . . . . . . . . . 5-119
RESERVATION_object_widths_ TC_VALIDATION_TIMESTAMP_
shown . . . . . . . . . . . . . . . . . . . 10-60 NREFS . . . . . . . . . . . . . . . . . . 5-120
Select IR . . . . . . . . . . . . . . . . . . . . 10-61 TC_VALIDATION_USE_
Selection Criteria . . . . . . . . . . . . . . 10-61 PLMXML . . . . . . . . . . . . . . . . . 5-120
Structure_Alias_File . . . . . . . . . . . 10-62 TC_wc_setting_modifiable_
TC_<datasettype>_Tool . . . . . . . . . 10-69 default . . . . . . . . . . . . . . . . . . . 10-77
TC_AE_<datasettype>_Default_View_ TC_wc_show_all . . . . . . . . . . . . . . 10-78
Tool . . . . . . . . . . . . . . . . . . . . . 10-62 TCENG_wc_allow_subgroup_
TC_ALLOW_ADHOC_ default . . . . . . . . . . . . . . . . . . . 10-77
VALIDATIONS . . . . . . . . . . . . . 5-116 TCViewMarkupApplicationPref . . . . 10-76
TC_Allow_Longer_ID_Name . . . . . . 10-63 TOOL_object_columns_hidden . . . . 10-78
TC_Auto_Checkout . . . . . . . . . . . . 10-63 TOOL_object_columns_shown . . . . . 10-79
TC_auto_login . . . . . . . . . . . . . . . . 10-63 TOOL_object_widths_hidden . . . . . 10-79
TC_check_out_dir . . . . . . . . . . . . . 10-64 TOOL_object_widths_shown . . . . . . 10-80
TC_checkout_and_export . . . . . . . . 10-64 Tracelink_deepcopy_on_Revise . . . . 10-80
TC_control_wildcard . . . . . . . . . . . 10-64 Tracelink_deepcopy_on_SaveAs . . . . 10-80
TC_control_wildcard_exception . . . . 10-65 treeDisplayOrder . . . . . . . . . . . . . . 10-81
TC_days_non_login_timeout . . . . . . 10-65 <Type_Name>_
TC_DISABLE_FLASH . . . . . . . . . . 10-66 DefaultChildProperties . . . . . . . 10-82
TC_display_group_names_limit . . . . 10-66 <type_
TC_display_real_prop_names . . . . . 10-67 name>.CREATERENDERING . . 10-82
TC_display_thumbnail_in_UI . . . . . 10-67 <type_
TC_export_child_groups . . . . . . . . . 18-74 name>.FORMRENDERING . . . . 10-86
TC_export_parent_groups . . . . . . . . 18-74 <type_
TC_Graph_Node_Thumbnail_ name>.SUMMARYRENDERING . . 10-87
Shown . . . . . . . . . . . . . . . . . . . 10-67 type_name.RENDERING . . . . . . . . 10-86
TC_GROUP_PFILE . . . . . . . . . . . . 10-68 <Type>_PseudoFolder . . . . . . . . . . 10-81
TC_ignore_case_on_search . . . . . . . 10-68 USER_object_columns_hidden . . . . 10-88
TC_inbox_interval . . . . . . . . . . . . . 10-69 USER_object_columns_shown . . . . . 10-88
TC_markup_named_ref . . . . . . . . . 10-70 USER_object_widths_hidden . . . . . . 10-89
TC_max_number_of_retries . . . . . . 10-70 USER_object_widths_shown . . . . . . 10-89
TC_name_delimiter . . . . . . . . . . . . 10-71 VALIDATION_APPLICATIONS . . . 5-124
TC_name_sequence . . . . . . . . . . . . 10-71 ValidationMasterForm
TC_pattern_match_style . . . . . . . . . 10-72 ColumnPreferences . . . . . . . . . . 5-124
TC_QRY_display_latest_dataset_ ValidationMasterFormColumn
only . . . . . . . . . . . . . . . . . . . . . 10-72 WidthPreferences . . . . . . . . . . . 5-125
TC_QRY_search_by_rev_rule . . . . . 10-72 WHERE_REFERENCED_RELATIONS_
TC_remove_file_on_check_in . . . . . . 10-73 FILTER . . . . . . . . . . . . . . . . . . 10-89
TC_retry_time . . . . . . . . . . . . . . . . 10-73 Word_12_installed . . . . . . . . . . . . . 10-90
TC_ROLE_PFILE . . . . . . . . . . . . . 10-74 WORKSPACEOBJECT_object_ columns_
TC_show_checkedout_icon . . . . . . . 10-74 hidden . . . . . . . . . . . . . . . . . . . 10-90
TC_suppress_Edit_Latest_Menu . . . 10-74 WORKSPACEOBJECT_object_ columns_
TC_suppress_inactive_group_ shown . . . . . . . . . . . . . . . . . . . 10-91
members . . . . . . . . . . . . . . . . . 10-75 WORKSPACEOBJECT_object_ widths_
TC_Thumbnail_Tooltip_ hidden . . . . . . . . . . . . . . . . . . . 10-91
Properties . . . . . . . . . . . . . . . . . 10-75 WORKSPACEOBJECT_object_ widths_
TC_user_delimiters . . . . . . . . . . . . 10-76 shown . . . . . . . . . . . . . . . . . . . 10-92
TC_USER_PFILE . . . . . . . . . . . . . 10-75 WS_expand_on_paste . . . . . . . . . . . 10-94
TC_VALIDATION_FILE_TYPES . . 5-117 WS_icon_placement . . . . . . . . . . . . 10-92
TC_Validation_relation_primary . . . 5-118 WSColumnsHiddenPref . . . . . . . . . 10-93
TC_VALIDATION_RESULT_ALLOW_ WSColumnsShownPref . . . . . . . . . . 10-93
REPLICA_OBJECT . . . . . . . . . . 5-118 WSDisplayTypePref . . . . . . . . . . . . 10-94

Index
WSHiddenColumnWidthsPref . . . . . 10-94 scheduling_graph_histogram_single_

WsoFolderSavePref . . . . . . . . . . . . 10-95 color . . . . . . . . . . . . . . . . . . . . . . 15-6
WsoInsertNoSelectionsPref . . . . . . . 10-95 scheduling_graph_reference_
WsoInsertSelectionsPref . . . . . . . . . 10-96 calendar . . . . . . . . . . . . . . . . . . . 15-7
WSOM_find_editUserList . . . . . . . . 10-96 scheduling_graph_task_legend . . . . . 15-7
WSOM_find_list_separator . . . . . . . 10-97 scheduling_graph_view . . . . . . . . . . . 15-7
WSOM_find_set_search_limit . . . . . 10-97 SiteTimeZone . . . . . . . . . . . . . . . . . 15-8
WSOM_find_set_total_limit . . . . . . 10-97 SM_CriticalPath_Color . . . . . . . . . . . 15-8
WSOM_only_edit_effectivity_in_ SM_EVM_Calc_Labels . . . . . . . . . . . 15-9
ecm . . . . . . . . . . . . . . . . . . . . . 10-98 SM_EVM_Calc_Preference . . . . . . . . 15-9
WSShownColumnWidthsPref . . . . . 10-98 SM_EVM_Export_Units . . . . . . . . . . 15-9
Rich Client interface preferences SM_EVM_Work_Complete . . . . . . . 15-10
PLMXML_put_pie_log_in_syslog . . . 18-73 SM_SCHEDULING_ENGINE_
PLMXML_sdk_threshold . . . . . . . . 18-73 DATE . . . . . . . . . . . . . . . . . . . . 15-10
Rich client preferences . . . . . . . . . . . . . 10-1 SM_TIMESHEET_APPROVE_
RICH_CLIENT_MARKER_ID WORKFLOW . . . . . . . . . . . . . . 15-10
preference . . . . . . . . . . . . . . . . . . . . 11-14 SM_TIMESHEET_REVISE_
Role object mapping preferences . . . . . 5-104 WORKFLOW . . . . . . . . . . . . . . 15-11
LDAP_role_attr_mapping . . . . . . . . 5-105 SM_View_CriticalPath . . . . . . . . . . 15-11
LDAP_role_object_class . . . . . . . . . 5-104 SM_WBS_FORMAT_PREF . . . . . . . 15-12
LDAP_role_query_filter . . . . . . . . . 5-104 SM_WBS_INITIAL_PREF . . . . . . . 15-12
Role-based preferences . . . . . . . . . . . 18-20 scheduling_graph_dataSource
TC_always_exclude_dataset_files_on_ preference . . . . . . . . . . . . . . . . . . . . . 15-3
export . . . . . . . . . . . . . . . . . . . 18-22 scheduling_graph_dataSource_filter
TC_bom_level_export . . . . . . . . . . . 18-21 preference . . . . . . . . . . . . . . . . . . . . . 15-4
TC_dataset_vers_export . . . . . . . . . 18-20 scheduling_graph_date_format
TC_modified_only_export . . . . . . . . 18-21 preference . . . . . . . . . . . . . . . . . . . . . 15-4
TC_ownership_export . . . . . . . . . . . 18-20 scheduling_graph_date_interval
TC_relation_export_hidden . . . . . . . 18-22 preference . . . . . . . . . . . . . . . . . . . . . 15-4
ROLL_UP_QUANTITY_FLAG scheduling_graph_domain_label_vertical
ROSE variable . . . . . . . . . . . . . . . . . . . 3-8 scheduling_graph_font_name
ROSE_DB variable . . . . . . . . . . . . . . . . 3-8 preference . . . . . . . . . . . . . . . . . . . . . 15-5
Running environment variable script scheduling_graph_font_size
files . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 preference . . . . . . . . . . . . . . . . . . . . . 15-6
scheduling_graph_font_style
preference . . . . . . . . . . . . . . . . . . . . . 15-6
S scheduling_graph_histogram_single_color
preference . . . . . . . . . . . . . . . . . . . . . 15-6
Schedule Manager preferences . . . . . . . 15-2 scheduling_graph_reference_calendar
cost_default_currency . . . . . . . . . . . . 15-2 preference . . . . . . . . . . . . . . . . . . . . . 15-7
Default_Base_Calendar_ scheduling_graph_task_legend
Preference . . . . . . . . . . . . . . . . . 15-3 preference . . . . . . . . . . . . . . . . . . . . . 15-7
DefaultActualToSystemDate . . . . . . . 15-2 scheduling_graph_view preference . . . . 15-7
scheduling_graph_dataSource . . . . . . 15-3 SCM_CheckIn_Identical_Version
scheduling_graph_dataSource_ preference . . . . . . . . . . . . . . . . . . . . 23-54
filter . . . . . . . . . . . . . . . . . . . . . . 15-4 SCM_ClearCase_Server preference . . . 23-53
scheduling_graph_date_format . . . . . 15-4 SCM_ClearCase_UNCO_Keep_Version
scheduling_graph_date_interval . . . . 15-4 preference . . . . . . . . . . . . . . . . . . . . 23-54
scheduling_graph_domain_label_ SCM_notification_history . . . . . . . . . . . 9-22
vertical . . . . . . . . . . . . . . . . . . . . 15-5 SCM_notification_WorkspaceObject_
scheduling_graph_font_name . . . . . . 15-5 props . . . . . . . . . . . . . . . . . . . . . . . . 9-22
scheduling_graph_font_size . . . . . . . 15-6 Script files running . . . . . . . . . . . . . . . . 1-5
scheduling_graph_font_style . . . . . . . 15-6 Scripts

Index
tc_cshvars . . . . . . . . . . . . . . . . . . . . . 1-4 ServiceDiscrepancy.ENABLE_

tc_profilevars . . . . . . . . . . . . . . . . . . . 1-4 PROPERTIES_EDIT . . . . . . . . . 22-93
search_automatic_wildcard ServiceDiscrepancy.RENDERING . . 22-94
preference . . . . . . . . . . . . . . . . . . . . . 5-51 ServiceEvent_
SecondaryVMUDatasets preference . . . 21-7 DefaultChildProperties . . . . . . . 22-95
Security Services preferences . . . . . . . . 5-95 ServiceEvent.
Select IR preference . . . . . . . . . . . . . 10-61 MROCREATERENDERING . . . 22-96
Selection Criteria preference . . . . . . . 10-61 ServiceEvent.
SerialNumberCharsForPhysicalPartIdPref SUMMARYRENDERING . . . . . 22-96
preference . . . . . . . . . . . . . . . . . . . . 22-77 ServiceEvent.ENABLE_PROPERTIES_
SerialNumberGenerator_ EDIT . . . . . . . . . . . . . . . . . . . . 22-95
DefaultChildProperties preference . . 22-78 ServiceEvent.RENDERING . . . . . . 22-96
SerialNumberGenerator.SUMMARY ServiceGroup.
RENDERING preference . . . . . . . . . 22-78 MROCREATERENDERING . . . 22-97
Service Event Management ServiceGroup.
preferences . . . . . . . . . . . . . . . . . . . 22-87 SUMMARYRENDERING . . . . . 22-97
ActivityCost. ServiceGroup.ENABLE_PROPERTIES_
SUMMARYRENDERING . . . . . 22-88 EDIT . . . . . . . . . . . . . . . . . . . . 22-96
ActivityCost.RENDERING . . . . . . . 22-88 ServiceGroup.RENDERING . . . . . . 22-97
ActivityEntryValue. TransactionElement_
MROCREATERENDERING . . . 22-88 DefaultChildProperties . . . . . . . 22-98
ActivityEntryValue. TransactionElement_Document_default_
SUMMARYRENDERING . . . . . 22-89 relation . . . . . . . . . . . . . . . . . . 22-99
ActivityEntryValue.RENDERING . . 22-89 TransactionElement_DocumentRevision_
FaultCode. default_relation . . . . . . . . . . . . 22-99
MROCREATERENDERING . . . 22-89 TransactionElement_PhysicalElement_
FaultCode. default_relation . . . . . . . . . . . . 22-99
SUMMARYRENDERING . . . . . 22-90 TransactionElement_
FaultCode.RENDERING . . . . . . . . 22-89 PhysicalElementRevision_default_
MRODefaultLogBook . . . . . . . . . . . 22-90 relation . . . . . . . . . . . . . . . . . . 22-99
PartMovement_ TransactionElement.COLUMNS_
DefaultChildProperties . . . . . . . 22-90 SHOW . . . . . . . . . . . . . . . . . . . 22-98
PartMovement. TransactionElement.COLUMNS_
MROCREATERENDERING . . . 22-91 WIDTH . . . . . . . . . . . . . . . . . . 22-98
PartMovement. Service Manager preferences . . . . . . . 22-81
SUMMARYRENDERING . . . . . 22-92 Service Request Manager
PartMovement.ENABLE_PROPERTIES_ preferences . . . . . . . . . . . . . . . . . . 22-100
EDIT . . . . . . . . . . . . . . . . . . . . 22-91 ActivityCost.MROCREATE
PartMovement.RENDERING . . . . . 22-91 RENDERING . . . . . . . . . . . . . 22-100
ServiceAction. ActivityCost_SRP0RqstActivityRevision.
SUMMARYRENDERING . . . . . 22-92 MROCREATERENDERING . . 22-100
ServiceAction.RENDERING . . . . . . 22-92 ActivityCost_SRP0ServiceOffering.
ServiceDiscrepancy_ MROCREATE RENDERING . . 22-101
DefaultChildProperties . . . . . . . 22-92 ActivityCost_SRP0ServiceRequest.
ServiceDiscrepancy_FaultCode_default_ MROCREATE RENDERING . . 22-101
relation . . . . . . . . . . . . . . . . . . 22-93 CM_SRP0DgSrvRequestRevision_
ServiceDiscrepancy. displayed_pseudofolders . . . . . . 22-101
MROCREATERENDERING . . . 22-93 CM_SRP0PrSrvRequestRevision_
ServiceDiscrepancy_ServiceEvent_default_ displayed_pseudofolders . . . . . . 22-102
relation . . . . . . . . . . . . . . . . . . 22-94 CM_SRP0RqstActivityRevision_displayed_
ServiceDiscrepancy_ServiceGroup_default_ pseudofolders . . . . . . . . . . . . . 22-102
relation . . . . . . . . . . . . . . . . . . 22-94 CompanyContact.MROCREATE
ServiceDiscrepancy. RENDERING . . . . . . . . . . . . . 22-103
SUMMARYRENDERING . . . . . 22-95

Index
CompanyLocation.MROCREATE SRP0ServiceDiscrepancy.
RENDERING . . . . . . . . . . . . . 22-103 MROCREATERENDERING . . 22-111
SR_CHANGE_HOME_SITE_ SRP0ServiceOffering_ActivityCost_default_
PREFERENCE . . . . . . . . . . . . 22-103 relation . . . . . . . . . . . . . . . . . 22-112
SRP0DgSrvRequest. SRP0ServiceOffering_
SUMMARYRENDERING . . . . 22-104 DefaultChildProperties . . . . . . 22-113
SRP0DgSrvRequestRevision_ SRP0ServiceOffering_HWSOStructure_
DefaultChildProperties . . . . . . 22-105 default_relation . . . . . . . . . . . 22-113
SRP0DgSrvRequestRevision. SRP0ServiceOffering.
MROCREATERENDERING . . 22-104 MROCREATERENDERING . . 22-112
SRP0DgSrvRequestRevision. SRP0ServiceOffering.
RENDERING . . . . . . . . . . . . . 22-104 RENDERING . . . . . . . . . . . . . 22-112
SRP0DgSrvRequestRevision. SRP0ServiceOffering_SRP0ServiceCatalog_
SUMMARYRENDERING . . . . 22-105 default_relation . . . . . . . . . . . 22-113
SRP0PrSrvRequest. SRP0ServiceOffering.
SUMMARYRENDERING . . . . 22-105 SUMMARYRENDERING . . . . 22-112
SRP0PrSrvRequestRevision_ SRP0ServiceOfferingTable_
DefaultChildProperties . . . . . . 22-106 ColumnPreferences . . . . . . . . . 22-114
SRP0PrSrvRequestRevision. SRP0StatusViewColumns
MROCREATERENDERING . . 22-106 ShownPref . . . . . . . . . . . . . . . 22-114
SRP0PrSrvRequestRevision. ServiceAction.SUMMARYRENDERING
RENDERING . . . . . . . . . . . . . 22-106 preference . . . . . . . . . . . . . . . . . . . . 22-92
SRP0PrSrvRequestRevision. ServiceAction.RENDERING
SUMMARYRENDERING . . . . 22-106 preference . . . . . . . . . . . . . . . . . . . . 22-92
SRP0RequalifyRqstActivityRevision. ServiceDiscrepancy_DefaultChildProperties
MROCREATERENDERING . . 22-107 preference . . . . . . . . . . . . . . . . . . . . 22-92
SRP0RqstActivity. ServiceDiscrepancy_FaultCode_default_
SUMMARYRENDERING . . . . 22-107 relation preference . . . . . . . . . . . . . . 22-93
SRP0RqstActivityRevision_ ServiceDiscrepancy.
DefaultChildProperties . . . . . . 22-108 MROCREATERENDERING
SRP0RqstActivityRevision.MROCREATE preference . . . . . . . . . . . . . . . . . . . . 22-93
RENDERING . . . . . . . . . . . . . 22-107 ServiceDiscrepancy_ServiceEvent_default_
SRP0RqstActivityRevision. relation preference . . . . . . . . . . . . . . 22-94
RENDERING . . . . . . . . . . . . . 22-108 ServiceDiscrepancy_ServiceGroup_default_
SRP0RqstActivityRevision_ relation preference . . . . . . . . . . . . . . 22-94
ServiceDiscrepancy_default_ ServiceDiscrepancy.SUMMARYRENDERING
relation . . . . . . . . . . . . . . . . . 22-109 preference . . . . . . . . . . . . . . . . . . . . 22-95
SRP0RqstActivityRevision. ServiceDiscrepancy.ENABLE_PROPERTIES_
SUMMARYRENDERING . . . . 22-108 EDIT preference . . . . . . . . . . . . . . . 22-93
SRP0ServiceCatalog_ ServiceDiscrepancy.RENDERING
DefaultChildProperties . . . . . . 22-110 preference . . . . . . . . . . . . . . . . . . . . 22-94
SRP0ServiceCatalog_HWSOStructure_ ServiceEvent_DefaultChildProperties
default_relation . . . . . . . . . . . 22-110 preference . . . . . . . . . . . . . . . . . . . . 22-95
SRP0ServiceCatalog. ServiceEvent.MROCREATERENDERING
MROCREATERENDERING . . 22-109 preference . . . . . . . . . . . . . . . . . . . . 22-96
SRP0ServiceCatalog_ ServiceEvent.SUMMARYRENDERING
PseudoFolder . . . . . . . . . . . . . 22-111 preference . . . . . . . . . . . . . . . . . . . . 22-96
SRP0ServiceCatalog. ServiceEvent.ENABLE_PROPERTIES_EDIT
RENDERING . . . . . . . . . . . . . 22-109 preference . . . . . . . . . . . . . . . . . . . . 22-95
SRP0ServiceCatalog_SRP0ProductCatalog_ ServiceEvent.RENDERING
default_relation . . . . . . . . . . . 22-111 preference . . . . . . . . . . . . . . . . . . . . 22-96
SRP0ServiceCatalog. ServiceGroup.MROCREATERENDERING
SUMMARYRENDERING . . . . 22-110 preference . . . . . . . . . . . . . . . . . . . . 22-97

Index
ServiceGroup.SUMMARYRENDERING SM_WBS_INITIAL_PREF
ServiceGroup.ENABLE_PROPERTIES_EDIT SOA_MaxOperationBracket InactiveTime
ServiceGroup.RENDERING SOA_MaxOperationBracketTime
ServiceManagerAssetGroup SOACAD_checkout_required
ColumnsShownPref preference . . . . . 22-85 preference . . . . . . . . . . . . . . . . . . . . . 5-22
ServiceManagerAssetGroup Solution-specific preferences . . . . . . . . 22-1
ColumnWidthsPref preference . . . . . 22-85 ActivityCost.MROCREATE
ServiceManagerColumnsShownPref RENDERING . . . . . . . . . . . . . 22-100
preference . . . . . . . . . . . . . . . . . . . . 22-86 ActivityCost_SRP0RqstActivityRevision.
ServiceManagerPhysicalLocation MROCREATERENDERING . . 22-100
ColumnsShownPref preference . . . . . 22-87 ActivityCost_SRP0ServiceOffering.
ServiceManagerPhysicalLocation MROCREATE RENDERING . . 22-101
ColumnsWidthsPref preference . . . . . 22-87 ActivityCost_SRP0ServiceRequest.
ServiceManagerShownColumnWidthsPref MROCREATE RENDERING . . 22-101
preference . . . . . . . . . . . . . . . . . . . . 22-86 AdditionalAsBuiltAccCheck
Setting environment variables for Properties . . . . . . . . . . . . . . . . . 22-81
logging . . . . . . . . . . . . . . . . . . . . . . . . 2-1 AdditionalAsBuiltCompare
SHLIB_PATH variable . . . . . . . . . . . . . 3-9 Properties . . . . . . . . . . . . . . . . . 22-80
ShowModuleIcons preference . . . . . . . 19-80 AdditionalAsMaintainedCompare
ShowViIcons preference . . . . . . . . . . . 19-80 Properties . . . . . . . . . . . . . . . . . 22-82
SIG_asystem_source_rules ADS_Lists_DrawingRevisions_relation_
preference . . . . . . . . . . . . . . . . . . . . 22-48 primary preference . . . . . . . . . . . 22-1
SIG_asystem_target_rules ADS_Lists_PartRevisions_relation_
preference . . . . . . . . . . . . . . . . . . . . 22-49 primary . . . . . . . . . . . . . . . . . . . 22-2
SIG_asystem_transmitter_rules ADS_Lists_Parts_relation_
preference . . . . . . . . . . . . . . . . . . . . 22-49 primary . . . . . . . . . . . . . . . . . . . 22-2
SIG_pvariable_rules preference . . . . . 22-50 ADSDrawing_Revision_PseudoFolder
SIG_redundant_rules preference . . . . 22-50 preference . . . . . . . . . . . . . . . . . 22-1
SIGNOFF_adhoc_quorum preference . . 11-3 ADSTechDocument Revision_
SIGNOFF_fill_in_reviewers DefaultChildProperties . . . . . . . . 22-3
preference . . . . . . . . . . . . . . . . . . . . . 11-1 ADSTechDocument Revision_
SIGNOFF_required_group_and_role PseudoFolder . . . . . . . . . . . . . . . 22-3
preference . . . . . . . . . . . . . . . . . . . . . 11-1 APN_absolute_path_name_
SiteTimeZone preference . . . . . . . . . . . 15-8 separator . . . . . . . . . . . . . . . . . 22-24
SM_CriticalPath_Color preference . . . . 15-8 AsBuiltManagerColumns
SM_EVM_Calc_Labels preference . . . . 15-9 ShownPref . . . . . . . . . . . . . . . . 22-79
SM_EVM_Calc_Preference AsBuiltManagerShownColumn
preference . . . . . . . . . . . . . . . . . . . . . 15-9 WidthsPref . . . . . . . . . . . . . . . . 22-79
SM_EVM_Export_Units preference . . . 15-9 Ccd0ColumnPreference . . . . . . . . . 22-44
SM_EVM_Work_Complete CCDM_grp_rev_val . . . . . . . . . . . . 22-45
preference . . . . . . . . . . . . . . . . . . . . 15-10 CM_SRP0DgSrvRequestRevision_
SM_SCHEDULING_ENGINE_DATE displayed_pseudofolders . . . . . . 22-101
preference . . . . . . . . . . . . . . . . . . . . 15-10 CM_SRP0PrSrvRequestRevision_
SM_TIMESHEET_APPROVE_WORKFLOW displayed_pseudofolders . . . . . . 22-102
preference . . . . . . . . . . . . . . . . . . . . 15-10 CM_SRP0RqstActivityRevision_displayed_
SM_TIMESHEET_REVISE_WORKFLOW pseudofolders . . . . . . . . . . . . . 22-102
preference . . . . . . . . . . . . . . . . . . . . 15-11 CompanyContact.MROCREATE
SM_View_CriticalPath preference . . . 15-11 RENDERING . . . . . . . . . . . . . 22-103
SM_WBS_FORMAT_PREF CompanyLocation.MROCREATE
preference . . . . . . . . . . . . . . . . . . . . 15-12 RENDERING . . . . . . . . . . . . . 22-103
Connected_ToRules . . . . . . . . . . . . 22-22

Index
datasetParmDef.REGISTEREDTO . . 22-41 ESM_Processor_architecture_

datasetParmDefBCDRevision. attr . . . . . . . . . . . . . . . . . . . . . 22-30
REGISTEREDTO . . . . . . . . . . . 22-38 ESM_Processor_byteOrder_attr . . . 22-30
datasetParmDefBitDefRevision. ESM_processor_direct_child_of_
REGISTEREDTO . . . . . . . . . . . 22-39 hardware . . . . . . . . . . . . . . . . . 22-28
datasetParmDefBoolRevision. ESM_Processor_is_gateway_attr . . . 22-28
REGISTEREDTO . . . . . . . . . . . 22-35 ESM_Processor_linked_attr . . . . . . 22-29
datasetParmDefDateRevision. ESM_Processor_memoryType_
REGISTEREDTO . . . . . . . . . . . 22-36 attr . . . . . . . . . . . . . . . . . . . . . 22-29
datasetParmDefDblRevision. ESM_Processor_programmableInService_
REGISTEREDTO . . . . . . . . . . . 22-34 attr . . . . . . . . . . . . . . . . . . . . . 22-29
datasetParmDefHexRevision. ESM_Processor_Type . . . . . . . . . . . 22-27
REGISTEREDTO . . . . . . . . . . . 22-37 ESM_Software_Categories . . . . . . . 22-26
datasetParmDefIntRevision. ESM_SW_Compatibility_Report_Excel_
REGISTEREDTO . . . . . . . . . . . 22-33 StyleSheet_Dataset . . . . . . . . . . 22-32
datasetParmDefSEDRevision. ESM_SW_Compatibility_Report_HTML_
REGISTEREDTO . . . . . . . . . . . 22-37 StyleSheet_Dataset . . . . . . . . . . 22-32
datasetParmDefStrRevision. ESM_SW_Compatibility_Report_
REGISTEREDTO . . . . . . . . . . . 22-35 TransferMode . . . . . . . . . . . . . . 22-31
datasetParmGrpDef. GDE_exclude_list . . . . . . . . . . . . . . 22-25
REGISTEREDTO . . . . . . . . . . . 22-40 GDELink_default_type . . . . . . . . . . 22-25
datasetParmGrpDefRevision. GMO_enable_new_pnum_match_
REGISTEREDTO . . . . . . . . . . . 22-41 criteria . . . . . . . . . . . . . . . . . . . 22-12
datasetParmGrpValRevision. GMO_GRP_browser_default . . . . . . . 22-7
REGISTEREDTO . . . . . . . . . . . 22-39 GMO_GRP_edit_prop_mapping_
datasetProductVariant. default . . . . . . . . . . . . . . . . . . . . 22-8
REGISTEREDTO . . . . . . . . . . . 22-42 GMO_GRP_hostname_default . . . . . . 22-7
datasetProductVariantCreate. GMO_GRP_port . . . . . . . . . . . . . . . . 22-7
REGISTEREDTO . . . . . . . . . . . 22-43 GMO_GRP_req_edit_props_
datasetProductVariantIntent. default . . . . . . . . . . . . . . . . . . . . 22-8
REGISTEREDTO . . . . . . . . . . . 22-43 GMO_GRP_req_ir_types . . . . . . . . . . 22-8
datasetProductVariantIntentCreate. GMO_GRP_show . . . . . . . . . . . . . . . 22-6
REGISTEREDTO . . . . . . . . . . . 22-44 GMO_MATFORM_
DefaultAsBuiltAccCheck AUTOCREATE . . . . . . . . . . . . . 22-22
Properties . . . . . . . . . . . . . . . . . 22-81 GMO_RDV_enable_audit_criteria . . 22-12
DefaultAsBuiltCompare Implemented_ByRules . . . . . . . . . . 22-23
Properties . . . . . . . . . . . . . . . . . 22-80 Investment_Cost_Form_
DefaultAsMaintainedCompare Elements . . . . . . . . . . . . . . . . . 22-21
Properties . . . . . . . . . . . . . . . . . 22-83 IPVBOM_build_intent_status . . . . . 22-13
EngChange_Revision_Change_Type_ IPVBOM_compare_mode_var_level_
SaveAs_no_copy . . . . . . . . . . . . . 22-5 Occurrence_Notes . . . . . . . . . . . 22-17
EngChange_Revision_Change_Type_ IPVBOM_compare_mode_var_level_
Revise_no_copy . . . . . . . . . . . . . . 22-5 RevisionCompare_ItemTypes . . . 22-16
ESM_<Category>_Software_ IPVBOM_UPCFNA_Occ
Types . . . . . . . . . . . . . . . . . . . . 22-27 NoteName . . . . . . . . . . . . . . . . 22-18
ESM_Compatibility_Report_Excel_ ISS_Cost_Form_Elements . . . . . . . . 22-20
Template_Dataset . . . . . . . . . . . 22-33 Lot_DefaultChildProperties . . . . . . 22-70
ESM_HW_Compatibility_Report_Excel_ Lot.SUMMARYRENDERING . . . . . 22-69
StyleSheet_Dataset . . . . . . . . . . 22-32 ME_Cost_Form_Elements . . . . . . . . 22-20
ESM_HW_Compatibility_Report_HTML_ MRONeutralColumnsShownPref . . . 22-70
StyleSheet_Dataset . . . . . . . . . . 22-31 MRONeutralShownColumn
ESM_HW_Compatibility_Report_ WidthsPref . . . . . . . . . . . . . . . . 22-70
TransferMode . . . . . . . . . . . . . . 22-30 ParmDef.RENDERING . . . . . . . . . 22-40
ParmDefBCDRevision.RENDERING . . 22-38

Index
ParmDefBitDefRevision. ServiceManagerPhysicalLocation
RENDERING . . . . . . . . . . . . . . 22-39 ColumnsShownPref . . . . . . . . . . 22-87
ParmDefBoolRevision.RENDERING . . 22-35 ServiceManagerPhysicalLocation
ParmDefDateRevision.RENDERING . . 22-36 ColumnsWidthsPref . . . . . . . . . 22-87
ParmDefDblRevision.RENDERING . . 22-34 ServiceManagerShownColumn
ParmDefHexRevision.RENDERING . . 22-36 WidthsPref . . . . . . . . . . . . . . . . 22-86
ParmDefIntRevision.RENDERING . . 22-33 SIG_asystem_source_rules . . . . . . . 22-48
ParmDefSEDRevision.RENDERING . . 22-37 SIG_asystem_target_rules . . . . . . . 22-49
ParmDefStrRevision.RENDERING . . 22-34 SIG_asystem_transmitter_rules . . . 22-49
ParmGrpDef.RENDERING . . . . . . . 22-40 SIG_pvariable_rules . . . . . . . . . . . . 22-50
ParmGrpDefRevision.RENDERING . . 22-41 SIG_redundant_rules . . . . . . . . . . . 22-50
ParmGrpValRevision.RENDERING . . 22-38 SR_CHANGE_HOME_SITE_
PhysicalContext_relation_ PREFERENCE . . . . . . . . . . . . 22-103
primary . . . . . . . . . . . . . . . . . . 22-74 SRP0DgSrvRequest.
PhysicalLocationContainsColumns SUMMARYRENDERING . . . . 22-104
ShownPref . . . . . . . . . . . . . . . . 22-84 SRP0DgSrvRequestRevision_
PhysicalPart.SUMMARY DefaultChildProperties . . . . . . 22-105
RENDERING . . . . . . . . . . . . . . 22-76 SRP0DgSrvRequestRevision.
PhysicalPartRevision_ MROCREATERENDERING . . 22-104
DefaultChildProperties . . . . . . . 22-76 SRP0DgSrvRequestRevision.
PhysicalPartRevision.SUMMARY RENDERING . . . . . . . . . . . . . 22-104
RENDERING . . . . . . . . . . . . . . 22-77 SRP0DgSrvRequestRevision.
PhysicalRealization_relation_ SUMMARYRENDERING . . . . 22-105
primary . . . . . . . . . . . . . . . . . . 22-77 SRP0PrSrvRequest.
Piece_Cost_Form_Elements . . . . . . 22-21 SUMMARYRENDERING . . . . 22-105
Plant_Cost_Form_Elements . . . . . . 22-19 SRP0PrSrvRequestRevision_
ProductVariant.CREATE DefaultChildProperties . . . . . . 22-106
RENDERING . . . . . . . . . . . . . . 22-42 SRP0PrSrvRequestRevision.
ProductVariant.RENDERING . . . . . 22-42 MROCREATERENDERING . . 22-106
ProductVariantIntent. SRP0PrSrvRequestRevision.
CREATERENDERING . . . . . . . 22-44 RENDERING . . . . . . . . . . . . . 22-106
ProductVariantIntent. SRP0PrSrvRequestRevision.
RENDERING . . . . . . . . . . . . . . 22-43 SUMMARYRENDERING . . . . 22-106
QR_Cost_Form_Elements . . . . . . . . 22-20 SRP0RequalifyRqstActivityRevision.
RDV_build_intent_status . . . . . . . . 22-10 MROCREATERENDERING . . 22-107
RDV_default_option_values_for_tracking_ SRP0RqstActivity.
vehicle . . . . . . . . . . . . . . . . . . . 22-11 SUMMARYRENDERING . . . . 22-107
RDV_default_options_for_tracking_ SRP0RqstActivityRevision_
vehicle . . . . . . . . . . . . . . . . . . . 22-10 DefaultChildProperties . . . . . . 22-108
RDV_product_obsoletion_status . . . 22-11 SRP0RqstActivityRevision.MROCREATE
RDV_usage_synchronized_architecture_ RENDERING . . . . . . . . . . . . . 22-107
type . . . . . . . . . . . . . . . . . . . . . 22-12 SRP0RqstActivityRevision.
Realized_ByRules . . . . . . . . . . . . . 22-24 RENDERING . . . . . . . . . . . . . 22-108
SerialNumberGenerator_ SRP0RqstActivityRevision_
DefaultChildProperties . . . . . . . 22-78 ServiceDiscrepancy_default_
SerialNumberGenerator.SUMMARY relation . . . . . . . . . . . . . . . . . 22-109
RENDERING . . . . . . . . . . . . . . 22-78 SRP0RqstActivityRevision.
ServiceManagerAssetGroup SUMMARYRENDERING . . . . 22-108
ColumnsShownPref . . . . . . . . . . 22-85 SRP0ServiceCatalog_
ServiceManagerAssetGroup DefaultChildProperties . . . . . . 22-110
ColumnWidthsPref . . . . . . . . . . 22-85 SRP0ServiceCatalog_HWSOStructure_
ServiceManagerColumns default_relation . . . . . . . . . . . 22-110
ShownPref . . . . . . . . . . . . . . . . 22-86 SRP0ServiceCatalog.
MROCREATERENDERING . . 22-109

Index
SRP0ServiceCatalog_ QS_QSEARCH_ENABLED . . . . . . 19-131

PseudoFolder . . . . . . . . . . . . . 22-111 QS_SPATIAL_ENABLED . . . . . . . 19-132
SRP0ServiceCatalog. QS_TRUSHAPE_GENERATION_
RENDERING . . . . . . . . . . . . . 22-109 ENABLED . . . . . . . . . . . . . . . 19-132
SRP0ServiceCatalog_SRP0ProductCatalog_ QSEARCH_update_enabled . . . . . 19-132
default_relation . . . . . . . . . . . 22-111 RDV_QSEARCH_REFINE . . . . . . 19-134
SRP0ServiceCatalog. RDV_QSEARCH_REVISION_RULE_
SUMMARYRENDERING . . . . 22-110 NAMES . . . . . . . . . . . . . . . . . 19-135
SRP0ServiceDiscrepancy. RDV_QSEARCH_STREAMING_
MROCREATERENDERING . . 22-111 MODE . . . . . . . . . . . . . . . . . . 19-135
SRP0ServiceOffering_ActivityCost_default_ SR_CHANGE_HOME_SITE_PREFERENCE
relation . . . . . . . . . . . . . . . . . 22-112 preference . . . . . . . . . . . . . . . . . . . 22-103
SRP0ServiceOffering_ SRM_host_port preference . . . . . . . . . 18-60
DefaultChildProperties . . . . . . 22-113 SRP0DgSrvRequest.
SRP0ServiceOffering_HWSOStructure_ SUMMARYRENDERING
default_relation . . . . . . . . . . . 22-113 preference . . . . . . . . . . . . . . . . . . . 22-104
SRP0ServiceOffering. SRP0DgSrvRequestRevision_
MROCREATERENDERING . . 22-112 DefaultChildProperties
SRP0ServiceOffering. preference . . . . . . . . . . . . . . . . . . . 22-105
RENDERING . . . . . . . . . . . . . 22-112 SRP0DgSrvRequestRevision.
SRP0ServiceOffering_SRP0ServiceCatalog_ MROCREATERENDERING
default_relation . . . . . . . . . . . 22-113 preference . . . . . . . . . . . . . . . . . . . 22-104
SRP0ServiceOffering. SRP0DgSrvRequestRevision.RENDERING
SUMMARYRENDERING . . . . 22-112 preference . . . . . . . . . . . . . . . . . . . 22-104
SRP0ServiceOfferingTable_ SRP0DgSrvRequestRevision.
ColumnPreferences . . . . . . . . . 22-114 SUMMARYRENDERING
SRP0StatusViewColumns preference . . . . . . . . . . . . . . . . . . . 22-105
ShownPref . . . . . . . . . . . . . . . 22-114 SRP0PrSrvRequest.SUMMARYRENDERING
TAE_Powertrain_site . . . . . . . . . . . 22-19 preference . . . . . . . . . . . . . . . . . . . 22-105
TC_Configuration_File . . . . . . . . . . 22-16 SRP0PrSrvRequestRevision_
TC_customization_libraries . . . . . . . 22-3 DefaultChildProperties
TC_external_system_attr_value_ preference . . . . . . . . . . . . . . . . . . . 22-106
separator . . . . . . . . . . . . . . . . . 22-14 SRP0PrSrvRequestRevision.
TC_external_system_bom_ MROCREATERENDERING
attributes . . . . . . . . . . . . . . . . . 22-14 preference . . . . . . . . . . . . . . . . . . . 22-106
TC_external_system_item_type . . . . 22-13 SRP0PrSrvRequestRevision.RENDERING
TC_external_system_url . . . . . . . . . 22-15 preference . . . . . . . . . . . . . . . . . . . 22-106
TC_external_system_url_value_ SRP0PrSrvRequestRevision.
name . . . . . . . . . . . . . . . . . . . . 22-16 SUMMARYRENDERING
TC_Interspec_URL . . . . . . . . . . . . . 22-4 preference . . . . . . . . . . . . . . . . . . . 22-106
TC_LAST_USED_PATTERNS . . . . . 22-4 SRP0RequalifyRqstActivityRevision.
TC_send_to_external_system . . . . . 22-15 MROCREATERENDERING
TC_Validation_Datasettype . . . . . . 5-116 preference . . . . . . . . . . . . . . . . . . . 22-107
TC_Validation_Utility . . . . . . . . . . 5-121 SRP0RqstActivity.SUMMARYRENDERING
TCAE_autogen_name_form_types . . . 22-9 preference . . . . . . . . . . . . . . . . . . . 22-107
TCAE_installation_level . . . . . . . . . 22-18 SRP0RqstActivityRevision_
TCENG_releasable_logical_types . . 22-25 DefaultChildProperties
Spatial search preferences preference . . . . . . . . . . . . . . . . . . . 22-108
QS_BBOX_GENERATION_ SRP0RqstActivityRevision.MROCREATE
ENABLED . . . . . . . . . . . . . . . 19-133 RENDERING preference . . . . . . . . 22-107
QS_BBOX_GENERATION_FROM_NX_ SRP0RqstActivityRevision.RENDERING
ENABLED . . . . . . . . . . . . . . . 19-134 preference . . . . . . . . . . . . . . . . . . . 22-108
QS_MAX_QUERY_EXECUTION_TIME_
FOR_BOTTOMUP . . . . . . . . . 19-134

Index
SRP0RqstActivityRevision_ STEP_drawing_pref . . . . . . . . . . . . 18-77

ServiceDiscrepancy_default_relation STEP_export_data_format . . . . . . . 18-78
preference . . . . . . . . . . . . . . . . . . . 22-109 STEP_export_directory . . . . . . . . . . 18-78
SRP0RqstActivityRevision. STEP_FILETYPE_2_DATATYPE . . 18-78
SUMMARYRENDERING STEP_IMAN_manifestation . . . . . . 18-80
preference . . . . . . . . . . . . . . . . . . . 22-108 STEP_IMAN_master_data . . . . . . . 18-79
SRP0ServiceCatalog_DefaultChildProperties STEP_IMAN_reference . . . . . . . . . 18-80
preference . . . . . . . . . . . . . . . . . . . 22-110 STEP_IMAN_requirement . . . . . . . 18-80
SRP0ServiceCatalog_HWSOStructure_ STEP_IMAN_specification . . . . . . . 18-79
default_relation preference . . . . . . . 22-110 STEP_IMAN_UG_altrep . . . . . . . . . 18-81
SRP0ServiceCatalog. STEP_IMAN_UG_scenario . . . . . . . 18-81
MROCREATERENDERING STEP_import_directory . . . . . . . . . 18-81
preference . . . . . . . . . . . . . . . . . . . 22-109 STEP_informative_doc_role . . . . . . 18-82
SRP0ServiceCatalog_PseudoFolder STEP_make_or_buy_attr . . . . . . . . 18-82
preference . . . . . . . . . . . . . . . . . . . 22-111 STEP_material_specification_
SRP0ServiceCatalog.RENDERING pref . . . . . . . . . . . . . . . . . . . . . 18-82
preference . . . . . . . . . . . . . . . . . . . 22-109 STEP_not_yet_approved_status . . . 18-83
SRP0ServiceCatalog_SRP0ProductCatalog_ STEP_part_items . . . . . . . . . . . . . . 18-83
default_relation preference . . . . . . . 22-111 STEP_process_specification_pref . . . 18-83
SRP0ServiceCatalog. STEP_surface_finish_specification_
SUMMARYRENDERING pref . . . . . . . . . . . . . . . . . . . . . 18-84
preference . . . . . . . . . . . . . . . . . . . 22-110 TC_organization_id . . . . . . . . . . . . 18-84
SRP0ServiceDiscrepancy. STEP_<relation_type> preference . . . . 18-75
MROCREATERENDERING STEP_approved_status preference . . . 18-75
preference . . . . . . . . . . . . . . . . . . . 22-111 STEP_cad_filename_pref
SRP0ServiceOffering_ActivityCost_default_ preference . . . . . . . . . . . . . . . . . . . . 18-77
relation preference . . . . . . . . . . . . . 22-112 STEP_default_BOMView_type
SRP0ServiceOffering_DefaultChildProperties preference . . . . . . . . . . . . . . . . . . . . 18-76
preference . . . . . . . . . . . . . . . . . . . 22-113 STEP_default_datasettype
SRP0ServiceOffering_HWSOStructure_ preference . . . . . . . . . . . . . . . . . . . . 18-76
default_relation preference . . . . . . . 22-113 STEP_default_item_type preference . . 18-76
SRP0ServiceOffering. STEP_design_specification_pref
MROCREATERENDERING preference . . . . . . . . . . . . . . . . . . . . 18-77
preference . . . . . . . . . . . . . . . . . . . 22-112 STEP_DMI_markup preference . . . . . 18-79
SRP0ServiceOffering.RENDERING STEP_drawing_pref preference . . . . . 18-77
preference . . . . . . . . . . . . . . . . . . . 22-112 STEP_export_data_format
SRP0ServiceOffering_SRP0ServiceCatalog_ preference . . . . . . . . . . . . . . . . . . . . 18-78
default_relation preference . . . . . . . 22-113 STEP_export_directory preference . . . 18-78
SRP0ServiceOffering. STEP_FILETYPE_2_DATATYPE
SUMMARYRENDERING preference . . . . . . . . . . . . . . . . . . . . 18-78
preference . . . . . . . . . . . . . . . . . . . 22-112 STEP_IMAN_manifestation
SRP0ServiceOfferingTable_ preference . . . . . . . . . . . . . . . . . . . . 18-80
ColumnPreferences preference . . . . 22-114 STEP_IMAN_master_data
SRP0StatusViewColumnsShownPref preference . . . . . . . . . . . . . . . . . . . . 18-79
preference . . . . . . . . . . . . . . . . . . . 22-114 STEP_IMAN_reference preference . . . 18-80
STEP Translator preferences . . . . . . . 18-75 STEP_IMAN_requirement
STEP_<relation_type> . . . . . . . . . . 18-75 preference . . . . . . . . . . . . . . . . . . . . 18-80
STEP_approved_status . . . . . . . . . . 18-75 STEP_IMAN_specification
STEP_cad_filename_pref . . . . . . . . 18-77 preference . . . . . . . . . . . . . . . . . . . . 18-79
STEP_default_BOMView_type . . . . 18-76 STEP_IMAN_UG_altrep preference . . 18-81
STEP_default_datasettype . . . . . . . 18-76 STEP_IMAN_UG_scenario
STEP_default_item_type . . . . . . . . 18-76 preference . . . . . . . . . . . . . . . . . . . . 18-81
STEP_design_specification_pref . . . 18-77 STEP_import_directory preference . . . 18-81
STEP_DMI_markup . . . . . . . . . . . . 18-79

Index
STEP_informative_doc_role ConditionValidationResult
preference . . . . . . . . . . . . . . . . . . . . 18-82 ColumnPreferences . . . . . . . . . 19-105
STEP_make_or_buy_attr ConditionValidationResultColumn
preference . . . . . . . . . . . . . . . . . . . . 18-82 WidthPreferences . . . . . . . . . . 19-106
STEP_material_specification_pref CondValData.CREATERENDERING . . 19-101
preference . . . . . . . . . . . . . . . . . . . . 18-82 CondValData.
STEP_not_yet_approved_status SUMMARYRENDERING . . . . 19-102
preference . . . . . . . . . . . . . . . . . . . . 18-83 CondValDataCreate.CREATE_
STEP_part_items preference . . . . . . . 18-83 REGISTEREDTO . . . . . . . . . . 19-102
STEP_process_specification_pref CondValDataRevision.
preference . . . . . . . . . . . . . . . . . . . . 18-83 REGISTEREDTO . . . . . . . . . . 19-102
STEP_surface_finish_specification_pref CondValDataRevision.
preference . . . . . . . . . . . . . . . . . . . . 18-84 RENDERING . . . . . . . . . . . . . 19-103
Structure Manager assembly CondValDataRevision.
preferences . . . . . . . . . . . . . . . . . . . 19-72 SUMMARYRENDERING . . . . 19-103
Structure Manager behavior CondValdataRevSummary.SUMMARY_
preferences . . . . . . . . . . . . . . . . . . . 19-44 REGISTEREDTO . . . . . . . . . . 19-102
Structure Manager column CondValDataSummary.SUMMARY_
preferences . . . . . . . . . . . . . . . . . . . 19-53 REGISTEREDTO . . . . . . . . . . 19-103
PortalPSEColumnsShownPref . . . . 19-54 CONDVALIDATION_Keep_PrevRev_
PortalPSEShownColumnsWidthPref . . 19-54 Result . . . . . . . . . . . . . . . . . . 19-105
Structure Manager display CondValidation_NoData . . . . . . . . 19-104
preferences . . . . . . . . . . . . . . . . . . . 19-58 CondValResult.SUMMARY
Structure Manager preferences . . . . . 19-44 RENDERING . . . . . . . . . . . . . 19-104
AbsOccGrmCopyRules . . . . . . . . . . 19-77 CondValResultSummary.SUMMARY_
<application name>.ic_show_remove_ REGISTEREDTO . . . . . . . . . . 19-104
icons . . . . . . . . . . . . . . . . . . . . 19-59 ConfigureToLoadEnableDefault
application name.ic_icon_level . . . . 19-58 VariantConfig . . . . . . . . . . . . . . 19-75
BOM_Additional_Packing_ GDE_objects_with_integer_
Criteria . . . . . . . . . . . . . . . . . . 19-90 quantity . . . . . . . . . . . . . . . . . . 19-46
BOM_Additional_Ref_Designator_Search_ IC_baseline_carry_forward_active_
Criteria . . . . . . . . . . . . . . . . . . 19-90 changes . . . . . . . . . . . . . . . . . . 19-61
BOM_Enable_Quantity_Validation_ IC_baseline_carry_forward_
Against_Ref_Designator . . . . . . . 19-91 status . . . . . . . . . . . . . . . . . . . . 19-62
BOM_Enable_Ref_Designator_Value_ ICPanelAttachChangeDefs . . . . . . . 19-63
Packing . . . . . . . . . . . . . . . . . . 19-89 ICPanelAttachChangeWidths . . . . . 19-63
BOM_MARKUP_ADD_FONT_ ICPanelBomChangeDefs . . . . . . . . . 19-62
STYLE . . . . . . . . . . . . . . . . . . . 19-60 ICPanelBomChangeWidths . . . . . . . 19-62
BOM_MARKUP_ADD_ ICPanelOccAttrChangeDefs . . . . . . 19-64
FOREGROUND . . . . . . . . . . . . 19-60 ICPanelOccAttrChangeWidths . . . . 19-64
BOM_MARKUP_STRIKE_ Incremental_Change_
FOREGROUND . . . . . . . . . . . . 19-61 Management . . . . . . . . . . . . . . . 19-65
BOM_objects_excluded_from_ JT_File_Excluded_Refsets . . . . . . . 19-95
split . . . . . . . . . . . . . . . . . . . . . 19-45 JT_File_OverrideChildren_
BOMCompareVisibleModes . . . . . . 19-59 ownRefsets . . . . . . . . . . . . . . . . 19-93
BOMExcludeFromPackCheck . . . . . 19-92 JT_File_Priority_Refsets . . . . . . . . 19-94
BOMWriterDirectMode JTContentBomLineProperties . . . . . 19-95
RelationType . . . . . . . . . . . . . 19-129 JTContentHintPropertyPolicy . . . . . 19-96
BOMWriterNoDescendantsn LOU_display_name_properties . . . 19-114
PLMXML . . . . . . . . . . . . . . . . 19-130 MoveICCreationToMenu . . . . . . . . . 19-66
BOMWriterNoDirectParents . . . . . 19-130 New_Ic_Dialog_last_ic_type . . . . . . 19-66
CFM_ITEM_TYPE_RULE_INCLUDE_ NX_InterOptWithProduct
SUB_TYPES . . . . . . . . . . . . . . . 19-45 ViewDataset . . . . . . . . . . . . . . . . 5-73
CFMOccEffMode . . . . . . . . . . . . . . 19-76

Index
PS_allow_plmxml_transforms_with_no_ PSESubstituteColorPref . . . . . . . . . 19-69

legacy_factor . . . . . . . . . . . . . . . 19-98 PSEVariantRuleDialogTableSort . . . 19-71
PS_assume_legacy_transform_ PSEVariantsMode . . . . . . . . . . . . . 19-73
units . . . . . . . . . . . . . . . . . . . . 19-98 PSM_classic_variants_numeric_
PS_assume_old_transform_ families . . . . . . . . . . . . . . . . . . 19-84
format . . . . . . . . . . . . . . . . . . . 19-97 PSM_classic_variants_text_
PS_convert_legacy_transform_to_ families . . . . . . . . . . . . . . . . . . 19-82
plmxml . . . . . . . . . . . . . . . . . . . 19-99 PSM_global_option_item_id . . . . . . 19-88
PS_Duplicate_FindNo_Update . . . . 19-92 PUBLISH_AlignableSourceTypes . . 19-51
PS_Find_Number_Validation . . . . . 19-49 PUBLISH_AlignableTargetTypes . . 19-51
PS_new_seqno_mode . . . . . . . . . . . 19-49 RAC_expand_below_batch_size . . . . 19-96
PS_Reference_Designator_ RDV_show_itemid_prefix . . . . . . . 19-125
Validation . . . . . . . . . . . . . . . . . 19-91 RDV_show_lou_prop . . . . . . . . . . 19-125
PS_replace_with_substructure . . . . 19-50 ROLL_UP_QUANTITY_FLAG . . . . 19-48
PS_structure_change_condition . . . . 19-99 ShowModuleIcons . . . . . . . . . . . . . 19-80
PS_wu_configd_imprecise_only . . . . 19-50 ShowViIcons . . . . . . . . . . . . . . . . . 19-80
PSE_check_read_access_for_Rev_Rule_ TC_BOM_Precision_Preference . . . . 19-52
entry . . . . . . . . . . . . . . . . . . . . 19-46 TC_BVRSYNCFORM_
PSE_default_view_type . . . . . . . . . 19-46 DELEGATE . . . . . . . . . . . . . . 19-101
PSE_Display_Pending_Edits . . . . . . 19-47 TC_CFG_PRODUCTS_USE_
PSE_enable_related_substitutes . . . 19-70 VARIABILITY . . . . . . . . . . . . . 19-85
PSE_expand_on_open . . . . . . . . . . . 19-47 TC_config_rule_name . . . . . . . . . . . 19-52
PSE_icon_placement . . . . . . . . . . . 19-67 TC_ExportConfigUGNXAssembly . . 19-72
PSE_prompt_for_remote_import . . . 19-96 TC_JT_voxel_size . . . . . . . . . . . . . . 19-93
PSE_ROLL_UP_TEMPLATES . . . . 19-48 TC_show_open_in_pse_button . . . . . 19-52
PSE_show_option_family_prefix . . . 19-67 TC_ValidApprovedStatus . . . . . . . . 19-76
PSE_show_option_item_prefix . . . . . 19-68 TCAllowedChildTypes_
PSEAdditionColorPref . . . . . . . . . . 19-70 <ItemTypeOrGDEType> . . . . . . 19-87
PSEAllowLegacyVICreation . . . . . . 19-78 TCEnforceSingleType . . . . . . . . . . . 19-87
PSEAutoPackPref . . . . . . . . . . . . . 19-69 variant_description_column_
PSEAutoViCreateEmptyVI . . . . . . . 19-81 width . . . . . . . . . . . . . . . . . . . . 19-56
PSEAutoViNamePrefix . . . . . . . . . . 19-82 variant_item_column_width . . . . . . 19-56
PSEAutoViNewItemPopup . . . . . . . 19-82 variant_option_column_width . . . . . 19-56
PSEAutoViStopVICreation variant_state_column_width . . . . . . 19-57
ForUnconfiguredModule . . . . . . 19-81 variant_value_column_width . . . . . 19-57
PSEBypassVISearch . . . . . . . . . . . 19-79 variant_values_column_width . . . . . 19-57
PSEChangedColorPref . . . . . . . . . . 19-71 Vis_InterOptWithProduct
PSECreateVISameType . . . . . . . . . 19-79 ViewDataset . . . . . . . . . . . . . . . 19-53
PSEDisplayTypePref . . . . . . . . . . . 19-66 VISTopLevelRef_relation_
PSEEnableFilteringUnconfigdDueTo primary . . . . . . . . . . . . . . . . . . 19-53
ClassicVariantsPref . . . . . . . . . . 19-75 vrule_reln_column_width . . . . . . . . 19-58
PSEImpreciseColorPref . . . . . . . . . 19-69 Structure Manager transform
PSEIsNewVIisLinkedToModule . . . 19-78 preferences . . . . . . . . . . . . . . . . . . . 19-97
PSEIsNewVILinkedToModule . . . . . 19-71 Structure_Alias_File preference . . . . . 10-62
PSEoccnotesnocopy . . . . . . . . . . . . 19-67 StructureContext_DefaultChildProperties
PSEPreciseColorPref . . . . . . . . . . . 19-68 preference . . . . . . . . . . . . . . . . . . . . 10-85
PSESavedConfigRelationTypes . . . . 19-89 Subscription Manager daemon
PSESearchColumnsShownPref . . . . 19-55 preferences . . . . . . . . . . . . . . . . . . . . 9-10
PSESearchShownColumn TC_notification_msg_ext . . . . . . . . . . 9-13
WidthsPref . . . . . . . . . . . . . . . . 19-55 TC_subscriptionmgrd_cloning_
PSEShowSubstitutesPref . . . . . . . . 19-70 interval . . . . . . . . . . . . . . . . . . . 9-12
PSEshowToolBar . . . . . . . . . . . . . . 19-48 TC_subscriptionmgrd_max_subscriptions_
PSEShowUnconfigdEffPref . . . . . . . 19-74 to_dispatch . . . . . . . . . . . . . . . . . 9-12
PSEShowUnconfigdVarPref . . . . . . 19-73

Index
TC_subscriptionmgrd_processing_ T
hours . . . . . . . . . . . . . . . . . . . . . 9-11
TC_subscriptionmgrd_sleep_ TAE_CM_change_name_is_mandatory
minutes . . . . . . . . . . . . . . . . . . . 9-11 preference . . . . . . . . . . . . . . . . . . . . 12-17
Subscription Monitor preferences . . . . . 9-13 TAE_CM_show_task_viewer
Mail_subscription_notify_sub_groups_ preference . . . . . . . . . . . . . . . . . . . . 12-17
too . . . . . . . . . . . . . . . . . . . . . . . 9-18 TAE_Powertrain_site preference . . . . 22-19
SCM_notification_history . . . . . . . . . 9-22 TAO_ROOT variable . . . . . . . . . . . . . . . 3-9
SCM_notification_WorkspaceObject_ TASK_MONITOR_SLEEP_TIME
props . . . . . . . . . . . . . . . . . . . . . 9-22 preference . . . . . . . . . . . . . . . . . . . . 11-11
TC_automatic_refresh_list_ TaskInBox_DefaultChildProperties
maximum . . . . . . . . . . . . . . . . . . 9-18 preference . . . . . . . . . . . . . . . . . . . . 10-83
TC_automatic_refresh_time_ <TC Publishing Page type>_
interval . . . . . . . . . . . . . . . . . . . 9-17 DefaultChildProperties preference . . 20-50
TC_automatic_refresh_waiting_ <TC Publishing Technical Portfolio
time . . . . . . . . . . . . . . . . . . . . . . 9-17 type>_DefaultChildProperties . . . . . 20-49
TC_refresh_notify . . . . . . . . . . . . . . 9-14 TC_<daemon name>_<site ID>_prog_number
TC_refresh_notify_list_maximum . . . 9-17 preference . . . . . . . . . . . . . . . . . . . . 18-23
TC_refresh_notify_pull_time_ TC_<daemon name>_<site name>_port_
interval . . . . . . . . . . . . . . . . . . . 9-16 number preference . . . . . . . . . . . . . . 18-23
TC_refresh_notify_scope . . . . . . . . . . 9-14 TC_<daemon name>_<site name>_prog_
TC_refresh_notify_subscribe_to_ number preference . . . . . . . . . . . . . . 18-24
types . . . . . . . . . . . . . . . . . . . . . 9-15 TC_<datasettype>_Tool preference . . . 10-69
TC_refresh_notify_timed_out . . . . . . 9-18 TC_<file type>_Cache_Mode
TC_subscription . . . . . . . . . . . . . . . . 9-13 preference . . . . . . . . . . . . . . . . . . . . . 9-25
TC_subscription_log_event_and_action_ TC_actionmgrd_cloning_interval
status . . . . . . . . . . . . . . . . . . . . . 9-19 preference . . . . . . . . . . . . . . . . . . . . . 9-10
TcActionColumnPreferences . . . . . . . 9-21 TC_actionmgrd_general_processing_hours
TcActionColumnWidthPreferences . . 9-21 preference . . . . . . . . . . . . . . . . . . . . . . 9-9
TcEventColumnPreferences . . . . . . . 9-20 TC_actionmgrd_max_actions_to_dispatch
TcEventColumnWidthPreferences . . . 9-20 preference . . . . . . . . . . . . . . . . . . . . . 9-10
TcSubscription TC_actionmgrd_max_subprocess_to_start
ColumnWidthPreferences . . . . . . 9-19 preference . . . . . . . . . . . . . . . . . . . . . 9-10
TcSubscriptionColumnPreferences . . 9-19 TC_actionmgrd_sleep_minutes
<TypeName>_subscribe_to_events . . 9-15 preference . . . . . . . . . . . . . . . . . . . . . . 9-8
Supercedure_DefaultChildProperties TC_Administration_Logging
Synchronization preferences . . . . 5-95, 5-98 TC_AE_<datasettype>_Default_View_Tool
LDAP_admin_dn . . . . . . . . . . . . . . . 5-97 preference . . . . . . . . . . . . . . . . . . . . 10-62
LDAP_admin_pw . . . . . . . . . . . . . . . 5-98 TC_ALLOW_ADHOC_VALIDATIONS
LDAP_cert_db_path . . . . . . . . . . . . . 5-97 preference . . . . . . . . . . . . . . . . . . . . 5-116
LDAP_member_list_attr . . . . . . . . . 5-101 TC_allow_appr_checking preference . . . 19-2
LDAP_member_type_attr . . . . . . . . 5-101 TC_allow_appr_query_auditing
LDAP_object_type_attr . . . . . . . . . . 5-101 preference . . . . . . . . . . . . . . . . . . . . . 19-3
LDAP_port_number . . . . . . . . . . . . . 5-96 TC_allow_inherited_group_volume_access
LDAP_service_hosts . . . . . . . . . . . . . 5-96 preference . . . . . . . . . . . . . . . . . . . . . 9-38
LDAP_sync_group_flags . . . . . . . . . . 5-99 TC_Allow_Longer_ID_Name
LDAP_sync_member_flags . . . . . . . . 5-99 preference . . . . . . . . . . . . . . . . . . . . 10-63
LDAP_sync_role_flags . . . . . . . . . . 5-100 Tc_allow_users_edit_pfdata_options
LDAP_sync_user_flags . . . . . . . . . . . 5-98 preference . . . . . . . . . . . . . . . . . . . . 18-24
LDAP_use_ssl . . . . . . . . . . . . . . . . . 5-96 TC_altrep_update_lmd preference . . . 18-25
Syntax definition conventions . . . . . . . . . 1-1 TC_always_exclude_dataset_files_on_export
Syslog file output . . . . . . . . . . . . . . . . 9-23 role-based preference . . . . . . . . . . . . 18-22
Syslog files environment variables . . . . . 2-1 TC_APP_UID_DIR variable . . . . . . . . . . 3-9

Index
TC_Application_Logging preference . . . 9-38 TC_Configuration_File preference . . . 22-16

TC_appr_allow_remote_query TC_control_wildcard preference . . . . . 10-64
preference . . . . . . . . . . . . . . . . . . . . . 19-4 TC_control_wildcard_exception
TC_appr_checking_interval preference . . . . . . . . . . . . . . . . . . . . 10-65
preference . . . . . . . . . . . . . . . . . . . . . 19-3 TC_CRF_overwrite_existing_dataset_content
TC_appr_remote_query_timeout preference . . . . . . . . . . . . . . . . . . . . . 20-5
preference . . . . . . . . . . . . . . . . . . . . . 19-5 tc_cshvars script . . . . . . . . . . . . . . . . . . 1-4
TC_appref_registry_site preference . . . 18-25 TC_current_role . . . . . . . . . . . . . . . . . . 6-6
TC_assembly_xml_relation TC_DATA environment variable . . . . . . . 1-4
preference . . . . . . . . . . . . . . . . . . . . 18-25 TC_DATA variable . . . . . . . . . . . . . . . . 3-9
TC_audit_buffer_size preference . . . . . . . 9-2 TC_DATA_MODEL variable . . . . . . . . . 3-9
TC_audit_delimiter preference . . . . . . . . 9-3 TC_dataset_deep_copy_rules
TC_audit_file_format preference . . . . . . . 9-3 preference . . . . . . . . . . . . . . . . . . . . . . 5-5
TC_audit_log_dir preference . . . . . . . . . 9-2 TC_Dataset_Import_Exclude_Wildcard
TC_audit_manager preference . . . . . . . . 9-1 preference . . . . . . . . . . . . . . . . . . . . . 5-23
TC_authorization_mode . . . . . . . . . . . . . 8-1 TC_dataset_vers_export preference . . 18-28
TC_Auto_Checkout preference . . . . . . 10-63 TC_dataset_vers_export role-based
TC_auto_login preference . . . . . . . . . 10-63 preference . . . . . . . . . . . . . . . . . . . . 18-20
TC_automatic_refresh_list_maximum TC_days_non_login_timeout
TC_automatic_refresh_time_interval TC_DB_CONNECT variable . . . . . . . . . 3-9
preference . . . . . . . . . . . . . . . . . . . . . 9-17 TC_default_export_sites preference . . 18-28
TC_automatic_refresh_waiting_time TC_default_gms_site preference . . . . . 18-60
preference . . . . . . . . . . . . . . . . . . . . . 9-17 TC_default_gms_transfer_mode
TC_background_object_export_dir preference . . . . . . . . . . . . . . . . . . . . 18-61
preference . . . . . . . . . . . . . . . . . . . . 18-26 TC_default_part_type preference . . . . . 5-74
TC_BIN variable . . . . . . . . . . . . . . . . . . 3-9 TC_directly_transferable_classes
TC_bom_level_export preference . . . . 18-26 preference . . . . . . . . . . . . . . . . . . . . 18-29
TC_bom_level_export role-based TC_DIS_2D_named_ref preference . . . . 21-7
preference . . . . . . . . . . . . . . . . . . . . 18-21 TC_DIS_3D_named_ref preference . . . . 21-8
TC_BOM_Precision_Preference TC_DIS_Search preference . . . . . . . . . 21-8
preference . . . . . . . . . . . . . . . . . . . . 19-52 TC_DISABLE_FLASH preference . . . 10-66
TC_bomchange_export preference . . . . 12-17 TC_DISABLE_FLASH variable . . . . . . 3-10
TC_BVRSYNCFORM_DELEGATE TC_disallow_release_status_on_replica
TC_BYPASS_CANNED_METHODS TC_disallowed_replica_relations
TC_Cache_Allowed preference . . . . . . . 9-24 TC_display_group_names_limit
TC_Cache_Dir preference . . . . . . . . . . 9-24 preference . . . . . . . . . . . . . . . . . . . . 10-66
TC_Cache_Mode preference . . . . . . . . . 9-25 TC_display_real_prop_names
TC_Cache_Protection preference . . . . . 9-26 preference . . . . . . . . . . . . . . . . . . . . 10-67
TC_Cache_Size preference . . . . . . . . . . 9-24 TC_display_thumbnail_in_UI
TC_CFG_PRODUCTS_USE_VARIABILITY preference . . . . . . . . . . . . . . . . . . . . 10-67
preference . . . . . . . . . . . . . . . . . . . . 19-85 TC_Distributor_info_form
TC_check_object_before_create preference . . . . . . . . . . . . . . . . . . . . 22-63
preference . . . . . . . . . . . . . . . . . . . . . 5-22 TC_do_not_insert_imported_objects_into_
TC_check_out_dir preference . . . . . . . 10-64 folder preference . . . . . . . . . . . . . . . 18-30
TC_check_remote_user_priv_from_sites TC_EMAIL_AFTER_BACKGROUND_
preference . . . . . . . . . . . . . . . . . . . . 18-27 REMOTE_IMPORT preference . . . . . 18-31
TC_checkout_and_export TC_enable_backup_modes preference . . . 9-7
preference . . . . . . . . . . . . . . . . . . . . 10-64 TC_ERP_current_schema_name
TC_CM_approvers_modifier_roles preference . . . . . . . . . . . . . . . . . . . . 23-49
preference . . . . . . . . . . . . . . . . . . . . . 11-2 TC_ERP_dataset_types_to_transfer
TC_config_rule_name preference . . . . 19-52 preference . . . . . . . . . . . . . . . . . . . . 23-52

Index
TC_ERP_mapping_files preference . . . 23-49 TC_fts_indexed_types preference . . . . . 5-56

TC_ERP_rellog_file_path TC_fts_indexing_wait_timeout
TC_ERP_uom_mapping_file TC_fts_max_results preference . . . . . . . 5-57
preference . . . . . . . . . . . . . . . . . . . . 23-50 TC_fts_query_port preference . . . . . . . 5-57
TC_export_child_groups preference . . 18-74 TC_fts_real_time_indexing
TC_export_parent_groups preference . . . . . . . . . . . . . . . . . . . . . 5-58
preference . . . . . . . . . . . . . . . . . . . . 18-74 TC_fts_service_port preference . . . . . . . 5-58
Tc_export_pfmember_replica TC_gms_enable_immediate_option
TC_ExportConfigUGNXAssembly TC_gms_export_default_transfermode
TC_external_app_reg_url TC_gms_export_transfermode_for_<site_
preference . . . . . . . . . . . . . . . . . . . . 18-31 name> preference . . . . . . . . . . . . . . 18-62
TC_external_application_names TC_gms_gs_bos_service_url
TC_external_application_types TC_gms_gs_server_url preference . . . . 18-63
preference . . . . . . . . . . . . . . . . . . . . . 5-95 TC_gms_gs_uri preference . . . . . . . . . 18-63
TC_external_default_launch_ui TC_gms_import_default_transfermode
TC_external_local_app_guid TC_gms_monitoring_gui_total_number_of_
preference . . . . . . . . . . . . . . . . . . . . . 5-92 steps_for_transfer preference . . . . . . 18-63
TC_external_proxiable_objects . . . . . . . 5-92 TC_gms_sso_enabled preference . . . . . 18-64
TC_external_proxiable_objects_ TC_Graph_Node_Thumbnail_Shown
props . . . . . . . . . . . . . . . . . . . . . . . . 5-93 preference . . . . . . . . . . . . . . . . . . . . 10-67
TC_external_Requirements_proxy_props_ TC_GROUP_PFILE preference . . . . . 10-68
external preference . . . . . . . . . . . . . . 5-94 TC_HANDLERS_DEBUG variable . . . . 3-10
TC_external_Requirements_proxy_props_ TC_HELP_FILE variable . . . . . . . . . . . 3-10
internal preference . . . . . . . . . . . . . . 5-93 TC_HTDOCS variable . . . . . . . . . . . . . 3-10
TC_external_system_attr_value_separator TC_hub_groups preference . . . . . . . . . 18-33
preference . . . . . . . . . . . . . . . . . . . . 22-14 TC_identify_plmxml_import_dataset
TC_external_system_bom_attributes preference . . . . . . . . . . . . . . . . . . . . 18-34
preference . . . . . . . . . . . . . . . . . . . . 22-14 TC_idsm_client_def_timeout
TC_external_system_item_type preference . . . . . . . . . . . . . . . . . . . . 18-35
preference . . . . . . . . . . . . . . . . . . . . 22-13 TC_idsm_client_initial_timeout
TC_external_system_url preference . . 22-15 preference . . . . . . . . . . . . . . . . . . . . 18-35
TC_external_system_url_value_name TC_idsm_proxy_server_site_table
TC_follow_ownership_chain_max_site_count TC_ie_error_report preference . . . . . . 18-36
preference . . . . . . . . . . . . . . . . . . . . 18-32 TC_ignore_case_on_search
TC_force_remote_sites_exclude_files preference . . . . . . . . . . . . . . . . . . . . 10-68
preference . . . . . . . . . . . . . . . . . . . . 18-32 TC_inbox_interval preference . . . . . . . 10-69
TC_FS_SERVICE variable . . . . . . . . . . 3-10 TC_INCLUDE variable . . . . . . . . . . . . 3-10
TC_fts_aci_port preference . . . . . . . . . . 5-52 TC_INSTALL_DIR variable . . . . . . . . . 3-10
TC_fts_database_name preference . . . . 5-52 TC_Installation_Logging preference . . . 9-38
TC_fts_default_language_type TC_Interspec_URL preference . . . . . . . 22-4
preference . . . . . . . . . . . . . . . . . . . . . 5-53 TC_JOURNAL environment variable . . . 2-2
TC_fts_engine preference . . . . . . . . . . . 5-53 TC_JOURNAL variable . . . . . . . . . . . . 3-10
TC_fts_fsf_host preference . . . . . . . . . . 5-54 TC_Journal_Modules preference . . . . . . 9-39
TC_fts_fsf_port preference . . . . . . . . . . 5-54 TC_Journalling preference . . . . . . . . . . 9-39
TC_fts_host preference . . . . . . . . . . . . 5-55 TC_JT_voxel_size preference . . . . . . . 19-93
TC_fts_index_port preference . . . . . . . . 5-55 TC_KEEP_SYSTEM_LOG environment
TC_fts_index_retries preference . . . . . . 5-56 variable . . . . . . . . . . . . . . . . . . . . . . . 2-3
TC_fts_index_timeout preference . . . . . 5-56

Index
TC_KEEP_SYSTEM_LOG TC_NX_NEW_COPY_REV
preference . . . . . . . . . . . . . . . . . . . . . 9-39 preference . . . . . . . . . . . . . . . . . . . . . 5-79
TC_KEEP_SYSTEM_LOG variable . . . 3-11 TC_NX_NEW_NR_FORMS
TC_language_data_entry preference . . . 5-59 preference . . . . . . . . . . . . . . . . . . . . . 5-80
TC_language_default preference . . . . . . 5-61 TC_NX_nonmaster_additional_forms
TC_language_localization_display . . . . 5-62 preference . . . . . . . . . . . . . . . . . . . . . 5-80
TC_language_localized_property_value_ TC_NX_save_precise_on_uprev
display . . . . . . . . . . . . . . . . . . . . . . . 5-62 preference . . . . . . . . . . . . . . . . . . . . . 5-81
TC_language_localized_property_value_ TC_NX_Unit_Of_Measure_As_Geometric_List
entry . . . . . . . . . . . . . . . . . . . . . . . . 5-63 preference . . . . . . . . . . . . . . . . . . . . . 5-81
TC_language_search . . . . . . . . . . . . . . 5-64 TC_NX_Unit_Of_Measure_Each_List
TC_LAST_USED_PATTERNS preference . . . . . . . . . . . . . . . . . . . . . 5-81
preference . . . . . . . . . . . . . . . . . . . . . 22-4 TC_NX_UPDATE_ATTRIBUTES
TC_LIBRARY variable . . . . . . . . . . . . 3-11 preference . . . . . . . . . . . . . . . . . . . . . 5-82
TC_LOG variable . . . . . . . . . . . . . . . . 3-11 TC_NX_View_Type preference . . . . . . . 5-82
TC_LOG_DIR variable . . . . . . . . . . . . 3-11 TC_ODBC_release_status
TC_mail_interval preference . . . . . . . . 5-67 preference . . . . . . . . . . . . . . . . . . . . 23-52
TC_Manufacturer_info_form TC_ods_client_def_timeout
TC_markup_named_ref preference . . . 10-70 TC_ods_client_extra_attributes
TC_master_locale_<site_name> preference . . . . . . . . . . . . . . . . . . . . 18-38
preference . . . . . . . . . . . . . . . . . . . . 18-37 TC_ods_client_initial_timeout
TC_max_number_of_retries preference . . . . . . . . . . . . . . . . . . . . 18-40
preference . . . . . . . . . . . . . . . . . . . . 10-70 TC_ods_proxy_server_site_table
TC_modified_only_export preference . . . . . . . . . . . . . . . . . . . . 18-40
preference . . . . . . . . . . . . . . . . . . . . 18-37 TC_on_demand_sync_broadcast_mode
TC_modified_only_export role-based preference . . . . . . . . . . . . . . . . . . . . 18-40
preference . . . . . . . . . . . . . . . . . . . . 18-21 TC_ONLINE_HELP variable . . . . . . . . 3-11
TC_MSG_ROOT variable . . . . . . . . . . . 3-11 TC_organization_id preference . . . . . . 18-84
TC_multi_site_ada_license_user_bypass TC_ownership_export preference . . . . 18-41
preference . . . . . . . . . . . . . . . . . . . . . 5-25 TC_ownership_export role-based
TC_multi_site_project_member_bypass preference . . . . . . . . . . . . . . . . . . . . 18-20
preference . . . . . . . . . . . . . . . . . . . . . . 6-5 TC_part_quote_rel_relation_primary
TC_name_delimiter preference . . . . . . 10-71 preference . . . . . . . . . . . . . . . . . . . . 22-63
TC_name_sequence preference . . . . . . 10-71 TC_pattern_match_style preference . . 10-72
TC_no_obsolete_message variable . . . . 3-11 TC_PERFORMANCE_MONITOR
TC_notification_msg_ext preference . . . 9-13 variable . . . . . . . . . . . . . . . . . . . . . . 3-11
TC_NX_allow_attrsync_master_with_item TC_plmxml_import_item_filter
TC_NX_Allow_Deepcopy preference . . . 5-75 TC_plmxml_sync_dataset
TC_NX_ATTRIBUTES_FORM preference . . . . . . . . . . . . . . . . . . . . 18-42
preference . . . . . . . . . . . . . . . . . . . . . 5-75 TC_POM_JOURNALLING environment
TC_NX_Database_Attributes_For_Load variable . . . . . . . . . . . . . . . . . . . . . . . 2-2
preference . . . . . . . . . . . . . . . . . . . . . 5-75 TC_POM_JOURNALLING variable . . . 3-12
TC_NX_DEFAULT_PART variable . . . . 3-11 TC_Populate_FSC_Server_Targets . . . . 9-36
TC_NX_DeleteMarkupsOnDrawing TC_post_export_script preference . . . . 18-42
SheetImport preference . . . . . . . . . . . 5-77 TC_pre_import_script preference . . . . 18-43
TC_NX_DrawingSheet_Deletion_Pattern tc_preferences.xml preference file . . . . . 5-68
preference . . . . . . . . . . . . . . . . . . . . . 5-77 Tc_preserve_replica_pfmember_ownership
TC_NX_FileNewPAXFiles_NX<version> preference . . . . . . . . . . . . . . . . . . . . 18-43
preference . . . . . . . . . . . . . . . . . . . . . 20-9 TC_prevent_appr_query_on_corrupt_root
TC_NX_Foreign_Datasets preference . . 5-78 preference . . . . . . . . . . . . . . . . . . . . . 19-4
TC_NX_Navigator_Override_NX_Load_ TC_PRINTER variable . . . . . . . . . . . . 3-12
Option preference . . . . . . . . . . . . . . . 5-79 tc_profilevars script . . . . . . . . . . . . . . . . 1-4

Index
TC_Program_Preferred_Items_relation_ TC_remote_checkin_preserve_
primary preference . . . . . . . . . . . . . . . 6-3 replica_owning_user_and_group
TC_project_bom_2nd_level_propagate preference . . . . . . . . . . . . . . . . . . . . 18-50
preference . . . . . . . . . . . . . . . . . . . . . . 6-4 TC_remote_checkin_relation_send_as_replica
TC_Project_DefaultChildProperties preference . . . . . . . . . . . . . . . . . . . . 18-51
preference . . . . . . . . . . . . . . . . . . . . . . 6-3 TC_remove_file_on_check_in
TC_Project_PseudoFolder preference . . . 6-3 preference . . . . . . . . . . . . . . . . . . . . 10-73
TC_project_validate_conditions TC_rendering_update_lmd
preference . . . . . . . . . . . . . . . . . . . . . . 6-2 preference . . . . . . . . . . . . . . . . . . . . 18-46
Tc_publish_pfdata_with_assemblies TC_replica_volume preference . . . . . . 18-51
preference . . . . . . . . . . . . . . . . . . . . 18-44 TC_replication_exclude_types
Tc_publish_pfmembers_with_pftemplate preference . . . . . . . . . . . . . . . . . . . . 18-51
preference . . . . . . . . . . . . . . . . . . . . 18-44 TC_Report_Transfer_Area
Tc_publish_pftemplate_with_pfmember preference . . . . . . . . . . . . . . . . . . . 10-133
preference . . . . . . . . . . . . . . . . . . . . 18-45 TC_retain_group_on_import
TC_publishable_classes preference . . . 18-45 preference . . . . . . . . . . . . . . . . . . . . 18-52
TC_QRY_display_latest_dataset_only TC_retry_time preference . . . . . . . . . 10-73
preference . . . . . . . . . . . . . . . . . . . . 10-72 TC_ROLE_PFILE preference . . . . . . . 10-74
TC_QRY_search_by_rev_rule TC_ROOT variable . . . . . . . . . . . . . . . 3-12
preference . . . . . . . . . . . . . . . . . . . . 10-72 TC_SAP_alt_bomview_file
TC_Quality_Document_relation_primary preference . . . . . . . . . . . . . . . . . . . . 23-50
preference . . . . . . . . . . . . . . . . . . . . 22-63 TC_SAP_cad_tables_path
TC_RA_server_parameters preference . . . . . . . . . . . . . . . . . . . . 23-51
preference . . . . . . . . . . . . . . . . . . . . 15-13 TC_SAP_sapcad_dir preference . . . . . 23-51
TC_reference_update_lmd TC_Schematic_BOMView_Types
TC_refresh_notify preference . . . . . . . . 9-14 TC_Security_Logging preference . . . . . 9-37
TC_refresh_notify_list_maximum TC_send_to_external_system
TC_refresh_notify_pull_time_interval TC_session_clearance preference . . . . . 5-25
preference . . . . . . . . . . . . . . . . . . . . . 9-16 TC_set_current_project preference . . . . . 6-5
TC_refresh_notify_scope preference . . . 9-14 TC_sfr_process_life_time preference . . . 9-41
TC_refresh_notify_subscribe_to_types TC_sfr_recovery_interval preference . . . 9-41
preference . . . . . . . . . . . . . . . . . . . . . 9-15 TC_show_all_user_projects . . . . . . . . . . 6-6
TC_refresh_notify_timed_out TC_show_checkedout_icon
TC_register_internal_service_modules TC_show_checkout_objects_on_exit
TC_relation_export_hidden role-based TC_SHOW_OPEN_IN_IDEAS_BUTTON
TC_relation_export_on_transfer TC_show_open_in_nx_button
preference . . . . . . . . . . . . . . . 18-47–18-48 preference . . . . . . . . . . . . . . . . . . . . 19-36
TC_relation_required_on_export TC_show_open_in_pse_button
TC_relation_required_on_transfer TC_show_open_in_vmu_button
preference . . . . . . . . . . . . . . . 18-47–18-48 preference . . . . . . . . . . . . . . . . . . . . . 21-9
TC_releasable_logical_types TC_SLOW_SQL environment variable . . 2-3
preferences . . . . . . . . . . . . . . . . . . . 22-25 TC_SLOW_SQL variable . . . . . . . . . . . 3-12
TC_remote_checkin_assy_option TC_SOA_MAX_PROPERTIES
preference . . . . . . . . . . . . . . . . . . . . 18-48 variable . . . . . . . . . . . . . . . . . . . . . . 3-12
TC_remote_checkin_exclude_relations TC_SPSD_FOLDER preference . . . . . . 5-83
preference . . . . . . . . . . . . . . . . . . . . 18-49 TC_SPSD_FOLDER_PATH
preference . . . . . . . . . . . . . . . . . . . . . 5-83

Index
TC_SQL_DEBUG environment TC_USE_DEFAULT_EXPORT_SITES

variable . . . . . . . . . . . . . . . . . . . . . . . 2-2 environment variable . . . . . . . . . . . . . 3-14
TC_SQL_DEBUG variable . . . . . . . . . . 3-12 TC_use_group_admin_as_default_replica_
TC_SSO_APP_ID variable . . . . . . . . . . 3-13 owner preference . . . . . . . . . . . . . . . 18-56
TC_SSO_CHANGE_PASSWORD_PAGE TC_USE_LOV_SHARED_MEMORY
variable . . . . . . . . . . . . . . . . . . . . . . 3-13 variable . . . . . . . . . . . . . . . . . . . . . . 3-14
TC_SSO_LOGIN_PAGE variable . . . . . 3-13 TC_USE_PREFS_SHARED_MEMORY
TC_SSO_LOGIN_URL variable . . . . . . 3-13 variable . . . . . . . . . . . . . . . . . . . . . . 3-14
TC_SSO_SERVICE variable . . . . . . . . 3-12 TC_use_tc_alias_in_pa8 preference . . . . 5-67
TC_STAGING_AREA preference . . . . . 9-26 TC_USE_TEST_ATTR_MAPPINGS
TC_Store_and_Forward preference . . . . . 9-6 preference . . . . . . . . . . . . . . . . . . . . . 5-84
TC_Store_and_Forward_Transfer_Delay TC_USE_TEST_ATTR_MAPPINGS
preference . . . . . . . . . . . . . . . . . . . . . . 9-7 variable . . . . . . . . . . . . . . . . . . . . . . 3-14
TC_stub_dataset_files_after_ownership_ TC_user_delimiters preference . . . . . . 10-76
transfer preference . . . . . . . . . . . . . 18-52 TC_USER_LIB variable . . . . . . . . . . . . 3-14
TC_subscribable_replica_classes TC_USER_MSG_DIR variable . . . . . . . 3-14
preference . . . . . . . . . . . . . . . . . . . . 18-53 TC_USER_PFILE preference . . . . . . . 10-75
TC_subscription preference . . . . . . . . . 9-13 TC_USER_TOOLS variable . . . . . . . . . 3-14
TC_subscription_log_event_and_action_ TC_USER_UID_DIR variable . . . . . . . . 3-14
status . . . . . . . . . . . . . . . . . . . . . . . . 9-19 TC_ValidApprovedStatus
TC_subscriptionmgrd_cloning_interval preference . . . . . . . . . . . . . . . . . . . . 19-76
preference . . . . . . . . . . . . . . . . . . . . . 9-12 TC_validate_stub_tickets
TC_subscriptionmgrd_max_subscriptions_to_ preference . . . . . . . . . . . . . . . . . . . . 18-56
dispatch preference . . . . . . . . . . . . . . 9-12 TC_Validation_Datasettype
TC_subscriptionmgrd_processing_hours preference . . . . . . . . . . . . . . . . . . . . 5-116
preference . . . . . . . . . . . . . . . . . . . . . 9-11 TC_VALIDATION_duplicate_nx_valdata
TC_subscriptionmgrd_sleep_minutes _error_on_import . . . . . . . . . . . . . . . 5-116
preference . . . . . . . . . . . . . . . . . . . . . 9-11 TC_VALIDATION_FILE_TYPES
TC_supercedure_export preference . . . 12-18 preference . . . . . . . . . . . . . . . . . . . . 5-117
TC_Supplier_info_form preference . . . 22-64 TC_VALIDATION_mandatory_ checkers_
TC_suppress_Edit_Latest_Menu required . . . . . . . . . . . . . . . . . . . . . 5-117
preference . . . . . . . . . . . . . . . . . . . . 10-74 TC_VALIDATION_PROGRAM . . . . . . 5-118
TC_suppress_inactive_group_members TC_Validation_relation_primary
TC_suppress_report_designs TC_VALIDATION_RESULT_ALLOW_
preference . . . . . . . . . . . . . . . . . . . 10-132 REPLICA_OBJECT preference . . . . . 5-118
TC_sync_max_assy_level TC_VALIDATION_RULE_SET_ITEM_
preference . . . . . . . . . . . . . . . . . . . . 18-53 REVISIONS . . . . . . . . . . . . . . . . . . 5-119
TC_sync_revision_rules preference . . . 18-54 TC_VALIDATION_run_validation_hidden_
TC_System_Logging preference . . . . . . 9-27 agents preference . . . . . . . . . . . . . . 5-119
TC_Thumbnail_Tooltip_Properties TC_VALIDATION_STYLESHEET_
preference . . . . . . . . . . . . . . . . . . . . 10-75 DATASETNAME . . . . . . . . . . . . . . . 5-119
TC_TMP_DIR preference . . . . . . . . . . . 9-40 TC_VALIDATION_TIMESTAMP_NREFS
TC_TMP_DIR variable . . . . . . . . . . . . 3-13 preference . . . . . . . . . . . . . . . . . . . . 5-120
TC_TRACEBACK environment TC_VALIDATION_USE_PLMXML
TC_TRACEBACK variable . . . . . . . . . . 3-13 TC_Validation_Utility preference . . . . 5-121
TC_transfer_area preference . . . . . . . 18-54 TC_VALIDATION_ViewValidation
TC_TransferMode_XMLReport WithRuleSetColumnPreferences . . . . 5-122
preference . . . . . . . . . . . . . . . . . . . 10-132 TC_VALIDATION_ViewValidation
TC_truncate_file_name preference . . . 18-55 WithRuleSetColumn Width
TC_ugmaster_name_separator Preferences . . . . . . . . . . . . . . . . . . . 5-122
preference . . . . . . . . . . . . . . . . . . . . . 5-78 TC_vendor_part_rel_relation_primary
preference . . . . . . . . . . . . . . . . . . . . 22-64

Index
TC_Volume_Failover_Trigger TCPublish_synchronized_asset_relations
TC_Volume_Failover_Volume_Name TCPublishing_Activities_Role
TC_VOLUME_MONITOR_CRITICAL_ TCPublishing_Aliases .IMAN_
LEVEL preference . . . . . . . . . . . . . . . 9-30 MEWorkInstruction preference . . . . . 20-50
TC_VOLUME_MONITOR_WARNING_ TCPublishing_Aliases.Activities
LEVEL preference . . . . . . . . . . . . . . . 9-30 preference . . . . . . . . . . . . . . . . . . . . 20-51
TC_Volume_Status_Resync_Interval TCPublishing_Default_Alias_File
TC_wc_allow_subgroup_default TCSSO_LOGIN_SERVICE_URL
preference . . . . . . . . . . . . . . . . . . . . 10-77 variable . . . . . . . . . . . . . . . . . . . . . . 3-15
TC_wc_setting_modifiable_default TcSubscription ColumnWidthPreferences
TC_wc_show_all preference . . . . . . . . 10-78 TcSubscriptionColumnPreferences
TC_WEB_NO_CACHE variable . . . . . . 3-15 preference . . . . . . . . . . . . . . . . . . . . . 9-19
TC_WSDL_MAX_PROPERTIES TcUseAppLauncher preference . . . . . 10-100
variable . . . . . . . . . . . . . . . . . . . . . . 3-15 TCVIEWER_default_workflow_view
TC_XML_ENCODING . . . . . . . . . . . . . 3-15 preference . . . . . . . . . . . . . . . . . . . . . 11-9
TcActionColumnPreferences TCViewMarkupApplicationPref
TcActionColumnWidthPreferences TCVIS_ALSG_ENABLED variable . . . . 3-15
preference . . . . . . . . . . . . . . . . . . . . . 9-21 Teamcenter Automotive Edition
TCAE_autogen_name_form_types preferences . . . . . . . . . . . . . . . . . . . . 22-4
preference . . . . . . . . . . . . . . . . . . . . . 22-9 Teamcenter Integration for AutoCAD
TCAE_installation_level preference . . 22-18 preferences . . . . . . . . . . . . . . . . . . . 23-32
TCAllowedChildTypes_ ACAD_COMPONENT_ONLY_
<ItemTypeOrGDEType> MODE . . . . . . . . . . . . . . . . . . . 23-32
preference . . . . . . . . . . . . . . . . . . . . 19-87 Teamcenter Integration for NX I-deas
TCAllowedParentTypes_itemtype . . . . 19-88 preferences . . . . . . . . . . . . . . . . . . . 23-46
TCCheckoutReserveOnly preference . . . 5-23 IDEAS_manager_library . . . . . . . . 23-46
TCDefaultKeepLimit preference . . . . . . 5-24 TC_SHOW_OPEN_IN_IDEAS_
TCDefaultKeepLimitByType BUTTON . . . . . . . . . . . . . . . . . 23-46
preference . . . . . . . . . . . . . . . . . . . . . 5-24 Teamcenter Integration for NX
TCEnforceSingleType preference . . . . 19-87 preferences . . . . . . . . . . . . . . . . 4-11, 5-68
TcEventColumnPreferences API_ugpart_attr_titles . . . . . . . . . . . 5-68
preference . . . . . . . . . . . . . . . . . . . . . 9-20 <DATASET TYPE>_saveas_
TcEventColumnWidthPreferences pattern . . . . . . . . . . . . . . . . . . . . 5-73
preference . . . . . . . . . . . . . . . . . . . . . 9-20 DATASET_saveas_allow_
TCPUBLISH_BATCH_<role>_ duplicates . . . . . . . . . . . . . . . . . . 5-69
PAGE_TEMPLATE_FAVORITES DATASET_saveas_allow_name_
preference . . . . . . . . . . . . . . . . . . . . 20-55 modification . . . . . . . . . . . . . . . . 5-69
TCPUBLISH_BATCH_<role>_ DATASET_saveas_always_copy . . . . . 5-70
PORTFOLIO_TEMPLATE_FAVORITES DATASET_saveas_force_name_
preference . . . . . . . . . . . . . . . . . . . . 20-56 validation . . . . . . . . . . . . . . . . . . 5-70
TCPUBLISH_BATCH_<role>_TEMPLATES DATASET_saveas_never_copy . . . . . 5-71
preference . . . . . . . . . . . . . . . . . . . . 20-55 DATASET_saveas_owner . . . . . . . . . 5-71
TCPUBLISH_BATCH_CLASSES DATASET_saveas_pattern . . . . . . . . 5-72
preference . . . . . . . . . . . . . . . . . . . . 20-56 TC_default_part_type . . . . . . . . . . . . 5-74
TCPUBLISH_BATCH_ROLE TC_NX_allow_attrsync_master_with_
preference . . . . . . . . . . . . . . . . . . . . 20-55 item . . . . . . . . . . . . . . . . . . . . . . 5-74
TCPublish_managed_asset_properties TC_NX_Allow_Deepcopy . . . . . . . . . . 5-75
preference . . . . . . . . . . . . . . . . . . . . 20-54 TC_NX_ATTRIBUTES_FORM . . . . . 5-75

Index
TC_NX_Database_Attributes_For_ AppInterface_TCPublishing
Load . . . . . . . . . . . . . . . . . . . . . 5-75 TechnicalPortfolio_shown_
TC_NX_DeleteMarkupsOnDrawing relations . . . . . . . . . . . . . . . . . . 20-48
SheetImport . . . . . . . . . . . . . . . . 5-77 Baseline_omitted_occurrence_
TC_NX_DrawingSheet_Deletion_ types . . . . . . . . . . . . . . . . . . . . . 20-1
Pattern . . . . . . . . . . . . . . . . . . . . 5-77 Clone_Pending_Release_Status . . . . 20-28
TC_NX_Foreign_Datasets . . . . . . . . . 5-78 Clone_Secured_Release_Status . . . . 20-28
TC_NX_Navigator_Override_NX_Load_ controllingOccsFor
Option . . . . . . . . . . . . . . . . . . . . 5-79 ProcessConfiguration . . . . . . . . . . 20-2
TC_NX_NEW_COPY_REV . . . . . . . . 5-79 DefaultAccountability
TC_NX_NEW_NR_FORMS . . . . . . . . 5-80 CheckProperties . . . . . . . . . . . . 20-33
TC_NX_nonmaster_additional_ Enterprise BOP preferences . . . . . . 20-62
forms . . . . . . . . . . . . . . . . . . . . . 5-80 FindCheckedOutColumns
TC_NX_Unit_Of_Measure_As_Geometric_ ShownPref . . . . . . . . . . . . . . . . 20-13
List . . . . . . . . . . . . . . . . . . . . . . 5-81 FindCheckedOutColumns
TC_NX_Unit_Of_Measure_Each_ ShownWidthPref . . . . . . . . . . . . 20-14
List . . . . . . . . . . . . . . . . . . . . . . 5-81 GDEOcc_display_instance_num_for_
TC_NX_UPDATE_ATTRIBUTES . . . 5-82 types . . . . . . . . . . . . . . . . . . . . 20-13
TC_NX_View_Type . . . . . . . . . . . . . 5-82 GenericBOPAllowedTemplates . . . . 20-68
TC_SPSD_FOLDER . . . . . . . . . . . . . 5-83 GenericBOPTemplate . . . . . . . . . . . 20-67
TC_SPSD_FOLDER_PATH . . . . . . . . 5-83 HRN_associated_part_relation_
TC_UG_save_precise_on_uprev . . . . . 5-81 secondary . . . . . . . . . . . . . . . . . 22-46
TC_USE_TEST_ATTR_ HRN_fixing_assignment_relation_
MAPPINGS . . . . . . . . . . . . . . . . 5-84 primary . . . . . . . . . . . . . . . . . . 22-48
TRACE_BACK . . . . . . . . . . . . . . . . 5-87 HRN_node_referenced_component_
UGhookupPartDisplayPreference . . . 5-87 relation_secondary . . . . . . . . . . 22-46
UGhookupStructureUpdate HRN_part_data_relation_
OnLoad . . . . . . . . . . . . . . . . . . . 5-86 primary . . . . . . . . . . . . . . . . . . 22-47
UGhookupStructureUpdate HRN_wire_length_data_relation_
OnSave . . . . . . . . . . . . . . . . . . . 5-86 primary . . . . . . . . . . . . . . . . . . 22-45
UGII_KEEP_SYSTEM_LOG . . . . . . . 5-87 IMAN_MEWorkInstruction_relation_
UGII_OPTION . . . . . . . . . . . . . . . . 5-88 primary . . . . . . . . . . . . . . . . . . 20-53
UGII_TMP_DIR . . . . . . . . . . . . . . . . 5-88 IMAN_PortfolioConfiguredPage_relation_
UGMAN_InsertItem . . . . . . . . . . . . 5-84 primary . . . . . . . . . . . . . . . . . . 20-52
UGMAN_PartType . . . . . . . . . . . . . . 5-85 IMAN_PortfolioPage_relation_
UGMAN_ShowPartType . . . . . . . . . . 5-85 primary . . . . . . . . . . . . . . . . . . 20-52
UGMAN_UGPARTNameWRev . . . . . 5-85 IMAN_PublishingPageAssetContext_
Teamcenter LDAP synchronization relation_primary . . . . . . . . . . . . 20-48
preferences . . . . . . . . . . . . . . . . . . . . 5-95 IMAN_TCPublishedPortfolio_relation_
Teamcenter services preferences . . . . . . 5-91 primary . . . . . . . . . . . . . . . . . . 20-48
SOA_MaxOperationBracket IPADefaultEmailMessage . . . . . . . . . 20-8
InactiveTime . . . . . . . . . . . . . . . 5-91 ItemRevision_TCPublishingPage_default_
SOA_MaxOperationBracketTime . . . 5-91 relation . . . . . . . . . . . . . . . . . . 20-49
Teamcenter’s manufacturing process Manufacturing features
management preferences . . . . . . . . . . 20-1 preferences . . . . . . . . . . . . . . . . 20-76
2D_Viewer_default_load_relation . . 20-12 Manufacturing search
AccountabilityCheck preferences . . . . . . . . . . . . . . . . 20-58
ReportStylesheetName . . . . . . . 20-34 ME_Proximity_FilteredIPA_
AdditionalAccountability suffix . . . . . . . . . . . . . . . . . . . . 20-60
CheckProperties . . . . . . . . . . . . 20-33 ME_Proximity_search_result_occ_group_
AppInterface_TCPublishing type . . . . . . . . . . . . . . . . . . . . . 20-59
TechnicalPortfolio_default_ ME_Proximity_search_result_occ_
relation . . . . . . . . . . . . . . . . . . 20-47 type . . . . . . . . . . . . . . . . . . . . . 20-59

Index
ME_Proximity_search_result_root_ MEGANTTPropagateDuration
name . . . . . . . . . . . . . . . . . . . . 20-59 UpToLevelEnabled . . . . . . . . . . 20-76
MEAccountabilityCheckEnable MEGenericBOP.MEGenericBOP.Paste
FilteringRules . . . . . . . . . . . . . . 20-36 DuplicateTemplate . . . . . . . . . . 20-69
MEAccountabilityCheckEnable MEGenericBOP.MEProductBOP.Paste
NetEffectivity . . . . . . . . . . . . . . 20-36 DuplicateTemplate . . . . . . . . . . 20-69
MEAccountabilityCheckSource MEGenericBopContextColumns
StructureExpansionFilterRules . . 20-35 ShownPref . . . . . . . . . . . . . . . . 20-62
MEAccountabilityCheckTarget MEGenericBopContextColumnsShown
StructureExpansionFilterRules . . 20-35 WidthsPref . . . . . . . . . . . . . . . . 20-62
MEActivityTypeColors . . . . . . . . . . 20-40 MEGenericBopContextPartition
MEAdvancedSearchResultsView ColumnsShownWidthsPref . . . . . 20-64
ColumnsShownPref . . . . . . . . . . 20-60 MEGenericBopContextPartitionColumns
MEAdvancedSearchResultsView ShownPref . . . . . . . . . . . . . . . . 20-63
ColumnsShownWidthPref . . . . . 20-60 MEHideChangesIconsForAttributes . . 20-20
MEAlignedPropertiesList . . . . . . . . . 20-2 MEImportMFGsManufacturing
MEAlignedPropertiestoExclude FeatureIdAttributeName . . . . . . 20-77
FromDetection . . . . . . . . . . . . . . 20-3 MEImportMFGsPartIdAttribute
MEAlignedPropertiestoExclude Name . . . . . . . . . . . . . . . . . . . . 20-77
FromInitialization . . . . . . . . . . . . 20-3 MELineLinkedIconsProperty . . . . . 20-12
MEAlignedPropertiestoExclude MELogicalDesignatorDelimiter . . . . 20-66
FromSync . . . . . . . . . . . . . . . . . . 20-4 MELogicalDesignatorForm
MEAlignmentCheckReport NameSuffix . . . . . . . . . . . . . . . 20-66
Definition . . . . . . . . . . . . . . . . . . 20-4 MEManufacturingDefaultBVR . . . . . 20-5
MEAlignmentCheckReportLocation . . 20-4 MEMFGDisplayName . . . . . . . . . . 20-22
MEAlignmentCheckReport MEMFGView_AssignmentFilter
Stylesheet . . . . . . . . . . . . . . . . . . 20-5 DefaultValue . . . . . . . . . . . . . . . 20-80
MEAllocatedTimeReport MEMFGViewColumnShownPref . . . 20-78
DefinitionID . . . . . . . . . . . . . . . 20-42 MEMFGViewShownColumn
MEAllocatedTimeReportStylesheet . . 20-43 WidthsPref . . . . . . . . . . . . . . . . 20-79
MEAPCSearchType . . . . . . . . . . . . 20-61 MEMFGViewSubPanelColumn
MEAssignCustomized ShownPref . . . . . . . . . . . . . . . . 20-80
OccurrenceType . . . . . . . . . . . . . 20-6 MEMFGViewSubPanelShown
MEAssignmentsViewColumns ColumnWidthsPref . . . . . . . . . . 20-80
ShownPref . . . . . . . . . . . . . . . . 20-65 MENEWMFG_
MEAssignmentsViewColumns DefaultJTDatasetName . . . . . . . 20-77
ShownWidthPref . . . . . . . . . . . . 20-65 MENEWMFG_
MEAvailableTimeUnits . . . . . . . . . 20-38 DeffaultJTFileName . . . . . . . . . 20-78
MEBlankDisplayTypes . . . . . . . . . . 20-19 MENEWMFG_
MEConsiderFlowsOnReSequence . . 20-23 LastJTFilePathBrowsed . . . . . . 20-78
MECopyIdInContextLowerLevels . . 20-21 MEOccTypeConsumed . . . . . . . . . . . 20-7
MECopyIdInContextToAssignedLine . . 20-21 MEOperationActivities
MECurrentTimeUnit . . . . . . . . . . . 20-39 FilteredComponents . . . . . . . . . 20-40
MEDataPanelPosition . . . . . . . . . . 20-18 MEPADChildTypesPref . . . . . . . . . 20-58
MEDataSetsToBeCheckoutFor MEProductBOP.MEGenericBOP.Paste
ProcessSimulate . . . . . . . . . . . . 20-83 DuplicateTemplate . . . . . . . . . . 20-71
MEDefaultActivityType . . . . . . . . . 20-41 MEProductBOP.MEProductBOP.Paste
MEExpandFirstLevelOnLoad . . . . . 20-18 DuplicateTemplate . . . . . . . . . . 20-70
MEExpandToSelection . . . . . . . . . . 20-18 MEProductBopContextColumns
MEFormsToBeCheckoutFor ShownPref . . . . . . . . . . . . . . . . 20-62
ProcessSimulate . . . . . . . . . . . . 20-84 MEProductBopContextColumnsShown
MEGANTTPropagateDuration WidthsPref . . . . . . . . . . . . . . . . 20-63
UpToLevel . . . . . . . . . . . . . . . . 20-75 MEProductBopContextPartition
ColumnsShownPref . . . . . . . . . . 20-64

Index
MEProductBopContextPartition MEWiWorkInstructionTemplate . . . 20-81

ColumnsShownWidthsPref . . . . . 20-64 MPP_
MEPSDTableColumnsShownPref . . 20-58 BrokenLinkSearchCriteriaList . . . 20-9
MEPSDTableColumnsShownPref. MPP_DefaultCandidateSearch
SORTING_COLUMN . . . . . . . . 20-57 Criteria . . . . . . . . . . . . . . . . . . . 20-8
MEPSDTableShownColumn MRMItemTypes . . . . . . . . . . . . . . . 20-22
WidthsPref . . . . . . . . . . . . . . . . 20-57 MRMPropagationRevisionRule . . . . . 20-7
MERelationTypePartsAssembled . . . 20-16 MSE_load_related_product_process_
MERelationTypePartsAssigned . . . . 20-15 plant . . . . . . . . . . . . . . . . . . . . 20-20
MERelationTypePartsConsumed . . . 20-15 NX_supported_operation_types . . . . . 20-9
MERelationTypePartsDisassembled . . 20-16 PasteDuplicateTemplates . . . . . . . . 20-71
MERelationTypePartsFeature . . . . . 20-17 PertChart.<object_type>.GColor . . . 20-29
MERelationTypePartsHandled . . . . 20-16 PertChart.<object_type>.Text . . . . . 20-29
MERelationTypePartsOther PertChart.ActivityDefault.GColor . . 20-29
Assigned . . . . . . . . . . . . . . . . . . 20-17 PertChart.ActivityDefault.Text . . . . 20-29
MERelationTypeUsedEquipment . . 20-15 PertChart.AutoSizeMode . . . . . . . . 20-30
MEReportColumnsFor PertChart.BoxAutoSizeMaxWidth . . 20-31
ProcessSimulate . . . . . . . . . . . . 20-84 PertChart.BoxDefaultHeight . . . . . . 20-32
MEReportColumnWidthFor PertChart.BoxDefaultWidth . . . . . . 20-31
ProcessSimulate . . . . . . . . . . . . 20-85 PertChartCreationLayout . . . . . . . . 20-32
MEResultViewSourceColumns Plant.Template . . . . . . . . . . . . . . . 20-25
ShownPref . . . . . . . . . . . . . . . . 20-36 Plant.Template.Cloning . . . . . . . . . 20-24
MEResultViewSourceColumns PLMXML_pre_expand_batch_
ShownWidthPref . . . . . . . . . . . . 20-37 size . . . . . . . . . . . . . . . . . . . . . 20-86
MEResultViewTargetColumns PLMXML_pre_expand_bop . . . . . . . 20-85
ShownPref . . . . . . . . . . . . . . . . 20-37 PLMXML_pre_expand_max_line_
MEResultViewTargetColumns limit . . . . . . . . . . . . . . . . . . . . . 20-86
ShownWidthPref . . . . . . . . . . . . 20-38 Process.Template . . . . . . . . . . . . . . 20-27
MESecondStructurePosition . . . . . . 20-17 Process.Template.Ignoring_
MEShowWeldPointsConnectedTo Consumes . . . . . . . . . . . . . . . . . 20-27
ConfiguredOutParts . . . . . . . . . 20-79 Process.Template.Mapping_
METIMEAllocatedTime Consumes . . . . . . . . . . . . . . . . . 20-25
PopulationMode . . . . . . . . . . . . 20-44 Process.Template.Referencing_
METimeAnalysisReport Consumes . . . . . . . . . . . . . . . . . 20-26
DefinitionID . . . . . . . . . . . . . . . 20-42 Product.Template . . . . . . . . . . . . . . 20-24
METimeAnalysisReportStylesheet . . 20-43 Product.Template.Cloning . . . . . . . 20-23
METimeDataCardConversion ProductBOPAllowedTemplates . . . . 20-68
Factor . . . . . . . . . . . . . . . . . . . 20-44 ProductBOPTemplate . . . . . . . . . . . 20-67
METimeDataCardPath . . . . . . . . . . 20-43 ReportXMLGenerationRules . . . . . . 20-10
METIMEPopulateAllocatedTime <TC Publishing Page type>_
UpToLevel . . . . . . . . . . . . . . . . 20-46 DefaultChildProperties . . . . . . . 20-50
METIMEPopulateAllocatedTime <TC Publishing Technical Portfolio
UpToLevelEnabled . . . . . . . . . . 20-46 type>_DefaultChildProperties . . 20-49
METIMEPopulateAllocated TC_CRF_overwrite_existing_dataset_
TimeUsedSources . . . . . . . . . . . 20-45 content . . . . . . . . . . . . . . . . . . . . 20-5
METIMEPopulateAllocatedTime TC_NX_FileNewPAXFiles_
ZeroValuesEnabled . . . . . . . . . . 20-46 NX<version> . . . . . . . . . . . . . . . . 20-9
METimesActivityShownColumn TC_show_checkout_objects_on_
Widths . . . . . . . . . . . . . . . . . . . 20-41 exit . . . . . . . . . . . . . . . . . . . . . 20-14
METimesActivityShownColumns . . 20-41 TCPUBLISH_BATCH_<role>_PAGE_
METimeTabFilteredComponents . . . 20-39 TEMPLATE_FAVORITES . . . . . 20-55
MEWiDcdNotEditableProperties . . . 20-82 TCPUBLISH_BATCH_<role>_
MEWiPreviewFormat . . . . . . . . . . . 20-82 PORTFOLIO_TEMPLATE_
MEWiStandardTextTemplate . . . . . 20-81 FAVORITES . . . . . . . . . . . . . . . 20-56

Index
TCPUBLISH_BATCH_<role>_ datasetProductVariantIntent.
TEMPLATES . . . . . . . . . . . . . . 20-55 REGISTEREDTO . . . . . . . . . . . 22-43
TCPUBLISH_BATCH_CLASSES . . 20-56 datasetProductVariantIntentCreate.
TCPUBLISH_BATCH_ROLE . . . . . 20-55 REGISTEREDTO . . . . . . . . . . . 22-44
TCPublish_managed_asset_ ESM_<Category>_Software_
properties . . . . . . . . . . . . . . . . . 20-54 Types . . . . . . . . . . . . . . . . . . . . 22-27
TCPublish_synchronized_asset_ ESM_Compatibility_Report_Excel_
relations . . . . . . . . . . . . . . . . . . 20-54 Template_Dataset . . . . . . . . . . . 22-33
TCPublishing_Activities_Role . . . . . 20-51 ESM_HW_Compatibility_Report_Excel_
TCPublishing_Aliases .IMAN_ StyleSheet_Dataset . . . . . . . . . . 22-32
MEWorkInstruction . . . . . . . . . . 20-50 ESM_HW_Compatibility_Report_HTML_
TCPublishing_Aliases.Activities . . . 20-51 StyleSheet_Dataset . . . . . . . . . . 22-31
TCPublishing_Default_Alias_File . . 20-50 ESM_HW_Compatibility_Report_
TechnicalPortfolioRoles . . . . . . . . . 20-52 TransferMode . . . . . . . . . . . . . . 22-30
TechnicalPortfolioTransferMode_IMAN_ ESM_Processor_architecture_
MEWorkInstruction . . . . . . . . . . 20-53 attr . . . . . . . . . . . . . . . . . . . . . 22-30
VisAssetPopulatedByEndobj_relation_ ESM_Processor_byteOrder_attr . . . 22-30
primary . . . . . . . . . . . . . . . . . . 20-54 ESM_processor_direct_child_of_
Teamcenter’s mechatronics process hardware . . . . . . . . . . . . . . . . . 22-28
management preferences . . . . . . . . . 22-22 ESM_Processor_is_gateway_attr . . . 22-28
APN_absolute_path_name_ ESM_Processor_linked_attr . . . . . . 22-29
separator . . . . . . . . . . . . . . . . . 22-24 ESM_Processor_memoryType_
Ccd0ColumnPreference . . . . . . . . . 22-44 attr . . . . . . . . . . . . . . . . . . . . . 22-29
CCDM_grp_rev_val . . . . . . . . . . . . 22-45 ESM_Processor_programmableInService_
Connected_ToRules . . . . . . . . . . . . 22-22 attr . . . . . . . . . . . . . . . . . . . . . 22-29
datasetParmDef.REGISTEREDTO . . 22-41 ESM_Processor_Type . . . . . . . . . . . 22-27
datasetParmDefBCDRevision. ESM_Software_Categories . . . . . . . 22-26
REGISTEREDTO . . . . . . . . . . . 22-38 ESM_SW_Compatibility_Report_Excel_
datasetParmDefBitDefRevision. StyleSheet_Dataset . . . . . . . . . . 22-32
REGISTEREDTO . . . . . . . . . . . 22-39 ESM_SW_Compatibility_Report_HTML_
datasetParmDefBoolRevision. StyleSheet_Dataset . . . . . . . . . . 22-32
REGISTEREDTO . . . . . . . . . . . 22-35 ESM_SW_Compatibility_Report_
datasetParmDefDateRevision. TransferMode . . . . . . . . . . . . . . 22-31
REGISTEREDTO . . . . . . . . . . . 22-36 GDE_exclude_list . . . . . . . . . . . . . . 22-25
datasetParmDefDblRevision. GDELink_default_type . . . . . . . . . . 22-25
REGISTEREDTO . . . . . . . . . . . 22-34 Implemented_ByRules . . . . . . . . . . 22-23
datasetParmDefHexRevision. ParmDef.RENDERING . . . . . . . . . 22-40
REGISTEREDTO . . . . . . . . . . . 22-37 ParmDefBCDRevision.RENDERING . . 22-38
datasetParmDefIntRevision. ParmDefBitDefRevision.
REGISTEREDTO . . . . . . . . . . . 22-33 RENDERING . . . . . . . . . . . . . . 22-39
datasetParmDefSEDRevision. ParmDefBoolRevision.RENDERING . . 22-35
REGISTEREDTO . . . . . . . . . . . 22-37 ParmDefDateRevision.RENDERING . . 22-36
datasetParmDefStrRevision. ParmDefDblRevision.RENDERING . . 22-34
REGISTEREDTO . . . . . . . . . . . 22-35 ParmDefHexRevision.RENDERING . . 22-36
datasetParmGrpDef. ParmDefIntRevision.RENDERING . . 22-33
REGISTEREDTO . . . . . . . . . . . 22-40 ParmDefSEDRevision.RENDERING . . 22-37
datasetParmGrpDefRevision. ParmDefStrRevision.RENDERING . . 22-34
REGISTEREDTO . . . . . . . . . . . 22-41 ParmGrpDef.RENDERING . . . . . . . 22-40
datasetParmGrpValRevision. ParmGrpDefRevision.RENDERING . . 22-41
REGISTEREDTO . . . . . . . . . . . 22-39 ParmGrpValRevision.RENDERING . . 22-38
datasetProductVariant. ProductVariant.CREATE
REGISTEREDTO . . . . . . . . . . . 22-42 RENDERING . . . . . . . . . . . . . . 22-42
datasetProductVariantCreate. ProductVariant.RENDERING . . . . . 22-42
REGISTEREDTO . . . . . . . . . . . 22-43

Index
ProductVariantIntent. TechnicalPortfolioTransferMode_IMAN_
CREATERENDERING . . . . . . . 22-44 MEWorkInstruction preference . . . . . 20-53
ProductVariantIntent. TEMP_FILESEARCHPATH variable . . 3-15
RENDERING . . . . . . . . . . . . . . 22-43 Thin clien Teamcenter’s manufacturing
Realized_ByRules . . . . . . . . . . . . . 22-24 process management preferences
SIG_asystem_source_rules . . . . . . . 22-48 TC_TransferMode_XMLReport . . . 10-132
SIG_asystem_target_rules . . . . . . . 22-49 Thin client
SIG_asystem_transmitter_rules . . . 22-49 Column and property
SIG_pvariable_rules . . . . . . . . . . . . 22-50 preferences . . . . . . . . . . . . . . . 10-118
SIG_redundant_rules . . . . . . . . . . . 22-50 Thin client column and property preferences
TCENG_releasable_logical_types . . 22-25 Folder_ColumnPreferences . . . . . . 10-121
Teamcenter’s simulation process management WEB_dataset_columns . . . . . . . . . 10-119
preferences WEB_inbox_columns . . . . . . . . . . 10-119
CAE_always_remesh . . . . . . . . . . . 23-44 WEB_po_columns . . . . . . . . . . . . 10-121
CAE_batch_meshing_always_create_ WEB_psm_columns . . . . . . . . . . . 10-120
new . . . . . . . . . . . . . . . . . . . . . 23-45 WEB_wso_columns . . . . . . . . . . . 10-121
CAE_batch_meshing_attribute . . . . 23-45 Thin client DesignContext
CAE_batch_meshing_import_file_ preferences . . . . . . . . . . . . . . . . . . 10-125
extensions . . . . . . . . . . . . . . . . 23-44 RDVThinClient
CAE_dataMapping_file . . . . . . . . . . 23-42 BomlinePropsDisplay . . . . . . . 10-126
CAE_input_geometry . . . . . . . . . . . 23-44 RDVThinClient
CAE_meshing_params_criteria_ UserProductItem . . . . . . . . . . . 10-126
source . . . . . . . . . . . . . . . . . . . 23-43 RDVThinClient
CAE_post_processor_additional_ UserrevisionRule . . . . . . . . . . 10-127
output . . . . . . . . . . . . . . . . . . . 23-41 WebDesignContextDefault
CAE_post_processor_primary_ SearchDistance . . . . . . . . . . . . 10-125
input . . . . . . . . . . . . . . . . . . . . 23-39 WebDesignContextMax
CAE_post_processor_primary_ MatchingObjects . . . . . . . . . . . 10-126
output . . . . . . . . . . . . . . . . . . . 23-40 WebDesignContextMaxMatching
CAE_post_processor_startup_ BOMLines . . . . . . . . . . . . . . . 10-125
scripts . . . . . . . . . . . . . . . . . . . 23-38 Thin client image preferences . . . . . . 10-122
CAE_post_processor_tools . . . . . . . . 23-37 WEB_fullsize_image_generate_
CAE_pre_processor_additional_ type . . . . . . . . . . . . . . . . . . . . 10-122
output . . . . . . . . . . . . . . . . . . . 23-41 WEB_image_size_horiz . . . . . . . . 10-123
CAE_pre_processor_alternate_ WEB_image_size_vert . . . . . . . . . 10-123
input . . . . . . . . . . . . . . . . . . . . 23-39 WEB_show_banner . . . . . . . . . . . 10-123
CAE_pre_processor_primary_ WEB_show_thumbnail_image . . . . 10-124
input . . . . . . . . . . . . . . . . . . . . 23-38 WEB_thumbnail_image_display_
CAE_pre_processor_primary_ type . . . . . . . . . . . . . . . . . . . . 10-124
output . . . . . . . . . . . . . . . . . . . 23-40 WEB_thumbnail_image_generate_
CAE_pre_processor_startup_ type . . . . . . . . . . . . . . . . . . . . 10-124
scripts . . . . . . . . . . . . . . . . . . . 23-37 Thin client interface interface preferences
CAE_pre_processor_tools . . . . . . . . 23-36 WEB_login_page . . . . . . . . . . . . . 10-112
CAE_simulation_tool_config_ Thin client interface preferences
dsname . . . . . . . . . . . . . . . . . . 23-46 appbar_title_contents . . . . . . . . . . . 10-99
CAE_solver_additional_output . . . . 23-42 Batch_Report_Request_File . . . . . 10-133
CAE_solver_primary_input . . . . . . . 23-39 Class_Resource_Robot . . . . . . . . . 10-131
CAE_solver_primary_output . . . . . . 23-40 Class_Resource_WeldGun . . . . . . . 10-131
CAE_solver_startup_scripts . . . . . . 23-38 Folder_ColumnPreferences . . . . . . 10-121
CAE_solver_tools . . . . . . . . . . . . . . 23-37 General . . . . . . . . . . . . . . . . . . . . . 10-99
CAE_startup_scripts . . . . . . . . . . . 23-43 JT_WEB_UI_PREF . . . . . . . . . . . 10-100
CAE_structure_map_dataset_ RDVThinClient
type . . . . . . . . . . . . . . . . . . . . . 23-42 BomlinePropsDisplay . . . . . . . 10-126
TechnicalPortfolioRoles preference . . . 20-52

Index
RDVThinClient WEB_show_thumbnail_image . . . . 10-124

UserProductItem . . . . . . . . . . . 10-126 WEB_show_unconfigured_revs . . . 10-114
RDVThinClient WEB_simple_search_queries . . . . . 10-115
UserrevisionRule . . . . . . . . . . 10-127 WEB_StationProcess_Reports . . . . 10-128
TC_Report_Transfer_Area . . . . . . 10-133 WEB_status_icons . . . . . . . . . . . . 10-107
TC_suppress_report_designs . . . . . 10-132 WEB_style_sheet_list . . . . . . . . . . 10-115
TC_TransferMode_XMLReport . . . 10-132 WEB_style_sheet_list_names . . . . 10-116
WEB_<Class>_default_type . . . . . 10-102 WEB_thumbnail_image_display_
WEB_active_optimizer_server . . . . 10-102 type . . . . . . . . . . . . . . . . . . . . 10-124
WEB_auto_assign_ds_id . . . . . . . . 10-102 WEB_thumbnail_image_generate_
WEB_Change_default_type . . . . . . 10-103 type . . . . . . . . . . . . . . . . . . . . 10-124
WEB_column_one_new_window . . 10-108 WEB_title_contents . . . . . . . . . . . 10-116
WEB_core_help_server . . . . . . . . . 10-103 WEB_unpackage_multipart . . . . . 10-117
WEB_create_<business_object>_exclude_ WEB_use_activex_lov . . . . . . . . . . 10-117
types . . . . . . . . . . . . . . . . . . . 10-108 WEB_use_lhn_home_
WEB_dataset_columns . . . . . . . . . 10-119 component . . . . . . . . . . . . . . . 10-117
WEB_dataset_shown_relations . . . 10-103 WEB_use_lhn_inbox_
WEB_dataset_upload_mode . . . . . 10-108 component . . . . . . . . . . . . . . . 10-118
Web_default_site_deployed_ app_ WEB_wso_columns . . . . . . . . . . . 10-121
name . . . . . . . . . . . . . . . . . . . 10-104 WEB_ZoneProcess_Reports . . . . . . 10-127
WEB_default_site_server . . . . . . . 10-104 WebDesignContextDefault
WEB_disable_structure_read_ SearchDistance . . . . . . . . . . . . 10-125
optimizations . . . . . . . . . . . . . 10-105 WebDesignContextMax
WEB_filter_person . . . . . . . . . . . . 10-105 MatchingObjects . . . . . . . . . . . 10-126
WEB_filter_user . . . . . . . . . . . . . 10-106 WebDesignContextMaxMatching
WEB_fullsize_image_generate_ BOMLines . . . . . . . . . . . . . . . 10-125
type . . . . . . . . . . . . . . . . . . . . 10-122 Thin client preferences . . . . . . . . . . . 10-98
WEB_help_server . . . . . . . . . . . . 10-105 WEB_protocol . . . . . . . . . . . . . . . 10-106
WEB_image_size_horiz . . . . . . . . 10-123 WEB_style_sheet . . . . . . . . . . . . . 10-115
WEB_image_size_vert . . . . . . . . . 10-123 Thin client Teamcenter’s manufacturing
WEB_inbox_columns . . . . . . . . . . 10-119 process management preferences . . 10-127
WEB_item_default_relation . . . . . 10-110 Batch_Report_Request_File . . . . . 10-133
WEB_itemrevision_default_ Class_Resource_Robot . . . . . . . . . 10-131
relation . . . . . . . . . . . . . . . . . 10-110 Class_Resource_WeldGun . . . . . . . 10-131
WEB_IWantToDefaultActions . . . . 10-111 TC_Report_Transfer_Area . . . . . . 10-133
WEB_max_search_results . . . . . . . 10-112 TC_suppress_report_designs . . . . . 10-132
WEB_MELocateCompOp_ WEB_MELocateCompOp_
Reports . . . . . . . . . . . . . . . . . 10-131 Reports . . . . . . . . . . . . . . . . . 10-131
WEB_menu_entry_new_window . . 10-109 WEB_MEPrPlantProcess_
WEB_menu_entry_suppressions . . 10-109 Reports . . . . . . . . . . . . . . . . . 10-130
WEB_MEPrPlantProcess_ WEB_MEWeldOp_Reports . . . . . . 10-130
Reports . . . . . . . . . . . . . . . . . 10-130 Web_Report_Jars . . . . . . . . . . . . . 10-133
WEB_MEWeldOp_Reports . . . . . . 10-130 WEB_StationProcess_Reports . . . . 10-128
WEB_NX_UseBookmark . . . . . . . 10-112 WEB_ZoneProcess_Reports . . . . . . 10-127
WEB_package_multipart . . . . . . . 10-113 Ticket_Expiration_Interval
WEB_packaging_extension . . . . . . 10-113 preference . . . . . . . . . . . . . . . . . . . . . 9-27
WEB_po_columns . . . . . . . . . . . . 10-121 TIE_allow_import_with_different_SML
WEB_processes . . . . . . . . . . . . . . 10-113 preference . . . . . . . . . . . . . . . . . . . . 18-64
WEB_psm_columns . . . . . . . . . . . 10-120 TIE_exp_pending_object preference . . 18-64
Web_Report_Jars . . . . . . . . . . . . . 10-133 TIE_reference_objects_list
WEB_show_banner . . . . . . . . . . . 10-123 preference . . . . . . . . . . . . . . . . . . . . 18-65
WEB_show_export_nx_assy_ TIE_validate_against_xsd
menu . . . . . . . . . . . . . . . . . . . 10-114 preference . . . . . . . . . . . . . . . . . . . . 18-66
WEB_show_summary . . . . . . . . . . 10-114 Time management preferences . . . . . . 20-38

Index
TNS_ADMIN variable . . . . . . . . . . . . . 3-15 <TypeName>_indexed_properties

TOOL_object_columns_hidden preference . . . . . . . . . . . . . . . . . . . . . 5-58
preference . . . . . . . . . . . . . . . . . . . . 10-78 <TypeName>_subscribe_to_events
TOOL_object_columns_shown preference . . . . . . . . . . . . . . . . . . . . . 9-15
preference . . . . . . . . . . . . . . . . . . . . 10-79
TOOL_object_widths_hidden U
preference . . . . . . . . . . . . . . . . . . . . 10-79
TOOL_object_widths_shown UG/Manager, see Teamcenter Integration for
preference . . . . . . . . . . . . . . . . . . . . 10-80 NX
TRACE_BACK preference . . . . . . . . . . 5-87 UGhookupPartDisplayPreference
Tracelink_deepcopy_on_Revise preference . . . . . . . . . . . . . . . . . . . . . 5-87
preference . . . . . . . . . . . . . . . . . . . . 10-80 UGhookupStructureUpdateOnLoad
Tracelink_deepcopy_on_SaveAs preference . . . . . . . . . . . . . . . . . . . . . 5-86
preference . . . . . . . . . . . . . . . . . . . . 10-80 UGhookupStructureUpdateOnSave
TransactionElement_DefaultChildProperties preference . . . . . . . . . . . . . . . . . . . . . 5-86
preference . . . . . . . . . . . . . . . . . . . . 22-98 UGII_APISERVER_PROGRAM
TransactionElement_Document_default_ variable . . . . . . . . . . . . . . . . . . . . . . 3-15
relation preference . . . . . . . . . . . . . . 22-99 UGII_BASE_DIR variable . . . . . . . . . . 3-15
TransactionElement_DocumentRevision_ UGII_KEEP_SYSTEM_LOG
default_relation preference . . . . . . . . 22-99 preference . . . . . . . . . . . . . . . . . . . . . 5-87
TransactionElement_PhysicalElement_ UGII_OPTION preference . . . . . . . . . . 5-88
default_relation preference . . . . . . . . 22-99 UGII_OPTION variable . . . . . . . . . . . . 3-16
TransactionElement_ UGII_TMP_DIR preference . . . . . . . . . 5-88
PhysicalElementRevision_default_relation UGII_USE_NEW_SURFACE_FILE_
preference . . . . . . . . . . . . . . . . . . . . 22-99 FORMAT variable . . . . . . . . . . . . . . . 3-16
TransactionElement.COLUMNS_SHOW UGII_USERFCN variable . . . . . . . . . . 3-16
preference . . . . . . . . . . . . . . . . . . . . 22-98 UGMAN_InsertItem preference . . . . . . 5-84
TransactionElement.COLUMNS_WIDTH UGMAN_PartType preference . . . . . . . 5-85
preference . . . . . . . . . . . . . . . . . . . . 22-98 UGMAN_ShowPartType preference . . . 5-85
Transient_Volume_Installation_Location UGMAN_UGPARTNameWRev
Transient_Volume_Installation_Location UGMASTER_DefaultChildProperties
variable . . . . . . . . . . . . . . . . . . . . . . 3-15 preference . . . . . . . . . . . . . . . . . . . . . 5-48
Transient_Volume_RootDir UGPART_DefaultChildProperties
Treat_Curr_Rev_As_Any_Rev UGS_LICENSE_SERVER variable . . . . 3-16
preference . . . . . . . . . . . . . . . . . . . . . . 5-6 UGSideastojt_IdeasAssembly_ets_nr_types
Treat_Next_Rev_As_Any_Rev . . . . . . . . 5-6 preference . . . . . . . . . . . . . . . . . . . . . 5-32
treeDisplayOrder preference . . . . . . . 10-81 UGSideastojt_IdeasDrawing_ets_nr_types
TYPE_DISPLAY_RULES_list_of_primary_ preference . . . . . . . . . . . . . . . . . . . . . 5-33
types preference . . . . . . . . . . . . . . . . . 5-7 UGSideastojt_IdeasPart_ets_nr_types
TYPE_DISPLAY_RULES_list_types_of_ preference . . . . . . . . . . . . . . . . . . . . . 5-33
subclasses preference . . . . . . . . . . . . . . 5-7 UGSnxtocgmdirect_ets_ds_types
<Type_Name>_DefaultChildProperties preference . . . . . . . . . . . . . . . . . . . . . 5-46
preference . . . . . . . . . . . . . . . . . . . . 10-82 UGSnxtocgmdirect_UGALTREP_ets_nr_types
<type_name>.CREATERENDERING preference . . . . . . . . . . . . . . . . . . . . . 5-44
preference . . . . . . . . . . . . . . . . . . . . 10-82 UGSnxtocgmdirect_UGMASTER_ets_nr_
<type_name>.FORMRENDERING types preference . . . . . . . . . . . . . . . . 5-45
preference . . . . . . . . . . . . . . . . . . . . 10-86 UGSnxtocgmdirect_UGPART_ets_nr_types
<type_name>.SUMMARYRENDERING preference . . . . . . . . . . . . . . . . . . . . . 5-45
preference . . . . . . . . . . . . . . . . . . . . 10-87 UGSnxtocgmdirect_UGSCENARIO_ets_nr_
type_name.RENDERING types preference . . . . . . . . . . . . . . . . 5-45
preference . . . . . . . . . . . . . . . . . . . . 10-86 UGSnxtopvdirect_ets_ds_types
<Type>_PseudoFolder preference . . . . 10-81 preference . . . . . . . . . . . . . . . . . . . . . 5-47

Index
UGSnxtopvdirect_UGALTREP_ets_nr_types NXCheckMateRevision.
preference . . . . . . . . . . . . . . . . . . . . . 5-46 SUMMARYRENDERING . . . . . 5-110
UGSnxtopvdirect_UGMASTER_ets_nr_types NXCheckMateRevSummary. SUMMARY_
preference . . . . . . . . . . . . . . . . . . . . . 5-47 REGISTEREDTO . . . . . . . . . . . 5-110
UGSnxtopvdirect_UGPART_ets_nr_types NXCheckMateSummary. SUMMARY_
preference . . . . . . . . . . . . . . . . . . . . . 5-47 REGISTEREDTO . . . . . . . . . . . 5-111
UGSproetojt_ets_ds_types NXCMValData.
preference . . . . . . . . . . . . . . . . . . . . . 5-50 CREATERENDERING . . . . . . . 5-111
UGSproetojt_ProPrt_ets_nr_types NXCMValData.
preference . . . . . . . . . . . . . . . . . . . . . 5-50 SUMMARYRENDERING . . . . . 5-112
UIL_INCLUDE variable . . . . . . . . . . . 3-15 NXCMValDataCreate. CREATE_
UNLOAD_LOGGING_LEVEL REGISTEREDTO . . . . . . . . . . . 5-111
preference . . . . . . . . . . . . . . . . . . . . . 9-36 NXCMValDataRevision.
UNLOAD_MINIMUM_LIFE SUMMARYRENDERING . . . . . 5-112
preference . . . . . . . . . . . . . . . . . . . . . 9-35 NXCMValDataRevSummary. SUMMARY_
UNLOAD_TRIGGER_CEILING REGISTEREDTO . . . . . . . . . . . 5-112
preference . . . . . . . . . . . . . . . . . . . . . 9-33 NXCMValDataSummary. SUMMARY_
UNLOAD_TRIGGER_FLOOR REGISTEREDTO . . . . . . . . . . . 5-113
preference . . . . . . . . . . . . . . . . . . . . . 9-34 NXRDDV.
User and person object mapping SUMMARYRENDERING . . . . . 5-114
preferences . . . . . . . . . . . . . . . . . . . 5-105 NXRDDVRevision.
LDAP_attribute_mapping . . . . . . . . 5-105 SUMMARYRENDERING . . . . . 5-113
User object mapping preferences NXRDDVRevSummary. SUMMARY_
LDAP_base_dn . . . . . . . . . . . . . . . 5-106 REGISTEREDTO . . . . . . . . . . . 5-113
LDAP_ignore_users . . . . . . . . . . . . 5-107 NXRDDVSummary. SUMMARY_
LDAP_user_object_class . . . . . . . . . 5-107 REGISTEREDTO . . . . . . . . . . . 5-114
LDAP_user_query_filter . . . . . . . . . 5-107 NXRDDVValData.
USER_baseline_dryrun_validator SUMMARYRENDERING . . . . . 5-115
preference . . . . . . . . . . . . . . . . . . . . . 5-26 NXRDDVValDataRevision.
User_DefaultChildProperties SUMMARYRENDERING . . . . . 5-114
preference . . . . . . . . . . . . . . . . . . . . 10-84 NXRDDVValDataRevSummary.
USER_object_columns_hidden SUMMARY_
preference . . . . . . . . . . . . . . . . . . . . 10-88 REGISTEREDTO . . . . . . . . . . . 5-115
USER_object_columns_shown NXRDDVValDataSummary. SUMMARY_
preference . . . . . . . . . . . . . . . . . . . . 10-88 REGISTEREDTO . . . . . . . . . . . 5-115
USER_object_widths_hidden TC_VALIDATION_mandatory_ checkers_
preference . . . . . . . . . . . . . . . . . . . . 10-89 required . . . . . . . . . . . . . . . . . . 5-117
USER_object_widths_shown TC_VALIDATION_PROGRAM . . . . 5-118
preference . . . . . . . . . . . . . . . . . . . . 10-89 TC_VALIDATION_RULE_SET_ITEM_
UtilizationViewColumnsShownPref REVISIONS . . . . . . . . . . . . . . . 5-119
preference . . . . . . . . . . . . . . . . . . . . 22-78 TC_VALIDATION_STYLESHEET_
DATASETNAME . . . . . . . . . . . 5-119
V TC_VALIDATION_ViewValidation
WithRuleSetColumnPreferences . . 5-122
Validation Manager preferences . . . . . 5-108 TC_VALIDATION_ViewValidation
Baseline_precondition_validation_rule WithRuleSetColumn Width
_item_revision . . . . . . . . . . . . . 5-109 Preferences . . . . . . . . . . . . . . . . 5-122
NXCheckMate. ValidationAgent_
CREATERENDERING . . . . . . . 5-109 DefaultChildProperties . . . . . . . 5-123
NXCheckMate. ValidationAgentRevision_
SUMMARYRENDERING . . . . . 5-110 DefaultChildProperties . . . . . . . 5-123
NXCheckMateCreate. CREATE_ ValidationAgentRevision_Folder_ default_
REGISTEREDTO . . . . . . . . . . . 5-109 relation . . . . . . . . . . . . . . . . . . 5-123

Index
ValidationAgentRevision_ValData_ default_ BidPackageLineItem_default_

relation . . . . . . . . . . . . . . . . . . 5-124 relation . . . . . . . . . . . . . . . . . . 22-51
ValToolAgentRevision_ BidPackageLineItem_
DefaultChildProperties . . . . . . . 5-126 DefaultChildProperties . . . . . . . 22-51
ValToolAgentRevision_Tool_ default_ BidPackageLineItem_
relation . . . . . . . . . . . . . 5-116, 5-126 PseudoFolder . . . . . . . . . . . . . . 22-51
Validation preferences BidPackageRevision_
TC_ALLOW_ADHOC_ DefaultChildProperties . . . . . . . 22-52
VALIDATIONS . . . . . . . . . . . . . 5-116 BidPackageRevision_
TC_VALIDATION_FILE_TYPES . . 5-117 PseudoFolder . . . . . . . . . . . . . . 22-52
TC_Validation_relation_primary . . . 5-118 CommercialPart_
TC_VALIDATION_RESULT_ALLOW_ DefaultChildProperties . . . . . . . 22-53
REPLICA_OBJECT . . . . . . . . . . 5-118 CommercialPart_PseudoFolder . . . . 22-53
TC_VALIDATION_run_validation_hidden_ CompanyLocation_
agents . . . . . . . . . . . . . . . . . . . 5-119 DefaultChildProperties . . . . . . . 22-54
TC_VALIDATION_TIMESTAMP_ CompanyLocation_PseudoFolder . . . 22-54
NREFS . . . . . . . . . . . . . . . . . . 5-120 ContactInCompany_relation_
TCViewMarkupApplicationPref . . . . 10-76 primary . . . . . . . . . . . . . . . . . . 22-54
VALIDATION_APPLICATIONS . . . 5-124 LocationInCompany_relation_
ValidationMasterForm primary . . . . . . . . . . . . . . . . . . 22-55
ColumnPreferences . . . . . . . . . . 5-124 ManufacturerPart
ValidationMasterFormColumn Revision.RENDERING . . . . . . . 22-57
WidthPreferences . . . . . . . . . . . 5-125 ManufacturerPart Revision.SUMMARY
VALIDATION_APPLICATIONS RENDERING . . . . . . . . . . . . . . 22-57
preference . . . . . . . . . . . . . . . . . . . . 5-124 ManufacturerPart_
ValidationAgent_ DefaultChildProperties . . . . . . . 22-55
DefaultChildProperties . . . . . . . . . . 5-123 ManufacturerPart_
ValidationAgentRevision_ DefaultPSEProperties . . . . . . . . 22-56
DefaultChildProperties . . . . . . . . . . 5-123 ManufacturerPart_PseudoFolder . . . 22-56
ValidationAgentRevision_Folder_ default_ ManufacturerPart.REGISTERED
relation . . . . . . . . . . . . . . . . . . . . . 5-123 TO . . . . . . . . . . . . . . . . . . . . . . 22-58
ValidationAgentRevision_ValData _default_ ManufacturerPart.RENDERING . . . 22-58
relation . . . . . . . . . . . . . . . . . . . . . 5-124 ManufacturerPart.SUMMARY
ValidationMasterForm RENDERING . . . . . . . . . . . . . . 22-58
ColumnPreferences . . . . . . . . . . . . . 5-124 ManufacturerPartRevision.
ValidationMasterFormColumn REGISTEREDTO . . . . . . . . . . . 22-56
WidthPreferences . . . . . . . . . . . . . . 5-125 ManufacturerPartRevSummary.
ValToolAgentRevision_ SUMMARY_
DefaultChildProperties . . . . . . . . . . 5-126 REGISTEREDTO . . . . . . . . . . . 22-57
ValToolAgentRevision_Tool_ default_ ManufacturerPartSummary.SUMMARY_
relation . . . . . . . . . . . . . . . . . . . . . 5-126 REGISTEREDTO . . . . . . . . . . . 22-59
variant_description_column_width ProvidedFrom_relation_primary . . . 22-59
preference . . . . . . . . . . . . . . . . . . . . 19-56 PseudoFolder.ContactInCompany_
variant_item_column_width ColumnPreferences . . . . . . . . . . 22-60
preference . . . . . . . . . . . . . . . . . . . . 19-56 PseudoFolder.lineitems_
variant_option_column_width ColumnPreferences . . . . . . . . . . 22-60
preference . . . . . . . . . . . . . . . . . . . . 19-56 PseudoFolder.LocationInCompany_
variant_state_column_width ColumnPreferences . . . . . . . . . . 22-60
preference . . . . . . . . . . . . . . . . . . . . 19-57 PseudoFolder.ProvidedFrom_
variant_value_column_width ColumnPreferences . . . . . . . . . . 22-61
preference . . . . . . . . . . . . . . . . . . . . 19-57 PseudoFolder.TC_part_quote_rel_
variant_values_column_width ColumnPreferences . . . . . . . . . . 22-61
preference . . . . . . . . . . . . . . . . . . . . 19-57 Quote_DefaultChildProperties . . . . 22-62
Vendor management Restricted_Vendor_Part_Statuses . . 22-62

Index
Restricted_Vendor_Statuses . . . . . . 22-62 SecondaryVMUDatasets . . . . . . . . . . 21-7

TC_Distributor_info_form . . . . . . . . 22-63 TC_DIS_2D_named_ref . . . . . . . . . . 21-7
TC_Manufacturer_info_form . . . . . . 22-63 TC_DIS_3D_named_ref . . . . . . . . . . 21-8
TC_part_quote_rel_relation_ TC_DIS_Search . . . . . . . . . . . . . . . . 21-8
primary . . . . . . . . . . . . . . . . . . 22-63 TC_Schematic_BOMView_Types . . . . 21-8
TC_Quality_Document_relation_ TC_show_open_in_vmu_button . . . . . 21-9
primary . . . . . . . . . . . . . . . . . . 22-63 VIS_multi_file_datasettypes . . . . . . . 21-9
TC_Supplier_info_form . . . . . . . . . . 22-64 VIS_simpgen_admin_group . . . . . . . 5-51
TC_vendor_part_rel_relation_ VisMarkup_relation_primary . . . . . . 21-9
primary . . . . . . . . . . . . . . . . . . 22-64 VisSession_relation_primary . . . . . . 21-10
Vendor_DefaultChildProperties . . . . 22-64 VMU_Datasets . . . . . . . . . . . . . . . 21-10
Vendor_PseudoFolder . . . . . . . . . . . 22-65 VMU_FileSearchOrder . . . . . . . . . . 21-11
VendorRevision_ VMU_RelationSearchOrder . . . . . . 21-12
DefaultChildProperties . . . . . . . 22-65 VMRepresents_relation_primary
VendorRevision_PseudoFolder . . . . . 22-66 preference . . . . . . . . . . . . . . . . . . . . 22-67
VMRepresents_relation_primary . . . 22-67 VMS_Maintain_Vendor_History
VMS_Maintain_Vendor_History . . . 22-67 preference . . . . . . . . . . . . . . . . . . . . 22-67
VMS_vendor_part_selection_rule . . 22-67 VMS_vendor_part_selection_rule
Vendor management preferences . . . . 22-51 preference . . . . . . . . . . . . . . . . . . . . 22-67
Vendor_DefaultChildProperties VMU_Datasets preference . . . . . . . . . 21-10
preference . . . . . . . . . . . . . . . . . . . . 22-64 VMU_FileSearchOrder preference . . . 21-11
Vendor_PseudoFolder preference . . . . 22-65 VMU_RelationSearchOrder
VendorRevision_DefaultChildProperties preference . . . . . . . . . . . . . . . . . . . . 21-12
preference . . . . . . . . . . . . . . . . . . . . 22-65 vrule_reln_column_width
VendorRevision_PseudoFolder preference . . . . . . . . . . . . . . . . . . . . 19-58
preference . . . . . . . . . . . . . . . . . . . . 22-66
Vis_InterOptWithProductView Dataset W
preference . . . . . . . . . . . . . . . . . . . . 19-53
VIS_multi_file_datasettypes WEB_<Class>_default_type
preference . . . . . . . . . . . . . . . . . . . . . 21-9 preference . . . . . . . . . . . . . . . . . . . 10-102
VIS_simpgen_admin_group WEB_active_optimizer_server
VisAssetPopulatedByEndobj_relation_ WEB_auto_assign_ds_id
primary preference . . . . . . . . . . . . . 20-54 preference . . . . . . . . . . . . . . . . . . . 10-102
VisMarkup_relation_primary WEB_Change_default_type
VisSession_relation_primary WEB_column_one_new_window
preference . . . . . . . . . . . . . . . . . . . . 21-10 preference . . . . . . . . . . . . . . . . . . . 10-108
VISTopLevelRef_relation_primary WEB_core_help_server preference . . 10-103
preference . . . . . . . . . . . . . . . . . . . . 19-53 WEB_create_<business_object>_exclude_
Visualization preferences . . . . . . 21-86, 21-1 types preference . . . . . . . . . . . . . . 10-108
3DMarkup_relation_primary . . . . . . 21-1 WEB_dataset_columns preference . . 10-119
DMI_markup_relation_primary . . . . 21-1 WEB_dataset_shown_relations
INTEROP_Extra preference . . . . . . . . . . . . . . . . . . . 10-103
PLMXMLInstanceAttributes . . . . 21-2 WEB_dataset_upload_mode
Interop_Vis_Attributes . . . . . . . . . . . 21-3 preference . . . . . . . . . . . . . . . . . . . 10-108
Interop_Vis_Attributes_Admin_ Web_default_site_deployed_app_name
Filter . . . . . . . . . . . . . . . . . . . . . 21-4 preference . . . . . . . . . . . . . . . . . . . 10-104
ItemRevision_DirectModel3DMarkup_ WEB_default_site_server
default_relation . . . . . . . . . . . . . 21-4 preference . . . . . . . . . . . . . . . . . . . 10-104
ItemRevision_Vis_Session_default_ WEB_disable_structure_read_optimizations
relation . . . . . . . . . . . . . . . . . . . 21-5 preference . . . . . . . . . . . . . . . . . . . 10-105
MetaDataStamp_template . . . . . . . . 21-5 WEB_Enable_Create_Change
PLM_End_Item_Key . . . . . . . . . . . . 21-6 preference . . . . . . . . . . . . . . . . . . . . 13-20

Index
WEB_filter_person preference . . . . . 10-105 WEB_thumbnail_image_generate_type

WEB_filter_user preference . . . . . . . 10-106 preference . . . . . . . . . . . . . . . . . . . 10-124
WEB_fullsize_image_generate_type WEB_title_contents preference . . . . . 10-116
preference . . . . . . . . . . . . . . . . . . . 10-122 WEB_unpackage_multipart
WEB_help_server preference . . . . . . 10-105 preference . . . . . . . . . . . . . . . . . . . 10-117
WEB_image_size_horiz preference . . 10-123 WEB_use_activex_lov preference . . . 10-117
WEB_image_size_vert preference . . . 10-123 WEB_use_lhn_home_component
WEB_inbox_columns preference . . . . 10-119 preference . . . . . . . . . . . . . . . . . . . 10-117
WEB_item_default_relation WEB_use_lhn_inbox_component
preference . . . . . . . . . . . . . . . . . . . 10-110 preference . . . . . . . . . . . . . . . . . . . 10-118
WEB_itemrevision_default_relation WEB_wso_columns preference . . . . . 10-121
preference . . . . . . . . . . . . . . . . . . . 10-110 WEB_ZoneProcess_Reports
WEB_IWantToDefaultActions . . . . . 10-111 preference . . . . . . . . . . . . . . . . . . . 10-127
WEB_login_page preference . . . . . . . 10-112 WebDesignContextDefault SearchDistance
WEB_max_search_results preference . . . . . . . . . . . . . . . . . . . 10-125
preference . . . . . . . . . . . . . . . . . . . 10-112 WebDesignContextMaxMatching BOMLines
WEB_MELocateCompOp_Reports preference . . . . . . . . . . . . . . . . . . . 10-125
preference . . . . . . . . . . . . . . . . . . . 10-131 WebDesignContextMaxMatchingObjects
WEB_menu_entry_new_window preference . . . . . . . . . . . . . . . . . . . 10-126
preference . . . . . . . . . . . . . . . . . . . 10-109 WHERE_REFERENCED_RELATIONS_
WEB_menu_entry_suppressions FILTER preference . . . . . . . . . . . . . 10-89
preference . . . . . . . . . . . . . . . . . . . 10-109 Word_12_installed preference . . . . . . . 10-90
WEB_MEPrPlantProcess_Reports Workflow preferences . . . . . . . . . . . 11-134
preference . . . . . . . . . . . . . . . . . . . 10-130 CR_allow_alternate_procedures . . . . 11-2
WEB_MEWeldOp_Reports EPM_adhoc_signoffs . . . . . . . . . . . . 11-3
preference . . . . . . . . . . . . . . . . . . . 10-130 EPM_ARG_target_user_group_list_
WEB_NX_UseBookmark . . . . . . . . . 10-112 separator . . . . . . . . . . . . . . . . . . 11-8
WEB_package_multipart EPM_enable_apply_template_
preference . . . . . . . . . . . . . . . . . . . 10-113 changes . . . . . . . . . . . . . . . . . . . 11-3
WEB_packaging_extension EPM_multiple_processes_targets . . . 11-6
preference . . . . . . . . . . . . . . . . . . . 10-113 EPM_notify_url_format . . . . . . . . . 11-14
WEB_po_columns preference . . . . . . 10-121 EPM_resource_pool_recipients . . . . . 11-8
WEB_processes preference . . . . . . . . 10-113 EPM_resource_pool_restrict_
WEB_protocol preference . . . . . . . . . 10-106 subscription . . . . . . . . . . . . . . . . 11-8
WEB_psm_columns preference . . . . . 10-120 EPM_sub_process_target_
Web_Report_Jars preference . . . . . . 10-133 inheritance . . . . . . . . . . . . . . . . . 11-7
WEB_show_banner preference . . . . . 10-123 EPM_valid_roles_to_assign_responsible_
WEB_show_export_nx_assy_menu party . . . . . . . . . . . . . . . . . . . . . 11-5
preference . . . . . . . . . . . . . . . . . . . 10-114 EPM_valid_user_to_apply_assignment_
WEB_show_summary preference . . . 10-114 list . . . . . . . . . . . . . . . . . . . . . . . 11-5
WEB_show_thumbnail_image Global_transfer_access . . . . . . . . . . . 11-9
preference . . . . . . . . . . . . . . . . . . . 10-124 INBOX_hide_suspended_tasks . . . . 11-11
WEB_show_unconfigured_revs ORG_UIF_spacing . . . . . . . . . . . . . 11-11
preference . . . . . . . . . . . . . . . . . . . 10-114 ORG_UIF_user_name_display . . . . 11-12
WEB_simple_search_queries . . . . . . 10-115 RICH_CLIENT_MARKER_ID . . . . . 11-14
WEB_StationProcess_Reports SIGNOFF_adhoc_quorum . . . . . . . . . 11-3
preference . . . . . . . . . . . . . . . . . . . 10-128 SIGNOFF_fill_in_reviewers . . . . . . . 11-1
WEB_status_icons preference . . . . . 10-107 SIGNOFF_required_group_and_
WEB_style_sheet preference . . . . . . 10-115 role . . . . . . . . . . . . . . . . . . . . . . 11-1
WEB_style_sheet_list preference . . . 10-115 TASK_MONITOR_SLEEP_TIME . . 11-11
WEB_style_sheet_list_names TC_CM_approvers_modifier_roles . . . 11-2
preference . . . . . . . . . . . . . . . . . . . 10-116 TC_external_default_launch_ui . . . . 11-13
WEB_thumbnail_image_display_type TCVIEWER_default_workflow_
preference . . . . . . . . . . . . . . . . . . . 10-124 view . . . . . . . . . . . . . . . . . . . . . . 11-9

Index
WORKFLOW_adhoc_process . . . . . 11-12 WSHiddenColumnWidthsPref

WORKFLOW_advanced_paste . . . . 11-13 preference . . . . . . . . . . . . . . . . . . . . 10-94
WORKFLOW_new_route_task_ WsoFolderSavePref preference . . . . . . 10-95
panel . . . . . . . . . . . . . . . . . . . . 11-10 WsoInsertNoSelectionsPref
WORKFLOW_adhoc_process preference . . . . . . . . . . . . . . . . . . . . 10-95
preference . . . . . . . . . . . . . . . . . . . . 11-12 WsoInsertSelectionsPref preference . . 10-96
WORKFLOW_advanced_paste WSOM_find_editUserList
WORKFLOW_new_route_task_panel WSOM_find_list_separator
WORKSPACEOBJECT_object_columns_ WSOM_find_set_search_limit
hidden preference . . . . . . . . . . . . . . 10-90 preference . . . . . . . . . . . . . . . . . . . . 10-97
WORKSPACEOBJECT_object_columns_ WSOM_find_set_total_limit
shown preference . . . . . . . . . . . . . . . 10-91 preference . . . . . . . . . . . . . . . . . . . . 10-97
WORKSPACEOBJECT_object_widths_hidden WSOM_only_edit_effectivity_in_ecm
WORKSPACEOBJECT_object_widths_shown WSShownColumnWidthsPref
WS_expand_on_paste preference . . . . 10-94
WS_icon_placement preference . . . . . . 10-92 X
WSColumnsHiddenPref preference . . . 10-93
WSColumnsShownPref preference . . . 10-93 XFILESEARCHPATH variable . . . . . . . 3-16
WSDisplayTypePref preference . . . . . 10-94

Preferences Environment Variables Reference PLM Teamcenter

Uploaded by

Copyright:

Available Formats

You might also like

Preferences Environment Variables Reference PLM Teamcenter

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Preferences Environment Variables Reference PLM Teamcenter

Uploaded by

Copyright:

Available Formats

Teamcenter 8.

Preferences and Environment

This software and related documentation are proprietary to Siemens Product

2 Preferences and Environment Variables Reference PLM00026 F

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

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Introduction to environment variables . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Introduction to preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Configuration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Access Manager and Portfolio, Program and Project Management

eIntegrator Admin preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Authorization preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

File management and maintenance preferences . . . . . . . . . . . . . . . . . . 9-1

PLM00026 F Preferences and Environment Variables Reference 3

Audit Manager preferences . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Client preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Workflow preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Change Viewer preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Change Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Issue Manager preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Reports, requirements, and scheduling preferences . . . . . . . . . . . . . . 15-1

Classification Administration preferences . . . . . . . . . . . . . . . . . . . . . . 16-1

Classification preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Data sharing preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Product structure and Repeatable Digital Validation preferences . . . 19-1

Teamcenter’s manufacturing process management preferences . . . . . 20-1

4 Preferences and Environment Variables Reference PLM00026 F

PAD preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-56

Visualization preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Solution-specific preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Integration preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1

EDA preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1

Quality data preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1

ADA License preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1

PLM00026 F Preferences and Environment Variables Reference 5

Syntax definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Basic configuration concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Basic configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

PLM00026 F Preferences and Environment Variables Reference

Teamcenter installation and basic configuration is performed with the Teamcenter

The conventions are:

PLM00026 F Preferences and Environment Variables Reference 1-1

Basic configuration concepts

• Preferences are special environment variables stored in the Teamcenter

1-2 Preferences and Environment Variables Reference PLM00026 F

Configure Teamcenter before deploying to other sites

Important configuration variables for your initial Teamcenter

What are environment variables?

What are preferences?

Basic configuration tasks

PLM00026 F Preferences and Environment Variables Reference 1-3

is required. Configuration tasks include systems-based tasks, such as user

Manually configuring the Teamcenter environment

Sourcing the $TC_DATA/tc_cshvars file creates a csh subshell in which

1-4 Preferences and Environment Variables Reference PLM00026 F

Running environment variable script files

Creating and editing preferences