TC 10 1 Release Bulletin PDF

Teamcenter 10.
1 Release Bulletin
Publication Number
PLM00001 K (01-037134-0101)
Proprietary and restricted rights notice
This software and related documentation are proprietary to Siemens Product

Lifecycle Management Software Inc.
© 2013 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenter
is a trademark or registered trademark of Siemens Product Lifecycle Management
Software Inc. or its subsidiaries in the United States and in other countries. All
other trademarks, registered trademarks, or service marks belong to their respective
holders.
2 Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

Contents
Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Installing or upgrading Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Teamcenter and compatible third-party software versions . . . . . . . . . . . . . . . 1-3
Global Technical Access Center (GTAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Available Teamcenter 10.1 platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Hardware, software, and disk space requirements . . . . . . . . . . . . . . . . . . . . . 1-6
Using documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Support announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Overview of feature support announcements . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Deprecated feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Obsolete feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

New Teamcenter applications and solutions . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
New, revised, and obsolete Teamcenter documentation . . . . . . . . . . . . . . . . . . 3-2
Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Installing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Configuring Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Administering Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Using Teamcenter interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Managing changes and workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Getting started with document management . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Managing content, reports, and schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Systems Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
Sharing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87
4th Generation Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92
Managing product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Managing manufacturing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Visualizing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120
Repeatable Digital Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-132
Managing CAE data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-134
Managing quality data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-140
Managing maintenance, repair, and overhaul . . . . . . . . . . . . . . . . . . . . . . . 3-141
Customizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-142
Teamcenter solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-145
Performing integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-150
Teamcenter 10.1 release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin 3

Contents
Documentation release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-192
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
4 Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

Chapter
1 Before you begin
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Installing or upgrading Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Teamcenter and compatible third-party software versions . . . . . . . . . . . . . . . 1-3
Global Technical Access Center (GTAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Available Teamcenter 10.1 platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Hardware, software, and disk space requirements . . . . . . . . . . . . . . . . . . . . . 1-6
Using documentation . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Using documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Using PDF files . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Using HTML files . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin

Chapter
1 Before you begin
Before you begin

This release bulletin contains the following information:
• Support announcements
Important announcements about deprecated and obsolete features.
For more information, see Overview of feature support announcements.
• What’s new announcements

Descriptions of new features.
For more information, see What’s New.
• Release notes
Workarounds for known problems.
For more information, see Release notes.
Note For release notes pertaining to Product Master Management, see the Product
Master Management Release Bulletin.
Installing or upgrading Teamcenter

This bulletin contains information useful for customers who are installing or
upgrading Teamcenter.
• If you are Installing Teamcenter for the first time, see the following:
o Articles describing new installation features.

For more information, see Installing Teamcenter.
o Release notes describing workarounds for known installation problems.

For more information, see Installation and upgrade release notes.
Also see the Installation on UNIX and Linux Servers Guide or Installation on
Windows Servers Guide.
PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin 1-1

Chapter 1 Before you begin
• If you are upgrading from an earlier version of Teamcenter, see the following:
o Announcements of the deprecation or obsoletion of Teamcenter features.
For more information, see Support announcements.
Caution The deprecation or obsoletion of features such as preferences
can impact your upgrade. Before upgrading, take steps to
accommodate the removal of these features.
o Release notes describing workarounds for known upgrade problems.

For more information, see Installation and upgrade release notes.
Also see the Upgrade Guide.
For more information about installing or upgrading Teamcenter, see the following:
• Installation of Teamcenter patches and maintenance packs is described in
Installing Teamcenter patches in the Installation on UNIX and Linux Servers
Guide and the Installation on Windows Servers Guide.
• For general guidelines and best practices when deploying a new Teamcenter
installation or upgrading an existing Teamcenter system, see the latest version
of the Teamcenter Deployment Guide:
http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
Note You must have a WebKey account to access the Web site.
1-2 Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

Before you begin
Teamcenter and compatible third-party software versions

The Siemens PLM Software Certification site on the Global Technical Access
Center (GTAC) documents versions of operating systems, databases, compilers,
Web browsers, and other third-party software certified for use with Teamcenter.
Teamcenter releases do not coincide with releases of compatible third-party software,
so Teamcenter customers may acquire and install later versions of third-party
software before Siemens PLM Software is able to certify it.
Siemens PLM Software’s standard policy with respect to later versions of operating
systems and other third-party software relies on manufacturers’ guarantees. If a
manufacturer guarantees that a later version of its product is binary-compatible
with the preceding version, Siemens PLM Software expects our products to function
properly with the later version. Our experience shows few problems are encountered
when executing Teamcenter with a third-party version later than the version we
certified.
Siemens PLM Software makes a reasonable effort to support Teamcenter on later
software versions and to work with you to resolve any difficulty that may arise but
will not, in most cases, test adequately to certify the later version.
Teamcenter compatibility with operating systems and compilers involves these
two considerations:
• Compatibility for run time.
• Compatibility for relinking customizations and paths.
Typically, operating system manufacturers assure run-time binary compatibility

between successive versions of their operating systems. We make a reasonable effort
to support Teamcenter running on a later version of an operating system. Some
operating system manufacturers assure compatibility when relinking or rebuilding
executables and libraries with later versions of compilers. If later versions of
compilers are not compatible with earlier versions, you must link all Teamcenter
customizations using the compiler version certified for the Teamcenter release. This
also applies to installation of Teamcenter patches.
To reiterate, Teamcenter may run on a later version of an operating system, but
customizations and patches may need to be compiled and linked on an earlier version.
Although Teamcenter may run using an earlier software version, we strongly
discourage running earlier versions, and we do not provide support for doing so.
For information about the earliest versions of software with which to run Teamcenter,
that is, versions of software certified for use with Teamcenter, see the Siemens PLM
Software Certification site on GTAC:
http://support.industrysoftware.automation.siemens.com/ certification/teamcenter.shtml
Note If Siemens PLM Software discovers incompatible versions of third-party
software, we will post bulletins on GTAC. This information is also available
from your Teamcenter provider.

Global Technical Access Center (GTAC)

GTAC is the vehicle for Teamcenter communication. It provides a single repository
of current, accurate, version-controlled Teamcenter information that is accessible
through the Internet by authorized users. Maintained within GTAC is a wealth of
information for the diverse mix of customers and employees in the Teamcenter
community.
Information in GTAC includes, but is not limited to, the following:
• Certification announcements and bulletins
• Frequently asked questions
• Product defect reports
• Enhancement requests
• Patches and technical documentation
• Shareware customizations
• Tips pertaining to Teamcenter customization, performance, and administration
• Product information, customer success stories, and user conference presentations
GTAC can be accessed from the Siemens PLM Software Web site or directly through
its Web server at the following Web site:
http://support.industrysoftware.automation.siemens.com
You must have a WebKey account to access GTAC. A customer WebKey account is a
single point of authentication that allows customers to access product information
and associated support tools. WebKey accounts are strictly limited to Siemens PLM
Software employees and to people or companies who belong to the Teamcenter
community through contractual agreements with Siemens PLM Software pertaining
to Teamcenter. Requests for access to GTAC using a WebKey account can be directed
to the following Web site:
https://plmapps.industrysoftware.automation.siemens.com/webkey/

Before you begin
Available Teamcenter 10.1 platforms

The following distribution images are available as part of Teamcenter 10.1:
Teamcenter 10.1 for HP-UX Itanium
Teamcenter 10.1 for IBM AIX
Teamcenter 10.1 for Sun Solaris Sparc
Teamcenter 10.1 for Microsoft Windows 64-bit
Teamcenter 10.1 for Microsoft Windows 32-bit
Teamcenter 10.1 for Linux 64
Teamcenter 10.1 for Over-the-Web installation, All Platforms
Teamcenter 10.1 Embedded Visualization, All Platforms
Teamcenter 10.1 Publications, All Platforms
Teamcenter 10.1 is translated into the following language locales on all

server-supported platforms:
Chinese (Simplified)
Chinese (Traditional)
Czech
English
French
German
Italian
Japanese
Korean
Polish
Portuguese (Brazilian)
Russian
Spanish

Hardware, software, and disk space requirements

For information about system hardware and software requirements for Teamcenter
10.1, see the Siemens PLM Software Certification Database
http://support.industrysoftware.automation.siemens.com/
certification/teamcenter.shtml
The following table shows the required disk space for the platforms certified by
Teamcenter.
Required hard disk space for Teamcenter configurations

Corporate Two-tier
Platform server rich client Web tier
Hewlett-Packard HP-UX1 3.0 GB Not supported 3 GB
IBM AIX 2.0 GB Not supported 3 GB
SUSE Linux 2.0 GB 300 MB 3 GB
Red Hat Linux 2.0 GB 300 MB 3 GB
Sun Solaris 2.5 GB Not supported 3 GB
Microsoft Windows 1.5 GB 450 MB 4.5 GB
Using documentation
Using documentation
Teamcenter documentation is delivered in PDF and HTML format.
Using PDF files

The PDF directory on the documentation distribution media contains Adobe PDF
versions of the Teamcenter online help. From this directory, open the index.html
file in a Web browser to view the Teamcenter PDF Help Collection. You can view,
search, and print individual guides or selected pages from within your Web browser.
1. Itanium platforms only. PA-RISC hardware is not supported.

Before you begin
Teamcenter PDF online help collection

Viewing PDF files requires Adobe Reader, which you can download free from
Adobe at http://www.adobe.com. Viewing PDF files in a Web browser requires the
appropriate Adobe Reader plug-in for your Web browser.
If you want to open PDF files directly, browse to the following directory on the
documentation distribution media:
Windows or Macintosh systems:
PDF\index.html
UNIX or Linux systems:

PDF/index.html
If you want to share the PDF collection on your network, copy the top-level PDF
directory from the documentation distribution media to a network location and set
file permissions as necessary to allow viewing. Make sure you copy the complete
contents of the PDF directory to ensure the collection and search features are
available.

Searching the PDF help collection

To search the entire PDF collection, click Search collection using Adobe Reader
in the Teamcenter PDF Help Collection page. This opens the search index for the
collection in Adobe Reader. In the Search dialog box in Adobe Reader, type the text
you want to find.
The Search collection using Adobe Reader option is available only on a local host
or over a network file system. If you view the Teamcenter PDF Help Collection from
a Web (HTTP) server, you cannot search the entire PDF collection.
For collection search capability, open the PDF collection in a Web browser from a
local host or file system, using a URL with file protocol, for example:
• Local host:
file:///D://pdf/index.html
• Network host (UNC path):

file://///host-name/pdf/index.html
If your Web browser is not configured to open Adobe Acrobat catalog index (.pdx)
files, the browser may prompt you to choose an application to open the file. If this
occurs, select Adobe Acrobat Reader to open the index.
Note • If you encounter errors opening the PDF collection search, you may need
to upgrade Adobe Reader or your Web browser.
• When opening the PDF collection search index, Adobe Reader may open
the Search dialog box behind the Adobe Reader window. If you do not
see the Search dialog box, check behind the Adobe Reader window in
case the Search dialog box is hidden.
• If you want to open the PDF collection search directly in Adobe Reader,
open the PDF index file, tchelp.pdx, in the PDF\locale\tdocExt\pdf
directory.
Using the PDF online help collection in Firefox Web browsers

The default popup blocker in Firefox prevents opening PDF guides from the Product
Area pane in the PDF online help collection. You can work around this one of the
following ways:
• In the popup blocker bar at the top of the page, click Options, and then click the
title of the blocked document.
• Turn off the popup blocker (Tools®Options®Content).
If you access the PDF collection using a URL that begins with file:, you must paste
the URL directly into the address bar in Firefox. This is due to a default Firefox
security setting.

Before you begin
Using HTML files

Documentation in HTML format is installed when you select the Online Help option
in the Features panel in Teamcenter Environment Manager (TEM).
Teamcenter HTML online help collection

The Teamcenter online help requires a Web browser that supports Java for the
search to work. The browser version and Java specification required for online help
depends on the operating system you are using.
For information about certified browsers and Java versions for your operating
system, see the Siemens PLM Software Certification Database:
Note • Some features of the online help system require the display of popup
windows, for example, viewing footnotes. If a popup blocker utility is
installed on the Web server or client workstation, you must configure the
utility to allow popup windows from the online help domain. Otherwise,
the online help system does not function correctly.
• If you want to view the Teamcenter online help library in HTML

format, expand the tchelp.jar file from the Teamcenter documentation
distribution image to a local directory. To display the online help library
index page, open the index.html file in the help directory.
Additional online help features, such as Teamcenter developer
references, can also be installed.
For more information, see Installing Teamcenter online help in the
appropriate server installation guide (for Windows or UNIX/Linux).

Chapter
2 Support announcements
Overview of feature support announcements . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Deprecated feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

General deprecated feature announcements . . . . . . . . . . . . . . . . . . . . . . 2-1
Deprecated utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Deprecated ITK functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Deprecated services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Deprecated Java classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Deprecated data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Deprecated data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Deprecated Schedule Manager data model . . . . . . . . . . . . . . . . . . . . . 2-10
Deprecated Content Management data model . . . . . . . . . . . . . . . . . . 2-11
Deprecated preferences and environment variables . . . . . . . . . . . . . . . . . 2-13
Deprecated constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Deprecated Workflow handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Obsolete feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

General obsolete feature announcements . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Obsolete ITK functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Obsolete Global Services features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Obsolete data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Obsolete data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Obsolete Systems Engineering data model . . . . . . . . . . . . . . . . . . . . . 2-24
Obsolete Workflow data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Obsolete preferences and environment variables . . . . . . . . . . . . . . . . . . . 2-24
Obsolete utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Obsolete Workflow handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

Chapter
2 Support announcements
Overview of feature support announcements

As Siemens PLM Software enhances Teamcenter, some features are deprecated
or obsoleted.
• Deprecated features will be removed in a future version of Teamcenter.
• Obsolete features are either removed from Teamcenter or may be removed

without further notice.
If a feature you use is deprecated, read the deprecation announcement to learn of

any replacement feature. Migrate to the replacement feature as soon as possible to
avoid problems when the deprecated feature becomes obsolete.
For information about features deprecated in Teamcenter 10.1, see Deprecated
feature announcements.
For information about features removed in Teamcenter 10.1, see Obsolete feature
announcements.
Deprecated feature announcements
General deprecated feature announcements

The following features are deprecated in Teamcenter 10.1.
• Support for Teamcenter on 32-bit Microsoft Windows is deprecated
(First published Teamcenter 10.1)
Support for running Teamcenter on 32-bit versions of Microsoft Windows is
deprecated and will be obsolete in Teamcenter 11.1.
Support for running 32-bit Teamcenter on 64-bit Windows platforms is also
deprecated and will be obsolete in Teamcenter 11.1.
Siemens PLM Software recommends migrating all Teamcenter servers and
clients to a supported 64-bit version of Windows and also migrating to 64-bit
Teamcenter executables.
For information about operating system versions certified with Teamcenter 10.1,
see the Siemens PLM Software certification database:

Chapter 2 Support announcements
• Support for Microsoft Windows XP is deprecated

Support for running Teamcenter clients on Microsoft Windows XP is deprecated
and will be obsolete in Teamcenter 11.1.
Siemens PLM Software recommends migrating to a supported 64-bit version
of Microsoft Windows.
• Support for Internet Explorer 8 is deprecated

Support for running Teamcenter clients in Internet Explorer 8 is deprecated and
will be obsolete in Teamcenter 11.1.
Siemens PLM Software recommends migrating to a later version of Internet
Explorer.
For information about Web browser versions certified with Teamcenter 10.1, see
the Siemens PLM Software certification database:
• PER_CLIENT activation mode in two-tier rich client is deprecated

When the two-tier rich client is configured with PER_CLIENT activation mode,
it allows multiple client sessions running on a single client host.
Supporting multiple end users on a single client host in a two-tier deployment is
not recommended by Siemens PLM Software, and the PER_CLIENT mode is
deprecated starting in Teamcenter 10.1.
Siemens PLM Software recommends using four-tier Teamcenter deployment to
support multiple client sessions for different end users on a single client host.
• Audit Manager application is deprecated

The Audit Manager application (now referred to as the Legacy Audit Manager)
is deprecated and is replaced by a new Audit Manager solution.
For more information, see the Audit Manager Guide.

Support announcements
• User Services is deprecated

(First published Teamcenter 10)
User Services is a legacy way to call custom server code from only the rich
client. The capability to define new User Services is deprecated and will not be
supported in new Teamcenter Client Frameworks.
Use Business Modeler IDE to define custom Services (SOA) when you need to
directly call custom code from the rich client or any SOA client.
Existing User Service implementations will continue to be supported. The
TcUserService Rich Client class and the USERSERVICE_register_methods
ITK function are not deprecated but only their use for legacy code is supported.
Customers are encouraged to investigate alternatives (de-customization and
SOA services) as new client technologies are introduced.
• Audit Manager file storage mode is deprecated

File storage mode in Audit Manager is deprecated and will be removed in
Teamcenter 11. Siemens PLM Software recommends that new deployments
using Audit Manager persist audit history in the database only. File storage
mode will continue to be available in Teamcenter 10.
Audit Manager file storage mode is enabled when the TC_audit_manager
preference is set to ON and an audit definition is set to select File for Storage
Type.
For more information about storage type, see the Audit Manager Guide.

• Legacy user administration and CICO (checkin or checkout) audit files

are deprecated
Legacy user administration and checkout audit files are deprecated and will be
removed in Teamcenter 11. Siemens PLM Software recommends new customers
migrate to Audit Manager using audit definitions that specify Database for
Storage Type.
Note Legacy workflow files are obsolete in Teamcenter 10.1. For more
information, see Legacy workflow is obsolete.
Legacy audit file storage mode is the logging enabled when the
TC_audit_manager preference is set to OFF.
If the TC_audit_manager preference is set to OFF, several Teamcenter
features append entries to legacy audit files in a Teamcenter volume:
Checkin or checkout (CICO) (audit.log)
User administration (administration.log)
Others
The strategic Teamcenter direction for event auditing is the comprehensive and
configurable Audit Manager. The audit files identified in our documentation as
legacy audit files are inconsistent with that strategy and are not being enhanced
and are less efficient in performance and resource consumption. Each will be
removed in a future Teamcenter version.
Siemens PLM Software recommends that customers configure Audit Manager
to record these events during this transition period.
• NC Package Browser is deprecated

The NC Package Browser is deprecated. If you need a solution for connecting
between Teamcenter and MCIS DNC, Siemens PLM Software recommends
using Shop Floor Connect. For more information, contact your Siemens PLM
Software representative.

• Deprecation of Cold Backup and Hot Backup utilities

The Cold Backup and Restore utility performs integrated cold backup and restore
operations on the Microsoft SQL Server database and Teamcenter volumes.
The Hot Backup and Recovery utility performs integrated hot backup and
recovery operations on the Microsoft SQL Server database and Teamcenter
volumes.
One shortfall of these utilities is that the restore operation is not a targeted
operation. When restoring databases and volumes, all objects are rolled back to
a point in time, potentially removing a significant amount of valid data simply to
repair what could be a small problem.
Also, these utilities assume all volumes are accessible directly from the machine
on which the backup is executed (the database server) and that there is space to
take copies of all volume files.
These utilities (Cold Backup and Restore, Hot Backup and Recovery) will be
removed in a future version of Teamcenter. Only the wrapper functionality
will be removed from Teamcenter. The underlying command line utilities for
both utilities will remain.
Siemens PLM Software recommends that customers migrate away from the Cold
Backup and Restore utility and the Hot Backup and Recovery utility and use
more robust and flexible procedures with third-party backup and restore tools.
• Deprecation of the tc.h header file

In Teamcenter 8.1, the tc.h file was deprecated and will be removed in a future
version of Teamcenter. This include file is being split into two include files.
Code that calls one or more of the following methods should be changed from
#include <tc/tc.h> to #include <tcinit/tcinit.h>:
ITK_init_from_cpp
ITK__initialize_tc
ITK_init_module
ITK_auto_login
Code that does not call one of these methods should be changed from #include
<tc/tc.h> to #include <tc/tc_startup.h>.

• Support for running Teamcenter on Hewlett-Packard HP-UX is

deprecated
Running Teamcenter on the HP-UX operating system, including HP-UX on
Itanium hardware, is deprecated and will not be supported in the next release
of Teamcenter. This includes all Teamcenter clients and servers. Siemens PLM
Software recommends migrating to another supported platform and operating
system.
Note o Teamcenter support for HP-UX on PA-RISC hardware was
discontinued in Teamcenter 9.1.
o Support for Teamcenter clients on HP-UX on Itanium hardware was

discontinued in Teamcenter 9.1.
o Only Teamcenter servers are supported on HP-UX on Itanium

hardware in Teamcenter 10.1.
• Deprecation of the ERP Connect Toolkit

(First published atTeamcenter 10.1)
The ERP Connect Toolkit feature is deprecated. This functionality was replaced
by third-party integration products for Oracle Manufacturing and SAP in a
previous version of Teamcenter and will be obsolete in a future version of
Teamcenter.
The following ERP Connect Toolkit-specific preferences are also deprecated:
o ENABLE_ERP_integration_configuration
o TC_ERP_current_schema_name
o TC_ERP_dataset_types_to_transfer
o TC_ERP_mapping_files
o TC_ERP_rellog_file_path

The following ERP Connect Toolkit-specific action and rule handlers are also
deprecated:
o ERP-att-logfile-as-dataset-RH
o ERP-attach-targets-AH
o ERP-check-effective-date-RH
o ERP-check-target-status-RH
o ERP-delete-log-dataset-AH
o ERP-download-AH
o ERP-post-upload-AH
o ERP-set-form-value-AH
o ERP-validate-data-RH
o SAP-check-forms-attached-RH
o SAP-check-forms-to-download–RH
o SAP-upload-AH
Deprecated utilities
Teamcenter command line utilities are used by administrators to manage
Teamcenter installations. For more information about utilities, see the Utilities
Reference.
The following utilities are deprecated in Teamcenter 10.1.
• Deprecation of the bmide_postupgradetotc utility
The bmide_postupgradetotc utility is deprecated and will be removed in a
future version of Teamcenter.
• Deprecation of the combine_audit_files utility

The combine_audit_files utility is deprecated and will be removed in a future
version of Teamcenter.
• Deprecation of the define_auditdefs utility

The define_auditdefs utility is deprecated and will be removed in a future
This utility is used to create audit definitions in the Legacy Audit Manager. In
the new Audit Manager solution, you can create audit definitions using Business
Modeler IDE.
• Deprecation of the install_event_types utility

The install_event_types utility is deprecated and will be removed in a future
You can use the Event Type and Event Type Mapping functionality of Business
Modeler IDE in place of this utility.

• Deprecation of the tc_config_attr_mapping utility

The tc_config_attr_mapping utility is deprecated and is replaced by the
bmide_manage_batch_lovs utility.
Deprecated ITK functions

The Integration Toolkit (ITK) is a set of C functions provided by Siemens PLM
Software that you can use to integrate third-party or user-developed applications
with Teamcenter. For information about deprecated and obsolete ITK functions and
their replacement functions, see the Integration Toolkit Function Reference. Choose
the Deprecated menu option on the top menu bar.
• Deprecation of askLOVLength()
The askLOVLength() ITK function is deprecated because it always executes a
server call. Use the getLOVSize() function ITK instead, which is published and
based on the rich client ListOfValuesInfo cache.

Deprecated services
Teamcenter Services are a collection of Teamcenter operations used by system
administrators to connect their company’s applications to Teamcenter.
For the list of deprecated services, see the Services Reference in the Teamcenter
HTML Collection. Choose the Deprecated menu command on the top menu bar of
each set of API documentation.
Deprecated Java classes

Java classes are used to compose the rich client, and are documented in Javadoc
found on the Teamcenter installation media.
For the list of deprecated Java classes, see the Javadoc. Choose the Deprecated
menu command on the top menu bar of each set of Javadoc.
• Deprecation of the unpublished TCDnDAdapter.java class
The unpublished TCDnDAdapter.java Java class will be removed in a future
• Deprecation of the unpublished NevaIEViewer.java class

The unpublished NevaIEViewer.java Java class will be removed in a future
NevaIEViewer.java is a Swing-based Java class presented in various
applications in the rich client that embeds Microsoft Office documents into
the rich client for viewing and editing. NevaIEViewer.java is replaced by a
SWT-based counterpart.
Deprecated data model
Deprecated data model

The following data model items have been deprecated. You can view data model
items using the Business Modeler IDE.
For more information about data model, see the Business Modeler IDE Guide.

Deprecated Schedule Manager data model

The Schedule Manager data model includes some business objects and some business
object properties that are no longer used. These are marked as deprecated and
will be removed at a later date.
• Deprecated Schedule Manager business objects
Deprecated business object Replacement business object

ScheduleDeliverable SchDeliverable
TaskDeliverable SchTaskDeliverable
• Deprecated Schedule Manager properties on business objects
Business object Deprecated property Replacement property

Schedule act_date_preference None
base_schedule_cost None
dates_linked None
rights_mask None
sch_deliverable_taglist schedule_deliverable_taglist
ScheduleRevision act_date_preference None
archive_notification_events None
dates_linked None
rights_mask None
ScheduleTask baseline_var_cost None
ms_integration_link None
task_deliverable_taglist sch_task_deliverable_taglist
TaskSchedulingFormInfo task_deliverable_taglist sch_task_deliverable_taglist
TCCalendar tccal_desc None
TCCalendarEvent event_expiry_date None
event_type None
first_recur_end None
num_recurrences None
recur_days_of_week None
recur_interval None
recur_month None
recur_weeks_of_month None
TimeSheetEntry time_category None

Deprecated Content Management data model
(Revised at Teamcenter 8.3)

The Content Management data model includes some business objects and some
business object properties that are no longer used. These are marked as deprecated
and will be removed as specified.
• Deprecated Content Management run-time properties on business
objects
There is no migration planned for the following properties; they are simply not
needed without the separate Content Management Web server. These properties
will be removed at Teamcenter 9.0.
The isFrozen, lockOwner and inLifeCycle run-time properties are being
deleted from all classes where they are currently used:
DC_ComposedDocRevision
DC_ExtEntAdminRevision
DCt_ItemRevision
DC_ProcedureRevision
DC_PublicationRevision
DC_ReviewerDocRevision
DC_TopicRevision
DC_UnparsedDocRevision (only for the isFrozen and inLifeCycle
properties)

• Deprecated Content Management properties on business objects

These properties have string names that will be deprecated and replaced by
tag reference properties to other objects. These deprecated properties will
be removed at a future release when they are no longer needed for upgrade
purposes.
Business object Deprecated property Replacement property

DC_ComposedDocRevision topicReference ctm0PublicationTagref
languageRef ctm0LanguageTagref
DC_ProcTool grphcPrioReference ctm0GraphgicPriorityTagref
DC_PublicationRevision masterLanguageRef ctm0MasterLanguageTagref
styleTypeRef ctm0StyleTypeTagref
templateRef ctm0TemplateTagref
topicTypeRef ctm0TopicTypeTagref
DC_ReviewerDocRevision topicReference ctm0PublicationTagref
languageRef ctm0LanguageTagref
DC_TopicRevision masterLanguageRef ctm0MasterLanguageTagref
templateRef ctm0TemplateTagref
topicTypeRef cmt0TopicTypeTagref
DC_TransfPolTbl tpProcedure ctm0ProcedureTagref
tpStyleSheet None. Always use procedures.
tpToolName ctm0ToolTagref
DCt_GraphcTrnsltnRevision languageRef ctm0LanguageTagref
DCt_TranslationRevision languageRef ctm0LanguageTagref
topicReference None. Not used.
DCt_XmlAttrMapTbl xamProcedure ctm0ProcedureTagref
GrphicOptRevision languageRef Fnd0LanguageRef
GraphicRevision masterLanguageRef Fnd0LanguageRef
LanguagesTbl language Fnd0LanguageRef
TranslationOrderRevision topicReference Fnd0ItemRevTagref
translOfficeReference Fnd0TrnslOfficeTagref
translResponsible Fnd0TrnslRespblTagref
TransltnOfficeRevision translResponsible Fnd0TrnslRespblTagref
styleTypeRef ctm0StyleTypeTagref

Deprecated preferences and environment variables

Preferences are settings stored in the Teamcenter database that are read during
application usage. To work with preferences, in the rich client, choose Edit→Options
and click Filters at the bottom of the Options dialog box.
For more information about preferences, see the Preferences and Environment
Variables Reference.
• Separator preferences are deprecated

The following preferences are deprecated and will be removed in a future version
of Teamcenter:
o AE_dataset_id_separator
o FLColumnCatIVFSeparatorPref
o FLColumnCatObjSeparatorPref
o FLColumnCatSeqSeparatorPref
Separators are now defined using the DisplayName business object constant.
For more information, see the Business Modeler IDE Guide.
• Tc_Allow_Longer_Id_Name preference is deprecated

The Tc_Allow_Longer_Id_Name preference is deprecated and will be removed
in a future version of Teamcenter.
There is no replacement for this preference. Teamcenter now uses longer ID
names by default.
• TC_dataset_deep_copy_rules
Teamcenter 10.1 refactors deep copy rule processing so rule configuration
takes precedence in processing over configuration in the legacy
TC_dataset_deep_copy_rules preference.
• Audit Manager preferences are deprecated

The following preferences are deprecated and will be removed in a future version
of Teamcenter:
o TC_audit_log_dir
o TC_audit_buffer_size
o TC_audit_file_format
o TC_audit_delimiter
o TC_audit_track_changed_properties_only
o TC_audit_display_gmt

Deprecated constants
Global constants provide consistent definitions that can be used throughout
the system. These constants have only one value, either the default value or
the value you set. You can change the value of a global constant using the
BMIDE→Editors→Global Constants Editor menu command in the Business Modeler
IDE.
For more information about setting global constants, see the Business Modeler IDE
Guide.
• Fnd0AutoGenNextIdPerItemType is deprecated
The Fnd0AutoGenNextIdPerItemType global constant is deprecated and will
be removed in a future version of Teamcenter.
For more information about setting global constants, see the Business Modeler
IDE Guide.
Deprecated Workflow handlers

The following Workflow handlers and tasks are deprecated.
• AR-mark-archive
(First published Teamcenter 10.0; handler name modified Teamcenter 10.1)
The AR-mark-archive handler (formerly named EPM-mark-archive) is
deprecated and will be obsolete in a future version of Teamcenter.
For more information, see the Workflow Designer Guide.
• CONTMGMT-notify
The CONTMGMT-notify handler is deprecated and will be obsolete in a future
• Product Master Management handlers

The following Product Master Management handlers are deprecated and will be
obsolete in a future version of Teamcenter.
o USAGE-ir-has-status
o USAGE-ir-is-candidate-for-publish
o USAGE-check-vizfiles-or-submit-request
These handlers were used only in Product Master Management.

Obsolete feature announcements
General obsolete feature announcements

The following features are obsolete in Teamcenter 10.1.
• Obsoletion of Change Viewer
The Change Viewer application is obsolete. Change Viewer appeared as CM
Viewer (Classic) and is replaced with the Change Manager application.
If you used Change Viewer, you have options to migrate your change processes to
Change Manager.
For more information about migrating to Change Manager, see the Change
Manager Guide.
Incremental change is unaffected with the following exceptions:
o Double-clicking an incremental change in My Teamcenter does not open it in
Change Viewer Classic. The Summary pane is displayed instead.
o The Send To→CM Viewer (Classic) shortcut menu command is not available.
o Set the incremental change effectivity in Structure Manager instead of

Change Viewer.
o Initiate workflows in the application where you are accessing your

incremental change instead of Change Viewer.

The obsoletion of Change Viewer is accompanied by the obsoletion of the

following business objects.
Obsolete Workflow templates:
o Checklist Task
o Impact Analysis
o Prepare ECO
o CMII Change Notice
o CMII Change Request
o CMII WA
Obsolete queries:
o CM - BOM Changes
o CM - Change Forms
o CM - Change Progress
o CMII CN Type
o CMII CR Type
o Change Revision
Obsolete reports:
o Classic CM - BOM Changes
o Classic CM Change Forms
o Classic CM Change Progress
o ECO Details Report
o ECO Signoff Details
Handlers, preferences, and a utility for Change Viewer are also obsolete.
For information about the handlers, see Obsolete handlers for Change Viewer. For
information about the preferences, see Obsolete preferences for Change Viewer.
For information about the utilities, see Obsolete utility for Change Viewer.
• Legacy workflow is obsolete

Legacy workflow files are obsolete and are no longer available in Teamcenter
10.1. Siemens PLM Software recommends new customers use Audit Manager
with audit definitions that specify Database for Storage Type.
Legacy audit file storage mode is the logging enabled when the
TC_audit_manager preference is set to OFF.
If the TC_audit_manager preference is set to OFF, several Teamcenter
features append entries to legacy audit files in a Teamcenter volume:
Checkin or checkout (CICO) (audit.log)
User administration (administration.log)
Others
The strategic Teamcenter direction for event auditing is the comprehensive and
configurable Audit Manager. The audit files identified in our documentation as
legacy audit files are inconsistent with that strategy and are not being enhanced
and are less efficient in performance and resource consumption. Each will be
removed in a future Teamcenter version.

Siemens PLM Software recommends that customers configure Audit Manager

to record these events during this transition period.
• Support for the rich client and thin client on IBM AIX is obsolete
The Teamcenter rich client and thin client are no longer supported on IBM AIX
systems.
Teamcenter servers and Web tier continue to be certified on IBM AIX.
For more information about platforms certified for Teamcenter, see the Siemens
PLM Software certification database:
• Integration for Adobe Illustrator is obsolete

The Teamcenter Integration for Adobe Illustrator is obsolete and is no longer
supported.
This change accompanies the removal of Teamcenter proxy server for WebDAV.
For more information, see Teamcenter proxy server for WebDAV is obsolete.
• RDVUseNewVariantModel global constant is obsolete

The RDVUseNewVariantModel global constant is obsolete and is not
supported in Teamcenter 10.
• Global variables defined in appr.h are obsolete

(First published Teamcenter 8 MP1)
The external global variables defined in the appr.h file are obsolete in
Teamcenter 10. All customizations that require these variables must use
replacement getter functions.
The appr.h file defines external global variables such as the APPR_attr_op_like
variable. This causes the dependency of the libappr module with other modules
that use these external variables. These external variables should be removed.

• My Teamcenter (2007) is obsolete

(First published Teamcenter 8 )
The My Teamcenter (2007) application in the rich client is removed in
Teamcenter 10. Use the My Teamcenter application
Siemens PLM Software recommends that deployments using My Teamcenter
(2007) migrate any custom functionality to the My Teamcenter application prior
upgrading to Teamcenter 10.
For more information about the My Teamcenter application, see the My
Teamcenter Guide.
• Teamcenter Network Folders is obsolete

Teamcenter Network Folders is obsolete on all Windows platforms and is no
longer provided with Teamcenter. Functionality provided by Network Folders is
available through other existing Teamcenter functionality.
This change accompanies the removal of Teamcenter proxy server for WebDAV.
For more information, see Teamcenter proxy server for WebDAV is obsolete.
• Teamcenter proxy server for WebDAV is obsolete

Teamcenter proxy server for WebDAV is obsolete and is no longer provided with
Teamcenter. Functionality provided by Teamcenter proxy server for WebDAV is
available through other existing Teamcenter functionality.
With the removal of Teamcenter proxy server for WebDAV, the following
dependent features are also obsolete:
o Teamcenter Network Folders
o Teamcenter Integration for Adobe Illustrator
For more information, see Teamcenter Network Folders is obsolete and Integration
for Adobe Illustrator is obsolete.

Obsolete ITK functions

The Integration Toolkit (ITK) is a set of C functions provided by Siemens PLM
Software that you can use to integrate third-party or user-developed applications
with Teamcenter.
For information about deprecated and obsolete ITK functions and their replacement
functions, see the Integration Toolkit Function Reference. Choose the Deprecated
menu command on the top menu bar.
• PIE_init_module function is obsolete

(First published Teamcenter 8.3i)
The PIE_init_module ITK function is obsolete and is removed in Teamcenter
10.
• Obsolete Workflow ITK functions

The following Workflow ITK functions were are obsolete and are not available in
Teamcenter 10.1. There are no replacements for these functions.
CR_delete_approver_rig
CR__update_signoffs
CR__ask_status_release_date
CR_ask_roles
CR_ask_status_job
CR_add_indexed_reviewers (empty method)
CR_ask_signoff_index (empty method)
CR_set_signoff_index (empty method)
EPM__check_access
• Obsolete legacy Workflow ITK functions

The following Workflow ITK functions were deprecated in Teamcenter
engineering process management 9.1 and are obsolete in Teamcenter 8.3.
The Cascade Release (CR) model (and some of its ITK functions) was a simple
model of a workflow process that only included review tasks (release level in
older terminology) in series. This meant that you could assume that there was
an active review task, that there would only ever be one review active at any
time, and that they were all top level tasks not contained in another parent task
(like a route task or other organizational parent tasks).
That simple model has been obsolete for many releases. Currently, a workflow
process can include zero to many review tasks, and zero to many task types
active at any one time. These tasks may be hierarchically deeper than top level
in a parent/child task hierarchy. Code using the obsolete CR API (that assumes
there is one top-level active review task at any time) against current workflows
is incorrect and should be rewritten to consider the reality of the newer features.
Newer code must get the tasks of the EPMJob object and check their status and
task type before operating on them.

Replace calls to the CR_ask_current_release_level function with the following

calls:
1. Use the EPM_ask_root_task function (to get the root task from the
EPMJob object).
2. Use the EPM_get_type_tasks function (to get subtasks of type review task)
or the EPM_ask_sub_tasks function (to get all subtasks)
3. Use the EPM_ask_state function to check state of the task. If it is in a

started state that may be one of several started tasks that you need to
process.
Obsolete Workflow ITK function Replacement ITK function

CR_add_reference_objects EPM_ask_root_task
EPM_add_attachments
CR_add_target_objects EPM_ask_root_task
EPM_add_attachments
CR_ask_current_release_level EPM_ask_root_task
EPM_get_type_tasks or
EPM_ask_sub_tasks
EPM_ask_state
EPM_ask_review_task_name
CR_ask_reference_objects EPM_ask_root_task
EPM_ask_attachments
CR_ask_release_levels EPM_get_type_tasks
CR_ask_target_objects EPM_ask_root_task
EPM_ask_attachments
CR_create_job EPM_create_process
CR_demote_job EPM_ask_root_task
EPM_get_type_tasks (or
EPM_ask_sub_tasks)
EPM_ask_state
EPM_demote_task
CR_demote_target_objects EPM_ask_root_task
EPM_get_type_tasks (or
EPM_ask_sub_tasks)
EPM_ask_state
EPM_demote_task
CR_initialize_job EPM_create_process
CR_initiate EPM_create_process
CR_promote_job EPM_ask_root_task
(EPM_ask_sub_tasks)
EPM_ask_state
EPM_promote_task

Obsolete Workflow ITK function Replacement ITK function

CR_promote_target_objects EPM_ask_root_task
(EPM_ask_sub_tasks)
EPM_ask_state
EPM_promote_task
CR_remove_reference_objects EPM_ask_root_task
EPM_remove_attachments
CR_remove_target_objects EPM_ask_root_task
EPM_remove_attachments
CR_set_decision EPM_ask_root_task
(EPM_ask_sub_tasks)
EPM_ask_state
EPM_set_decision
EPM_create_job EPM_create_process
EPM_initialize_job EPM_create_process

Obsolete Global Services features

The following Global Services connectors are obsolete. Use the designated
replacement connectors instead.
Obsolete Global Services connector Replacement Global Services connector or feature
Global Services Framework – Web Services Replaced by the BPEL process partner links functionality
Connector of Global Services.
Teamcenter Global Services – Global Services Replaced by partner links provided through the
Connector Teamcenter 10 Global Services Framework - Ode BPEL
web application solution.
Teamcenter Global Services – Teamcenter 2007 Teamcenter 10 Global Services – Teamcenter 10 SOA
Rich Client Connector Connector
Teamcenter Global Services – Teamcenter No replacement.
Engineering 2005/2007 Connector
Teamcenter Global Services – Teamcenter No replacement.
Engineering v9 Connector
Teamcenter Global Services – Teamcenter 8 No replacement.
Connector
GS2GS connector Replaced by the functionaly provided by the bundled ODE
BPEL engine.
Teamcenter Global Services – SAP Connector Replaced by TTC10315 Teamcenter Gateway for SAP
Business Suite, which is available for download from
GTAC.
Teamcenter Global Services – Oracle Manufacturing Replaced by TC10316 Teamcenter Gateway for Oracle
Connector EBS, which is available for download from GTAC.
In addition, the following Global Services features are obsolete.

• Global Services BPEL engine endpoint is obsolete
The BPEL 1.1 engine that Global Services supplies is obsolete. This functionality
is replaced by the ODE BPEL 2.2 engine supplied through the Teamcenter 10
Global Services Framework - Ode BPEL web application solution. As a result,
the following Global Services invocation endpoint is also obsolete:
http://host:port/tcgs-context-root/controller/invoke
The new endpoint is:

http://host:port/tcgs-context-root/processes/process
Your clients must call this new endpoint in Teamcenter 10.

There are two significant changes for calling the new endpoint:
1. The URL must contain the process binding name.
2. A simple object access protocol (SOAP) header must contain the security
credentials.
The following is an example of an existing data-transfer call to Data Exchange:

http://localhost:7001/tcgs/controller/index
With the following SOAP message:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<data-transfer-request xmlns="http://teamcenter.com/globalservices/process/2007-06"
xmlns:xfer="http://teamcenter.com/globalservices/transfer/2007-06">
<client-message-id>cmid</client-message-id>
<master-site-id>1234</master-site-id>
<requestor-info>
<site-id>987</site-id>
<user-name>fred</user-name>
<group-id>cgroup</group-id>
</requestor-info>
<xfer:replica-info>
<xfer:site-id>987</xfer:site-id>
</xfer:replica-info>
<xfer:object-info>
<xfer:id>MTIObjectHandle</xfer:id>
</xfer:object-info>
<email>some-address; some-other-address</email>
<transfer-formula/>
<synchronize>true</synchronize>
<schedule>off-hours</schedule>
</data-transfer-request>
</soapenv:Body>
</soapenv:Envelope>
This is an example of a new call (differences in bold):

http://localhost:7001/tcgs-ode/processes/data-transfer
SOAP message:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/
oasis-200401-wss-wssecurity-secext-1.0.xsd"
soapenv:mustUnderstand="1">
<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/
oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="UsernameToken-22633664">
<wsse:Username>bob</wsse:Username>
<wsse:Password
Type="http://docs.oasis-open.org/wss/2004/01/
oasis-200401-wss-username-token-profile-1.0#PasswordDigest">
ax5JDeCpZHgQqln6sze3IR0zaoQ=</wsse:Password>
<wsse:Nonce>pqw5Lcz54OmVmYM6W1ruWQ==</wsse:Nonce>
<wsu:Created>2009-02-19T16:31:04.671Z</wsu:Created>
</wsse:UsernameToken>
</wsse:Security>
<addr:To xmlns:addr="http://www.w3.org/2005/08/addressing">
http://localhost:8081/tcgs-test/services/audit</addr:To>
<addr:Action xmlns:addr="http://www.w3.org/2005/08/addressing">audit</addr:Action>
<addr:ReplyTo xmlns:addr="http://www.w3.org/2005/08/addressing">
<addr:Address>http://www.w3.org/2005/08/addressing/none</addr:Address>
</addr:ReplyTo>
<addr:MessageID xmlns:addr="http://www.w3.org/2005/08/addressing">
urn:uuid:BDED93F98FA79F53B71235061065229</addr:MessageID>
</soapenv:Header>
<soapenv:Body>
<data-transfer-request xmlns="http://teamcenter.com/globalservices/process/2007-06"
xmlns:xfer="http://teamcenter.com/globalservices/transfer/2007-06">
<client-message-id>cmid</client-message-id>
<master-site-id>1234</master-site-id>
<requestor-info>
<site-id>987</site-id>
<user-name>fred</user-name>
<group-id>cgroup</group-id>
</requestor-info>
<xfer:replica-info>
<xfer:site-id>987</xfer:site-id>
</xfer:replica-info>
<xfer:object-info>
<xfer:id>MTIObjectHandle</xfer:id>
</xfer:object-info>
<email>some-address; some-other-address</email>
<transfer-formula/>
<synchronize>true</synchronize>
<schedule>off-hours</schedule>
</data-transfer-request>
</soapenv:Body>
</soapenv:Envelope>

Obsolete data model
Obsolete data model

The following data model items obsolete. You can view data model items using the
Business Modeler IDE.
For more information about data model, see the Business Modeler IDE Guide.
Obsolete Systems Engineering data model

The following Systems Engineering data model is obsolete.
• TraceLink class is obsolete
The TraceLink class, as extended from the ManagedRelation class, is
obsolete. The class feature is migrated to the new trace link FND_TraceLink
class under the TCRelation class. Also, a migration utility is provided and all
trace link instances are migrated to new trace links during database upgrade.
Obsolete Workflow data model

The following Workflow data model objects are obsolete and are no longer used.
• Obsolete Workflow business objects
Obsolete business object Replacement business object

EPMInheritance None
EPMTaskDefinition EPMTaskTemplate
EPMTaskStatus ReleaseStatus
OLD_EPMBRHandler EPMBRHandler
OLD_EPMBusinessRule EPMBusinessRule
OLD_EPMHandler EPMHandler
ReleaseLevel EPMReviewTask
ReleaseLevelDefinition EPMReviewTaskTemplate
RLMAccessDefinition None
SignoffList None
Obsolete preferences and environment variables

Preferences are special environment variables stored in the Teamcenter database
that are read during application usage. To work with preferences, in the rich client,
choose Edit→Options and choose Filters at the bottom of the Options dialog box.
For more information about preferences, see the Preferences and Environment

The following environment variables are obsolete:

• TC_LOCALIZATION_DIR
The following preferences are obsolete:

• WSOM_find_set_total_limit preference is obsolete
The WSOM_find_set_total_limit preference is obsolete and is not available in
Teamcenter 10.1.
• Obsolete preferences for Change Viewer

The following preferences are obsolete due to the obsoletion of Change Viewer.
o ECM_change_id_modifiable
o Enable_Create_Classic_Change
o Enable_Show_Classic_Change
o TAE_CM_change_name_is_mandatory
o TAE_CM_show_task_viewer
For more information about the obsoletion of Change Viewer, see Obsoletion
of Change Viewer.
• ASSIGNED_DATASET_ID_MODIFIABLE
• ASSIGNED_DATASET_REV_MODIFIABLE
• ASSIGNED_ITEM_ALTREV_MODIFIABLE
• BMF_BYPASS_ALL_EXTENSION_RULES
• BMF_ENABLE_DEBUG
• BMF_SUPPRESS_EXTENSION_RULES_DISPLAY
• BOM_line_full_props
• BYPASS_RULES
• CATIA_check_in_generate_vis_data_priority
• CATIA_on_demand_generate_vis_data_priority
• CATIA_V4_on_demand_generate_vis_data_priority
• Cfg_Att_add_props_of_form_types
• CM_ChangeNoticeRevision_displayed_pseudofolders
• CM_ChangeRequestRevision_displayed_pseudofolders

• CM_Cm0DevRqstRevision_displayed_pseudofolders
• CM_default_displayed_pseudofolders
• CM_ProblemReportRevision_displayed_pseudofolders
• <type>_createprops
• DEEPCOPY_keep_name_list
• <type>_DisplayProperties
• EDA_CadenceBOMOptionDefault
• EDA_GatewayCombinedBOMOptionDefault
• EDA_GatewayPcbBOMOptionDefault
• EDA_GatewaySchematicBOMOptionDefault
• EDA_GenerateViewable
• EDA_MentorBOMOptionDefault
• EDA_PadsBOMOptionDefault
• EDA_SecondaryItems
• ETS_available
• ETS_home
• GMS_site_checkin_after_import
This preference was for internal Siemens PLM Software use only.
• ICS_classify_immediately_NX
Use the Reuse Library when classifying in NX.
• IDEAS_check_in_generate_vis_data_priority
• IDEAS_import_from_tdm_default_gen_vis_data_priority
• IDEAS_import_from_tdm_gen_vis_data_display
• IDEAS_import_from_tdm_gen_vis_data_input
• IDEAS_import_from_tdm_options_default_gen_vis_data_priority
• IDEAS_import_translation_service_name
• IDEAS_on_demand_generate_vis_data_priority
• IDEAS_translation_dataset_type_names
• IDEAS_translation_service_name

• IMAN_<datasettype>_Volume
• IMAN_NFS_IMPORT_EXPORT_PERF
• IMPORT_EXPORT_USING_TCFS
• ItemCreation.NoMasterForm
For workarounds, see the release note about this obsolete preference in the
Business Modeler IDE release notes later in this guide.
• ItemCreation.NoRevMasterForm
For workarounds, see the release note about this obsolete preference in the
Business Modeler IDE release notes later in this guide.
• <ItemRevision-business-object>_Maturity_Level
All preferences of this type are replaced by the MaturityStatuses business
object constant.
• MSE_ICS_default_occurrences_types_map
• NX_Interop_Type
• NX_on_demand_generate_vis_data_priority
• NX_tocgm_on_demand_generate_vis_data_priority
• NX_tocgm_translation_service_name
• NX_translation_service_name
• PortalDesignContextCLRServers
Use the RDVClearanceProxyServers preference instead.
• PROE_on_demand_generate_vis_data_priority
• PROE_translation_service_name
• PSE_absocc_compound_properties
• PSE_add_props_of_item_form_types
• PSE_add_props_of_rev_form_types
• PUBLISHEDOBJECT_object_extended_attrs
• QRY_display_details
• QRY_number_of_favorites
• QRY_output
• QRY_output_options

• QRYColumnsShowWidthPref
• QUOTA_active
• QUOTA_logging_level
• QUOTA_minimum_lifetime
• QUOTA_unload_percentage
• QUOTA_unload_threshold
• RDV_variant_overlays_mode
• <relationType>_relation_primary
All preferences of this type are replaced by relation properties.
• REQ_avoid_default_Full_Text_creation
• REQ_default_styles_template
• SFRVolume_NT
• SFRVolume_UNX
• Show_ME_line_linked_icons
This preference is replaced by the MELineLinkedIconsProperty preference.
• ShowNewAliasMenu
• TC_always_try_volume_server
• TC_CURSOR_CACHE
• TC_CURSOR_LNSZ
• TC_CURSOR_NUM
• TC_CURSOR_SQL
• TC_CURSOR_STAT
• TC_DIS_3DMarkup_dstype
• TC_DIS_3DMarkup_relationship
• TC_DIS_AutoCreate_ITEM
• TC_DIS_image_capture_dstype
• TC_DIS_image_capture_relationship
• TC_DIS_ITEM_AutoCreated_TypeName

• TC_DIS_markup_dstype
• TC_DIS_markup_relationship
• TC_DIS_save_plmxml_dstype
• TC_DIS_save_plmxml_relationship
• TC_DIS_session_dstype
• TC_DIS_session_relationship
• TC_Export_Bucket_Size
• TC_force_nfs_access
• TC_negotiate_nfs_access
• TC_register_internal_service_modules
• TC_Security_Level
• TC_show_open_in_pv_button
• TC_Socket_Bucket_Size
• TC_validate_nfs_accessibility
• TC_VALIDATION_MANDATORY_CHECKERS
• TC_VALIDATION_PROGRAM
• TC_vmu_version
• TC_VOLUME_ACCESS_LOG
• TcSequenceIdVisible
• Tracelink_deepcopy_on_Revise
• Tracelink_deepcopy_on_SaveAs
• UGSideastojt_IdeasAssembly_ets_nr_types
• UGSideastojt_IdeasDrawing_ets_nr_types
• UGSideastojt_IdeasPart_ets_nr_types
• UGSnxtocgmdirect_ets_ds_types
• UGSnxtocgmdirect_UGALTREP_ets_nr_types
• UGSnxtocgmdirect_UGMASTER_ets_nr_types
• UGSnxtocgmdirect_UGPART_ets_nr_types

• UGSnxtocgmdirect_UGSCENARIO_ets_nr_types
• UGSnxtopvdirect_ets_ds_types
• UGSnxtopvdirect_UGALTREP_ets_nr_types
• UGSnxtopvdirect_UGMASTER_ets_nr_types
• UGSnxtopvdirect_UGPART_ets_nr_types
• UGSproetojt_ets_ds_types
• UGSproetojt_ProPrt_ets_nr_types
• <type>_viewerprops
• View_line_display_props
• view_view_valid_occurrencetypes

Obsolete utilities
Teamcenter command line utilities are used by administrators to manage
Teamcenter installations.
For more information about utilities, see the Utilities Reference.
Warning Do not use any of these utilities or data model corruption may result.
The following utilities are obsolete:

• Obsolete utility for Change Viewer
The following utility is obsolete due to the obsoletion of Change Viewer.
o verify_tasks
of Change Viewer.
• append_procedure
Use the plmxml_import utility instead.
• batchmode_clearance_analysis.pl
This script is replaced by the analyze_managed_product.pl script, which
is included in the stand-alone Teamcenter lifecycle visualization mockup
installation.
• generate_loadfsccache_tickets
The generate_loadfsccache_tickets is obsolete and is replaced by the
load_fsccache utility.
• import_dfa_file
(First published Teamcenter 2007.1.3)
The import_dfa_file utility is obsolete. Use the Business Modeler IDE to create
and manage the objects that were previously managed by this utility.
• object_backup
Use the Hot Backup over FMS feature instead.
• object_recover
• purge_mirror_volumes

The following utilities are also obsolete:

• apply_naming_rule
• bmide_upgrade_baselines
• business_rules_dtdxml2plmxml
• create_ai_type
• create_change_types
• create_cost_form
• create_snap_shot_view_form
• datasettype_cleanup
• deepcopyrules_migration
• grm
• gmpdm_get_location_info
• imanhelp
• import_export_business_rules
• input_notetype_default
• install_bmf_rules
• install_lovs
• install_type_display_rules
• install_types
• make_datasettype
• migrate_action_rules_to_bmf
• migrate_alias
• migrate_complex_property_rules
• migrate_type_display_prefs
• reset_protection
• runJtCacheClean
• runJtCacheInit
• runJtCachePopulator

• sb
• tc_erp_schema
• upgrade_ar
• update_class_property
• upgrade_motif_workflow_templates
• upgrade_nx_cam_templates
• upgrade_types
• upgrade_validation_objects
• upgrade_workflow_objects

Obsolete Workflow handlers

The following Workflow handlers are obsolete.
• add-status
This handler is obsolete because you can use the EPM-set-status handler to
obtain equivalent functionality.
• check-process-completion
The Sync task and related check-process-completion handler are obsolete
in Teamcenter 10. Obtain equivalent functionality by creating subprocesses
from parent processes.
• EPM-attach-item-revision-targets
This handler is replaced by the EPM-attach-related-objects handler.
• EPM-check-oramfg-transfer-status
This handler is obsolete because of the obsolescence of Oracle Manufacturing.
The handler is removed from the user interface in Teamcenter 10.1.
• EPM-send-to-oramfg
This handler is obsolete because of the obsolescence of Oracle Manufacturing.
The handler is removed from the user interface in Teamcenter 10.1.
• TCX-check-form
This handler is obsolete and is removed from the user interface in Teamcenter
10.1.
• Obsolete handlers for Change Viewer

The following action and rule handlers are obsolete due to the obsoletion of
Change Viewer.
Obsolete action handlers:
o ECM-add affected-irs-as-target
o ECM-att-new-status-for-aff-revs
o ECM-attach-components-to-change
o ECM-copy-end-item-effectivity

o ECM-create-base-revrule-form
o ECM-notify-competing-changes
o ECM-set-base-revrule
o ECM-start-new-sub-process
Obsolete rule handlers:

o ECM-check-target-is-ec
o ECM-is-all-affected-irs-released
o ECM-is-all-affected-irs-target
o ECM-is-valid-ec-process
of Change Viewer.
• Handler names obsolete because their names changed

The following handler names are obsolete because they have been renamed.
Obsolete handler name (prior to Teamcenter 10.1) New handler name (beginning in Teamcenter 10.1)
adhoc-signoffs EPM-adhoc-signoffs
allowed-role-list EPM-allowed-role-list
approve-service-structure SERVICEPROCESSING-approve-service-structure
ASB-attach-physical-components ASBUILT-attach-physical-components
ASM-attach-physical-components ASMAINTAINED-attach-physical-components
assert-signoffs-target-read-access EPM-assert-signoffs-target-read-access
auto-assign EPM-auto-assign
auto-assign-rest EPM-auto-assign-rest
auto-relocate-file SMP-auto-relocate-file
change-all-started-to-pending EPM-change-all-started-to-pending
check-assignment EPM-check-assignment
check-condition EPM-check-condition
check-responsible-party EPM-check-responsible-party
check-signoff EPM-check-signoff
CR-assert-targets-checked-in EPM-assert-targets-checked-in
CR-assign-team-selector EPM-assign-team-selector
CR-change-group-owner EPM-change-group-owner
CR-change-target-group EPM-change-target-group
CR-change-target-group-owner EPM-change-target-group-owner
CR-check-item-status EPM-check-item-status
create-status EPM-create-status
CR-fill-in-reviewers EPM-fill-in-reviewers
CR-notify EPM-notify-report

debug EPM-debug
debug-rule EPM-debug-rule
demote EPM-demote
demote-on-reject EPM-demote-on-reject
disallow-adding-targets EPM-disallow-adding-targets
disallow-removing-targets EPM-disallow-removing-targets
EPM-add-released-parts-queue RDV-add-released-parts-queue
EPM-assert-target-classified ICS-assert-target-classified
EPM-attach-assembly-components PS-attach-assembly-components
EPM-attach-mgcitemrev-targets MGC-attach-mgcitemrev-targets
EPM-attach-targets-AH ERP-attach-related-targets-AH
EPM-check-assembly-status-progression PS-check-assembly-status-progression
EPM-check-occ-notes PS-check-occ-notes
EPM-check-validation-result VAL-check-validation-result
EPM-check-validation-result-with-rules VAL-check-validation-result-with-rules
EPM-delete-ugcgm-markup RDV-delete-ugcgm-markup
EPM-export-AI-AH AI-export-AH
EPM-export-to-plmxmlfile PIE-export-to-plmxmlfile
EPM-generate-image RDV-generate-image
EPM-generate-ugcgm-drawing RDV-generate-ugcgm-drawing
EPM-make-mature-design-primary PS-make-mature-design-primary
EPM-mark-archive AR-mark-archive
EPM-perform-offline-export BC-perform-export
EPM-publish-target-objects PUBR-publish-target-objects
EPM-send-target-objects OBJIO-send-target-objects
EPM-set-condition-by-check-validation-result VAL-set-condition-by-check-validation-result
EPM-set-form-value-AH ERP-set-form-value-AH
EPM-tessellation-handler RDV-tessellation-handler
EPM-unpublish-target-objects PUBR-unpublish-target-objects
execute-follow-up EPM-execute-follow-up
inherit EPM-inherit
invoke-system-action EPM-invoke-system-action
invoke-system-rule EPM-invoke-system-rule
late-notification EPM-late-notification
notify EPM-notify
notify-signoffs EPM-notify-signoffs
release-asbuilt-structure ASBUILT-release-asbuilt-structure
release-asmaintained-structure ASMAINTAINED-release-asmaintained-structure
require-authentication EPM-require-authentication
schmgt-approve-timesheetentries SCHMGT-approve-timesheetentries
schmgt-revise-timesheetentries SCHMGT-revise-timesheetentries

schmgt-reject-timesheetentries SCHMGT-reject-timesheetentries
set-condition EPM-set-condition
set-duration EPM-set-duration
set-parent-result EPM-set-parent-result
set-status EPM-set-status
suspend-on-reject EPM-suspend-on-reject
system EPM-system
TCX-auto-approve-first-step TCRS-auto-approve-first-step
TCX-check-approver TCRS-check-approver
TCX-check-bomchild-statuslist TCRS-check-bomchild-statuslist
TCX-check-bom-precise TCRS-check-bom-precise
TCX-check-comps-against-pattern TCRS-check-comps-against-pattern
TCX-check-datasets TCRS-check-datasets
TCX-check-itemrev-status TCRS-check-itemrev-status
TCX-check-jobowner TCRS-check-jobowner
TCX-check-prev-itemrev-status TCRS-check-prev-itemrev-status
TCX-check-signoff TCRS-check-signoff
TCX-check-status TCRS-check-status
TCX-has-target-drawing TCRS-has-target-drawing
TCX-create-form TCRS-create-form
TCX-create-snapshot TCRS-create-snapshot
TCX-Create-Translation-Request TCRS-Create-Translation-Request
TCX-delete-dataset TCRS-delete-dataset
TCX-delete-log-datasets TCRS-delete-log-datasets
TCX-export-signoff-data TCRS-export-signoff-data
TCX-IRM-cleanfields TCRS-IRM-cleanfields
TCX-purge-dataset TCRS-purge-dataset
TCX-release-previous-itemrevs TCRS-release-previous-itemrevs
TCX-remove-targets-with-status TCRS-remove-targets-with-status
TCX-set-bom-precise TCRS-set-bom-precise
TCX-store-cr-data TCRS-store-review-data
TCX-trigger-approve-first-step TCRS-trigger-approve-first-step
trigger-action EPM-trigger-action
trigger-action-on-related-process-task EPM-trigger-action-on-related-process-task
validate-for-checkedout-asmaintained ASMAINTAINED-validate-for-checkedout-
-physicalpartrevision physicalpartrevision
validate-for-checkedout-physicalpartrevision ASBUILT-validate-for-checkedout-physicalpartrevision
validate-for-class MROCORE-validate-for-class
validate-for-latest-asmphysicalpartrevision ASMAINTAINED-validate-for-latest-asmphysicalpartrevision
validate-for-physicalpartrevision ASBUILT-validate-for-physicalpartrevision

validate-for-unserviceable ASMAINTAINED-validate-for-unserviceable-physicalpartrevision
-physicalpartrevision
validate-missing-asmaintained-structure ASMAINTAINED-validate-missing-asmaintained-structure
validate-missing-structure ASBUILT-validate-missing-structure

Chapter
3 What’s New
New Teamcenter applications and solutions . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
New, revised, and obsolete Teamcenter documentation . . . . . . . . . . . . . . . . . . 3-2
Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Introducing Teamcenter Rapid Start as a pre-configuration of Teamcenter . . 3-5
Installing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Teamcenter supports IPv6 networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
TEM creates compact installation package for simplified Teamcenter
deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Teamcenter registered in Windows program list . . . . . . . . . . . . . . . . . . . . 3-6
Teamcenter can be fully uninstalled using TEM . . . . . . . . . . . . . . . . . . . . 3-7
Teamcenter installation tools verify Java version . . . . . . . . . . . . . . . . . . . 3-7
Teamcenter Environment Manager creates copy of production
environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Teamcenter supports new application server and Eclipse versions . . . . . . . 3-9
J2EE server manager runs as a service or daemon . . . . . . . . . . . . . . . . . . 3-10
Teamcenter supports client-certificate authentication . . . . . . . . . . . . . . . . 3-11
Configuring Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Enhanced Save As functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Mapper lookup table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Configure deep copy rules used in revisions . . . . . . . . . . . . . . . . . . . . 3-12
Create dynamic LOVs more easily . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Simplified Business Modeler IDE user interface . . . . . . . . . . . . . . . . . 3-15
Multifield keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Multifield keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Application changes to support the use of multifield keys . . . . . . . . . . 3-26
Server changes to support the use of multifield keys . . . . . . . . . . . . . . 3-27
New multifield key preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Control access to preferences and options . . . . . . . . . . . . . . . . . . . . . 3-28
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Administering Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

Audit Manager enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Vendor Management supports multifield keys . . . . . . . . . . . . . . . . . . . . . 3-33
Update object properties in bulk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Managing authorized data access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Validation Manager enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Users can validate 4th Generation Design objects . . . . . . . . . . . . . . . . . . 3-34

Client cache enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Configuring authorized data access (ADA) license categories . . . . . . . . . . . 3-35
Designating multiple project team administrators . . . . . . . . . . . . . . . . . . 3-35
Teamcenter stores passwords on disk in an advanced encryption format . . 3-36
Tracking module usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Saved query results using revision rules . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Support for multiple citizenships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
FMS UTF-8 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
License bundling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Store and forward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Using Teamcenter interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41

Teamcenter Client for Microsoft Office enhancements . . . . . . . . . . . . . . . 3-41
Microsoft Office 2010 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Access to all core Microsoft Office file types . . . . . . . . . . . . . . . . . . . . 3-42
Transfer object reservations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
Additional Teamcenter workflow features . . . . . . . . . . . . . . . . . . . . . 3-42
Getting Started with Teamcenter enhancements . . . . . . . . . . . . . . . . . . . 3-43
Thin client user interface enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Classification query enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Rich client user interface enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Rich client XRT style sheet, view, and create dialog box enhancements . . . 3-46
Preference names added to option descriptions and Using Teamcenter
Preferences video available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Date Control enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
Named References dialog box revised . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
My Teamcenter (2007) removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Application bar and browser title bar display . . . . . . . . . . . . . . . . . . . . . . 3-51
Summary style sheet updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
New Save As wizard in the thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Changes to the display of lists of values (LOVs) . . . . . . . . . . . . . . . . . . . . 3-56
HTML style sheet in Client for Office . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Managing changes and workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61

Workflow Condition task branches based on subprocess results . . . . . . . . . 3-61
Issue Manager interface enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Making bulk updates of assemblies in a structure . . . . . . . . . . . . . . . . . . 3-61
Tracking workflow and schedule progress in the Process History view . . . . 3-62
Workflow handler, argument, argument values, and keyword name
changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
Workflow can run tasks in the background . . . . . . . . . . . . . . . . . . . . . . . 3-69
Workflow propagates parent process states to child subprocesses for delete and
abort actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Change Viewer-specific templates and handlers are removed from
Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Claiming tasks from a resource pool or other users . . . . . . . . . . . . . . . . . . 3-70
Promote Review and Route tasks along either the Approved or Rejected
path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Customize the perform signoff user interface . . . . . . . . . . . . . . . . . . . . . . 3-70
Filter Workflow processes more extensively . . . . . . . . . . . . . . . . . . . . . . . 3-71
Expanded audit information is available for Workflow users . . . . . . . . . . . 3-71
Add change folders in a schedule task to the Target and Reference folders of a
workflow task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

Change Manager schedule and general enhancements . . . . . . . . . . . . . . . 3-72
Getting started with document management . . . . . . . . . . . . . . . . . . . . . . . . . 3-74

Document management enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Digitally signing PDF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Launch applications for datasets in Teamcenter Client for Microsoft
Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
Create-with-attached-files and submit-to-workflow functionality in the thin
client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
Checkout/checkin files transfer in the thin client . . . . . . . . . . . . . . . . 3-76
Create and summary style sheets for Document objects . . . . . . . . . . . 3-76
Managing content, reports, and schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77

Content Management enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Schedule Manager enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Systems Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79

General Relationship Management (GRM) relations in Visio diagrams . . . 3-79
Domain assignment for child diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
Multi-Site Collaboration support for Visio diagrams . . . . . . . . . . . . . . . . . 3-80
Traceability across Teamcenter domains . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Diagram enhancements for functional and logical models . . . . . . . . . . . . . 3-81
Arranging the Traceability view layout . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
Navigating to an object by its URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
Hierarchical numbering in Relation Browser . . . . . . . . . . . . . . . . . . . . . . 3-83
Attaching custom notes to trace links . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
Comparing requirement content in Microsoft Office Word . . . . . . . . . . . . 3-83
Transferring exported object data by e-mail . . . . . . . . . . . . . . . . . . . . . . . 3-84
Copying a snapshot of exported data to a Microsoft Office Word dataset . . . 3-84
Design requirements and validation requirements for NX parts . . . . . . . . 3-84
Multifield keys for Systems Engineering object definitions . . . . . . . . . . . . 3-85
MATLAB integration enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86
View and edit the validation requirement or design requirement . . . . . . . . 3-86
Sharing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87

Briefcase file viewer and editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87
Briefcase file export to suppliers without Teamcenter . . . . . . . . . . . . . . . . 3-87
Export of incremental change to structures . . . . . . . . . . . . . . . . . . . . . . . 3-88
Multi-Site Collaboration support for 4th Generation Design data . . . . . . . 3-89
Data Exchange support for 4th Generation Design data . . . . . . . . . . . . . . 3-90
Enhanced transition mapping process using Teamcenter Enterprise dry run
export feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Multi-Site Collaboration support for Visio diagrams . . . . . . . . . . . . . . . . . 3-91
4th Generation Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92

4th Generation Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92
Working with 4GD effectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Working with variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Working with partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Making cacheless searches in 4GD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-96
Implementing audit logging of 4GD objects . . . . . . . . . . . . . . . . . . . . . . . 3-97
Transition to 4th Generation Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Working with the Product Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Users can validate 4th Generation Design objects . . . . . . . . . . . . . . . . . 3-100

Multi-Site Collaboration support for 4th Generation Design data . . . . . . 3-100
Data Exchange support for 4th Generation Design data . . . . . . . . . . . . . 3-101
Support for 4GD in Manufacturing Process Planner . . . . . . . . . . . . . . . . 3-102
Managing product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104

Automating part-CAD alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Making bulk updates of assemblies in a structure . . . . . . . . . . . . . . . . . 3-105
Making spatial searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Saving the state of the View®Show Unconfigured... menu commands . . . 3-106
Defining conditions on PSOccurrence objects . . . . . . . . . . . . . . . . . . . . . 3-106
Options and variants support for multifield keys . . . . . . . . . . . . . . . . . . 3-107
Structure Manager usability enhancements . . . . . . . . . . . . . . . . . . . . . 3-107
Rolling up variant conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108
Enhanced closure rule filtering of BOM expansion . . . . . . . . . . . . . . . . . 3-109
Managing manufacturing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109

Manufacturing Execution System Integration . . . . . . . . . . . . . . . . . . . . 3-109
Structure search enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110
Saving the state of the Show Unconfigured... buttons . . . . . . . . . . . . . . . 3-111
Using standard text to create work instructions . . . . . . . . . . . . . . . . . . . 3-111
Composing 3D PDF reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-112
4D planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113
Line balancing variant support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113
Structure expansion based on a closure rule . . . . . . . . . . . . . . . . . . . . . 3-115
Scoping data in studies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115
Tool design packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115
Support for 4GD in Manufacturing Process Planner . . . . . . . . . . . . . . . . 3-116
Export of incremental change to structures . . . . . . . . . . . . . . . . . . . . . . 3-118
Automatic assembly graphics positioning in Resource Manager . . . . . . . . 3-118
Manufacturing features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119
Import/export of enterprise BOP search criteria . . . . . . . . . . . . . . . . . . . 3-119
Visualizing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120

New features for Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120
Exact measurements in Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120
Advanced entity selection in Base . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120
Change the active reference set . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120
Creating and viewing PMI effectivity . . . . . . . . . . . . . . . . . . . . . . . 3-120
Enhancements to PMI display in Lifecycle Visualization . . . . . . . . . . 3-121
Visualize 4GD worksets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-121
Visualize occurrence groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-121
Create images of 3D models for Content Management . . . . . . . . . . . 3-121
PDF text search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
DGN enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
2D export enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
View structure in monolithic JT files . . . . . . . . . . . . . . . . . . . . . . . . 3-122
Automatic 3D model rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
Support for IPv6 addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123
Visualization support for multifield keys . . . . . . . . . . . . . . . . . . . . . 3-123
New features for Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123
Add BOM line properties to text markups in embedded viewers . . . . . 3-123
New features for Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
Motion clients honor constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
Color intersecting parts in cross sections . . . . . . . . . . . . . . . . . . . . . 3-127

Side by side 3D comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
Visual report enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
Product view support for unconfigured view toggle states . . . . . . . . . 3-128
Create product views of expanded monolithic JT files . . . . . . . . . . . . 3-128
Enhancements to product view site preferences . . . . . . . . . . . . . . . . 3-128
New features for Mockup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-129
Constrain parts in an assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-129
Enhanced clearance usability and performance . . . . . . . . . . . . . . . . 3-129
Filter enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130
New features for ClearanceDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130
New ClearanceDB product attributes . . . . . . . . . . . . . . . . . . . . . . . 3-130
Oracle Instant Client support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-131
64-bit ClearanceDB Proxy on Solaris and Linux . . . . . . . . . . . . . . . . 3-131
Repeatable Digital Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-132

Making product-scoped cacheless searches . . . . . . . . . . . . . . . . . . . . . . 3-132
Managing CAE data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-134

Launch tool enhancements for multifield keys . . . . . . . . . . . . . . . . . . . . 3-134
Structure management enhancements for multifield keys . . . . . . . . . . . . 3-134
Create CAE data using packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-135
Usability enhancements incorporating multiple views . . . . . . . . . . . . . . 3-136
Checking out-of-date notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-136
Comparing structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-137
CAE structure attribute enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 3-137
Simulation tool launch usability enhancements . . . . . . . . . . . . . . . . . . . 3-138
CAE structure creation and comparison enhancements . . . . . . . . . . . . . 3-138
Managing quality data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-140

Defining quality inspection processes . . . . . . . . . . . . . . . . . . . . . . . . . . 3-140
Date and time displayed in DPV Measurements . . . . . . . . . . . . . . . . . . 3-140
DPV enhancements for handling errors in measurement data . . . . . . . . . 3-140
Managing maintenance, repair, and overhaul . . . . . . . . . . . . . . . . . . . . . . . 3-141

MRO support for multifield keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-141
Customizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-142

Enhanced support for UTF-8 in Teamcenter Services . . . . . . . . . . . . . . 3-142
Dynamic buffer allocation support for multibyte strings . . . . . . . . . . . . . 3-142
Bulk object creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143
Changed default display value of Boolean properties . . . . . . . . . . . . . . . 3-144
Teamcenter solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-145

Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-145
Aerospace and Defense multifield keys support . . . . . . . . . . . . . . . . 3-145
Location code management enhancements . . . . . . . . . . . . . . . . . . . . 3-145
Unincorporated changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-145
Managing stock materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-146
Managing work packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-146
Managing finishes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-147
Configuration audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-147
Thin client support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-148
Materials Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-149
Substance Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-150

Performing integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-150
Manufacturing Execution System Integration . . . . . . . . . . . . . . . . . . . . 3-150

Chapter
3 What’s New
New Teamcenter applications and solutions

Teamcenter 10.1 includes the following new applications, a new integration, and
reworked applications.
• New applications:
o 4G Designer is the principal application used to manage 4th Generation
Design products or programs. It allows configuration developers to
create the collaborative design that holds the CAD data and then divide
it into functional, physical, and logical partitions. Design team leaders
then populate the partitions with subsets that represent assemblies and
subassemblies. They may create promissory design elements for new CAD
designs, and also reuse design elements for reused, standard, or vendor
parts. You can configure design data with date, unit or intent effectivity,
and also with variants.
For more information about 4G Designer, see the 4th Generation Design
Guide.
o The Product Configurator allows you to define global variant option libraries
and variants rules for your company. You can then associate them with
product items and product models. These definitions are used by the 4G
Designer application, in which you apply the defined variability to the CAD
designs. You create items representing option libraries and products in
other applications (typically, in My Teamcenter) and then send them to the
Product Configurator.
For more information about the Product Configurator, see the Product
Configurator Guide.
• New solutions:
o Materials Management stores the material and substance information
imported from a third-party data base like Granta or International Material
Data System (IMDS) into the Teamcenter database. By storing materials in
Teamcenter, other Siemens PLM Software applications can be modified to
use the Teamcenter material library as a source for material information,
rather than each application owing individual databases. The Materials
Management solution is also required to support environmental compliance.
A Teamcenter part or BOM is sent to an external compliance checker to
verify if the part or BOM is environmentally compliant.
For more information about this new solution, see the Materials Management
Solution Guide.

Chapter 3 What’s New
o Substance Compliance allows original equipment manufacturers (OEMs)

to conform to environmental laws, regulations, standards, and other
requirements for their own parts and for the parts manufactured or supplied
from an external source.
For more information about this new solution, see the Substance Compliance
Solution Guide.
• New integrations:
o Manufacturing Execution System Integration is a new integration that
allows companies to more effectively and efficiently execute manufacturing
operations from the product order through each step of the manufacturing
process to its final point of delivery. Equally important, manufacturing
execution systems are dynamic information systems that are key to
collaborative manufacturing strategies by providing mission-critical
information about production activities to managers across an organization
and its supply chain.
By default, this integration is designed to work with the Siemens SIMATIC
IT software. You can customize it to run with other manufacturing execution
systems.
For more information about this new integration, see the Manufacturing
Execution System Integration Guide.
New, revised, and obsolete Teamcenter documentation

The following tables list new, revised, or obsolete Teamcenter documentation
deliverables for Teamcenter 10.1.
New Teamcenter documentation

Name Description
4th Generation Design This guide describes how to use the 4G Designer
Guide application to manage 4th Generation Design products
or programs. 4th Generation Design allows users of
NX CAD or Lifecycle Visualization to cooperate in
real time during the design cycle of a product. It is
particularly suitable for development teams working
on large products that typically include millions of
parts, for example, those found in the shipbuilding
industry. This guide previously was available only to
early adopters of 4th Generation Design.
Product Configurator This guide describes how to use the Product
Guide Configurator to define and manage option families,
option values, option rules, and constraints (rule
checks). It also describes how to create and manage
groups or libraries of options.

What’s New
New Teamcenter documentation

Name Description
Site Consolidation Guide This guide documents processes required to safely
consolidate two Teamcenter sites into one. This guide
previously was available only through the Global
Technical Access Center (GTAC).
Briefcase Browser Guide This guide documents the installation, configuration,
customization, and use of the stand-alone Briefcase
Browser application. It is intended for supplier
sites that do not manage their product data in
Teamcenter (unmanaged supplier). It is included
in the Teamcenter help collection for reference for
Teamcenter administrators.
Materials Management This guide documents how to install and configure
Solution Guide the Materials Management application, as well as
how to import, export, and manage materials within
Teamcenter.
Substance Compliance This guide documents how to install and configure
Solution Guide the Substance Compliance application, as well as
how to manage material substance declarations from
suppliers.
Manufacturing Execution This guide documents the Manufacturing Execution
System Integration Guide System Integration.
Revised Teamcenter documentation

Name Description
Installation on Linux The Installation on UNIX and Linux Clients Guide is
Clients Guide renamed Installation on Linux Clients Guide.
Dimensional Planning and The Getting Started with Dimensional Planning and
Validation Tutorial Validation Guide is renamed Dimensional Planning
and Validation Tutorial. It only contains a tutorial of
defining the quality inspection process. The overview
information describing Dimensional Planning and
Validation is moved to the Dimensional Planning and
Validation Administration Guide.

Revised Teamcenter documentation

Name Description
Getting Started with The Getting Started with Electronic (EDA) Lifecycle
Electronic (EDA) Lifecycle Management guide is not available in the Teamcenter
Management 10.1 documentation set.
In response to the growing customer demands in the
ECAD domain, Teamcenter EDA is now separately
licensed and distributed. The Getting Started with
Electronic (EDA) Lifecycle Management guide will be
available as part of a separate EDA 1.0 release.
If you need any information about Electronic
(EDA) Lifecycle Management documentation,
contact the Global Technical Access Center (GTAC):
http://support.industrysoftware.automation.siemens.com.
Obsolete Teamcenter documentation

Name Description
Authorization Guide Content from this guide is now included in the
Application Administration Guide.
Change Viewer Guide The Change Viewer Guide is removed because the
Change Viewer application is obsolete.
Command Suppression Content from this guide is now included in the
Guide Application Administration Guide.
Network Folders Guide The Network Folders Guide is removed because the
Network Folders client is obsolete.
Web Browser Guide Content from this guide is now included in the

What’s New
Teamcenter Rapid Start
Introducing Teamcenter Rapid Start as a pre-configuration of

Teamcenter
Teamcenter Rapid Start is a preconfigured deployment option of Teamcenter.
It provides a complete, easy-to-use, and easy-to-deploy collaborative product
development management (cPDM) solution that delivers a preconfigured yet
extensible environment.
This solution is designed to apply preconfigured best practices to everyday
engineering tasks and processes of the following organizations:
• Small to mid-sized manufacturing companies
• Well-defined departmental workgroups
• Suppliers to OEMs and other product manufacturers
For more information about Teamcenter Rapid Start, see Getting Started with
Teamcenter Rapid Start.
Installing Teamcenter
Teamcenter supports IPv6 networks

Teamcenter 10.1 adds support for Internet Protocol IPv6 in client interfaces that
use Teamcenter client communication system (TCCS) in four-tier environments on
IPv6-enabled networks.
IPv6 is the latest generation of network address protocol. It employs 128-bit
addressing, as compared to its predecessor, IPv4, which uses 32-bit addressing.
An IPv4 address is composed of four numbers between 0 and 255, for example:
146.122.220.221
An IPv6 address is composed of eight 16-bit hexadecimal values, for example:
2011:db8:ffff:1:101:12ff:de13:1322
Teamcenter 10.1 supports IPv6 addresses in the following clients that use
Teamcenter client communication system (TCCS):
• Four-tier rich client
• Thin client
• Teamcenter Client for Microsoft Office
• Lifecycle Visualization
IPv6 support for other Teamcenter clients will be added in future versions.

Note IPv6 support is limited to clients or integrations that use TCCS and
Teamcenter components that communicate with clients on IPv6-enabled
networks. Teamcenter enterprise tier server components that communicate
with other server components in the same network are assumed to be on an
IPv4 network and are not supported on IPv6.
For more information about using IPv6 addressing in a Teamcenter network, see the
System Administration Guide.
TEM creates compact installation package for simplified Teamcenter

deployment
Teamcenter Environment Manager (TEM) can create a compact deployable package
to simplify and expedite Teamcenter deployments, especially deployments of
multiple clients.
TEM can package a compact deployable Teamcenter installation package as an
alternative to installing from a full Teamcenter distribution image. This package can
contain a select subset of Teamcenter features instead of the entire set of features in
the release. This smaller package can be more easily distributed to an organization
and reduce network load during deployment.
For example, a two-tier rich client installation can be distributed in a package as
small as 580 MB, where a full Teamcenter software distribution image can be as
large as 5 GB. A four-tier rich client deployable package can be as small as 283 MB,
and a Client for Office deployable package can be only 93 MB.
This feature is available from the Create custom distribution option on the Welcome
to Teamcenter panel in TEM.
For more information about this feature, see the Teamcenter client installation
guides for Windows and Linux and Teamcenter Environment Manager Help.
Teamcenter registered in Windows program list

Teamcenter is registered in the program list in the Windows Control Panel after
installation, upgrade, or patching.
Teamcenter Environment Manager (TEM) registers Teamcenter in the program list
in Microsoft Windows. After installing Teamcenter using TEM, the Add/Remove
Programs dialog box in the Windows Control Panel contains an entry named
Teamcenter, appended with the path to the TC_ROOT location.
Note Installing Teamcenter using the Over-the-Web Installer does not register
Teamcenter in the Windows program list.
For more information about Teamcenter installation on Windows systems, see the
Installation on Windows Servers Guide and the Installation on Windows Clients
Guide.

What’s New
Teamcenter can be fully uninstalled using TEM

Teamcenter can now be fully uninstalled using Teamcenter Environment Manager
(TEM).
You can initiate a complete uninstallation of Teamcenter from TEM or, on Microsoft
Windows systems, from the Add/Remove Programs dialog box in the Windows
Control Panel.
For more information about uninstalling Teamcenter, see the appropriate
Teamcenter server installation guide (for Windows or UNIX/Linux) or the
appropriate Teamcenter client installation guide (for Windows, Linux, or Macintosh).
Teamcenter installation tools verify Java version

Teamcenter Environment Manager (TEM) verifies the required version of Java is
available on the host. If the required version is not present, TEM does not launch.
Siemens PLM Software no longer provides a Java Runtime Environment (JRE) with
Teamcenter software. You must download and install the required JRE before you
install Teamcenter. Teamcenter 10 requires version 1.7 of the JRE.
Before you launch TEM to install Teamcenter, specify the location of the JRE by
one of the following methods:
• Set the appropriate environment variable on your host:
o 32-bit Java
Set the JRE_HOME environment variable to the location of the 32-bit Java
JRE.
o 64-bit Java
Set the JRE64_HOME environment variable to the location of the 64-bit
Java JRE.
Note You must use the appropriate Teamcenter software distribution image
(32- or 64-bit) for the JRE you use.

• Use the -jre argument to specify the JRE location when you launch TEM from a
command prompt:
tem —jre JRE-path
For example:
tem –jre c:\apps\jre1.7
Note If the path to the JRE contains spaces, enclose the path in double
quotation marks. For example:
tem -jre "C:\Program Files (x86)\Java\jdk1.7.0\jre"
TEM stores the JRE location during Teamcenter installation. After installation is
complete, TEM no longer requires the JRE_HOME or JRE64_HOME environment
or the -jre argument.
For more information about required versions of the JRE for Teamcenter, see the
Siemens PLM Software certification database:
http://support.industrysoftware.automation.siemens.com/ certification/teamcenter.shtml

What’s New
Teamcenter Environment Manager creates copy of production

environment
Teamcenter Environment Manager (TEM) can create an environment based on
a copy of production database. This is useful in performing a test upgrade of
Teamcenter.
This new functionality provides the capability of creating a test environment based
on a copy of production database for upgrade testing. This environment is intended
to be used only for the purpose of testing a Teamcenter upgrade.
Providing this option in TEM greatly reduces the manual steps previously required
to create a test system, simplifying test upgrades and providing more reliable results.
To use this feature, launch TEM and select the Create environment for upgrade
testing option and then click Install.
Testing production upgrade before upgrading production database is critical for the
successful upgrade of a production database. Copying a Teamcenter production
environment for test upgrade is an important step in upgrading Teamcenter. An
incorrectly configured test environment can lead to many upgrade problems that
delay the upgrade of the production database.
For more information, see the Upgrade Guide.
Teamcenter supports new application server and Eclipse versions

Teamcenter 10.1 and Global Services Web applications can be deployed on WebLogic
12.c and WebSphere 8.5. Additionally, Global Services Web applications can be
deployed on a JBoss 7.1 application server. Previously, JBoss 7.1 was supported
only for Teamcenter Web applications.
Note JBoss 7.1 does not support a front-end web server, such as Internet
Information Server (IIS). Therefore, you cannot deploy Teamcenter in the
H-SE configuration on JBoss.
For more information, see the Web Application Deployment Guide.

The Briefcase Browser, the Business Modeler IDE, and rich client customization
now support Eclipse 3.8.
For more information, see the Briefcase Browser Guide and the Business Modeler
IDE Guide.
For the most current information about versions of operating systems, third-party
software, Teamcenter software, and system hardware certified for your platform,
see the Siemens PLM Software Certification Database:
Note Some software requirements differ for non-English locales. When viewing
the certification database, make sure you note any exceptions for your locale.

J2EE server manager runs as a service or daemon

Teamcenter 10.1 adds support for operating the J2EE server manager as a Windows
service on Windows systems and as a daemon on UNIX/Linux systems.
During installation of the J2EE server manager, you choose one of the following
startup modes for the server manager:
• Service/Daemon
• Command Line
To install the J2EE server manager as a service or daemon, choose Service/Daemon.

(This is the default option.) On Windows systems, the server manager runs
as a Windows service automatically. On UNIX/Linux systems, the installer or
administrator must run the root_post_tasks_*.ksh postinstallation script to
register the J2EE server manager daemon in the system /etc directory. When the
system is restarted, the J2EE server manager daemon starts with the other daemons.
This feature includes additional enhancements:
• Simplified installation
Installation options for the J2EE server manager are simplified in Teamcenter
Environment Manager (TEM). Some advanced settings are removed from TEM
but can still be configured manually in the server manager configuration file.
• Directory structure supports multiple services or daemons

The run-time directory structure for the J2EE server manager now supports
multiple server manager services or daemons on the same host. Each service or
daemon is given its own configuration directory and log files.
The server manager run-time directory is placed in the following location:
TC_ROOT\pool_manager\confs\config-name
Replace config-name with the name of the specific server manager configuration.
Each server manager configuration directory contains a logs directory. When
the service or daemon is running, all server manager output is recorded in a
mgr.output file in the configuration directory.
• Upgrade and patching

During upgrade, TEM creates the server manager services and imports the
existing server manager configuration before removing the previous server
manager.
Note Administrators must stop the existing server manager before beginning
upgrade.
During patching, TEM stops the server manager service before patching and
restarts the service after patching.
Note This feature affects the J2EE server manager only. There are no changes to
the .NET server manager.

What’s New
For more information, see the System Administration Guide and the Teamcenter
server installation guides (for Windows and UNIX/Linux).
Teamcenter supports client-certificate authentication

Teamcenter 10.1 adds support for client-certificate authentication using a smart card
or a soft certificate, for example, a .p12, .pfx, or .jks file.
Teamcenter also now supports display of a notice and consent logon banner. This is
a message displayed at logon that notifies users of the legal rights of users on the
network. Teamcenter administrators can define the contents of the notice displayed
when Teamcenter users log on.
Client-certificate authentication allows Teamcenter to use a digital certificate
in a public key infrastructure (PKI) for authentication to protected Teamcenter
applications. Client-certificate authentication is an alternative to basic, digest,
NTLM, Kerberos, or form-based authentication. It uses HTTP over SSL (HTTPS), in
which the server and the client authenticate each other using a public key certificate.
Client-certificate authentication provides data confidentiality, data integrity, and
client and server authentication for a TCP/IP connection.
In client-certificate authentication, clients are required to submit certificates that
are issued by a certificate authority that you choose to accept.
A client certificate can be in one of the following forms:
• A smart card containing a client certificate and adhering to PKCS #11 standard.
Smart card authentication is an example of two-factor authentication (2FA)
that requires the presentation of something the user knows and something the
user has.
Note Smart card authentication is supported only on Windows platforms with
32-bit Teamcenter client applications. It is not supported for 64-bit
Teamcenter client applications.
• A file containing a client certificate and adhering to PKCS #12 standard.

Commonly used file extensions are .p12, .pfx, or .jks. These types of certificates
files are also known as soft certificates. This is supported with both 32-bit and
64-bit Teamcenter client applications on Microsoft Windows, Red Hat Linux, and
SUSE Linux systems.
For more information, see the Security Services Installation/Customization guide

and the Teamcenter server installation guides (for Windows and UNIX/Linux).
Configuring Teamcenter
Business Modeler IDE
Enhanced Save As functionality

The Save As functionality is enhanced in the rich client:
• The Save As action can be performed on any workspace object. Previously, it
was available only on item revisions.

• The appearance of the Save As wizard is enhanced. To see the new wizard,
select an object and choose File→Save As.
Note If you have custom code for the Save As dialog boxes, you must migrate
it to the new Save As wizard.
• You can now define the properties displayed in the Save As wizard. To define
them, use the SaveAsInput operation on the Operation Descriptor tab in the
Business Modeler IDE.
• The deep copy rules now allow you to copy any object and to configure deep
copy rules on any persistent business object. Previously, deep copy rules were
allowed only on the ItemRevision business objects and its children. Also, deep
copy rules can now be configured on reference properties in addition to relation
properties. To configure, use the Deep Copy Rules tab in the Business Modeler
IDE.
For more information, see the Business Modeler IDE Guide and the My Teamcenter
Guide.
Mapper lookup table

The Mapping Designer module of the Business Modeler IDE allows customers to
map the property values in one system (for example, Teamcenter Enterprise) to
another (for example, Teamcenter) for data migration or data sharing. The lookup
feature in Mapping Designer allows customers to transform an input value to an
output value using a lookup table.
For example, suppose you want to map the user property from one system to
another. In the first system, users are identified by their first name and last name,
and in the second system, they are known by an ID number. You can place a lookup
table between the user property on the two systems that maps the value of one
property to the value of the other.
Mapper lookup tables supports factor inheritance, conditional lookups, and
factor-specific lookups using in-factor artifacts. The mapper lookup functionality
consists of two main components:
• A set of features in the Mapping Designer that allows creation and manipulation
of lookup definitions
• A lookup component within the mapper engine that carries out the lookups at
runtime
Configure deep copy rules used in revisions

End users choose File®Revise in the rich client or Edit®Revise in the thin client to
revise an item revision.
Now you can use the Business Modeler IDE to configure some new aspects of how
deep copy rules are handled during revise operations:
• Configure deep copy rules for the revise operation on all business object types.
• Configure deep copy rules for reference properties during the revise operation.

What’s New
• Manage the Save As action on deep copy rules with the

CopyAsReferenceOrReferenceNewCopy action.

The TC_dataset_deep_copy_rules preference is deprecated. So while the deep
copy action during a revise operation continues to process this preference, the system
ignores preferences with conflicting deep copy rule configurations. The recommended
best practice is to replace any existing TC_dataset_deep_copy_rules preferences
with deep copy rules in the Business Modeler IDE.
For more information about this preference, see the Preferences and Environment
Create dynamic LOVs more easily

Lists of values (LOVs) are lists in property boxes in the user interface. Dynamic
LOVs show a list of values obtained dynamically by querying the database.
Previously, when creating a dynamic LOV in the Business Modeler IDE, you wrote
code to do the querying. Now you can create a query as part of the dynamic LOV
definition. This makes it much easier to create queries because no coding knowledge
is required. You can query for product data from objects such as items, parts, and
datasets, or query for administrative data from categories such as users, groups,
and roles. You can use the property values of the queried data as the LOV value
and description. You can also specify other properties on the queried data as filter
attributes that help the end user to filter down to the LOV value of interest.
When you create dynamic LOVs, the database must hold instances of the type
specified in the Query Type box of the New Dynamic LOV dialog box. You can
use existing instance data, or you can create instance data for your own custom
business object. You can also use the COTS Administrative List Of Values
(Fnd0AdminLOVValue) business object to create instances by either creating the
instances in Teamcenter clients, or by using the tcxml_import utility to import
instance data from an XML file.
To create a dynamic LOV in the Business Modeler IDE, open the Extensions®LOV
folders, right-click the Dynamic LOV folder, and choose New Dynamic LOV.
Creating a dynamic LOV

In the following sample dynamic LOV, note how you can create query criteria. This
sample dynamic LOV queries for all instances of a custom Part business object
owned by the Engineering group.

Sample dynamic LOV

When you click the Test button, the query is sent to the database, which returns
the results.
Testing a dynamic list of values

What’s New
For more information about creating dynamic LOVs, see the Business Modeler IDE
Guide.
Simplified Business Modeler IDE user interface
The Business Modeler IDE user interface is simplified through the following changes.
For more information about the user interface, see the Business Modeler IDE Guide.
• Business Modeler IDE user interface enhancements
o Standard perspective
Provides a simplified user interface. The old Business Modeler IDE
perspective is still available as a secondary user interface now named the
Advanced perspective.
Before - Now called the Advanced After - The Standard perspective

perspective
The BMIDE view in the Standard perspective provides a single view for
favorites, data model elements, and project files.

BMIDE view
o New Model Element wizard

Lists all wizards for element creation.
New Model Element wizard
o Apply button when creating lists of values and deep copy rules
Saves the user from having to use the wizard each time to perform the action.

What’s New
Apply button
o Required box designators

Indicate mandatory boxes with a red asterisk (*). A red border shows boxes
containing errors.
Apply button
o Subtabs in the Properties tab

Prevent content from running off the bottom of the viewable page.

Subtabs in the Properties tab
o Toolbar customization
Customize toolbars to contain actions for the most commonly-created
elements. Choose Window®Preferences, and in the Preferences dialog box,
select Teamcenter®Toolbar Customization.

What’s New
Toolbar customization
o Toolbar modifications
Move buttons from the context menu (right mouse button) to the toolbar.
Button Name
icon
Reload Data Model
Organize Extensions
Open Global Constants Editor
Open GRM Rules Editor
Open Verification Rules
Provide the most commonly required actions on the Organize Extensions

button.
Organize Extensions button

Reduce the number of menu options on the context menu (right mouse
button).
Smaller context menu
Place a New Model Element button and a Find button on the toolbar.
New Model Element button and Find button on the toolbar
o Organizing elements using filters and favorites.

Allows you to hide elements or only hide COTS elements.
Hide elements
Configures what business objects to display. Right-click the Business

Objects folder and choose Filter®Business objects to display.

What’s New
Configure business objects to display
Adds elements to Favorites for quick access.
Add to Favorites from context menu
Adds elements to Favorites from editors.

Add to Favorites from editors
o Improvement in search functionality.

Finds a specific element using the context menu.
Find an element from the context menu
Shows a description of the selected element in the Find dialog box.
Descriptions in the Find dialog box

What’s New
o Double-click in editors
Launches the edit dialog box for the element when you double-click a box
with data in it, or launches the add dialog box for the element when you
double-click an empty box.
Double-click in editors
• Tools
o Import project from package
Formerly, if you needed to retrieve a backup of your project, you downloaded
the backed up project from the Teamcenter database. Now you can import
the project from the package files. Choose File®Import®Business Modeler
IDE®Import a Business Modeler IDE Template Package.

Import project from package
o XML sorting
Formerly, XML elements in project extension files were not sorted. Now they
are sorted alphabetically within their groups.
• Troubleshooting
o Problems view
Shows problems in the project. Double-clicking a problem in the Problems
view takes you directly to the problem location in the project files.
Import project from package

What’s New
Multifield keys
Multifield keys
Multifield keys are identifiers assigned to each object to ensure their uniqueness in
the database. The unique identifier is composed of a domain name and a combination
of the object’s properties. For example, the default multifield key for item business
objects is Item{item_id}.
Administrators use the MultiFieldKey business object constant to assign the key
definitions to different business object types. When the template is installed to
the Teamcenter database, all instances of those business object types get that key
definition. Administrators can add multiple properties to define a key.
MultiFieldKey business object constant on the Item business object

In a multifield key definition, the domain is the name of the business object type
where the multifield key is defined. For example, in the Part{item_id} key, Part
is the domain. Because all children of a business object type inherit the multifield
key definition, they belong to the same domain. Establishing domains allows
administrators to identify the object types that have the same multifield key. This
ensures a unique identifier across all the objects in the domain.
Prior to Teamcenter 10, the value of the item_id property was assumed to
be an object’s unique ID. Now Business Modeler IDE administrators use the
MultiFieldKey business object constant to assign the key definitions to different
business object types. One of the reasons to use multifield keys to uniquely identify
objects is because end users regularly refer to multiple related objects using the
same item ID. For example, end users can refer to a part and drawing using the
same item ID or part number. To help maintain uniqueness of the object instances
in the database, an administrator could define the unique key for part business
objects and their children as Part{item_id} and for drawing business objects and

their children as Drawing{item_id}. When these definitions are applied, it results

in a unique key for each instance of an object type in the database, even though
the different object types can use the same item ID. (A part and a corresponding
drawing can have the same item ID.)
If you search for an item ID that is used by multiple objects, a dialog box is displayed
that allows you to choose the desired object from the list of all objects with the same
item ID.
Searching for an item ID used by multiple objects

An administrator can restrict the ability of others to change multifield key definitions
by using the following global constants:
• Fnd0MultiFieldKeyExclusions
Excludes selected business object types and their children from having their
multifield keys definitions changed. The business objects types that already that
have the multifield key defined cannot be added to this exclusion list.
• Fnd0SecuredMultiFieldKey
Ensures that dependent templates do not change the MultiFieldKey business
object constant on specified business objects and their children.
In addition, an administrator can analyze multifield key definitions or rebuild

multifield key values in the database using the mfk_update utility.
For more information about multifield keys, see the Business Modeler IDE Guide.
Application changes to support the use of multifield keys

Teamcenter applications are changed to support the use of multifield keys, which are
identifiers assigned to each object to ensure their uniqueness in the database. For
more information about these application changes, see the following topics:
• Options and variants support for multifield keys

What’s New
• Visualization support for multifield keys
• MRO support for multifield keys
• Aerospace and Defense multifield keys support
• Launch tool enhancements for multifield keys
• Structure management enhancements for multifield keys
For more general information, see the Business Modeler IDE Guide.
Server changes to support the use of multifield keys

The -key argument is added to some utilities. This argument specifies the multifield
key ID of the item to act on and provides an alternative to the -item argument as a
method to specify items. The -key argument was previously added to other utilities
in earlier versions of Teamcenter.
The -key argument is added to the following utilities:
import_file
item_export
item_to_part_design
ps_upload
qpl_convert_occs2tc
rdv_context_download
rdv_run_audit_report
rdv_set_default_variant_condition
release_man
sync_on_demand
sync_product_apns
sync_product_variant_data
tc_workflow_postprocess
update_apprpathroot
update_bomchanges
update_project_bom
For more information about these utilities, see the Utilities Reference.
To obtain the key ID for an item, use the get_key_string utility.
New multifield key preference

A new TC_MFK_DEFAULT_DOMAIN preference defines the domain used by the
ITEM_find_item ITK function when the multifield key unique identifier is not
used. A valid value is a business object type name (for example, Item). The search
operation searches among objects of the specified type.
This preference enables users of nonmultifield key compliant applications, such as
external CAD applications, to define the domain where objects exist.
For more information about the TC_MFK_DEFAULT_DOMAIN preference, see
the Preferences and Environment Variables Reference.

Preferences
Control access to preferences and options

Teamcenter preferences are redesigned to place preference access fully under
customer control.
Previously, administrative, group, role, and user access to preferences were defined
in each preference’s scope. Preference scope was coded into each preference. This
implementation had limitations, including:
• No method for Teamcenter administrators to change the scope of a preference.
• The dialog box provided no feedback to indicate whether the creation of a

preference instance with a particular scope would be supported.
• The ability to create multiple instances of preferences with different scopes

resulted in inconsistencies between the documented scope and the actual
implemented code.
The redesign of Teamcenter preferences introduces a new category of preferences,

named system preferences.
• System preferences apply to the entire Teamcenter deployment and are governed
by strict access controls.
• Hierarchical preferences have a protection scope of User, Role, Group, or Site.

The system uses the hierarchy, beginning with User, then checking Role,
Group, and Site locations to retrieve a preference value.
For more information about the system and hierarchical preferences, see the
Preferences and Environment Variables Reference.
Additionally, the redesign of Teamcenter preferences removes the concept of scope.

Access to each preference is now determined by its protection scope. The protection
scope of hierarchical preferences can be easily changed from their default shipped
value to meet business needs. The protection scope of system preferences cannot
be changed. The protection scope defines where the system starts the hierarchical
search as well as controls where preference instances can be created.
For more information about how preference values can be defined at different levels
depending on the defined protection scope, see the Preferences and Environment
Protection scope can be managed either:
• In the Options dialog box.
This method is best for modifying small numbers of preferences, individually.
• Using the preferences_manager utility.

This method is best for updating the protection scope, values, and behavior
of many preferences simultaneously.
Additional enhancements to the Options dialog box include:

• Fields are now enabled/disabled, depending on user access to the field.

What’s New
• The new Environment Variable field allows administrators to specify whether

the preferences setting can be set using an environment variable.
This setting is independent of the protection scope.
• The display of tabs vary, depending on the user’s logged-on role.
• Changes to user interface components.
Current terms Pre-10 terms

In the bottom right of the In the bottom right of the dialog box, the
dialog box, the available tabs available tabs are:
are:
Options
Options Index
Filters Search
Search Organization
Organization
Selecting Filters displays the Selecting Index displays the Preferences
Preferences By Filters pane. pane.
In the Preferences By Filters In the Preferences pane, tabs (displayed in
pane, available tabs (displayed the lower right), are always:
in the upper right), vary
depending on user access. Details
New
All possible tabs are: Category
Import
Definition Export
Instances
Category
Import
Export
Selecting Search displays the Selecting Search displays the Search Options
Preferences By Search pane. pane.
Selecting Organization Selecting Organization displays the
displays the Preferences By Organization pane.
Organization pane.
For more information about using the Options dialog box, see the Rich Client
Interface Guide.
Additional enhancements to the preferences_manager utility include:
• The import, export, and append modes are enhanced to support the new
protection scope functionality, support multiple targets, provide reports, and
so on.
• The new upgradeXML mode allows you to upgrade the preference file from a
legacy format to the current format.
• The new cleanup mode allows you to remove stale preferences not removed
by other administrative tasks.

For more information about using the preferences_manager utility, see the
Utilities Reference.
Preferences
Teamcenter 10.1 includes the following new preferences:
ADSDesign.SUMMARY_REGISTEREDTO=ADSDesign
ADSDesign.SUMMARYRENDERING=ADSDesignSummary
ADSDrawing.SUMMARYRENDERING=ADSDrawingSummary
ADSDrawingSummary.SUMMARY_REGISTEREDTO=ADSDrawing
ADSPart.SUMMARY_REGISTEREDTO=ADSPart
ADSPart.SUMMARYRENDERING=ADSPartSummary
AssignFinishDialog
BOM_Display_Attachments_Panel
BOM_Display_Referencer_Panel
BOM_Display_Variant_Super_Panel
BOM_Frozen_Column_Count
cae_datamap_files_location
cae_structureMap_log_dataset_name
CC_ExtraPLMXMLInstanceAttributes
Cm0GnReviewRevision_Cm0ActionItemRevision_default_relation
ConfigureOutParentProcess
CPD_Default_RevRule
CPD_mandatory_effectivity_qualifiers
CPD_Related_Objects_Search_Option_ClosureRule
CR-notify handler changed to EPM-notify-report
CrossProbing_AllowedRelationTypes
CrossProbing_RelationDepthTraversal
CrossProbing_RelationTraversalType
CrossProbing_SelectedRelationTypes
ctm0DIsableS100DItemIDCheck
ctm0RestoreStateOfPubStructure
DisableSaveSos
EPM-add-released-parts-queue handler changed to
RDV-add-released-parts-queue
EPM-send-target-objects handler changed to OBJIO-send-target-objects
EPM_task_execution_mode
EPM-tesselation-handler handler changed to RDV-tessellation-handler
Excel_Office_Launchable_TcTypes
Excel_ViewMarkup_Launchable_TcTypes
FMS_SAF_Batch_Transfer_Enabled
Fnd0LicenseExportAuditSec_ColumnPreferences
Fnd0ScheduleAuditSec_ColumnPreferences
Fnd0StructureAuditSec_ColumnPreferences
Fnd0WorkflowAuditSec_ColumnPreferences
HTMLStylesheetIncludes
HTMLStylesheetSharedLibs
HTMLStylesheetUnsupportedRenderingHints
LicenseUsage_module_usage_warning_level
LOV_value_desc_separator
ME3DPDFAllowedReportTemplate
ME4DProcessStartDateFromTask
ME4DSearchCriteriaDate

What’s New
MEDoNotUseSCTypeForColumns
MEFourDResultsViewColumnsWidthPref
MEFourDResultsViewDisplayNameColumnsShownPref
MEAccountabilityCheckMappedAttrGrpsForComparison
MEAccountabilityCheckMappedAttrGrpsForPropagation
MEMESReleaseStatus
MEMESReleaseTraversalClosureRule
MEMESUpdateWorkflows
MEMESWorkInProgressReleaseStatus
MEOPRevison_DefaultChildProperties
MEProcessRevison_DefaultChildProperties
MEWiStandardTextTemplate
MEWiWorkInstructionMacroTemplate
MEWiWorkInstructionTemplate
NE_Relation_Rule_relation_list
Outlook_Office_Launchable_TcTypes
Outlook_Sign_Launchable_TcTypes
Outlook_ViewMarkup_Launchable_TcTypes
PCA_enable_authoring
PLMXML_export_legacy_EngChangeRev
PLMXML_IC_Delta_export_transfermodes
PortalDesignContextProductItemQuery
PowerPoint_Office_Launchable_TcTypes
PowerPoint_ViewMarkup_Launchable_TcTypes
Process.Template.Cloning
Process.Template.Ignoring_Consumes
Process.Template.Mapping_Consumes
Process.Template.Referencing_Consumes
PS_Bypass Occurrence Condition
PS_Default_Rev_For_Occ_Cond_Validation
PSE_ShowSubstitutesPref
PSM_classic_variants_logical_families
PTN0_Default_CarryOver_ViewData
PTN0PartitionTemplateModelCREATE_REGISTEREDTO
PTN0PartitionTemplateModel.CREATERENDERING
QSEARCH_disable_bbox_for_product_scoping
QSEARCH_process
Rollup_Variant_Feature
RollUp_Variant_Traverse_Level_Is_InstallationAssembly
ScheduleTask.CHGDETAILRENDERING
search_suppress_results_count
Siemens_PL_email_id
SM_SCHEDULE_DATE_LINKED_TO_ACTUAL
StructureManagerIncludeSubComponentsForSpatialSearch
SUBSCMPL_msd_always_send_blank
SUBSCMPL_msd_create_new_materials
SUBSCMPL_msd_create_new_substances
SUBSCMPL_msd_default_pdf_file
SUBSCMPL_msd_default_xml_file
SUBSCMPL_msd_done_dir
SUBSCMPL_msd_error_dir
SUBSCMPL_msd_file_naming_prefix
SUBSCMPL_msd_import_notifiers
SUBSCMPL_msd_include_pdf

SUBSCMPL_msd_incomplete_composition_limit
SUBSCMPL_msd_part_unique_attrib_maps_to
SUBSCMPL_msd_partial_disclosure_limit
SUBSCMPL_msd_processing_dir
SUBSCMPL_msd_use_unknown_material
SUBSCMPL_msd_use_unknown_substance
SUBSCMPL_msd_vendor_unique_attrib_maps_to
SUBSCMPL_request_msd_mode
SUBSCMPL_substance_composition_tolerance
SUBSCMPL_unknown_material_ext_id
SUBSCMPL_unknown_material_name
TC_audit_manager_version
TC_CFG_PRODUCTS_USE_VARIABILITY
TC_cms_relation_optset_map
TC_dataset_deep_copy_rules
TCDigitalSigningApplicationPref
TC_Fnd0SoaConfigFilterCriteria_AutoCheckinRevisable
TC_Fnd0SoaConfigFilterCriteria_AutoPublishRevisable
TC_inbox_interval
TC_language_no_encoding_discrepancy_warning_message
TC_MFK_DEFAULT_DOMAIN
TC_publish_item_or_itemrev
TC_QRY_search_result_display_mode
TC_Store_and_Forward
TC_SwitchToLegacyItemCreate
TC_USE_TEST_ATTR_MAPPINGS
TC_VariantConfigurable_MaxCacheSize
UGS_LICENSE_SERVER environment variable changed to
SPLM_LICENSE_SERVER
WEB_default_site_server
WEB_default_site_deployed_app_name
WEB_status_icons
Word_Office_Launchable_TcTypes
Word_Show_Display_Name
Word_ViewMarkup_Launchable_TcTypes
For more information about these preferences, see the Preferences and Environment
Administering Teamcenter
Audit Manager enhancements

A new Audit Manager application is available with the following functionalities:
• Capability to create audit definitions, event types, and event type mappings
using the Business Modeler IDE application
• Capability to store audit data in different database tables. This makes searching
for audit logs faster
• Capability to purge audit records

What’s New
• New audit reports
• Capability to create audit queries using the Query Builder application
• View audit information in the Summary view of Teamcenter applications like

My Teamcenter, Authorized Data Access, Structure Manager, Multi-Structure
Manager, Platform Designer, Workflow Viewer, and Schedule Manager.
• Capability to migrate Audit Manager configuration information from the old

Audit Manager application to the new Audit Manager application
• Capability to migrate audit logs from the old Audit Manager application to the
new Audit Manager application
• Capability to view legacy audit records from the Audit logs tab
• Capability to export audit logs from the Audit logs tab
• Capability to export audit logs from the Details view
To use these new functionalities, you must set the value of the
TC_audit_manager_version preference to 3.
Note The old Audit Manager application is deprecated and will be removed in
a future version.
For more information, see the Audit Manager Guide.
Vendor Management supports multifield keys

In vendor management, the VendorPart object uses the new multifield key
capability. The multifield key definition of VendorPart is the VendorPart ID and
the associated vendor reference: item_id, vm0vendor_reference. Therefore, you
can create multiple VendorPart objects with the same VendorPart ID. During
VendorPart creation, if duplicate vendors exist with the same vendor ID, a new
dialog box, Item Resolution, appears allowing you to select the appropriate vendor.
For more information, see Getting Started with Vendor Management.
Update object properties in bulk

Teamcenter administrators can now update the properties of a large number of
objects in bulk using a two-step process:
1. Use the new attribute_export utility to:
• Query for specified properties and their current values.
• Provide new values for the specified properties.
• Export the data to a TC XML file.
2. Run the existing tcxml_import utility with the -bulk_load and

-bypassSiteCheck arguments to import the updated properties stored in the
TC XML file back into the database.

The values of the specified properties are updated during import.
For complex update operations, Teamcenter administrators can create an input XML
file containing instructions on which objects to update and the new values to apply.
The file is constructed as a series of UpdateSet entries; each entry must contain
type, where, and update components.
Before performing lengthy update operations, Teamcenter administrators can use the
utility to determine the number of objects affected by a specified update operation.
For more information about the bulk update process, including instructions on
creating the input file, examples of different update operations, and performance
statistics, see the System Administration Guide.
Managing authorized data access

Access Manager now provides 12 new rule conditions in the following categories to
facilitate authoring fine-grained access rules for managing authorized data access
(ADA):
• To check for a user on a specifically named intellectual property (IP),
International Traffic in Arms Regulations (ITAR), or exclude license, irrespective
of whether the license is attached to the workspace object being evaluated.
• To check for a user on any or all IP, ITAR, or exclude licenses that are attached
to a workspace object.
• To check if the workspace object has a specific named IP, ITAR, or exclude
license attached.
For more information, see the Security Administration Guide.
Validation Manager enhancements

There are three new Report Builder reports for validation results.
• VO - NX Validation Result on Item Revisions displays all NX Check-Mate
validation results on the item revisions specified in the search criteria.
• VO - Item Revisions Validation Results displays all NX Check-Mate validation

results on the selected item revisions.
• VO - Validation Result with Override Requests Information reports the

override request properties on validation results and also includes the override
information.
Validation Manager also supports multifield keys.

For more information, see the Validation Manager Guide and the Report Builder
Guide.
Users can validate 4th Generation Design objects

Users can validate 4th Generation Design (4GD) reuse design element and shape
design element objects in addition to other standard Teamcenter objects, such as
items and item revisions.

What’s New
For more information about using Validation Manager to validate objects, including
4GD objects, see the Validation Manager Guide.
Client cache enhancements

The performance of the generate_client_meta_cache utility is enhanced. There
is a 30 percent improvement in the execution of the command line utility relative
to Teamcenter 9.1. Some performance improvement is also apparent in a TEM
install/upgrade or Business Modeler IDE hot deploy if the option to run the client
cache is selected.
For information about using this utility, see the Utilities Reference.
Configuring authorized data access (ADA) license categories

Administrators can now use the Business Modeler IDE to configure user-defined
license categories using the Fnd0ADALicensecategories list of values (LOV).
Users can set the license category when modifying or creating an International
Traffic in Arms Regulations (ITAR), intellectual property (IP), or exclusion license
and define Access Manager rules that check for the license category.
The ada_util utility has also been enhanced to enable it to associate a license
category with an ADA license.
For more information, see the Authorized Data Access License Guide.
Designating multiple project team administrators

You can now designate more than one project team administrator per project.
Also, the following usability enhancements are made to the project definition
functionality:
• Added ability to select team members within the team tree and set their status
as privileged, nonprivileged, or project team administrator using a shortcut
menu. The separate dialog box for performing these tasks is removed.
• Enhanced the display of the team member tree so that both role and group are
displayed beside the user names.
• Added ability to filter the team member tree to display only privileged,
nonprivileged, or project team administrator members.
• Added ability to search the project team member tree in the same manner that
you can currently search the organization tree.
• Moved search boxes and buttons to be displayed above the organization and
team member trees rather than below them.
For more information, see the Project and Program Guide.

Teamcenter stores passwords on disk in an advanced encryption

format
Teamcenter now stores passwords in disk files using advanced encryption standard
(AES) 256-bit encryption. These encrypted passwords are used by Teamcenter
utilities, services (daemons) that access the Teamcenter database, and Teamcenter
Environment Manager (TEM).
During installation, the TEM installer provides a Password Security panel that
allows you to designate the path to the directory that contains the password files.
TEM also locks access to the password directory to all users except the operating
system user performing the installation.
Caution For security reasons, access to the password directory must not be
changed unless other methods of ensuring access control are in place.
In maintenance mode, choose Update Security on the Feature Maintenance panel

in TEM to change the directory where the password files are stored. Changing the
stored password does not change the Teamcenter database password. This must be
done separately in the rich client interface.
Password Security panel in TEM

The Teamcenter utilities that support the password file argument (-pf) read the
encrypted password and decrypt it for use in the utility functions.
Three new arguments for the install utility support password encryption:
• -encryptpwf calls the encrypt password function,
• -e specifies the environment variable that contains the password to encrypt, and
• -f specifies the file name that stores the encrypted password.
You can change the encryption key used to encode the password by creating a
CryptKey file in the TC_DATA directory and providing the key in the file.

What’s New
Note Changing the encryption key is not required and not a common practice.
For more information, see the Utilities Reference, System Administration Guide, and
the server installation guides (Windows or UNIX/Linux).
Tracking module usage

When a user tries to access a licensed module, its usage is granted or denied based
on the usage of that module in the month. M
Module warnings, based on usage of the module in a particular month, are enforced
to keep customers in compliance with their license agreement.
As an administrator, you can use the Report Generation Wizard from My Teamcenter
and run the Module Usage Report.
For more information, see the System Administration Guide.
Saved query results using revision rules

In Query Builder, administrator users can:
• Associate a revision rule to any ItemRevision saved query.
• Specify the default sort order attributes based on secondary objects for a saved
query. You can specify the default sorting attributes against attributes on
secondary objects.
In the rich client in My Teamcenter:

• Users can execute a saved query with an associated revision rule and see only
results that match both the search criteria and the revision rule.
• When a sort order is specified for a saved query, this sort order applies to all
users that execute that saved query. Users see the new sort attributes in the
existing Sort dialog box.
• Individual users can override sort order settings from the Sort dialog box.
A new preference, TC_QRY_xxx_REVRULE, where xxx the name of the saved

query, is provided to let the administrator specify a different revision rule for a saved
query. This preference can be defined at the user or group level to override the
site-level setting.
For more information, see the Query Builder Guide.
Support for multiple citizenships

Teamcenter now supports users with multiple citizenship, and enables
administrators to control access to restricted data based on citizenship. It lets
administrators:
• Create users with multiple citizenship in the Organization application and the
make_user utility.

• Create ADA licenses with multiple citizenship using the ADA License application
and the ada_util utility.
• Hide the citizenship, nationality, and geography of a user from other users.
• Use the new Access Manager conditions that are based on user and license
citizenship to create Access Manager rules to control a user’s data access based
on the user’s citizenship and the licenses attached to the restricted data.
For more information, see the Organization Guide and the Authorized Data Access
License Guide.
FMS UTF-8 support

The Teamcenter File Management System (FMS) now supports UTF-8 encoding,
providing:
• Greater flexibility for client applications. They can now use existing 8-bit
encoding (native), UTF-8 encoding (8-bit Unicode) or Unicode (wchar) APIs.
• Consistency between APIs (data types) and other services (for example, SOA).
Note Windows 7 or later is required for full UTF-8 support. Windows XP and
earlier versions are not supported by this UTF-8 implementation.
For more information about FMS, see the System Administration Guide.
License bundling
Teamcenter employs named user licensing, which ties each user in the system to an
available license and ensures the total number of active licenses of each type in the
system is always less than or equal to the number of licenses purchased.
Previously, your site’s licensing named user licensing requirements could be
managed with two licensing programs:
• Seat-level licensing
Specifies the base license level associated with each user, such as author,
consumer, and occasional user.
This association is mandatory for the users to log on to Teamcenter and use the
basic features of the Foundation template (core Teamcenter).
• Optional module
Includes all licensed Teamcenter features excluding those associated with seat
levels.
Optional module licenses are required to use certain Teamcenter solutions, such
as Change Management and Requirements Management.
Now a third licensing program is available:

• License bundles
Includes specified Teamcenter features comprising a seat level and/or optional
modules. License bundles are then assigned to specific users.

What’s New
The user assigned to the bundle is assured the availability of all the features
in the bundle.
You can use license bundling in conjunction with other licensing schemes.
Consider a scenario when a user is assigned a license bundle that does not
include Requirements Manager. When the user launches Requirements
Manager, the system confirms if the feature key exists in the license file outside
of the license bundle. If the feature key is found and a license is available, the
application can be used.
The following existing licensing functionality is enhanced to support the new license
bundle feature:
• The License Usage Report is extended to indicate which license bundles are
associated with which users.
• The License Bundle option is added to the Organization application, allowing

administrators to assign a license bundle to a user, one user at a time.
Lisence Bundle option
• The -licensebundle argument is added to the make_user utility, allowing

administrators to assign license bundles to users in bulk or individually.
• You can configure usage warnings for license bundle usage in the same manner
it is configured for feature licenses. A warning is issued when only a specified
number of licenses (the value of the license_warning_level preference) remain
unassigned.
• License bundle usage is logged in the same manner as seat level and optional
module licenses. As individual features within the bundle are checked out and
checked in, usage is logged in both the FLEXlm log and the Teamcenter database.
For more information about licenses, see the System Administration Guide.
Store and forward

Default local volumes are temporary local volumes that allow files to be stored
locally before they are automatically transferred to the final destination volume.
This functionality is also known as store and forward.
This functionality improves end-user file upload times from clients by uploading files
to a temporary volume. This is useful in situations when an FMS volume does not
exist on the LAN with the remote user. In these situations, the closer the initial
volume is to the user uploading the file, the faster the upload.

Legacy default local volume functionality moves files from the local volume one
at a time. Now you can use the store_and_forward Dispatcher translator, which
in turn uses the move_volume_files utility, which is enhanced to support store
and forward behavior.
For more information regarding configuring and using these two different methods,
see the System Administration Guide.
Administrators enable default local volume behavior with the
TC_Store_and_Forward preference. Specify which default local volume method to
use by setting the FMS_SAF_Batch_Transfer_Enabled preference.
When this functionality is enabled, users can specify which local volume to use in
the User Settings dialog box. By default, this value is unset.
Rich client settings Thin client settings
Previously, local volumes could only be specified using the Organization application,
which required administrative privileges.
For more information about default local volumes, see the System Administration
Guide.
Utilities
Teamcenter 10.1 includes the following new utilities:
4GD_populate_cd
ada_util
assy_jt_creator
audit_purge
cae_execute_datamap
cae_execute_structuremap
cae_migrate_datamap_definition
cae_validate_structuremap
create_or_update_bbox_and_tso
data_share
data_sync
EPM-add-released-parts-queue
identify_non_structure_edges
installmgr.bat
install
invoke-system-action
invoke-system-rule
make_user
manage_effectivity_options
mgrstop

What’s New
migrate_audit_configs
migrate_audit_data
migrate_home_folder
migrate_wf_handlers
move_volume_files
Ptn0_set_is_partition_owned_true
qsearch_process_queue
rc.tc.mgr_<config>
subscmpl_msd_import
tcxml_export
uninstallmgr.bat
update_apprpathroot
For more information about using these utilities, see the Utilities Reference.
Using Teamcenter interfaces
Teamcenter Client for Microsoft Office enhancements

Client for Office is enhanced in several major areas:
• Microsoft Office 2010 support
• Access to all core Office file types
• Transfer of checked-out objects
• Additional Teamcenter workflow features
Microsoft Office 2010 support
Client for Office incorporates the Teamcenter tab on the Office ribbon in the
following Microsoft Office 2010 applications:
• Word
• Excel
• PowerPoint
• Outlook
The Teamcenter tab features give you access to Teamcenter directly from these
Office applications. Some Teamcenter tab features are available only in particular
applications.

Note For Microsoft Office 2007, Client for Office support is unchanged.
• The Teamcenter tab is added to the Office ribbon in Word, Excel, and
PowerPoint.
• In Microsoft Outlook 2007, the main window contains a Teamcenter

custom toolbar that gives you access to Teamcenter workflow features.
The Teamcenter tab is added to the Office ribbon in each open Outlook
2007 message.
For more information, see the Client for Microsoft Office Guide.
Access to all core Microsoft Office file types

A new .NET application launcher enables Client for Office to open all core Office
file types from any Office application:
• For Microsoft Word, .docx or .doc.
• For Microsoft Excel, .xlsx or .xls.
• For Microsoft PowerPoint, .pptx or .ppt.
• For Microsoft Outlook, .msg.
For example, if you are running Word, you can open Teamcenter datasets in Excel,
PowerPoint, and Outlook. You can open the dataset in read-only mode, or you can
check out the dataset and open it for editing simultaneously.
Note • You can open any core Office file type from the Client for Office Browse
pane, Folder View pane, and Search Results pane.
• If you use the Open button on the Teamcenter tab, you can open only a
dataset whose file type matches the active Office application.
Transfer object reservations

If an object is currently checked out from Teamcenter under your user name, you
can transfer that reservation to another user. In the Teamcenter Check-In/Out
pane, select the Transfer Check-Out option to display a list of users. Then, select
the new user name for the reservation.
Additional Teamcenter workflow features

You can use Client for Office to:
• Perform Form, Condition, and Route workflow tasks.
You access your tasks from the Client for Office Perform Workflow Task pane.
This pane continues to support the Do, Review, and Acknowledge tasks.

What’s New
Note In Microsoft Outlook 2010 only, you can update your worklist by clicking
the Synchronize Teamcenter Tasks button on the Teamcenter tab of
the Office ribbon.
• Manage resource pool inboxes that you subscribe to.

You access resource pools by clicking the My Worklist button on the Teamcenter
tab of the Office ribbon.
o In the Browse pane and the Folder View pane, your My Worklist inbox
displays your subscription resource pools.
o In the Outlook Tasks List, your resource pools are displayed as categories.
The tasks assigned to each resource pool are listed below that category.
Note You can delegate or reassign tasks to resource pools as you do to other
users.
Getting Started with Teamcenter enhancements

In Getting Started with Teamcenter, the Logging on to Teamcenter topic is updated
with the following note:
Note Sites with more than one Teamcenter Security Services server configured in
the client_specific.properties file display a logon dialog box that includes
configured server name entries. You can select the server to which you want
to connect and click Connect to connect to that server.
Thin client user interface enhancements

The thin client is enhanced in several areas:
• In the Summary pane:
o Check In, Check Out, and Save buttons are moved to the header bar from
the bottom of the pane.
o Tabs are moved from above the header bar to below the header bar.
• In object set tables:

o Users can double-click an object in a table to open the object as the top-level
object in the table.
• The Organize Favorites dialog box displays favorites in a tree layout, rather
than a table layout.
• Relations can be selected during creation of new Item and Other objects.
• Direct access to online context help is now available for the following applications,
when the application is the currently active application in the thin client:
o My Teamcenter

o Structure Manager
o Manufacturing Process Planner
o Classification
o Adhoc Design Context
o DesignContext
o Schedule Manager
o Issue Manager
• The Help menu commands are now:

o Current Application
o Thin Client Interface Guide
o Help Library
• In addition to selection from a calendar, modifiable dates can now be selected

directly from the date control fields.
For more information about the thin client user interface, see the Thin Client
Interface Guide.
Classification query enhancements

The thin client Classification application now supports switching the measurement
system for property display and search. This capability is available on the Properties
and Query tabs.
For each of these interface components, the initial value is based on the system of
measurement associated with the classification class.
The previous mechanism for using preferences to set unit system selection is still
supported.
• ICS_web_preferred_unit preference specifies the active unit system.
• ICS_web_search_in_unit_system preference specifies the search unit system.
The thin client Classification application now lets users add a revision rule to a query.
On the Query tab, users can click the Revision Rule setting button to display the
Revision Rule setting dialog box, and then select the appropriate checkbox:
• Use Revision Rule
Enable or disable the revision rule during the search.
• Save as default
Set the selected revision rule as the default revision rule.
• Restore default

What’s New
Restore the revision rule that was set earlier as the default.
For information about managing classification data in the Classification application

in the thin client, see the Thin Client Interface Guide.
Rich client user interface enhancements

The rich client user interface has the following enhancements:
• Rich client view toolbar resize
When the rich client or a rich client view is resized, view toolbars and dropdown
menus always stay in same row.
o When the view toolbar is not wide enough to display all its items, a chevron
button is added to toolbar to indicate there are hidden toolbar items.
o Click the chevron button on a view toolbar to display a popup list for
access to any hidden items.
Note When the view toolbar is wide enough to display all its items, the
chevron button is not displayed.
• Rich client navigation pane section order

You can reorder sections in the left-hand navigation pane using the Navigation
Section Ordering dialog box or by dragging a section to a new location above
or below the current location.
To use the Navigation Section Ordering dialog box to order and set visibility
for sections:
1. Click the reorder button to display the Navigation Section Ordering
dialog box.
Use the left and right arrows to move one or more selection to or from the
Hidden Sections box.
2. Select one or more section titles and then use the up and down arrows or
click-and-drag to move the selection up or down the list.
To drag a section to a new location in the navigation pane:
1. Click in the section title bar to the right of the section title.
2. Drag the section up or down to a new location in the navigation pane.

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

For more information about the rich client interface, see the Rich Client Interface
Guide.
Rich client XRT style sheet, view, and create dialog box enhancements
The rich client has the following updates:
• XRT style sheet tags and attributes
These tags are deprecated:
o <firstColumn> and <secondColumn>
These two tags are replaced by <column>.
o <attachments>
This tag is replaced by <objectSet>.
o <view>
This tag is replaced by <section>.
These attributes are deprecated:

o text
This attribute is used by the <page>, <section>, and <command> tags and
is replaced by the title and titleKey attributes.
o defaultTitle
This attribute is used by the <command> tag and is replaced by the title
and titleKey attributes.
o format
This attribute is used by the <page> tag. It is no longer required because
the <firstColumn> and <secondColumn> tags are deprecated.
The commandLayout attribute is used in <section> tags.

o The commandLayout attribute in an XRT style sheet section tag specifies
whether the options are displayed vertically or horizontally. The default, if
not specified, is horizontal.
o This attribute is available for all provided XRT style sheets that include
an <actions> section.
All XRT-related entries are moved to text server files.

o Teamcenter no longer uses client side resource bundle files for XRT entry
lookup.
o All entries are moved to text server file.
For information about adding or modifying XRT entries, see the Client
Customization Programmer’s Guide.

What’s New
• Generic creation wizards for items, folders, and forms

The rich client provides a generic New Item creation wizard dialog box for Item,
Folder, and Form objects. The generic creation wizard is more flexible, and
property definitions are configurable. Properties configured in the template
for create definitions are displayed in the generic creation wizard, which also
provides the capabilities available in New Item legacy dialog box.
The generic New Item creation wizard dialog box is enlarged to display more
content and enhanced to retain new proportions when the dialog box is resized.
Note The TC_Enable_Legacy_Create preference specifies whether the
legacy dialog box or the generic dialog box is displayed for the rich client
File®New menu command for Item, Folder, and Form objects.
Note By default, the Configuration Item check box does not appear on the New
Item wizard. You must enable it using the Business Modeler IDE.
For more information, see the Structure Manager Guide.
• Generic creation wizards for objects and datasets

The generic New Other and New Dataset creation wizard dialog boxes lets you
specify a relation with the parent item from a provided a list of relations.
• Two business object constants, Fnd0EnableSubmitToWorkflow and

Fnd0EnableAssignProjects, control display of the Submit to Workflow pane
and the Assign to Projects pane in the generic create wizard.
o Fnd0EnableSubmitToWorkflow
Set this constant to true on a custom business object operation descriptor to
display the Submit to Workflow pane in the rich client generic dialog box for
the specified type and operation. By default for Item objects, the Submit to
Workflow pane is displayed.
o Fnd0EnableAssignProject
Set this constant to true on a custom business object operation descriptor
to display the Assign to Projects pane in the rich client generic dialog box
for the specified type and operation.
For information about working with business object constants, see the Business
Modeler IDE Guide.
• ExportToCSV dialog box

The rich client Details view toolbar includes a button to display the ExportToCSV
dialog box to export Teamcenter data in comma-separated value (CSV) format.
For information about creating items in the rich client, see the My Teamcenter Guide.

Preference names added to option descriptions and Using

Teamcenter Preferences video available
Option and preference documentation in the Rich Client Interface Guide is enhanced:
• Options described in the Option reference section list the related preference
names, and most preference names are linked to the full preference description
in the Preferences and Environment Variables Reference.
For more information about options you can set in the rich client, see the Rich
Client Interface Guide.
• The Using preferences topic includes a link to a short video, Using Teamcenter
Preferences, which explains how preferences are structured and how they are
viewed and modified.
For more information about using preferences, see the Rich Client Interface
Guide.

What’s New
Date Control enhancements

The Date Control dialog box in the rich client is enhanced.
A Today button is provided in all Date Control dialog boxes; users can now enter
valid date information manually or by using the Paste command.
• For date entry, the following delimiters are supported:
/ forward slash
, comma
. dot (period)
: colon
space
- hyphen
• Dates can be set in any valid format:

MM/dd/yyyy 1*4*2012
MMM/dd/yyyy Jan*4*2012
MMMM/DD/yyyy January*4*2012
yyyy/DD/MM 2012*4*1
yyyy/MMMM/dd 2012* January*4
yyyy/MMM/dd 2012*Jan*4
M/d/yy 1*4*12
o * must be a valid delimiter.
o Final date display (en_us) is January 4, 2012.
o Dates are formatted according to the Teamcenter locale.
• Date display is formatted according to client locale:
Language Format
English en_us January 4, 2012
German 4. Januar 2012
French 4 janvier 2012
Chinese 2012 1 4
Japanese 2012/01/04
Korean 2012 1 4 ( )
Polish 9 luty 2012

Named References dialog box revised

The Named References dialog box now provides an Upload button and a Download
button for adding files to a dataset or for creating a local copy of a file attached
to a dataset.
• The Upload button and Download button replace the Import and Export buttons.
• Related dialog boxes and messages also use the new terminology, but the old
terminology continues to exist in other areas of the software.
For more information about uploading and downloading named references, see the
My Teamcenter Guide.
My Teamcenter (2007) removed

The My Teamcenter (2007) application is obsolete. Documentation describing the My
Teamcenter (2007) application is removed from the Teamcenter 10.1 help collection.
Note The use of the MyTeamcenterLegacy value with the HiddenPerspectives
preference is no longer supported.
Siemens PLM Software recommends that deployments using My Teamcenter (2007)

migrate any custom functionality to the My Teamcenter application prior upgrading
to Teamcenter 10.1.
For more information about the My Teamcenter application, see the My Teamcenter
Guide.

What’s New
Application bar and browser title bar display

Two preferences are updated to support information displayed in the application bar
for the thin client and the rich client, and in the thin client browser title bar.
• appbar_title_contents
Specifies values to be displayed in the title string of the application bar for the
thin client and the rich client.
Valid values include:
user Specifies the full Teamcenter user name.
userid Specifies the Teamcenter logon user name.
group Specifies the group the logged-on user is assigned to.
role Specifies the role of the logged-on user.
site Specifies the site identifier.
curr_proj Specifies the current project selected.
prev_login_time Specifies the previous logon time.
prev_session_ip Specifies the previous session address.
current_login_timeSpecifies the logon time for the current session.
locationcode Specifies the location code identifier.
change_notice Specifies the current change notice in the rich client.
Note This value is not supported by the thin client.
Specifies the organization identifier.

version Specifies the version of selection.
Note The rich client application bar can also display a value for Organization,
but only when the TcSetOwningOrganization constant is set to true
in the Business Modeler IDE, and Organization is configured for the
group to which a logged-on user belongs.
For more information about the appbar_title_contents preference, see the


• WEB_title_contents
Defines the contents of the thin client browser title bar.
Valid values include:
application Specifies the current application name.
object Specifies the current selected object.
user Specifies the full Teamcenter 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.
rev_rule Specifies the active revision rule.
version Specifies the version of selection.
locationcode Specifies the location code identifier.
For more information about the WEB_title_contents preference, see the
Summary style sheet updates

Summary style sheets determine the layout of the Summary view in the rich client
and the Overview tab in the thin client. Summary style sheets are enhanced to
better reflect how our customers and the industry use our products.
The purpose of this enhancement is to:
• Present industry-neutral style sheets.
• Deliver a more business-focused user experience.
• Provide better examples of summary style sheet usage and definition.
• Leverage a broader tagset of functionality.

What’s New
Following are the business object types for which the summary style sheets are
updated:
ChangeNoticeRevision
ChangeRequestRevision
Cm0DevRqstRevision
CommercialPartRevision
DocumentRevision
EDA Revision
EDACompRevision
EDASchem Revision
EPMTask
ItemRevision
ManufacturerPart
ManufacturerPart Revision
ProblemReportRevision
Requirement Revision
Vendor
VendorRevision
For a complete list of the new and old summary style sheet file names, see the Client
Customization Programmer’s Guide.
Note The style sheets that are actually updated at your site depend on your
current database and environment. If this is a new installation, all style
sheets for the listed business objects are updated. However, if this is an
upgraded environment, the registration is updated only for those style
sheets that have no previous registration; the registration for existing style
sheets is not overridden.
The previous versions of the summary style sheets remain in the system so that you
can still use them if you want. To return to the previous version of the style sheet,
change the registration of the business object type to point to the older style sheet
using the <type-name>.SUMMARYRENDERING=<dataset-name(dataset-uid)>
and <dataset-name(dataset-uid)>.SUMMARY_REGISTEREDTO=<type-name>
preferences.
As an example of the updates, following are the old and new style sheets for the
ItemRevision business object type.

ItemRevision style sheet display ItemRevision style sheet display

in the rich client in the rich client
before update (Teamcenter 9.1) after update (Teamcenter 10)
ItemRevision style sheet display ItemRevision style sheet display

in the thin client in the thin client
before update (Teamcenter 9.1) after update (Teamcenter 10)
New Save As wizard in the thin client

The Save As functionality is enhanced in the thin client:
• A new Save As wizard in the thin client provides more capabilities than the
previous wizard and more closely matches the functionality in the rich client.

What’s New
For example, you can define the copy options on attached objects. To display the
new wizard, select an item or item revision object and choose Edit®Save As.
New Save As wizard user interface

The previous version of the wizard is retained; to display the previous version,
choose Edit®Save As (Legacy).
• You can define the properties displayed in the Save As wizard. To define them,
use the SaveAsInput operation on the Operation Descriptor tab in the Business
Modeler IDE.
SaveAsInput operation
• The deep copy rules now allow you to copy any object and to configure deep copy
rules on any persistent business object. Previously, deep copy rules were allowed
only on the ItemRevision business object and its children. Also, deep copy rules
can now be configured on reference properties in addition to relation properties.
To configure, use the Deep Copy Rules tab in the Business Modeler IDE.
For more information, see the Business Modeler IDE Guide and the Thin Client
Interface Guide.

Changes to the display of lists of values (LOVs)

Lists of values (LOVs) are lists in property boxes in the user interface. In the
end-user client applications, the format of the LOV box is changed. It now appears
as a table rather than a simple list (except for hierarchical and range LOVs).
This allows for the display of columns that show the value’s description and other
properties.
Old list of values display New list of values display
Note To allow the description to be displayed for a particular list of values,

use the List of Values preference in the rich client (accessible from the
Edit®Options menu) or the Shown LOV descriptions preference in the thin
client (accessible from the Edit®Options®Advanced menu).
The new list of values table format allows you to:

• Sort the values in the columns.
• Scroll the list of values using a scroll bar.
• Resize the box containing the list of values.
• Type in the LOV box to narrow the choices when there are many values to choose
from. You can even use an asterisk (*) for wildcard searching.
Note If you type text when looking for a value in the format of an integer,
double, or date, you must type the exact value.
Narrowing the LOV choices

What’s New
In addition to displaying lists of values in tables, the end user interface now makes
presentation more intuitive for interdependent LOVs, cascading (hierarchical) LOVs,
and range LOVs:
• Interdependent LOVs
With this type of LOV, what you enter for the first LOV determines the available
choices for the second LOV. Interdependent LOVs formerly displayed values in a
simple list. Now the values are shown in a table format.
Old interdependent LOV New interdependent LOV
You can now change interdependent LOV values on the Details tab of the rich
client. (You cannot do this in the thin client.)
Changing an interdependent list of values on the rich client Details tab

• Cascading LOVs
Cascading LOVs formerly displayed values in a tree format. Now the values
are shown in a table format.
Old cascading LOV New cascading LOV
• Range LOVs
Range LOVs formerly showed only the valid range format. Now the input is
validated when you enter the value in the box and press a tab key or click
anywhere on the form. If you enter a value outside the range, the background
color of the text box changes to red.
Old range LOV New range LOV
You can also now change range LOV values in the Details tab of the rich client.
(You cannot do this in the thin client.)
Changing a range list of values on the rich client Details tab

What’s New
For more information about using preferences to configure the display of lists of
values, see the Rich Client Interface Guide and the Thin Client Interface Guide. For
more information about the widgets used for the new list of values layout, see the
Client Customization Programmer’s Guide
HTML style sheet in Client for Office

As a result of a new HTML style sheet, users of Client for Office have a fully
functional properties dialog box that allows them to edit the properties of Teamcenter
objects, whereas previously, users could only view the properties. Following is an
example of the new HTML user interface in Client for Office.

HTML style sheet rendering in Client for Office

Perform the following steps to edit the properties for a Teamcenter object in Client
for Office:
1. Click the Teamcenter tab.
2. Click the Navigate button and choose Browse or Folder View.
3. Select a Teamcenter object in the left-hand navigation pane, such as an item

revision.
4. Right-click the Teamcenter object and choose Properties.

The HTML-rendered dialog box is displayed.
5. Click the Properties link on the Overview tab.
6. Click the Checkout button.
7. Edit the properties.

What’s New
Managing changes and workflows
Workflow Condition task branches based on subprocess results

The workflow Condition task now can branch based on the results of the task’s
subprocesses. If there are multiple subprocesses, a query executes on the associated
subprocesses, and the results are used to branch accordingly. The query is typically
configured to look at the root task’s result attribute for all the subprocesses. If there
is only one subprocess and it is configured to set the result on the Condition task,
no query is needed, and the workflow follows the branch based on the result. The
existing EPM-set-task-result-to-property handler now allows the setting of the
result attribute on the root task and the dependent parent Condition task. The
EPM-set-condition handler can now set the results based on a query of a task’s
subprocesses, as well as the task or its targets.
Issue Manager interface enhancements

The Issue Manager user interface for browsing issues is enhanced. The issues
appear in an Issue List Details view in both the rich client and thin client. The Issue
List Details view supports standard issue reports, as well as Teamcenter visual
issues and penetration requests. The new interface better aligns the Teamcenter
view with the Teamcenter community collaboration view and provides different
means for you to browse and view issues to better support the design review process.
The following shows the Issue List Details view in the rich client.
Issue Manager also provides support for issues created for items with a multifield key
and for creating issues in the context of a part. In addition, it provides a new Issue
Manager thin client interface for browsing, viewing, creating, and reviewing issues.
For more information, see the Issue Manager Guide and the Thin Client Interface
Guide.
Making bulk updates of assemblies in a structure

Privileged users can make bulk updates of multiple assemblies with a single action,
for example, identifying and automatically replacing every occurrence of an impacted
part with the solution item. The update may include multiple types of operations
including replace, remove, add, and manual update (revise parts that are released)
when making design changes. This automates a manual, time-intensive process that
would otherwise take users many hours to complete. Typically, you replace a part
with a preferred substitute or nonpreferred substitute, although it is not mandatory
for the replacing part to be a designated substitute.

The assemblies can be updated by selecting the item revision and using one of two
processes:
• A single phase manually initiated process in My Teamcenter
• A two-phase change request (CR) and change notice (CN) change process in
Change Manager. The change processes allow the user to execute, track, and
manage all impacted structures when performing a mass replace (add or remove)
action. The update is stored in a change item.
As part of the two-phase process, you can also add, modify, and remove annotations
associated with the change. You cannot work with annotations if you use the
single-phase process.
A new Mass Update wizard and menu commands in the rich client and thin client
user interfaces allows you to initiate bulk updates in either application.
To configure this enhancement, you must set the following preference:
• MassUpdateDefaultRevRule
Defines the revision rule that is used to perform a where used search on the
target part of a mass update.
For more information, see the My Teamcenter Guide and the Change Manager Guide.
Tracking workflow and schedule progress in the Process History view

In the Process History view, you can review the progress of a workflow or schedule
and do the following:
• Determine the progress of an object in a schedule or workflow and who has

responsibility for the object.
• Review comments by other workflow participants.
• Verify that the appropriate participants completed the required reviews.
• Debug a workflow that proceeded down an unexpected path.
• Identify workflows that require attention to continue processing.
• Review user activity to verify the appropriate users signed off.
The Process History view displays the Workflow or Schedule Manager process of
the business object selected in the Home, My Worklist, or Search Results view in
My Teamcenter. If there is no audit data for the business object, the view displays a
No process history data available for selected object. message. If the object you
select has passed through more than one workflow process, you can choose which
process to display from the list to the right of the tab.
For more information, see Getting Started with Workflow.

What’s New
Workflow handler, argument, argument values, and keyword name

changes
To systemize the naming of handlers, arguments, and keywords, some have been
changed to a standardized format. The migrate_wf_handlers utility automatically
converts those in use to the new names.
The handler name changes are:
Handler name prior to Teamcenter 10.1 New handler name beginning in Teamcenter 10.1
add-status EPM-set-status
adhoc-signoffs EPM-adhoc-signoffs
approve-service-structure SERVICEPROCESSING-approve-service-structure
ASB-attach-physical-components ASBUILT-attach-physical-components
ASM-attach-physical-components ASMAINTAINED-attach-physical-components
assert-signoffs-target-read-access EPM-assert-signoffs-target-read-access
auto-assign EPM-auto-assign
auto-assign-rest EPM-auto-assign-rest
auto-relocate-file SMP-auto-relocate-file
change-all-started-to-pending EPM-change-all-started-to-pending
check-condition EPM-check-condition
check-responsible-party EPM-check-responsible-party
check-signoff EPM-check-signoff
CR-assert-targets-checked-in EPM-assert-targets-checked-in
CR-assign-team-selector EPM-assign-team-selector
CR-change-group-owner EPM-change-group-owner
CR-change-target-group EPM-change-target-group
CR-change-target-group-owner EPM-change-target-group-owner
CR-check-item-status EPM-check-item-status
create-status EPM-create-status
CR-fill-in-reviewers EPM-fill-in-reviewers
CR-notify EPM-notify-report
debug EPM-debug
debug-rule EPM-debug-rule
demote EPM-demote
demote-on-reject EPM-demote-on-reject
disallow-adding-targets EPM-disallow-adding-targets
disallow-removing-targets EPM-disallow-removing-targets
EPM-add-released-parts-queue RDV-add-released-parts-queue
EPM-assert-target-classified ICS-assert-target-classified
EPM-attach-assembly-components PS-attach-assembly-components
EPM-attach-mgcitemrev-targets MGC-attach-mgcitemrev-targets
EPM-attach-targets-AH ERP-attach-related-targets-AH
EPM-check-assembly-status-progression PS-check-assembly-status-progression

EPM-check-occ-notes PS-check-occ-notes
EPM-check-validation-result VAL-check-validation-result
EPM-check-validation-result-with-rules VAL-check-validation-result-with-rules
EPM-delete-ugcgm-markup RDV-delete-ugcgm-markup
EPM-export-AI-AH AI-export-AH
EPM-export-to-plmxmlfile PIE-export-to-plmxmlfile
EPM-generate-image RDV-generate-image
EPM-generate-ugcgm-drawing RDV-generate-ugcgm-drawing
EPM-make-mature-design-primary PS-make-mature-design-primary
EPM-mark-archive AR-mark-archive
EPM-perform-offline-export BC-perform-export
EPM-publish-target-objects PUBR-publish-target-objects
EPM-send-target-objects OBJIO-send-target-objects
EPM-set-condition-by-check-validation-result VAL-set-condition-by-check-validation-result
EPM-set-form-value-AH ERP-set-form-value-AH
EPM-tessellation-handler RDV-tessellation-handler
EPM-unpublish-target-objects PUBR-unpublish-target-objects
execute-follow-up EPM-execute-follow-up
inherit EPM-inherit
invoke-system-action EPM-invoke-system-action
invoke-system-rule EPM-invoke-system-rule
late-notification EPM-late-notification
notify EPM-notify
notify-signoffs EPM-notify-signoffs
release-asbuilt-structure ASBUILT-release-asbuilt-structure
release-asmaintained-structure ASMAINTAINED-release-asmaintained-structure
require-authentication EPM-require-authentication
schmgt-approve-timesheetentries SCHMGT-approve-timesheetentries
schmgt-revise-timesheetentries SCHMGT-revise-timesheetentries
schmgt-reject-timesheetentries SCHMGT-reject-timesheetentries
set-condition EPM-set-condition
set-duration EPM-set-duration
set-parent-result EPM-set-parent-result
set-status EPM-set-status
suspend-on-reject EPM-suspend-on-reject
system EPM-system
trigger-action EPM-trigger-action
trigger-action-on-related-process-task EPM-trigger-action-on-related-process-task
validate-for-checkedout-asmaintained ASMAINTAINED-validate-for-checkedout-
-physicalpartrevision physicalpartrevision
validate-for-checkedout-physicalpartrevision ASBUILT-validate-for-checkedout-physicalpartrevision
validate-for-class MROCORE-validate-for-class

What’s New
validate-for-latest-asmphysicalpartrevision ASMAINTAINED-validate-for-latest-asmphysicalpartrevision
validate-for-physicalpartrevision ASBUILT-validate-for-physicalpartrevision
validate-for-unserviceable ASMAINTAINED-validate-for-unserviceable-physicalpartrevision
-physicalpartrevision
validate-missing-asmaintained-structure ASMAINTAINED-validate-missing-asmaintained-structure
validate-missing-structure ASBUILT-validate-missing-structure
The argument changes are:

New argument name
Handler name beginning in Argument name prior to Teamcenter beginning in Teamcenter
Teamcenter 10.1 10.1 10.1
EPM-adhoc-signoffs AUTO_COMPLETE -auto_complete

-auto_incomplete Argument removed.
-conventional-execution -ce
EPM-assign-team-selector -owner -assignee=$PROCESS_OWNER

-person -assignee=person:person-name
-resourcepool -assignee=resourcepool:pool-name
-user -assignee=user:user-name
EPM-attach-related-objects -status_allow -allowed_status
-status_disallow -disallowed_status
-att_type -attachment
-exclude_type -exclude_related_types
-type -include_related_types
EPM-auto-assign resource pool Argument removed.
-owner -assignee=$PROCESS_OWNER
-person -assignee=person:person-name
-resourcepool -assignee=resourcepool:pool-name
-user -assignee=user:user-name
subtasks -subtasks
EPM-auto-assign-rest list-of-users (legacy syntax) -assignee
EPM-auto-check-in-out -include_type -include_related_type
-user -assignee
The values can be

$REVIEWERS or
$RESPONSIBLE_PARTY.
EPM-change-ownership -owner -assignee
The values can be

$REVIEWERS or
$RESPONSIBLE_PARTY.
EPM-check-action-performer-role user-values -responsible
EPM-check-condition task-name -source_task
None. -decision

New argument name

EPM-check-item-status -status -allowed_status

-type -include_related_type
EPM-check-object-properties -att_type -attachment
The values are now

lowercase.
-props -property
-type -include_type
-values -value
EPM-check-related-objects -status -allowed_status
-target_type -include_type
EPM-check-signoff -QUORUM -quorum
EPM-check-signoff-comments -decision -decision
The values are now

lowercase.
EPM-check-target-attachments -att_type -include_related_type
-attachtype -include_related_type
-status -allowed_status
-target -include_type
-type -include_type
EPM-check-target-object -status_allow -allowed_status
-status_disallow -disallowed_status
-status -disallowed_status
EPM-create-form -location -target_task
-default -property and -value
EPM-create-relation -primary -primary_attachment
-secondary -secondary_attachment
EPM-create-status status -status
EPM-create-sub-process -exclude_related_types -exclude_related_type
-exclude_types -exclude_type
-include_related_types -include_related_type
-include_types -include_type
-process_desc -description
EPM-debug comment -comment
EPM-debug-rule comment -comment
EPM-demote -level -target_task
EPM-display-form -form -source_task
EPM-execute-follow-up argument -command
EPM-fill-in-reviewers -level (legacy syntax) -target_task
-review_task_name -target_task
-reviewer -assignee

What’s New
New argument name

EPM-hold {true | false } Argument removed.

EPM-inherit PREVIOUS | CALLER | ROOT -task
The values are now

$PREVIOUS | $CALLER
| $ROOT.
TARGET | REFERENCE | SIGNOFFS -attachment
The values are now

lowercase. Multiple values
are separated from commas.
EPM-invoke-system-action -signoff -comment
-system -command
EPM-invoke-system-rule debug -debug
-signoff -comment
-system -command
EPM-late-notification user -recipient
EPM-notify -comments -comment
-attachment -attachment
The values are now

lowercase and the $ has
been removed.
EPM-notify-report -comments -comment
EPM-notify-signoffs -comments -comment
log -log
-attachment -attachment
The values are now

lowercase and the $ has
been removed.
EPM-set-condition $Query -query
All | Any | None -check_targets
The values are now

lowercase.
-query_type -query_type
The values are now

lowercase and sub-process
is now sub_process.
EPM-set-duration day -day
hour -hour
minute -minute
week -week
year -year
EPM-set-parent-result true | false -value

EPM-set-property -exclude_types -exclude_type

New argument name

-from_att_type -from_attach
-include_types -include_type
-props -property
-to_att_type -to_attach
-values -value
EPM-set-rule-based-protection named-ACL -acl

EPM-set-status APPEND | REPLACE | DELETE | -action
RENAME
The values are now
lowercase.
-f -status
RETAIN_RELEASE_DATE -retain_release_date
SET_EFFECTIVITY -set_effectivity
-t -new_status
EPM-set-task-result-to-property -target_type -include_type
-task_name -source_task
-target -target_task
EPM-system argument -command
EPM-trigger-action action -action
comment -comment
EPM-trigger-action-on-related -process_template -template
-process-task
EPM-validate-target-objects -allowed_type -exclude_type

-disallowed_type -include_type
PS-attach-assembly-components -exclude_types -exclude_related_type
-include_types -include_related_type
The keyword changes are:
Keyword name prior to New keyword name beginning in

Teamcenter 10.1 Teamcenter 10.1
$PROCESSGROUP $PROCESS_GROUP
$PROCESSOWNER $PROCESS_OWNER
$ROLEINGROUP $ROLE_IN_GROUP
For more information, see the note that
follows.
$ROOTTask $ROOT

What’s New
Keyword name prior to New keyword name beginning in

Teamcenter 10.1 Teamcenter 10.1
ROOT $ROOT
$TARGETGROUP $TARGET_GROUP
$TARGETOWNER $TARGET_OWNER
Note For the EPM-auto-assign , EPM-auto-assign-rest, and

EPM-fill-in-reviewers handlers, use resourcepool:$GROUP::$ROLE
instead of $ROLE_IN_GROUP.
For the EPM-notify and EPM-notify-report handlers, use
allmembers:$GROUP::$ROLE instead of $ROLE_IN_GROUP.
For more information, see the Workflow Designer Guide and the Utilities Reference.
Workflow can run tasks in the background

You can configure Workflow to run tasks in one of the following ways:
• All tasks in the background (asynchronously)
• All tasks in the foreground (synchronously)
• According to the task’s background processing setting

The Workflow Designer user can designate the root task or its children of a
particular workflow process for background execution in the task’s attributes.
When a task is marked to be processed in the background, all the task actions and
the accompanying task handlers are executed in the background (with the exception
of the Perform and Assign actions because they are intended for interactive
processing).
The EPM_task_execution_mode preference determines which of the three ways
tasks are executed.
For more information, see the Workflow Designer Guide and the Preferences and
Environment Variables Reference.
Workflow propagates parent process states to child subprocesses

for delete and abort actions
The following actions on the parent process are now be propagated to the child
subprocess:
• Delete
• Abort
This takes place whether the subprocess is an independent subprocess or has

interprocess task dependencies defined between the parent and child processes, and
this is the last parent process.
For more information, see the Workflow Viewer Guide.

Change Viewer-specific templates and handlers are removed from

Workflow
The following Workflow process and task templates specific to Change Viewer are
removed with the obsoleting of that application:
• Checklist task template
• Impact Analysis task template
• Prepare ECO task template
• CMII Change Notice process template
• CMII Change Request process template
• CMII WA process template
In addition, the Sync task template is removed.

Also, Change Viewer-specific handlers are also obsolete.
For more information, see the Teamcenter 10.1 Release Bulletin.
Claiming tasks from a resource pool or other users

If a task is assigned to a resource pool or another user, individual users can claim
the task, which moves it to their personal worklist in the rich client and thin client.
For more information, see the My Teamcenter Guide, Thin Client Interface Guide,
Workflow Viewer Guide, or Getting Started with Workflow.
Promote Review and Route tasks along either the Approved or

Rejected path
Users are given an option when promoting a Review or Route task whether to follow
the Approved path or the Rejected path. The workflow proceeds through the
process along that path.
For more information, see the My Teamcenter Guide, Thin Client Interface Guide,
Workflow Viewer Guide, or Getting Started with Workflow.
Customize the perform signoff user interface

Workflow provides a mechanism to use your own dialog boxes for performing
signoffs. Customizations may include:
• Additional input boxes or action buttons.
• Additional validation of arguments.
• Custom layout of user interface elements within the dialog box.
For more information, see the Client Customization Programmer’s Guide.

What’s New
Filter Workflow processes more extensively

You can provide your own filter criteria for workflow process templates that override
the default behavior, such as:
• User
• Role
• Release status
Expanded audit information is available for Workflow users

Teamcenter now provides the Process History view, where you can review the
progress of a workflow or schedule and do the following:
• Determine the progress of an object in a schedule or workflow and who has
responsibility for the object.
• Review comments by other workflow participants.
• Verify that the appropriate participants completed the required reviews.
• Debug a workflow that proceeded down an unexpected path.
• Identify workflows that require attention to continue processing.
• Review user activity to verify the appropriate users signed off.
With this new functionality, legacy audit information is accessible only from a button
in the Audit Logs tab in the Summary view when a legacy audit file is present.
For more information, see the My Teamcenter Guide or Getting Started with
Workflow.
Add change folders in a schedule task to the Target and Reference

folders of a workflow task
You can add a schedule task and its change folders to the Target and Reference
folders of a workflow task by using the EPM-attach-related-objects workflow
handler.

Change Manager schedule and general enhancements

Change Manager now provides an interface in which you can selectively propagate
the problem, impacted, solution, and reference items related to a change object
to the related plan items (schedules) leaf-level schedule tasks. You can also add
change items to the schedule task change folders using the new Change Details view
in the Schedule Manager application. The Change Details view also allows the
viewing of the authorized change and the state of the workflow for a schedule task
from within the Change Manager or My Worklist applications. A new menu feature
also allows you to open the Workflow Viewer in either the Change Manager or My
Worklist applications.
In addition, the revise impacted items feature is enhanced to allow the revision of
multiple impacted items instead of only one at a time.
For more information, see the Change Manager Guide.
Change Manager also:
• Adds new Change Manager conditions that provide administrators with a way to
control who can propagate change items to schedules. The new conditions begin
with isCm0 and are named exactly like the old conditions except for the 0 in
the name. They are replacements for the old conditions and refer to the old
conditions in the expression.
For more information, see Business Modeler IDE Guide.
• Revises the following business object constants in the business object constants
reference to allow them to be available on the ScheduleTask business object.
By default, CMHasImpactedItemCreCondition for the ScheduleTask type
is set to Cm0isCMHasProblemItemCreatableForTask.
o CMHasImpactedItemCreCondition
o CMHasProblemItemCreCondition
o CMHasSolutionItemCreCondition
o CMReferencesCreCondition
• By default, Change Manager no longer checks that a user has dba privileges
when creating a change notice, change request, or deviation request. Therefore,
the following conditions are changed so they no longer check for dba:
o isChangeRequestCreatable
o isChangeNoticeCreatable
o isCM0DevRequestCreatable

What’s New
• Adds a new workflow handler (CSI-propagate-folder-contents) to propagate

objects related to the change with the problem, impacted, reference and, if
applicable, solution relations to all the related plan items (schedules) leaf-level
schedule tasks change folders.
• Adds a new preference, ScheduleTask.CHGDETAILRENDERING, which

provides for the registration of the change details style sheet for schedule task
objects.
• Removes Classic Change Viewer.

For more information, see the Teamcenter 10.1 Release Bulletin.

Getting started with document management
Document management enhancements

Document management is enhanced in several major areas:
• New capability to digitally sign PDF files
Note Digital signing is supported only for PDF datasets created in Teamcenter
10.1 or later.
• New capability to launch applications for datasets in Teamcenter Client for

Microsoft Office
• Enhanced thin client checkout and checkin files transfer
• For create actions, new Attach Files and Submit to Workflow functionality in
the New Business Object wizard in the thin client
• New style sheets for create dialog boxes and summary display for Document
objects in the rich client and the thin client
For more information about document management functionality, see Getting

Started with Document Management.
Digitally signing PDF files

You can digitally sign a PDF file stored as a dataset named reference file with:
• Adobe Acrobat
• Adobe Reader
Note The PDF file must have Enable Usage Rights for Digitally Sign enabled.
Use Adobe Acrobat or Adobe LiveCycle Reader Extensions to enable
usage rights for PDF files.
Digital signing is supported only for PDF datasets created in Teamcenter
10.1 or later.
The Digital Sign Dataset ACL rule grants the owning user and owning group
digital signing privileges for the dataset object.
• World access users do not have digitally sign privileges.
Note The Digital Sign Dataset ACL rule may not be present in an upgraded
system. To use the digital signature capability, this rule must be created.
• Sign a PDF file by choosing the rich client File®Sign command or the thin client
Tools®Sign command.
o The signed PDF file updates the PDF file stored in Teamcenter.
o To cancel a sign action, choose the Cancel Signing menu command.

What’s New
For more information about digital signing, see Getting Started with Document
Management.
Launch applications for datasets in Teamcenter Client for Microsoft Office

Teamcenter Client for Microsoft Office users can launch Adobe Acrobat/Reader
and other Office applications for edit, view and markup, and sign. From Client for
Office, users can now digitally sign PDF datasets that uniquely identify the user
that signs a document.
New site preferences control which applications are available for launch, view and
markup, and sign.
1. In the Client for Office Navigation task pane, select an Office or PDF dataset.
2. Right-click to display the context menu.
3. Choose one of the following:

• Open File (for read-only access)
• Open and Check-Out File
• View/Markup
• Sign (for PDF datasets only in Microsoft Office)
Additional functionality is provided when you save a dataset in Teamcenter Client

for Microsoft Office.
In the Save As dialog box, you can now perform the following actions:
• Create new folders
• Create new items
• Revise items
For more information about launching applications, see Getting Started with
Document Management.
Create-with-attached-files and submit-to-workflow functionality in the thin client

Two user interface dialog boxes are added to the New Business Object wizard to
support:
• Attaching files to a new object.
• Submitting a new object to workflow.
The new dialog boxes are enabled only for ItemRevision objects under IRDC control
and objects under IRDC control descended from ItemRevision.
Note These dialog boxes are displayed after you click Finish in the New Business
Object wizard.
In the thin client, choose New®Other or New®Item to display the New
Business Object wizard.

• In the Attach Files dialog box, you can attach the local files based on IRDC
source dataset definition.
o The system ignores the IRDC template and associates the local files to the
ItemRevision object using the relation defined in the IRDC source dataset
definition.
o The default relation is Tc_Attaches.
• In the Submit to Workflow dialog box, you can submit the newly created item
revision to an appropriate workflow process.
For more information about attaching files and submitting objects to a workflow, see
Getting Started with Document Management.
Checkout/checkin files transfer in the thin client

You can download source files when checking out an item revision.
• The download dialog box lets you choose the directory for each source file being
downloaded.
• You can open the file in an application. The system remembers the download
path.
When you check out an item revision under IRDC control and there are source files
associated with the item revision, a download dialog box lets you choose the directory
for each source file to download and choose whether to open the file in an application.
When you check in the item revision, the checkin file transfer functionality is used.
• During the subsequent checkin operation, the system finds and uploads the
previously checked out and downloaded dataset.
• Based on IRDC settings, the directory is searched for local derived dataset files
to be uploaded.
For more information about file transfer during checkin and checkout, see Getting
Started with Document Management.
Create and summary style sheets for Document objects

Create style sheets provided for Document objects customize the New Business
Object wizard in the rich client and thin client to streamline the document creation
process.
Display the New Business Object wizard in your client. Then, to access the
customized wizard, select Document as the object type to create.
• In the thin client, choose New®Other or New®Item to display the New Business
Object wizard.
• In the rich client, choose File®New®Other or File®New®Item to display the

New Business Object wizard.
• In Client for Office, click the New button on the command ribbon to display the
New Business Object wizard.

What’s New
In the rich client and the thin client, the Summary pane is displayed on the right
side of the window when a Document or Document Revision object is selected
in the navigation pane.
Summary style sheets customize the Summary pane in the rich client and the thin
client.
• New summary style sheets are provided for Document and Document
Revision objects to customize the layout for the specific needs of those objects.
• Along with layout changes, a View/Markup action is added to Actions list on the
Summary pane.
For more information about style sheets for document objects, see Getting Started
with Document Management.
Managing content, reports, and schedules
Content Management enhancements

The following enhancements to Content Management are included in Teamcenter
10.1:
• You can capture 2D images of your 3D models in Teamcenter lifecycle
visualization and save them into Teamcenter for use with Content Management.
• Content Management preferences are viewable as rich client options.
• You can configure UI options so that imported documents and graphics are placed
in the Newstuff or selected folder. You can set the PLMXML_put_objects_in
newstuff preference so that imported administration data is placed in the
Newstuff folder.
• The last path used persists the Save As dialog box when you export a topic or
publication to a .zip file.
• The state of the Publication Structure view persists between login sessions.
• Content Management saved searches have user friendly names.
• Creating an S1000D object is prohibited when the entered attributes are not
valid for the schema.
• A new icon is added for reference topic types.
• A progress bar appears during the import of documents.
• Translations can be partially received.
• Child topics can be selectively copied or marked as a reference during a save as

or duplicate operation.
• Support for DITA Open Toolkit is upgraded to version 1.5.3.

• Upgraded support for DITA 1.1 Content Management includes:

o Relationship tables
o Content references
o Link management, which enables the validation of links so that if a

referenced element is removed from a topic, an error message appears when
the author tries to save the topic.
o Bookmaps
• Upgraded support for DITA 1.2 Content Management includes:

o Key and key references
o New elements:
<text>
<bodydiv>
<sectiondiv>
<keydef>
<mapref>
<topicset>
<topicsetref>
<anchor>
<anchorref>
Note The contents of anchorref elements are not included in documents
published with DITA Open Toolkit 1.5.3 publishing tools.
o Refinement to maps, which includes a new topicref attribute,

processing-role, stored on the Ctm0RefTopicRefR relation attribute
ctm0RefXMLCont.
o Refinements to content references to point to a range of elements using the

conref and conrefend attributes together.
• Upgraded support for S1000D Content Management includes:

o S1000D version 4.0.1
o Support for SCORM package module
For more information, see the Content Management Guide.
Schedule Manager enhancements

The following enhancements to Schedule Manager are included:
• Tasks and schedules can now be aborted, with notifications sent to assigned
users and integration with associated workflows
• Schedule Manager events are auditable.
• You can restrict the creation, updating, and deletion of tasks and schedules, as
well as the rescheduling of tasks using new preferences.

What’s New
• Tasks can be assigned to resource pools, as well as groups and roles; this feature
is integrated with Workflow.
• Multifield keys are supported.
• You can link planned schedule dates and actual schedule dates.
• You can navigate between the Manufacturing Process Planner application and
schedule tasks, creating a relationship between the manufacturing process
revision and the schedule task.
For more information, see the Schedule Manager Guide.
Systems Engineering
General Relationship Management (GRM) relations in Visio diagrams
General Relationship Management (GRM) relations among Teamcenter objects
appear as connector shapes in Visio diagrams. For each diagram template, a relation
rule lists the GRM relations that can be represented in diagrams based on the
template.
Those relations are available in the template’s diagrams when you do the following:
• Create shapes for the relations in a Visio stencil that is associated with the
template.
• Map the relation shapes from the stencil to the corresponding relations in
Teamcenter.
Then, you can use the stencil’s relation shapes to create those relations between
objects in Systems Engineering:
• From the stencil, drop a relation shape on the diagram page.
• Glue the relation shape ends to the connection points on the shapes that
represent the related objects.
For more information, see the Systems Engineering Guide.
Domain assignment for child diagrams

A Teamcenter application domain defines a context for accomplishing particular
business tasks. Each Visio diagram is assigned to an application domain.
Domain-specific context information is stored with the diagram object and governs
the diagram content.
When you create a child diagram, you can assign it to one of the following application
domains:
• The parent diagram’s domain
• The FunctionalModeling domain
• The LogicalModeling domain

• A custom domain created in the Business Modeler IDE
For more information, see the Systems Engineering Guide and the Business Modeler
IDE Guide.
Multi-Site Collaboration support for Visio diagrams

If you use Multi-Site Collaboration to share Systems Engineering data, you can
export the following to another Teamcenter site:
• All Visio diagrams for a structure, including diagrams that are attached to the
root object and to its subordinate elements
• The latest revisions of individual Visio diagram objects, including their owning
objects
In each type of export operation, you can specify one of the following site ownership
options for the exported diagrams:
• Transfer ownership to the target site.
The exported diagrams become the master objects, with the full Systems
Engineering diagramming functionality.
For more information about editing diagrams, see the Systems Engineering
Guide.
• Retain ownership on the source site.

On the target site, the exported diagrams are read-only replicas of the master
objects. You can open replica diagrams, but you cannot edit them.
Note If a replica diagram’s owning structure is also a replica, you can make
changes in the diagram that do not affect the structure. For example,
you can enter a text description on the diagram page.
Note On the target site, proxy objects called stubs can represent objects whose
complete data is excluded from the export process. A stub is substituted for
a whole object due to certain conditions on the source site, such as object
ownership or user access permission.
You cannot open a stub, because it contains only that data that shows how
the excluded object relates to the exported objects in the same structure.
Multi-Site Collaboration uses the data in tracking revisions to the master
object.
The TC_relation_required_on_export preference controls the related objects that

are exported when you export an object using Multi-Site. Therefore, the required
datasets (image and Visio) and any other required object must be added to the
preference to support this feature.
For more information about Multi-Site preferences, see the Preferences and
For more information about remote import and export options, see the Multi-Site
Collaboration Guide.

What’s New
Traceability across Teamcenter domains

This feature traverses upstream and downstream paths between Teamcenter 4th
Generation Design and Teamcenter Systems Engineering to locate objects that are
related by trace links, such as:
• Subsets in 4th Generation Design.
• Requirements, functional models, logical models, and physical models in Systems

Engineering.
Collaborative designers can trace these relationships to determine how changes to

a given object affect its defining and complying objects. Cross-domain tracing can
fully traverse upstream and downstream paths faster than can Systems Engineering
traceability reports.
For source and target object selection, you can open the following views in Systems
Engineering:
• The Content Explorer view and the 3D Viewer from 4G Designer
• The Requirements, Function, Logical Block, and Product views in Systems

Engineering
You can select the source object in any one of those views. The other open views
highlight the target objects automatically.
Using new preferences and settings in the Options dialog box, you can define:
• The number of levels to trace in the target hierarchies.
By extending the trace to the lowest level, you can view all of the related objects
simultaneously. Otherwise, you can continue the trace by selecting a target
object to highlight its related objects in the other views.
• The direction of the trace.

You can trace upstream, downstream, or in both directions simultaneously.
• The relation types and object types to be traced.

For Teamcenter 10.1, you can define only trace link relation types.
For more information, see the Systems Engineering Guide and the 4th Generation
Design Guide.
Diagram enhancements for functional and logical models

Teamcenter Systems Engineering provides new features for diagrams in Microsoft
Office Visio.
• Create different types of diagrams.
• Create domain-specific diagrams.
• Create diagrams with or without interface shapes.
• Create trace links to occurrences from a diagram.

• Display multiple object properties on a shape.
• Show different shapes based on object properties.
For more information about diagramming architectures with Microsoft Office Visio,
see the Systems Engineering Guide.
Arranging the Traceability view layout

In the Traceability view, you can arrange the Defining Object and Complying Object
panes horizontally or vertically.
• The horizontal layout displays the Defining Object pane on the left and the
Complying Object pane on the right.
• The vertical layout (the default layout) displays the Defining Object pane at the
top and the Complying Object pane at the bottom.
For this
layout Do this
Horizontal Do one of the following:
• Select the Left-Right View option in the Traceability view.
• Use the Options dialog box.

1. To display the dialog box, choose Edit→Options.
2. In the left pane, select the Systems Engineering option.
3. In the right pane, select the Left-Right Trace View check box.
• Set the SE_Trace_Report_Layout preference value to true.

For more information about the SE_Trace_Report_Layout
preference, see the Preferences and Environment Variables
Reference.
Vertical Do one of the following:
• Clear the Left-Right View option in the Traceability view.
• Use the Options dialog box.

1. To display the dialog box, choose Edit→Options.
2. In the left pane, select the Systems Engineering option.
3. In the right pane, clear the Left-Right Trace View check box.
• Set the SE_Trace_Report_Layout preference value to false.

For more information about the SE_Trace_Report_Layout
preference, see the Preferences and Environment Variables
Reference.

What’s New
For more information about the Traceability view, see the Systems Engineering
Guide.
Navigating to an object by its URL

Object URLs can be copied from Systems Engineering and inserted in files from
external applications. For example, you may receive object URLs in an e-mail
message from a subordinate or a colleague. Or, URLs can be inserted in Office
documents that are attached to a message or stored on a shared drive.
You can click a URL to navigate to that object in Systems Engineering. In the related
view, the object’s parent structure expands and the object is highlighted.
You can place a URL in your Windows Clipboard by right-clicking the object and
choosing Copy URL. You can then paste the URL into an external file, for example,
an e-mail message that you send to recipients such as your manager or colleagues.
For more information about capturing and navigating to object URLs, see the
Systems Engineering Guide.
Hierarchical numbering in Relation Browser

Relation Browser displays the Number property value for each structure element.
This value indicates the element’s position in the hierarchy.
For example, a value of 1.1 shows the element’s position as the first object at the
level below the root element.
For more information about expanding a structure in Relation Browser, see the
Attaching custom notes to trace links

Trace link objects can own custom notes as attachments. The notes can be used to
record supplemental information about the trace links, such as issues involving
the downstream or upstream paths, reasons for decisions or actions, and meeting
minutes discussing the trace links.
A trace link’s custom notes can be copied to other trace links. Custom notes can be
removed from trace links.
For more information about creating custom notes on trace links, see the Systems
Engineering Guide.
Comparing requirement content in Microsoft Office Word

The Export to Word: For Compare Content dialog box contains options to determine
the output content by selecting a specification template and an object template. It
also contains an option to generate the output in the static mode.
The comparison document can be saved in Teamcenter. The Word document can be
attached to the source or target object.
Note The AE_dataset_default_keep_limit preference sets the number of dataset
versions that can be saved before older versions are deleted.

For more information about comparing requirement content, see the Systems
Engineering Guide.
Transferring exported object data by e-mail

Data can be exported to Microsoft Office Word or Excel and a new e-mail message
simultaneously. The output can be generated in the static output mode or the live
output mode.
A static file is attached to the e-mail message. For a live file, the file’s URL is
inserted in the e-mail message body.
The exported content can be determined by selecting a specification template and
an object template. The message can be sent to Teamcenter users and to external
e-mail addresses.
For more information about exporting data to Teamcenter e-mail, see the Systems
Engineering Guide.
Copying a snapshot of exported data to a Microsoft Office Word

dataset
When you export data to Microsoft Office Word in the Static Snapshot output mode,
you can copy the snapshot to a Word dataset in addition to the output document.
By selecting the Copy Snapshot to Dataset option, you attach the snapshot dataset
to the parent object selected for export.
The snapshot dataset’s URL is placed on the Teamcenter clipboard. To open the
dataset in Word, you can paste the URL into your browser’s address field.
The dataset is read-only. You cannot edit the snapshot and save the changes in
Teamcenter.
Note • The QRY_dataset_display_option preference determines whether the
latest version or all versions of a dataset are displayed when query
results are returned.
• The AE_dataset_default_keep_limit preference sets the number of

dataset versions that can be saved before older versions are deleted.
For more information about the Static Snapshot output mode for Word, see the
Design requirements and validation requirements for NX parts

Subtypes for NX part design requirements and validation requirements are available
for selection in the Systems Engineering New Requirement wizard and Quick
Create bar.
For more information about designing and validating NX parts with requirements,
see the Systems Engineering Guide.

What’s New
Multifield keys for Systems Engineering object definitions

Systems Engineering objects can be defined with multifield keys in Business Modeler
IDE. A multifield key is a unique combination of one or more properties. Once this
combination is defined, Teamcenter does not allow that key to be used in defining
another business object.
Caution Data that is imported from Microsoft Office Excel must contain only
properties that participate in multifield keys.
For more information about configuring business object identifiers with multifield
keys, see the Business Modeler IDE Guide.

MATLAB integration enhancements

The Teamcenter MATLAB integration supports the following new features:
From MATLAB Simulink
• Capability to independently manage model reference blocks as separate models

that can be extended to subsystem blocks.
• Inserting managed subsystems in models
• Canceling checkout
• Creating a copy of a model using Save As
• Creating and deleting trace links from Teamcenter objects to model blocks
and subsystems
• Saving subsystems
• Inserting subsystems as blocks, reference, or as model reference
• Automatically assigning IDs and revision IDs when you save the model
• Automatically assigning a revision ID when you revise the model
• Checking out submodels when checking out a parent model
• Configuring type mapping for explicit and implicit model save
• Configuring the block types to be saved in Teamcenter based on user choice
From Teamcenter rich client
• Opening models in MATLAB
• Revising models
• PLM XML import and export
Others
• Over-the-Web installation
For more information, see the Behavior Modeling Tool Integration Guide.
View and edit the validation requirement or design requirement

You can view and edit the validation requirement or design requirement in a
Requirement Specification view with the addition of a new run-time property.
For more information, see the Systems Engineering Guide.

What’s New
Sharing data
Briefcase file viewer and editor

Briefcase Browser is a new stand-alone application that allows suppliers that do not
have Teamcenter installed, know as an unmanaged site, to work with briefcase files
from sites that manage their data in Teamcenter, know as managed sites. Typically,
an OEM site is a managed site that may work with some unmanaged supplier
sites. An unmanaged site must have NX installed to edit or create assemblies or
components in Briefcase Browser.
The unmanaged supplier site users can:
• Read and display briefcase files.
• Open JT files and display them in JT viewers.
• Open CAD parts or assemblies in NX for modification.
• Open NX native CAD parts or assemblies to create new briefcase files (CAD with
the required TC XML data).
• Distinguish objects based on site ownership and allow user modifications

appropriately
Briefcase Browser has the following restrictions:

• Limited to NX CAD data in initial release .
• JT files launch requires JT2Go or Teamcenter Lifecycle Viewer (no other viewers
supported).
• JT is created for only the top assembly transferred from the managed site.
• Absolute positioning is not supported.
• Substitutes, alternatives, and delta briefcase files are not supported but do not
generate errors (can be viewed) .
• Briefcase files must be exported from Teamcenter to a site defined as unmanaged

in Teamcenter.
• All editing must be performed in NX.
• Write is supported for UGMASTER and UGPART (master model drawings)

dataset types.
• Display feature supports only datasets attached to item revisions.
For more information, see the Data Exchange Guide.
Briefcase file export to suppliers without Teamcenter

Briefcase Browser is a new stand-alone application that allows suppliers that do not
have Teamcenter installed, identified as an unmanaged site, to work with briefcase

files from sites that manage their data in Teamcenter, known as managed sites. You
define sites as unmanaged in the Organization application. This allows you to export
data to and import data from unmanaged supplier sites that have only Briefcase
Browser and NX.
For more information about Briefcase Browser, see Briefcase file viewer and editor.
The export functions in My Teamcenter and Structure Manager provide options
specific to unmanaged sites or managed sites depending on the site’s definition,
such as the contents of the Option Set and Revision Rule lists, Dataset Options,
and Session Options. When you export a briefcase file for an unmanaged site,
the Teamcenter converts the CAD data to the format that the CAD system (NX)
can operate on as native data without Teamcenter support. This type of briefcase
file may be limited to only JT data if the ug_clone utility cannot export all of
the required NXfiles. Teamcenter provides warning messages when an exported
briefcase file does not contain all of the required CAD data.
For more information, see the Data Exchange Guide and Preferences and
Export of incremental change to structures

Teamcenter 10.1 allows you to export changes (delta) to structure as tracked by
the incremental change (IC) mechanism, in full PLM XML format and in TC XML
format. Previously, Teamcenter provided export changes to structure by exporting
the item revisions as they evolve. Because the IC mechanism allows changes to
structure without requiring a new revision, Teamcenter now allows you to export
the structure changes alone, without exporting the entire structure. The exported
changes contain all relevant data required by the importing site to achieve the same
structure configuration as the exporting site.
The configured ICs whose incremental change elements (ICEs) affect the structure
in the following ways are detected and exported:
• Add line (new)
• Add line (existing)
• Add line (new or existing subassembly line)
• Remove line (cut)
• Remove line (subassembly line)
• Modify relative occurrence data
• Modify absolute occurrence data
• Create attachment (create on object) (File®New®Attachment)
• Adding an existing attachment (dataset/form)
• Delete attachment (dataset/form)
• Modify attachment
• Replace actions
The configuration of the structure is controlled by revision rules.

You can export incremental change data using the Tools®Export®To PLMXML or
To Briefcase (non-Global Services mode) menu commands from My Teamcenter,
Structure Manager, Multi-Structure Manager, and Manufacturing Process Planner.
Additionally, you can use the plmxml_export or tcxml_export utilities.
For more information, see the Data Exchange Guide, PLM XML/TC XML Export
Import Administration Guide, Structure Manager Guide, and Multi-Structure
Manager Guide.

What’s New
Multi-Site Collaboration support for 4th Generation Design data

For Teamcenter 10.1 sites that participate in your Multi-Site environment, you can
replicate data at remote sites, synchronize remote data, and transfer ownership
between sites for the following 4th Generation Design (4GD) business objects.
• Collaborative design (Cpd0CollaborativeDesign class)
• Design control element (Cpd0DesignControlElement class)
• Design feature (Cpd0DesignFeature class)
• Worksets (Cpd0Workset class)
• Promissory, reuse, and shape design elements (Cpd0DesignElement class)
• Partition (Ptn0Partition class)
• Subset definition (Mdl0SubsetDefinition class)
• Partition template model (Ptn0PartitionTemplateModel class)
When replicating partition data model memberships:

• Partition-owned memberships are exported along with the partition that owns
them.
• Member-owned memberships are exported along with the member that owns
them.
When replicating partition data model members:

• Partition-owned memberships are exported as a full object export.
For an example, see the Multi-Site Collaboration Guide.
them.
When replicating partition data model child parent links are owned by the child
partition and follow their owning partition when exported.
4GD data is transferred using the TC XML format and TC XML import export (TIE)
functionality. This provides scalability and performance required for the large
numbers of objects required by 4GD.
Multi-Site also supports transfers between Teamcenter 10.1 sites using a TC XML
payload and TIE functionality for other types of Teamcenter business objects. This
allows increased performance and scalability over existing Multi-Site transfer
features when support for a specific set of transfer options is not required.
For more information, see the Multi-Site Collaboration Guide and 4th Generation
Design Guide.

Data Exchange support for 4th Generation Design data

For Teamcenter 10.1, offline managed sites and unmanaged sites that participate
in your Data Exchange environment using briefcase files can export and import
4th Generation Design (4GD) objects.
Note The Briefcase Browser application does not support briefcase files containing
4GD data.
Data Exchange also supports low-level TC XML transfers for bulk loading data. This
capability can be used during site consolidation activities that include 4GD data.
You can export and import configured and unconfigured 4GD data and its supporting
infrastructure.
The following 4GD business objects are supported in briefcase transfers:
• Workset (Cpd0Workset class)

them.
them.

For an example, see the Data Exchange Guide.
them.
Exported objects are listed as the master object in the export log. The imported
objects are listed as new objects in the import log.
When importing the same object after the initial import the imported object is listed
as updated in the import log

What’s New
For roots objects designated as not exportable, the object is listed as

STUB_INSUFFICIENT_PRIVILEGE in the export log and a stub object is created
at the importing site.
For more information, see the Data Exchange Guide and 4th Generation Design
Guide.
Enhanced transition mapping process using Teamcenter Enterprise

dry run export feature
Teamcenter Enterprise provides a Dry Run for Export to a Remote Site command
available from the Actions®GMS Actions menu in the classic client and available
from the More Actions menu in the thin client when you select one or more
exportable objects.
This feature generates an XML file containing the selected objects and the required
related objects as determined by closure rules. This allow you to use the XML file
as a starting point for determining the mapping required to map your Teamcenter
Enterprise objects to Teamcenter objects.
You can use this feature independently from your Data Exchange environment. An
operational transition configuration with Global Services and Teamcenter setup is
not required to generate sample export XML files.
Because a completely operational transition environment is not required, this
function does not change any objects and does not create or update any export or
import records. Additionally, it does not support the following transfer features
that required a full setup:
• Switch actions (flip the switch functionality)
• Swarming
• Transfer of site ownership
• Include modified objects only
For more information, see the Transition Guide.
Multi-Site Collaboration support for Visio diagrams

If you use Multi-Site Collaboration to share Systems Engineering data, you can
export the following to another Teamcenter site:
• All Visio diagrams for a structure, including diagrams that are attached to the
root object and to its subordinate elements
• The latest revisions of individual Visio diagram objects, including their owning
objects
In each type of export operation, you can specify one of the following site ownership
options for the exported diagrams:
• Transfer ownership to the target site.
The exported diagrams become the master objects, with the full Systems
Engineering diagramming functionality.

For more information about editing diagrams, see the Systems Engineering
Guide.
• Retain ownership on the source site.

On the target site, the exported diagrams are read-only replicas of the master
objects. You can open replica diagrams, but you cannot edit them.
Note If a replica diagram’s owning structure is also a replica, you can make
changes in the diagram that do not affect the structure. For example,
you can enter a text description on the diagram page.
Note On the target site, proxy objects called stubs can represent objects whose
complete data is excluded from the export process. A stub is substituted for
a whole object due to certain conditions on the source site, such as object
ownership or user access permission.
You cannot open a stub, because it contains only that data that shows how
the excluded object relates to the exported objects in the same structure.
Multi-Site Collaboration uses the data in tracking revisions to the master
object.
The TC_relation_required_on_export preference controls the related objects that

are exported when you export an object using Multi-Site. Therefore, the required
datasets (image and Visio) and any other required object must be added to the
preference to support this feature.
For more information about Multi-Site preferences, see the Preferences and
For more information about remote import and export options, see the Multi-Site
Collaboration Guide.
4th Generation Design

4th Generation Design (4GD) allows users of NX CAD and Lifecycle Visualization
to cooperate in real time during the design cycle of a product. It is particularly
suitable for development teams working on large products that typically include
millions of parts, for example, ships and automobiles. It allow users to check out
and modify individual parts or subassemblies in the structure without locking the
entire structure or major assemblies.
4GD end users work in two main phases:
• Product or program initiation
When you initiate a product or program, the design team manager or other
expert user defines the main systems into which Engineering will provide
solutions. In many cases, the initial design is created from a similar product or
from an existing template for the product type. This initial framework is called
the collaborative design.
• Design authoring

What’s New
In this phase, design engineers populate the collaborative design with elements
that describe the product’s design. It can contain CAD designs, product-specific
geometry, and features such as datum points, welds, and weld seams. The
collaborative design can be populated directly or from within a workset that is
instanced into a subset of the collaborative design. Typically, the design team
manager allocates tasks in various areas of the collaborative design to designers
with appropriate skills and assigns worksets accordingly.
A collaborative design is a model of a product that is developed by a team of

contributors. The elements of the model are arranged in a hierarchy that allows
team members to collaborate and author common product information in an efficient
manner.
Users are assigned tasks through worksets. A workset is conceptually similar to a
user sandbox. It allows you to check out local copies of subsets and assemblies and
then make updates. Only one user at a time can check out a workset, and changes
are not shared with other users until they are checked in.
Model elements in a collaborative design can include:
• Design elements
A design element is an occurrence of a standard part design, a design component,
or a design assembly. Design elements are the basic building blocks with which
the users populate the collaborative design.
• Partitions
Partitions logically organize large sets of design elements into a hierarchy that
permits CAD users to easily find their assigned data. Partitions can also expand
into other partitions. They can represent functional divisions of the product
(for example, propulsion systems or avionics), or they can represent physical
divisions (for example, an engine room or electronics bay).
• Subsets
A subset is a collection of model elements from a single collaborative design that
is created by a search recipe or manually by a user.
• Product specific geometry

Positionable model geometry that is associated with the current collaborative
design, not with a reused design part. It is related to a DirectModel dataset
containing JT and TruShape files. Teamcenter uses the JT file when rendering
the positioned geometry and the TruShape data for refining spatial searches.
• Welds and weld seams

4GD supports individual welds of several types, for example, spot weld or arc
weld. A weld seam is a set of individual welds that may also control access
to those welds. Adhesive joins may also be modeled as welds. Weld data is
authored in NX, managed in Teamcenter, and consumed in Manufacturing
Process Management.
• Datum points
Datum points are typically used in the manufacturing process to help position
parts in fixtures or to specify measurement points used by quality assurance
processes. Weld data is authored in NX, managed in Teamcenter, and consumed

in Manufacturing Process Management. By default, only pin and surface datum

points are available.
• Routing
Routing represents piping or electrical cabling.
In addition to creating model elements in the CAD system, you can also realize BOM
lines, BOM view revisions (BVRs), items, or items revisions into a collaborative
design, for example, items that represent standard or bought assemblies. The
realized objects are referred to as reuse design elements.
You can configure a collaborative design by status, revision rule, variant rule, intent,
date effectivity, or unit effectivity.
Users manage 4GD data with the 4G Designer rich client application. You cannot
currently manage 4GD data with the thin client.
The 4GD solution must be specifically selected during server installation. When you
install the 4GD solution and other required features, Teamcenter provides four
Business Modeler IDE installation templates—4GD, Application Model, Realization,
and Partitions. Additional templates are required if you want to use the integrations
with Manufacturing Process Management and NX.
For more information about 4th Generation Design, see the 4th Generation Design
Guide.
Working with 4GD effectivity

Effectivity allows you to configure structures according to intents, specified unit
numbers, date conditions, or a combination of these values. You can configure
the entire collaborative design, part of the collaborative design, partitions, design
elements, or your working content (workset).
You can create and store effectivity criteria as a revision rule. This allows you to
utilize the same criteria for subsequent effectivity configurations. You can then
do the following:
• Configure the structure to see data that is effective for a date other than today.
• If you are using effectivity criteria relative to future dates, configure a structure
as of now to show the currently planned data effective for a future date.
• Specify an independent effective-for date or date ranges. These date ranges

typically include dates that are later than the as-of date. However, you can
specify a effective-for date that precedes the as-of date, for example, if you notice
an error in your effective-for conditions for past dates and you want to correct it.
In this example, you can compare the data effective for a specified past date as it
existed prior to your correction and now.
• Configure a structure as-of a past date while using a different date for the
effectivity configuration.
• Define intents that allow you to identify the goal of the configuration. Examples
of intents include production, carryover, and prototype. An intent may be
converted into unit or date effectivity later.

What’s New
In a typical scenario, a buyer ordered parts last month to support a prototype

build that is scheduled for next month. Some of the parts are delivered today and
the procurement department wants to validate the delivery. To do this, you query
for all objects effective for next month’s prototype build event as of last month’s
data version configuration. In this case, next month’s prototype build event is the
effectivity selection criteria, while last month’s data version configuration describes
the historical version selection criteria.
Note Effectivity configuration in 4GD is not implemented in other Teamcenter
applications. For example, elsewhere in the product, you cannot separate
effectivity and historical revisioning.
For more information about working with 4GD effectivity, see the 4th Generation
Design Guide.
Working with variants

You can work with variant data in the 4G Designer application. You must
first associate variant data to a product, and then associate the product with
a collaborative design.
4G Designer allows you to configure a collaborative design using variants, as follows:
• Associate a collaborative design with a product item revision.
• Specify variant conditions for model elements, including design elements, design
features, and partitions.
• Apply variant configurations to collaborative design content, including 120% and

discrete overlayed configurations if appropriate.
For more information about working with variants in 4GD, see the 4th Generation
Design Guide.
You use the Product Configurator to manage variant data in item revisions,
including values, rules, defaults, and configurations, before associating this data
with a product or program in 4GD.
Item revisions defining variant data that are not associated with design data are
referred to as option libraries. They provide a collection of variant data for others
to copy. If you associate an item revision to a collaborative design in 4GD, the item
revision becomes a product item revision. It manages the variant data with which
you can configure the collaborative design. Item revisions may allocate shared
variant data managed in other item revisions, define their own variant data, or both.
For more information about the Product Configurator, see Working with the Product
Configurator and the Product Configurator Guide.
Working with partitions

Partitions logically organize large sets of design elements into a hierarchy that
permits the CAD users to easily find their assigned data. Partitions can also expand
into other partitions. They can represent functional divisions of the product (for
example, propulsion systems or avionics), or they can represent physical divisions
(for example, an engine room or electronics bay).

You can create formal partitions representing actual Teamcenter items that
optionally go through a workflow to receive a status indicating they are approved
for use in collaborative designs. You can also create ad hoc partitions in the context
of the collaborative design that are not representing actual items. They are not
formally created or reviewed before use.
Partitions can be static or dynamic. End users populate static partitions by dropping
or pasting in design elements. In contrast, dynamic partitions are populated by a
search recipe, which contains a set of saved search criteria that identify the desired
content.
You can also add partitions to other partitions, typically to build a default
manufacturing process. For example, you can paste partition P1 into partition P2,
where the content of partition P1 represents a set of expected components and the
parent partition P2 represents a generic manufacturing process step. Pasting the
generic physical partition P1 into the generic process partition P2 implies that you
will assemble the components that will be attached to P1 with the manufacturing
process represented by P2. Pasting P1 as content into P2 does not build a partition
hierarchy; P1 and P2 generally have separate independent partition types.
Partitions can be organized hierarchically into breakdowns. Partitions reference
a scheme that defines constraints for the partitions in this scheme, for example,
the list of partition types that you can arrange into a partition breakdown in this
scheme. The nodes in a physical partition breakdown represent placeholders that
may be populated by actual product content obtained from part releasing systems,
CAD systems, or manufacturing planning systems.
These hierarchies are built using child-parent links, where the child chooses the
parent. As a consequence of the direction of this relationship partition, you must
delete hierarchies from the bottom up and (typically) release them from the top
down. This contrasts with BVR structures, which must be deleted from the top down
and are released from the bottom up.
Your administrator uses partition schemes to control the types of child partitions that
you can add to a partition used in each scheme. Several default partition schemes
are provided including Functional, Physical, and Spatial. Default partition types
provided include Design, Functional, Manufacturing, System, and Design. You can
configure these schemes for your environment with the Business Modeler IDE.
You can create partition templates using knowledge of partition breakdowns in
existing collaborative designs. A partition template is a stable, reusable, blueprint
of partition breakdowns that you could potentially reuse in multiple future
collaborative designs. A typical partition template contains one or more partition
schemes and a suggested partition breakdown structure. You can realize the
partition template or only the configured partitions into a collaborative design.
For more information about working with partitions, partition schemes, and
partition templates, see the 4th Generation Design Guide.
Making cacheless searches in 4GD

The existing Teamcenter cacheless search mechanism is available in 4G Designer for
spatial and attribute searches of live data. Cacheless searches allow you to query the
configured collaborative design to retrieve objects satisfying certain search criteria.
You can search the collaborative design or specified partitions; you cannot search
in subsets or worksets.

What’s New
You can make spatial searches by specifying any of the following parameters:
• Box volumes (either inside, intersecting or outside the box)
• Above, intersecting or below defined planes
• Proximity to another object
Spatial searches are particularly useful for end items that represent large products
containing a large number of structure lines, allowing you to focus quickly on a
particular area or part of the product. For example, if you are designing a ship, you
may want to identify all pipes that pass through a selected compartment but not
pipes that are routed around its perimeter.
You can also use an attribute or combination of attributes, including name,
description, created dates, last modified dates, released dates, and release status.
You can also specify a combination of spatial and attribute searches.
Teamcenter uses bounding boxes and TruShape voxel maps that are created during
the processing of CAD designs to implement cacheless searches. Internally, it uses
part-level bounding boxes to construct and maintain the necessary internal spatial
indexes. Bounding box data can be saved from NX or derived from JT files attached
to Lifecycle Visualization DirectModel datasets.
You can save these search queries as search recipes in subset definitions to run
multiple times, if required.
For more information about cacheless searches in 4GD, see the 4th Generation
Design Guide.
Implementing audit logging of 4GD objects

You can use existing Audit Manager functionality to maintain the history of 4GD
objects, partitions, and effectivity data. Audit Manager is an application that tracks
the history of events and actions performed on Teamcenter objects. The audit
log contains details of the object on which the event or action was performed, the
event name, the user who performed the action, the time at which the action was
performed, and any additional properties selected for logging. Depending on the
object type, you may be able to track its creation, modification, deletion, copying,
and release. The audit log is useful to generate reports and helps understanding the
activities users perform on Teamcenter data.
You create audit definition objects for 4GD in the same way as any other Teamcenter
objects. You can enable audit logging of any standard object defined in the 4GD,
Application Model, and Partition templates. The 4GD audit logging capability must
be specifically installed using Teamcenter Environment Manager (TEM).
To view its audit log, you can right-click an object in the Home view of the 4G
Designer application and choose View Audit Log.
For more information about creating audit definition objects, see the Audit Manager
Guide.

Transition to 4th Generation Design

You can transition to 4th Generation Design to achieve business efficiency
improvements without reworking your existing designs. 4GD provides a number of
capabilities that allow you to assist with this transition:
• For an existing product structure, you can generate the corresponding
collaborative design with the 4gd_populate_cd utility. You can then use the
generated collaborative design as the basis of a new version of the product or of a
similar product.
The collaborative design has the following characteristics:
o A name derived from the name of the source product or assembly
o A set of physical partitions and optional corresponding functional partitions
o One or more reuse design elements with names derived from the names of
the items from which the reuse design elements are realized
The product structure remains intact, and you can continue to manage it with
previously available structure management applications.
• You can realize existing design assemblies into a collaborative design that was
created manually or with the 4gd_populate_cd utility. A design assembly
defines in-product positions of end-item designs, and may contains classic
variant and occurrence effectivity information about the use of those end items
in a design. The realization process replicates a design assembly as reuse design
elements in the collaborative design. The design assembly remains intact and, if
it is subsequently updated, you can update the realization with the changes.
If you work in a Multi-Site Collaboration, you can realize shared design
assemblies, including stub assemblies.
For more information about realizing design assemblies into the collaborative
design, see the 4th Generation Design Guide.
• You can realize items, item revisions, BOM views, and BOM view revisions into
a collaborative design. The realized objects may represent existing or standard
parts or assemblies, or they may represent parts or assemblies sourced from
vendors. They remain intact and, if they are subsequently updated, you can
update the realization with the changes.
For more information about realizing parts and assemblies into the collaborative
design, see the 4th Generation Design Guide.
Working with the Product Configurator

The Product Configurator allows you to manage variant option libraries, including
values, rules, defaults, and configurations, independently of any application model.
For Teamcenter 10.1, you should only use the Product Configurator with 4G
Designer, but in a future version, it will be available for other applications.
You can use the Product Configurator application to define and manage the
variability of a product, including the following:
• Options families.

What’s New
• Option values.
• Fixed default and derived default rules.
• Variant constraints (rule checks).
• Groups of option families.
• Libraries of option families and values.
The Product Configurator contains several views that allow you to manage variant
data in the context of a product item revision:
• Variant Options
Allows you to create or edit option families, option groups, and values.
• Variant Defaults
Allows you to define derived default value rules within the context of the
currently selected product item.
• Variant Expressions Editor

Allows you to view and edit the details of one or more variant expressions. It
is a secondary view of any primary view that lists variant expressions. Variant
expressions are constructed in Teamcenter Normal Form (TNF) using similar
syntax to previous versions.
• Variant Constraints
Allows you to define constraints (rule checks) for selected values in the context of
the current item.
• Saved Variant Rules

Allows you to manage saved variant rules (SVRs) for the current item revision.
The Product Configurator uses the new classic variant data model, with the following
enhancements:
• The ability to define variability and named variant expressions for partitions.
• The introduction of variant rules to store variant configuration criteria and

optional validation records. They are attached to the product or the application
model (collaborative design) by GRM relationships. Variant rules perform the
same function as stored option sets, which will be deprecated in a future version.
Customers who use classic variants can begin to transition to variant rules by
setting the DisableSaveSos preference to false.
• Support for multiselection option families.
• Variant constraints may include both inclusion and exclusion rules.
• Variant families with free form values within optional boundaries, rather than
only lists of predefined values.

• Discretionary variant option families, in addition to mandatory variant option

families.
• The ability to turn off default rule processing, for example, when working with
120% variant rules.
• The ability to control the order in which default rules are applied. You can also
disable rule check processing and default processing if required.
Note Currently, you cannot use the Product Configurator to create or manage
modular variant data.
For more information about the Product Configurator, see the Product Configurator
Guide.
Users can validate 4th Generation Design objects

Users can validate 4th Generation Design (4GD) reuse design element and shape
design element objects in addition to other standard Teamcenter objects, such as
items and item revisions.
For more information about using Validation Manager to validate objects, including
4GD objects, see the Validation Manager Guide.
Multi-Site Collaboration support for 4th Generation Design data

For Teamcenter 10.1 sites that participate in your Multi-Site environment, you can
replicate data at remote sites, synchronize remote data, and transfer ownership
between sites for the following 4th Generation Design (4GD) business objects.
• Worksets (Cpd0Workset class)

them.
them.

What’s New

them.
When replicating partition data model child parent links are owned by the child
partition and follow their owning partition when exported.
4GD data is transferred using the TC XML format and TC XML import export (TIE)
functionality. This provides scalability and performance required for the large
numbers of objects required by 4GD.
Multi-Site also supports transfers between Teamcenter 10.1 sites using a TC XML
payload and TIE functionality for other types of Teamcenter business objects. This
allows increased performance and scalability over existing Multi-Site transfer
features when support for a specific set of transfer options is not required.
For more information, see the Multi-Site Collaboration Guide and 4th Generation
Design Guide.
Data Exchange support for 4th Generation Design data

For Teamcenter 10.1, offline managed sites and unmanaged sites that participate
in your Data Exchange environment using briefcase files can export and import
4th Generation Design (4GD) objects.
Note The Briefcase Browser application does not support briefcase files containing
4GD data.
Data Exchange also supports low-level TC XML transfers for bulk loading data. This
capability can be used during site consolidation activities that include 4GD data.
You can export and import configured and unconfigured 4GD data and its supporting
infrastructure.
The following 4GD business objects are supported in briefcase transfers:
• Workset (Cpd0Workset class)

them.
them.

them.
Exported objects are listed as the master object in the export log. The imported
objects are listed as new objects in the import log.
When importing the same object after the initial import the imported object is listed
as updated in the import log
For roots objects designated as not exportable, the object is listed as
STUB_INSUFFICIENT_PRIVILEGE in the export log and a stub object is created
at the importing site.
For more information, see the Data Exchange Guide and 4th Generation Design
Guide.
Support for 4GD in Manufacturing Process Planner

When you use 4th Generation Design (4GD) to author design data, you can assign or
consume this data in a manufacturing representation of the data that is based on a
BOM view revision structure. Teamcenter can bridge the gap between the two data
models to allow you to perform accountability checks and propagate attributes from
a collaborative design to a manufacturing structure (MBOM).
Note The term MBOM refers to a structure that is based on BOM view revisions
and not on a collaborative design.
When developing the MBOM, the manufacturing planner performs some of the
following tasks:
• Author manufacturing assemblies in the BVR structure, while consuming design
elements from the collaborative design.
• Add provisional elements (placeholders) for parts not yet defined in the
collaborative design.
• Add nongeometrical elements to assemblies, for example, consumable raw

material not modeled in CAD such as glue, oil, or water.
• Assign design features (welds and datums) from subsets to the MBOM,
including carrying over the design feature properties, attribute properties, and
connected-to relations.

What’s New
• Restructure assemblies by moving parts from one manufacturing assembly to

another.
• Decompose assemblies into subassemblies for creating kits.
Manufacturing Process Planner includes the Content Explorer as well as supporting

secondary views to view 4GD data without leaving the application. You can only
load subsets as root into this view. You cannot load a collaborative design, a design
element, or a workset as root.
The general workflow for working with collaborative design data in manufacturing
is as follows:
1. Create a 4GD subset in the Content Explorer that represents the scope of the
design elements that must be included in the manufacturing BOM.
2. Open the subset in the Manufacturing Process Planner application.
3. Create a BOM structure to represent the manufacturing BOM.
4. Assign design elements from the subset to the MBOM with the goal of assigning
all relevant design elements to the MBOM.
Note You can only assign design elements to precise BOM view revisions.
5. Assign design features from the subset to the MBOM.
6. Use the MBOM to support process structures and downstream integrations.
7. After changes are made to the design, compare the design structure to the
MBOM using an accountability check to find differences and propagate these
differences to the MBOM where necessary.
For more information, see the Manufacturing Process Planner Guide.

Managing product structures
Automating part-CAD alignment

Teamcenter provides part CAD independence, allowing you to associate parts and
designs in two ways.
• Globally, by relating part and design objects.
This capability is enhanced to provide a generic method of automating the
creation of a target object (for example, a part) as a postprocess of item creation
(for example, a design).
Automation also links parts and designs through a specified relation.
To implement automation, you must define the property value that the
target business object inherits from the newly created source business object
on the Fnd0InheritFrom Business Modeler IDE property constant. The
Fnd0LinkageOption list of values (LOV) allows you to select the source and
target objects. You must attach the Fnd0automateAndLink extension to
the post action on the create operation of the source item or its subclass. An
additional Fnd0isPLMXMLImportActive condition is provided to refine the
linking process.
Automation is particularly useful if CAD tools create designs and subsequently
save them to Teamcenter.
For more information about implementing this capability, see the Business
Modeler IDE Guide.
• Occurrence level alignment

You can align a design occurrence to a part occurrence, allowing engineers to
visualize the associated geometry.
The Delete PublishLink For Source command is enhanced, allowing you to
choose whether to delete the in-context shape, transformation, or both.
For more information about deleting publish links, see the Multi-Structure
Manager Guide.

What’s New
Making bulk updates of assemblies in a structure

Privileged users can make bulk updates of multiple assemblies with a single action,
for example, identifying and automatically replacing every occurrence of an impacted
part with the solution item. The update may include multiple types of operations
including replace, remove, add, and manual update (revise parts that are released)
when making design changes. This automates a manual, time-intensive process that
would otherwise take users many hours to complete. Typically, you replace a part
with a preferred substitute or nonpreferred substitute, although it is not mandatory
for the replacing part to be a designated substitute.
The assemblies can be updated by selecting the item revision and using one of two
processes:
• A single phase manually initiated process in My Teamcenter
• A two-phase change request (CR) and change notice (CN) change process in
Change Manager. The change processes allow the user to execute, track, and
manage all impacted structures when performing a mass replace (add or remove)
action. The update is stored in a change item.
As part of the two-phase process, you can also add, modify, and remove annotations
associated with the change. You cannot work with annotations if you use the
single-phase process.
A new Mass Update wizard and menu commands in the rich client and thin client
user interfaces allows you to initiate bulk updates in either application.
To configure this enhancement, you must set the following preference:
• MassUpdateDefaultRevRule
Defines the revision rule that is used to perform a where used search on the
target part of a mass update.
For more information, see the My Teamcenter Guide and the Change Manager Guide.
Making spatial searches

The spatial search user interface provided for cacheless searches in the Structure
Manager, Multi-Structure Manager, and Manufacturing Process Planner
applications is enhanced to match the interface provided in standalone Lifecycle
Visualization.
The following actions are available:
• Allow search volume creation based on a minimum bounding box enclosing the
selected parts.
• Define the bounding box dimensions with interactive sliders as well as spinner
controls.
• Specify a bounding box with x, y, z minimum and maximum extents of bounding

box dimensions in addition to centroid and size or origin and size specifications.
• Specify the spatial volume with an interactive graphical display.
• Allow spatial search based on user-defined units of measure.

• Distinguish between the input search scope and the spatial search results,
allowing you to easily re-establish the input scope.
• Specify target parts in the Structure Manager and Multi-Structure Manager

spatial filter dialog box in a table, similar to the one currently provided in the
Manufacturing Process Planner application.
The collapsible target part table displays in the search results dialog box with
the results table. You can select items in the target parts table and display the
selections in the tree or viewer. You can hide the target parts table by setting
the RDV_show_targets_on_results_dialog preference to false. (This setting
does not apply to manufacturing structure searches.)
• Allow searches based on fully contained, allow crossing, and fully outside values,
in a similar way to the DesignContext application.
For more information about the enhancements made to Manufacturing Process

Planner and Multi-Structure Manager, see Structure search enhancements.
For more information about making spatial searches, see the Structure Manager
Guide, Multi-Structure Manager Guide, and Manufacturing Process Planner Guide.
Saving the state of the View→Show Unconfigured... menu commands

Teamcenter provides you with several menu options that show or hide objects in the
structure and in the Graphics view. These are:
• Show GCS Connection Points
• Show Unconfigured Variants
• Show Unconfigured By Occurrence Effectivity
• Show Unconfigured Changes
• Show Suppressed Occurrences
Whether these options are turned on or off affects what is shown in the Graphics
view, and, therefore, affects any product view snapshots created in that view.
Teamcenter saves the state of these options so that when a product view is restored,
the same objects are displayed in the Graphics view as when the snapshot was
created.
For more information, see the Structure Manager Guide or the Multi-Structure
Manager Guide.
Defining conditions on PSOccurrence objects

You can configure Teamcenter to enforce any rules imposed by the organization on
what types of content are allowed in the structure. The user cannot add content that
is prohibited by the defined business rules.
The following types of restrictions on content within a structure are enforced:
• Only certain item classes or types can exist anywhere in a structure.
• Only certain item classes or types can be children of others.

What’s New
• Only certain item classes or types can be parents of others.
• Properties of the parent or child object must satisfy specified values or be NULL.
For allowable substitutes in a given BOM line, the same restrictions that apply to
the primary part occurrence are applied to the substitute.
The administrator uses the Business Modeler IDE to define these rules on explicitly
stated classes. Any subclasses or subtypes of these classes inherit the same rules.
Users can request on demand validation of property updates in Structure Manager,
Multi-Structure Manager, and the thin client. Feedback is provided if any edits
have violated the defined business rules.
To configure this enhancement, you must create and set the following preferences:
• PS_Default_Rev_For_Occ_Cond_Validation
Defines the default revision rule when a child item is used for validation.
• PS_Bypass_Occurrence_Condition
Configures the system to bypass occurrence condition validation for defined
actions or operations.
For more information, see the Business Modeler IDE Guide, Multi-Structure
Manager Guide, and Structure Manager Guide.
Options and variants support for multifield keys

Multifield keys are now supported in the variants feature in Structure Manager.
Both modular and classic variants are now compliant with the multifield key
framework.
Administrators use multifield keys to define a unique key for every object type that
is composed of the object’s properties. This allows end users to name objects with
the same ID, but the objects are uniquely identified in the database based on the
values of the object’s properties used in the multifield key.
Formerly, the item_id property was used as the module ID for modular variants and
as the ID for classic variants. Now, the object_string property is used instead of
the item_id property.
The object_string property is set using the DisplayName business object constant
in the Business Modeler IDE, and this constant is provided by the multifield key
framework.
The PSM_global_option_item_ids preference specifies the item IDs to use for
global options. You can now use the Tools®Variants®Set/Unset Global Option Item
menu command to add items to the PSM_global_option_item_ids preference.
For more information, see the Preferences and Environment Variables Reference.
Structure Manager usability enhancements

In the rich client, Structure Manager is enhanced to allow you to:
• Save column configurations and share them between users.

You can save and apply column configurations available for your group or site.
This allows you to configure your view of Structure Manager to view and edit
only those properties that your group or site deals with.
• Display substitute parts as separate BOM lines and edit, remove, or compare
them.
When a primary part has one or more substitutes, you can configure the
PSEShowSubstitutesPref preference and display all the substitute parts as
siblings of the preferred BOM line directly below the primary part. This allows
you to edit, remove, and compare substitute lines. In addition, the BOM Compare
report now identifies differences between substitutes in comparable structures.
• Freeze the BOM tree column during horizontal scrolling of the properties
columns.
This helps you easily view the name and number of the part without scrolling
horizontally. You can configure the BOM_Frozen_Column_Count preference
to determine how many columns you want to freeze.
• Hide Structure Manager tabs and configure which tabs in the data pane are
visible at the group or site level.
You can decide which tabs to display or hide in the data pane by configuring the
BOM_Display_Referencer_Panel, BOM_Display_Variant_Super_Panel,
and BOM_Display_Attachments_Panel preferences.
• Drag and drop multiple BOM lines.

The BOM pane allows drag and drop of multiple BOM lines. This is similar to
the copy and paste operation.
Note These enhancements are not available in the thin client.
Rolling up variant conditions

You can optionally propagate rolled-up variant conditions from the EBOM to the
MBOM. As a result, the BOM lines in the MBOM hold the equivalent variant
conditions as the corresponding BOM lines in the EBOM. Teamcenter copies the
variant condition on the source EBOM line, rolls up the variant conditions of all
parents of the source line, and then propagates the rolled-up variant condition to
the target MBOM line. The top levels of the EBOM and MBOM must be linked for
correct propagation of rolled-up variant conditions.
The accountability check is modified to recalculate the rolled-up variant condition
on the source line and compare it with the variant condition already stored on the
associated MBOM line. It then reports any partial match discrepancies between
the variant conditions.

What’s New
By default, rolling up of variant conditions is disabled and must be enabled by

setting the Rollup_Variant_Feature site preference to true.
You can also select the Consider values of rolled up variant condition when
searching for a partial match check box to manually disable or enable processing
of rolled-up variant conditions during compare and propagate operations, even if
rolling up of variants is switched on by preference. This check box is added to the
Partial Match tab and Propagation Settings dialog box of the accountability check
dialog box.
For more information, see the Manufacturing Process Planner Guide and the
Multi-Structure Manager Guide.
Enhanced closure rule filtering of BOM expansion

In Structure Manager, when expanding product structures, you can set closure rules
so that lines with selected criteria do not appear.
If the action type in the closure rule is SKIP, lines meeting the criteria do not
appear. If the action type is PROCESS, qualified lines appear but are not expanded
(they show a + symbol).
For more information, see the Manufacturing Process Planner Guide and the
Structure Manager Guide.
Managing manufacturing data
Manufacturing Execution System Integration

A manufacturing execution system (MES) is designed to help companies more
effectively and efficiently execute manufacturing operations from the product order
through each step of the manufacturing process to its final point of delivery. Equally
important, an MES is a dynamic information system that is key to collaborative
manufacturing strategies by providing mission-critical information about production
activities to managers across an organization and its supply chain.
A manufacturing execution system supports timely execution. Siemens offers a
tailor-made system to access all of real-time process information company-wide.
SIMATIC IT, Siemens MES, conforms to the ISA S95 standard, delivers multiple
capabilities, and enables optimum utilization with high production quality at lower
cost.
The new PLM–MES solution provided as part of Teamcenter 10.1 and certified
compatible versions of SIMATIC IT collects the bill of process, the bill of materials
to be consumed, and any relevant work instructions into a work package that is
released to the manufacturing execution system so that the MES has a work-plan
for that product without a need to re-author. The operator can use this information
to machine the desired product. If there is a problem in production that requires
engineering intervention, the planner can modify the contents of the work package
and send the changes to the MES. You can create a master execution plan containing
data relevant to multiple variants of the same product family (representing different
customer-orders) or you can create order-specific execution plans for execution by
the manufacturing execution system.

You can use the following new features as part of preparing the manufacturing
execution plan in Teamcenter manufacturing that can be transferred accurately and
efficiently to the MES where it awaits execution when the order is issued:
• Tools®MES®Validate for MES to validate that the data conforms to the data
model expectations and constraints of the MES, in particular SIMATIC IT.
• Tools®MES®Release to MES to validate and then transfer the package to

After release, Teamcenter includes monitoring capabilities of the status of the

transfer transaction and the level of consumption in SIMATIC IT.
• Tools®MES®Load Last Released Execution Plan to retrieve the exact state of
the execution plan the last time it was released to the MES
• Tools®MES®Launch MES Web Page to view MES data in the embedded

browser
The PLM-MES solution provides visualization capabilities. A new feature allows

the planner to create hyperlinks between a text fragment in the textual work
instructions and a product view in visualization. Once transferred, the same
hyperlink is available to the operator in SIMATIC IT.
The PLM-MES solution is pre-configured for Teamcenter manufacturing
and SIMATIC IT software. You can customize the services in Teamcenter
manufacturing to run with other manufacturing execution systems, but this requires
customer-specific projects.
For more information, see the Manufacturing Execution System Integration Guide.
Structure search enhancements

The structure search found in the Multi-Structure Manager and Manufacturing
Process Planner applications is enhanced to include the following features:
• You can save a search object that includes the search definition and, optionally,
the search criteria and search results. You can reload this search at a later date
and modify it, rerun it, or save it under another name. You can also make the
search available to other users.
• Teamcenter displays the search results in a separate view, the Structure Search
Results view. Each new search is, optionally, displayed in a separate tab in
this view.
• The spatial search is enhanced to include many new features.

For more information, see Making spatial searches.
• There is a new intuitive user interface for the Structure Search view. The
expand bars are removed.
• There is an enhanced tooltip for the Scopes box.
• The general criteria are displayed at the top of the view; the custom criteria
are displayed at the bottom.

What’s New
• The Clear and Search buttons are unavailable until the criteria are populated.
• All criteria are not cleared when you change the scope to a new structure.
Teamcenter clears only structure-specific criteria such as the spatial filter and
body-in-white criteria.
• A Clear button is available for each parameter on the user interface.
• The tooltips are enhanced for the Structure Search Results tabs.
• The Structure Search Results view displays the criteria along with the search
result.
• When the search is in progress, the result status bar displays an intuitive
message, for example, Search in progress…found 5 BOMLines.
• The views now have horizontal and vertical scroll bars.
For more information, see the Manufacturing Process Planner Guide or the
Multi-Structure Manager Guide.
Saving the state of the Show Unconfigured... buttons

Teamcenter provides you with several buttons or menu commands that show or hide
objects in the structure and in the Graphics view. These are:
• Show Unconfigured Variants
• Show Unconfigured By Occurrence Effectivity
• Show Unconfigured Changes
• Show Unconfigured Assigned Occurrences—(only applicable to process

assemblies)
Whether these buttons are turned on or off affects what is shown in the Graphics
view, and, therefore, affects any product view snapshots created in that view.
Teamcenter saves the state of these buttons, as well as the state of the guided
component search connection point display and any occurrence type filters you have
set, so that when a product view is restored, the same objects are displayed in the
Graphics view as when the snapshot was created. The state of these buttons is
stored in a configuration context.
When you create a new configuration context or save an existing configuration to a
configuration context, you can specify the state of the four buttons (On or Off) or you
can specify that the state is Preference-driven.
You can also view or change the state of all six configuration display options in the
configuration context properties.
Using standard text to create work instructions

By default, both librarians and planners can now use rich text capabilities in both
the standard text editor and the textual work instructions editor.

This version introduces a new data collection definition (DCD) type for images.
While the Image DCD currently does not contain image data, users can set its Out
of Range and Data Acquisition Method attributes to determine the behavior for
integer DCDs and real number DCDs.
Additionally, you can now reference datasets or Teamcenter product views in the
technical work instructions.
For more information about these features, see the Manufacturing Process Planner
Guide.
Composing 3D PDF reports

3D PDF provides templates that enable you to create the following types of reports:
• 2D PDF reports where the images originate from either product views or image
datasets
• 3D PDF reports that makes use of textual work instructions for the report
step description
The following functionality is introduced:

• In all reports containing a 3D component, the parts/tools table and the graphic
viewer are synchronized (a change in either is reflected in the other).
• All reports containing a 3D component (not including animation) have an option

to enable smooth transition between views.
• All reports containing a 3D component and animation have Zoom to Part and
Zoom to Tool functionality.
The following new report types are implemented in Teamcenter 10.1:

• Tools catalog
• Part catalog
• Part catalog with 3D
• Interactive part catalog
• 2D3D tabbed report
• 2D PDF report with activities
• 3D PDF report with activities
• 2D PDF report multi-page work instructions
• 3D PDF work instructions with 2D images
• 3D PDF rich textual work instructions
For more information about these features, see the Manufacturing Process Planner
Guide.

What’s New
4D planning
When manufacturing very large structures, it is often necessary to visualize the
completion state of a certain area of the structure at a specific point in time. 4D
planning is a capability used in construction projects to simulate and visualize
the construction over time. You take a construction schedule, link each building
activity and its 3D components with a timeline, and then view the progression of the
construction both in a GANTT chart and in 3D. For example, if you are building a
ship, you want to see what has been installed in the engine room on July 15th to
see if it will be ready for the next manufacturing step.
Teamcenter has embedded Schedule Manager features within Manufacturing
Process Planner to allow you to associate schedule tasks with processes or operations
to perform 4D planning. You can run a 4D analysis on a process structure, taking
physical and date input into consideration, to visualize the construction state. There
is a new manufacturing perspective, the Manufacturing – 4D Planning perspective,
that provides you with the views necessary to work with 4D planning.
Line balancing variant support

When using the line balancing feature in Manufacturing Process Planner, you can
now define product variants (also known as control models) to balance an assembly
line in a mixed production scenario. You can define production programs based on
these product variants that determine the probability of operations according to
given production rates.
In the Line Balancing Chart view, you can see the work content of the stations
according to the operation probability defined by the production program that you
are working on.

1 Header Displays the active production program. In the

figure, the line balancing chart is in Average
mode with no variant filter applied.
2 Overlay Shows the maximum and minimum work
content of all the product variants in the
production program. The station bar shows the
weighted average times of all the operations,
but the overlay indicates the range of work
content for these operations. Using this, you
can quickly determine if there are larger time
deviations from the average.
3 Operations Displays operations found in all the product
variants. The darker green operations have
a probability of 1—they are found in every
product variant. The lighter green operations
have a probability of less than 1—they are
not contained in every product variant. Their
probability is the sum of their individual
probabilities of being included in each of the
product variants.
4 Time per bar Shows a time value on top of each bar. You can
view:
• Overall working time: the working time of
the bar.
• Available time: the difference between

the capacity of the station and the overall
working time for the given bar.
• Utilization: overall working time/capacity

of the station.

What’s New
Structure expansion based on a closure rule

You can limit the expansion of the structure using site-specific criteria to reduce
potentially time-consuming expansions. For example, if a line has a monolithic JT
file attached to it, you may not want to expand the subassembly below it. Similarly,
you may not want to expand an assembly if it is not assigned to the current project.
You can now expand structures based on a closure rule that you set. The closure rule
you choose is specific to your company’s business needs.
The lines filtered out using closure rules are treated similarly to lines configured out
based on variants or effectivity. They do not show up as results in the accountability
check, nor can you use the Find menu commands to find them in other structures.
Find the View/Set Closure Rule for Expansion in the Tools menu.
Scoping data in studies

You can now create a study object in Manufacturing Process Planner. A study is
designed to gather data into one object. There are two types of studies:
• Shared study
The structure shares some of its elements with the source structure. A planner
can scope data from other structures. Changes made to the study are also made
to the source structure and vice versa.
• Isolated study
The structure is isolated from the source structure in terms of processes and
operations (consumed products or resources are shared). A planner can perform
what if scenarios, and the changes are not reflected in the source structure. A
planner can change the source, and the changes are not reflected in the study.
A planner can decide to propagate changes from the isolated study back to the
source structure or synchronize changes from the source structure to the study.
Studies are also used to pass data to Process Simulate for use in event and time
based simulations. Studies are also used to create tool design packages.
For more information about tool design packages, see Tool design packages.
For more information about creating studies, see the Manufacturing Process Planner
Guide.
Tool design packages

In a manufacturing environment, tool design is often outsourced to other companies.
These companies work with native NX to design custom tooling. You can create
a tool design package in Manufacturing Process Planner that contains pertinent
information from NX, Teamcenter, and Process Simulate. This information is
imported into NX at the tool design supplier. The tools design package can include:
• Consumed parts
• Work area data
• In-process assemblies coming from a previous stations

• Consumed welds
• Assigned datums
• Weld projections (coming from Process Simulate)
• Datum direction and type (defined in the context of the BOP)
• Resources
• Welds consumed by a particular resource
Information can also be suppressed so that it does not appear in the package or
during an export.
After completion, the tool designer sends the completed tool back to the manufacturer
where it is imported into Teamcenter from NX.
A tool design package is a kind of study. Studies are new manufacturing objects
being introduced this version.
Support for 4GD in Manufacturing Process Planner

When you use 4th Generation Design (4GD) to author design data, you can assign or
consume this data in a manufacturing representation of the data that is based on a
BOM view revision structure. Teamcenter can bridge the gap between the two data
models to allow you to perform accountability checks and propagate attributes from
a collaborative design to a manufacturing structure (MBOM).
Note The term MBOM refers to a structure that is based on BOM view revisions
and not on a collaborative design.
When developing the MBOM, the manufacturing planner performs some of the
following tasks:
• Author manufacturing assemblies in the BVR structure, while consuming design
elements from the collaborative design.
• Add provisional elements (placeholders) for parts not yet defined in the
collaborative design.
• Add nongeometrical elements to assemblies, for example, consumable raw

material not modeled in CAD such as glue, oil, or water.
• Assign design features (welds and datums) from subsets to the MBOM,
including carrying over the design feature properties, attribute properties, and
connected-to relations.
• Restructure assemblies by moving parts from one manufacturing assembly to

another.
• Decompose assemblies into subassemblies for creating kits.

What’s New
Manufacturing Process Planner includes the Content Explorer as well as supporting

secondary views to view 4GD data without leaving the application. You can only
load subsets as root into this view. You cannot load a collaborative design, a design
element, or a workset as root.
The general workflow for working with collaborative design data in manufacturing
is as follows:
1. Create a 4GD subset in the Content Explorer that represents the scope of the
design elements that must be included in the manufacturing BOM.
2. Open the subset in the Manufacturing Process Planner application.
3. Create a BOM structure to represent the manufacturing BOM.
4. Assign design elements from the subset to the MBOM with the goal of assigning
all relevant design elements to the MBOM.
Note You can only assign design elements to precise BOM view revisions.
5. Assign design features from the subset to the MBOM.
6. Use the MBOM to support process structures and downstream integrations.
7. After changes are made to the design, compare the design structure to the
MBOM using an accountability check to find differences and propagate these
differences to the MBOM where necessary.

Export of incremental change to structures

Teamcenter 10.1 allows you to export changes (delta) to structure as tracked by
the incremental change (IC) mechanism, in full PLM XML format and in TC XML
format. Previously, Teamcenter provided export changes to structure by exporting
the item revisions as they evolve. Because the IC mechanism allows changes to
structure without requiring a new revision, Teamcenter now allows you to export
the structure changes alone, without exporting the entire structure. The exported
changes contain all relevant data required by the importing site to achieve the same
structure configuration as the exporting site.
The configured ICs whose incremental change elements (ICEs) affect the structure
in the following ways are detected and exported:
• Add line (new)
• Add line (existing)
• Add line (new or existing subassembly line)
• Remove line (cut)
• Remove line (subassembly line)
• Modify relative occurrence data
• Modify absolute occurrence data
• Create attachment (create on object) (File®New®Attachment)
• Adding an existing attachment (dataset/form)
• Delete attachment (dataset/form)
• Modify attachment
• Replace actions
The configuration of the structure is controlled by revision rules.

You can export incremental change data using the Tools®Export®To PLMXML or
To Briefcase (non-Global Services mode) menu commands from My Teamcenter,
Structure Manager, Multi-Structure Manager, and Manufacturing Process Planner.
Additionally, you can use the plmxml_export or tcxml_export utilities.
For more information, see the Data Exchange Guide, PLM XML/TC XML Export
Import Administration Guide, Structure Manager Guide, and Multi-Structure
Manager Guide.
Automatic assembly graphics positioning in Resource Manager

Resource Manager uses coordinate systems to position components at the correct
location when creating tool assemblies. These coordinate systems are defined in the
part family templates in the Manufacturing Resource Library or imported from NX.
When you create graphics for the part family template components, these coordinate
systems are created and then saved to Teamcenter when you save the part file.
When you add a component to an existing one, either manually or using the guided
component search (GCS), Teamcenter checks the coordinate systems and aligns
them according to preset rules.
You can see the correctly assembled tools in the Graphics view where Teamcenter
automatically positions the graphical representations of the tool components in
the tool assembly.
When working with automatic assembly, you can:
• Show or hide all coordinate systems in a resource view.

What’s New
• Select multiple ICOs in the classification table and create graphics (and
coordinate systems) for these at one time.
• Hide guided component search connection points that are already connected.
• Use neutral coordinate systems to position components.
• View the coordinate system and its partner connection point on one line in the
structure view.
When automatically assembling resources, Resource Manager performs the following

tasks automatically when you click the Create/Update NX Tool Assembly Part File
button :
• Creates the NX part file
• Sets the tool junctions
• Identifies the cutting and non-cutting geometry
• Generates the spinning geometry
• Writes part attributes to the part file and maps them to Teamcenter
For more information, see the Resource Manager Guide.
Manufacturing features
Teamcenter allows you to define features that represent weld points or datums that
are not defined as part of the physical structure in the BOM. The features are added
to an MBOM structure when the structure is imported from an external authoring
system (this feature does not apply to NX). When importing features, you can:
• Specify a container to import discrete manufacturing features. Each XML
import corresponds to the content of one container. This allows you to import a
smaller portion of the welds.
• Specify whether you want to delete features not specified in the XML.
• View different 3D representations for each weld type. These are defined as
attributes in the form. The JT used depends on the number of connected parts.
Furthermore, for all features, you can now select a part and see which features
are connected to it by using the Show Connected Manufacturing Features menu
command.
Import/export of enterprise BOP search criteria

When working with enterprise bill of process structures (eBOP), the PLM XML
export of eBOP structures now contains information about the search criteria objects
for logical assignments and tool requirements. Modifications to these search criteria
objects in the PLM XML file are recognized by the PLM XML import functionality.

For more information about importing and export eBOP structures, see the Getting
Started with Manufacturing.
Visualizing products
New features for Base
Exact measurements in Base

Lifecycle Visualization now supports exact measurements at the Base service level. If
your model is created with precise geometry (NURBS or B-Rep data), you can choose
to display either exact measurements or approximate measurements. Previously,
exact measurements were available only in Standard, Professional, and Mockup.
For more information about exact measurements, see Working with 3D Models.
Advanced entity selection in Base

Lifecycle Visualization now supports selecting point, vertex, edge, surface, and
part entities at the Base service level. Previously, advance entity selection (edge,
surface, and part) was available only in Standard, Professional, and Mockup. This
enhancement allows Base users to make more types of 3D measurements.
For more information about selecting part entities, see Working with 3D Models.
Change the active reference set

You can now dynamically change reference sets at any time after an assembly is
loaded in the stand-alone viewer or the Lifecycle Viewer. Previously, a reference set
was applied only when an assembly was first loaded.
For more information about using reference sets, see Working with 3D Models.
Creating and viewing PMI effectivity

You can create and view assembly level PMI, including PMI effectivity, in NX,
Teamcenter, and Teamcenter lifecycle visualization. For example, NX customers
author CAD data that is configured for PMI. Next, JT data that includes the
configured PMI is saved to Teamcenter. From Teamcenter, you can then send JT
data to a supported Teamcenter viewer like Lifecycle Viewer and configure how you
want to display assembly level PMI. Assembly level PMI, including PMI effectivity,
is displayed in a supported Teamcenter viewer, where you can manipulate the view,
mark up the file, and save those results to Teamcenter.
Note • Non-NX CAD customers, for example JTOpen customers, can also
configure data assembly level PMI. You will require support to make
sure the customized integration performs correctly.
• Customizing and configuring the assembly level PMI solution is complex.

Please contact Global Technical Access Center (GTAC) or your sales
contact about the details for implementing this solution.

What’s New
For more information about creating and viewing PMI effectivity, see Working with
3D Models.
Enhancements to PMI display in Lifecycle Visualization

The display of PMI in Lifecycle Visualization has been enhanced as follows:
• You can now sort PMI using the same criteria as in NX. You can sort
alphabetically and alphanumerically, in ascending and descending orders.
For more information, see Sort PMI.
• Lifecycle Visualization now displays cross-section hatching the same way as it is

displayed in NX. This includes hatching patterns and hatch lines.
For more information, refer to the NX documentation.
Note For sorting, and displaying cross-section hatching the same way as it is
displayed in NX, you must use NX 9.0 or later.
• Unicode string specification in JT PMI is now consistent:

o PMI strings in DirectModel 8.0 are stored in Unicode format.
o Lifecycle Visualization now displays Unicode strings from JT in the

appropriate dialog boxes (for example, the PMI Attributes dialog box) and
in the PMI tree.
Note The conversion to Unicode PMI has no noticeable effect on the display of
PMI entities in the 3D scene.
Visualize 4GD worksets

You can now visualize 4GD worksets in the stand-alone application viewer and the
embedded Teamcenter Lifecycle Viewer. This enables you to perform design reviews
that make use of visualization session files.
For more information about sending 4GD worksets to the stand-alone viewer or the
Lifecycle Viewer, see the 4th Generation Design Guide.
Visualize occurrence groups

Lifecycle Visualization now properly loads and displays structures with occurrence
groups, including nested occurrence groups. This enhancement enables the
integrated stand-alone viewer and the embedded viewers to support product views
referencing occurrence groups from Multi-Structure Manager and Manufacturing
Process Planner. In addition, this enhancement enables proper visualization support
for in-process assemblies.
For more information about occurrence groups, see the Manufacturing Process
Planner Guide.
Create images of 3D models for Content Management

You can now capture 2D images of your 3D models and save them into Teamcenter
for use with Content Management.

For more information about saving images of 3D models for Teamcenter Content
Management, see Getting Started with Product Visualization.
PDF text search

You can now search for a word or text string in a PDF document. A marker is
included to help point to your text string, which is useful when searching large
documents.
For more information about searching text strings in PDF documents, see Working
with 2D images.
DGN enhancement
For DGN files, you can now configure 2D loader preferences to automatically find
reference files (XRef) that are saved on your local file system or server.
For more information about working with DGN files, see Working with 2D images.
2D export enhancement
Document is a now a supported export option. Use Document to export the entire
document, including all pages and markups as either PDF or CGM. When you export
a PDF file as a PDF file, an exact copy of the input PDF file is exported. That is, the
original quality of the PDF is exported. Also, PDF text search is supported when
you use Document.
For more information about exporting 2D images, see Getting Started with Product
Visualization.
View structure in monolithic JT files

Assemblies may contain subassemblies imported into Teamcenter as single
monolithic JT files. A monolithic JT file appears as a single part, even though it may
contain multiple component parts and an assembly structure. You can now use
Show Subcomponent to expand a monolithic JT file to see its component parts and
structure. Once expanded, the parts and assemblies from the monolithic JT file
behave the same as other parts and assemblies.
Previously, Show Subcomponents expanded monolithic JT files, but the component
parts appeared in a flat list. You could not view assembly structures contained
in monolithic JT files.
For more information about working parts and structures included in monolithic JT
files, see the Structure Manager Guide, the Manufacturing Process Planner Guide,
or the Simulation Process Manager Guide.
Automatic 3D model rotation

A new 3D navigation option called Automatic Motion continuously rotates the
navigation camera around the model, creating a spinning turntable effect.
For more information about automatic 3D model rotation, see Working with 3D
Models.

What’s New
Support for IPv6 addressing

Teamcenter 10.1 adds support for Internet Protocol IPv6 in its public facing
interfaces that use Teamcenter Client Communication System (TCCS). You can use
IPv6 addresses to connect Teamcenter 10.1 lifecycle visualization to Teamcenter
using TCCS on IPv6-enabled networks in a 4-tier environment.
IPv6 is the latest generation of network address protocol. It employs 128-bit
addressing, as compared to its predecessor, IPv4, which uses 32-bit addressing.
An IPv4 address is composed of four numbers between 0 and 255. For example:
146.122.220.221
An IPv6 address is composed of eight 16-bit hexadecimal values. For example:

2001:db8:ffff:1:101:12ff:de13:1322
IPv6 support is limited to clients or integrations that use TCCS and Teamcenter
components that communicate with clients on IPv6-enabled networks. Teamcenter
enterprise tier server components that communicate with other server components
in the same network are assumed to be on an IPv4 network and are not supported
on IPv6.
For more information about using IPv6 addressing and TCCS, see the Installation
on Windows Clients Guide, Installation on Linux Clients Guide, or Installation on
Macintosh Clients Guide.
Visualization support for multifield keys

Teamcenter lifecycle visualization is now multifield key compliant. Multifield keys
are identifiers assigned to objects to ensure their uniqueness in the database.
Most visualization features do not require any special configuration to work with
multifield key data, with the following exceptions:
• ClearanceDB – The managed product name must include the
__PLM_ITEMREV_UID value for the item revision, and the
clearance.cfgproduct file must include the multifield key properties for the item.
For more information about using ClearanceDB with Teamcenter multi-field key
data, see the ClearanceDB Administration Guide.
• MDS stamping – The MetaDataStamp_template preference must specify the

values of the multifield key properties associated with the item containing the
MDS_default_styles_template dataset.
For more information about configuring MDS stamping to work with multifield
key data, see the Preferences and Environment Variables Reference.
For more information about configuring multifield key data, see the Business
Modeler IDE Guide.
New features for Standard
Add BOM line properties to text markups in embedded viewers

You can now populate anchored text markups with BOM line properties in embedded
viewers.

In the Lifecycle Viewer and stand-alone Lifecycle Visualization you can late load
BOM line properties from Teamcenter and use the properties to populate anchored
text markups. The markups act as captions or callouts displaying specific metadata
from Teamcenter. Markups can be saved in visualization session files. The viewers
embedded in Structure Manager and Manufacturing Process Planner have the same
3D markup capabilities, however they did not have the ability to reference BOM line
properties. This enhancement adds the ability to load BOM line properties into the
embedded viewers and use these properties to populate anchored text markups.
Before you can add BOM line properties to anchored text markups in embedded
viewers, you must specify which properties should be available. You do that in the
Lifecycle Viewer or stand-alone Lifecycle Visualization. The BOM line properties
you specify are stored as the Interop_Vis_Attributes user preference.
Specify which BOM line properties can be added to anchored text markups
1. Send an Item Revision to Lifecycle Viewer (or open it in Lifecycle Visualization).
2. In the viewer, choose File®Preferences®Teamcenter Integration.
3. In the Preferences dialog box, click the Attributes tab.
4. From the Teamcenter Attributes list, select an attribute (a BOM line property)
and click Add.
Note Administrators can use the interop_vis_attributes_admin_filter

attribute to control which BOM line properties appear in the Teamcenter
Attributes list.
5. Repeat the previous step for each attribute you want to be available for text
markups.
6. Click OK.
7. Close the viewer.
8. Do the following to reload your Teamcenter preferences:

a. Choose Edit®Options®Filters.

What’s New
b. In the Options dialog box, click Filters (bottom).
c. Click Reloads the Site, Group, Role, and User preferences on the server
(top).
d. (Optional) To confirm that the preference is set correctly, type interop in

the Search by preference name box, and select the Interop_Vis_Attributes
User preference.
The BOM line attributes you selected in the Lifecycle Viewer should appear
in the Value area on the right.
Add BOM line properties to 3D anchored text markups

You can add BOM line properties to any 3D anchored text markups. There are
several ways to create 3D anchored text markups:
To Do this
1. On the 3D Markup toolbar, click 3D Markup , and
then click Text and Anchored .
2. Click a part in the viewing window.
3. If the Markup Text dialog box opens in Basic mode,

click Advanced to switch to Advanced mode.
4. In the Edit Markup Text section, expand Meta Data

Manually add text markup Attributes.
to a part.
5. Select an attribute and click Add <Key>.
6. (Optional) Add more attributes and other text.
7. (Optional) Select the Include labels check box.
8. Click OK.
The text markup appears next to the part in the
Viewing window.

To Do this
1. On the 3D Markup toolbar, click 3D Markup and
Preferences .
2. In the Markup3D Preferences dialog box, click the

Text tab.
3. In the Pre-defined Text section, click Edit.
4. In the Edit Markup Text section of the Edit Text

dialog box, expand Meta Data Attributes.
5. Select an attribute and click Add <Key>.
Add predefined text to 6. (Optional) Add more attributes and other text.
each part you click.
7. Click OK.
8. (Optional) On the Text tab of the Markup3D

Preferences dialog box, select the Include labels
check box.
9. Click OK.
10. On the 3D Markup toolbar, click Text , Anchor

Mode , and Use Pre-defined Text Mode .
11. In the Viewing window, click each part to mark up.

Markups are added as you click the parts.
1. On the 3D Markup toolbar, click 3D Markup and
Preferences .
2. In the Markup3D Preferences dialog box, click the

Text tab.
3. In the Pre-defined Text section, click Edit.
4. In the Edit Markup Text section of the Edit Text

Add predefined text to all dialog box, expand Meta Data Attributes.
selected parts with one
click. 5. Select an attribute and click Add <Key>.
6. (Optional) Add more attributes and other text.
7. Click OK.
8. (Optional) On the Text tab of the Markup3D

Preferences dialog box, select the Include labels
check box.

What’s New
To Do this
9. Click OK.
10. In the Viewing window, select the parts to markup.
11. On the 3D Markup toolbar, click Auto Create.

Markups are added to the selected parts.
New features for Professional
Motion clients honor constraints

Lifecycle Visualization motion clients honor constraints saved in session and PLM
XML files. When you open session or PLM XML files containing constraints In
the Lifecycle Viewer or stand-alone viewers, the constraints are honored when you
transform parts or play motion files. You can also:
• View the constraint tree in the Lifecycle Viewer Constraints view and on the
Constraints page of the Project Workspace window in stand-alone viewers.
• Show and hide constraint annotations in the Viewing window.
• Drag constraint annotations in the Viewing window.
• Show the degrees of freedom of constrained parts.

Note Creating and modifying constraints requires the Mockup service level.
For more information about constraints, see Working with 3D Models.
Color intersecting parts in cross sections

Clipped cross sections now display areas where parts intersect in a unique color.
For more information about clipping cross sections, see Working with 3D Models.
Side by side 3D comparisons

The 3D Compare feature now provides the option to perform side by side comparisons
of 3D models. In this mode, two or more viewing windows are tiled, vertically or
horizontally, and their cameras are synchronized. This enables you to easily stage
multiple models, and then visually compare them.
For more information about side by side 3D comparisons, see Working with 3D
Models.
Visual report enhancements

Visual reports now support Teamcenter cacheless searches. A cacheless search
occurs on the Teamcenter server, improving performance by minimizing the transfer
of data to your local machine.

On Windows, the interface used to create visual reports is also updated for greater
usability. For example, the visual report UI has been upgraded to streamline how
you specify evaluating an attribute and an attribute value.
For more information about visual reports, see Working with 3D Models.
Product view support for unconfigured view toggle states

When you capture product views, active view toggles can generate non-buildable
assembly configurations. With this release, the site administrator can now avoid the
creation of product views that capture non-buildable configurations. For example,
the administrator can configure the intervention level to Prevent, which prevents
you from saving a product view with active view toggles. The administrator can
configure the active view toggle intervention level to Off, Warning, or Prevent. The
default of this preference is Warning.
A product view sent from Teamcenter to the Lifecycle Viewer or the stand-alone
application viewer conforms to the state of the view toggle settings at the time
it was captured, except for the view toggle Show Suppressed Occurrences. To
avoid difficulties displaying product views with the view toggle Show Suppressed
Occurrences, configure Teamcenter product view options (preferences) so that
product views are not captured when this view toggle is active.
For more information about managing unconfigured data in a product view, see the
Manufacturing Process Planner Guide.
Create product views of expanded monolithic JT files

You can now save and update product views when working with expanded monolithic
JT files in Teamcenter. When you open a product view, the viewer loads the parts
and restores the view captured in the product view, although the structure in the
monolithic JT file is not automatically expanded in the tree.
Previously, if you used Show Subcomponent to expanded monolithic structure, you
could not save or update product views to capture the current state.
For more information about product views, see the Lifecycle Visualization Integration
Guide.
Enhancements to product view site preferences

Two enhancements were made to product view preferences:
• Your administrator can now configure the product view preference protection
scope. Administrators can configure access to changing product view preferences
at the USER, GROUP, or SITE level. The default protection scope is USER. If
the administrator sets the protection scope to SITE, some or all of the product
view preferences will be unavailable for you to change.
• Product view preferences were moved from the Product View Gallery context
menu to the Edit→Options menu. These preference options include working
with product views, thumbnails, and image capture.
For more details about changes to product view site preferences, see the Rich Client
Interface Guide.

What’s New
New features for Mockup
Constrain parts in an assembly

You can now create and manage basic constraints to control the position of parts in
an assembly.
New functionality includes:
• Creating and managing constraints in Lifecycle Visualization.
• Loading and applying saved constraints in the Lifecycle Viewer and stand-alone
viewer.
• Honoring constraints when playing motion files and transforming parts.
This feature integrates the D-Cubed 3D Dimensional Constraint Manager technology

(3D DCM) into Lifecycle Visualization.
For more information about constraints, see Working with 3D Models.
Enhanced clearance usability and performance

The 3D clearance feature has numerous enhancements, including:
• Intersection volumes no longer require XT B-Rep data.
For more information about creating intersection volumes, see Working with 3D
Models.
• The parts involved in a clearance penetration issue can display the extraction
vector.
For more information about displaying the extraction vector, see Working with
3D Models.
• Cross sections aligned with clearance issues display intersecting parts in a

unique color.
For more information about aligning cross sections with clearance issues, see
Working with 3D Models.
• The General Clearance Results list now displays clearance issues using a tree,
which you can easily group, search, sort, and filter. The list also includes a new
toolbar, which provides easy access to many commonly used features.
For more information about working with clearance results, see Working with 3D
Models.
• A new Clearance Toolbox window enables you to quickly disposition clearance

results.
For more information about using the Clearance Toolbox window to assign
status information to clearance results, see Working with 3D Models.
• A summary of the analysis is now available.

For more information about viewing the analysis summary, see Working with 3D
Models.

• Multi threaded clearance analysis is now available for both Mockup and the
clearance calculator (clearance.exe). This improves the performance of clearance
analysis significantly on machines with multiple CPUs or cores.
For more information about enabling multi threaded clearance analysis, see
Working with 3D Models.
• The Contact/Penetration Check option in the clearance calculator settings

is now enabled by default. When you run a clearance check, all issues are
automatically analyzed to determine if they are contacts or penetrations.
For more information about the Contact/Penetration Check option, see Working
with 3D Models.
• Clearance issues are now analyzed by default. After running a clearance check,
when you double-click a clearance issue in the General Clearance Results
list, the part pairs involved in the issue are analyzed and displayed in the 3D
Viewing window according to the clearance results preferences.
For more information about analyzing clearance results, see Working with 3D
Models.
Filter enhancements
The visualization filters available in the stand-alone application viewer and the
Lifecycle Viewer have been updated to support Teamcenter cacheless searches.
A cacheless search occurs on the Teamcenter server, improving performance by
minimizing the transfer of data to your local machine.
For more information about visual reports, see Working with 3D Models.
New features for ClearanceDB
New ClearanceDB product attributes

Teamcenter 10.1 lifecycle visualization includes the following new product
configuration parameters for ClearanceDB:
• EAICL_CLEARANCE_CHANGE_DETECTION
You can use this parameter to specify the change detection method. You can
choose to determine change based on model inputs (geometry changes, part
transformations, requirement, or variant condition) or analysis outputs (result,
type, location, orientation, intersection volume, or requirement).
For more information about the EAICL_CLEARANCE_CHANGE_DETECTION
product attribute, see the ClearanceDB Administration Guide.
• EAICL_PRESERVE_RESOLVED_ISSUES
You can use this parameter to maintain a history of ClearanceDB issues. If set to
True, resolved issues are preserved; if set to False, resolved issues are deleted.
For more information about the EAICL_PRESERVE_RESOLVED_ISSUES
• EAICL_PRODUCT_HISTORY_MAX_ENTRIES

What’s New
You can use this parameter to specify the maximum number of ClearanceDB
history issues. If not included in the product configuration, or to a value of -1, no
deletion of history entries is performed.
For more information about the EAICL_PRODUCT_HISTORY_MAX_ENTRIES
Oracle Instant Client support

ClearanceDB now uses the Oracle Instant Client instead of the full Oracle Client for
proxy connectivity to the Oracle database. This results in a simplified installation
process for the proxy, along with a smaller footprint for the Oracle Client software.
For more information about downloading and installing the Oracle Instant Client for
use with ClearanceDB Proxy, see the ClearanceDB Administration Guide.
64-bit ClearanceDB Proxy on Solaris and Linux
The ClearanceDB Proxy on Solaris and Linux is now 64-bit. In previous releases, the
proxy was shipped as a 32-bit application on these platforms.
For more information about ClearanceDB requirements, see the ClearanceDB
Administration Guide.

Repeatable Digital Validation
Making product-scoped cacheless searches

At some customer sites, a significant proportion of the product structure data in the
databases is no longer in use, for example, it belongs to programs that are complete
and no longer active. If you index this data for spatial searches, it has an adverse
impact on the speed at which indexes are created and also on search performance.
Cacheless searches allow you to limit spatial and attribute searches to active
programs, which may correspond to end items, top-level items, or top-level
product items. You can index data in the scope of structures defined by a system
administrator, rather than indexing the entire database. By default, all data is
unsearchable; you must run the qsearch_process_queue utility on the chosen
product structures to mark all items and occurrences that are part of those
structures as indexable. The create_or_update_bounding_box_and_tso utility
permits you to:
• Allow processing only of bounding boxes attached to indexable product structures

and their components.
• Query for missing bounding boxes and TSO data for the indexable product.
After an active structure is indexed, you can make incremental updates to its spatial
search index, rather than generating a complete new index each time. Incremental
index updates are restricted to product structures previously identified as active.
To do this, the administrator runs the qsearch_process_queue utility with the
-process_queue option.
Product-scoped cacheless searches also include the following enhancements:
• A cycle detection and removal tool to detect and remove cyclic data that may
adversely affect spatial indexing operations. The output of the tool is a dot (.) file
that you can use with various tools to decide how to break the cycles by modifying
the BOM structure. For example, this format is interpreted by external utilities
available with the third-party Graphviz freeware package. The output can be
processed to produce a graphical representation of the cycles, so that the user can
easily decide how best to break the cycles by identifying structure edges to ignore
when traversing a structure. The identified nonstructure edges are ignored
when the spatial indexer traverses a structure for spatial index generation.
Note Automatic cycle removal is not supported.
• Performance and scalability improvements by reducing the number of SQL calls

made to fetch bounding boxes, simplifying the occurrence note initial query, and
the introduction of improved SQL code for structure traversal.
• The spatial indexer utility (qsearch_process_queue) can now handle up to

30,000 requests per hour in the indexer queue. The requests are assumed to
consist of a mixture of geometry (for example, bounding box and transforms)
and nongeometry (for example, occurrence) changes. Requests are processed in
batches, in the order in which they are received.

What’s New
• The ability to log and track the items made indexable for validation and
accuracy checks is added. To permit this, a list_indexable option is added to
the qsearch_process_queue utility. Optionally, you can also store the results
in a flat file.
• The ability to clear the spatial indexes from a product (unindex it) is
added. To achieve this, a clear_product_indexes option is added to the
qsearch_process_queue utility. If you use this option, ensure you analyze the
impact to items shared across programs, to ensure you remove indexes specific to
the affected product. That is, if you remove indexes from product A, any indexes
it shares with product B still remain indexed.
• The ability to list legacy transforms for a given product or program is added to
the qsearch_process_queue utility.
• Streaming mode in DesignContext. Previously, errors occurred on some target

parts when the RDV_qsearch_streaming_mode preference was set to true.
• Statistics can be collected for spatial search performance, assisting with further
tuning and improvements.
• The Create_or_update_bbox_and_tso utility can accept a list of datasets in

delete mode.
• Unit of measure support is added to Classification searches.
• The identify_non_structure_edges utility is added to mark parent and child

items that are ignored when adding, listing, or removing entries in spatial
indexes.
For more information about product-scoped cacheless searches, see Getting Started
with RDV and the Cacheless Search Guide.

Managing CAE data
Launch tool enhancements for multifield keys

Multifield keys is now supported for simulation launch process in Simulation
Process Management.
Simulation Process Management provides the capability to launch configured batch
meshing tools. When a user starts the option to launch a batch meshing tool either
interactively or through a workflow, the system evaluates the preference values
that hold the configuration information, prepares the appropriate input, and starts
the appropriate launch script.
The simulation process is enhanced to handle the export of parameter and criteria
files when the types holding the files are defined with multifield keys. The process
also handles the passing of the input item revisions to the launch script when the
input item revisions are of types defined with multifield keys.
For more information, see the Simulation Process Management Guide.
Structure management enhancements for multifield keys

The New CAE Item wizard is used to create CAEModel, CAEGeometry, CAEResult,
CAEAnalysis, and StructureMap item types. This wizard is enhanced to support the
creation of items that are configured with multifield keys.
In addition, the following dialog boxes and data panes are enhanced in CAE Manager
to support multifield keys:
• Open CAE Model (dialog box)
• Open CAE Analysis (dialog box)
• Open Product (dialog box)
• Edit References (dialog box)
• Composite (data pane)
• Attachments (data pane)

What’s New
Create CAE data using packages

The CAE Manager application provides capabilities to create and manage CAE data.
Currently, the New CAE Item wizard allows users to create a single CAE item and
item revision and create relations with existing item revisions, as well as create and
attach datasets to the new CAE item revision. Often, analysts want to create their
CAE data in collections or packages of related objects.
Package definitions may include a description of the new items and item revisions to
be created and the relationships that should be established between them, as well as
possible relationships with existing item revisions. Further, the package definition
describes datasets to be created and attached to any new item revisions.
Simulation Process Management is enhanced to support defining and creating
packages of CAE data. The simulation administrator or database administrator
(DBA) can use CAE Manager to capture package definitions accessible to analysts
across the Teamcenter site using CAE Manager to capture package definitions
accessible to members of their group to create packages of CAE data. Individual
users can use package definitions to create their own packages of CAE data.

Usability enhancements incorporating multiple views

CAE Manager provides users the capability to view and manipulate loaded product
structures, CAEModel structures, and CAEAnalysis objects in separate panes, of
which only one of these panes can be active at a time. Additionally, these panes
support the viewing and manipulating the details of the loaded objects through
various data panes associated with the main object pane.
Simulation Process Management is enhanced to allow users to separate each of the
Product, Model, and Analysis panes into separate views, as well as each of the
currently supported data panes. This provides more flexibility to view the data in
these panes at the same time and for easier comparison.
The tabbed layout previously used in Simulation Process Management is replaced
with a more dynamic selection of views. You can:
• Open only the relevant data views as required for your current task.
• Position and size any view as convenient to you.
• Maximize, minimize, or even undock views and move them to another monitor.
• Drag and drop items from one view to another appropriate view.
Checking out-of-date notifications

The Composite and Attachment panes in the CAE Manager Model pane provide
capabilities to check for references, check for later revisions, and check for
attachment changes. Further, there are tools to update the references of the
CAEModel item revisions represented in the loaded CAEModel structure based on
these findings. These help determine whether the CAEModel data is out-of-date
with respect to referenced data.
The capability to examine out-of-date references is now extended to CAEAnalysis
item revisions. Prior to Teamcenter 10.1, this capability was available for CAEModel
item revisions only.
Also, previously, determination of whether changes occurred was based solely on the
last modified dates of the related objects and the existence of later revisions. This
is enhanced to provide customers with more flexible control of determining and
recording out-of-date states for both CAEModel and CAEAnalysis item revisions.
The enhancements allow analysts to:
• Check CAEModel and CAEAnalysis item revisions for changes and mark them
as up-to-date.
• Check CAEModel and CAEAnalysis item revisions for attachment changes and
update or add latest references.

What’s New
Comparing structures
CAE Manager provides a mechanism through data mapping and applying structure
maps to quickly generate a CAEModel structure from a product structure. It also
provides a mechanism through the Inspector view to compare an existing CAEModel
structure to a product structure and make modifications to the CAEModel structure
based on the comparison.
The Inspector view is enhanced by incorporating concepts from data mapping. When
you perform any actions in the Inspector view that result in creating new items and
item revisions, CAE Manager can leverage the mappings defined in the data map
file to create these new objects. Moreover, comparison capabilities are enhanced to
include some detections of restructuring and introduction of actions to react to a
detected restructuring.
CAE structure attribute enhancements

You can use the CAE Manager application to quickly create a CAEModel structure
from a product structure through data mapping and applying structure map
rules. The comparisons performed in the Inspector view rely on evaluating target
relationships between the item revisions represented in the model structure and
the item revisions represented in the product structure. This project introduces
enhancements that allow the comparison of mapped attribute values in the model
structure with current attribute values in the product structure.
Enhancements include:
• Changes to the data model to establish an explicit target occurrence relationship

between occurrences in the CAEModel structure and occurrences in the product
structure. The operations that support the creation and manipulation of this
newly introduced relationship are limited in version 10.1. You can create
the relationship manually or Simulation Process Management creates it
automatically when you execute a data map or a StructureMap item.
• An accountability check in the CAE Manager perspective. The existing

accountability check functionality in Teamcenter is extended to allow you to
compare the model structure with the product structure. You can compare any
attributes that you declare as mapped in the data mapping configuration. The
compared values are driven by the data mapping file.
These enhancements allow analysts to:
• Create a CAE target occurrence relationship between product and model

occurrences.
• Compare the model structure with a product structure using an accountability

check for mapped attribute value changes and identify components and attribute
values that are not synchronized.

Simulation tool launch usability enhancements

Simulation Process Management provides a framework for configuring and
launching simulation tools that can include preprocessors, solvers, postprocessors,
and other tools. Analysts can launch simulation tools from Simulation Process
Management to send a product structure to a preconfigured application for analysis.
Analysis tools provide accurate results on design behavior. After the analysis is
complete, the results are imported back to Teamcenter. You can view the results and
make changes to the product structure as appropriate.
The credentials of the active user (user, group, and role settings) determine whether
the user has access to the configured tools.
Usability enhancements are as follows:
• Allow analysts to customize the menu and make frequently used simulation
tools accessible from the toolbar.
• Allow the simulation administrator to customize the simulation tool launch

dialog box.
• Improve the progress monitor to provide easy access to the temporary files being
manipulated by the simulation tool and provide a capability to prematurely
terminate the simulation tool.
These enhancements allow the simulation administrator to:

• Configure a style sheet file for simulation tool launch.
• Configure skipping the simulation tool launch dialog box during tool launch.
• Configure an icon file name for simulation tool launch.
• Specify group settings to define the launch display for a category/tool.
These enhancements allow analysts to:

• Select an entry in the simulation tool launch progress monitor, and select an
option to open the associated temporary folder/directory to gauge the progress of
the tool execution or examine intermediate results.
• Select an option to terminate the process associated with the launch.
• Configure favorite tools in the My Favorites submenu.
CAE structure creation and comparison enhancements

You can use the CAE Manager application to quickly create a CAEModel structure
from a product structure through data mapping and applying structure map rules.
CAE Manager also provides mechanisms through Composite, Target References,
and Inspector views to compare an existing CAEModel structure to a product
structure and make modifications to the CAEModel structure based on the
comparison.
Enhancements are as follows:

What’s New
• Select all commonly color coded lines. Often analysts want to select objects
presented in secondary views such as Attachments, Composite, and Target
Reference views based on the color-coded results and perform subsequent
actions. To make it easier to select the desired objects, these views now provide
an option to select all commonly colored objects in the view.
• Find represented product and model BOM lines from the Target References
view. The Target References view introduces a capability to identify BOM lines
in the product and model structure that are being represented by selected lines
of this view.
• Find represented product from the Model view. The Model view is enhanced
with a new capability to quickly identify the objects in the Product view that
correspond to a selection in the Model view.
• Find represented model from the Product view. The Product view is enhanced
with a new capability to quickly identify the objects in the Model view that
correspond to a selection in the Product view.
• Replace model item revision in one structure with another. The Model view
in CAE Manager provides capabilities to manually edit the loaded CAEModel
structure. There is currently an option to replace the existing BOM line with
an existing item revision. This capability is enhanced to provide an alternative
that allows the user to select from a list of existing item/item revisions that have
the corresponding product item revision as a target.
• Configure data map item revision location for persistence. To manage rules
deployment across a multi-site installation, data map definition files have to be
moved from the TC_DATA folder of the operating system to the Teamcenter
database. The Edit option panel now provides an option to specify the item
revision to manage these definition files based on a preference.
• Define data mapping rules to map datasets. You can specify rules that allow the
system to create and attach datasets to the item revisions in the output structure
based on datasets attached to the related item revisions in the input structure.
The rules allow the datasets in the input structure to be referenced directly by
the item revisions in the output structure or to be copied and the dataset copy
to be attached to the newly created item revisions.
• Define data mapping rules to map project information. You can specify rules
that allow the system to set project information on newly created items and item
revisions based on information found in the input structure.

Managing quality data
Defining quality inspection processes

Users must create several forms in Dimensional Planning and Validation (DPV) to
define the properties for a plant, device, and routine in a quality inspection process.
Administrators can now use the Business Modeler IDE to configure these objects so
some or all of the forms are automatically created when the object is created. The
Dimensional Planning and Validation Administration Guide also provides tips for
creating and managing forms.
For more information, see the Dimensional Planning and Validation Administration
Guide.
Date and time displayed in DPV Measurements

The DPV Measurements application now displays the date and time when event
data was added to the measurement database. To display the date and time, after
updating Dimensional Planning and Validation (DPV) and Teamcenter to 10.1, you
must update each of your measurement databases.
For more information, see the Upgrade Guide.
DPV enhancements for handling errors in measurement data

Dimensional Planning and Validation (DPV) now accommodates errors that occur in
measurement data by letting you configure whether it should ignore extra feature
measurements (those not defined in the DPV Engineering workbook) and provide
a warning when it ignores the data. You use the new option in the FactoryLink
Configuration Explorer to set the threshold for handling extra feature attributes.
In addition:
• The DPV Error Viewer lets you view the partial success and warning files similar
to how you view failed and error files.
• The ETL Dashboard displays the partial success file count, and lets you download
and view the warning files associated with each partial success file. The Partial
Success Report page displays the file names of partial success and warning files.
You can also upload, download, reprocess, and delete the partial success files.
For more information about configuring the threshold for extra feature attributes, see
the Dimensional Planning and Validation Administration Guide. For information
about the DPV Error Viewer and the ETL Dashboard, see the DPV online help
collection.

What’s New
Managing maintenance, repair, and overhaul
MRO support for multifield keys

Multifield keys are identifiers assigned to each object to ensure their uniqueness in
the database. Multifield keys are supported for the following MRO applications:
• As-Built Manager
• Service Manager
• Service Planner
• Service Request Manager
• Service Scheduler
For more general information about multifield keys, see the Business Modeler IDE
Guide.

Customizing Teamcenter
Enhanced support for UTF-8 in Teamcenter Services

A services-oriented architecture (SOA) C++ client can now communicate with
a UTF-8 enabled Teamcenter server and database when the client is using the
Teamcenter client communication system (TCCS) and also in non-TCCS mode.
Previously, although Teamcenter supported character data under UTF-8 encoding,
UTF-8 enabled client applications that used Teamcenter Services C++ could not
communicate with a UTF-8 Teamcenter server and database.
The XML serialization and parsing in Teamcenter Services on the client and the
C++ server side are enhanced to handle UTF-8 data as well as any other encoding
specified by the client application. Clients can specify the type of encoding (UTF-8 or
some other type) through a new OPT_ENCODING_TYPE connection option. If this
option is not set, the conversion from the local code page to UTF-8 (while encoding)
and UTF-8 to local code page (while decoding) takes place.
The getTcSessionInfo service also is enhanced to get the server encoding
information that is added to the TcSessionInfo response. This response object has
an extraInfo array that contains the server encoding value. The encoding value can
be retrieved from this array at the client application.
For more information, see the Services Guide.
Dynamic buffer allocation support for multibyte strings

Many of the Integration Toolkit (ITK) APIs in Teamcenter are based on fixed-size
string lengths. As long as Teamcenter is operating in a deployment scenario where
each character occupies only one byte (such as western European languages), there
are not any issues. However, when Teamcenter is deployed in a scenario where each
character can occupy multiple bytes (such as Japanese, Korean, or Chinese), data
truncation can occur. Therefore, the fixed-size buffer ITK APIs are now deprecated,
and wrapper APIs are now provided for each of the fixed-size buffer APIs.
Siemens PLM Software recommends that you refactor any customizations that
use the older fixed-size buffer APIs and replace them with the new APIs. For this
version of Teamcenter, the new APIs are simply wrappers for the older fixed-buffer
APIs. In a future version, the new APIs will use the type of char * instead of
fixed char array size in the input and output parameters. The new APIs will use
dynamic buffering to replace the fixed-size buffering method. Early deprecation of
the fixed-size buffer APIs provides enough time for you to move to the new APIs.
There is no change to the existing APIs. The new APIs merely call the existing API;
no code work for these new APIs is needed.
For a list of the deprecated ITK APIs and their replacements, see the Deprecated
tab in the Integration Toolkit Function Reference.
Note The Integration Toolkit Function Reference is available only in the
Teamcenter HTML Help Collection. It is not available in the PDF collection.

What’s New
Bulk object creation

When some object types such as items are created, a number of associated objects
are also created. This is known as bulk create.
A single transaction for bulk object creation is now available, thereby significantly
reducing the number of SQL queries. With this single transaction method, bulk
creation is improved for Item, ItemRevision, Dataset, and Form business object
types.
The following bulk create APIs are supplied, as well as a user exit:
• ITK
TCTYPE_create_objects
For more information about this API, see the Integration Toolkit Function
Reference in the Teamcenter HTML Help Collection.
• Teamcenter Services
DataManagement.CreateResponse bulkCreateObjects(DataManagement.BulkCreIn[] input)
For more information about the bulkCreateObjects service operation, see the
Services Reference in the Teamcenter HTML Help Collection.
• User exit
USER_new_item_ids
For more information about this user exit, see the Integration Toolkit Function
Reference in the Teamcenter HTML Help Collection.
Note The Integration Toolkit Function Reference is available only in the
Teamcenter HTML Help Collection. It is not available in the PDF
collection.
By using the new APIs, you no longer must implement custom bulk object creation
through POM ITK APIs that bypass the business logic of object creation.
For more information about create APIs, see the Server Customization Programmer’s
Guide.

Changed default display value of Boolean properties

The default display value of Boolean properties is changed from “Y” and ““ (or blank)
to True and False. The change was made to align the display value with industry
standards for a Boolean value.
Note If for some reason you still want to use the “Y”
and ”“ values, you can change the values in the
TC_ROOT\lang\textserver\lang_locale\tc_text_locale.xml file. For
example:
<key id="gk_logical_true_label">Y</key>
<key id="gk_logical_false_label"></key>
If you have customization code that uses the hard-coded values of “Y” and ““, you
must remove the hard-coded values:
• Server code
Replace hard-coded display value comparison code with the is_logical function
call. For example, replace this:
AOM_UIF_ask_value(rev1, "fnd0IsCheckoutable", val);
//Please do not assume the display value for logical property (true) is “Y”
if (tc_strcasecmp(val, "Y") == 0)
with this:
logical verdict = false;
int ifail = STRING_is_logical( val, &verdict );
if (verdict)
Remove hard-coded display value comparison code and use

the AOM_ask_value_logical call for scalar properties and
AOM_ask_value_logicals call for array properties. For example, replace this:
//Please do not assume the display value for logical property (true) is “Y”
if (tc_strcasecmp(val, "Y") == 0)
with this:
AOM_ask_value_logical(rev1, "fnd0IsCheckoutable", val);
if ( val )
• Java client code

Remove hard-coded values. For example, replace this:
String blIsPrecise = bomLine.getProperty( CAESEConstants.BOMLINE_PRECISE_PROPERTY );
if( blIsPrecise.equals( "Y" ) )
with this:
if( bomLine.getLogicalProperty( CAESEConstants.BOMLINE_PRECISE_PROPERTY ) )

What’s New
Teamcenter solutions
Aerospace and Defense
Aerospace and Defense multifield keys support

• Aerospace and Defense objects support multifield keys.
When you enable multifield keys, if there are multiple technical document
objects matching a given source document, Teamcenter allows you to select the
correct technical document.
• Contract data management objects also support multifield keys.

When you enable multifield keys, if there are multiple contracts for a given
contract ID, Teamcenter allows you to select the correct contract.
For more information, see the Aerospace and Defense Solution Guide.
Location code management enhancements

Managing location codes can be difficult and error prone when companies have a lot
of suppliers. Teamcenter provides the following features to manage location codes:
• Associate users and groups to company locations.
• You can only view location codes that are associated with you or your group.
• Configure location codes to display as LOVs.
Unincorporated changes
An unincorporated change is a change that is approved but not incorporated in the
design of a product. The reasons can vary from reacting to a critical last minute
change identified on the factory floor to correcting a misspelling on a drawing or for
budget reasons deferring the change to a different financial quarter or program.
Using the unincorporated change feature in Teamcenter, you can:
• Mark a change as unincorporated.
• Incorporate changes partially.
• Fully incorporate previous partially incorporated changes.
• View unincorporated changes for an item or item revision.
• View unincorporated changes for a change notice.
For more information, see the Aerospace and Defense Solution Guide or the Change
Manager Guide.

Managing stock materials
The stock material functionality in Teamcenter allows you to manage stock materials
or raw materials by supporting the following features:
• Creating a library of stock materials.
• Creating stock materials.
• Making the stock material the preferred stock material of a program using the
Make From command
You can also add a standard part to a part using the Make From command.
• Assigning the stock material to a part along with the cut dimensions of the
stock material
• Querying stock materials
Managing work packages
A work package or package is typically any collection of CAD files and documentation
that an outsourcing partner requires to build, test, or maintain a component or
subassembly of a larger product.
A package serves as a revisable collection of product information and can be used in
a variety of contexts. A package’s contents may include information from different
team members like drawings, parts list, part geometry, work instructions (build) or
purchase order (buy), analysis, and test reports.
With work packages, you can:
• Create, revise, and edit work packages.
• Add Teamcenter objects to work packages through static and dynamic content
relationships.
• Start a workflow on a work package.

What’s New
Managing finishes
Finishes are part of the engineering definition of a part or product. Finishes are
employed to improve appearance, adhesion, corrosion resistance, tarnish resistance,
chemical resistance, wear resistance, removes burrs, and so on.
Finishes are defined once and used many times. Finishes can also be grouped and
reused as a set. When grouped in a set, you can define the order of the finishes. The
order of finishes is the one which defines the sequence in which the finishes are
executed, for example, clean, prime, paint.
These finishes can be combined into a finish group and applied to a part. The
finishes are consumed by manufacturing.
The finishes feature provides you with the ability to:
• Create a finish item.
• Create a finish group.
• Apply finish to an item or item revision.
• Apply finish to a part occurrence in Structure Manager using trace links.
Configuration audits
Configuration audits are conducted to verify that the product has achieved its
required features and performance and that its design is accurately documented.
This is achieved by:
• Inspecting documents and products.
• Reviewing processes and procedures.
Using the configuration audit functionality you can:

• Create different types of configuration audits like Functional Configuration
Audit (FCA), Physical Configuration Audit (PCA), and so on.
• Create an action item.
• Associate an action item with a configuration audit.
• View action items on an action item status dashboard.

Thin client support
The following Aerospace and Defense features are now supported in the thin client:
• Assigning an object to a project or program during item creation
• Displaying project or program data and preferred items in the project or program
pseudofolders
• Associating preferred standard parts to programs
• Removing preferred standard parts from programs
• Attaching a standard note to an item or item revision
• Attaching a custom note to an item or item revision
• Replacing standard note revision with another revision
• Validating whether a note is qualified for a technical document
• Viewing and editing a custom notes
• Displaying change notices in the User Settings dialog box and allowing users to
set that as the current change notice.
• Assigning company location to users and groups.
• Support for naming rule patterns for item IDs and revision IDs during object
creation.
• Support for conditional naming rules and revision naming rules.
• Support for validation of naming rules and revision rules.
For more information, see the Thin Client Interface Guide.

What’s New
Materials Management
The Materials Management application provides the following features:
• Import material and substance information from a third-party database into a
material library in the Teamcenter database.
• Export materials from Teamcenter.
• Create materials and substances.
• Classify materials using the classification feature.
• Assign substances to materials.
• Assign materials to parts.
• Run the default Materials Management queries.
• View the material and substance dashboard.
For more information, see the Materials Management Solution Guide.

Substance Compliance
The Teamcenter Substance Compliance solution is an environmental compliance
solution that enables companies to conform to environmental laws, regulations,
standards, and other requirements for their own parts and for the parts
manufactured or supplied from an external source.
The Substance Compliance application:
• Requests for material substance declaration from the suppliers in the IPC
1752-2 version 1.1 XML format.
Note Customer sites may set the SUBSCMPL_request_msd_mode
preference to send the material substance declaration in Microsoft Excel
format.
• Imports the material substance declaration sent by the supplier in the IPC
1752-2 version 1.1 XML format.
• Rejects or approves the material substance declaration imported through IPC

1752-2 version 1.1 documents.
• Requests the compliance checker to grade a part or BOM.
• Applies exemptions to compliance items with Fail or Unapproved Fail

compliance status.
• Views the substance compliance dashboard.
• Initiates compliance results validation.
These capabilities assume:

• The content for the rules, regulation, and exemptions are provided by PE
International.
• Teamcenter is not intended to be a material authoring or material life cycle

application.
• Only IPC 1752-2 version 1.1 XML documents are supported for export and
import.
For more information, see the Substance Compliance Solution Guide.
Performing integrations
Manufacturing Execution System Integration
A manufacturing execution system (MES) is designed to help companies more
effectively and efficiently execute manufacturing operations from the product order
through each step of the manufacturing process to its final point of delivery. Equally
important, an MES is a dynamic information system that is key to collaborative
manufacturing strategies by providing mission-critical information about production
activities to managers across an organization and its supply chain.

What’s New
A manufacturing execution system supports timely execution. Siemens offers a

tailor-made system to access all of real-time process information company-wide.
SIMATIC IT, Siemens MES, conforms to the ISA S95 standard, delivers multiple
capabilities, and enables optimum utilization with high production quality at lower
cost.
The new PLM–MES solution provided as part of Teamcenter 10.1 and certified
compatible versions of SIMATIC IT collects the bill of process, the bill of materials
to be consumed, and any relevant work instructions into a work package that is
released to the manufacturing execution system so that the MES has a work-plan
for that product without a need to re-author. The operator can use this information
to machine the desired product. If there is a problem in production that requires
engineering intervention, the planner can modify the contents of the work package
and send the changes to the MES. You can create a master execution plan containing
data relevant to multiple variants of the same product family (representing different
customer-orders) or you can create order-specific execution plans for execution by
You can use the following new features as part of preparing the manufacturing
execution plan in Teamcenter manufacturing that can be transferred accurately and
efficiently to the MES where it awaits execution when the order is issued:
• Tools®MES®Validate for MES to validate that the data conforms to the data
model expectations and constraints of the MES, in particular SIMATIC IT.
• Tools®MES®Release to MES to validate and then transfer the package to

After release, Teamcenter includes monitoring capabilities of the status of the

transfer transaction and the level of consumption in SIMATIC IT.
• Tools®MES®Load Last Released Execution Plan to retrieve the exact state of
the execution plan the last time it was released to the MES
• Tools®MES®Launch MES Web Page to view MES data in the embedded

browser
The PLM-MES solution provides visualization capabilities. A new feature allows

the planner to create hyperlinks between a text fragment in the textual work
instructions and a product view in visualization. Once transferred, the same
hyperlink is available to the operator in SIMATIC IT.
The PLM-MES solution is pre-configured for Teamcenter manufacturing
and SIMATIC IT software. You can customize the services in Teamcenter
manufacturing to run with other manufacturing execution systems, but this requires
customer-specific projects.
For more information, see the Manufacturing Execution System Integration Guide.

Chapter
4 Teamcenter 10.1 release notes
Release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Teamcenter 10.1 product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Teamcenter Rapid Start release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Installation and upgrade release notes . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Installation and upgrade release notes . . . . . . . . . . . . . . . . . . . . . . . 4-12
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
General installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Lifecycle Visualization installation . . . . . . . . . . . . . . . . . . . . . . . 4-16
Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
General upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Access Manager upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Classification upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Content Management upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Usage release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Usage release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
4th Generation Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Automotive Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Audit Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Briefcase Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Change Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Client for Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Data Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Document Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Extensions for Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Global Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
GM Overlay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
MATLAB integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Maintenance, Repair, and Overhaul . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Manufacturing Process Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Mechatronics Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
Multi-Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Multi-Structure Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88

PLM XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
Query Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-91
Repeatable Digital Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
Report Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
Resource Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97
Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97
Schedule Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98
Specification Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100
Structure Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-101
Systems Engineering and Requirements Management . . . . . . . . . . . 4-111
Vendor management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-140
Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-141
Visualization Illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-142
Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-143
Configuration release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-145
Configuration release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-145
Command Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-145
Administration release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-146
Administration release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-146
General administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-146
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-148
Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-149
Site Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-151
Subscription Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-152
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-152
Customization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154
Customization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154
Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-155
Teamcenter interfaces release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-159
Teamcenter interfaces release notes . . . . . . . . . . . . . . . . . . . . . . . . 4-159
Rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-159
Thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-168
Internationalization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-172
Third-party release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-180
Third-party release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-180
IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-180
Platform-specific release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-180
Platform-specific release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-180
Hewlett-Packard HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-180
IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-183
Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184
Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-186
SUSE Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-187
UNIX platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-188
Apple Macintosh MacOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-190
Documentation release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-192

Teamcenter 10.1 documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-192
Teamcenter 10.1 online help collection . . . . . . . . . . . . . . . . . . . . . . . . . 4-192
Application Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-193
Audit Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-203
Business Modeler IDE Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204

Classification Administration Guide . . . . . . . . . . . . . . . . . .... . . . . . . 4-206
Client Customization Programmer’s Guide . . . . . . . . . . . . .... . . . . . . 4-207
Data Exchange Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-208
Dimensional Planning and Validation Administration Guide ... . . . . . . 4-209
Dispatcher Server Installation Guide . . . . . . . . . . . . . . . . .... . . . . . . 4-210
Getting Started with Document Management . . . . . . . . . . .... . . . . . . 4-210
Getting Started with Manufacturing . . . . . . . . . . . . . . . . . .... . . . . . . 4-211
Getting Started with Systems Engineering . . . . . . . . . . . . .... . . . . . . 4-213
Getting Started with Teamcenter . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-213
Getting Started with Workflow . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-213
Global Services Customization Guide . . . . . . . . . . . . . . . . .... . . . . . . 4-215
Installation on UNIX and Linux Servers Guide . . . . . . . . . .... . . . . . . 4-216
Installation on Windows Servers Guide . . . . . . . . . . . . . . . .... . . . . . . 4-217
Lifecycle Visualization Integration Guide . . . . . . . . . . . . . .... . . . . . . 4-218
Localization Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-218
Materials Management Solution Guide . . . . . . . . . . . . . . . .... . . . . . . 4-218
Multi-Site Collaboration Guide . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-221
Organization Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-224
Platform Designer Guide . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-224
PLM XML/TC XML Export Import Administration Guide . . .... . . . . . . 4-224
Preferences and Environment Variables Reference . . . . . . . .... . . . . . . 4-225
DISPLAY_Param_In_NotesText . . . . . . . . . . . . . . . . . .... . . . . . . 4-234
Mail_internal_mail_activated . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-235
Mail_send_file_attachments_activated . . . . . . . . . . . . .... . . . . . . 4-236
NX_Supports_VISSC . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-237
ScheduleTaskClassNameToCreate . . . . . . . . . . . . . . . .... . . . . . . 4-238
WEB_Applications_List . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-239
WEB_Nav_Items_List . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-240
Word_Export_TcTypes . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-241
Rich Client Interface Guide . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-242
Schedule Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-243
Service Planner Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-246
Site Consolidation Guide . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-246
Structure Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-247
Substance Compliance Solution Guide . . . . . . . . . . . . . . . .... . . . . . . 4-248
System Administration Guide . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-249
Systems Engineering Guide . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-250
Teamcenter Environment Manager Help . . . . . . . . . . . . . . .... . . . . . . 4-253
Teamcenter Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-254
Thin Client Interface Guide . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-254
Transition Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-254
Upgrade Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-255
Validation Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-256
TC_VALIDATION_send_envelope_for_override . . . . . . .... . . . . . . 4-257
Volume Management Guide . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-257
Utilities Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-258
build_fts_index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-260
cleanup_userinbox . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-266
Web Application Deployment Guide . . . . . . . . . . . . . . . . . .... . . . . . . 4-267
What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . 4-267

Chapter
4 Teamcenter 10.1 release notes
Release notes
Release notes are comprised of product release notes (known problems in the software
and workarounds) and documentation release notes (corrections to documentation).
Product release notes
Teamcenter 10.1 product release notes

The following notes pertain to Teamcenter 10.1.
Teamcenter Rapid Start release notes

The following notes pertain to Teamcenter Rapid Start.
• TC_MFK_DEFAULT_DOMAIN preference value required for Teamcenter
Rapid Start NX
Your NX integration does not work if the TC_MFK_DEFAULT_DOMAIN
preference is missing.
How to work around or avoid
1. Close the rich client and TAO.
2. Open the Teamcenter Rapid Start command prompt.
3. Run the following command:

preferences_manager -u=infodba -p=password -g=dba
-mode=import -scope=SITE -preference=TC_MFK_DEFAULT_DOMAIN
-values="Item" -action=OVERRIDE
4. Close the command prompt.
5. Verify your NX integration is working.

Chapter 4 Teamcenter 10.1 release notes
• Teamcenter Client for Office issues with JT files

(First published Teamcenter Rapid Start 9.1)
You cannot view JT files embedded in a Microsoft Office document without
accepting the JT2Go license agreement.
Before embedding a JT file in a Microsoft Office document, start the JT2Go
application and accept the license agreement.
Note You only need to perform this workaround once.
• Issues viewing Solid Edge data

You may encounter issues when viewing Solid Edge part and assembly data.
Solid Edge parts and assemblies cannot be viewed in the iSeries viewer launched
from the thin client. In addition, Solid Edge parts and assemblies cannot
be viewed when opened in a visualization application in the rich client (for
example, double-clicking a dataset). You can, however, view Solid Edge parts
and assemblies in the Viewer tab in the rich client.
Use JT data instead of Solid Edge parts and assemblies for viewing purposes.

Teamcenter 10.1 release notes
• PSE Edit in Place functionality replaced by Export to Live Excel

Teamcenter Rapid Start PSE Edit in Place functionality is replaced by the
Export to Live Excel feature in Structure Manager. To use this new functionality,
you must export Item Master/ItemRevMaster attributes from the Structure
Manager to Microsoft Excel.
Export Item Master/ItemRevMaster attributes from the Structure Manager
to Microsoft Excel as follows:
1. Open Structure Manager.
2. Ensure that the required columns are displayed.

To add columns, right-click the column header and choose Insert Column(s).
From the Available Columns list, select the required columns and click the +
button. Click Apply and then click Close.
3. Select the required BOM line and choose Tools®Export®Objects To Excel.

The Export To Excel dialog box appears.
4. Select Live integration with Excel (Interactive).
5. In the Output Template section, select Export All visible Columns.
6. Click OK.
All of the displayed columns are exported to Microsoft Excel.

• Thin client issues with browsers other than Microsoft Internet Explorer
When attempting to install Lifecycle Visualization, FCC, or the Microsoft Office
add-in in the thin client, you may encounter issues if you are using a browser
other than Microsoft Internet Explorer. Other browsers have limitations that
prevent the installations from functioning properly.
Access the thin client using Microsoft Internet Explorer.
• Problem viewing data from thin client for base level licenses
After installing Lifecycle Visualization from the thin client, you cannot view
data (for base-level licenses only). Clicking the View link next to the dataset
fails to open the viewer.
When installing Lifecycle Visualization from the thin client, if you see a Program
compatibility assistant dialog box, click Reinstall using recommended settings.
After the installation is complete, start Lifecycle
Visualization by double-clicking VisView.exe in C:\Program
Files\Siemens\Teamcenter8.3\Visualization\Products\Base
(for 32-bit systems) or C:\Program Files
(x86)\Siemens\Teamcenter8.3\Visualization\Products\Base (for 64-bit
systems). This only needs to be performed once per computer.
• Problem with Schedule Manager workflows and time sheet approvals

Schedule Manager workflows and time sheet approvals do not work properly.
Install and configure the schmgrtrans translator.
1. Install a four-tier tcserver and pool manager with Dispatcher Server, the
dispatcher client, and the DispatcherClient plug-in for the rich client using
the appropriate installation kits.
2. Copy the schmgrtrans translator folder from install_kits\tc_cdrom\tc to

TC_ROOT.
This step is not necessary if schmgrtrans is selected
during the server installation. If installed, the path is
C:\PROGRA~1\Siemens\Teamcenter9\schmgrtrans.

3. In the DispatcherRoot\Module\conf\translator.xml file, change the

isactive entry for schmgrtrans to true. For example:
SchMgrTrans provider=”SIEMENS” service=”schmgrtrans” isactive=”true”
For Teamcenter Rapid Start, the path is C:\Program

Files\Siemens\Teamcenter9\ets\Module\conf.
4. In the DispatcherRoot\Module\conf\translator.xml file, change the

directory path for schmgrtrans.bat. For example:
TransExecutable dir=”C:/PROGRA~1/Siemens/Teamcenter9/schmgrtrans”
name=”schmgrtrans.bat”/
5. In the schmgrtrans.bat file, set the TC_ROOT environment variable and

add the JAVA_HOME environment variable using proper values.
These environment variables may already be set as a result of the
installation.
6. Extract the axis.zip file from

install_kits\tc_cdrom\additional_applications\dispatcher\axis
to DispatcherRoot\DispatcherClient\lib.
Files\Siemens\Teamcenter9\ets\DispatcherClient\lib.
7. In the DispatcherClient.config file, uncomment the Axis.Port

(port_number) line and change the value for the port number. The port
number can be any number that is not already used.
Files\Siemens\Teamcenter9\ets\DispatcherClient\conf.
8. Add the SyncDispatcherClientUrl site preference and set it to the

following value:
http://hostNameWhereDispatcherClientIsRunning:port_number/axis2/services/
AxisDispatcherClient.AxisDispatcherClientHttpSoap12Endpoint
9. Verify that the scheduler and module services are running.
10. Open a Teamcenter Rapid Start command prompt and type the following:
DispatcherRoot\DispatcherClient\bin location start
runDispatcherClient.bat file
11. Verify that http://host_name:port_number/axis2/services/

AxisDispatcherClient.AxisDispatcherClientHttpSoap12Endpoint is
available and shows submit as one of the available operations.
12. Log on to the rich client and test the workflow task update and trigger.

• Development and Production Release workflows do not work on

Traditional Chinese servers
Development and Production Release workflows do not work on Traditional
Chinese (CHT/TW) servers. There is an issue with template files.
Contact GTAC for details.
• No ACLs defined for Schedule Manager object in Access Manager

There are several ACLs that are required to define access rules for Schedule
Manager. These ACLs are not defined by default and must be configured
manually.
1. Log on to Teamcenter as a DBA user.
2. Open the Access Manager application.
3. In the ACL tree structure, navigate to Has Class(POM_Application_Object)

-> Working.
4. Select Has Class (Item).
5. Define a new ACL as follows:
For details on adding ACLs, refer to the Access Manager Guide.
6. In the ACL tree structure, navigate to Has Class(POM_Application_Object)

-> Working.
7. Select Has Class (Form).
8. Define three new ACLs as follows:

9. Restart Teamcenter.

• Some workflow handlers unavailable after upgrade

After upgrading from Teamcenter Rapid Start to Teamcenter, the
TCRS-Create-Print-Requests and TCRS-setstatus-EO-folder workflow
handlers are unavailable.
Do not use the TCRS-Create-Print-Requests handler. The Print workflow
process template must be removed from the Teamcenter database as it is not
supported.
If you have an Engineering_Order workflow template that uses the
TCRS-setstatus-EO-folder handler, perform the following steps to replace the
TCRS-setstatus-EO-folder handler in Teamcenter:
1. Create an obsolescence workflow as follows:

a. Create a new workflow template with the name Quick Obsolescence.
b. Add an Add Status Task task into the workflow, and add two handlers as
shown.

2. In the Engineering_Order workflow, remove the

TCRS-setstatus-EO-folder handler on the Start action of the in_Approval
task.
3. Place an EPM-create-sub-process handler on the Complete action of the

in_Approval task using the arguments shown.

• Missing ACLs
Teamcenter Rapid Start is missing the following markup dataset-related ACLs:
o Markup Official
o Private Markup
o General Markup

Manually create the missing ACLs using the following procedure.
1. Open Teamcenter Rapid Start.
2. Log on as a DBA user.
3. Open the Access Manager application.
4. In the ACL tree structure, expand Has Class( POM_application_object )

–>Working and select Has Class( Dataset ).
5. Create the first ACL as follows, and then click the Add button.
6. Create the next ACL as follows, and then click the Add button.

7. Create the next ACL as follows, and then click the Add button.
The three new ACLs now appear in the tree structure.

Installation and upgrade release notes
Installation and upgrade release notes
The following release notes pertain to installation and upgrade of Teamcenter.
Installation
Installation
The following release notes pertain to the installation of Teamcenter.
General installation
The following general release notes pertain to the installation of Teamcenter.

• Avoid Oracle 11g default encoding for Japanese SJIS
Oracle 11 offers a new default encoding for Japanese SJIS with identifier
JA16SJISTILDE. Currently, this is not recognized in Teamcenter; Siemens
PLM Software recommends using JA16SJIS.
When installing the Oracle database for Japanese SJIS, use the JA16SJIS
database character set identifier and not the default JA16SJISTILDE identifier.
• Use TEM to install TCCS on Windows 8 and Windows Server 2012

Installation of Teamcenter client communication system (TCCS) fails on
Windows 8 and Windows Server 2012 if you attempt to install TCCS using the
stand-alone installation program, tccsinst.exe.
The 64-bit version of the stand-alone TCCS installer fails with a message that
begins with the following text:
This application has Unexpectedly Quit.
The 32-bit version of the stand-alone TCCS installer fails with the following
message:
Installer User Interface Mode Not Supported.

To install TCCS on Windows 8 or Windows Server 2012, use Teamcenter
Environment Manager (TEM).

• Teamcenter does not support WinZip

Siemens PLM Software does not support use of WinZip for extracting Teamcenter
files or for any Teamcenter customization or archiving actions due to the
scalability limitations of WinZip. Teamcenter will continue to produce and
support such use cases using files in the ZIP format.
Use another utility that supports ZIP format, for example, 7-Zip.
• POM_TIMESTAMP table blocking sessions

There are performance issues with saving/deleting instances serializing due to
contention with cleanupof the POM_TIMESTAMP table during logout.
Cleanup is no longer performed during logout therefore avoiding contention.
Cleanup is still performed using the clearlocks utility so as to offer control
over scheduling.
• Visual C++ 2008 not found after using the Over-the-Web Installer
Installing the rich client using the Over-the-Web Installer completes successfully,
but the following message is displayed:
Microsoft Visual C++ Redistributable is not found.
Please make sure it is installed before using Teamcenter or errors may occur.

The fix is in patch 8.3.0.1. After patching the rich client installed using the
Over-the-Web Installer, the administrator must recopy the otwweb folder to the
Web server hosting the installation.

• Rich Client Lite Edition is unavailable

When you install the Rich Client Lite Edition, the full Teamcenter rich client
is installed.
1. After the rich client installation, remove the following plug-in JAR files from
the Teamcenter-installation-root/portal/plugins directory:
com.teamcenter.rac.cme.cmereport_8000.0.0
com.teamcenter.rac.padpdf_8000.0.0
jfreechart
com.teamcenter.rac.accessmanager_8000.0.0
com.teamcenter.rac.aif.registryeditor_8000.0.0
com.teamcenter.rac.appearanceconfiguration_8000.0.0
com.teamcenter.rac.architecturemodeler_8000.0.0
com.teamcenter.rac.auditmanager_8000.0.0
com.teamcenter.rac.authorization_8000.0.0
com.teamcenter.rac.cae.ase_8000.0.0
com.teamcenter.rac.caese_8000.0.0
com.teamcenter.rac.caese_dm_8000.0.0
com.teamcenter.rac.charts_8000.0.0
com.teamcenter.rac.classification.icadmin_8000.0.0
com.teamcenter.rac.classification.icm_8000.0.0
com.teamcenter.rac.cme.collaborationcontext_8000.0.0
com.teamcenter.rac.cme.fse_8000.0.0
com.teamcenter.rac.cme.mpp_8000.0.0
com.teamcenter.rac.cme.mrm_8000.0.0
com.teamcenter.rac.cme.pmp_8000.0.0
com.teamcenter.rac.commands.report.reportdesigner_8000.0.0
com.teamcenter.rac.commandsuppression_8000.0.0
com.teamcenter.rac.crf_8000.0.0
com.teamcenter.rac.databaseutilities_8000.0.0
com.teamcenter.rac.designcontext_8000.0.0
com.teamcenter.rac.dpv_8000.0.0
com.teamcenter.rac.ecmanagement_8000.0.0
com.teamcenter.rac.edalib_8000.0.0
com.teamcenter.rac.eintegrator.eintadmin_8000.0.0
com.teamcenter.rac.organization_8000.0.0
com.teamcenter.rac.plmxmlexportimportadministration
com.teamcenter.rac.project_8000.0.0
com.teamcenter.rac.pse_8000.0.0
com.teamcenter.rac.querybuilder_8000.0.0
com.teamcneter.rac.requirementsmanager.win.embeddedword_8000.0.0
com.teamcenter.rac.requirementsmanager_8000.0.0
com.teamcenter.rac.schedule_8000.0.0
com.teamcenter.rac.setupwizard_8000.0.0
com.teamcenter.rac.smb_8000.0.0
com.teamcenter.rac.subscriptionmonitor_8000.0.0
com.teamcenter.rac.tctdv_8000.0.0
com.teamcenter.rac.tdv_8000.0.0
com.teamcenter.rac.tracelinks.ui_8000.0.0
com.teamcenter.rac.ui.advanced_8000.0.0
com.teamcenter.rac.validation_8000.0.0
com.teamcenter.rac.vis_8000.0.0
com.teamcenter.rac.vm_8000.0.0
com.teamcenter.rac.workflow.processdesigner_8000.0.0
com.teamcenter.rac.workflow.processviewer_8000.0.0
PLMContainerProxy
scheduling_rac_interface_8000.0.0
2. Do not install the following rich client add-ons:
GM Overlay for Rich Client

SCM ClearCase for Rich Client
Embedded Software Manager for Rich Client
Rich Client Lite Edition does not support these add-ons.
3. Delete the following run-time configuration before you run the Rich Client
Lite Edition:
C:\Documents and Settings\user-id\Teamcenter\RAC\8000.0.0

• Users after first logon get error for some actions

When Teamcenter is installed in PER_CLIENT mode with a two-tier
configuration as a common installation for more than one operating system user,
after the first user has logged on, subsequent users get a Permission Denied
exception when they perform some actions.
Currently, there is no workaround for this problem.
Note PER_CLIENT activation mode is deprecated in Teamcenter 10.1.
For more information, see PER_CLIENT activation mode in two-tier rich
client is deprecated.
DB2 installation
The following release notes pertain to IBM DB2 installation.

• Teamcenter servers for DB2 on Windows require DB2 ODBC driver
installed as prerequisite
To configure TC servers for DB2 on Windows requires the DB2 ODBC driver (in
a kit) to be installed ahead of the TEM installation of Teamcenter. The ODBC
installer requires administrator privilege.
Install the DB2 ODBC driver with administrator privileges. For sites with
large numbers of Windows machines requiring TC servers (two-tier or four-tier
servers), use installation distribution tools like Microsoft’s SMS. For more
information about how to install and configure Teamcenter on DB2, see the IBM
DB2 Installation and Configuration for Teamcenter manual.

Lifecycle Visualization installation

The following release notes pertain to installation and upgrade of Lifecycle
Visualization.
• FCC warning message in Lifecycle Visualization viewer
When you run the viewer with the FMS client cache (FCC), Lifecycle
Visualization may display the following warning in the console:
***** WARNING: The FCC Client Proxy shared library is not installed. *****
***** Reverting to self-proxying mode. *****
***** (Installing an FMS client update will silence this warning.) *****

No immediate action is required. The FCC will function normally but not with
optimal performance. This warning message can be eliminated by installing an
updated FCC on the client host.
• Embedded Lifecycle Visualization must be run in like environment

32-bit Lifecycle Visualization applications can be run only within 32-bit Web
browser versions on 32-bit operating systems. Similarly, 64-bit Lifecycle
Visualization applications must be run only within 64-bit Web browsers on 64-bit
operating systems. Running 32-bit Lifecycle Visualization applications in a
64-bit environment is not supported, nor is running 64-bit Lifecycle Visualization
applications in a 32-bit environment.
This applies to the embedded Lifecycle Visualization viewer in the thin client
and all Lifecycle Visualization applications.
Ensure that you use only supported configurations for Lifecycle Visualization,
that is, 32-bit Lifecycle Visualization with 32-bit Web browsers and operating
systems, and 64-bit Lifecycle Visualization with 64-bit Web browsers and
operating systems.
• Over-the-Web Installer nonroot user installation of Lifecycle

Visualization not interoperable with NX
Lifecycle Visualization places files in a root folder used by NX to determine
interoperability. The folder usually needs to be created by a user with rights to
the root folder. However, the Over-the-Web Installer does not require users to
have access rights to the root. Although the warning is written to the Lifecycle
Visualization install.log file, no warning is displayed by the Over-the-Web
Installer.
Either run the Over-the-Web Installer as a user with rights to the root, or create
the ugs directory before starting the Over-the-Web Installer and give read and
write permissions on the ugs directory to the user running the Over-the-Web
Installer.

Upgrade
Upgrade
Following are release notes pertaining to Teamcenter upgrade.
General upgrade
Following are general release notes pertaining to upgrading from a previous version
of Teamcenter.
• Resolving Oracle parallel query error (ORA-12801)
If you use Oracle, you may need to rebuild Oracle tables and indexes during
Teamcenter upgrade. Typically, this is done using Oracle parallel options
for efficiency. However, in Teamcenter 10.1, the parallel options are reset to
noparallel (degree 1) to ensure they reflect a new installation and do not cause
the Oracle optimizer to employ parallelism.
Some queries can result in an error message similar to the following:
ORA-12801, "error signaled in parallel query server ..."
This error is often accompanied by a secondary message:

ORA-1460 unimplemented or unreasonable conversion requested
When certifying, you should not run the default behavior with parallel execution
features. If the database administrator does not explicitly apply parallel options
to improve an optimizer plan, you should remove existing parallel settings.
Verify with your database administrator whether this is needed.
Find remaining indexes in this state by typing the following SQL command:
select index_name from user_indexes where degree > 1
Set the resulting indexes to noparallel mode:

alter index name noparallel;
To perform this on a set of indexes, create the following script:

select ’alter index ’ || index_name || ’ no parallel;’ from user_indexes where degree
For tables, find non-default cases by typing the following SQL command:
select table_name from user_tables where degree > 1;
Fix the resulting tables by typing the following command:

alter table name noparallel;
To perform this on a set of tables, create the following script:

select ’alter table ’ || table_name || ’ no parallel;’ from user_table where degree >

• Duplicate query names cause upgrade to fail when upgrading the

database
In Teamcenter 10.1, the bmide_schema command requires unique names
for query name indexes, so upgrading to Teamcenter 10.1 fails if the existing
database contains duplicate query names. The Query Builder application began
enforcing unique query names at Teamcenter 8, so this problem affects upgrades
from versions earlier than Teamcenter 8.
Before you begin upgrading to Teamcenter 10.1, you must make sure your
existing database does not contain duplicate query names. If your database
contains duplicate query names, you can manually remove duplicate queries or
rename duplicate queries before you begin upgrading.
• Notification details are blank for subscriptions upgraded from

pre-Teamcenter 8.1 release
If you upgrade to Teamcenter 10.1 from a version earlier than Teamcenter
8.1, the notification details page in the Subscription and Notification wizard
shows blank values for Subject, Message and Properties fields when modifying
existing subscriptions. Also, the Finish button is disabled.
When modifying the upgraded subscriptions, you must manually add a value
for Subject and, if required, values for Message and Properties to activate the
Finish button on the Subscription and Notification wizard.
• Missing last saved date case cause problems with build_fts_index utility
during upgrade
If your database was upgraded from Teamcenter 2007 and did not contain the
last saved date, the build_fts_index utility writes the incorrect date in the
lastsaveddate.txt file. This can cause the utility to loop indefinitely on the
first batch.
Remove the lastsaveddate.txt file and batch operation. This causes the utility
to start from the beginning. You can use a query to start from a specific date.

• Values of attributeType, arrayLength, isArray, and isTransient

attributes cannot be changed
Beginning in Teamcenter 9.1, changes to the values of the attributes
attributeType, arrayLength, isArray and isTransient cause the upgrade to
fail. In earlier versions, these changes were ignored.
If a test upgrade fails because of this change, the values of the attributes in the
custom template must be modified with the ones in the database. After the
custom template is corrected, there should be no issues during the production
upgrade.
If the test upgrade was not performed and this issue is noticed during the
production upgrade, the values of these attributes in the custom template,
TC_DATA/model.xml, and TC_DATA/delta.xml files must be modified to
match the values in the database. After these changes are completed, the
manage_model_files utility must be run to upload these changes to the
datasets.
• Outdated files in TC_USER_MSG_DIR directory cause upgrade problems

Outdated files in the directory specified in the TC_USER_MSG_DIR
environment variable can cause serious issues including problems during
Teamcenter upgrade.
Local copies of Teamcenter text server are kept in a directory referenced by the
TC_USER_MSG_DIR environment variable.
Before you begin Teamcenter upgrade, you must refresh (merge) local copies
of the files in the directory specified in TC_USER_MSG_DIR to reflect the
changes in the latest version of Teamcenter.
For more information, see the Localization Guide.

• Import of certain objects to previous Teamcenter version may cause

data corruption
The length of the following fields of following objects is increased from 32 to 128.
Object Field
ADSPart Source Document Id
ADSDrawing Source Document Id
ADSDesign Source Document Id
Data Requirement Item Contract Reference
If you try to import these objects that have the fields shown above to a release
prior to Teamcenter 9.1, and these fields have lengths greater than 32, your data
may become corrupt.
If you intend to import these objects to a release prior to Teamcenter 9.1, keep
the lengths of these fields less than or equal to 32 because these fields represent
item IDs of certain referred objects. Also, keep the lengths of the item IDs of
these objects less than or equal to 32.

• Upgrade failure logs

In case of upgrade failures, customers may not be familiar with the need to
collect upgrade and installation logs to assist in resolving the upgrade problems.
Use the collect_install_upgrade_logs utility to collect installation and upgrade
error logs in case of failure. This in turn helps rapid resolution of upgrade issues.
In case of an upgrade failure, run the collect_install_upgrade_logs utility
before you contact GTAC or file an IR (incident report). This utility collects
installation and upgrade logs into a single ZIP archive.
Run the utility as follows based on your platform:
o Windows systems
Teamcenter-software-distribution-image\additional_applications\
upgradeutilities\collect_install_upgrade_logs.bat
o UNIX systems
Teamcenter-software-distribution-image/additional_applications/
upgradeutilities/collect_install_upgrade_logs.sh
When you run the collect_install_upgrade_logs utility, the utility prompts

you for the following information:
o Path to the new Teamcenter root directory (TC_ROOT)
o Path to the new Teamcenter data directory (TC_DATA)
o Path to the output directory for the utility (where to store the collected log
files)
The utility collects the required installation and upgrade logs into an archive
named install_upgrade_logs_number.zip, where number is random unique
number, and places this archive in the output directory you specify. Upload the
generated ZIP file to an IR (incident report).
• cae_geometry_fix utility fails during upgrade

The cae_geometry_fix utility is run automatically during upgrade to retype
all existing CAEGeometry datasets to CAEGeom and then install the
CAEGeometry item class and type. The installation of the CAEGeometry
item type fails if any business rules reference the CAEGeometry dataset type
prior to the upgrade attempt.


Prior to initiating an upgrade to Teamcenter 10.1 from any version of
Engineering Process Management, follow these steps:
1. Capture the existing business rule definitions:
import_export_business_rules –u=infodba –p=password
-g=dba –action=export –rule=HideTypeRule –file=output-xml-file
2. Make a copy of the output XML file from the previous step. Modify the file
by removing all tags in the file that contain the CAEGeometry string and
save the modified XML file. Be careful when performing this step. After
the modifications are complete, compare the modified file to the original to
ensure that only the expected differences exist. There is no need to continue
with this workaround if there were no instances of CAEGeometry in the
output XML file from the previous step.
3. Remove the rules from the database:

-g=dba –action=delete –rule=HideTypeRule
4. Reload the rules except for those referring to CAEGeometry:

-g=dba –action=import –merge_add –rule=HideTypeRule
–file=modified-xml-file
5. Regenerate the schema file using:

install –regen_schema_file infodba password dba
After the upgrade to Teamcenter 10.1, the rules can be re-created using standard
Business Modeler IDE functionality to create business rules.
• Synchronize all data directories with the latest templates

If your Teamcenter environment has more than one data directory installation
referring to the same Teamcenter database, you must synchronize all data
directories with the templates. This ensures the clips rules file, the PLM XML
schema file, and .des files are all regenerated in the data directories any time
a template is installed or updated in the database.
For example, if you have a Teamcenter database installed with a single data
directory and you create additional data directories to connect to the same
database, after the creation of additional data directories any future template
install or update to the database should ensure all data directories are
synchronized.
Follow these steps for every data directory installation any time a template is
installed or updated in the database from any of the multiple data directory
installations. In this example, the data directories are data1 and data2. Your
templates in the database were changed in data1 and you must synchronize
data2.

1. Launch Teamcenter Environment Manager in maintenance mode.
2. Select the configuration where you created the data2 directory.
3. If you made a template installation from data1, do the same in data2

by selecting Add/Remove features. Because the template was already
installed from a different data directory, data1, the template installation
from data2 directory does not update the database but only the files in the
data2 directory.
4. If you made a template update from data1, do the same in data2 by

selecting Rebuild/Update the database. Because the template was already
updated in the database from a different data directory,data1, the template
update from data2 directory does not update the database but only the files
in the data2 directory.
5. If you have additional data directories, repeat steps 1 to 4.
• Database upgrade may fail at tcxml_import step when importing scope

rules (TC_DATA/defaultTransfermodes.xml)
When upgrading to Teamcenter 9.1, if the GMS_tcxml_string_separator
preference is set to something other than a comma (default value), the scope
rules import and upgrade may fail. This preference is used to specify a separator
for strings in TC XML import. For default scope rules .xml files, the separator
should be a comma.
Before starting the upgrade to Teamcenter 9.1, check to see if the
GMS_tcxml_string_separator preference exists in the database. If it does,
delete it temporarily. After the upgrade completes, you can reset the preference.

Access Manager upgrade
The following release notes pertain to Access Manager upgrades.

• New rule must be added manually when upgrading existing databases
If you are upgrading an existing database, you must manually add a required
rule to support the new sequences feature and object content restoration if you
cancel a checkout. If you are installing a new database, this rule is automatically
created. If you already added the rule to Teamcenter 2007, you do not have to
add it again.
In Access Manager, add the following rule to the tree:
1. Select the Has Class (POM_object) root node.
2. Create a new Has Class (WorkspaceObject) condition.
3. Move the new condition under Has Class (POM_object)→System Objects.
4. Select the new condition.
5. Create an InactiveSequence (true) condition in an Inactive Sequence access

control list (ACL). In the ACL, remove all access privileges except Read and
Copy for World. The Read and Copy privileges must remain blank.
Classification upgrade
The following release note pertains to the upgrade of the Classification application.
• Hierarchy root class names retained after upgrade
After upgrading a database from Engineering Process Management,
Classification retains the customized or legacy root class names in the hierarchy
tree. If required, you can change these names manually. For example, you can
change legacy root node names to their new form as follows:
iMAN Classification Root→SAM Classification Root

in-CLASS Classification Root→Classification Root
Note This action is optional. Classification continues to work correctly if you
do not rename these nodes.

Content Management upgrade
The following release note pertains to the upgrade of the Content Management
application.
• Remove old Content Management saved queries
When you upgrade Content Management to Teamcenter 10.1, several saved
queries still exist that are no longer needed.
If S1000D 4.0 is installed, use Query Builder to remove all saved queries that
start with DC_ and Civ0.
• Pre-upgrade step for DITA

The DITA Composite and DITA Map Editable publication types must be changed
to topic types before you upgrade from Teamcenter 8.n to Teamcenter 10.1.
In Teamcenter 9.0, the DITA Composite and DITA Map Editable publication
types were changed to topic types. If you are upgrading from Teamcenter 8.n
to Teamcenter 10.1, you must manually create two new topic types to replace
these two publication types.
1. In the Content Management Administration view, query for publication

types.
2. In the list returned, locate DITA Composite and DITA Map Editable.
3. Drag these two publication types to your workspace.
4. Perform the following steps on each of these two publication types:

a. Select the publication type.
b. In the item information, you see the attributes for the publication type.
c. Record the values for all of the attributes. You need these when you
create a new topic type.
d. Create a new topic type with the same values as the publication type.
Make sure the Name value for the topic type is exactly the same as the
name of the publication type. This is very important.

e. Right-click the publication type and choose Expand→all left to right.

The system displays all the items related to the publication type.
f. For each of the five groups below the publication type, select the items
and drag them to the new topic type. These groups include the following:
o compose modified by Policy
o has Schema
o has Topic Type
o has XML Attribute Mapping
o has stylesheet
This step results in the same items being related to the new topic type.
5. After you create the two new topic types, delete the DITA Composite and
DITA Map Editable publication types.
6. Search for the DITA OOTB topic type group.
7. Drag the new DITA Composite and DITA Map Editable topic types to this
topic type group.
8. Proceed with Teamcenter upgrade. After the upgrade, your DITA Composite
and DITA Map Editable topics will use the new topic types you created.
• Manual upgrade of Content Management DITA and content references

Teamcenter 9.1 adds a naming rule to Content Management DITA objects so
their item_id values all begin with X. This was done because DITA requires that
document IDs begin with a letter. However, DITA objects created in Teamcenter
8.n versions do not have this letter prefix.
Also, content references in Teamcenter 9.n now contain the file extension that is
specified on the topic type. Having the file extension in the content reference
ensures the exported content references have the correct file extensions.
However, content references in Teamcenter 8.n versions only contain the
item_id in the document. They must be run through an XSLT script to add
the correct extension. This is no longer required in Teamcenter 9.1. Therefore,
existing Teamcenter 8.n documents with content references do not have the file
extension in them after upgrading to Teamcenter 9.1.


A new utility, contmgmt_upgrade_8x, is added to Teamcenter 9.1. You must
run this utility after you upgrade your database to Teamcenter 9.1. You must
also run it after the manual Content Management migration steps are finished.
For more information about manual migration steps, see Content Management
Administration®Migrating Content Management data in the Content
Management Guide.
This utility adds a prefix to DITA object item_id values and updates all the
content references with the correct extensions.
For more information about this utility, see the Utilities Reference.
• Cancel checkout of topics in Content Management fails if

TcCheckoutReserveOnly preference is not changed in systems
upgraded from Teamcenter 8.3
In Teamcenter 8.3, the TcCheckoutReserverOnly preference was recommended
for Content Management classes due to performance reasons during the
checkout of topics. In Teamcenter 10.1, if this preferences is set, users are not
able to cancel checkout on Content Management objects that are checked out.
This does not affect checking in or checking out of these objects.
If you do not want this behavior, you must remove all Content Management
classes from the TcCheckoutReserverOnly preference setting. Removing this
preference may still cause an impact on performance, but the impact is much
smaller compared to its impact in Teamcenter 8.3 when checking out large
publication structures.

Usage release notes
Usage release notes
The following release notes pertain to the usage of Teamcenter.
The following release notes pertain to 4th Generation Design.

• Internal error displayed when allocating an already allocated variant
option
When allocating an option that is already allocated, an internal error message
is displayed.
The error message will be reworded in a future version of Teamcenter to indicate
no data corruption occurred.
• Saved query for partition templates

There is no saved query for partition templates.
As an administrator, you can define a saved query for partition templates using
the Query Builder application. Use Ptn0PartitionTemplate as the class name
for which you define the query.
• Assign Collaborative ID button is not consistent with general

Teamcenter behavior
The Assign Collaborative ID button remains available after the ID is assigned,
which is not consistent with general Teamcenter behavior.
This behavior will be made consistent with general Teamcenter behavior in a
future version of Teamcenter.
• Refresh required to review a design element after a revision

When a design element is revised a second time, it is removed from the partition.
A refresh is required to view the revised design element within the partition.
There is a refresh issue in the Content Explorer. This will be fixed in a future

• Opening a workset BOM view revision in Structure Manager thin client

displays an error message
In the thin client, double-clicking a BOM view revision (BVR) of a workset opens
the workset BVR in Structure Manager.
A workset BVR has subsets that are different from PSOccurrence business
objects. In general, opening worksets in Structure Manager are not supported. A
more descriptive error message will be displayed in future version of Teamcenter.
• Icon for Partition Membership

Partition Membership is a hidden object from a user perspective. However, if
you extend this object and make any property visible, there is no icon associated
with this object.
The Partition Membership icon appears as a question mark (?).
• Spatial search for design features unsupported

The following error is displayed when doing a proximity search for design
features:
Missing valid boundary box definitions.

Bounding box information for design features are not published from NX into
Teamcenter. This will be supported in a future version of NX and Teamcenter.
• Traversal of references generating relations

Teamcenter supports forward traversal of reference geometry relations;
backward traversal is not supported.
This feature is not supported in Teamcenter 10.1 and will be added in a future
version.

Automotive Edition
The following release notes pertain to Automotive Edition.

• CORP_Part item revision save as issue
In the Save As wizard for CORP_Part item revision, navigating to the Define
Attached Data form generates an incorrect UGMASTER name. Performing any
action on newly created UGMASTER produces incorrect results.
In the Save As wizard for CORP_Part item revision, after assigning Item
id/revision - name and entering information on the Define additional Item
revision information page, click Finish. You must explicitly copy additional data
sets that are not copied over as per default copy rule.
Aerospace and Defense
The following release notes pertain to Aerospace and Defense.

• Thin client support for Aerospace and Defense features
Thin client support for Aerospace and Defense functionalities is not provided in
Teamcenter 8.1 or 8.2.
• PLM XML support for Aerospace and Defense objects.

PLM XML support for Aerospace and Defense objects is not provided in
Teamcenter 8.1 or 8.2.
Audit Manager
The following notes pertain to usage of Audit Manager.

• Audit log export to Microsoft Excel and CSV formats not supported in
the thin client
The thin client does not support the following:
o Export of audit logs to Microsoft Excel from the Audit Logs tab
o Export of audit logs to CSV file

In the thin client, you can export audit logs to Excel by executing audit saved
queries and exporting the results from the Search Result page using the
AUDIT_log_export_template_new template in the Tools®Export to Excel
command.
• Error when using Audit Manager on IBM DB2

An error is reported when running on IBM DB2 and auditing is enabled. The
error written to the syslog file is similar to the following:
Message: [IBM][CLI Driver][DB2/AIX64] SQL0668N
Operation not allowed for reason code "7" on table
"INFODBA.AUDITLOG". SQLSTATE=57016
Approx SQL was "INSERT INTO AUDITLOG
(PUID, ObjectUID, EventTypeUID, ObjectId, ObjectName, ObjectRev, AuditDefUID,...

The error is due to the audit log table being in a pending state and therefore not
being able to be written to. This can be confirmed by running the following
query command:
select TABSCHEMA, TABNAME from SYSIBMADM.ADMINTABINFO where REORG_PENDING = ’Y’
For any tables returned by the query, run the following command:
reorg table <schema>.<table>
Briefcase Browser
The following notes pertain to use of Briefcase Browser.
• User interface changes are not reflected in non-English help
Changes to the preference dialog box of the Briefcase Browser application
occurred after localization of the help documentation, resulting in only the
English help being accurate and all non-English help containing fields that no
longer exist.
Ignore the field descriptions in the non-English help and graphic that do not
appear in the actual dialog box. The fields were removed from the Custom
Mappings section (callout 2 area in the graphic).

New Preferences dialog box
Change Manager
The following notes pertain to usage of Change Manager.

• Save As function is not disabled for change revision items
The thin client has the Save As function exposed for change objects when it
should be disabled. Save As functionality violates change management business
logic and also violates the data model, so the functionality should have been
disabled in the thin client to prevent customers from breaking the business
rules and creating bad change management data. The change is not reflected
in the thin client.
Create a new change. This creates the data properly.
• BOM change displays BVRs

BOM change displays BOM view revisions (BVRs) for any revision object.
BOM change displays item revisions by default. Any other revision to be displayed
in a BOM change must be added to the CM_BomChangeDisplayableTypes
preference.

• Save As action is disabled in Change Manager

Save As functionality violates Change Manager business logic and also violates
the data model. Therefore, Save As functionality is disabled to prevent
customers from breaking the business rules and creating corrupt change
management data.
Create a new change object that creates the data properly.
• Change Manager preferences changes after upgrade

After Teamcenter 8.1, the following run-time properties are no longer used, and
should not appear in any of the preference content:
CMImplement
CMImpactedItems
CMProblemItems
CMReferenceItems
CMSolutionItems
CMWorkBreakdown
Their replacements are the following properties:

CMImplements
CMHasImpactedItem
CMHasProblemItem
CMReferences
CMHasSolutionItem
CMHasWorkBreakdown
Because upgrade should not overwrite existing preference content, the

corrections should be done manually by site administrators after upgrade (for
example, to Teamcenter 8.3). The correction ensures proper display and function
of the Change Manager folders.


The following example shows how to correct preference content. The following
preference definition appears in Teamcenter 8.1:
<preference name="ChangeNoticeRevision_DefaultChildProperties"
type="String" array="true" disabled="false">
<preference_description>Specifies the list of properties that can
be displayed as children of a ChangeNoticeRevision
node.</preference_description>
<context name="Teamcenter">
<value>IMAN_master_form_rev</value>
<value>IMAN_specification</value>
<value>IMAN_requirement</value>
<value>IMAN_manifestation</value>
<value>IMAN_reference</value>
<value>release_status_list</value>
<value>TC_Attaches</value>
<value>CMImplement</value>
<value>CMImpactedItems</value>
<value>CMProblemItems</value>
<value>CMReferenceItems</value>
<value>CMSolutionItems</value>
<value>CMWorkBreakdown</value>
</context>
</preference>
After upgrade to Teamcenter 8.3, the preference should be manually corrected as

follows. (The order of values may differ according to sites.)
<preference name="ChangeNoticeRevision_DefaultChildProperties"
type="String" array="true" disabled="false">
<preference_description>Specifies the list of properties that can
be displayed as children of a ChangeNoticeRevision
node.</preference_description>
<context name="Teamcenter">
<value>IMAN_master_form_rev</value>
<value>IMAN_reference</value>
<value>release_status_list</value>
<value>TC_Attaches</value>
<value>CMHasProblemItem</value>
<value>CMHasImpactedItem</value>
<value>CMHasSolutionItem</value>
<value>CMReferences</value>
<value>CMHasWorkBreakdown</value>
<value>CMImplements</value>
</context>
</preference>
The following preferences are also no longer needed. They either can be deleted
or left with empty content.
CM_default_displayed_pseudofolders
CM_ProblemReportRevision_displayed_pseudofolders
CM_ChangeRequestRevision_displayed_pseudofolders
CM_ChangeNoticeRevision_displayed_pseudofolders
CM_Cm0DevRqstRevision_displayed_pseudofolders

Classification
The following notes pertain to usage of Classification.

• Editing LOV values in the rich client
If the KeyLOV definition consists of submenus, the Edit Properties dialog box in
the rich client may not display the selected value. However, when you exit the
Edit Properties dialog box, the value can be seen. This display issue, seen only
with LOVs containing submenus in the rich client, does not impact saved data.
Display the selected LOV value in nonedit mode.
• Dataset display of classified items with restricted item revision access

A No Read Access error is shown in the following scenario. An item with multiple
item revisions is classified, and the first item revision is released and the second
one is in a Working state. If a dataset is attached to both of the item revisions
and the logged-on user has no read access on the Working item revision, if
the user tries to access the classified object (the item) in the Classification
application, a No Read Access error appears.
Revision rules are used to decide which item revision to use while selecting
the dataset to be displayed. Use the ICS_instance_image_revision_rule
preference to specify the revision rule. The default value of this preference is set
to the Latest Working state.
• Loading large classification data in the thin client

When loading a large set of classification data in the thin client, the following
message appears:
There are too many objects to load. Try refining your search criteria.

The number of objects that can be loaded from Classification search results in
the thin client client are limited by browser memory and processing constraints.
If the user tries to load more than 1000 objects from Classification search results,
the user receives the There are too many objects to load. Try refining your
search criteria message.
The user can refine the search criteria to find a smaller set of objects.

• PLM XML import of classification objects does not support incremental

flag in transfer mode
When you import a classification object (dictionary attribute, keylov, class,
view, or ICO) using PLM XML and the object already exists in the database, the
import action updates existing objects in the database.
Classification import functionality ignores the incremental change flag on
transfer modes and updates existing classification objects.
• ICS XML export of ICO with export item option is not supported
ICS XML export of a classification object (ICO) with the export item option is no
longer supported in Teamcenter 9.0.

• PLM XML between two sites with different site master locale set
Due to a Classification PLM XML schema limitation, the Classification PLM
XML importer does not import data in the same language format as exported
(like Teamcenter PLM XML export/import) if the site master language from the
exporting site (which is mentioned in the XML file) is different from the site
master language of the importing site.
The PLM XML import is allowed despite the site master language from the
exporting site. However, this may result in importing the exported master value
as the importing site master language translations.
o Export/import with no locale selection

When no locales are selected during export, the exporter exports the
database scalar/master values for the localized properties. During import, if
no localizations are present in the PLM XML file, the importer imports the
values as importing site master language translations.
o Export/import with locale selection

When locales are selected during export, the exporter exports the database
scalar/master values and the translations for the localized properties.
During import, if localizations are present in the PLM XML file, the importer
imports the master values as importing site master language translations,
and the importer verifies if the languages represented in the PLM XML file
are supported by the importing site. If all of the languages represented in the
PLM XML file are not supported in the importing site, the import may fail.
If some of the languages represented in the PLM XML file are supported in
the importing site, the importer ignores nonsupported languages and imports
the supported ones. The ignored languages are logged in the importer log.

• Granting or revoking translation privilege for Classification users

Not all Classification business objects have the Owning User attribute. Due
to this limitation, the translation ACL revokes the translation privilege from
the Classification user.
Classification administrator rights are required to configure translation ACL
privileges using Access Manager:
o Grant the translation privilege to a Classification administration user.

Classification users do not have the translation privilege. Add the
Classification user into the translation ACL and grant the translation
privilege using Access Manager.
o Revoke the translation privilege from a Classification user.

Because users in the DBA group have the translation privilege, any
Classification administration user who belongs to the DBA group
automatically has the translation privilege granted. To revoke the
translation privilege from a specific Classification administration user,
the administrator must remove the DBA group from the translation ACL,
add a specific Classification administration user, and grant the translation
privilege using Access Manager.
• Unable to remove the image of a classified instance in the Classification

application
If you try to remove an image of a classified instance in the Classification
application, the image is not removed. It is still displayed.
Remove the image from the classified object in the My Teamcenter application.
• Classification import and export fails on ECAD library items

The Classification application has the concept of unit bundles. For example,
distance is measured using units in a bundle, such as millimeters, centimeters,
meters, inches, and so on. Among units in a bundle, one of them is known as the
base unit, and its attribute value is saved into the database.
However, the Classification import/export layer does not provide APIs to access
subunits other than the base unit. This leads to ECAD library integrations
failing during import when the value is not in the base unit.
Avoid using unit bundles for ECAD attributes in ECAD tools as well as in
Classification.

Client for Office
The following release notes pertain to the use of Teamcenter Client for Microsoft
Office.
• Script error appears when using lists to select Client for Office
properties
A script error message appears when using lists to select Client for Office
properties.
When the following script error message displays:
Do you want to continue running scripts on this page?
Click Yes to continue without data loss.
• Display problem editing properties in Microsoft Excel using Client for

Office
When editing properties of a checked-out Teamcenter object in the summary
view properties dialog box in Microsoft Excel, entering values into a text box field
causes the data to be typed into one of the spreadsheet cells behind the dialog
box rather than in the property text box field in the foreground.
Minimize the Excel spreadsheet by clicking the minimize button for the
worksheet (not the workbook). Edit the properties as you normally would, and
then restore the worksheet after you are done editing. If this does not work,
restore the Excel worksheet, click in a different worksheet cell, minimize it
again, and then retry editing the properties.
• File type mismatch error if IRDC setup specifies wrong file type for
DMTemplate type
In Client for Office, when you attempt to create a new dataset in the context of
a document revision that is under IRDC control, Client for Office displays a
message about a file type mismatch.
This occurs because the Teamcenter administrator incorrectly used the wrong file
type. For example, this can occur if the administrator defined the DMTemplate
type with a .doc file extension instead of a .docx file extension in the IRDC
setup in the Business Modeler IDE.
The Teamcenter administrator must correct the IRDC setup to specify the
correct corresponding file type.

• Client for Office does not support customized Microsoft Office datasets
Teamcenter Client for Microsoft Office does not work with customized Microsoft
Office datasets.
Using Client for Office with customized Microsoft Office datasets requires a
manual update to the schema XML file and then a redeployment. This is required
to enable the OfficeOpen operation when you open the customized Microsoft
Office dataset in the rich client. This cannot be done through the Business
Modeler IDE because the OfficeOpen operation is a legacy operation type.
If the system has customized datasets for Microsoft Office file extensions (for
example, .doc, .xls, .ppt, or .msg), you must manually add the following entry
to the XML schema file, and then deploy the file:
<ADD>
...
<TcExtensionAttach extensionName="OfficeOpenExt" operationName="OfficeOpen"
isActive="true"
extendableElementName="custom-dataset-name"
extendableElementType="Type"
extensionPointType="BaseAction" conditionName="isTrue"/>
...
</ADD>
For example, if the system has a customized dataset for Microsoft Word file types
named CustomMSWord, add the following XML entry:
<ADD>
...
<TcExtensionAttach extensionName="OfficeOpenExt" operationName="OfficeOpen"
isActive="true"
extendableElementName="CustomMSWord"
extendableElementType="Type"
extensionPointType="BaseAction" conditionName="isTrue"/>
...
</ADD>
Redeploy the schema.

Add the custom dataset name to the new Client for Office configuration
file before you install Client for Office. Configuration files are
located in the additional_applications\OfficeClient\program
files\Siemens\Teamcenter9\Office Client directory in the Teamcenter
software distribution image.
Microsoft Office
application Configuration file
Microsoft Word TcWordAddin.dll.config.template
Microsoft Excel TcExcelAddin.dll.config.template
Microsoft PowerPoint TcPowerPointAddin.dll.config.template
Microsoft Outlook TcOutlookAddin.dll.config.template

For example, to add a customized dataset for a Microsoft Word file type named
CustomMSWord with the *.doc file type extension, update the typemaps
section in the TcWordAddin.dll.config.template configuration file:
Locate the following lines in the configuration file.
...
<typemaps>
...
<add extension="doc" soadatasettype="MSWord" soareftype="word"
toolname="MSWord" />
...
Modify these lines to read as follows:

...
<typemaps>
<add extension="doc" soadatasettype="MSWord,CustomMSWord"
soareftype="word"
toolname="MSWord" />
...
This procedure assumes that the reference name of customized dataset is

the same as the default dataset provided with Teamcenter. In this case, the
default MSWordX dataset has the reference name word. The customized
CustomMSWord dataset should has the same reference name called word.
Perform similar updates for other customized Microsoft Office datasets in the
appropriate configuration files.
Note The method described here for configuring Client for Office is valid only
for administrators. Nonadministrative users can modify their user
settings to change the dataset type to the custom type for the desired
file extension after Client for Office is installed.
• Buttons in the Configurations – Attribute Exchange dialog box do not

respond after duplicate mappings message
When users create or modify attribute exchange mappings, they may select the
Teamcenter attributes or Microsoft Office properties that have already been
mapped. Teamcenter displays a message about the duplication.
If you attempt to create or modify another mapping from the Configurations
dialog box, you may find that the Create or Modify buttons do not respond
immediately. You must click several times before the Create/Modify dialog box
is displayed.
After you dismiss the duplicate mapping message, before you click any buttons,
click anywhere in the Configurations dialog box to set focus on the dialog box for
the buttons to function as expected.

• Users are not returned to the correct Word window after create or
modify attribute exchange mappings
After creating or modifying an attribute exchange mapping, when you close all
the attribute exchange configuration dialog boxes, Teamcenter does not return to
the Microsoft Word window in which you started the configuration.
Currently, there is no workaround for this problem. Make sure the active
Microsoft Word window is the one you want to work in after the attribute
exchange configuration.
• Read-only Microsoft PowerPoint file remains read-only after Open and

Check-Out
If you open a Microsoft PowerPoint dataset in read-only mode, and then check
out the dataset, the file remains read-only. Without closing the opened document,
you perform an Open and Check-Out action, but the file is still opened in
read-only mode and you are unable to save any changes to Teamcenter.
After a PowerPoint dataset is opened in read-only mode, it cannot be made
writeable until the document is closed. Close the document completely and then
perform an Open and Check-out action.
• Client for Office Minimize Ribbon setting triggers error

The Teamcenter Search dialog box in Client for Office may not paint properly
or may trigger an error message dialog box from Office. This is only seen when
the Minimize Ribbon option is selected. The error message text indicates an
Invalid Handle error.

You can temporarily toggle the Minimize Ribbon setting in the Office application
while initially displaying the Search dialog box. After the window is displayed,
the Minimize Ribbon option can be reset. When dealing with the Teamcenter
ribbon, the preferred mode is to have the ribbon content displayed.

• Some features are disabled when Word opens all documents in the same
window
In the Word Options dialog box, clearing the Show all windows in the Taskbar
check box sets Word to open all documents in the same window, with the
Windows taskbar showing only the active document name. This setting disables
some Client for Office features.
1. Before opening a document, click the Office button and select Word Options.
2. In the Word Options dialog box, select Advanced in the left pane, and then
scroll to the Display section in the right pane.
3. Under Display, select the Show all windows in the Taskbar check box.
With this setting:
o Each document opens in a separate Word window and the taskbar shows
the individual document names.
o All Client for Office features for Word are enabled.

Content Management
The following release notes pertain to usage of Content Management.

• Cannot create multiple topics types for the same schema
Currently you cannot create two or more topic types using the same schema. To
distinguish between the two topic types, you should be able to use the topic type
conditions. However, this is currently not supported in Content Management.
This does work for DITA maps because DITA uses an import dialog box that
enables you to select the topic type used during the import of the DITA map.
Create two different schema objects using the same DTD or XSD file. When you
create the second schema object, edit the DTD or XSD file so it has a different
public ID or system ID. Use this new public ID or system ID when creating the
schema object in Content Management.
• Remove old Content Management saved queries

When you upgrade Content Management to Teamcenter 10.1, several saved
queries still exist that are no longer needed.
Using Query Builder, remove all the saved queries that start with DC_and Civ0
if S1000D 4.0 is installed.
• Document title is not saved in the XML when exporting a SCORM

package
The XML attribute mapping for the SCORM Package - 4-0 topic type does not
contain a mapping for the document title. This results in the title missing from
the XML for a Sharable Content Object Reference Model (SCORM) package.
Add the following entry to the XML attribute mapping for the SCORM Package -
4-0 topic type:
DocumentTitle Bidirectional identAndStatusSection/
scormContentPackageAddress/scormContentPackageAddressItems/
scormContentPackageTitle

• Validation error from XMetal

When you save or validate an S1000D 4.0 Procedural4.0 topic using XMetal
in Content Management, XMetal displays a validation error that states the
itemCharacteristic has an invalid value. However, according to the schema for
Procedural4.0, the value ic00 is valid.
Either remove the itemCharacteristic attribute from the XML or ignore the
error from XMetal.
Data Exchange
The following release notes pertain to Data Exchange.

• Cannot transfer a dataset shared by multiple item revisions
If you revise an item revision without revising its dataset, both the new and old
item revisions share the same dataset. You cannot transfer that dataset using
Data Exchange.
Currently, there is no workaround for this problem. This problem will be
resolved in a future maintenance release. Contact GTAC for further information
about availability.
• Customization may alter behavior of monitoring interface

If the behavior of the monitoring interface changes, it may be because of your
customizations. If it does fail, compare your mapping to the Teamcenter
out-of-the-box (OOTB) mapping.
Currently, there is no workaround for this problem. This problem will be resolved
in a future patch. Contact GTAC for further information about availability.
• Remote import that transfers ownership in Global Services fails to

update ownership in ODS
If you perform a remote import that transfers ownership using Global Services,
it fails to update the ownership in ODS.
Currently, there is no workaround for this problem. This problem will be resolved
in a future patch. Contact GTAC for further information about availability.

Document Management
The following release notes pertain to Document Management.

• Markup Manager task pane context menu
When you right-mouse click to perform an action and the focus is outside the
Markup Manager task pane, the action does not work.
Make the focus for the context menu within the task pane. The same issue
exists with the disposition context menu.
• Cannot save markup from Adobe Reader X to Teamcenter

You cannot save markup to Teamcenter from a Adobe Reader-enabled PDF file
launched from the View/Markup action of the context menu in the Outlook Office
client session.
Save the results in the Acrobat Save As dialog box instead of saving the markup
to Teamcenter.
Also, in Adobe Reader X, choose Edit®Preferences and clear the Enable
Protected Mode at startup check box.
• The delete key on the keyboard fails to delete e-mail in Outlook

After a user clicks any object in Teamcenter task pane in Microsoft Outlook, the
delete key on the keyboard does not delete the selected e-mail.
The delete option on the context menu still works. Also, Microsoft technical
support provides the following work-around: Right-click any e-mail to display
the context menu, or switch tabs on the ribbon (in Outlook 2010). After this,
the delete key works.
• No feedback given when no tool exists for viewing and markup of PDFs
on a Macintosh system
No feedback is given when no tool exists for viewing and markup of PDF
documents on a Macintosh thin client system.
Because the tool has not been set up, look in the Java console to see the error
that occurs.

Extensions for Office
The following release notes pertain to the use of Extensions for Office.
• Requirements task pane fails to display (Microsoft Word 2010)
When attempting to open a requirements specification document when no
other Microsoft Word document has previously been opened, the Requirements
Management task pane is not shown. This happens only with Microsoft Word
2010. Microsoft Word 2007 does not display this behavior.
Open a different Microsoft Word document before you open the requirements
specification document.
It is not necessary to leave the other document open after you successfully open
the requirements specification document.
• Patch upgrade for Extensions for Office add-in files

There are no specific instructions when the add-in is updated in patch for
Extensions for Office add-in files.
Perform the following steps whenever the patch contains changes to the
Extensions for Office (live Excel) add-in:
1. Verify that the patch contains the wnti\tc\officeliveaddins folder. If it

does not, the patch does not contain any changes to the add-in.
2. Depending on which Office version is installed, copy files

from either the office2007 or office2003 folder to the folder
where add-ins are installed (most likely the C:\Program
Files\Siemens\Teamcenter8\tc_ext4mso\office200X\ folder).

3. Register the DLLs using the regasm.bat file in the installation folder. If
this file is not present or is deleted, re-install the add-ins using the standard
installer using the released kit in Teamcenter.
4. Close all Microsoft Word instances.
5. Locate the following file in the wnti\tc\officeliveaddins\office200X

folder:
o Office 2007:
TcO2K7Preprocessor.dotm
o Office 2003:
TcO2K3Preprocessor.dot
Copy the file to the %APPDATA%\Microsoft\Word\STARTUP folder.

(Type the path in the Start→Run dialog box to navigate to the folder.)
Overwrite the file if it is already present.
6. Make sure the file is read-only by inspecting the properties of the file.
Following these steps ensures that the add-in was updated successfully in
the patch.
• Disconnect button renamed in Extensions for Office

The Disconnect ribbon button in live Word is used to signify that you are
disconnecting the document and can reconnect the document to Teamcenter in
the future. Currently, it makes the document static so that you cannot connect to
Teamcenter.
The ribbon button is renamed to Make Static. The warning message is modified
accordingly.

Global Services
The following release notes pertain to Global Services software.

• Changes to the mapping_designer_projects directory
The file paths of some source files under the
TC_DATA/mapping_designer_projects directory are too long for Windows
systems if the length of the TC_ROOT directory itself exceeds 60 characters.
Zip the contents of the mapping_designer_projects directory into a
mapping_designer_projects.zip file and place it in the TC_DATA
directory. Also zip the mapping_designer_projects_TCEC directory into a
mapping_designer_projects_TCEC.zip file. Sites that need to access the
mapping project files must unzip the appropriate file into a local directory to
use it.
Note The mapping_designer_projects_TCEC directory is new in
Teamcenter 10.1.
• Library updates in Global Services EAR files may result in deployment

and or run-time problems
The Xalan library has been updated to the xalan-2.7.1.jar file from the original
Teamcenter 8.3 version of the xalan-2.7.0-2.jar file. If you use the Web
Application Manager (insweb) to install over a later version, both versions of
the Xalan JAR file may end up in the tcgs.ear file. Instances have been observed
where serialization issues occur after updating to a current patch level.
Additionally, the gs-ode.ear manifest makes reference to the old Xalan JAR file.
Depending on the install method, application server, and application server
configurations, the installer may or may not see this issue.
To avoid multiple JAR file versions, install with a fresh Web Application Manager
solution, or remove the old staging directories before creating the EAR file.
Alternatively, the installation may also remove the older JAR file from the EAR
file from the tcgs.ear/lib/xalan-2.7.0-2.jar location.
If issues are observed with the tcgs-ode.ear file, update the manifest file located
at tcgs-ode.ear/tcgs-ode.war/META-INF/MANIFEST.MF to reference the
new xalan-2.7.1.jar file.

• Deploying Global Services ODE EAR file in WebLogic 10.3.3

While deploying Teamcenter 9.1 Global Services ODE EAR files in WebLogic
10.3.3, a NoClassDefFoundError error appears, preventing deployment from
succeeding.
Copy the GS.EAR/lib/xercesImpl-2.9.0.jar file to the
ODE.EAR/ODE.WAR/WEB-INF/lib directory and redeploy the ODE EAR file.
• Asynchronous problem in WebSphere 8

Some GMS use case actions may not run asynchronously. As a result, some
process executions may be blocked, thus causing degraded performance or
producing errors and execution failures.
Use another supported application server.
• Client credential too weak error on Linux

This issue affects SUSE Linux 11 and Red Hat Enterprise Linux 6.
When executing the ODS startup command (/ods -u=infodba -p=infodba
-g=dba), the command shell displays the following error:
Cannot register service: RPC: Authentication error; why = Client credential too
weak
pid = 31635, unable to register (ODSPROG = 536875585, ODSVERS = 1)

Restart the rpcbind process with the -i and -w options:
kill -15 <rpcbind>
rpcbind -i -w
Note This problem can also occur when the idsminetd program is used for
custom Multi-Site configuration.

• ODS service does not start automatically on reboot on Linux

This issue affects SUSE Linux 11 and Red Hat Enterprise Linux 6.
After you run the Teamcenter Environment Manager (TEM) root script, the
rc.ugs.ods script does not start the ODS service automatically during a system
reboot.
You must add commands to terminate and restart the rpcbind service to the
TEM root script to enable these commands to run during a reboot.
The rpcbind process must be started once per boot session on SUSE Linux 11.
This should be handled similar to the kill -1 command on the inetd process ID.
Perform the following steps:
1. Modify the /etc/init.d/rpcbind startup script by adding the following line
immediately after the RPCBIND_BIN=/sbin/rpcbind line:
OPTIONS="-i -w"
2. Restart the rpcbind process by issuing the following command as root:

/etc/init.d/rpcbind restart
Note This is required only once after the rpcbind startup script is
modified.
After you apply this workaround to the rpcbind script, on a subsequent system
boot, the rpcbind process launches in insecure mode. This allows the ODS
service to start and function normally.
Be aware that by making this change, the rpcbind service thereafter always
runs in insecure mode.
• Deploying Global Services ODE EAR file in WebSphere 7

The Global Services ODE EAR file requires additional steps to be deployed on
the IBM WebSphere 7 application server in order for the BPEL engine to start
properly.
These steps are note required for other supported application servers.
Do not install any service pack later than 11 (that is, do not use a WebSphere
version later than 7.0.0.11).
Before you deploy the Global Services ODE EAR file, locate the
Ode.EAR/Ode.WAR/WEB-INF/modules directory and delete the
addressing-1.3.mar file.
Make sure the following JAR files are referenced in WebSphere’s classpath:
commons-io-1.4.jar
commons-fileupload-1.2.jar
woden-api-1.0M8.jar
commons-codec-1.3.jar

commons-httpclient-3.1.jar
commons-logging-1.1.1.jar
log4j-1.2.15.jar
The easiest way to obtain these files is to generate the Global Services
EAR file using the Web Application Manager, and then find the files in the
earapp_root/lib directory for the application.
The WebSphere classpath must also reference the servlet-api-4.2.jar file. This
file is not in the earapp_root/lib directory. If you do not know where to find this
file, download it from its official location:
http://repo1.maven.org/maven2/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar
Access WebSphere’s classpath entry point in the WebSphere Web console:
1. On the left side, choose Servers→Server Types→Websphere application

servers.
2. Click the server name (typically server1) in the main area of the Web console.
3. In the main area under Server Infrastructure, choose Java and Process
Management→Process Definition.
4. In the main area under Additional Properties, select Java Virtual Machine.
The Classpath multi-lined text area should be in the center of the main area
under General Properties.
5. Enter full path for each file and separate each entry with a classpath
separator appropriate for the host’s operating system.
6. When finished, click OK at the bottom of the main area, and then scroll to
the very top and click the Save link to persist the classpath entry.
7. Restart the application server.

Caution The classpath changes do not take effect until after you restart
the application server.

• CATIA site checkout support

Site checkout of CATIA table cell data does not work with Briefcase. In addition,
site checkout of CATIA data through a tier of suppliers does not work with
Briefcase.
• Global Services data transfers encounter deadlocks on MS SQL Server

2005
Global Services data transfers run using MS SQL Server 2005 and WebSphere
may encounter deadlocks when multiple transfers are done concurrently.
Because the Global Services Framework application may run on other
application servers and its database tables can be installed independent of
Teamcenter, use one of the following workarounds:
o Use Oracle to install the database scripts with the Global Services
Framework application. To install them outside of the Teamcenter
installation process, navigate to the directory where the Teamcenter
8.1 Global Services Framework application directory was installed.
From there, navigate to webapp_root\database\oracle. Run the
oracle_create_tcgs.sql script from SQL*Plus.
o Use WebLogic or JBoss to run the Global Services application. For any
specific details regarding installation on WebLogic or JBoss, see the
installation guides.
• CATDrawing name should be changed manually on new revisions

Drawing data set is missing after re-exporting the component.
If the CATDrawing name is different from that of associated assembly or
component part number, its name should be manually changed to be different on
all future revisions so that it will be associated with correct item on Teamcenter.
• Sample rich client BOD does not display revision number of item
The sample rich client BOD does not display the revision number of the item.
Ignore the revision column or modify the BOD to remove the revision column.

• Autopopulated nonmandatory fields should not be populated by user in

the Insert form
Several of the nonmandatory boxes (for example, Part Name) of the Teamcenter
assembly BOD are autopopulated by Teamcenter.
Currently, Global Services does not have a capability to suppress such
autopopulated fields from the Insert form. Therefore, do not enter information in
these boxes when using the Insert form.
GM Overlay
The following release notes pertain to Teamcenter Automotive Edition–GM Overlay.
• GM Overlay fails to autocreate UGMASTER dataset for CORP_PART
as PowerTrain group user
Automatic creation of a UGMASTER dataset fails for a CORP_PART object if
the TAE_Powertrain_site preference is set to 2. Teamcenter does not display
an error message about this.
Create the UGMASTER dataset manually in Teamcenter instead of using
automatic creation.

Lifecycle Visualization
The following release notes pertain to usage of Lifecycle Visualization.

• DWG to PDF fails for files with more than 10 pages
(First published Teamcenter [release])
Converting DWG files to PDF when the DWG files have embedded OLE objects.
If you get an error in Microsoft Excel when converting the file to PDF, then
choose File®Options®Trust Center®Trust Center Settings®Macro Settings
®Disable all macros without notification.
You may also need to set up the vvcp.ini file with the following resource
settings: DxfOLERasterQuality and DxfOLERasterQuality. Uncommnet
them and set to 0. These settings require less memory when converting the file.
• Converting DWG to PDF displays crash for dwg_loader

Converting DWG files to PDF format causes a crash when the DWG files have
embedded OLE objects.
If you get an error in Microsoft Excel when converting a DWG file to PDF format,
choose File®Options®Trust Center®Trust Center Settings®Macro Settings
®Disable all macros without notification.
You may also need to set up the vvcp.ini file with the following resource
settings: DwgOLERasterQuality and DxfOLERasterQuality. Uncomment
the settings and set them to 0. These settings require less memory when
converting the file.
• Cross section viewer stays active

The cross section viewer stays active when switching from Structure Manager
to My Teamcenter if My Teamcenter has no viewer.
Close the cross section viewer.

• Controlling automatic behavior of File Locator search when loading

two-tier data in a four-tier environment
In a two-tier Teamcenter 9.x or 10.x environment, load data into Lifecycle
Visualization and save the session locally. Then, load the session into Lifecycle
Visualization in a four-tier environment when the two-tier environment is not
running. The four-tier authentication prompt appears after authentication data
is loaded.
Data is loaded automatically without confirmation prompt. The File Locator
dialog box is not displayed.
You can resolve this problem by creating the WEB_default_url_autoconfirm
preference with the following values:
Preference name: WEB_default_url_autoconfirm
Type: Logical
Values: TRUE, True, true, 1, FALSE, False, false, 0
The WEB_default_url_autoconfirm preference modifies behavior of the File

Locator feature of Lifecycle Visualization to automatically load the found data
in the following way:
o If WEB_default_url_autoconfirm preference is set to true (or equivalent

values True, TRUE, or 1), and data is found using the site’s four-tier URL,
the data is immediately loaded from that location. No user confirmation
is required.
o If WEB_default_url_autoconfirm preference is set to false (or equivalent

values False, FALSE, or 0), and data is found using the site’s four-tier
URL, Lifecycle Visualization displays the File Locator dialog box. You must
confirm that you want to load from this address before any data is loaded.
Note o The WEB_default_url_autoconfirm preference is not set by
default. A user or a Teamcenter administrator must add this
preference to the environment.
o When the WEB_default_url_autoconfirm preference is not set,

the default behavior of the viewer is the same as if the preference
was set to True, that is, to load automatically without confirmation.
o To correctly load two-tier persisted data in a four-tier environment,

the following Teamcenter preferences must be set correctly when you
save data in two-tier environment:
WEB_default_site_server
WEB_protocol
WEB_default_site_deployed_app_name
These preferences already exist in Teamcenter and are not new.

• Displaying CGM files generated from CATIA V5

Some CGM files generated by CATIA V5 with embedded raster data fail to
display the image when loaded into Lifecycle Visualization. This is because
some CGM data generated by CATIA V5 can be invalid based on the CGM
specification. The invalid data may not impact the rendering of the image, but
any found error can cancel the processing of the image.
If the CGM specification check is overridden, the image may still display properly.
To enable the override, while Lifecycle Visualization is not running, create an
environment variable named TCVIS_IGNORE_CGM_RASTER_ERROR and
set it to any value. If any problems loading CGM files are still present, disable
the override by deleting the TCVIS_IGNORE_CGM_RASTER_ERROR
environment variable and restarting Lifecycle Visualization.
• Massive Model Visualization (MMV) parts flashing

When rendering in Massive Model Visualization (MMV) mode, parts may
oscillate between the visible and invisible state for brief or extended periods of
time. These oscillations may occur when parts are displayed or hidden, or even
when a model is rotated.
• Opening rich client Lifecycle Visualization secondary views

If you open a rich client visualization secondary view from the top-level menu,
for example, using the Window→Show View command, you may see unexpected
results. Views are not associated with any particular 3D or 2D primary view, for
example, Window→Show View→Other→PMI.
Siemens PLM Software recommends you open views using the menu in the
active 3D/2D view, so they are associated with the viewer view.
• Potential Massive Model Visualization (MMV) stability issue with

FX1800 graphics card
Nvidia Quadro FX1800 has been found to show stability issues when Massive
Model Visualization (MMV) technology is used to display 3D models in Lifecycle
Visualization. The stability issue is worse when older graphics driver versions
are used but still occasionally seen with the latest driver.


Siemens PLM Software recommends that the graphics driver be updated to the
latest on the visualization client machine when such a stability issue is observed,
or switch to another Nvidia graphics card, such as the FX580, if the latest driver
does not completely fix the stability issue.
• Solution for X11 issue loading fonts in the UTF-8 locale

On Linux systems running in a UTF-8 locale (for example, en_US.UTF-8), text
may be missing from the Teamcenter lifecycle visualization user interface. For
example, text may be missing from the assembly tree or the File Open dialog
box. On systems with this issue, when you start the application, it may display
the following error message:
Font Creation Failed
Also, the X11 log file (/var/log/Xorg.0.log) may contain error messages such
as the following:
FreeType: couldn’t find encoding ’iso8859-13’ for ’/..../generic.ttf’.
This is a result of some Linux distributions failing to generate the encodings.dir

file during installation. X11 requires the encodings.dir file to load fonts in
UTF-8 locales.
1. Ensure that all X11 Unicode font packages are installed.
2. Navigate to the X11 fonts/encodings directory. On Red Hat Enterprise

Linux 6, this directory is located in /usr/share/X11/fonts/encodings, but
other distributions may put the encodings folder in a different location.
3. If the encodings.dir file does not exist in this location, generate the file
using the mkfontdir command. On RedHat 6, type the following at the
command prompt:
cd /usr/share/X11/fonts/encodings
sudo mkfontdir -e /usr/share/X11/fonts/encodings -e /usr/share/X11/fonts/
encodings/large
Note You must run the mkfontdir command from the directory
containing the encodings, and it should have a separate -e flag
for each subdirectory that also contains encodings, such as the
encodings/large subdirectory on Red Hat 6.
4. If the encodings.dir file exists and the problem persists, check to make
sure that it includes encodings for each of the classes in the XLC_LOCALE
file for the locale (in /usr/share/X11/locale/en_US.UTF-8 on Red Hat 6, for
example), or regenerate the encodings.dir file using these instructions.

• Lifecycle Visualization behavior is configurable when opening duplicate

documents
Behavior in stand-alone and embedded Lifecycle Visualization when opening
duplicate documents is changed in Teamcenter 10.
In previous versions, when you open a document in that is already open,
Lifecycle Visualization opens a new window with a copy of the document.
In Teamcenter 10, this behavior is configurable.
In Teamcenter 10, by default, when a document is opened in Lifecycle
Visualization that is already open, the application activates the already-opened
document view.
You can configure Lifecycle Visualization to use the previous behavior (opening
a duplicate window) by setting the Vis_Doc_OpenOption preference. Valid
values for this preference are as follows:
CreatenewDocument Opens a duplicate document window.
ActivateExistingDocument Makes the already open document window

active.
For more information about the Vis_Doc_OpenOption preference, see the

• Automatic update of product views fails with the Use current option
Automatic update of product views in Teamcenter fails with an update status
shown in red, indicating the update failed. This can occur if product views are
captured using the Use current option.
Set the TCVIS_VAA_DISABLE_VISIO_OPTIMIZE_APPROCH system
environment variable to true, and then restart the server host. This variable
must be set regardless of whether you use the Use current or Update from
Product View options when the product view is captured.

• 2D Markup toolbar in the thin client cannot be turned off

If the 2D Markup toolbar is visible, you cannot turn it off in the toolbar context
menu.
• Teamcenter rich client Group/Role switch and stand-alone Lifecycle

Visualization
Stand-alone Teamcenter Lifecycle Visualization does not support group and
role change.
When launching data from the rich client to stand-alone Lifecycle Visualization,
the new Teamcenter session (separate Teamcenter server) is created by Lifecycle
Visualization. If the group/role changed during the rich client session, Lifecycle
Visualization is still working with the old Teamcenter server that is separate
from the rich client and is not aware about group/role switch.
There are two implications:
1. You may see the additional authentication prompt because of the changed
group/role portion of the credentials. After authentication, the viewer joins
the previously established Teamcenter server and the server side session
that is not aware of group/role switch.
2. The data access permission is the same as for first logon. You may not
see data as expected for new group/role because the group and role on the
Teamcenter server did not change.

For stand-alone Lifecycle Visualization, the stand-alone viewer must be closed
when group and role are switched by launching the application (rich client).
You must save the unsaved data and close the viewer.
The data may then be launched into a new Lifecycle Visualization viewer and be
processed and displayed correctly according to the new group/role permissions.

• Session files created by two-tier Lifecycle Visualization 8.1 have bad

IOR references
Teamcenter lifecycle visualization 8.1 in two-tier mode created sessions with
interoperable object references (IORs) that are temporary random numbers
that identify current sessions. These session files could only be reopened in the
viewer if current two-tier session was still valid. Once the Teamcenter server
process was closed, these sessions could not be reopened.
In Lifecycle Visualization 8.3 and Teamcenter 8.3, there were modifications to
prevent incorrect creation of sessions in two-tier mode, so this problem does not
exist for sessions created in versions 8.3 or later.
You can open Teamcenter 8.1 two-tier sessions that contain IORs in Lifecycle
Visualization 9.0 using File Locator. Note that modifications were made in
Teamcenter clients to support File Locator search, so setting File Locator in
Lifecycle Visualization 8.3.2 does not result in sessions loading correctly.
To configure the Lifecycle Visualization 9.0 viewer to use File Locator, perform
the following steps:
1. Select File→Preferences→File Locate, and then click the Document Search

Order tab.
2. Move the User-Defined Directory Set directory set to the top of the list.
3. Make sure the User-Defined Directory Set directory set is set to Enabled
and the Auto Confirm setting is set to Yes.
4. Click Edit. In the lower pane, click Add for the unatt extension.
5. In the Browse dialog box, click the Servers tab in lower left corner.
6. In the list of servers, select the two-tier server entry, and then click OK.
7. Authenticate if necessary, and then close the open dialog boxes.

Note You may need to load an item from the server first to seed the Browse
dialog box with the two-tier server location or you may need to add that
entry manually.

• Security Services profile setting and parameters resolution

Currently, the Lifecycle Visualization viewer does not support multiple Security
Services configurations or dynamic Security Services configuration discovery
capability in Teamcenter 8 or later versions.
Dynamic discovery of Security Services configuration was available in earlier
DAK-enabled servers and is available for Teamcenter community collaboration
servers.
The following capabilities were added to Lifecycle Visualization 8.3.1:
o Dynamic discovery of Security Services configuration
o Multiple Security Services configurations using Windows registry settings

through registry scripts
If Security Services configuration is set using Windows registry settings,

dynamic discovery of Security Services configuration is not attempted.
Consider the following considerations when configuring dynamic discovery of
Security Services configuration:
o Dynamic discovery of Security Services configuration works only for four-tier
deployments that also have Teamcenter thin client deployments.
o Dynamic discovery of Security Services configuration does not work for

two-tier deployments.
o Dynamic discovery of Security Services configuration does not work for

WebSEAL deployments.
o Dynamic discovery of Security Services configuration does not work if

Security Services configuration settings exist in the Windows registry for
the same server.
Keep the following considerations in mind when configuring registry settings for
multiple Security Services configurations:
o Configurations can be entered into the Windows registry using registry

scripts similar to the following example:
REGEDIT4
[HKEY_CURRENT_USER\Software\Siemens\VisView_Retained\8.3\Common\C\
SSOService\SSOProfilesMap]"SSOProfileMap_Version"="1.0"
"https://server3:port3/service3"="SSOLoginURL=https://ssoserver3:
ssoPort3/LoginService-->SSOAppID=ssoAppID3"
"http://svli6122:8081/S83i_1012Wa"="SSOLoginURL=http://svli6122.
siemens.com:7400/ssoLogin83-->SSOAppID=Tc8S30"
"http://svli6122.siemens.com:8081/S83i_1012Wa"="SSOLoginURL=http://
svli6011v03.siemens.com:7400/ssoLogin83-->SSOAppID=Tc8S30"
"https://svsun011.siemens.com:7102/S83_Sc_dil"="SSOLoginURL=https://
svsun021.siemens.com:7911/LS830_CSIP-->SSOAppID=S83_Sc_dil"
"http://10.126.2.69:7001/tc"="SSOLoginURL=http://svsun025.siemens.com
:7901/LS830-->SSOAppID=S83_Wa_dil"
"http://10.126.3.23:9080/tc"="SSOLoginURL=http://svsun025.siemens.com
:7901/LS830-->SSOAppID=S83_Wb_dil"

Observe the following important considerations:

The preceding registry script example applies to the English section of
the registry. Similar additions are required for other locales.
◊ The scripts registry location will be different for other locales. For
example, for German, the path would be as follows:
[HKEY_CURRENT_USER\Software\Siemens\VisView_Retained\8.3\Common
\de\SSOService\SSOProfilesMap]
The entries must be UTF-8, then URL encoded. ASCII values are
encoded the same as nonencoded values. If the SSOLoginURL or
SSOAppID values have non-ASCII characters, they must be encoded in
the following order:
1. UTF-8 encode.
2. URL encode.
Do not insert extra spaces between equal signs (=), quotation marks
("), and separators.
Any number of HTTP URLs can be entered in the mapping, but it is

recommended to repeat HTTP URLs in different notations. For example:
◊ Short notation URL: http://server:port/service
◊ Full domain notation: http://server.domain:port/service
◊ IP address notation URL: http://IP-address:port/service
The mapping to the Security Services URL and Security Services

application ID would be the same in all of these cases.
Observe the following guidelines when formatting a registry script:
The first line must specify your version of regedit, for example:
REGEDIT4
The second line must specify the registry section location, for example:
[HKEY_CURRENT_USER\Software\Siemens\VisView_Retained\8.3\Common\C\
SSOService\SSOProfilesMap]
Make sure this line reflects your product installation location and
product version.
The third line must specify the Security Services profile map, for
example:
"SSOProfileMap_Version"="1.0"
This line is currently ignored in processing but should be kept in the

script for compatibility with future enhancements.
The remaining lines specify HTTP URL to Security Services information

mappings, formatted as key and value pairs, using the following form:
"key"="SSOLoginURL=http://host:port/service-->SSOAppID=app–ID"

Replace key with the HTTP URL, UTF-8-encoded, and URL-encoded

in double quotation marks ("). Replace host, port, and service with the
appropriate values for the Security Services URL. Replace app-ID with
the Security Services application ID.
The URL following the SSOLoginURL= portion can be of any of the
URL forms previously described (short notation URL, full domain
notation, or IP address notation).
For example:
"http://19.118.8.91:9080/tc"="SSOLoginURL=http://svsun127.siemens
.com:7901/LS830-->SSOAppID=S83_Wb_dil"
Note Make sure you do not insert spaces before or after the quotation
marks ("), equal signs (=) or mapping separators (–>).
• Using motion in a managed environment

DirectModelMotion datasets without a JTPART reference, such as those
created through Lifecycle Visualization, need a JTPART reference added to
them.
Locate the dataset in My Teamcenter, bring up the named references, and
upload the JTPART reference.
The preferred method of persisting motion in Teamcenter lifecycle
visualization 8.3 with a Teamcenter 8 or later server is through the use of
sessions. After creating a new motion using the Teamcenter Visualization
Actions→Motion→New Motion menu command, allow the session save process
to guide you through persisting the motion document. The motion file is saved
into the session dataset as a session dependant document. The motion file is not
visible in the My Teamcenter navigation but can be retrieved by getting the
named references of the session file.
Following is an example of creating a DirectModelMotion dataset using My
Teamcenter:
1. Navigate to the location where you want to create the motion dataset.
2. Choose File→New→Dataset to display the New Dataset dialog box.
3. Select the DirectModelMotion dataset on the left side of the dialog box.
4. Provide a name and use the ... button to import the .vfm motion file.
5. Click OK.
6. Right-click the new dataset and choose Named References.
7. The .vfm file is listed, but it requires a base document.
8. Click Upload to display the upload file dialog box.

9. Ensure the reference is set to JTPART and navigate to the JT file that the
motion was created against.
• Lifecycle Visualization part reconciliation

Historically there have been issues when using Lifecycle Visualization session
files in identifying parts from Teamcenter when the product structure has been
cloned. Lifecycle Visualization has not been able to establish the connection to
the cloned part in session file data. Reconciliation functionality was previously
added to Lifecycle Visualization to help correct this problem.
To further enhance the ability of Lifecycle Visualization to identify parts, new
information can be included in Teamcenter (clone stable identifiers) that is
leveraged by Lifecycle Visualization to identify parts when product structure
data is cloned. However, to take advantage of this new information, you must
perform the following:
1. Configure Teamcenter to create and maintain the clone stable identifiers.
2. Ensure the clone stable identifiers are in the Lifecycle Visualization session
files.
After updating the Teamcenter database to Teamcenter 8.3 or later and

configuring it to use clone stable identifiers, you must update any old session
files. Before modifying any session content, you should open and resave your
session files. The act of resaving the session files includes the new clone stable
identifiers in the session file so that they can be used later when the session
content is used.

• FCC size for rich client embedded viewer

The FCC must be configured to be large enough to load all the JT files
required for visualization during a rich client session. If the FCC cache is too
small, not all the JT files are available during a viewing session, yielding
unpredictable results. For example, the geometry for a part may not be visible,
or a LoadPartException error may be thrown.
Make sure the size of the FCC is large enough to hold the entire set of JT files to
be viewed during a rich client session.
• Sending legacy product views to the rich client Lifecycle Viewer

When sending legacy product views to the rich client Lifecycle Viewer (or
stand-alone Lifecycle Visualization) the reconcile dialog box is displayed. Legacy
product views are those created before Teamcenter 8 (for example, in Teamcenter
Engineering 2005 or Teamcenter 2007). In some cases the product views still
display correctly, whereas in others (Teamcenter Engineering 2005 SR1), the
visibility may not be correct.
Launch the product views in Structure Manager (which works correctly) and
recapture them or update them so that they are saved with the latest data model.
Note You can still launch Teamcenter 2007 snapshots. These still work
correctly despite the reconcile dialog box being displayed.
• Reconcile dialog box may be displayed when a product view is sent to

Lifecycle Viewer with pruning enabled
If the TC3DSS_ENABLE_PRUNED_LAUNCH environment variable is set
to True, when a ProductView is sent to the stand-alone viewer or the rich
client Lifecycle Viewer, the reconcile dialog may appear listing occurrences that
it cannot resolve.
The following example uses color, but putting transforms on parts is another
operation that can also demonstrate the issue:
1. Send a structure to Structure Manager and load parts 1, 2 and 3 into the
Structure Manager viewer.
2. Put an appearance (for example, color) on each of the parts. Part 1 gets red,
part 2 gets white, and part 3 gets blue.
3. Turn off visibility of part 2.
4. Create a product view of the current set.
5. Right click the new product view and send to the Lifecycle Viewer. Assume
pruning is enabled.

The Lifecycle Viewer displays the reconcile dialog box with a message stating
that it cannot resolve part 2.
This occurs because pruning means only visible parts are loaded. Part 2 is not
visible, so it is not loaded. However, there is information about part 2 recorded
in the product view because a color was specified for it during the session that
the product view was created. Therefore, a reconcile dialog box is displayed.
The use of variants may also cause the same issue since variants could be used
to remove BOM lines that previously had information recorded about them in
the product view data. Basically the variant rule is the pruning mechanism
in this case.
If you see a reconcile dialog box in these situations, you can ignore it, and do not
need to update the references.
• Lifecycle Viewer status bar does not show loading status

After sending an assembly to the Lifecycle Viewer, loading the data shows no
status in the Teamcenter status bar. For a large assembly that takes 5 minutes
or more to load, you receive no feedback where in the loading process Teamcenter
is and when it is going to finish. In stand-alone Lifecycle Visualization, the
status bar shows the progress of the loading and provides good feedback.
Log onto Teamcenter, choose Windows→Show View→Other…, expand the
General folder, and select Progress. The Progress view is displayed. The status
bar has limited space when too many items are displayed on it, but you can
see the progress in the Progress view.
• iSeries interoperation not supported

If you purchased a Named User Visualization license, you have access to iSeries
for the thin client, but not the rich client. The license does not include support
of interoperability between iSeries and NX using PLM XML interoperability
functionality.
• Cannot launch Lifecycle Visualization with autologin enabled

If enableAutologin=true and you attempt to launch JT data to Lifecycle
Visualization, the launch fails with the following error message:
The current user credentials are not valid.

You cannot launch Lifecycle Visualization when enableAutologin=true.

MATLAB integration
The following notes pertain to the MATLAB integration.

• Problem handling subsystems with the same name at different levels
If a root model contains subsystems in which two subsystems have the same
name and appear at different levels in the root model hierarchy, the subsystems
are not shown in the model selection page of the save dialog. If this occurs, you
cannot save in Teamcenter subsystems that have the same name and appear
at different levels within the root model hierarchy.
Currently, there is currently no workaround for this problem.
Maintenance, Repair, and Overhaul
The following notes pertain to usage of Maintenance, Repair, and Overhaul.

• Derived characteristic value is not shown on job card
In some rich clients installed using the Over-the-Web Installer, the derived
characteristic value is not shown on the job card. This is rare and does not affect
other functionality critical to the Maintenance, Repair, and Overhaul release of
Service Scheduling in Teamcenter 10.1 and has no impact outside of Service
Scheduling.
This issue will be fixed in the next version of Teamcenter.
• Restriction on the number of service discrepancies that can be resolved

by a service requirement
Currently, there is an unnecessary restriction on the number of service
discrepancies that can be resolved by a service requirement.
Set a generic relationship management (GRM) rule on the SPI0ResultsIn
relation to restrict the number of service discrepancies that can be resolved by a
service requirement to 1. This can safely be changed to allow multiples.

To update the cardinality for the SPI0ResultsIn relation, perform the following
steps:
1. Access the Business Modeler IDE.
2. Create a custom template extending the sspspralignment template.
3. Open the GRM Rules Editor.
4. Select the SPI0ResultsIn relation and click Edit.
5. Modify the relation to update the cardinality and click OK.
6. Deploy the change.
• All options are not stored in the stored option set

When a physical structure is generated from a neutral structure that was
configured with Classic Variants, any options that were identified as Derived
when the structure was configured are not captured in the stored option set.
When physical parts are later installed into the physical structure, the correct
configuration cannot always be properly determined at every level of the
structure, so the correct open usages are not always correct.
When configuring the options, validate that all options are identified as Set by
user and not Derived prior to generating the physical structure. If the options
does specify Derived, manually set that option to another value, then change
it back to the correct value. This changes it to Set by user, and the value is
properly stored in the stored option set.

• Physical part generated prior to Teamcenter 8.1 is missing configuration

information
Physical parts generated prior to Teamcenter 8.1 do not contain a reference
to the configuration context and BOMView type. This information is used
to correctly determine the open usages during part installs when occurrence
effectivity, incremental change, or options and variants were used to configure
the structure. When a part is being installed, the incorrect open usages are
displayed, and parts may not be able to be installed.
The parent physical part must be rebased to establish the configuration
information so that the correct open usages can be determined during
installation.
• Changing default disposition

Updating the PhysicalPartDefaultDisposition business object constant in
the Business Modeler IDE overrides values on existing physical parts that have
never had their disposition changed. Additionally, exporting a physical part to
another site (CMS) may override the disposition if it has never been changed
and if the business object constant of the second site is different than the
originating site.

Manufacturing Process Planner

The following release notes pertain to usage of Manufacturing Process Planner.
• 3D PDF objects with umlaut characters in the name are not simulated
The Generate 3D PDF Report menu command supports creating an animated
PDF report based on Process Simulate data.
Objects (for example, consumed parts) with names that contain diacritical marks
(for example, umlauts such as öäü) cannot be animated.
Use only English letters in object names.
• Automatic refresh of new attachments is disabled in some cases

In Teamcenter 9.1.2.2, 9.1.2.3, 9.1.2.4 and 10.1, the automatic refresh of new
attachments is disabled in some cases, for example, when adding an attachment
in an external application like My Teamcenter or NX. This was done to solve a
performance issue at some sites. One consequence of this is that the new release
status does not appear automatically in the Attachments tree.
There are several workarounds for this issue:
o Step to another BOM line and then back to the selected BOM line.
This applies to Teamcenter 9.1.2.2, 9.1.2.3, 9.1.2.4, and 10.1.
o Use the Refresh Window command, selecting the Refresh current structure
only option to improve performance.
This applies to Teamcenter 9.1.2.2, 9.1.2.3, and 9.1.2.4 only.
o Use the Refresh Current Structure command.

This applies to Teamcenter 10.1 only.
o Set the MEAttachmentPanelEnableRefreshChildren site preference

to TRUE. This enables automatic refresh of the attachments in the
Attachments tree.
This applies to Teamcenter 9.1.2.4 and 10.1 only.
• Some preference settings prevent export of items with occurrence

effectivities
Some preference settings prevent export of items with occurrence effectivities
in certain cases.
If the CFMOccEffMode preference is set to legacy, you cannot export an
assembly that has occurrence effectivities.

If the CFMOccEffMode preference is set to maintenance, you cannot export

an assembly if Structure Manager is open and you try to export the same item
from My Teamcenter.
If the CFMOccEffMode preference is set to legacy, you must create occurrence
effectivities with the CFMOccEffMode preference set to maintenance.
If the CFMOccEffMode preference is set to maintenance, you must close the
Structure Manager view to export the item successfully.
• No direct command for creating Study from Study template

Currently, there is no command in Teamcenter to create a Study from a Study
template.
Currently, you can create a Study using the Save As command. Teamcenter can
create a Study within the limitations of the structure.
A means to create a Study from a Study template will be provided in the future
• Activities view now supports read-only mode

The Activities view was accessible and editable to users that did not have a
Manufacturing author license.
TheActivities view can now be opened in read-only mode by a user that has a
Manufacturing viewer license.
• New Process command now informs users if no license is available

The New Process command was unavailable to users that did not have a
Manufacturing author license, but no error message was displayed to the user.
The New Process command now displays an appropriate error message if the
user does not have a Manufacturing author license.
• New Workarea command now verifies license

The New Workarea command was accessible to users that did not have a
The New Workarea command now verifies the user has a Manufacturing author
license and displays an appropriate error message if the user does not.

• New Activity command now checks license

The New Activity command was accessible to users that did not have a
The New Activity command now verifies the user has a Manufacturing author
license and displays an appropriate error message if the user does not.
• Time and Process Gantt view now supports read-only mode

In earlier versions of Teamcenter, users with a Manufacturing viewer license
could not open Time and Process Gantt views in Manufacturing Process Planner.
Teamcenter now allows users with Manufacturing viewer licenses to open Time
and Process Gantt views in read-only mode.
• Preview file is opened in a stand-alone window

If the preview format for the textual work instructions is defined as PDF and
you have installed 64-bit rich client, the preview file is opened in a stand-alone
window and not embedded in the Teamcenter application.
You must have an Adobe Reader installed on your system to view work
instructions if the preview format is defined as PDF.
Adobe Reader is a 32-bit application on Windows platforms. If you try to open a
PDF file in a 64-bit version of Internet Explorer, the PDF opens in stand-alone
Acrobat or Reader, not in Internet Explorer.
If you have installed 64-bit rich client, the preview file is opened in a stand-alone
window and not embedded in the Teamcenter application.
For more information about this issue, see the following Adobe help page:
http://helpx.adobe.com/acrobat/kb/cant-view-pdf-web.html

• Refresh problem when pasting into a pseudofolder

Pasting into a pseudofolder does not refresh the Attachments view, and you
cannot view the change immediately.
After pasting the design object under the Represented by pseudofolder in the
Attachments view, choose one of the following solutions to see the pasted object:
o Reload the part object again. When opening the Attachments view for this
object, you see the pasted design object.
o Send the object back to Manufacturing Process Planner from My Teamcenter.

You then see the pasted object.
o If the structure has more than one product, move the selection between the
children. The Attachments view is refreshed and you can see the pasted
design object.
• Refresh issue in release status in Attachments view

When releasing an item, the release status is not updated automatically in the
Attachments view. It appears there only after a refresh (for example, when you
change the selection).
Change the line selection or close and re-open the Attachments view to see the
change.
• Problem with an IPA structure

If you have a process with a generated IPA structure with the Show
Unconfigured Assigned Occurrences button set to true, and you unload the
product and toggle the Show Unconfigured Assigned Occurrences button to
false, some of the IPA levels are not displayed.
When toggling the Show Unconfigured Assigned Occurrences button, do not
unload the product structure.

• Changing the use of the typeAndRuleForProcessConfiguration

preference
(First published Teamcenter 9.1
The process tree is not filtered correctly according to children.
Use the controllingOccsForProcessConfiguration preference to filter
the process tree according to consumed status as well as child relations. The
preference should contain definitions for both child and occurrence type relations.
Examples for values for the preference:
o MEOP : One: OCCType : MEConsumed
o MEOP : All: OCCType : MEConsumed
o MEOP : OneLoaded: OCCType : MEConsumed
o MEOP : AllLoaded: OCCType : MEConsumed
o MEOP : One: OCCType : MEConsumed

MEOP : All: OCCType : MEAssign
o MEOP : One: OCCType : MEConsumed, MEAssign
o MEProcess : All : CHILD : MEOP

MEOP : One: OCCType: MEConsumed
o MEProcess: One: CHILD : MEOP

MEPROCESS : ALL : TYPE: MEConsumed
MEOP : ONE: TYPE : MEConsumed
• GD&T symbols in a 3D PDF report are not displayed correctly

Geometric dimensioning and tolerancing (GD&T) symbols in a 3D PDF report do
not display correctly.
Copy the Y14.5M-2009.ttf font file from the font folder in the rich client
installation directory to the c:\windows\fonts folder on the machine on which
the 3D PDF is opened.

• Problems with selection synchronization in line balancing views

In the Line Balancing Chart view and in the Line Balancing Constraints view,
you can experience problems with the synchronization of the selection between
those views and the product BOP or plant BOP structures. In the Constraints
view, this affects the Load Selection and Load Operations commands. The
commands may not always load all operations and processes you selected. In the
Chart view, this affects the Set Scope command. When you set the scope to a
certain station, you cannot set the scope to a different station as long as the scope
object is visible in the plant BOP structure (that is, its parent is not collapsed).
Workarounds are available for both views:
o Line Balancing Constraints view

For the Load Operations and Load Selection commands to work, you must
make sure that only operations and processes that are not yet in the view are
loaded, and you should clear all operations in the Constraints view. Do this
by clicking in an empty area in that view before you execute the command.
o Line Balancing Chart view

If you want to set a different scope, you can temporarily enable response to
selections for the view, change the selection in the plant BOP structure to
the new scope, and then disable the response to selections again for the view.
• 2D images of some types are displayed in low quality in the PDF report
A 3D PDF report may contain a 2D section that displays the PV image (2D
image). If the image is of type ps or tif, it is displayed in the report in low quality.
You can create the image using type jpg or png. In these formats, the image
quality is determined by the settings for the file type definition. The ps and tif
file types are not supported. The bmp type is supported, but the resulting file
size is often too large and the report generation fails, so it is not recommended.

• Not all GD&T symbols are supported

The description of a step (process revision description or operation revision
description) can contain geometric dimensioning and tolerancing (GD&T)
symbols. Not all the GD&T symbols that can be created in Teamcenter can be
displayed in the PDF report.
Formatting of the symbols (italic, bold, frame, and so on) is not supported. Most
symbols are supported. However, the following symbols are not supported and
cannot be used:
GD&T checkmark symbol
Formatting
Positive and negative

numbers formatted
vertically
• Name issue when updating a 3D PDF report after revising

When revising a process or an operation that has a 3D PDF report attached to it,
you may open the Define Attached Data page in the Revise wizard. If you do
not, no problem occurs. If you do, a default name containing a slash character (/)
is generated for the report of the new revision. This character is not valid as part
of a 3D PDF report name so if you try to update this report, the wizard displays
an error prompting you to change the name.
Add the Mes0PDFReport string to the DEEPCOPY_keep_name_list
preference. If the preference does not exist, create it as a multiple value
preference.
• Service Planning PLM XML export/import for Activity assignments

PLM XML export/import for activity assignments (using the same PLM XML
format for export and import) is not supported.

• Classification search for TcPublishing pages does not work

When a TcPublishing portfolio is being edited in My Teamcenter, you can insert
pages by choosing the Insert Reference→Technical Illustration menu command.
From the resulting dialog box, you can opt to specify the TcPublishing page
dataset to be inserted by Classification search. This capability does not work in
My Teamcenter and the button is unavailable.
The Classification search works in the Manufacturing Process Planner
application. To view the portfolio:
o If the portfolio was generated using the Generate Portfolio menu:

1. Send the IDC to the Manufacturing Process Planner application.
2. Select the portfolio under the IDC in the navigator panel.
3. Turn on the data panel to see the viewer.
4. Click the Classification Search button.
o If the portfolio is not generated from the menu, the portfolio can be viewed
in the Manufacturing Process Planner this way:
1. Create an item.
2. Copy the portfolio dataset and paste it to the item revision.
3. Send the item revision to the Manufacturing Process Planner application.
4. Select the portfolio under the item revision in the navigator panel.
5. Turn on the data panel to see the viewer.
6. Click the Classification Search button.
The Classification application can also be used to perform a search. From

there, the dataset can be copied to the clipboard using the application’s
toolbar button and then pasted to the portfolio dataset in My Teamcenter.
• Incremental change (IC) information of occurrence group data

In Teamcenter 8.3, you can create incremental change (IC) information about
occurrence groups and their content (children). However, configuring the view
to show or hide configured changes does not work for this information. Only
incremental change information that is common with the base view (in the item
structure) is filtered.

• Property list of criteria for broken links candidates depends on BOM

line columns
In the Repair Broken Links dialog box, the display of criteria details for the
broken link candidates search depends on the BOM line columns. The list of
available properties is the list of BOM line columns. Properties not exposed in
the BOM lines are not available in the list. Also, if any property is not exposed
as a BOM line column (for example, added from a preference), the label for it is
displayed as the internal property name.
Add the property to the BOM line columns to display it in the property list with
the localized label.
Mechatronics Process Management
The following release notes pertain to Mechatronics Process Management

implementation.
• Thin client in Internet Explorer displays "Stop running this script?"
prompt
When running the thin client in Microsoft Internet Explorer, certain operations
that require more processing may cause the browser to display the following
prompt:
"Stop running this script? A script on this page is causing your web
browser to run slowly. If it continues to run, your computer might
become unresponsive." [yes] [no]

A fix for this problem is available from Microsoft:
http://go.microsoft.com/?linkid=9729250
After installing this fix, the prompt is not displayed.
• The Embeds column does not show any content when expanding a
parent BOM line
In the Structure Manager thin client, when expanding a BOM line whose
children should have content in the Embeds column, the column content is
not displayed.
The Embeds column content can be displayed by opening any BOM line higher
in the structure and choosing View→Expand Below. When the structure is
expanded in this way the Embeds column displays the correct content.

• Invalid relations
Invalid relations resulting as part of Mechatronics Process Management BOM
restructuring are not consistent in PLM XML export/import.
In Structure Manager, BOM restructuring operations can be performed on
structure. Existing relations in the structure can become invalid after these
operations. If a user performs PLM XML export with these invalid associations,
all relations, including the invalid association, are exported. But during import
with this XML, all invalid associations may not get imported as it is.
After a structure is finalized, perform the Fix In-Structure Associations
operation to fix any invalid association existing in the structure after restructure
operations, and then perform the PLM XML export operation. During import
with the same XML, all associations can be imported and both the sites are in
sync. Choose Tools→Fix In-Structure Associations and select the Current Level
option or the All Levels option. The Current Level option validates the selected
BOM line and its immediate children for all Mechatronics Process Management
relations. The All Levels option validates selected BOM lines and its entire
subtree for all Mechatronics Process Management relations. Therefore, it may
take a long time to perform this operation.
• Implemented By and Realized By relationships are not displayed when

copied in another structure
If you copy a product structure containing Implemented By or Realized By
relationships and paste it in another product structure, the relationships are not
displayed in the new structure.
Re-create the Implemented By and Realized By relationships in the new
structure.
• Editing a GDE element fails at a replica site

If you have a Multi-Site environment and you perform any editing operation on a
GDE element under a checked out structure at a replica site, it fails.

• Hierarchical GDE structure at remote site cannot be remotely checked

out
When a hierarchical GDE structure is replicated at a remote site using multisite
functionality, it cannot be remotely checked out and modified at the replica site.
Transfer the ownership of the structure to the remote site before modifying it.
• The Allocation IC Information panel is not displayed

When you modify allocations in IC context and click View-> Show Allocation IC
information Panel to view those changes, no pop up window appears displaying
the IC changes information.

Multi-Site
The following release notes pertain to Multi-Site implementation.

• Use system administrator group to execute 4GD Multi-Site HTTP
environment
When running a Multi-Site HTTP environment with 4GD data, only the system
administrator group is allowed to execute Multi-Site operations. This problem
does not happen in a Multi-Site RPC environment.
For example:
data_share -u=user1 -p=user1 -g=Engineering -4gd_id=DE001
-class=Cpd0DesignElement -site=site2 -f=send -low_level

Run the Multi-Site command line utility using the system administrator group.
• Multi-site publication and remote search failing on HP_UX

Multi-Site publication and remote search do not work on Hewlett-Packard
HP-UX servers when HTTP Multi-Site and SSL are configured.
Currently, there is no workaround for this problem. For more information,
contact GTAC.
• Correlation ID points to a remote site server instead of the proxy server

When a proxy is set up, the correlation ID points to a remote site server instead
of the proxy server. In client and server syslog files, correlation IDs for the
interacting client or server are present. In the proxy environment, this behavior
remains, and although an intermediate proxy exists, its correlation IDs are
not present in the syslog file.
If you know the exact proxy syslog file for analyzing a given interaction, you can
perform the following:
1. To find the server proxy logs on the client side, get the server correlation ID
from the syslog file.
2. Go to the proxy logs location. The proxy host name is specified as the remote
site’s node name in the organization panel site definition at the client site.
3. In the proxy logs, look for the same server correlation ID that is needed
in the client side.
The log containing the server-side log is the corresponding client-side log. The
same process goes in the reverse direction for identifying client proxy logs.

• Multi-Site progress bar causes unnecessary writes to the Oracle redo

logs
During remote import in the background, the Oracle redo logs fill very quickly.
Set the TC_RIMP_BG_prg_update_interval site preference to a numerical
value greater than 0 (the default is 5). The background import progress bar
updates are done only after an interval of n seconds, or if the import state
changes. This restricts the number of progress bar updates, so that input to
the Oracle redo logs is limited.
Multi-Structure Manager
The following release notes pertain to Multi-Structure Manager.

• Cannot import collaboration context directly through Briefcase
Browser
After importing a collaboration context in Briefcase Browser, the collaboration
context is not visible on the second site.
1. Export all the structures individually.
2. Export the collaboration context.
3. Download the Briefcase Browser files.
4. Copy the Briefcase Browser files to the second site.
5. Import the collaboration context first on second site.
6. Import the structures.
7. Send the collaboration context to Manufacturing Process Planner.
The collaboration context is now visible in Manufacturing Process Planner.

My Teamcenter
The following release notes pertain to My Teamcenter.

• Cannot select multiple value mode using the keyboard
When defining a preference, if you want to enter multiple values, you cannot
switch to multiple mode using the keyboard.
For example, when you create a preference
(Edit®Options®Filters®Definition®Create a new preference definition),
select Category, and then use the tab key or press M to select Multiple mode.
The interface remains in Single mode.
Select Multiple mode using the mouse or the arrow keys on the keyboard.
• Set preference to set default Autonomy keyword search logic

When using keyword search, the default logic operator is OR. For example,
searching for cat dog returns search results that contain cat or dog.
If you want to change the default operator to be AND so the search string
cat dog returns search results that contain both cat and dog, you must set
a preference.
Set the TC_fts_default_AND_operator preference to true. This sets the
default logic operator to AND. The default value of this preference is false.
• Calendar dialog box remains open

In the Properties dialog box, click the date button to display the calendar dialog
box. When you click on any other box, such as the Description box, the calendar
dialog box does not close.
Close the Properties dialog box. The calendar dialog box is closed.
• Checkout fails for business objects with unique attributes

When an object is checked out, a copy is made so it can be restored to its original
values if you cancel checkout. The addition of unique attributes to the business
object prevents the copy from being saved to the database and checkout fails.
Prevent the copy action during checkout by adding the business object to the
TcCheckoutReserveOnly preference. This also disables the cancel checkout
function for that business object.

• Display of multivalued properties containing a comma followed by a

space
If a value in a multivalued property contains a comma followed by a space, that
value is shown as two separate values. For example, consider the following
values for a multivalued property:
Cypress, CA
Milford, OH
The values are displayed as follows:

Cypress
CA
Milford
OH

Do not use a comma followed by a space for values that appear in a multivalued
property. It is safe to use a comma without a space, for example:
Cypress,CA
Milford,OH
• Cancel checkout of an ItemRevision instance

When a user cancels a checkout of an ItemRevision instance, changes made
by other users to related data may be discarded if the latest sequence has an
independent copy of this data. This applies to the master form and datasets
referenced by the Specification relation.
Check out related forms and datasets to prevent other users from making
changes while the ItemRevision instance is checked out.
• Properties dialog box checkout operation changes contents displayed

during refresh
When you perform a check out in the Properties dialog box, the dialog box
defaults to the first tab after the dialog box is refreshed.
After checkout, click the desired tab in Properties dialog box again.

• Unable to open text file with Microsoft Word

If you choose File→Open With and attempt to open a text file with Microsoft
Word, Teamcenter displays an error.
Use Notepad, Wordpad, or another text editor to open text files.
• Microsoft Office documents open externally instead of in the Viewer

pane
If you have Microsoft Office 2007 installed and you select a MSWord, MSWordX,
MSPowerpoint, MSPowerpointX, MSExcel, or MSExcelX dataset in My
Teamcenter and switch to the Viewer pane, the document is opened externally
in its application (for example, in PowerPoint) and not embedded in the Viewer
pane.
By default, Microsoft Office 2007 prevents Office 2007 documents from being
embedded in another application. For example, if you try to view a Word
document within Internet Explorer, it opens the document in Microsoft Word
and not within Internet Explorer.
o To enable embedded viewing in Microsoft Windows Vista, you must change

registry settings. For more information, see the instructions at this link:
http://support.microsoft.com/kb/927009
o To enable embedded viewing in Windows XP:

1. Open Windows Explorer.
2. Choose Tools→Folder Options.
3. Click the File Types tab.
4. In the Registered File Types list, select the DOC extension.
5. Click the Advanced button.
6. In the Edit File Type dialog box, ensure that Browse in same window
check box is selected. Click OK.
7. Repeat steps 4 through 6 for the DOCX, PPT, PPTX, XLS, and XLSX
extensions.

• Clicking the Save button in Viewer pane does not save dataset
(First published Teamcenter 2007
If you edit a Microsoft Word dataset in the My Teamcenter Viewer pane and
click the Save button on the Word toolbar within the Viewer pane, the changes
are not saved to the dataset.
Click the Save button at the top of the Viewer pane. The Save button on the
Word toolbar within the Viewer pane saves the document to the client machine
but not the dataset.

NX Integration
The following release notes pertain to use of NX Integration and Teamcenter

Integration for NX.
• NX component is not visible in preview
Occasionally while adding a component using the By Constraint positioning
option, the preview window goes blank when the assembly constraint dialog box
is launched. This prevents the user from making any selection in the preview
window to create assembly constraints between the newly added component and
the existing entities in the workspace.
There are two workarounds for this issue:
o Perform a View Fit (Ctrl+F) on the component preview window. The

components to be added are visible in the preview window.
o Turn on the Preview Component in Main Window option in the assembly

constraint dialog box. The components to be added appear on the main
graphic window. To create assembly constraints, make the selection directly
from the main graphics window.
• Error launching NX
When you have the NX Integration installed and you first attempt to launch
NX, the following error is displayed:
SOA: Failed to find property file(s). See log file.
When NX is upgraded to the next version, the property policy files in Teamcenter
also need to be upgraded. These files enable NX Integration to work correctly.
The upgrade must be performed with every release of NX, including maintenance
releases.
Copy the SOA properties files from NXto Teamcenter. In NX, copy all the
UGII_BASE_DIR\UGMANAGER\NxManager*.xml files to the Teamcenter
TC_DATA\soa\policies folder. This update can only be done by the Teamcenter
administrator who has privileges to update the TC_DATA directory.
Note Some files should be overwritten in the TC_DATA/soa/policies folder. If
these files are not replaced in Teamcenter, the error persists.

• Download hyperlink is not available after exporting an NX assembly

If you export an NX assembly in the thin client using the Sun Java System
9.1 application server with Internet Explorer, the Export Status window is not
updated with the Download hyperlink when the operation is complete. Also, if
the export request is terminated, the dialog box is not updated.
Use an application server that does not run on Sun Java System 9.1.
• Download hyperlink is not available for the first subassembly if a

second subassembly is exported too soon
If you export a second NX subassembly before the first subassembly export has
completed in the same Structure Manager window, the Export Status window is
not updated with the Download hyperlink for the first subassembly.
Either wait for the first subassembly export to finish before attempting to export
the second subassembly or export the assembly that contains both subassemblies.

PLM XML
The following release notes pertain to PLM XML import and export.
• Avoiding checking the expired or locked status at TIE import
When transferring Global Multi-Site data from Teamcenter Enterprise to
Teamcenter, the license cannot be attached because the license is locked or
expired.
Add the GMS_expired_or_locked_ada_licenses_bypass site preference to
bypass checking the license locked or expired status when performing Global
Multi-Site (TIE) import. If the preference value is set to true, the license locked
or expired status is not checked and the license is attached to the object.
• Database upgrade may fail at tcxml_import step when importing scope

rules (TC_DATA/defaultTransfermodes.xml)
When upgrading to Teamcenter 9.1, if the GMS_tcxml_string_separator
preference is set to something other than a comma (default value), the scope
rules import and upgrade may fail. This preference is used to specify a separator
for strings in TC XML import. For default scope rules .xml files, the separator
should be a comma.
Before starting the upgrade to Teamcenter 9.1, check to see if the
GMS_tcxml_string_separator preference exists in the database. If it does,
delete it temporarily. After the upgrade completes, you can reset the preference.
Project
The following release notes pertain to Project.

• Cannot remove an object from a project
You cannot remove an object from a project (for example, the owning project) if
the project is autoassigned during object creation.
Set the TC_allow_remove_owning_project site preference to true. This
preference allows users to remove the owning project attribute.

Query Builder
The following release notes pertain to the use of Query Builder.

• Customizing quick search query names
The list of available quick searches is missing the General... query.
You can add any query names to the quick search list by updating site
preferences.
1. Log on to Teamcenter as a dba user.
2. Choose Edit→Options→Search.
3. Edit the following preference

o In the Quick_Access_Queries preference, add the custom query name
(for example, add General...).
o In the Quick_Access_Queries_Attribute preference, add the custom

query search attribute using the following format:
query-name_SearchAttribute=search-attribute
For example, to add , use the following format:
General..._SearchAttribute=search-attribute
• Indented search returns incorrect results

Indented searches return incorrect results when the query has complex clauses.
For example, if a dataset is attached to several item revisions, searching from
the item revision to the dataset works, but the reverse traversal does not return
the correct result.
Avoid adding more than one query parameter during a reverse traversal search
(that is, while defining a query, do not add more than one query criteria).

Repeatable Digital Validation

The following release notes pertain to Repeatable Digital Validation (RDV).
• Save button in Platform Designer is not enabled consistently when the
design is added to an architecture breakdown element
The Save button in Platform Designer is not consistently enabled when the IA
(Design) is added to the architecture breakdown element (ABE). This issue is
not consistently reproducible.
Change the focus from the Platform Designer perspective, and then return
to the Platform Designer perspective. The system prompts you to save the
modifications when you exit Platform Designer.
• Automatic population of Part Data does not work in the Add Part To
Product dialog box when localization template is applied
The option to autopopulate fields in the Part Data pane in the Add Part To
Product dialog box does not work when a localization template is applied.
Add the value manually. You can then proceed to the Architecture Breakdown
dialog box.
• ClearanceExe fails
When the ObjectUnloadable business object constant on Variant and
VariantRevision business objects is set to true, the ClearanceExe execution
fails.
Follow these steps to set the ObjectUnloadable business object constant to
false for the Variant and VariantRevision business objects in the Business
Modeler IDE:
1. Create a new project in the Business Modeler IDE or use the existing custom
project.
2. Add following entry in, for example, the objunload.xml file:

<TcTypeConstantAttach constantName="ObjectUnloadable" typeName="Variant"
value="false" />
<TcTypeConstantAttach constantName="ObjectUnloadable" typeName=" VariantRevision"
value="false" />
3. Save the objunload.xml file and reload the data model.
4. Verify that the ObjectUnloadable business object constant property is set

to false for the Variant and VariantRevision business objects.
5. Deploy the template. For example:

business_model_updater -process=add -file=objunload.xml -log=log.txt

Report Builder
The following release notes pertain to the use of Report Builder.

• Upgrading standard Report Builder reports
Because of possible customization loss, the upgrade process does not
automatically upgrade standard Report Builder reports.
1. Back up report definitions using the import_export_reports utility with

the -export argument. This exports one report definition at a time:
import_export_reports -export
-u=user-name -p=password -g=group
-stageDir=${TC_DATA}/crf -reportId=REPORTID
If you have style sheet customizations, you can save them with using Report
Builder by opening the style sheet and saving to a local hard drive.
2. Update all standard reports using following command:

import_export_reports -import -overwrite
-u=user-name -p=password -g=group
-stageDir=${TC_DATA}/crf -reportFile=${TC_DATA}/crf/CrfReports.xml
Reporting and Analytics
The following release notes pertain to Reporting and Analytics:

• Password confirmation on change profile page
If you save the Reporting and Analytics logon password when asked by the
browser (if the save password feature of the browser enabled), a problem may
occur on the change profile page. The browser asks you whether you want to
change the password stored in the browser memory even if you do not change
the password.
Do not change the password when asked by the browser on the change profile
page unless you have really changed the password. If you save the password, the
browser stores the wrong password in its memory. In this case, your next logon
to Reporting and Analytics fails if you rely on a saved password.

• Inconsistent list of databases when creating WAR file

While creating a WAR file from Teamcenter Environment Manager (TEM) on
Teamcenter 9 (drop 2011061500) on Windows, the Reporting and Analytics
databases are displayed as Oracle and SQL Server on the menu. On SUSE
Linux, they are displayed as IBM DB2 and Oracle.
To reproduce the problem:
1. Log on to Windows or SUSE Linux machine and run TEM.
2. In the Features panel, select Reporting and Analytics→Teamcenter for

Reporting and Analytics.
3. Select the Create WAR File option and continue with the installation.
4. In the TcRA Database Selection panel, the following options are displayed
in the Database Engine box:
o Windows systems
Oracle and MS SQL Server
o SUSE Linux systems

DB2 and Oracle

Use eQube’s stand-alone installer to install Reporting and Analytics for DB2.
For instructions about using this installer, see the eQube deployment guide,
which can be found in the download area for Reporting and Analytics on GTAC.
Following is an overview of the instructions for using the eQube installer:
1. Download the TCRA.zip file and the deployment documentation from GTAC.
2. Unzip the TCRA.zip file.
3. Launch the eQube installer using the ../Installer/install.bat file.
4. For further instructions, see the eQube deployment guide.
• Cannot open a report from the rich client using Firefox

If multiple reports are launched from the rich client in the same browser, they do
not appear when using Firefox.
When a report is launched from Teamcenter with Firefox as the default browser,
log out from Reporting and Analytics before launching the next report.

• Attribute search problem

In Semantic Mapper, when an attribute is searched in the cube creation wizard,
if you clear the attribute in the search and attempt to search gain, you cannot
select a new attribute using the mouse.
Select an attribute using the keyboard or go back to the previous page and start
over.
• Scheduled tasks do not appear in BuildNPlay

After viewing the results of any report in the BuildNPlay application, add new
tasks to the schedule in the Teamcenter Schedule Manager application. When
you refetch the report from the BuildNPlay application, the new tasks are not
shown.
Close the session and launch a new BuildNPlay session to view the updates.
• Filter conditions are not working properly

If the Saved Query option is selected as a source object for a report, and the
ISNULL or IS NOT NULL filter values are applied, the report does not return
any values.
Save the report definition, and while saving do not select these operators. When
users of the report run the definition, they do not see nonfunctioning operators.
• != and IS NULL operators do not work when running saved queries

for a Teamcenter 2007 connection
The != and IS NULL operators do not work when running saved queries for a
Teamcenter 2007 connection. They do not work in ad-hoc flow from BuildNPlay
because saved queries work only for the = operator.
The administrator should select only the = operator when saving the report
definition build on saved queries.

• All operators appear in the interface for both saved and database
queries
All operators appear in the interface for both saved queries and database
queries, even though only the = operator works for saved queries.
The administrator should select only the = operator when saving the report
definition build on saved queries.

Resource Browser
The following release notes pertain to usage of Resource Browser.

• Resource Browser does not support mixed unit classes
Resource Browser does not support mixed unit classes. If Classification data
is stored in a mixed unit class using nonmetric units (for example, inches),
Resource Browser displays the nonmetric values as they were stored, but shows
them followed by the metric unit symbols (for example, mm).
If working with nonmetric Classification objects in mixed unit classes, you may
ignore the displayed metric symbol names and assume the same nonmetric
symbols apply as used as in Classification when storing the data.
Resource Manager
The following release notes pertain to usage of Resource Manager.

• Guided component search connection points are invalid
When performing a Save As operation on a classified workspace object with
guided component search connection points, the connection points are copied to
the new workspace object but are invalid in the new workspace object’s context.
This can be verified by right-clicking the connection points in the new workspace
object and choosing Guided Component Search from the shortcut menu. The
following message is displayed:
No GCS CP ICO tag found for occurrence

Remove the invalid connection point lines from the workspace object bill of
materials using the Remove a line (Ctrl R) button on Resource Manager toolbar,
and save the workspace object without the old connection points. New valid
connection points are created during the Save operation.

• NX part attributes fail for NX Integration

When you execute NX Integration functions in Teamcenter, part attributes are
not written into the part file.
When you use the MRM NX Integration functionality, the part attributes are
written into the NX part file. You can synchronize those attribute values from
NX to Teamcenter, but this does not work automatically.
1. Export the attribute mapping definition from the database:
export_attr_mappings -file=attr_mappings.txt
-u=admin-user-name -p=password -g=dba
2. Modify the text file and add the following three lines (for setups X, Y, and Z):
CAM_TOOL_ATT_X : ItemRevision.ICS(-45002:1) /master=both
CAM_TOOL_ATT_Y : ItemRevision.ICS(-45003:1) /master=both
CAM_TOOL_ATT_Z : ItemRevision.ICS(-45004:1) /master=both
to the following block in the text file:
{ Dataset type="UGMASTER"
# (hard-wired) DB_PART_NAME : "Part Name"
# (hard-wired) DB_PART_DESC : "Part Description"
CAM_TOOL_ATT_X : ItemRevision.ICS(-45002:1) /master=both
CAM_TOOL_ATT_Y : ItemRevision.ICS(-45003:1) /master=both
CAM_TOOL_ATT_Z : ItemRevision.ICS(-45004:1) /master=both
}
3. Save the text file and import it back into the database to define the attribute
synchronization:
import_attr_mappings -file=attr_mappings.txt
-u=admin-user-name -p=password -g=dba
When you now execute the NX Integration functions in Teamcenter, the part
attributes are written into the part file. When you save the part file in NX, the
attribute values are transferred to Teamcenter. When you reload the resource
in Teamcenter, the new values are displayed there.
Schedule Manager
The following release notes pertain to usage of Schedule Manager.

• Multi-Site functionality is not supported for Schedule Manager
Schedule Manager functionality fails when working with remote data.
Do not use Multi-Site functionality with Schedule Manager. This capability
is not supported.

• Schedule Tasks folder name under My Worklist is not localized in the

rich client
In the rich client, the Schedule Tasks folder name under My Worklist is
displayed in English in all locales.
The Schedule Tasks folder under My Worklist is always displayed in English
because it is not localized in the rich client. However, in the thin client, the
Schedule Tasks folder name is displayed correctly in all locales.
• LOV values show in integer format in audit logs for Schedule Tasks
Audit Manager logs show the internal integer values for Schedule Task LOV
properties instead of string representations of integer values.
Currently, there is no workaround for this problem. The impact of this issue is
minor and affects only audit logs in which internal values are shown.
• Certain properties for the summary task in the Properties dialog box
cannot be modified in Schedule Manager
Certain properties for summary tasks in the Properties dialog box cannot be
modified. For example, the Description box cannot be modified.
Certain properties like description can be updated through inline editing on the
task tree in Schedule Manager.
• Problem viewing the subschedule calendar from the master schedule

You cannot view a subschedule calendar from within a master schedule. Only
the master schedule calendar is available.
Load the subschedule separately in the Schedule Manager to view the calendar.
To update the calendar, the master schedule and subschedule relationship
should be unlinked, updated, and relinked.

Specification Manager
The following notes pertain to usage of Specification Manager.

• Specification transfer from Interspec to Teamcenter fails if the
PS_Find_Number_Validation preference is set to true
The PS_Find_Number_Validation preference determines whether Teamcenter
validates find numbers.
Specifications transferred from Interspec to Teamcenter do not have find
numbers. If this preference is set to true, you get an error when the find number
is zero or not unique within the parent structure.
You can perform either of the following steps:
o Set the PS_Find_Number_Validation preference to FALSE.
o If you want the PS_Find_Number_Validation preference value set to

TRUE, create a new preference as follows:
Preference name: PS_Allow_Null_Find_Number
Preference type: Logical
Preference value: TRUE
• Base Name type not supported

The Interspec integration with Teamcenter does not support transfer of
specification sections of the Base Name type.

Structure Manager
The following release notes pertain to Structure Manager.

• Run in Background duplicate operation creates incorrect link in e-mail
When Subscription Manager is turned ON and the Run In Background
duplicate feature in Systems Engineering is selected, the asynchronous system
sends a notification processed by the Subscription Manager with a link to the
DispatcherRequest object. Because the DispatcherRequest object is deleted
quickly, clicking the URL in the notification displays an error.
Check for the newly created item in the Teamcenter mail folder and do not click
the DispatcherRequest URL.
• com.teamcenter.rac.pse.PSEAppplication.MRUEntries preference is
created with wrong site scope
The com.teamcenter.rac.pse.PSEAppplication.MRUEntries preference is
created at run time in a Teamcenter rich client session. Normally, it is created
with user level protections. Under certain circumstances, you can create the
com.teamcenter.rac.pse.PSEAppplication.MRUEntries preference with
site-level protection that can cause error messages and potentially undesired
results.
You can manually delete the
com.teamcenter.rac.pse.PSEAppplication.MRUEntries preference. It will
be created with the expected user-level protection in subsequent instantiations.
• Internet Explorer in the thin client issues Stop running this script?
prompt
This problem is specific to Microsoft Internet Explorer (IE) while using the thin
client. For certain operations that require more processing, the IE browser
responds with the following prompt:
"Stop running this script? A script on this page is causing your web browser
to run slowly. If it continues to run, your computer might become unresponsive."
[yes] [no]

Download the fix from the Microsoft site:
http://go.microsoft.com/?linkid=9729250
After installing the fix, the dialog box is not visible.

• Incremental change icon not displayed after form checkout and edit
The incremental change icon is not shown on item revision master forms after
you edit them using shortcut menu commands. To reproduce the problem,
perform the following steps:
1. Create an item in Structure Manager.
2. Create an incremental change context.
3. Open the data pane with the Attachments tab available.
4. Right-click the item revision master form and choose Check Out.
5. Right-click the item revision master form and choose Properties.
6. Edit some property, save the item, and check in.
The incremental change icon is not shown next to the item revision master form
as expected.
Double-click the item revision master form and check it out. Edit it, save it, and
then check it in. The incremental change icon is shown next to the item revision
master form as expected.
Note This procedure assumes the Incremental_Change_Management
preference is set to true.
• Unable to remove BOM lines in detached Structure Manager view

Removing a BOM line does not work in the Structure Manager view.
1. Open the Structure Manager view in My Teamcenter.
2. Send a part to the Structure Manager view.
3. Detach the Structure Manager view from My Teamcenter.
4. Drop another part in My Teamcenter onto the BOM line in the Structure
Manager view to create a structure.
5. Remove the child from the structure. Observe the child is not removed.

To remove a BOM line within a detached Structure Manager view, select the
BOM line in the detached Structure Manager view and then press the delete key.

• Upgrade failure on database with PIPMEAPPEARANCE_3 index set as

unique
If you have a database with the PIPMEAPPEARANCE_3 index set as unique
in the database to be upgraded, you may encounter errors during upgrade.
If the PIPMEAPPEARANCE_3 index is not defined, or it is defined as a
non-unique, the upgrade should proceed normally.
If you have a unique apn_occ_root_ind index (a PIPMEAPPEARANCE_3
index), remove the unique index before upgrading to Teamcenter 10.1, and then
replace the nonunique index with a unique index after the upgrade completes.
If you have a nonunique apn_occ_root_ind index, these steps are not necessary.
1. Type the following command to drop the apn_occ_root_ind index before

upgrading toTeamcenter 10.1:
install -drop_index -u=infodba -p=password -g=dba
"MEAppearancePathNode" apn_occ_root_index
2. Upgrade to Teamcenter 10.1.
3. Drop the nonunique index installed during the upgrade process by typing
the following command in the upgraded environment:
install -drop_index -u=infodba -p=password -g=dba
"MEAppearancePathNode" apn_occ_root_index
4. Create a unique apn_occ_root_ind index by typing the following command

in the upgraded environment:
install -add_index -u=infodba -p=password -g=dba apn_occ_root_index
1 "MEAppearancePathNode" occ_thread parent path_root
NONE:apn_occ_root_index:0:MEAppearancePathNode:occ_thread,parent,path_root
• Auto VI process messaging is updated

Auto VI processing was performed as a Depth-First Search (DFS) in Teamcenter
9.1 and earlier versions. This means children of the first subassembly under the
top line are processed before the second subassembly in the structure.
In Teamcenter 10 and later versions, the order of Auto VI processing of lines is
enhanced to take advantage of bulk processing in some cases. BOM lines are
now processed in order of level in structure. Teamcenter 10 uses a Breadth-First
Search (BFS) algorithm. This means all valid modules in the first level in the
structure are processed first, then the second level module, and so on.

When the PSEAutoVINewItemPopup preference is set to false, all valid

modules in a level are processed in bulk to improve performance as well as
reduce chattiness. However, when the PSEAutoVINewItemPopup preference
is set to true, bulk processing is not done.
• Missing information in baseline or duplicate error messages

There is a limitation in the baseline and duplicate error handling code.
Sometimes, certain error messages miss some dynamic information. For
example, if the baseline or duplicate operation fails with an occurrence condition
validation, the condition name is missing in the error message.
Currently, there is no workaround for this problem. This issue does not cause
any data corruption or loss of functionality.
• Saving structures with multiple open windows

When multiple BOM windows with different structures are pending for save,
clicking the Save button saves only the modifications in the active BOM window.
The Save button remains active until all BOM windows having modifications
are individually saved.
This behavior is working as designed. When all windows with modifications
are saved, the Save button is disabled.
• Date properties in Structure Manager

Date properties in Structure Manager show the server time instead of the client
time when using a rich client in a different time zone than the server. By default,
there are no date properties on BOM lines, so this behavior is seen only on
custom date properties.
Right-click and choose View Properties to see the correct client time and date
on date properties in Structure Manager when using a rich client that is in a
different time zone than the server.

• Modifications to BOM reports

The BOM report is blank when the BOM is made up of design objects.
Perform one of the following:
o Perform the following steps to generate reports if your environment has been
upgraded from Teamcenter 2007 or 8.x to Teamcenter 9.1:
1. Create a file named ModReports.xml with the following content and
store it in the TC_DATA directory:
<?xml version="1.0" encoding="iso-8859-1"?>
<OOTBReports>
<reportdefinition id="crf_itm_rpt_id3" domain="bom"
specification="TC_2007_00_ITM_RPT_0003.xml" />
</OOTBReports>
2. Execute the utility import_export_reports utility as follows:

import_export_reports -u=infodba -p=<> -g=dba -stageDir=%TC_DATA%\crf
-reportFile=%TC_DATA%\crf\ModReports.xml" -overwrite
o Perform the following steps to generate reports for any custom item types.
(The Item, Part, and Design types are already supported.)
1. Update the TC_2007_00_CrfPSBOMReports property set with
required clauses for new item types.
2. Make changes to the following style sheets and update the corresponding
datasets with the updated XSL files. Existing style sheets have changes
for Part and Design and the same objects can be extended for the new
item type. In My Teamcenter, use the General... search to find the
following datasets and update the style sheets:
XSL file Style sheet dataset name

ps_bom_report_html.xsl CrfHtmlStyleSheet
ps_bom_report_excel.xsl CrfExcelStyleSheet
l10n_ps_bom_report_html.xsl CrfHtmlStyleSheet
l10n_ps_bom_report_excel.xsl CrfExcelStyleSheet

• Clear Repositioning check box removed from the Product View Gallery
dialog box
The Clear Repositioning check box in the Product View Gallery dialog box is
no longer available when applying product views. The positions are always
applied relative to the positions stored in the Teamcenter structure, which was
the previous default behavior.
The option that controls whether or not to clear repositioning when product
views are applied is removed. The default behavior to clear repositioning before
applying a product view is now the only behavior supported. The product view
positioning always applied relative to the positions stored in the Teamcenter
structure, and any temporary repositioning set within the current viewer session
(that have not been saved to Teamcenter) is ignored when the product view is
applied. This has been the default behavior for many releases, and is now the
only behavior supported.
• Manufacturing Process Planner application refresh problem with

in-context overrides
If you are in the Manufacturing Process Planner application and create a new
product structure, apply in-context overrides to the structure, and then revise
the in-context line of the structure, you encounter a refresh issue with the
overrides on the revised structure. This problem only occurs when doing all
the steps within the same Manufacturing Process Planner session. Already
established data does not encounter this refresh problem.
If the in-context data is missing after a revise, choose View→Refresh Window
and the in-context information is loaded.
• Copying data during variant item creation is controlled by preferences

During variant item creation, absolute occurrence data, appearance path nodes
(APNs), and arrangements are copied by default. This causes performance
problems.
Absolute occurrence data, appearance path nodes (APNs), and arrangements are
not always required during variant item creation. Copying them to the variant
item is now controlled through preferences.

To change the default behavior during data item creation, create the following
preferences as site-level preferences and set them as described.
Preference Description
PSECreateVISameType If you want to allow NX
arrangement data to carry
forward during variant item
creation, set this preference to
False.
Note Setting this preference
to False only
enables copying
of arrangements
data. Copying of
NX arrangement
data depends on
the following two
preferences being set
to True.
If this preference is set
to True, absolute
occurrence data
and arrangements
are carried forward
regardless of the
values of the following
two preferences.
PSECopyAbsOccDuringVICreation To carry forward absolute
occurrence data and APNs,
create this site-level preference
and set it to True.
This preference does not carry
forward arrangements data.
PSECopyArrangementsDuringVICreation To carry forward arrangements
data, set this preference
and PSECopyAbsOcc
DuringVICreation to True.
For more information about these preferences, see the Preferences and
• Precise entry removed from Where Used search

The Precise entry option is removed from the Rule combination box that
configures Where Used searches. This option is no longer required because the
Where Used algorithm is redesigned to provide correct results with a rule that
contains only a precise entry.


Use the Precise Only entry option to obtain the desired results. This entry is
obtained from the default revision rule.
• Refresh problem when switching NX arrangements in Structure

Manager
After you import an NX structure into Structure Manager using the Import
Assembly into Teamcenter menu command, you may encounter problems
configuring the NX structure.
Perform the following steps to import a native NX structure into Teamcenter
using the Import Assembly into Teamcenter menu command:
1. Start Teamcenter.
2. Start the NX application from Teamcenter.
3. In NX, import a structure with arrangement data into Teamcenter

(File→Import Assembly into Teamcenter).
Note Assemblies imported into Teamcenter have no arrangement data.
4. In NX, open the Teamcenter structure you imported.
5. In NX, choose File→Force Save All.

Note This step imports the arrangement data into Teamcenter from the
NX part files.

Perform one of the following workarounds.
o Close and reopen the structure in Structure Manager.
o Perform a Teamcenter refresh from NX immediately after you choose the

File→Force Save All command:
1. Perform the recommended steps for importing a native NX structure into
Teamcenter using the Import Assembly into Teamcenter option in NX.
2. In NX, choose File→Close→Close and Reopen Selected Parts.
3. In the Reopen Part dialog box in NX, click the Refresh Teamcenter
Information button.

• Enhancement of the item_to_part_design utility

The item_to_part_design utility was not working due to the core data model
changes from Teamcenter 8 onward.
The item_to_part_design utility was modified in Teamcenter 8.3 according to
the new data model changes from Teamcenter 8 onward.
For a full description of this utility, see the Utilities Reference.
• Form edits in incremental change context

Editing forms for incremental change and reservations features (such as
checkout, checkin, cancel checkout) does not work as expected when you use
the context menu.
While working in incremental change context and form edits, use the Check-Out,
Check-In and Cancel Check-Out buttons available through the form dialog box.
• Teamcenter Duplicate limitations with Pro/ENGINEER data

The Teamcenter Duplicate feature has limitations when used on structures
containing certain types of Pro/ENGINEER data. Until these limitations are
removed in a future version of the Teamcenter Integration for Pro/ENGINEER,
Teamcenter Duplicate must be used carefully on Pro/ENGINEER structures
that contain external references with an assembly context, such as Interchange
assemblies and geometry copied from the assembly level. Such structures should
always be duplicated with the All Dependencies option enabled to ensure that
all necessary models are included in the replica structure.
Structures that contain context-dependent external references should be
duplicated with the All Dependencies option enabled, and the user must not
manually omit any item revision resulting from the All Dependencies setting.
Alternatively, the assembly may be loaded into a Pro/ENGINEER session, and
then duplicated with the integration’s Teamcenter→Save→Replace command.
• Insert Level dialog box does not support special types

The Insert Level dialog box only displays certain types of classes. Any classes
that require special dialog boxes do not appear in the list.
Create the object of the special class, copy the object into the clipboard, choose
Paste Special, and paste the object as a new level above the selected lines. It
performs the insert level.

• Incremental change (IC) context override not seen when change is

made under new IC revision
An incremental change context override does not appear when the change is
made under a new incremental change revision.
While it is possible to revise incremental changes, this makes their analysis
and usability more complex, and Siemens PLM Software does not recommend
this approach.
• Missing refresh after changing properties on multiple objects

If multiple objects are selected and the properties dialog box is opened, properties
are displayed and common properties for the selected objects can be edited. After
making an edit and clicking OK or Apply, the property changes are saved to the
database but are not updated in the dialog box.
Property changes are displayed after choosing Refresh from the menu.
• Structure Manager behavior after four-tier server session time-out

Structure Manager edits are lost if a four-tier server session time-out occurs.
There are four-tier configuration settings that cause a server to time-out if
clients are inactive. If a server times out and is killed, Structure Manager
client-pending changes are lost.
Four-tier administrators should set the time-out in a way that a time-out does
not occur for a server in edit mode. For Structure Manager, this corresponds to
an active SAVE button in at least one BOM dialog box, which represents at least
one Structure Manager session with unsaved changes. The default is 8 hours
for a server in edit mode. If sessions are up overnight, a 24-hour time-out (or
longer to allow for weekends) addresses most issues.

Systems Engineering and Requirements Management

The following release notes pertain to use of Systems Engineering and Requirements
Management.
• Placement of transfer mode rules in an object template
To place a single secondary property between two primary properties, use
transfer modes with properties.
The following example shows an invalid object template:
{%object_name}
{%Rule:Selection.Export.TM.Transfermode}
{%body_text}
The following example shows a valid object template:

{%object_name}
{%body_text}
{%Rule:Selection.Export.TM.Transfermode}
The transfer mode section is always placed after the end of the property section
in the object template.
• Full-text migration XML must be split into multiple XML files

The TcServer process runs out of memory when performing full-text migration
using the req_migrate_fulltext utility with a large PLM XML file containing
50,000 objects.
Split the PLM XML file into files of 10,000 objects each. The size of each file
should not exceed 15,000 objects because a large amount of memory is required
to hold the rich text for each requirement. For example, if you have a PLM XML
file containing 50,000 objects, split the file into 5 files of 10,000 objects each.
Then run the req_migrate_fulltext utility and input the files one at a time.
• Certain characters and symbols appear as question marks in plain text

Characters such as curly quotation marks (“ ”) and em dash (—) are not
displayed in plain text and are replaced with question mark characters (?). This
can cause problems because Microsoft Word automatically changes en dashes
to em dashes, straight quotation marks to curly quotation marks, and so on.
These text characters also do not appear in the names of requirements, plain
text, and similar areas.
Microsoft Word allows you to type and save characters outside the ISO 8859-1
character set. These characters cannot be safely stored in a database running in
the ISO 8859-1 code page. If your server is running in the ISO 8859-1 code page
(that is, the TC_CHARACTER_ENCODING_SET environment variable is set
to ISO 8859-1), some characters that are entered in Microsoft Word such as curly

quotation marks, em dash, and so on, cannot be stored safely in the database.
Also, such characters cannot be displayed in the Teamcenter user interface.
To view these characters, you must do one of the following:
o Use a rich text application like Microsoft Word.
o Use CP1252 encoding; that is, run the server on Windows and use a database
compliant with CP1252 encoding.
o Use UTF-8 encoding for server and database.

Note Characters that cannot be displayed and stored safely in the ISO 8859-1
code page are converted to question marks (?).
• Object templates determined by precedence when creating new

requirements in live Word
When creating a new requirement in a live Word document, the object template
Teamcenter uses is determined by precedence of object templates.
If you attempt to create a type of object that already exists in the structure,
Teamcenter creates the new object using the object template used to export
that type of object.
If you attempt to create a type of object that does not exist in the structure,
one of the following may occur:
o If the object template override for the selected object type exists, the object
template override is used.
o If the object template override does not exist (is not defined), the object
template specified by the REQ_default_object_template preference is
used.
• Rich client client hangs when exporting a large BOM

The rich client client may hang when exporting a large BOM structure (for
example, 3,000 lines) to live Word using the option to check out objects before
export.
Increase the Java virtual memory:
1. Locate the directory where the rich client is installed.
2. Locate the otwportal.bat file.
3. Locate the VM_XMX setting and set it as follows:

VM_XMX=1024m

• Import specifications do not support documents with external

references
Import specifications do not support documents with external references.
External references refer to files on a local disk and can refer to files of any type,
such as a document, image, or Microsoft Excel spreadsheet. These external
references must be removed before importing.
Locate external references in a document, remove the external references, and
then import the document again.
To remove external references from Microsoft Word 2010 documents, perform
one of the following procedures.
o External references in document content

1. Open the Microsoft Word document.
2. In the File tab, choose Edit Links to Files. Word displays a dialog box
that shows all external links within the content of the document.
3. Select a link in the dialog box and click the option to break the link.
Do this for all links to external references.
4. Save the document.
o External references to a document template on the local machine

1. Open the Microsoft Word document.
2. In the File tab, choose Options®Customize Ribbon.

Select the Developer check box.
3. Click OK.
4. In the Microsoft Office ribbon, choose Developer®Document Template.
5. In the Templates and add-ins dialog box, select the attached document
template that is on the local machine, and then remove that path.
6. Click OK.
7. After the external reference to the document template is removed,

Microsoft Word attaches the normal document template.

• Importing a requirements document with a keyword

When a keyword is supplied that is part of a heading or a paragraph that has
an outline applied, all objects that are created from the imported requirements
document are created as paragraphs instead of as a user-specified requirement.
To split the requirement based on keyword parsing, use keywords that are part
of the containing text or the body text paragraph.
• Microsoft Office primary interop assemblies (PIA)

Microsoft Office 2007/2010 primary interop assemblies (PIA) must be installed
for the flat file import to work correctly.
Teamcenter installation programs no longer install Microsoft Office PIA libraries
automatically or prompt you to install them. You must install these before you
install Systems Engineering and Requirements Management.
Install the appropriate Microsoft Office PIA libraries (for Microsoft Office 2007 or
2010) before you install Systems Engineering and Requirements Management.
• Markup support in Systems Engineering and Requirements

Management
When you perform an Export for Markup operation, the specification is exported
to Word, but the content controls for properties other than body text are
read-only.
Currently, there is no workaround for this problem. Markups are supported
only for the body text property of the specification element revision in Systems
Engineering and Requirements Management. So when you export a specification
to Word in markup mode, the property content control other than body text
is read-only.
• Export To Word dialog box selection list

In the Export to Word dialog box, you can select different data types under the
Override Object Template for list. The list displays many different data types
that you may not want to display.
Use the new Word_Export_TcTypes preference to define the list of types whose
child types display in the Override Object Template for list.

• Performance problems when loading POM long strings

Whenever business objects contain properties with a POM long string, it can
cause performance problems when accessing those properties.
The Requirement business object references FullText business objects that
store rich text in POM long strings. All use cases related to loading of FullText
or Requirement business object instances can impact performance.
In Teamcenter 9.1, the TC_LSBLT_SIZE environment variable was added,
which specifies a size threshold for loading long strings. By default, the threshold
is 1K. All of the long strings for a set of objects less than the threshold in size are
loaded together in a bulk load. This can produce many SQLs in the database.
If you increase this threshold to 6K, fewer POM long string queries are produced
in the database, therefore enhancing performance. You can set the environment
variable at the server to optimize loading of POM long string as follows:
set TC_LSBLT_SIZE=6000
• Occurrence trace links

When you select a trace link from a trace report and click the Go To Object
button, the trace link is opened in My Teamcenter showing the primary and
secondary objects as children under the trace link. For occurrence trace links, a
? symbol is shown because these trace link primary and secondary objects are
absoute occurrence types and are not supported for display in the rich client.
Note If the trace link is a workspace object link and the primary and secondary
objects of the trace links are workspace objects, the rich client properly
shows those reference objects as children of trace link.
You can see same behavior if you open the Properties dialog box for occurrence
trace links.
Use a tracebility report to see primary and secondary objects of occurrence trace
links.

• Requirements Management template does not support custom

document properties
If you import a Microsoft Word document that has a custom document property
as a specification template, and then export the objects to Word using this new
specification template, a corrupt document is generated.
Microsoft Word displays an error if you import a template with a custom
document property.
• Some subclasses are not displayed in the MATLAB integration

Open/Insert dialog box when Classification tree nodes are expanded
In the MATLAB integration, in the Classification pane, when you select the
Open/Insert menu command, the Behavior Model libraries tree is displayed.
When you expand the nodes in this tree, some subclasses displayed in
Teamcenter are not displayed in the Open/Insert dialog box. The tree displays
only classes and groups if the library type for the selected class or its immediate
parent is set to Behavior Model. For classes whose library type attribute is not
set, the models in these classes are still displayed in the Open/Insert dialog
box when the parent classes are selected. However, its classification properties
are not displayed.
To display all the subclasses in a Behavior Model library in the Open/Insert
dialog box, the Classification administrator must set the library type attribute
for each class that needs to be displayed in MATLAB integration dialog boxes to
the Behavior Model library value. This is done by selecting Behavior Model in
the library type LOV.

• Rich client commands do not work with the Traceability Report dialog
box
The Traceability Report dialog box does not honor keyboard commands in the
same way the Traceability Report view does. If you select anything from the
Traceability Report dialog box and try to release the selected components using
the File®New®Workflow command or by using Ctrl+P, the new workflow
process is not launched. If you do the same from the Traceability Report view, it
works fine and launches the new workflow process dialog box for the selected
trace link objects.
The Traceability Report dialog box is static view of traceability. Commands
available on this dialog box only work for the selections from this dialog
box. Commands outside of this dialog box that are from the rich client are
only considered for the selections from the rich client, not for selections in
the Traceability Report dialog box. You can see the same behavior for the
View®Properties dialog box.
To get other commands to work with selections from the traceability report,
select the Traceability Report view, which is installed with Systems Engineering
and Requirements Management. The current behavior of the Traceability Report
dialog box is as designed. The commands that are in context of the dialog box
(accessed from the traceability report toolbar and the popup menu only work for
the Traceability Report dialog box selections. Other commands from the rich
client do not work for those selections from the dialog box but can work with
Traceability Report view selections.
• Microsoft Word and Excel regular expressions differ for flat file add-ins
The wildcard expressions used for Microsoft Word and Excel are not consistent.
When you use a wildcard expression such as an asterisk (*) to match the strings
for ID formation, the Word add-in can find the strings correctly, but the Excel
add-in cannot.
In Excel, use a period before the asterisk (.*) as the wildcard expression.
Teamcenter uses .NET regular expressions to find text in Excel cells, while the
Word API provides its own regular expressions to do pattern matching. Using
the period before the asterisk appears to be one of the differences in regular
expressions between .NET API and Word search API. The expression strings in
Word and Excel configuration files are not meant to be compatible or reusable.

• Creating an icon for use in the Systems Engineering and Requirements

Management BOM view
You cannot change an icon based on a property value. This occurs when using
the Fnd0Icon business object constant in the Business Modeler IDE to change
an icon for a property on a Requirement business object type.
Perform the following sample steps in the Business Modeler IDE to set the
icon property rendering for use in the Systems Engineering and Requirements
Management BOM view. In this example, add a b4_RiskPriority property
(display name Risk Priority) on the revision business object. Attach a
RiskPriorityLOV list of values to the property that has the High, Medium,
and Low values. The icon changes based on the property selection.
1. Import the icons to use (for example, B4_Normal.png, B4_Low.png,
B4_Medium.png, B4_High.png).
2. Create the B4_RiskReq business object as a child of the Requirement

business object.
3. Add the b4_RiskPriority property to the B4_RiskReqRevision business

object type.
Note The property should be string only.
4. Create the B4_PriorityRiskLOV LOV with the Low, Medium, and High
values and attach it to the b4_RiskPriority property.
5. Attach the Fnd0Icon business object constant to the B4_Normal.png icon

on the B4_RiskReqRevision business object.
6. Create a property renderer called B4_RiskPR.
7. Add the following render definition:

<?xml version="1.0" encoding="UTF-8"?>
<icons Version="1.0">
<propertyMap name="PriorityRiskMap">
<item key="High" value="B4_High.png"/>
<item key="Medium" value="B4_Medium.png"/>
<item key="Low" value="B4_Low.png" />
</propertyMap>
<primaryIcon source="B4_Normal.png"/>
<overlayIcon source=" b4_RiskPriority " mapName=" PriorityRiskMap " />
</icons>
8. In the Property Renderer Attachments box, attach

the business-object.object_string, in this case,
B4_RiskReqRevision.object_string.
9. Create a compound property pointing to the

B4_RiskReqRevision.b4_RiskPriority property called
RiskPriorityBOM on the Fnd0RequirementBOMLine business object.
10. Save and deploy.

In Teamcenter:
1. Add the B4_RiskReq business object to the

TcAllowedChildTypes_RequirementSpec preference.
2. Create a requirement specification and add three B4_RiskReq

requirements.
3. Add the RiskPriorityBOM property to the requirement BOM view.
• Problems using the Compare Content dialog box

Switching between the original and revised document can cause incorrect results
when comparing content using the Compare Content dialog box.
The generated compared document has a section for the original document
that shows contents of an object or specification from which you have started
comparison from Teamcenter using the Start Compare or Compare with Prior
commands. The section for the revised document shows contents of an object or
specification where you have selected the End Compare command (or contents
for the prior revision in the case of a Compare with Prior use case).
• Compare with Prior command does not compare with correct

predecessor
The Compare with Prior command does not compare the latest revision with an
exact prior revision of it in the tree.
For example, running the Compare with Prior command on RevD in the
structure compares with RevA instead of RevC.
The Compare with Prior command works based on the basedOn property.
The command compares the latest selected revision with the revision from
which it is derived. For example, if revision D is derived from revision A, the
Compare with Prior command shows a comparison between RevD and RevA
but not with RevC:
000163/A;1-RequiremenSpec1 (View)
REQ-000072/A;1-Req1-RevA
REQ-000073/D;1-Req2-RevD
If RevD is derived from RevA, it is irrelevant to compare RevD with RevC:

REQ-000073/A;1-Req2-RevA
REQ-000073/D;1-Req2-RevD
REQ-000073/C;1-Req2-RevC
Therefore, the Compare with Prior command is working as designed, because

it compares the latest selected revision with the revision on which it is based
or from which it got derived.

• Creation of item revisions is not supported using the Excel Import

wizard
Creation of item revisions is not supported using the Excel Import wizard. The
wizard crashes instead of giving an error.
To update properties on revision objects, first create the item and then export
revision objects from Teamcenter using the Work Offline and Import mode.
This behavior is by design and is applicable to all Teamcenter versions.
• Live Excel causes crash after session change and export

If you change the session parameters like user role, group, and so on, and then
export to live Excel and edit the session-based LOVs, the server is disconnected.
Log on to Teamcenter once more and export the same objects again to live Excel.
The behavior works correctly.
• Microsoft Office add-ins for flat file import

The Microsoft Office add-ins are not available to all users on the host where
they are installed.
An administrator must install the add-ins.
Users without administrative privileges cannot install these add-ins. There is
no option available to users to allow them to install the add-ins individually.
Add-ins always must be installed with the All Users option.
• Applying styles to bullets and numbering in an empty content control

When you apply bullets or numbering to an empty content control, the bullet
or numbering style is outside content control. This is the default behavior of
Microsoft Word.
1. Apply bullets or numbering to an empty content control.
2. Enter text in the content control and press Enter.
3. Microsoft Word automatically adds the next bullet or numbering style.

The previous style comes within content control.

• No error message when generating a report with the Office Live option
if live Excel is not installed
When you attempt to generate an live Excel sheet or an live Excel report, the
report is not displayed and no error message describes why the report did not
appear. An error message should appear stating that live Excel is not installed.
The following are prerequisites for live Excel or live Excel (Bulk mode):
o Excel 2007 or 2010.
o Teamcenter extensions for Microsoft Office should be installed on the client

machine.
The following are prerequisites for live Word:

o Word 2007 or 2010.
o Client for Office should be installed on the client machine.
If you are performing any live Excel or live Word operation without these
prerequisites, then no error appears.

• Markups are not supported when exporting intermediate BOM lines

to Word
Selecting a top specification and exporting it for markup works correctly. But if
you select an intermediate BOM line that has markup and attempt export it,
the markup is not displayed.
Export the top BOM line.
• Client-side validations for live Word

There is no validation on the client if you have any problem with user input in a
live Word document (for example, you enter text in a numeric property box).
In addition, the default placeholder text is displayed when you export an empty
property. This text is set on the server and is in English only. This poses a
problem for non-English clients, such as Japanese.
The client now validates the basic input with Word itself and shows a message
similar to the following if you enter invalid text: Value ’XYZ’ is not an Integer.
If you enter invalid data, the client validates basic data entered and reverts to
the old value or placeholder text as applicable.
Examples of invalid data are a string entered in an integer property content
control or plain text entered in a date property content control.
For empty properties, an asterisk (*) is set as the placeholder text in the content
control irrespective of locale setting. This indicates that the content control does
not have any value. While setting properties, this value is ignored on the server.
While creating new objects from Word, the same placeholder is used. To indicate
which property must be entered, temporary static text is displayed against the
content control indicating the localized display name of the property. This static
text (property name) is not saved in Teamcenter.

• Precedence followed for templates in document generation

In the document generation process, there are three sources from which you can
provide templates (specification templates and object templates).
o Export To Word dialog box
This method is called as a template override during run time.
o Item revision definition configuration (IRDC)

Teamcenter provides IRDC for paragraph revision and requirement revision
business objects.
o Site preferences, specifically the following preferences:

REQ_default_spec_template_for_export
REQ_default_spec_template_for_view
REQ_default_object_template
The order in which these sources are checked is not obvious and can cause
confusion.
Systems Engineering checks sources during document generation in the
following order:
1. Check for run-time template overrides, for example, from the Export to
Word dialog box.
2. If there are no run-time template override, check whether IRDC is available

for the selected business types.
3. If no IRDC configuration is found, get the templates names configured using

the following preferences:
o REQ_default_spec_template_for_export
o REQ_default_spec_template_for_view
o REQ_default_object_template
The system uses these templates during document generation.
Systems Engineering uses this precedence for finding templates during the
document generation process.

• Macro changes for Office 2010 users in Excel template

If you have Office 2010 with user-defined macros in the Excel template and you
export to Excel using the template, you see the following error:
You don’t have Office 2007 or 2003 which is required to support the interface.
It cannot connect to Tc2007 for live-editing or accumulate changes.

Use one of the following options to edit the macros:
o Option 1:
1. Copy the user-defined macro code.
2. Copy the Teamcenter macro code from any standard templates to the
user-defined template VBA macro section.
3. Merge the contents of the user-defined macro code and the Teamcenter
macro code so that there is no loss of Teamcenter macro code.
4. Save the macro and template.
o Option 2:
1. Create an item of an ExcelTemplate type.
This creates and attaches a standard template to the newly-created
Excel template.
2. Edit this template macro code to add the user-defined macro code so
there is no loss of Teamcenter macro code.
3. Save the macro and template.

Note In both cases, when you save the template the digital signature of the
macro breaks.

• Support for localized column names in Excel

The localized versions of property names are obtained from the
TC_ROOTlang\textserver\en_US\system_property_names_locale.xml
file.
If you want to use the Business Modeler IDE to define display names of
properties instead of the textserver files, Excel should also show the display
names from the Business Modeler IDE.
Use the Business Modeler IDE to localize the display name for the properties.
As a prerequisite, ensure that the display name for the property is specified in
the Business Modeler IDE and that localization changes are deployed in the
database.
Export to Excel now supports localized column names in the header. When you
export a group of objects to Excel, the generated sheet has localized column
names in the header part of the generated sheet. This feature is supported for
both Export all visible columns and Export using a template export options.
In the case of the Export all visible columns option, the column header now
contains localized names for the properties. In the case of the Export using
an Excel template option, you should add a particular format to the template.
In an Excel template, contents above the <start> tag are considered header
information. You should specify the following format in the Excel template:
{%TYPE.PROPERTY_NAME}
TYPE is the real type name of the business object, and PROPERTY_NAME is
the real name of the property.
If the property is inherited and the display name is defined on the parent,
you must define the following TC_ENABLE_PROPERTY_FROM_L10N
environment variable at the server in the tc_profile_vars file:
set TC_ENABLE_PROPERTY_FROM_L10N=0
If this environment variable is defined, the display names are fetched from the
parent. If you specify the new {%TYPE.PROPERTY_NAME} format, the
display name is queried from the Business Modeler IDE. You should ensure that
the property has the proper display name in the Business Modeler IDE.
Therefore, the generated Excel sheet now supports localized column names
in the header.
The old {%PROPERTY_NAME} format in the header is not yet deprecated
from the Excel template. This format obtains the display name from the
textserver localization files at the server installation. This approach is no
longer recommended because the textserver mechanism will be deprecated
in the future.
Siemens PLM Software recommends that you use the Business Modeler IDE to
localize the display name for the properties.

• Display name incorrect in Structure Pane in Microsoft Word

When you export a requirement structure to Microsoft Word for structure
editing, Word displays the structure tree (called the Structure Pane). The
display of nodes is not consistent with the display name of the object. While this
may not affect any functionality, you can overlook some information such as
the revision name and other values.
To make the node display name in the Microsoft Word Structure Pane
consistent with the Systems Engineering window in the rich client, set the
Word_Show_Display_Name preference to true. This uses the DisplayName
constant from the Business Modeler IDE to get the name and display it.
The default value of the Word_Show_Display_Name preference is false.
• Embedded Word window is not usable in the 64-bit rich client

When working with the 64-bit version of the rich client and the 32-bit version of
Microsoft Office Word, the embedded Word window does not work.
Use the 64-bit version of Microsoft Office Word to enable the embedded Word
window for the 64-bit rich client.
• Teamcenter to Excel integration on 64-bit machines requires 64-bit

.NET framework
Live Excel fails to open objects in Excel in the 64-bit rich client.
Install the 64-bit .NET framework 2.0 to work with the 64-bit rich client to
Excel integration.
For the Teamcenter to Excel integration, previously the Java2COM (neva-based
utility) was used to generate a wrapper over the COM applauncher component
(used to launch Excel and communicate data over a socket service). It is replaced
by a SWT-based wrapper which has a platform-independent (32-bit and 64-bit)
COM DLL file. A separate applauncher for the 64-bit platform is registered
using the 64-bit .NET framework tool.

• Import using keyword matches only the whole word

When keyword parsing is used during import, some instances of the keyword
are not found.
Beginning in Teamcenter 9.0, importing using a keyword matches the whole
word. Variations of the keyword are not processed.
For example, if you type the keyword item, then item’s is not recognized as a
keyword.
• REQ_create_object_template is not available

The REQ_create_object_template was available in Teamcenter 9.0, but it is
not available beginning in Teamcenter 9.1.
Create the template using the add_dm_template utility.
• Update of flat file dataset during Revise operation

Import a flat file with a few objects, open the dataset from Teamcenter, update
the document by adding a few more objects, and then import again with the
Revise command. After the import is complete, check the dataset attached to
Rev/A from Teamcenter. The expected result is that the data set should not
be updated with newly added objects.
By framework design, when the dataset is opened by double-clicking and the file
is closed after modification, rich client always updates files in the volume. To
work with flat file import, you should never directly open the dataset and update
the flat file. Save the flat file locally before making any changes to prevent
overwriting the previous file version in the volume after the revision.

• Assigning an ID does not work when a cell in Excel is in edit mode

When you attempt to assign an ID in a Microsoft Office Excel 2003/2007
workbook using the Teamcenter Flat File Import Addin for Excel, the assign ID
dialog box appears, but the ID is not assigned to the cell when you click OK.
This occurs only when you click the Assign ID button and the cell is in edit
mode, for example, when you press F2 to edit the cell, or double-click the cell to
type the contents.
This applies to:
o Microsoft Office Excel 2003
o Microsoft Office Excel 2007
o Teamcenter Flat File Import Addin for Excel

Exit the edit mode by using the escape key and then click the Assign ID
button. To see if you are in edit mode in Excel, see the toolbar button for
New/Open/Undo/Redo. If the button is disabled, then you are in edit mode.
This behavior is by design. Microsoft Excel 2003/2007 disables all other actions
while the cell is in edit mode, such as setting the cell value programmatically.
The Excel data model also does not raise any event or provide an API to query if
the cell is in edit mode. Certain functions are available only when cell is not in
edit mode, such as go-to, macro editing, and search. The same principle applies
to setting the cell value programmatically.
• Excel sheet cannot be connected using direct server connectivity mode

When an Excel sheet is generated through the Work offline and Import option on
the Export To Excel dialog box, it cannot be connected using the direct server
connectivity mode in Teamcenter Extensions for Office or in the rich client by
choosing the Tools→Open Live Excel command.
To connect a sheet generated through the Work offline and Import option, install
Client for Office and use the Excel import feature.
An Excel sheet generated using either the Live Integration with Excel
(Interactive) or Live Integration with Excel (Bulk Mode) option on the Export
To Excel dialog box are connected using direct server connectivity mode
of Teamcenter Extensions for Office or in the rich client by choosing the
Tools→Open Live Excel option.

• Client for Office does not show updated values

When you perform the following steps, Microsoft Office Word displays old values:
1. Export a Word document from the rich client to Client for Office.
2. Modify the Word document in Client for Office and save it to Teamcenter.
3. Export the Word document from the rich client again without doing a refresh.
The Word document shows the old values prior to the modification.

Configure the SharedSession feature in Client for Office. This feature enables
Client for Office to share the same Teamcenter server that the rich client uses.
To set it up, open the Client for Office TcWordAddin.dll.config configuration
file and set the SharedSession option to true.
After configuration, follow these steps to verify proper operation:
1. Log on to the rich client.
2. Log on to Client for Office using the same user ID, group, and role as
specified in rich client logon dialog box. Teamcenter automatically connects
Client for Office to the rich client server session.
Note Even though the rich client and Client for Office share the same server,
the rich client does not automatically show the changed value from
Client for Office. But, when you perform another operation on the object,
the values are picked from the server.
• Embedded Word window with the 64-bit rich client

The embedded Word window on a 64-bit rich client is supported only with the
64-bit version of Microsoft Word.
Install the 64-bit version of Microsoft Word with a 64-bit rich client.

• Default and traceability context names not localized

The default and traceability context names under the View menu in the Relation
Browser view display in English when the Chinese locale is running.
The names under the View menu in the Relation Browser are now localized
and display in the appropriate locale.
• Visio creates a duplicate interface

In an existing Visio diagram, if you create a connection between two interfaces
such that the connection starts and ends from the point at which the interface is
attached to the function, a duplicate interface may get created.
Always attach the connection to the interface points on the interface boundaries.
The connection to the interface point and the interface to the function point
should not be the same.
• Exporting markup on remote site

Markups associated with specification items do not get exported on a remote site.
Perform the following steps to include markups when exporting a specification:
1. Click the Display/Set remote export options button at the bottom of the
Remote Export dialog box.
2. In the Remote Export Options dialog box, click the Advanced tab.
3. Double-click Markup(s) in the Exclude Reference list.
4. Ensure Markup(s) is included in the Include Reference list.
5. Click OK.
• Secondary objects of trace links must be transferred manually

If you transfer a structure to another site using Change Viewer and if that
structure has trace links to occurrences, the secondary object of the trace link
is always transferred as a stub if the other end of the trace link is also an
occurrence. Even if you include the Tracelink option in the included list and the
Export Entire BOM option is also set to true, the secondary object of the trace
link is transferred as a stub only.
You must transfer the structure at other end of trace link manually.

• Blank column in Traceability report

In the traceability report, if the same child occurs more than once under the
same root, only one of them is visible.
This is due to an issue with the Eclipse JTree, which does not show duplicate
elements in a tree.
1. If there are duplicate elements, a blank value is shown in first column, but
all commands in the traceability report continue to work on the selected
line or row.
2. If you want to see the element in the blank cell, click the Show Tracelink
button in the report.
• LOVs are not supported by Microsoft Excel Import

Microsoft Excel Import supports only single value (basic data type) LOVs. Only
string and numeric LOVs are supported.
The following LOVs are not supported by Excel Import:
o Interdependent or cascading LOVs
o Multichoice LOVs
o LOVs mapping to references types
o Any LOV that has run-time or calculated data

Currently, there is no workaround for this problem. Excel Import, by design,
does not support LOVs. Single choice LOVs work because they do not require
anything other than simple property setting.

• Export to Microsoft Excel exports the trace links for the topline only
If you select the topline and export it to Microsoft Excel, only the trace links
created in the context of topline are exported to Excel.
For example, in the following structure, if you create a trace link between Bolt
and Wheel in the context of Car, and then you select Car and export it to Excel,
the trace link between Bolt and Wheel is exported to Excel. However, if you
create a trace link between Bolt and Wheel in the context of Axle, that trace
link is not exported to Excel if Axle is not the topline of the BOMWindow object.
Car
Axle
Bolt
Wheel

You must open the Axle assembly where Axle is the topline. You can then export
the trace link between Bolt and Wheel.
• List of dataset types supported for the copy reference feature

The Copy Reference action is enabled on all business objects.
The copy reference feature is supported for BMP, Image , Jpeg, GIF, TIF types of
image datasets. From the Teamcenter user interface, the Copy Reference action
is enabled for BMP, Image, Jpeg, GIF, TIF types of datasets.

• Newly created budget Excel template does not show up in New Budget
Definition dialog box
A newly created budget Excel template is not displayed in the New Budget
Definition dialog box.
Once LOV values are loaded, the values are cached in the rich client session.
You must restart the rich client session to see newly created budget templates
in the LOV.
Restart the rich client session to see newly created budget templates in the LOV
on New Budget Definition dialog box.
• Trace link symbol removed on workspace objects to reduce client-server

traffic
The trace link icon is not available on workspace objects in Teamcenter 10.1.
Previously, the trace link symbol on workspace objects indicated a trace link was
present on the object. This symbol has been removed to reduce traffic between
Teamcenter clients and servers.
To find whether a trace link exists on a workspace object, add the Has Tracelink
column in the details panel for each workspace object in the details pane. This
column displays a value of Y or N to indicate whether a trace link exists on
the object.
• Systems Engineering and Requirements Management disables autosave

for Word documents
The autorecovery feature in Microsoft Word opens the Save dialog box
unexpectedly for requirement documents.
The autosave feature is disabled for Word documents when you open a
requirement document. The Systems Engineering and Requirements
Management add-in disables the autosave feature of Microsoft Word when you
open a requirement document and it re-enables the autosave feature (if it was
enabled previously) when you close the requirement document.

• New icon in Requirements Management integration in Microsoft Word

An icon has been added for duplicate objects exported from Systems Engineering
to Microsoft Word. This icon is not documented in Teamcenter online help.
In addition, a visual indication has been added for dirty nodes in the task pane in
Microsoft Word. This indicator is also not documented in Teamcenter online help.
The icon for duplicate objects exported from Systems Engineering to Microsoft
Word is shown in the task pane that shows requirement structure. Also, if
you modify any structure or property in Microsoft Word, a red asterisk (*) is
displayed next to the object in the task pane to indicate a dirty node.
• Refresh window action does not work for multiple views

If two users work concurrently on a single object, and the first user updates the
object, when the second user has two views open (for example, the Systems
Engineering view and the Details view) and refreshes the Systems Engineering
view, the contents are not refreshed in the Details view.
The user must explicitly refresh both views by pressing the F5 key.
• Removal of Teamcenter macro code from the standard templates

If you have Microsoft Office 2010 installed and you export to Microsoft Excel,
an error message is displayed stating that the digital signature is broken and
you are unable to log on to Teamcenter with Office.
The Teamcenter macro code is removed from all the standard templates. When
you export using standard templates, there is no macro code in the generated
sheet. The generated sheet contains the following header:
"Live" edit on this spreadsheet requires
Teamcenter Extensions for Microsoft Office
However, any custom macro from the template is preserved in the generated
sheet.
Perform the following on standard Excel templates after upgrading to
Teamcenter 8.3i:
1. Search for the standard item in the following My Teamcenter templates

and delete it:
MFG_default_struct_template
REQ_default_excel_template
REQ_default_rel_export_template
REQ_default_RM_template
REQ_default_struct_template
REQ_defview_template

2. Run the add_req_templates utility.

This utility installs the new Excel templates to the database.
Note If you have done any customizations in the standard templates, you
must those customizations after reinstallation of templates.
3. Perform the following steps for the custom templates:

a. Open a custom template and press Alt-F11. If the custom template does
not have any custom macros, delete the Teamcenter macro code and
save the macro and template.
If the custom template has any custom macros, delete only the
Teamcenter macro code. Do not delete the custom macro code and save
the macro and template.
b. Repeat this step for all the custom templates. The custom macro code is
preserved in the Excel sheet that is generated at the server.
• Custom templates must be changed manually to export Systems

Engineering BOM lines
There are fundamental changes in Systems Engineering. The BOMline type
is now named RequirementBOMLine. So the real type in the database is
changed to Fnd0RequirementBOMLine. The standard template that had the
old BOMLine type is therefore changed to Fnd0RequirementBOMLine. Due
to this change, when you export the run-time objects fromSystems Engineering,
no objects are exported in the Excel sheet because it does not match any rule in
the template. The underlying type name is now changed and the template only
works with the real database names.
The standard REQ_default_RM_template template is modified to reflect
the real Fnd0RequirementBOMLine type name. This change is required
so that users can continue to use the standard template when exporting
fromSystems Engineering. If you export from Systems Engineering, all the
custom templates that have the type specified as BOMLine must be changed to
Fnd0RequirementBOMLine. You may also need to change the closure rule
clause that specified the old BOMLine type.
This template now has the ability to export BOMLine objects and
RequirementBOMLine objects. If you need any other type of lines, edit the
template and specify the real type name in the template.

If you are upgrading from a previous baseline, follow these steps:
1. Log on to the rich client and delete the REQ_default_RM_template item.
2. Open the command prompt on the server.
3. Run the following utility from the server prompt:

add_req_templates -u=user-name -p=password -g=group
This utility installs the new standard template, and you can start working
with this template to export run-time objects from Systems Engineering.
• Problem importing large documents in Systems Engineering

Importing large documents in Systems Engineering causes server time-out
issues. This is specific to an environment where the .NET Web tier (middle
tier) is installed.
This is a .NET middle tier configuration issue. Browse to the middle tier
installation directory. In the Web.config file, modify the executionTimeout
setting to a higher value. The default is set to 600 seconds (10 minutes). Change
it to 7200 as follows:
<-- This is used to change the default http connection timeout(90seconds)
to 600 secs and to change the default maxRequestLength (4MB)
to 128MB = 131072 KB -->
<httpRuntime executionTimeout="7200"maxRequestLength="131072"/>
Clear the cache, restart the IIS server, the Teamcenter server, and the client.
• Parametric values of attached notes are not shown in the Microsoft

Word viewer
When you select a parametric note and launch the Microsoft Word viewer, the
viewer shows the contents of the selected parametric note in My Teamcenter or
Systems Engineering. If you select any other SpecElement revision, the viewer
does not show contents of the new selection. The status at the bottom of the rich
client shows Ready indicating that the change has not been noted.
Before switching to the next selection to display the contents in the Microsoft
Word viewer, you must click the Home tab of the My Teamcenter perspective
(or the View tab in the Systems Engineering perspective). Then if you change
the selection, the contents of changed selection is updated in the Microsoft
Word viewer.

• Excel does not automatically refresh non-Workspace object properties

The rich client does not perform component change events for non-Workspace
object property changes. For example, when a user tries to modify the Geography
property on the User object (which is a non-Workspace object), the rich client
does not fire the component change event to inform Excel about the property
change. As a result, Excel does not automatically refresh the property value.
Perform a manual refresh in Excel. Perform a manual refresh in scenarios where
non-Workspace objects and their properties are involved.
• Importing requirement specifications with SpecElement subtypes that

have required attributes
When importing a requirement specification with a subtype that has required
attributes that are null or without initial values, the requirement structure is
created in Systems Engineering as expected. However, the new objects’ required
attributes remain empty because the import process does not set values for those
attributes. This results in problems when objects are moved or copied within the
imported structure and when their properties are updated using live Excel.
Define the initial values for all required attributes of subtypes in the Business
Modeler IDE and deploy before the import. Otherwise, you must set the required
attributes from the properties panel for each object.
• Microsoft Office 2010 security settings

Microsoft Office 2010 has a different user interface than Microsoft Office
2007 for enabling active content security settings. You must be aware of this
user interface or the live Excel add-in may not work correctly in the secure
environment.
1. In Microsoft Office 2010, select the following security option in the Trust
Settings→Addin tab:
Require Application Add-ins to be signed by Trusted Publisher
2. Open a live Teamcenter sheet.

The following message is displayed:
Security Warning: Some active content has been disabled.
Click for more details. Button[Enable Content]
3. Click the link in the Some active sentence and click the Enable Content
button.
An Advanced Options menu is displayed.

4. Click Advanced Options and select the following options:

o Add-in: TcO2k7Addin. Connect Friendly Name
o Enable all code published by this publisher
5. Click OK and close Excel.
After you open the sheet again, the live Excel add-in behaves normally.
Note In Microsoft Office 2007, this option appears immediately on the message
bar after you click the Options button after you receive the security
warning; it is a one-step process.
To enable this option in Microsoft Office 2010, it is a three-step process.
This option is buried deep in the user interface, so it makes it difficult
for the user to enable this option.
• Marshalling error when creating an item with a special character in

the name
When you create item or import a Word document containing a special character
that is not supported by the Teamcenter server character set, you receive a
marshalling error.
Install an import preprocessor utility to help you locate invalid characters
present in a document that are not supported by the Teamcenter server
character set:
1. Ensure you have the following installed:

o Microsoft .NET framework 3.5
o Visual Studio Tools for Office Runtime 3.0
o Microsoft Office 2007 with .NET interoperability pack
2. Locate the word_import_preprocessor.zip file in the

installation-source\tc folder and unzip it.
3. Run the setup.exe file provided in the Word preprocessor. (Ensure that the
TcUA Word PreProcessor.msi file is in the same folder as the setup.exe
file.)
4. After successful installation, open the Word document that needs to

preprocessed prior to importing into Teamcenter.
You should see the Import preprocessor tab in Word 2007.
5. Click the Import preprocessor tab.

You see the Review and Delete ribbon buttons.

6. Click the Review button and select the Teamcenter server character set
against which document is validated.
The invalid characters in the document are highlighted in the Word
document.
7. Click the Delete button and select the Teamcenter server character set
against which document will be validated.
The invalid characters in the Word document are removed.
8. Save the document and import it into Teamcenter.
• Cascading LOVs are not supported in live Excel and live Word
Cascading lists of values (LOVs), including hierarchical and interdependent
LOVs, cannot be edited in live Excel or live Word.
Currently, users must use the rich client to edit these properties.
• Multichoice properties are not supported in live Word

Editing of multichoice property values is not supported from the embedded live
Word using the keyword mechanism.
Currently, users must use the rich client to edit these properties.
• Reference designators cannot be imported in packed format

Properties, such as Find No, that need a unique value cannot be set on a packed
BOM line. Microsoft Excel Import prevents you from updating the property on
packed reference designators.
Unpack the BOM line and set a unique value on each occurrence. To update
the property on packed reference designators, unpack the rows in Excel before
importing.
• Duplicate reference designators created during import

Duplicate reference designator values are imported when the default value
is provided in the control file. If you enter default values for the reference
designator columns, a warning is displayed about duplicate reference
designators.
Do not give default values for reference designators in the control file.

Vendor management
The following release notes pertain to usage of vendor management functionality.

• Multi-Site support for vendor management objects
Not all objects from the vendormanagement template have Multi-Site support.
Only the following objects in the vendormanagement template have Multi-Site
support:
Vendor without vendor role

Vendor with vendor role
Vendor with commercial part
Vendor with vendor part
Vendor with commercial part or vendor part
Commercial part without vendor part
Vendor part with commercial part
Vendor part with vendor
Commercial part with preferred vendor parts

Teamcenter EDA
The following release notes pertain to usage of Teamcenter EDA.

• Problems launching EDA from rich client
The rich client can be installed from local media or installed using the
Over-the-Web Installer. Additionally, there are options in the installation process
to select either 32- or 64-bit versions of the rich client.
These choices present a problem for users of the EDA ECAD tool integrations.
Not all of the supported ECAD products are offered in 64-bit versions by their
vendors. Teamcenter EDA itself is available in a 32-bit version only. Conflicts
may occur when a 64-bit rich client attempts to launch the 32-bit EDA product.
The two environments are not compatible.
ECAD tools provide for pointers to alternate Java installations.
If a pure 32-bit environment is installed, the default Java environment setting
can be used. In a mixed 32/64-bit installation, rich client and EDA must use
different implementations of Java. To ensure that EDA uses the correct version of
Java, create a new system environment variable named TCEDA_JAVA_HOME.
Set this variable to the path to the 32-bit Java version that EDA must use.
Some ECAD products also require the JRE_HOME environment variable. This
is supported by the added TCEDA_JRE_HOME variable.
• Longer folder path problem on Windows operating system

The Windows operating system cannot create a folder if the length of
the absolute path of the folder is greater than 248 characters. When the
Tc_Allow_Longer_Id_Name preference is set to true, and if the user assigns
a longer item ID for a CCABase item type during the Save As operation, the
Zuken connector fails to create the circuit directory and displays an error
message.
Limit the length of the CCABase item ID to less than 32 characters to avoid
possible problems with circuit directory creation.

Visualization Illustration
The following release note pertains to the use of Visualization Illustration.

• TcPublishing page assets must be on a single page in the work
instruction
The information that Visualization Illustration requires to support asset updates
may be compromised if the assets are not on the visible page when the work
instruction is saved.
Define all assets on a single page (page 1) and always have that page visible
when saving the work instruction.
• Visualization Illustration Batch does not support incremental change

Visualization Illustration Batch does not configure publishing pages by effectivity
and it does not modify publishing pages according to any incremental change.
• Portfolio page list update does not reflect modular variant

configurations
(First published Teamcenter Engineering 2005 SR1)
When a structure that is configured with modular variants is used to generate a
list of pages in a portfolio, unconfigured pages can appear when the portfolio is
updated.
Use classic variants to configure structures, or cut the unwanted pages from
the portfolio after updating.

Workflow
The following release notes pertain to Workflow.

• Save toolbar button does not change the state of the selected template
in Workflow Designer
The Save toolbar button is always enabled in Workflow Designer, regardless of
the stage of the currently selected workflow template. Also, clicking the Save
button does not appear to have any noticeable impact to that template.
The Save toolbar button is not used in the Workflow Designer perspective to
save the workflow template that is being edited. Use the Edit Mode toolbar
button to make a workflow template editable, and select the Set stage to
Available check box to make the template available.
• Update_Process event does not get recorded in Audit Manager version 2

In Audit Manager version 2 (which is specified using the
TC_audit_manager_version preference), when an administrative
user updates a process template and there are active processes that are based on
the template being modified, the Update_Process event is not recorded.
Use Audit Manager version 3 instead of version 2. In Audit Manager version 3,
the Update_Process event is successfully recorded.
• Comments for Do Task and Condition Task are not being written to
audit file
When a user signs off a Condition Task or a Do Task, the comments are not
written to the audit file when the Audit Manager is turned off and users are
using the file-based audit.
Instead of completing a Do Task by choosing the Perform action, you can choose
the Complete action from the Actions®Complete menu, in which case the
comments are written to the audit file. There is no workaround in the case
of the Condition Task.

• EPM-set-property workflow handler cannot set properties that have

no property set methods
The EPM-set-property workflow action handler cannot set a property if a
property set method does not exist for it. Some run-time properties do not have
property set methods.
For example, dynamic participants runtime properties do not have property set
methods, so you cannot use the EPM-set-property handler to set them.
Use Teamcenter core functionality to set properties as required or add a property
set method for the given runtime property. If you create a custom property, you
should create a property set method and a property get method for it.
If you add a property set method, you can use the EPM-set-property handler to
set the property.
• Pre-Teamcenter 8 process assignment lists may cause issues

In an environment upgraded to Teamcenter 8.n or later (without the fix present
in Teamcenter 8.3.2.2), if there are process assignments lists with the default
value of All, they may not work correctly if assigned to a process with the
demote-on-reject/ EPM-demote-on-reject handler. The process may hang
and not proceed further.
Upgrade the process assignment lists to the default quorum value. Use one of
the following methods:
o Run the upgrade_pals utility using the following command:

upgrade_pals -u=user -p=password -g=group
o If there are a few existing process assignment lists, it may be more efficient
to update them manually. In Teamcenter, change the quorum value of
process assignment lists from 1% to 100%.
• Highlighting the select-signoff-team task is chatty in Workflow

The Select-signoff-team task has three resource pools and one user already
assigned in the user inbox. When the task is selected with the task view active,
the Communication Monitor catches this network call chattiness:
The last 56 calls happened in 4.674227823 seconds
On a customer WAN with 0.175 second latency, this could be 14.474227823

seconds.

Configuration release notes
Configuration release notes
The following release notes pertain to configuring Teamcenter.
Command Suppression
The following release notes pertain to Command Suppression.
• Command Suppression application user interface supports hiding only
commands added to the menu bar
The Suppress Commands tree pane displays all the commands that are
contributed to the menu bar for a selected application. Any commands that
are not contributed to the menu bar (for example, contributed either only
to the toolbar or context menu or both) are not displayed in the Commands
view. Therefore, an admin user cannot hide such commands directly from the
Command Suppression application user interface.
In such cases, you must manually add the command ID to the respective
preferences. For example, to hide the View/Edit Multi Unit Configuration
context menu in My Teamcenter for the dba group, you must edit the
com.teamcenter.rac.ui.perspectives.navigatorPerspective preference and
add the com.teamcenter.rac.effectivtyGroup command ID to the Current
Values box.
If the desired preference does not exist, you must first use Command Suppression
to hide the Edit→Cut menu for the desired application and group/role. Then,
edit the preference.
For more information about command IDs, see Rich client customization
reference®Common Teamcenter command IDs in the Client Customization
Programmer’s Guide.
• Command suppression constraint

The Command Suppression application cannot suppress commands that are
dynamic contributions. (For example, the <dynamic><dynamic> in the
menuContribution of the org.eclipse.ui.menus extension point cannot be
suppressed.)

Administration release notes
Administration release notes

The following release notes pertain to the system administration of Teamcenter and
the use of the administration applications.
General administration
The following general release notes pertain to the administration of Teamcenter.
• Error displayed after a project is deleted
When a project administrator deletes a project and then tries to change the
current project in the User Settings dialog box in the same session, Teamcenter
displays the following error:
The specified tag 00007c88 has been deleted, cannot find requested object.

There are two workarounds for this problem:
o Workaround 1
If the project administrator needs to change a project in the User Settings
dialog box, the administrator should do this before deleting a project.
o Workaround 2
After deleting a project, the project administrator can log off from the current
session and log on again to change the project in the User Settings dialog box.
• Removing performance testing classes

If you have run the install utility with the -performance_test argument in
versions earlier than Teamcenter 10.1, you can remove classes installed by the
utility. These classes were installed for testing only and do not generally impact
the performance of Teamcenter:
performance_test_ls
performance_test_1
performance_test_2

You can remove these classes using the install -remove_class command,
substituting your Teamcenter administrative user, password, and group names:
install -remove_class user password group performance_test_ls
install -remove_class user password group performance_test_1
install -remove_class user password group performance_test_2
The install -remove_class command should be run when there are no users
logged on to the system. If you run the utility when there are users on the
system, an error like the following is issued:
install -remove_class user password group performance_test_ls
Attempting to dropping class.

Started POM v1000.0.1 ...

Failed to modify the schema - are there other users?: got 515145 error
Failed to modify the schema - are there other users?
Error 515145 from POM_modify_schema, meaning: POM_schema_locked
*** Caught an error while installing ... aborting!
==================================================
There were 0 notes and 1 error during this run
Please see log file in C:\Temp\install-remove_class1cc0260b.syslog
==================================================
No harm is caused by this error. Make sure no users are logged on and then
run the utility again.
• Removing a project team member

Removing a user from a project where the project owns data for the user being
removed proceeds without warning and removes the user. This is a known issue.
Note This applies only if Aerospace and Defense Foundation template is
deployed in the Teamcenter configuration.

Project team administrators must make sure a user has no data that is owned by
the project before they remove a user.
• Problems with suggestive interactive hierarchical LOVs

For suggestive interactive lists of values (LOVs), the user can enter values in
two ways:
o Select the available values from the LOV list.
o Type values.
The first method works fine. The second method has some limitations. It does
not work in the following cases:
o The displayed value in the LOV is different from the value in the LOV.
o In localized environments, the value entered by the user is used and not the
translated value. The autocomplete feature does not work for suggestive
interdependent hierarchical LOVs.

Currently, there is no resolution to convert the values typed in by the user.

• ldapsync utility crashes when the LDAP_member_list_attr preference

points to parent node
If you set the LDAP_member_list_attr preference to point to a node on the tree
that contains a direct parent of the node being processed, it causes an infinite
loop that crashes the ldapsync utility. For example, if a parent node has one
child node and that child node uses the LDAP_member_list_attr preference to
point back to the parent, it causes an infinite loop.
Ensure the LDAP_member_list_attr preference does not point to a node that
causes an infinite loop.
Organization
The following release notes pertain to the Organization application.

• Group administrator is allowed to add groups where the current user
has group administrator privileges
(First published Teamcenter 10
If a user logs on with group administrator privileges in the logon group, the
Organization application allows you to add any groups to the logon group,
including the dba group. This means a group administrator can add any users
to the dba group. This is a security concern.
Allow a user with group administrator privileges to add groups only where the
user has group administrator privileges as well to the current logon group.

Security Services
The following release notes pertain to Security Services.

Note For additional Security Services release notes, see the Security Services
Release Notes (SecurityServicesReleaseNotes.pdf file) in the sso
subdirectory of the additional_applications directory of the Teamcenter
2007 software distribution image. This document describes features
introduced with the latest version of Security Services. It also contains
general notes and descriptions of known defects.
• Remove TC_SSO_LOGIN_URL from client.specific.properites file

The rich client logon dialog box is not displayed if Teamcenter is
configured for Teamcenter client communication system (TCCS) and
the TC_SSO_LOGIN_URL environment variable is specified in
client_specific.properties file.
You must remove the TC_SSO_LOGIN_URL environment
variable setting from the client_specific.properties file in the
rac\plugins\configuration_10000.1.0 directory on rich client hosts.
1. Open the client_specific.properties file from the

rac\plugins\configuration_10000.1.0 directory in a text editor.
2. Remove the following entry from the file:

TC_SSO_LOGIN_URL=value
• Logon failure with smart card authentication

If you log on into an environment configured for smart card authentication with
an instance of TCCS already running, the logon fails with a 403 error when you
insert the smart card and delete the certificate from Internet Explorer.
With the smart card inserted, stop the TCCS process and start the Teamcenter
rich client application.
• Use consistent Login Service URLs when configuring different

applications for Security Services
If you use different but logically equivalent URLs when configuring
Teamcenter applications to Security Services, the hosting Web server may
assign distinct JSessionID IDs to the applications. This interferes with
the capability of Security Services to host the applications within a single
Security Services session. Examples of different but logically equivalent URLs
are http://sv10.net.plm.eds:7001/TcSSLogin and http://sv10:7001/TcSSLogin.

The symptoms of this problem are:

o The following message appears in an alert window upon starting a second
Teamcenter application:
Failed to start SSO Session Agent.
Please verify that cookies and Javascript are enabled.
Please see Java Console for more information.
o The following appears in the Java console:

com.teamcenter.ss.SSOException: SSO Session agent is not available
at com.teamcenter._ss.client.login.ClientListener.<init>(Unknown Source)
at com.teamcenter._ss.client.login.applet.SSOSessionAgentApplet._start(Unknown Source)
at com.teamcenter._ss.client.login.applet.AbstractLoginApplet$1.run(Unknown Source)
This issue was observed with Apache Tomcat but may apply to other Web
Servers.
Use consistent Security Services Login Service URLs in all Teamcenter
application configurations.
• Disable the HTTP-only flag in WebLogic 10.x

Newer versions of WebLogic set the cookie-http-only flag by default. This flag
prevents browsers from accessing cookies using client-side scripting. Security
Services depends on this feature to start a viable session agent applet, so it must
be disabled for deployments of the Security Services Login Service servlet.
The symptoms of this problem are:
o The following message appears in an alert window upon starting a second

Teamcenter application:
Failed to start SSO Session Agent.
Please verify that cookies and Javascript are enabled.
Please see Java Console for more information.
o The following appears in the Java console:

com.teamcenter.ss.SSOException: SSO Session agent is not available
at com.teamcenter._ss.client.login.ClientListener.<init>(Unknown Source)
at com.teamcenter._ss.client.login.applet.SSOSessionAgentApplet._start(Unknown Source)
at com.teamcenter._ss.client.login.applet.AbstractLoginApplet$1.run(Unknown Source)

Go to the staging directory created while running the insweb.bat file. In
the staging directory, go to the webapp_root\WEB-INF directory and add
a weblogic.xml file.
Add the following code to the weblogic.xml file:
<session-descriptor>
<cookie-http-only>false</cookie-http-only>
</session-descriptor>

• Simpgen translator does not support Security Services

When Teamcenter is installed in the Security Services enabled mode, the
Simpgen translator may fail because access is denied.
Disable Security Services for the Simpgen translator. You can enable Security
Services for all other components; however, you must install the Simpgen
translator on a separate machine that is not Security Services enabled.
If you want all components on the same machine, associate a new TC_DATA
directory with the Simpgen translator that is not Security Services enabled. To
make the Simpgen translator work in Security Services enabled mode:
1. Duplicate $TC_DATA or %TC_DATA% by creating the

${TC_DATA}_nonsso or %TC_DATA%_nonsso (depending on
the platform) directory.
2. Unset all Security Services related variables in the ${TC_DATA}_nonsso

or %TC_DATA%_nonsso directory. The three variables that must be
removed or reset are TC_SSO_APP_ID, TC_SSO_SERVICE, and
TC_SSO_LOGIN_URL.
o Windows example:
rem set TC_SSO_APP_ID=Tc8S17
rem set TC_SSO_SERVICE=http://svli6011v03.net.plm.eds.com:7105/ssoService8
rem set TC_SSO_LOGIN_URL=http://svli6011v03.net.plm.eds.com:7105/ssoLogin8
o UNIX example:
#TC_SSO_APP_ID=Tc8S19; export TC_SSO_APP_ID
#TC_SSO_SERVICE=http://svli6011v03.net.plm.eds.com:7105/ssoService8;
export TC_SSO_SERVICE
#TC_SSO_LOGIN_URL=http://svli6011v03.net.plm.eds.com:7105/ssoLogin8;
#export TC_SSO_LOGIN_URL
3. Set the TC_DATA variable in the

Module\Translators\simpgen\simpgen.bat file or the
Module\Translators\simpgen\simpgen.sh file and point it to the
newly created ${TC_DATA}_nonsso (UNIX) or %TC_DATA%_nonsso
(Windows) directory.
Site Consolidation
The following release notes pertain to Site Consolidation.
• Site consolidation of Schedule Manager notifications and subscriptions
The list of users, groups, and disciplines to be notified using Schedule Manager
notifications and subscriptions is not transferred properly when using Site
Consolidation.
Fix the notifications manually after they are transferred.

Subscription Monitor
The following release notes pertain to Subscription Monitor.
• Subscription modification fails if duplicate subscriptions exist
Teamcenter 9.1 does not allow modification of duplicate subscriptions that share
the same subscriber, object type, and event type. This ensures consistency
between creation and modification of subscriptions. If a customer site has
duplicate subscriptions from a previous release, editing those subscriptions fails.
However, subscriptions that do not have duplicates can be modified as before.
If a customer site upgrades to Teamcenter 9.1, any duplicate subscriptions
that exist for the same subscriber, object type, and event type combination
should be deleted manually from the Subscription Monitor dialog box so there
is only one subscription left for that combination. Teamcenter then allows
the modification of the subscription. However, there is no need to delete the
duplicate subscriptions if they do not need to be modified.
Utilities
The following release notes pertain to utilities.
• Corrections to the item_to_part_design utility
The item_to_part_design utility does not work due to the core data model
changes beginning in Teamcenter 8.0.
The item_to_part_design utility is modified per the new data model changes
released in Teamcenter 8.3.
For more information about the utility, see the Utilities Reference.
• Cannot collect unreferenced UGMASTER datasets after saving JT data

The collect_garbage utility excludes unreferenced datasets from garbage
collection if the dataset has a secondary object. Therefore, the utility does not
collect unreferenced UGMASTER datasets after saving JT data.
The -child_references and -ignore_relation arguments are introduced
for the collect_garbage utility. The enhanced collect_garbage utility can
now collect all unreferenced datasets that have secondary objects by using
the -child_references argument with the -dataset argument. When the
-child_references argument is used, datasets that are unreferenced in the
system, but have secondary objects, qualify as garbage. However, to avoid any
unintentional data loss, the -ignore_relation argument is introduced for the
utility. The valid value for this argument is a comma-separated list containing
internal relation names. The -ignore_relation argument is effective only in
conjunction with the -child_references argument and -dataset argument.

For anything else supported by the collect_garbage utility, this argument is

ignored. When the -ignore_relation argument is used, all datasets that have
at least one secondary object attached with any of the relations in the list are
excluded from garbage collection.
When the utility is used as in the following example, all unreferenced datasets
that have secondary objects are collected as garbage, except those that
have any of the secondary objects attached with the IMAN_Rendering or
IMAN_specification relationship:
collect_garbage -u=infodba -p=<password> -g=dba
-dataset -query -rf=report.txt -child_references
-ignore_relation=IMAN_Rendering,IMAN_specification
Note Running the utility with the -child_references argument may impact
performance, depending on the data volume.

Customization release notes
Customization release notes
The following release notes pertain to customizing Teamcenter.
• Simplify WEB_status_icons preference configuration

Various status icons can be configured to be shown in My Teamcenter. This
includes in-process statuses (shown when an object is the target of an active
process) and arbitrary release statuses like Approved for Manufacturing.
The WEB_status_icons preference allows any release status name to be
included in the preference. A commonly desired configuration is to show all
applied release statuses. However, to satisfy this configuration, the customer
must add every release status. Some customers have hundreds of release status
names to track, and it creates a performance issue when processing large sets of
objects.
The best way to leverage this improvement is to shorten the WEB_status_icons
preference by removing all of the release status names. If you are satisfied with
showing all release statuses or only the latest status, listing arbitrary statuses
is no longer necessary.
The preference can optionally contain any of the following keys:
o configured
o in_process
o external_links
o TraceLink
o AllReleaseStatuses
Including the AllReleaseStatuses key causes icons for all release statuses to
be included.
The WEB_show_multiple_release_statuses preference also affects this part
of the display; its default value is false, indicating only the release status icons
for the latest release are displayed. When set to true, all release statuses listed
in the WEB_status_icons preference are displayed.
Sites having more than 25 different release statuses to display can cause
performance problems when the WEB_status_icons preference list grows. Use
one of the following scenarios to improve performance:
o Configure to show all release status icons.
1. Remove all release statuses from the WEB_status_icons preference.
2. Append the AllReleaseStatuses argument to the WEB_status_icons

preference.
3. Set the WEB_show_multiple_release_statuses preference to true.

o Configure to show only the latest release status icon.

1. Remove all release statuses from the WEB_status_icons preference.
2. Set the WEB_show_multiple_release_statuses preference to false.
• Removal of functions from the pom.h header file

(First published Teamcenter 9.1.2)
The POM_set_membership_datasource and
POM_set_membership_last_sync_date ITK functions have been removed
from the pom.h header file. This release note acknowledges the removal as
deliberate in case any generic processing of headers needs updating to reflect
their removal.
The POM_set_membership_datasource and
POM_set_membership_last_sync_date ITK functions have been removed
from the pom.h file as they are only for use in internal utilities. These functions
require system administrator rights and were not documented, as they should
not have appeared in a published header file. Given their nature, there should
be no risk of their being used; therefore, no deprecation was announced.
Business Modeler IDE

The following release notes pertain to the Business Modeler IDE.
• fnd0checkOutOnCreate property is set to be invisible on CreateInput
of ItemRevision
When the fnd0checkOutOnCreate property is set to be visible on the
CreateInput operation of the ItemRevision business object, the checkout
check box is presented in the generic New Item creation wizard dialog box
when Document type is selected. Once the checkout check box is selected,
ItemRevision is checked out after Item is created, but any dataset attached to
ItemRevision with the TC_Attaches relation is not checked out.
The fnd0checkOutOnCreate property is set to be invisible on the CreateInput
operation of the ItemRevision business object. You cannot see the checkout
check box option in the generic New Item creation wizard dialog box. You must
explicitly check out the dataset after an Item business object is created.
Use the legacy New Item creation wizard dialog box to check out on create
operations without checking out the dataset after the Item business object is
created. To display the legacy dialog box, set the TC_Enable_Legacy_Create
preference to Item.
• Required create operation refactoring for GRM_create postactions

Certain custom operations attached do not execute after migrating them to
Teamcenter 9.1 or later versions.

When a custom template is upgraded to Teamcenter 9.1 or later, postactions that

are attached to the GRM_create create message of ImanRelation are added by
a migration service to the attached value list of the Fnd0MigratedPostActions
global constant.
The purpose of this constant is to allow the create postactions in the attached
value list to be automatically dispatched (or executed) as postactions of the
corresponding save message, in this case the IMAN_save message; however, in
this case, the autodispatch fails and the operation is not executed.
Refactoring operations whose execution is autodispatched from the create
message to the save message and removing the constant attachment are
described as an optional procedure in the Refactor create operations topic in the
Business Modeler IDE Guide.
In this case, the automatic dispatch that makes this refactoring optional does
not work, so refactoring is required.

• Rich client user cannot attach an object to a typed reference property

If there is a typed reference property defined on a business object, changing the
referenced business object for that property is not supported. In earlier versions
of Business Modeler IDE, you could change the referenced business object, but
the database was not updated after deployment. Beginning in Teamcenter 10.1
you cannot change the referenced business object for typed reference properties
from the Business Modeler IDE.
For example, a Business Modeler IDE user creates a typed reference property
in a business object (for example, Item) that refers to another business object
(for example, Form) and deploys the template. Then the user changes the
referenced business object of this property from Form to Dataset in a version
of Business Modeler IDE prior to Teamcenter 10.1 and updates the template
using Teamcenter Environment Manager (TEM). TEM reports the update as
successful. However, the changes are not reflected in the database because it
is not supported. If the user attempts to attach any dataset type object to the
changed property, the rich client does not allow it because it is still expecting
instances of the Form type.
Because the Business Modeler IDE blocks changing the referenced business
object for the typed reference property, the user cannot revert the property to
its original state.
Assume that a typed reference property (for example, a2_myProp) on the Item
business object refers to the Dataset business object as shown in the following
XML sample:
<TcAttribute attributeName="a2_myProp" description=""
attributeType="POM_typed_reference" maxStringLength="0" isArray="false"
followOnExport="false" isNullsAllowed="true" isUnique="false"
isPublicRead="true" isPublicWrite="true" isCandidateKey="false" isTransient="false"
exportAsString="false" noBackpointer="false" typedRefClassName="Dataset"/>
Note This example is for a persistent property (TcAttribute). Similar steps

can be used for a run-time property (TcProperty).
If, in the rich client, an Item instance has the a2_myProp property, but the
property does not accept a Dataset business object, follow these steps to correct
the issue:
1. Open the Teamcenter command prompt.
2. Execute the following command to extract the model from database:

business_model_extractor -u=admin-user-name -p=password -g=dba -mode=all
-outfile=path-to-XML-file
path-to-XML-file can be C:\temp_model.xml or any path to the file where

the output of the extractor should be written.
3. Search for the a2_myProp property in the generated XML file, for example:
<TcAttribute attributeName="a2_myProp"

4. Locate the type property in model, for example:

<TcAttribute attributeName="a2_myProp" attributeType="POM_typed_reference"
typedRefClassName="Form"/>
5. Note that the value of the typedRefClassName attribute is Form.
6. Locate the a2_myProp property in the extension file of your template project
(for example, the default.xml file). The file looks similar to the following:
<TcAttribute attributeName="a2_myProp" description=""
attributeType="POM_typed_reference" maxStringLength="0" isArray="false"
followOnExport="false" isNullsAllowed="true" isUnique="false" isPublicRead="true"
isPublicWrite="true" isCandidateKey="false" isTransient="false"
exportAsString="false" noBackpointer="false" typedRefClassName="Dataset"/>
7. Update the value of the typedRefClassName attribute for this property

(for example, from Dataset to Form).
8. Save the extension file and reload the data model.
9. Correct the model errors, if any.
10. Save, package, and update your template using TEM.
• Published flag is ignored during enterprise tier C++ code generation

The code generated from the Business Modeler IDE ignores the Published flag
set on the operation. In Teamcenter 8, every operation is a published operation.
The published/unpublished flag is provided so that the users can tag their
operations as published or unpublished.
There is no specific workaround for this problem as it does not cause any error in
Business Modeler IDE or the code generated.

Teamcenter interfaces release notes
Teamcenter interfaces release notes
The following release notes pertain to using Teamcenter interfaces.
Rich client
The following release notes pertain to the use of the rich client.
• Delete an assembly item including components not working
You cannot delete an entire product structure using the Delete item and all
child items below option if the product structure has multiple occurrences of
one or more items.
Click the Select all component(s) button in the Delete below dialog box and
ensure the entire product structure is selected before proceeding. The loading
icon in the Delete below dialog box disappears once the entire product structure
is selected.
• Filtering in the Variants view

In the Variants view, when a filtering dialog box is selected for the first time and
some characters are typed to filter the list of values, the filtering does not work
correctly if the characters are uppercase.
Filter using lowercase characters, or close the dialog box and open it again.
• Reporting more objects degrades performance

When using Report Builder, performance is degraded the more objects are
selected for reporting. For example, when reporting 2000 objects, it takes about
2 minutes for the report to complete, 6 minutes for 4000 objects, and 30 minutes
for 8000 objects.
This is a known third-party library issue with the Xalan library.
Use more accurate criteria to generate smaller reports. For example, run a
report on items 1–5,000 and another report on items 5,001–10,000.

• Dialog boxes are hidden in the rich client

In the rich client, after retrieving product views in the Structure Manager or
Manufacturing Process Planner, dialog boxes may be hidden behind the main
rich client user interface, such as those accessed by choosing Edit®Options or
File®Exit. The user is unable to close these dialog boxes.
If the dialog boxes are hidden, and the rich client is unable to respond, do one
of the following:
o Use the Alt+Tab keys to switch back to the Teamcenter application. The
dialog box comes back to the front.
o Launch the task manager, and in the Applications tab, select the Teamcenter
application and click the Switch To button to force the dialog box to the front.
• Item ID assignment during a Save As operation is not correct when

using a seed part
When an item type does not have a naming rule attached to its ID property, the
end user expects that the item ID assigned during the Save As operation should
based on the existing ID value of the item. For example:
1. Start with an existing item whose ID was originally manually entered as
JPG-001.
2. Select the item and choose File®Save As.
3. In the Save As dialog box, click Assign.
The end user expects the ID box to be populated with JPG-002. However, the
assigned ID is retrieved from the item ID counter used to generate new item IDs,
for example, 100101.
Manually enter the ID for the new item instance.
• Microsoft PowerPoint and PDF files open in a new window

When opening a dataset with a Microsoft PowerPoint (.pptx) or Adobe Acrobat
(.pdf) file attached, the file is opened in a new window instead of displaying in
the Viewer view.
This is an issue with Internet Explorer 10 which no longer has add-ons to
support embedding PowerPoint or Adobe Acrobat files. This is a deliberate
change of architecture from Microsoft.

• Issue displaying a ControlContribution object on Linux platforms

The Impact Analysis view in the rich client has a combination box on the toolbar
that is created using a ControlContribution object in the Eclipse framework.
Whenever the view is resized, the ControlContribution object is rendered
twice on the toolbar in Linux.
This is a known issue. For more information, see the following article:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=378847
• Byte size cannot be displayed in property finder formatter search

results
In search results in the Edit menu of the Property Selection dialog box, when
obtaining ImanFile references, the entry for the byte size is missing and the
file size appears twice. The second file size is actually for the property path of
the byte_size attribute. If you select the entry for Dataset.ref_list.byte_size,
the resulting property finder formatter (PFF) column displayed still shows Title
of File Size and has file size data. Therefore, the byte size column and data
cannot be displayed in search results.
PFF cannot display byte sizes in the display tables. Use the properties table or
viewer to see this information.
• Items opened in My Teamcenter in previous session do not appear in

Open Items list
If you open several objects in My Teamcenter, and then exit Teamcenter, only
one item appears in the Open Items list the next time you launch Teamcenter.
This is the designed behavior.
Teamcenter opens only one active view in the previous session. The other tabs
are unopened view references stored in mementos in the Eclipse platform. You
must explicitly open view references by clicking each item or View tab.

• Default values set through the post hook for create actions are ignored
If you customized the post create handler to set the Description property to a
specific value, the File→New→Item dialog box does not save the default value.
Instead, it creates an object with the value specified by the user.
Register the post-action hook on the Save operation to set the appropriate value
for the Description property.
• Hiding commands that are not available on main toolbar menu

The Suppress Commands tree pane displays all the commands added to the
menu bar by a selected application. Any commands that are not added to the
menu bar (for example, added either only to the toolbar or context menu, or
both) are not displayed in the Commands view. An administrative user cannot
hide such commands from application.
You must manually add the command ID to the respective preferences.
For example, to hide the View/Edit Multi Unit Configuration context
menu in My Teamcenter for the dba group, you must edit the
com.teamcenter.rac.ui.perspectives.navigatorPerspective preference and
add the com.teamcenter.rac.effectivtyGroup command ID to the Current
Values box.
If the desired preference does not exist, you must first use Command Suppression
to hide the Edit→Cut menu for the desired application and group/role, and then
edit the preference.
• Clicking the date button does not close the calendar dialog box
If you click the date button, the calendar dialog box appears. If you click the date
button again, the calendar dialog box does not close.
Click the date button twice to close the calendar dialog box.

• Unchecking the Display PDF in browser option in Adobe Reader is not

supported in Teamcenter
If you clear the Display PDF in browser checkbox in Adobe Reader, this setting
is not reflected in Teamcenter.
To observe this issue, perform the following steps:
1. Launch Adobe Reader.
2. Click Edit→Preferences.
3. In the left pane of the Preferences dialog box, click Internet.
4. Under Web Browser Options, clear the Display PDF in browser check box.
Click OK.
5. Log on to Teamcenter.
6. Create an item.
7. Select the item revision and attach a PDF dataset and a DirectModel
dataset (.jt) file to the item revision.
8. Select the PDF dataset and then click the Viewer tab.
No error is displayed. The external Adobe Reader application opens.
9. Select the DirectModel dataset.

No error is displayed.
10. Select the previously viewed PDF dataset and the external Acrobat Reader
does not open. The following error is displayed:
Unable to Download. The system cannot find the path specified.
This behavior persists if you change the setting in Adobe Reader because
Teamcenter does not support the Display PDF in browser option in Adobe Reader.
Keep the Display PDF in browser option selected in Acrobat Reader preferences
to view PDF documents in the Web browser plug-in. Double-click a PDF dataset
to view a PDF document in the external Acrobat Reader application.

• Vertical scroll bar does not work

When you select a specific property to edit it, the vertical scroll bar does not work
using the keyboard keys. This occurs when you select a property of a checked-out
object such as a list or an object array in the Summary view, Viewer view, or the
Properties dialog box. This issue sometimes occurs for Swing widgets that are
embedded in the SWT widgets.
Use the mouse to scroll the page.
• Rich client crashes when thin client is launched in Web Browser

application
If you use the Web Browser application in the rich client and you attempt to open
the thin client within the Web Browser application, the rich client crashes.
Launch the thin client only in a standalone commercial Web browser.
Note For more information about the Web Browser application in the rich
client, see the Application Administration Guide.
• Teamcenter running status is displayed in the system tray and/or Web

browser
When Teamcenter is performing a time-consuming task, the window may seem
nonresponsive. At these times, the status icon and status text shown in the
client window may not be accurate.
An icon is added to the system tray to indicate the running status of Teamcenter.
The icon and tooltip are always available and are updated as the status changes.
The icon indicates the status, and you can also click the icon and select Status.
This invokes a window that contains detailed information about the server and
client status. On operating systems that do not provide a system tray, you can
view status information in a Web browser. The following table describes the
system tray status icons and text.

Server Description Client Description System tray Tooltip

Ready icon There is Ready icon The client is Ready icon Teamcenter
no current responsive. ready
communication
request
between the
client and
server.
Working The client is Ready icon The client is Working icon Teamcenter
icon waiting for a responsive. server processing
response from
the server.
Disconnected The client is Ready icon The client is Not ready icon Teamcenter
icon not currently responsive. client
connected to disconnected
the server. from the server
Ready icon There is Not ready icon The client is not Not ready icon Teamcenter
no current responsive. client not
communication responding
request
between the
client and
server.
Working The client is Not ready icon The client is not Not ready icon Teamcenter
icon waiting for a responsive. client not
response from responding and
the server. server processing
Disconnected The client is Not ready icon The client is not Not ready icon Teamcenter
icon not currently responsive. client is not
connected to responding and
the server. disconnected
from the server.
• Wrong data saved while saving parameter definition objects

When modifying the parameter definition object from the viewer or a properties
page, if you reduce the number of rows or columns and then directly click the
Save or Save and Checkin buttons, the client saves the wrong data.
When you reduce the number of rows or columns during modification of
parameter definition objects, after you enter the value, click some other area in
the properties dialog before you click the Save or Save and Checkin buttons.
• Clipboard Contents dialog box displays duplicate sections

In any application in Teamcenter rich client, when you click the clipboard button
in the bottom right corner, the Clipboard Contents dialog box is hidden behind
the main rich client window. If you click the button again to bring Clipboard
Contents dialog box back in front and resize the dialog box, the dialog box
displays duplicate sections.

• Teamcenter rich client displays ready status before completing some

operations
The rich client displays a ready status before completing some operations.
For example, when opening a large assembly in Structure Manager from My
Teamcenter, the ready status displays in the rich client even though the progress
bar is active and the assembly is not yet displayed in Structure Manager.
When these situations occur, the status is invalid and Teamcenter is still
processing information. The system is still locked from the user entering any
input. You must wait until control is given back from Teamcenter.
• Avoid division character (÷)

The division character (÷) cannot be used in the rich client when specifying
names and descriptions. This character, sometimes copied from Microsoft Office
documents, is actually a control character (0xF7) that is not supported by the
underlying libraries that the rich client uses.
Use something other than the division character when entering names and
descriptions in the rich client.
• Saved changes in PowerPoint do not appear in the dataset

If you open a PowerPoint dataset in the Viewer pane and then open it in the
PowerPoint application by double-clicking the dataset while it is still open in
the Viewer pane, changes made and saved in the application are not saved to
the dataset.
Do one of the following:
o Make changes in the Viewer pane.
o Manually terminate the POWERPNT process.

• Teamcenter rich client modal dialog boxes do not function properly on

most UNIX/Linux servers
On most UNIX/Linux systems, modal dialog boxes may be hidden behind the
main application window. Because the dialog boxes are modal, no keyboard or
mouse interaction is permitted with any other part of the user interface except
for the modal dialog box.
The problem occurs due to a focus issue with the window and is being followed
up with Eclipse and Sun Microsystems. To work around the problem, do either
of the following:
o Close the dialog box and open it again.
o Click another application or window and click back in the Teamcenter rich
client dialog box. Changing focus and bringing it back usually corrects this
problem, and you are then able to edit the text field or text area.

Thin client
The following release notes pertain to the use of the thin client.
• Page does not update after new items are added to the target
When selecting a task in My Worklist and adding a new target (using the Add
New action), the task appears in My Worklist under the target object. However,
the target is now shown in the Summary view in the Item Revision Targets
section.
Clear and reselect the check box against the task in My Worklist. This reloads
the Summary view, and the targets for the task appear. The new target is listed
in the table in the Item Revision Targets section.
• Applet error when using Generate URL with Microsoft Word or Excel
templates
When you attempt to access a live Word URL (from the Generate URL button
in the Export to Word dialog box), Internet Explorer displays an error similar
to the following:
Applet error, not ready. Please retry.
Note The Generate URL button is provided in the Export to Word, Export to
Excel and Generate Report dialog boxes.
You may see this message when using the URL-related use cases from live Word,
live Excel, or Reports.
1. Clear applets loaded from previous builds.

For more information, see the following article:
http://www.java.com/en/download/help/plugin_cache.xml
2. Clear your Web browser’s cache. For example:

o Internet Explorer: Tools→ Internet options→Delete browsing history
o Mozilla Firefox: Tools→Clear Recent History

• Search from search history does not populate hierarchical LOV values
Searching using the search history does not populate hierarchical LOV values in
the thin client. You can observe this issue by performing the following steps:
1. Log on as a Teamcenter administrator.
2. Create a query that includes a hierarchical LOV.
3. Set values on the hierarchical LOV and run the search in the rich client.
4. Log on to the thin client as the same user.
5. Select the same search from the search history.

The search criteria is displayed in the search dialog, but the hierarchical
LOV is not correctly populated like the rest of the search criteria.

To obtain correct search results, you must manually populate all hierarchical
LOV search criteria again before executing the search.

• Thin client shows looping alert box when logon for the first time
In a four-tier environment with GMO, logon through the thin client fails for the
first time. After entering the username and password, the browser continuously
displays the following error message:
Default configuration rule is invalid.
Each time you click OK or close the error message, the error message reappears.
This happens if the default preference value for TC_config_rule_name is set to
LatestReleased. The LatestReleased revision rule does not exist by default.
To resolve this issue, perform one of the following actions:
o Close the browser and restart it. This sets the TC_config_rule_name
preference to Latest Working. Subsequent logons succeed without any
issue.
o Log on to the rich client, set the TC_config_rule_name preference to a

valid revision rule, and then log on to the thin client.
• Use of the ampersand (&) character can cause issues in thin client
In certain cases, use of the ampersand (&) character within strings can cause
incorrect results, especially if there are no spaces before and after the ampersand
character.
Always use a leading and trailing white space character around the ampersand
(&) character. For example, type This & That instead This&That.
• Thin client does not support user names that contain ampersand
characters
The thin client does not support user names containing the ampersand (&)
character.
Avoid creating user names with the ampersand (&) character.
• Changes to preference values in the four-tier rich client are not

reflected in the thin client
If you log on to a four-tier rich client and change a value of a preference, and then
log on to the thin client using the same user account, you do not see the change
in the preference value reflected in the thin client.
You can observe this behavior by performing the following steps:
1. Log on to the four-tier rich client and the thin client using the same user
account.

2. Change a user preference value in the four-tier rich client.
3. Go to the thin client that is already open and check for the change in the
preference value. The changed value is not reflected in the thin client.
This behavior occurs because the Teamcenter server to which the thin client is
connected is not yet refreshed with the latest values of preferences.
This behavior is as designed. To see refreshed preference values in the thin
client, you must log off the thin client before you change preference values in
the four-tier rich client.
1. Log off the thin client if it is already running.
2. Change a user preference value in the four-tier rich client.
3. Log on to the thin client using the same user as for the four-tier rich client,
and then check for the change in the preference value. The modified
preference value is reflected in the thin client.
This behavior applies to thin client sessions running on the same host as the
rich client as well as to thin client sessions running on other hosts.
• Deleted objects not removed from the Favorites folder in the thin client
Deleted items are displayed in the Favorites list. If you click a deleted item
link, the following message is displayed:
The object requested in invalid. Click here to navigate to your Home Folder.

Manually delete the items from the Favorites list.
• PLM XML import/export does not handle import/export of files

associated with a dataset
(First published Teamcenter Engineering 2005)
Thin client PLM XML import/export of datasets does not handle transfer of
associated files attached to a dataset, such as UG NX assemblies and part files.
When a dataset is imported/exported through the thin client PLM XML
import/export, its associated files cannot be imported/exported along with the
PLM XML file containing the dataset definitions.
Use Teamcenter rich client PLM XML import/export to import/export datasets
and their associated files.

Internationalization release notes

The following release notes pertain to the internationalization of Teamcenter.
• Exporting localized properties when a variable length array (VLA) is
empty
The database may contain empty variable length arrays (VLAs) for some
localized properties when there is a blank master locale.
Perform the following steps to duplicate the problem:
1. Launch the Business Modeler IDE and add the following custom properties
to a custom item:
o customProp_one
o customProp_two
Set the Localizable property constant to true for these properties.
2. Deploy the template and log on to the rich client using the master locale
(for example, English).
3. Create an instance of the custom item.
4. Check out the custom item instance, right-click it, and choose Edit
Properties.
5. Provide a master value for the customProp_one property and do not

modify the customProp_two property. At this stage, the customProp_one
property contains a master locale and no localized value, and the
customProp_two property does not contain a master locale or a localized
value.
6. Select the custom item instance and choose Tools®Localization®Export

Translation. In the Export Translations dialog box, click the Translation
button. In the Locale box, select another locale, for example, French. Click
Finish.
7. The exported file contains all the localized properties. Following is sample
XML output:
<L10N locale="fr_FR">
<ObjectInstance typeName="CustomItem" displayName="customInstance"
uidValue="QJUF2HG_AAgcRA">
<Property propertyName="customProp_one" masterLocale="en_US">
<Value index="0">
<MasterValue>
Custom Prop one
</MasterValue>
<LocalizedValue>
User to provide the value in French.
</LocalizedValue>
</Value>
</Property>
</ObjectInstance>

<Property propertyName="customProp_two" masterLocale="en_US">

<Value index="0">
<MasterValue>
</MasterValue>
<LocalizedValue> This property shouldn’t have been exported.
This issue is fixed in TC10.1.
</LocalizedValue>
</Value>
</Property>
</ObjectInstance>
</L10N>
8. The user who is the translator provides the translation for the
customProp_one property.
9. After providing the translation, import the same XML file back by choosing
Tools®Localization®Import Translation.
10. The database contains the VLA for both the properties, but the VLA for the
customProp_two property is empty.
11. Log on to the rich client and check out the custom item instance again.
Modify the customProp_two property and provide the master locale value.
12. Export the file again for translation. The system assumes the translation
exists for all properties and therefore does not find anything to translate.

Check the exported XML files and make sure that there is no property in the
XML file that contains an empty master value. Delete all the XML elements that
contain an empty master value. For example, the following localized property
does not have a master value; delete it from the XML:
<Property propertyName="customProp_two" masterLocale="en_US">
<Value index="0">
<MasterValue>
</MasterValue>
<LocalizedValue> This property shouldn’t have been exported.
This issue is fixed in TC10.1.
</LocalizedValue>
</Value>
</Property>
</ObjectInstance>
To export localized properties when the VLA is empty:

1. Select the objects for which you want to perform translation and choose
Tools®Localization®Export Translation.
2. In the Export Translations dialog box, click the Review button instead of
the Translation button.
3. In the Locale box, select the locale that you want to translate to.
4. Select a status in the Localization Status box.

5. Perform the export.
Your output XML contains all the properties (including the empty properties).
• Edit Properties dialog box prompts for changes in unmodified

properties
Perform the following steps to duplicate the error:
1. Select and check out a business object instance.
2. Right-click the instance and choose Edit Properties.
3. Modify a property that is not localizable. (The Localizable property

constant on the property is set to false in the Business Modeler IDE.)
4. Click Save.
A warning appears stating that other properties have been modified. Those
properties have not been modified; the mentioned properties are localizable
properties.
o If you click Yes, the values from the localizable properties are impacted.
o If you click No, the values from the localizable properties are not
impacted, but the desired modification is not made.

Modify the property using the Summary view instead of the Edit Properties
dialog box.
• Export/Import of translations of compound property values is not fully

functional
When you export or import translations of compound property values, the master
value is lost at the importing site. The import considers the first translation in
the XML file as the master.
1. Add a compound property on a business object.
2. On the source property of the compound property, set the Localizable

constant to true.
3. Deploy the data model in both the exporting and importing sites.
4. In the rich client, create the instances of the object where compound property
is defined.
5. Ensure that the value of compound property exists by also creating the
source object.
6. On the source property, set the translations.

7. Export the objects using PLM XML.
8. Use the PLM XML file created in step 7 to import the data into another site.
Note At the importing site, the translation for master language may be
missing. Some other translation may be indicated as the master.

Until the problem is fully resolved, do not use export or import of translations of
compound property values. Instead, export the translations of source object.
• Text truncated in some TEM panels in Russian locales

In Russian locales, text in some panels in Teamcenter Environment Manager
(TEM) is truncated because it does not fit within the TEM panel.
Change the font sizes TEM uses for these panels. This allows the text to fit
within the TEM panel.
1. Open the TC_ROOT\install\temui.properties file in a text editor.
2. Locate all instances of the following text:

font.size=14
Replace these with the following:

font.size=12
For example:
Original text Replacement text

main.panel.intro.font.size=14 main.panel.intro.font.size=12
main.overview.list.font.size=14 main.overview.title.font.size=12
textpane.font.size=14 textpane.font.size=12
3. Save the changes to the temui.properties file.
4. Restart TEM.
• Localized query using LOVs that have no translations does not find
object
When performing a search on a property that has an attached list of values
(LOV), the search returns no results if the LOV has no translation, and the
search locale is not the master locale.
There are two workarounds. The first workaround is the best to follow:

o If you are not planning on providing translation for the LOV values in all
locales, keep the internal value and display value the same for the LOV to
avoid the issue with the query.
o If the LOV value and display value are different, provide translations for all
the locales. This ensures that the other locales get the same value as the
master translation. See the example below.
Locale LOV value LOV display name

En R Red
Fr R Red
De R Red
En B Blue
Fr B Blue
De B Blue
• Localized property with default value changes its master locale setting
after transfer to remote site
When creating a Teamcenter object instance using a business object type that
has a localized property with a default value, the value of the property is
automatically populated with the default value. However, the localization VLA
associated with this property is not populated with the master locale and the
value. Therefore, when this object is transferred to the remote site that has a
different master locale, the master locale of this localized property is changed to
the remote site master locale.
There are two workarounds to fix this problem.
When creating a custom localized property with default value in the

Business Modeler IDE:
1. Do not define the default value in the property creation dialog box.
Simply create the property first.
2. After the new property is created, modify its InitialValue property

constant and add the initial value in the Modify Property Constant
dialog box.
3. Package and deploy the change.
If you already defined the localized property with the default value from the
property creation dialog box in the Business Modeler IDE:
1. Before transferring the object to the remote site, launch the Edit
Properties dialog box in the rich client.
2. In the Edit Properties dialog box, click the Localization button next to
the localized attribute with the default value.

3. In the Localization button dialog box, click the OK button to dismiss

the dialog box.
4. Close the Edit Properties dialog box and transfer the object to the remote
site.
• ThinClient-GlobalOrg role does not return any users

The ThinClient-GlobalOrg populating role field does not return any users.
The name attribute for a group is defined in its parent class, POM_group. Also,
the name attribute is marked as Localizable in the subclass Group level, not
in the POM_group level. The query uses the POM_group level for group name
searches so it does not use L10N search because it is a common search.
Note This is not the same as the role name. The role_name attribute is
defined in Role and also marked as localizable in Role, so it is a
localized search for role name.
• Warning message dialog boxes for the SaveAs operation

Due to the legacy implementation, the warning message dialog box of the
SaveAs operation behaves differently for the Item and ItemRevision business
objects. A SaveAs operation based on an ItemRevision business object behaves
more like a Revision operation; that is, there is no way to revert back the string
modified in the dialog. As a result, the warning message dialog box only has an
Acknowledge button. However, a SaveAs operation based on an Item business
object has the option to proceed with a user response of Yes or No.
When trying to perform a SaveAs operation on an ItemRevision business
object, keep in mind that any modification to the Localizable field results in the
translations being marked invalid. Do not modify the string in the localized field
if you do not want the existing translation status being changed.
• Incorrect display name

The display name for the type_string attribute on the iman_relation type
is not correct at installation.
Alter the display name using the Business Modeler IDE, and install the updated
template.

• UNIX IDSM issue running UTF-8 character set

The data_share utility fails, and the error states it cannot find an item if
the item_id attribute contains non-English characters. This problem occurs
on UNIX systems when the IDSM daemon is not started with the identical
Teamcenter execution environment settings. By default, the IDSM server
process is started by the UNIX idsminetd daemon in the C locale.
To establish a UNIX Teamcenter UTF-8 character set execution environment,
the following variable settings must be added in the run_tc_idsm.sh IDSM
startup script file located in TC_BIN:
LANG=en_US.UTF-8
LC_ALL=en_US.UTF-8
• Non-English characters are not displayed correctly in a text file

Some of the characters in a text file are not displayed correctly on non-UTF-8
client connecting to a UTF-8 compliant server.
When the server is UTF-8 and the clients are non-UTF-8 clients (for example,
Japanese), text files must be edited only on a client having the same character
set as the text file; otherwise, data loss can occur. Also, when these text files are
not viewed on a system that does not have the same character set as the client,
characters may not be correctly displayed.
• Code page 932

Teamcenter does not support Japanese characters from code page 932
(abbreviated as CP932, also known by the IANA name Windows-31J). This is
Microsoft’s extension of Shift JIS to include NEC special characters (row 13),
NEC selection of IBM extensions (rows 89 to 92), and IBM extensions (rows
115 to 119). The coded character sets are JIS X0201:1997, JIS X0208:1997,
and these extensions.

• Oracle database character set setting for corporate server installation

and upgrade
Upgrade of the GM Overlay template and its dependent templates fails with
error 54034 (The list of values has duplicate values.)
For example, the update log may contain an error similar to the following:
Delete | TcLOVValueAttach | Discipline LOV
| 54034|The list of values has duplicate values.

This problem applies to the GM Overlay template and any template that
contains characters that are not compatible with, or supported by, the character
set (NLS_CHARACTERSET) in the Oracle database.
If the GM Overlay template contains German characters, when it is deployed to
a database that does not support the German character set (WE8MSWIN1252),
German characters such as umlauts and the double s (ß) are stored as different
characters in the database. This causes the Business Modeler IDE comparator
to generate an incorrect delta file.
By default, when an Oracle database instance is created, it is set with the
WE8MSWIN1252 character set (option 1) unless the database administrator
specifically selects a different character set (option 3).
If the database administrator accepts the default character set in the
Initialization Parameters dialog box during Oracle database instance creation,
there are no issues with installing the GM Overlay template. However, if the
database administrator changes the Oracle database character set to anything
other than WE8MSWIN1252, installation or upgrade of the GM Overlay
template most likely fails.
To verify whether the character set is set correctly, run the following SQL
command:
SQL> select * from NLS_DATABASE_PARAMETERS;
Note This problem can occur if any template having non-ASCII characters is
deployed to an Oracle database that has the character set to a value
other than WE8MSWIN1252.
For information about how to modify the database character set to work around
the problem, see the Oracle documentation.

Third-party release notes
Third-party release notes

The following release notes pertaining to components supplied by third parties.
IBM DB2
The following release note pertains to IBM DB2 databases.
• InClass attribute lengths limited to 128 (versus 256) bytes on DB2
In IBM DB2 databases, the InClass table string lengths are limited. For
example, 200 attributes using 256 bytes each exceeds the DB2 maximum row
size (limited by 32K block size).
Limit string definitions in DB to 128 bytes.
Platform-specific release notes
Platform-specific release notes

The following release notes pertaining only to the following platforms:
UNIX platforms
Hewlett-Packard HP-UX
Sun Solaris
IBM AIX
Microsoft Windows
SUSE Linux
Red Hat Linux
Hewlett-Packard HP-UX
The following release notes pertain to Hewlett-Packard HP-UX platforms only.
• Multiprocess ODS is not supported on HP-UX 11.31 (11i v3)
Multiprocess ODS does not operate on HP-UX 11.31. HP-UX 11.31 is also
identified as 11i v3.
Configure the ODS for nonmultiprocess operation or deploy multiprocess ODS
on HP-UX 11.23 (11i v2).
• Starting the pool manager on HP-UX 11i generates errors

If you start the pool manager with a large number of tcserver processes on
HP-UX 11.11, you may get the following error when UNIX system shared
memory segments and semaphores interprocess communication resources are
low:

open: Not enough space

(17739|1) init_acquire failed: Not enough space
ACE_Malloc_T<ACE_MEM_POOL_2, ACE_LOCK,
ACE_CB>::ACE_Malloc_T: Not enough space

To correct the resource issue:
1. Stop the pool manager and kill all running tcserver processes.
2. Free the shared memory segments and semaphores as described below.
3. Remove memory store backing files as described below.
4. Run the list_users utility on the command line.
5. Start the pool manager.
Text server uses shared memory segments and semaphores to control

interprocess communication between the Teamcenter server processes.
Type the ipcs –sb command in a shell to display a list of shared memory
segments and semaphores currently allocated to the system. This list includes
all the shared memory segments and semaphore sets allocated, their identifying
number, the owner, and the number of semaphores in each set.
Occasionally, unexpected termination of Teamcenter processes leaves shared
memory segments and semaphore resources locked. If Teamcenter is not
running, but the ipcs –sb command lists shared memory segments and
semaphores owned by the owner that started the pool manager, these resources
must be freed. If this is not done, shared memory segments and semaphore
resources may not be sufficient on the UNIX system to allow the text server
to use interprocess communication.
Freeing shared memory segments and semaphores
Freeing shared memory segments and semaphores is done by either using the
ipcrm command or by restarting the system. Normally, system administrators
do not want to restart the system only to free shared memory segments and
semaphore resources. Shared memory segments and semaphores can be freed by
performing the following procedure:
Warning Do not attempt to free shared memory segments and semaphore
resources from Teamcenter if the text server process (tcserver) is
running.
1. Log on as root.
2. Type the following command to display the list of shared memory segments
owned by Teamcenter:
ipcs —mb |grep user-id-used-to-start-pool-manager
3. Free the listed shared memory segments by typing:

ipcrm —m ID_1...—m ID_n
Replace ID_1 with the shared memory segment identifying number from
the list.

4. Type the following command to display a list of semaphores owned by

Teamcenter:
ipcs —sb |grep user-id-used-to-start-pool-manager
5. Free the listed semaphores by typing:

ipcrm —s ID_1...—s ID_n
Replace ID_1 with the semaphore identifying number from the list.
Remove memory store backing files

If you are using shared memory and have updated your XML text files, you must
refresh the shared memory cache by removing the memory store backing files.
1. Ensure the system is idle. No Teamcenter server processes can be running.
2. Remove the memory store backing files. The TC_SHARED_MEMORY_DIR

environment variable value specifies the directory where the store backing
files are stored. If you do not set this variable, its value is set by the
tc_profilevars script to be either the TEMP environment variable
(Windows) or the /tmp (UNIX) directory.
Note On Windows, if the environment variable is not available, the TEMP
directory is used.
The shared memory files are created under the

V2007.1.0.last-build-date/database-site-ID/language directory located
in the temporary repository. Server error messages are saved in the
emh_text.xml.mem file. Server strings are saved in the tc_text.xml.mem
file.
At the next process startup, the system finds the shared memory state is no
longer initialized, reads the XML text files, and populates the shared memory
cache, thus creating and populating the shared memory backing store file.
Note You can disable shared memory functionality and revert
system behavior to in-process text storage by setting the
TC_NO_TEXTSRV_SHARED_MEMORY environment variable
to TRUE.
Text server errors involving UNIX shared memory segments and semaphores
often indicate insufficient interprocess communication resources on that UNIX
system. Shared memory segments and semaphores resources may need to be
freed before the text server can use interprocess communication.
In this case, the text server automatically reverts to using tcserver memory to
provide text services. At a time when interprocess communication resources are
available, the text server automatically uses interprocess communication again
for new tcserver processes.

IBM AIX
The following release notes pertain to the IBM AIX platform only.
• Drag and drop of objects does not work on IBM AIX
Drag and drop of objects does not work in the rich client on IBM AIX platforms.
Use copy and paste to achieve the same functionality.
• Teamcenter installation problem with the TZ environment variable

The Teamcenter installation fails with at the install -encrypt stage of
installation.
Check the TZ (timezone) environment variable. The format should be tzn[
|-]hh:[mm[:ss]], for example, EST5EDT, GMT0BST, or IST-5:30. Use of other
formats can cause the images to fail to start. The AIX platform is known to be
sensitive to this issue if the format offered by tzselect and used on Linux is
used, for example, America/New_York.

Microsoft Windows
The following release notes pertain to Microsoft Windows platforms only.
• English-only toolbars on Windows 8
In the thin client on Windows 8, viewer toolbars are not localized. Toolbars
are displayed in English only.
• Slow relogon in four-tier rich client

If the Teamcenter enterprise tier runs on a Windows 2008 Server host with a
firewall that silently ignores TCP SYN messages to ports that are not open,
there can be a significant delay (20-40 seconds) in Teamcenter request processing
for certain use cases. In particular, a delay is likely if a user logs off and then
logs back on within a short time period or if a user’s Teamcenter server has
timed out and the client reconnects. Trend Micro Personal Firewall and the
stealth mode of Windows Firewall are known to exhibit this behavior.
Possible resolutions include disabling the firewall and configuring the firewall
not to suppress TCP connection reset (RST) packets in response to connection
attempts to closed ports. A workaround for the rich client is to turn off SOA
shared sessions (set shareSession=false in the site_specific.propertes file).
• Viewing contents of a ZIP file from Teamcenter on Windows 7

When a user tries to see the contents of a ZIP file from Teamcenter by
double-clicking it, it opens the My Documents folder in Windows Explorer
instead of showing the contents in the ZIP explorer.
This is a known issue on Windows 7. To support the current UnZip tool
definition, download the latest version of Winzip (14.0 or later), which does
support Windows 7.
• Unable to access files in TC_TMP_DIR on Windows 2003 Server

On some Windows 2003 Server configurations, users may not be able to access
log and other files contained in the TC_TMP_DIR directory on the server host.
To ensure that temporary files from different users remain separate, Windows
can assign each user their own TEMP directory. This can be seen when unique
temporary directories are created, such as C:\Temp\1 and C:\Temp\2, instead
of the shared C:\Temp. Each of the temporary directories is accessible only by
the owner of the directory and administrators. In this case, TC_TMP_DIR is
accessible only to the operating system user running the Teamcenter server and
the computer administrator.


You can stop the creation of the subdirectories by changing the Use temporary
folders per session setting to No in the Windows 2003 Terminal Services
Configuration. This sets the C:\Temp directory as the temporary directory
with read permissions for everyone.
• Data lost when editing Microsoft Excel datasets

When you edit a Microsoft Excel dataset and keep the Excel application running,
the dataset changes are not saved.
When editing a Microsoft Excel dataset, close the Excel application after each
edit to save the dataset. Otherwise, use Microsoft Office integration.

Sun Solaris
The following release notes pertain to the Sun Solaris platform only.
• Configure Sun Solaris to ensure unique Ethernet MAC addresses for
multiple interface cards
(First published Teamcenter Engineering 2005)
If multiple interface cards be connected to a common subnet and configured to
boot with nonunique MAC addresses, any multicast activity can severely disrupt
network communications to and from that machine.
Teamcenter 2007 has a JETI pool manager that can be configured to use
a multicast protocol for high performance management of its shared pool
configuration state.
Sun Solaris machines must have the EEPROM local-mac-address? set to true.
In particular, Sun Solaris machines with multiple interface cards installed must
be configured to boot with unique MAC addresses. To identify these, perform one
of the following procedures:
o Look for local-mac-address in the output of prtconf –pv.
For example, the following shows two devices with the same local MAC
address, and shows that the system is booted with local-mac-address?
set to false:
# prtconf -pv | grep local-mac-address
local-mac-address?: ’false’
local-mac-address: 0003bb7d.7c51
o As a root user, run ifconfig –a. As this user, the MAC address is shown
following the ether tag. (If run as a nonroot user, the inet address
information is still shown, which is useful information.)
The following is an example of cards that boot with nonunique MAC
addresses and are configured on the same subnet:
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 123.123.12.101 netmask ffffff00 broadcast 123.123.12.255
ether 0:3:bb:7d:7c:51

For the cards to boot with unique MAC addresses, the EEPROM
local-mac-address? must be set to true and the machine rebooted.
For example, as root user:
init 0
ok setenv local-mac-address? True
ok reset
After this reboot, the following shows the expected change in these commands,
showing unique MAC addresses:

o In the output of prtconf –pv:

# prtconf -pv | grep local-mac-address
local-mac-address?: ’true’
o (Alternative) As a root user, run ifconfig –a:

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
SUSE Linux
The following release notes pertain only to SUSE Linux platforms.

• Rich client crashes while switching between applications on Linux
SUSE
When using a Linux machine with a gnome or KDE desktop, Teamcenter rich
client crashes when switching between applications. This issue occurs when
users work on Linux SUSE 10 SP2 machines with an nVidia graphics card. The
issue is not reproducible when Teamcenter rich client is launched through an
Exceed session connecting to the same Linux machine.
The problem is caused by nVidia drivers. To fix the issue, update to the latest
SuSE certified nVidia driver. Use version 195.36.24 to fix the issue for the
Quadro FX 570 nVidia graphics card.
• Appearance update manager does not start on Linux

The appr_update_manager batch file fails to start on Linux systems and
validation of the appearance_updater process fails because of a known
limitation in starting and returning status from another process.
This happens only at the initial validation stage of the appearance update
manager startup. To work around this, set the following configuration parameter
in the .appr_update_env file:
updater.validation = 0

UNIX platforms
The following release notes pertain to UNIX platforms only.
• PDF files do not open in PDF reader on UNIX platforms
PDF files do not open in PDF reader on UNIX platforms.
Save the PDF file on a local directory, then open it using Adobe Acrobat Reader.
• Dialog box is hidden behind the workbench window on UNIX and Linux
While running the rich client from a local XWindows session on the UNIX and
Linux platforms, a modal dialog box launched from another dialog box is hidden
behind the main workbench window.
Move the topmost windows to find the dialog box you were working with.
• Character set prerequisite for GM Overlay installation on UNIX

Installation or upgrade of the GM Overlay feature fails if the ISO8859-1
character set is not loaded.
Run the locale –a command in a shell. If the output does not include ISO8859-1,
you must add this character set before you install or use GM Overlay:
1. Set or export the LC_ALL environment variable by typing
LC_ALL=en_US.ISO8859-1 or the equivalent command for your platform.
2. Verify the setting using the echo command or equivalent. Make sure the
correct value for LC_ALL is displayed.
3. Run the locale command and make sure the LANG variable and all the
LC_x variables are set the same as LC_ALL.
4. If LANG is still set to C, manually export LANG to be the same value as

LC_ALL.
5. Launch Teamcenter Environment Manager (tem.sh) from the current shell.
Alternatively, your system administrator may modify the date file (named
TIMEZONE in the etc directory), which can preset this environment, so every
time you log on and launch a shell, the environment is preset.
The recommended method, however, is to log on to the system using the Common
Desktop Environment (CDE) with the minimum required locale (ISO8859-1) by
choosing Option→Language→en_US.ISO8859-1 during logon.
If the ISO8859-1 character set is not loaded on your machine, contact your
system administrator to have it installed before you install the GM Overlay.

This requirement is due to changes in the installation process for Teamcenter

2007, which uses XML files rather than .dat files and associated scripts. Because
of this, GM Overlay data is transformed from .dat files into XML files.
To read and parse the XML files correctly, the system must be able to process
non-English (non-ASCII) locale characters. To facilitate this, the system must be
first loaded with the fonts for that locale.
Note Ensure the ISO8859-1 character set is loaded before you add any
Teamcenter features to your configuration that contains the GM Overlay.
If the ISO8859-1 character set is not loaded, lists of values (LOVs) for
GM Overlay are corrupted during feature installation.

Apple Macintosh MacOS

The following release notes pertain to the Apple Macintosh MacOS platform only.
• Changes to viewer file associations for MacOSX 10.6
The viewer executable is an X11/Motif application that is launched by a Korn
shell script. An application is required to open files from Finder or download
files through a the browser.
In the Lifecycle Visualization installation directory, there is a simple native
MacOSX application named ViewerLauncher.app that can be associated with
files that can be opened using the viewer.
The application executes one of the launch scripts for the viewer:
bin/vvbaselaunch
bin/vvstdlaunch
bin/vvprolaunch
Within the ViewerLauncher package is a file that controls the viewer service
level to be launched:
ViewerLauncher.app/Contents/Resources/English.lproj/Settings.txt
The file contains the following settings:

##
# Settings for Viewer Level
##
##
# ViewerLevel = PRO_LEVEL
# ViewerLevel = STD_LEVEL
# ViewerLevel = BASE_LEVEL
##
ViewerLevel = PRO_LEVEL
The default viewer level is VisView Professional.

The viewer launcher assumes the Lifecycle Visualization bin directory is either
at the same level or an immediate subdirectory of the ViewerLauncher.app
directory.
You can move all of the installation directories under the ViewerLauncher.app
directory, then relocate the ViewerLauncher.app directory, for example:
cd Siemens/Teamcenter9/Visualization
mv * ViewerLauncher.app
/bin/ls -F ViewerLauncher.app
Contents/
Darwin_i386/
TTFonts/
app_defaults/
bin/
common/
demos/
etc/

help/
install.log
license/
source.zip
support/
mv ViewerLauncher.app /Applications

Documentation release notes
Teamcenter 10.1 documentation

The following notes contain corrections or additions to the Teamcenter 10.1
documentation.
Note For documentation release notes pertaining to Product Master Management,
see the Product Master Management Release Bulletin.
Teamcenter 10.1 online help collection

The following release notes pertain to general issues that affect the Teamcenter 10.1
online help collection.
• Teamcenter does not support WinZip
Siemens PLM Software does not support use of WinZip for extracting Teamcenter
files or for any Teamcenter customization or archiving actions. Use another
ZIP utility, for example, 7-Zip.
In the Teamcenter online help collection, replace all specific references to WinZip
with 7-Zip.
This applies to the following deliverables:
Security Services Installation/Customization

Installation on Windows Servers Guide
Dispatcher Server Installation Guide
NX Remote Manager Guide
Getting Started with Manufacturing
Business Modeler IDE Guide

Application Administration Guide

The following release notes pertain to the Application Administration Guide.
• Installing the Autonomy Full Text Search engine
The following will be added to the Configuring FTS preferences topic in the
Application Administration Guide and to the Teamcenter Environment Manager
Help.
You install the full-text search engine using Teamcenter Environment Manager
(TEM).
The Autonomy full-text search engine enables users to retrieve objects from the
Teamcenter database based on search criteria. It allows users to specify searches
on metadata values, as well as full-text retrieval searches on both metadata and
common forms of text data.
The Autonomy full-text search system requires three servers that are installed,
configured, and active:
o IDOL server
The Autonomy Intelligent Data Operating Layer (IDOL) server includes
the content server, community server, category server, Agentstore server,
and the IndexTasks component. AutonomyIDOLServer.cfg is the IDOL
server configuration file. AutonomyIDOLServer.exe is the IDOL server
executable.
During installation, you can display the IDOL server version by going to the
Autonomy installation directory and running the IDOL executable with
the -version flag:
autonomy/idol/idol.exe –version
After installation and configuration, you can use a Web browser to display
IDOL server version information at:
http://host:aciport/action=getversion
host is the IP address of the machine on which IDOL resides.
aciport is the ACI port of IDOL specified by the Port parameter in the
IDOL configuration file’s [Server] section.

o DiSH Distributed Service Handler

This is required for licensing. The executable file is AutonomyDISH.exe.
You can use a Web browser to display license server information at:
http://DiSHhost:port/action=LicenseInfo
DiSHhost is the IP address of the machine on which DiSH resides.
port is the ACI port of DiSH specified by the Port parameter in the DiSH
configuration file’s [Server] section.
o File System Fetch server

The installation directory contains file system connector folders and files for
connecting to Teamcenter.
During installation, you can display the File System Fetch (FSF) server
version by going to the Autonomy installation directory and running the
fsf.exe executable file with the version flag:
autonomy/fsf/fsf.exe -version
Note To determine the version of the Autonomy Intelligent Data Operating

Layer (IDOL) server and the File System Fetch server being installed:
o Prior to configuration, in the installation directory, run
system_path/autonomy/IDOL/idol.exe –version to display a
dialog box with the version information.
For more information about installing the full-text search engine, see the
Teamcenter Environment Manager Help and the appropriate server installation
guide (for Windows or UNIX/Linux).
For information about the support and services available to Autonomy customers,
see the Autonomy services Web page:
https://customers.autonomy.com/support/index.html
• Configuring full-text search

The following will be added to the Configuring FTS preferences topic in the
The search engine configuration file, typically IDOL.cfg, is located in a
default installation in the autonomy/IDOL directory under the location
where the software is installed. After installation on Windows, go to Control
Panel®Services and double-click the idol service. This displays a dialog box
that shows the location of the executable file and the configuration file.
The TC_fts_indexed_types preference has an additional default value: HTML.

You can use the following preferences to modify the behavior of the Autonomy
search engine:
o TC_fts_any_language
Enables searches to return documents in any language for your query rather
than only in the query’s language.
Valid values are:
true
Searches return documents in any language.
false
Searches return documents only in the query’s language. This is the
default value for the preference.
o TC_fts_default_AND_operator
Activates the default logical operator of keyword search to AND.
Valid values are:
true
The default logical operator is set to AND.
false
No default logical operator is set. This is the default value for the
preference.
o TC_fts_hierarchical_index_delete
Specifies whether full-text search index and delete operations are
hierarchical.
Valid values are:
true
Subtypes are valid index and delete types. This is the default value for
the preference.
false
Subtypes are not valid index and delete types.
For example, when the TC_fts_hierarchical_index_delete

preference value is true and the type Item is listed in the preference
TC_fts_indexed_types value list, the subtypes of Item are valid index
and delete types.
o TC_fts_realtime_delete_cache_size
Specifies the cache size (number of objects) for real-time, full-text search
delete actions.
Valid values are any positive integer. The default value is 10.

o TC_fts_realtime_index_dt_cache_size
Specifies the cache size (number of objects) for the real-time, full-text search
dataset index actions.
Note Increase the value to cause fewer Autonomy calls to generate
indexing and potentially remove duplicated objects.
o TC_fts_realtime_index_item_cache_size
Specifies the cache size (number of objects) for real-time, full text search
item index actions.
Note Increase the value to cause fewer Autonomy calls to generate
indexing and potentially remove duplicated objects.
o TC_fts_result_latest_ItemRevision
Specifies whether keyword searches return only the latest item revisions.
Valid values are:
true
Return only the latest item revisions.
false
Return all item revisions. This is the default value for the preference.
o TC_fts_shared_tmp_dir_autonomy_path
Specifies the temporary exchange directory path for the machine where the
Autonomy server is running.
This preference is defined in a new installation but has no default value and
no instance created.
A valid value can be a UNC path or a local path, using forward slash / as a
separator, such as //myserver/shared, F:/shared, and /tmp.
Note The user account used to start the Autonomy server must have write
privileges to this directory.
A value specified in this preference overrides values defined by the
TC_fts_shared_tmp_dir_wnt and TC_fts_shared_tmp_dir_unix
preferences.

o TC_fts_shared_tmp_dir_unix
Specifies the temporary exchange directory for the UNIX machine where the
Teamcenter server or Autonomy server are running.
The separator used in this preference value must be the forward slash /, for
example, /mynetwork/mysite/myfolder.
This preference is defined in a new installation, but has no default value and
o TC_fts_shared_tmp_dir_wnt
Specifies the temporary exchange directory for the Windows host where the
Teamcenter server or Autonomy server is running.
The separator used in the preference value must be the back slash \, for
example, \\mynetwork\mysite\myfolder.
This preference is defined in a new installation but has no default value and
o TC_fts_supported_files
Specifies types of files that can be indexed.
Valid values are file extensions, for example, txt.
Default values are .as, .aw, .csv, .dat, .dc, .dif, .doc, .docm, .docx, .dot,
.dotm, .dotx, .eml, .epub, .fff, .htm, .ip, .mdb, .mif, .msg, .ods, .pdf,
.ppt, .pptx, .rtf, .stc, .sxc, .txt, .various, .vdx, .wo, .wpd, .xml, .xla,
.xlam, .xls, .xlsm, .xlsx, .xlt, .xltm, .xltx, and .xlw.
o TC_fts_use_shared_tmp_dir
Specifies whether the Autonomy server uses a network-shared folder as
a temporary work directory.
Valid values are:
true
The Autonomy server uses a network-shared folder as a temporary
work directory.
false
The Autonomy server does not use a network-shared folder as a
temporary work directory. This is the default value for the preference.
Caution When the Teamcenter server and the Autonomy server are
installed on different hosts, this preference must be set to true.

o TC_fts_windows_autonomy_server
Specifies whether the Autonomy server is installed on a Windows platform.
Valid values are:
true
The Autonomy server is installed on a Windows platform. This is the
default value for the preference.
false
The Autonomy server is not installed on a Windows platform.
For information about configuring the Autonomy full-text search capability, see
the Application Administration Guide.
• Supported Autonomy file types

The TC_fts_indexed_types preference specifies types whose objects can be
indexed. The default values for this preference are Text, MSWord, MSWordX,
HTML, MSExcel MSExcelX, MSPowerPoint, MSPowerPointX, and PDF.
The Autonomy search engine supports numerous data formats in addition
to the file types supported by default in Teamcenter, but file type extensions
must be added to the TC_fts_supported_files preference to be indexed. For
example, the compressed format .zip file extension must be added to the
TC_fts_supported_files preference if you want to index text-based .zip files.
Note You can run the build_fts_index utility to build keyword indexes for
the Autonomy search engine on an object-by-object basis for both the
properties of dataset objects and the contents of dataset files.
For information about the build_fts_index utility, see the Utilities
Reference.

• Starting and stopping Autonomy servers

Starting the DiSH licensing server and the IDOL server
1. Start the DiSH licensing server by doing one of the following:
o Use the start script (UNIX).
o Double-click the InstallationDiSH.exe file in your installation

directory (Windows).
o Start the DiSH Service from a system dialog box (Windows).
2. Start the IDOL server by doing one of the following:
o Use the start script (UNIX).
o Double-click the InstallationIDOLServer.exe file in your installation

directory (Windows).
o Start the IDOL Service from a system dialog box (Windows).
Stopping Autonomy servers
o To stop the Autonomy servers on Windows systems, use the Control

Panel®Services dialog box to select and stop the services.
o To stop the Autonomy servers on UNIX/Linux systems, use the scripts

provided in the appropriate directories to stop the servers.
o To stop the Autonomy servers from the service port, send the following
command:
http://host:servicePort/action=stop
host is the IP address of the machine on which IDOL resides.
servicePort is the ACI port of IDOL specified by the Port parameter in

the IDOL configuration file [Server] section.
• Special characters
Wildcards can be used when performing keyword searches; however, partial
keywords without wildcard characters cannot be used.
The following wildcards can be used in queries:
o ?
Used to match one character.
o *
Used to match zero or more characters.

Note You can use the UnstemmedMinDocOccs parameter in the [Server]

section of the configuration file to specify the number of documents in
which a term must occur for it to be considered in a wildcard search.
You cannot use wildcards to search for numeric characters if the
SplitNumbers configuration setting is set to true in the [Server]
section of the configuration file.
• Displaying help for IDOL server configuration parameters and action

commands
You can display IDOL server help by entering the following command from your
Web browser:
http://host:port/action=Help
o host is the IP address of the machine on which IDOL resides.
o port is the ACI port of IDOL specified by the Port parameter in the IDOL
configuration file [Server] section.
Note You can also view help without starting IDOL server. In the IDOL server
installation directory, open the help directory and click index.html.
• Troubleshooting full-text search installation

Use the following resources to investigate problems in a full-text search
installation:
o Log files created in the Autonomy installation directory structure
o Teamcenter log files generated by your session
o build_fts_index utility using the report argument
• Performing case-sensitive searches

By default, Autonomy searches are not case sensitive, but if you enter a keyword
search term within quotation marks and preceded by a tilde (~), the search
is case sensitive.
For example, to find the term Financial using case-sensitive search, use the
following syntax (including the quotation marks and tilde) in your search:
"~Financial"
Note Case sensitivity must be enabled in the IDOL configuration file.

• Dataset search and dataset keyword search differences

A dataset keyword search retrieves objects based on metadata and the contents
of dataset files using only the full-text search engine index.
A dataset search retrieves objects based on dataset metadata from the
Teamcenter database and on dataset content from the full-text search engine
index.
• Default FTS queries

After the Autonomy search engine is installed and configured at your site, you
can perform full-text searches on dataset files. Three full-text search queries are
standard with Teamcenter: Dataset Keyword Search, Dataset..., and Keyword
Search.
• Using the build_fts_index utility

Note the following:
o The build_fts_index utility is documented in the Utilities Reference.
o The -filter option is not used. It is replaced by the tc_fts_indexed_types

and tc_fts_supported_files preferences.
o For the -entry and -value arguments, -entry is the criteria name on a
search form and -value is the input for the criteria.
o For searches using the Modified after criteria, the value must be later than
installation date.
For more information about updates to the build_fts_index utility

documentation, see the Utilities Reference.
• Installing a PostScript printer on Windows

The following information will be added to the Configuring Lifecycle Visualization
topics.
Note You must have administrative permission to perform this task.
After installing Lifecycle Visualization, check for the existence of a PostScript

Printer entry in the Printers section of the Control Panel. If a PostScript Printer
entry does not exist, run the InstallPrinter.bat file from the following location:
install-path\Visualization\VVCP\Driver
This batch file assumes the c:\temp directory exists. If this directory does
not exist, create the directory before running the batch file, or modify the
PORTNAME value near the top of the batch file to place the psout.ps file
in a directory writable by all potential users of the Lifecycle Visualization
installation. The modified PORTNAME value must be less than 40 characters
in length.
If the Windows can’t verify the publisher of this driver software message is
displayed, click Install this driver software anyway.

Note For information about installing a PostScript printer on Windows 8 or

Windows Server, see the stand-alone Lifecycle Visualization Installation
Guide.
• Command Suppression user interface change

o The Suppress commands for roles topic has an error in step 2. The text
should say Filters instead of Index. The step will be changed to:
You can suppress commands for roles without selecting the group to
which it belongs.
1. In My Teamcenter, choose Edit→Options.
2. Click Filters.
3. Click New.
o The Display commands for roles topic has an error in the title. The title will
be changed to Delete commands for roles. The topic also has an error in step
2. The text should say Filters instead of Index. The step will be changed to:
You can delete commands for roles without selecting the group to which
it belongs.
1. In My Teamcenter, choose Edit→Options.
2. Click Filters.
3. Click New.

Audit Manager Guide

The following release notes pertain to the Audit Manager.
Exporting and importing audit logs along with items
• To include audit logs associated with items when you export and import items
from one site to another using high level data transfer, update the options in the
TIEUnconfiguredExportDefault transfer option set as follows:
o To export audit logs, set the value of the Opt_exp_auditrec option to True.
The default value is False.
o To export workflow audit logs, set the value of the Opt_exp_workflow option
to True. The default value is False.
• To include audit logs associated with items when you export and import items
from one site to another using low level data transfer, update the options in the
SiteConsolidationDefault transfer option set as follows:
o To export audit logs, set the value of the Opt_exp_auditrec option to True.
The default value is True.
o To export workflow audit logs, set the value of the Opt_exp_workflow option
to True. The default value is False.
For more information about modifying transfer option sets, see the PLM
XML/TC XML Export Import Administration Guide.
Best practices for managing audit logs
• Avoid activating audit definitions you do not require.
• Do not deactivate EPMTask-Add Attachment audit definition as some

workflow queries are dependent on the Add Attachment event.
• Frequently purge or archive old audit data.
• When migrating from legacy Audit Manager to the new Audit Manager, use the
date range option to limit the number of audit records for efficient processing.

Business Modeler IDE Guide

The following release notes pertain to the Business Modeler IDE Guide.
• Compound property rules cannot be modified using live update
The Introduction to deploying templates topic incorrectly lists compound property
rules among the data model elements that can be modified using live update.
To correct the problem, the entire list of data model elements presented at the
end of the topic will be removed. Readers will be directed to the Data elements
that can be updated live topic for the list of data elements that can be modified
using live update.
• Location of the sample Mapping Designer projects

The following changes will be made to the Import the sample Mapping Designer
projects topic:
Step 1 will be changed to the following:
1. Browse to the TC_DATA directory on a Teamcenter server installation and

locate the mapping_designer_projects_project-name.zip files. Copy these
ZIP files to a location on your machine and unzip them. The sample projects
are contained in directories in each ZIP file. (See the readme files under each
directory for more information about the projects.)
Note You can perform mapping of Systems Engineering and
Requirements Management to Teamcenter using the example in the
TC_DATA\tcse_migration directory.
• TC_MFK_DEFAULT_DOMAIN preference
In the Managing multifield keys topic, under the
TC_MFK_DEFAULT_DOMAIN bullet, this sentence:
Defines the domain used by find operations when the multifield key unique
identifier is not used.
will be changed to:
Defines the domain used by the ITEM_find_item ITK function when

the multifield key unique identifier is not used.

• Render definition examples

The following will be added to the Render definition examples topic:
In this example, different overlay icons are visible depending on the IP
classification of the object:
<icons Version="1.0">
<propertyMap name="ip_classificationMap">
<item key="Public" value="EMR8_green_overlay_16.png"/>
<item key="Internal Use" value="EMR8_blue_overlay_16.png"/>
<item key="Confidential" value="EMR8_yellow_overlay_16.png"/>
<item key="Development" value="EMR8_purple_overlay_16.png"/>
<item key="Restricted" value="EMR8_red_overlay_16.png"/>
</propertyMap>
<primaryIcon source="Fnd0Icon"/>
<overlayIcon source="ip_classification" mapName="ip_classificationMap" />
</icons>
• Lists of values should not be attached to the properties of the

ListofValues business object
The following note will be added to the Attach an LOV to a property topic:
Note Attaching lists of values to the properties of the ListofValues business
object or to any of its children business objects is not supported. If you
have attached lists of values to the properties of the ListofValues
business object or to any of its children business objects in your custom
template, you must delete the attachments prior to using the custom
template in the upgrade process.
• Business object constants reference

The following business object constants will be added to the Business object
constants reference topic:
o Fnd04GDObjectSelectionCriteria
Defines the selection criteria of the 4GD class. If a particular subclass of the
POM object has a value, the object of this subclass is supported as a root
object for the Multi-Site Collaboration utilities. This constant is placed on
the POM_object business object and its children. It has no default value.
Type a value in the Value box to add the class to use.
This constant is provided by the foundation template file.
o Fnd0OBJIOSuppportedType
Specifies that legacy object import and export processing is supported if the
value is set to true. This constant is placed on the POM_object business
object and its children. The default value is true. Select the Value check box
to toggle the value between true and false.

• Global constants reference

The following global constants will be added to the Global constants reference
topic:
o Fnd0AllowSameParamReqMutipleTime
If the value of this constant is true, it allows multiple attachments of a
parametric requirement or parametric requirement revision object to an
item or revision using the parametric requirements lists relation. The
default value is false.
For more information about attaching parametric requirements to an item
or item revision, see the My Teamcenter Guide.
• Correction to the BMF_SESSION_register_epm_handlers name

In the Register custom workflow handlers topic, all instances of _emp_ appearing
in the BMF_SESSION_register_emp_handlers name will be changed to
_epm_.
Classification Administration Guide

The following topic will be added to the Getting started with Classification
Administration topic of the Classification Administration Guide.
• Customizing the classification menu commands
You can hide Classification menu commands using the Command Suppression
application.
For more information, see the Application Administration Guide.
If you create new groups within Teamcenter, you can hide the following
Teamcenter menu commands (and buttons) that are displayed by default but not
used by the Classification applications. These menu commands and buttons are
hidden by default for the groups that are delivered with the software.
o File®Save
o Edit®Cut
o Edit®Copy
o Edit®Paste
o Edit®Delete


The following release notes pertain to the Client Customization Programmer’s Guide.
• Notes for the conditions and GoverningProperty tags

The notes in the conditions and GoverningProperty topics will be changed to
the following:
Note The conditions and GoverningProperty tags do not work in the
Viewer view if the style sheet is registered for properties or form display.
• Note for the visibleWhen attribute

The following note will be added to the page topic under the visibleWhen
attribute:
Note If there is only one page, and the visibleWhen condition hides this page,
the rich client ignores this condition and makes the page visible.
• Command line options for rich client startup

The following sentence will be added to the final bulleted item in the note in the
Command line options for rich client startup topic:
If you have multiple rich client installations on your system, the constructed URL
only opens the most recently installed rich client because the registry is updated
at each installation.

• Common Teamcenter command IDs

The following changes will be made to the Common Teamcenter command IDs
topic:
o The following note will be added:

Note This topic lists only the most common command IDs. For
a comprehensive list of Teamcenter command IDs, see the
CommandIds.xlsx file in GTAC.
You can access the file in the Product Updates section of GTAC
in the Teamcenter\patch\customer directory or by launching the
following URL:
http://ftp.ugs.com/special.php?dir=/teamcenter/patch
o In the Edit menu commands table, all instances of:

File®Edit
will be changed to:
Edit
• Localizing style sheets

The following note will be added to the Localizing style sheets topic:
Note There is no automated upgrade utility to move custom key/value pairs
into the tc_xrt_text_locale.xml file. You must move them manually.
Data Exchange Guide

The following release notes pertain to the Data Exchange Guide.
projects topic.

Note You can perform mapping of Teamcenter to Teamcenter using the
project examples in the tc2tc and TeamcenterToTeamcenter
directories in the mapping_designer_projects.zip file. See the
readme files for details about what the examples provide.

• ODS operations are not supported between Teamcenter and Teamcenter

Enterprise
In the Data sharing®Using Data Exchange from Teamcenter® Working with
remote objects using ODS topic, add the following note:
Note ODS operations are not supported between Teamcenter and Teamcenter
Enterprise sites. All Data Exchange operations related to ODS are
supported only for Teamcenter-to-Teamcenter operations. This includes
publishing objects to the ODS, remote search operations, and remote
import operations based on remote search results.
Dimensional Planning and Validation Administration Guide

The following release notes pertain to the Dimensional Planning and Validation
• Changes to the Business Modeler IDE user interface
The following updates will be made based on changes to the Business Modeler
IDE user interface:
o In the Business Modeler IDE, the Business Modeler IDE perspective is

renamed to the Advanced perspective.
Therefore, the following text in step 1 of the (Optional) Add the feature
attributes to the list of values in Business Modeler IDE topic:
Access the Business Modeler IDE perspective by choosing
Window®Open Perspective®Other®Business Modeler IDE.
will be changed to:
Access the Advanced perspective by choosing Window®Open

Perspective®Other®Advanced.
o In the Save the project and deploy it to Teamcenter topic, the following text:
Choose File®Save Data Model and click OK.
will be changed to:
Choose BMIDE®Save Data Model and click OK.

Dispatcher Server Installation Guide

The following release note pertains to the Dispatcher Server Installation Guide.
• Configuring the dispatcher client for SSO
Step 2 in the Configuring dispatcher client for SSO topic of Installing
and configuring the dispatcher client describes how to edit the
DispatcherClient\conf\Service.properties file. You need not perform step 2.
Getting Started with Document Management

The following release notes pertain to Getting Started with Document Management.
• Autonomy not supported on HP Itanium
The following note will be added to the Configuring full-text search topic:
Note Autonomy version 7.3.4 does not support the Japanese locale on the
HP Itanium platform. The Japanese locale is supported by Autonomy
version 7.3.4 on the generic HP platform.
For information about version support for compatible third-party
software, see the Siemens PLM Software Certification Database:
• Supported versions for third-party products

The following note will be added to the Document management prerequisites
topic:
Note Teamcenter releases are asynchronous with the release of compatible
third-party software, so references to version support for such software
may be out-of-date.
For information about version support for compatible third-party
software, see the Siemens PLM Software Certification Database:

Getting Started with Manufacturing

The following topic will be added to the Configuring the accountability check topic.
Customizing the accountability check report
To customize the accountability report that you generate as an Excel file from the
accountability check, you must modify the style sheet used to create the report or
create a new style sheet. When Teamcenter creates the accountability check report,
it does the following:
1. Creates an XML file.
2. Applies the style sheet to create the Excel report.
3. Deletes the XML file on your local directory.
If you want to customize the report, it is very useful to copy the temporary XML file
before Teamcenter deletes it. To do this, proceed as follows:
1. Open the Report Builder application and remove the acc_chk_rpt_excel.xsl
style sheet from the Selected Stylesheets list using the minus button .

2. Click Modify.
3. Run an accountability check including report generation.
4. Find the XML file in the your-TMP-folder\user\2TierTransientVolume folder.
5. Use this XML file to help you customize the style sheet.
6. After you finish customizing the style sheet, add it to the Selected Stylesheets
list of the Accountability Check Report definition in Report Builder.

Getting Started with Systems Engineering

The following release notes pertain to Getting Started with Systems Engineering.
• Preferences for setting the locations of Microsoft Office Word export

templates
The following preferences will be removed from the list in the Configuring
Teamcenter Systems Engineering topic:
o REQ_spec_template_folder
Defines the path for the folder in which all specification templates are stored.
o REQ_object_template_folder
Defines the path for the folder in which all object templates are stored.
The folder path preferences no longer exist in Teamcenter.
• Preference for configuring behavior modeling tool integration

The Configure the behavior modeling tool integration topic will be removed. The
Bhm0FilterEntriesForBehaviorModeling preference no longer exists in
Teamcenter.
Getting Started with Teamcenter

The following release notes pertain to the Getting Started with Teamcenter.
• Logging on to the Teamcenter rich client

The following note will be added to the Logging on to the Teamcenter rich client
topic in Getting Started with Teamcenter.
Note For information about choosing a display language for the rich client by
using the -nl argument during startup, see the Rich Client Interface
Guide.
Getting Started with Workflow

The following release notes pertain to Getting Started with Workflow.
• Audit - Workflow General query missing from list

In the Creating and running audit queries topic, the Audit - Workflow General
query is missing from the list of predefined audit queries.
• Audit Log dialog box graphic is out-of-date

In the View legacy audit log information topic, the Audit Log dialog box graphic
is out-of-date. The following is the correct graphic.

• Workflow reports erroneously listed as available

In the Process reports topic, the WF - Filtered Audit, WF - Signoffs, and
WF - Unfiltered Audit reports are erroneously listed as available from the
Tools®Reports®Report Builder Reports menu command in My Teamcenter.
• Audit Manager logs from version 2 are not displayed in the Process
History view
The following note will be added to the Reviewing workflow and schedule
progress by viewing the process history topic:
Note If you migrate from Audit Manager version 2 to version 3,
workflow-related events are migrated and are displayed in the Audit
Logs tab. However, the events are not displayed in the Process History
view.

Global Services Customization Guide

The following release notes pertain to the Global Services Customization Guide.
• Viewing content in Global Services
The following note will be added to the Customizing the user interface topic.
Note The content in the Global Services user interface may at times exceed
the window dimensions of your users’ browser. To view all of the content,
use the scroll bars or enlarge the browser window.

Installation on UNIX and Linux Servers Guide

The following release notes pertain to the Installation on UNIX and Linux Servers
Guide.
• Deploying Teamcenter online help on WebSphere

Teamcenter online help requires special considerations when deploying on IBM
WebSphere.
In Adding features®Installing Teamcenter online help®Install online help®
Install online help on the J2EE Web tier, insert the following changes:
o In step 6, insert the following note:

Note The Teamcenter - Online Help solution requires the Web Tier
Infrastructure and Web Tier Core Applications solutions.
If you deploy online help on WebSphere, do not select the Server

Adapter solution.

Note If you deploy online help on WebSphere, set the context root for the
Web application in WebSphere to the enterprise tier ID for the Web
application. This is the value of the Deployable File Name context
parameter or the Enterprise Application Lookup ID context
parameter. Make sure you include the file name (file-name.war)
when specifying the context root.
• Valid characters for Teamcenter passwords

In Teamcenter 10.1, empty passwords are not allowed, and certain characters
are not allowed in passwords.
The Site planning®Required operating system and user accounts topic contains
a caution about characters not allowed in passwords. Replace the caution with
the following:
Caution The password must not be empty nor contain any whitespace
characters such as space, tab, newline, carriage return, form feed,
or vertical tab.
In addition, the password must not contain any of the following
characters:
!@$%’": ;.<>(){}
Similarly replace this caution in the following topics:
o Managing installations and Configurations®Add an existing Teamcenter

database
o Managing installations and Configurations’®Add or configure a database

Installation on Windows Servers Guide

The following release notes pertain to the Installation on Windows Servers Guide.
Teamcenter online help requires special considerations when deploying on IBM
WebSphere.
In Adding features®Installing Teamcenter online help®Install online help®
Install online help on the J2EE Web tier, insert the following changes:

Note The Teamcenter - Online Help solution requires the Web Tier
Infrastructure and Web Tier Core Applications solutions.
If you deploy online help on WebSphere, do not select the Server

Adapter solution.

Note If you deploy online help on WebSphere, set the context root for the
Web application in WebSphere to the enterprise tier ID for the Web
application. This is the value of the Deployable File Name context
parameter or the Enterprise Application Lookup ID context
parameter. Make sure you include the file name (file-name.war)
when specifying the context root.

The Site planning®Required operating system and user accounts topic contains
a caution about characters not allowed in passwords. Replace the caution with
the following:
or vertical tab.
characters:
!@$%’": ;.<>(){}
o Managing installations and Configurations®Add an existing Teamcenter

database
o Managing installations and Configurations’®Add or configure a database

Lifecycle Visualization Integration Guide

The following release notes pertain to the Lifecycle Visualization Integration Guide.
• Saving product views in Massive Model Visualization (MMV) mode
The following information will be added to the Save product views to Teamcenter
topic:
Saving a product view from Lifecycle Visualization to Teamcenter when the
product is displayed in Massive Model Visualization (MMV) mode may take
additional time to complete. This is due to the potential need to expand portions
of the product structure. When product structure is loaded in MMV mode, the
occurrence paths of the visible parts are not fully expanded. Due to the data
model used by Teamcenter product views, the application must expand the
occurrence path to all visible parts.
Localization Guide
The following release notes pertain to the Localization Guide.
• Adding multibyte characters in Teamcenter when the rich client is
launched in English
In Displaying and deploying localized versions of Teamcenter®Displaying
localized versions of Teamcenter on your client workstation, insert the following
topic:
Add multibyte characters when the rich client is launched in English

1. In the rich client \rac\plugins\configuration_config-name directory,
create the customer.properties file, if it does not already exist.
2. Open the customer.properties in a plain text editor.
3. Add the following line to the file to set the UseDefaultSwingFonts

property.
UseDefaultSwingFonts=true
4. Save the file and exit the text editor.
5. Change to the rac\registry directory.
6. Run the genregxml.bat utility to register the change.
Materials Management Solution Guide

The following release notes pertain to the Materials Management Solution Guide.
• Using the material_import utility
The following information will be added to the Importing material into
Teamcenter topic:
Approaches to importing materials

All imported materials (including those which are owned by the local system)
require an external identifier.

o Material and related substances are created as local objects (MatML file
import from a local site).
When a user imports a MatML file using the material_import utility
and specifies the originating site as the local/target site in the XSLT file,
the system creates the material and substances as local objects. Locally
owned objects can be modified from the Teamcenter user interface. You
can use Access Manager to create access rules to prevent modifications of
the material and substance objects in Teamcenter.
If the material already exists, based on the external identifier, in
Teamcenter, a new material revision is created. The MatML input file is
attached as a MatML dataset to the newly created revision.
o Material and related substances are created as replicas (MatML file

import from an external site).
When a user imports a MatML file using the material_import utility
and specifies the originating site as some other external site in the
XSLT file, the system creates the replicas of the material and substance
objects. In this case, the master copy is owned by the external site.
Teamcenter does not allow any modifications to the replica objects from
Teamcenter user interface.
If the material already exists, based on the external identifier, in
Teamcenter, the existing material object is updated with the contents
of the MatML file. This process replaces any existing MatML dataset
attached to the material revision with the new copy of the MatML file.
• Perspective name change in the Business Modeler IDE

In the Business Modeler IDE, the Business Modeler IDE perspective is renamed
to the Advanced perspective.
Therefore, the following text in step 1 of the Add, update, and remove material
properties topic:
Access the Business Modeler IDE perspective by choosing Window®Open
Perspective®Other®Business Modeler IDE.
will be changed to:

• MatML file format example

The example in the MatML file format example topic will be updated to:
<!–– use this tag to add comments to the XML document ––>
<!–– these are the minimal set of data needed to define a material in Teamcenter ––>
<MatML_Doc>
<Material>
<BulkDetails>
<Name>Lead alloy</Name>
<ExternalIdentifier>GRA-111111-114-1</ExternalIdentifier>
<!–– ExternalIdentifier must be unique in Teamcenter>
<Class>
<Name>METAL</Name>
</Class>
<SubstanceData property="5001">
<!–– 5001 is not used in Teamcenter.-->
<!–– 5001 links SubstanceData to SubstanceDetails in the next section -->
<Data format="exponential">65</Data>
</SubstanceData>

</BulkDetails>
</Material>
<Metadata>
<SubstanceDetails id="5001">

<Name>Lead</Name>
<CasNumber>7439-92-1</CasNumber>


<Units description="" name="%">
<Unit>
<Name>%</Name>
</Unit>
</Units>
</SubstanceDetails>
<SubstanceDetails id="5002">
<Name>Lead stearate</Name>
<CasNumber>1072-35-1</CasNumber>
<Units description="" name="%">
<Unit>
<Name>%</Name>
</Unit>
</Units>
</SubstanceDetails>
</Metadata>
</MatML_Doc>

Multi-Site Collaboration Guide

The following release notes pertain to the Multi-Site Collaboration Guide.
• Perspective name change in the Business Modeler IDE
In the Business Modeler IDE, the Business Modeler IDE perspective is renamed
to the Advanced perspective.
Therefore, the following text in step 1 of the Add custom string attributes topic:
Access the Business Modeler IDE perspective by choosing Window®Open
Perspective®Other®Business Modeler IDE.
will be changed to:

• Multi-Site Collaboration licenses

The following the paragraph following the first bullet list in the Multi-Site
Collaboration license considerations topic will be replaced with the following
paragraph:
The ODS license controls the number of ODS sites that can be run in the
network. It is allocated when an ODS daemon starts and released when the
daemon terminates. It is checked during all Multi-Site Collaboration ODS
operations. Ensure you have purchased an ODS license for each ODS site you
plan to run in the network. If you do not have the required ODS licenses, your
Teamcenter users receive an error message when attempting any Multi-Site
Collaboration operation. All licenses can be placed in one ACS accessed by all
ODS processes or they can be distributed to several ACS sheets.
• Multi-Site Collaboration site IDs

The following information will be added to the Site naming convention topic:
The method the Teamcenter installation process uses to generate site IDs
required an upgrade for ID generated beginning on January 1, 2010. Prior to
this date, thegenerate_site_id utility generated only positive integer site IDs.
The available set of IDs was exhausted, requiring a utility upgrade to generate
negative integers.
If you have not downloaded the upgraded utility, you cannot create a new
database. See the Teamcenter-5058 (SFB 5058) software field bulletin,
available from GTAC, for information about the upgraded utility.
If you have sites with negative integer site IDs in your Multi-Site environment,
you must ensure that any utility argument, configuration file entry, or dialog box
entry contains the minus (-) sign prefix for the negative integer site IDs.

• Behavior of project relationships on replica objects

The following information will be added to the data_sync topic:
The behavior of the data_sync and data_share utilities for
project relationships on replica objects can be controlled by the
TC_sync_projects_with_owning_site preference. This preference is not
created by the Teamcenter installation process. To change the default behavior
of shared project relationships, you must create the preference.
For information about controlling project relationships on replica objects, see
the Utilities Reference.
• Content does not display in HTML for the Determining the setup
process topic
The content of the Determining the setup process topic cannot be accessed in the
HTML version of the help collection. The PDF version contains the missing
information. The following content will be made accessible in the HTML:
Review the Planning considerations before beginning the setup procedures as
some procedures are optional and some have optional configurations. The setup
procedures may be dependent on other procedures. Follow this process to ensure
that you have the required procedures completed before you begin a dependent
procedure.
1. Configure the sites in your Multi-Site network.

For information about site configuration, see Configure Multi-Site sites.
2. Configure File Management System (FMS).
3. (Optional) Configure global data caching.
4. (Optional) Set up a hub site.
5. Create remote site definitions

After all sites in the Multi-Site Collaboration network are created and
configured, each site must add site definitions to its database for all other
sites.
For example, Detroit-Manufacturing automatically has its site definition
added to its database during installation. Following installation, the
Detroit-Manufacturing system administrator must manually add site
definitions for the rest of the Multi-Site Collaboration network (for
example, Detroit-Engineering, London-Engineering, Tokyo-Supplier, and
SaoPaulo-Supplier).
For information about creating site definitions, see the Organization Guide.

6. Synchronize POM transmit schema files.

The final Multi-Site Collaboration setup procedure involves synchronizing
Persistent Object Model (POM) transmit schema files among all sites in the
entire Multi-Site Collaboration network. Basically, this involves physically
copying each site POM transmit schema file and sending it to every other
site in the Multi-Site Collaboration network. These copies are stored in
the POM_TRANSMIT_DIR directory.
Caution When IDSM or ODS is configured to run as a Windows
service, you must use a UNC formatted path for the
POM_TRANSMIT_DIR variable. If you use a network drive
(mapped) letter in this variable, the service is not able to locate
the directory to read the required files.
Warning Certain sites may be using more than one POM transmit schema
file. This is because 64-bit and 32-bit platforms require separate
POM transmit schema files. Copy all applicable current POM
transmit schema files.
For additional information about POM transmit directory variable and

schema files, see the Preferences and Environment Variables Reference.
7. (Optional) Configure multiprocess Object Directory Services (ODS).
8. (Optional) Set up partial item export.

Organization Guide
The following release notes pertain to the Organization Guide.
In the Defining users®Specifying password restrictions topic, insert the following
caution at the end of the topic:
or vertical tab.
characters:
!@$%’": ;.<>(){}
Platform Designer Guide

• Hiding Platform Designer
The following note will be added to the Getting Started with Platform Designer
topic:
Customers who do not use Platform Designer may hide the perspective by
adding the string PlatformDesigner to the HiddenPerspectives preference.
This action also hides the Tools®Add Design to Product and Tools®Add Part
to Product menu commands in My Teamcenter and also the Add Design to
Product and Add Part to Product buttons on the toolbar.
PLM XML/TC XML Export Import Administration Guide

The following release notes pertain to the PLM XML/TC XML Export Import
• bl_attachments should not be used
The following note will be added to the Working with transfer mode
objects®Create closure rule example® Step 4: Create traversal rules to export
attachments of a BOM line topic:
Note The BOMLine property bl_attachments should not be used by
Teamcenter applications because it returns run-time objects that do not
persist and are removed after the call to the property. This property is
intended to be used only in defining closure rules.
Alternatively,Siemens PLM Software recommends using the following
SOA APIs to get or close attachment lines:
manufacturing::StructureManagment::getBOMLineAttachments
manufacturing::StructureManagment::closeAttachmentWindow
For information about these APIs, see the Services Guide.

Preferences and Environment Variables Reference

The following release notes pertain to the Preferences and Environment Variables
Reference. A complete description of each new preference follows the notes.
• Valid values for logical preferences
In Managing preferences®Managing preferences®Preference definition elements,
revise the definition of the Logical element to read as follows:
o Logical
Valid value is one of any logical pair (on or off, true or false, yes or no, 0 or 1).
Note Logical preferences may have more than one valid value. For
example, 0, No, Off, and False may all be equivalent valid values of
the same preference that achieve the same result. The value shown
in the Options pane of the user interface may differ from the possible
values listed for a preference, but both values are valid settings.
• Data sharing preference value updates during upgrade

The following new Data sharing preference value updates during upgrade topic
will be added under the Data sharing preferences topic.
When a site is upgraded to a new version, there may be changes in the default
values for preferences as a result of new features or functionality. You can search
for preferences in the rich client to check the values.
For information about searching for preferences by name, see the Rich Client
Interface Guide.
Some of the changes are required to support functionality that you may or may
not use. Unless otherwise indicated, these changes have minor, if any, impact
on data sharing performance.

• Preference default protection scopes, valid values, and descriptions

Some preference descriptions are not updated in the Preferences and
Environment Variables Reference to align fully with the new preference
functionality.
As part of the new functionality, Scope was changed to Protection Scope.
o All preferences have a protection scope of System, Site, Group, Role, or
User. The protection scope is now dynamic; Site, Group, Role, and User
protection scope can be changed by an administrator.
o Each preference definition has an out-of-the box protection scope value.
o The System default protection scope is new. This protection scope cannot
be modified, and only a system administrator can provide a value for the
preference.
o The All protection scope is no longer valid. This concept is now represented
by the Environment Variable location.
The Preferences and Environment Variables Reference provides descriptions for

approximately 2700 preferences. Of these, approximately 250 do not have an
updated default protection scope and may have values such as All, Site and User,
User and Group, and so on. Also, some preference descriptions do not include
one or more standard sections for default values or description.
In cases where preference description information is missing or out-of-date in
the Preferences and Environment Variables Reference, follow these steps to view
the correct information:
1. Choose Edit®Options in the rich client to display the Options dialog box.
2. Click Filters to display the Preferences By Filters pane.
3. Type the preference name in the Search by preference name box.
4. Select the preference from the list.

The preference information is displayed on the right side of the Options
dialog box.
Note Administrator users see all preferences defined for a site.
Nonadministrator users see preferences defined for the site and for the
logged-on group, role, and user.
Siemens PLM Software recommends that you do not modify preference
descriptions.
For more information about Teamcenter preferences, see the Preferences and

• Environment variables listing

The following environment variables will be added to the Environment variables
listing topic:
FCC_PROXYPIPENAME
Defines the base name of the set of FIFOs (pipes) used to communicate with
the FCCClientProxy, for example:
set FCC_PROXYPIPENAME=\\.\pipe\FMSClientPipe|/tmp/FMSClientPipe
The value to the left of | is used for Windows hosts, and the value to the
right of | is used for UNIX and Linux hosts.
The value must exactly match the value of the FCC_ProxyPipeName FCC
configuration parameter in the fcc.xml file.
Note Siemens PLM Software recommends you do not set this parameter
except under certain circumstances where it may be required.
For more information, contact your Siemens PLM Software
representative.
TCCS_CONFIG
Sets the TCCS configuration directory containing information about the
various TCCS environments. This variable is required only when the default
TCCS configuration name is not used.
TCCS_CONFIG_HOME
Sets the TCCS home directory. This variable is required only when the
default home location is not used and a custom TCCS home location is
created.

The following environment variables will be changed:
o TC_LOG_VOLUME_DIR
The name of this environment variable is incorrectly listed as
LOG_VOLUME_DIR. It will be corrected to TC_LOG_VOLUME_DIR in
this topic and throughout the documentation.
In addition, this environment variable is incorrectly shown as
LOG_VOLUME_LOCATION in the documentation. All instances in the
documentation will be corrected to TC_LOG_VOLUME_DIR.
o TC_LOG_VOLUME_NAME
The name of this environment variable is incorrectly listed as
LOG_VOLUME_NAME. It will be corrected to TC_LOG_VOLUME_NAME
in this topic and throughout the documentation.
o TC_TMP_DIR
This environment variable is incorrectly listed as a preference instead of an
environment variable.
To correct this problem, the TC_TMP_DIR topic will be removed from the
Log file preferences topic, and any cross references to the TC_TMP_DIR
preference topic will be changed to point to this new environment variable
definition:
TC_TMP_DIR
Defines the temporary directory for storing temporary files. This value is
typically C:\Temp on Windows and /tmp on UNIX.
o TC_USER_LIB
The definition of this environment variable is incorrect and will be changed
to the following:
TC_USER_LIB
Contains user-defined custom libraries. On Windows systems, the
tc_profilevars file adds this directory to the PATH variable. On UNIX
systems, if this variable is set in the environment, the tc_profilevars
file adds this directory to the LD_LIBRARY_PATHLIB_PATH or
SHLIB_PATH settings.

• DISPLAY_Param_In_NotesText preference
The DISPLAY_Param_In_NotesText preference will be added to the
Dispatcher preferences topic.
• Mail_internal_mail_activated preference
The Mail_internal_mail_activated preference will be added to the Mail
gateway preferences topic.
• Mail_send_file_attachments_activated preference
The Mail_send_file_attachments_activated preference will be added to the
Mail gateway preferences topic.
• NX_Supports_VISSC preference
The NX_Supports_VISSC preference will be added to the Preferences set in the
.tc_preferences.xml file topic.
• ScheduleAvailableAttribute preference
The Valid Values section will be changed to contain the following values in the
ScheduleAvailableAttributes topic.
o The valid value Schedule.status will be changed to Schedule.fnd0status.
o The valid value Schedule.schedule_type will be added.

Displays the schedule type in the Column Chooser dialog box of the
Schedule Manager application when a program view is opened.
• ScheduleTaskClassNameToCreate preference
The ScheduleTaskClassNameToCreate preference will be added to the
Schedule Manager preferences topic.
• TC_directly_transferable_classes preference
The Default Values section will be changed to contain the following values in the
TC_directly_transferable_classes topic.
Item
ItemRevision
Dataset
Folder
Form
PSBOMView
PSBOMViewRevision
EPMTaskTemplate

• TC_ImpactAnalysis_Display_Limit preference
The TC_ImpactAnalysis_Display_Limit preference will be added to the
Client preferences topic.
• TC_MFK_DEFAULT_DOMAIN preference
The following changes will be made to the TC_MFK_DEFAULT_DOMAIN topic:
o This sentence:
Defines the domain used by find operations when the multifield key unique
identifier is not used.
will be changed to:
Defines the domain used by the ITEM_find_item ITK function

when the multifield key unique identifier is not used.
o The default value of the TC_MFK_DEFAULT_DOMAIN preference will be

changed from Item to None.
• TC_relation_required_on_export preference
TC_relation_required_on_export topic.
IMAN_master_form
IMAN_requirement
IMAN_specification
IMAN_ic_intent
IMAN_CCContext
IMAN_StructureContent
IMAN_SCTypeData
TC_Attaches
TCCalendar_Rel_Type

• TC_relation_required_on_transfer preference
TC_relation_required_on_transfer topic.
IMAN_master_form
IMAN_requirement
IMAN_specification
IMAN_RES_audit
IMAN_ic_intent
IMAN_CCContext
IMAN_StructureContent
IMAN_SCTypeData
TC_Attaches
TCCalendar_Rel_Type
IMAN_vi_linked_module
IMAN_vi_sos
IMAN_classification
Fnd0ShapeRelation
• TC_sync_projects_with_owning_site preference
The TC_sync_projects_with_owning_site preference topic will be replaced
with the following:
DESCRIPTION Controls the synchronization of the project list of replicas

with the project list of the master object when projects are
removed at the owning site. By default, when a project is
removed from the master object, the project for the replica
object is not removed. This allows the replica to maintain a
project list that is independent of the master object.
By default, removing all projects from the master object
removes all projects from the replica object.
Use this preference to enable the importing site to override
the default behavior. It must be defined at the importing
site and has no impact on the exporting site. Define this
preference at the importing site.
If performing a push operation using the data_sync or
data_share utility, define the preference at the remote
IDSM site.
Note This preference is not created by the Teamcenter
installation process. If you require this
functionality, you must create the preference.
For information about creating and using preferences, see

the Rich Client Interface Guide.
Tip Siemens PLM Software recommends that you use
the following values when creating this preference:
o Protection Scope: Site

o Category: Data Sharing.Multi-Site

Collaboration
o Environment: Disabled
You must select String from the Type list and

Multiple from the Multiple box.
VALID VALUES Accepts one or more strings as values. Acceptable values

are:
o FALSE
When a project is removed from the master object, the
project is not removed from the replica object. This
is the same as the default behavior. However, if all
projects are removed from the master object, unlike
the default behavior, projects are not removed from
the replica object, allowing the replica to maintain a
project list independent of the master object.
FALSE must be the only entry for the preference.
o ALL
Indicates that for all owning sites, when a project is
removed from the master object, that project is also
removed from the replica object; and when all projects
are removed from the master object, all projects are
removed from the replica object.
o site-name
Indicates the ALL value behavior applies to the
specified site. You can enter a list of sites, one site
name per line. Invalid site names are ignored.
The default behavior applies to all sites not specified.
DEFAULT None.
VALUES
If this preference is not defined, the default behavior
applies to all sites.
DEFAULT Site preference.
PREFERENCE
SCOPE
• WEB_Applications_List preference
The WEB_Applications_List preference will be added to the General thin
client preferences section.
• WEB_Nav_Items_List
The WEB_Nav_Items_List preference will be added to the General thin client
preferences section.

• Word_Export_TcTypes preference
The Word_Export_TcTypes preference will be added to the Client interface
preferences section.

DISPLAY_Param_In_NotesText
DESCRIPTION
Shows or hides the parameter name in the Note Text box of a standard note.
Example If your parameter definition is as follows:
Round all sharp corners to [Radius: 0.4, 0.5, 0.6] inches and heat treat to
[Temperature: 200, 220, 230] degrees Fahrenheit.
• If the value of this preference is true, the Note Text box of the
standard note displays the parameter name and parameter values
as follows:
Round all sharp corners to Radius 0.01 inches and heat treat to
Temperature 100 degrees Fahrenheit.
• If the value of this preference is false, the Note Text box of the
standard note displays only parameter values as follows:
Round all sharp corners to 0.01 inches and heat treat to 100 degrees
Fahrenheit.
VALID
VALUES
true Shows the parameter name in the Note Text box of the standard note.
false Hides the parameter name in the Note Text box of the standard note.
DEFAULT
VALUES
true
DEFAULT
PROTECTION
SCOPE
System preference.

Mail_internal_mail_activated
DESCRIPTION
Specifies whether Teamcenter internal mail functionality is available when using
the EPM-notify workflow handler.
VALID
VALUES
true The Teamcenter internal mail functionality is available when using the
EPM-notify workflow handler.
false The Teamcenter internal mail functionality is not available when using
the EPM-notify workflow handler.
DEFAULT
VALUES
false
DEFAULT
PROTECTION
SCOPE
Site preference.

Mail_send_file_attachments_activated
DESCRIPTION
Activates sending dataset attachments as e-mail file attachments.
This takes effect when the envelope functionality sends messages directly to an
e-mail address instead of a Teamcenter user. When the mail is sent to a Teamcenter
user, this preference has no impact, and the user always receives links to the
envelope object.
VALID
VALUES
true Activates sending dataset attachments as e-mail file attachments. The
recipient can open the attached files without requiring a Teamcenter logon
or privileges. Consider site security guidelines before setting this preference
to true.
false Deactivates sending dataset attachments as e-mail file attachments.
External recipients of e-mails receive only Teamcenter client links to the
attached datasets and not the actual files.
DEFAULT
VALUES
false
DEFAULT
PROTECTION
SCOPE
System preference.

NX_Supports_VISSC
DESCRIPTION
Activates NX support of configuration using the VisStructureContext object
during a Send to NX operation.
VALID
VALUES
true Activates NX support.
false Deactivates NX support. The value must be set to false if using a version
prior to NX 8.5.1.
DEFAULT
VALUES
false
DEFAULT
PROTECTION
SCOPE
User preference.

ScheduleTaskClassNameToCreate
DESCRIPTION
Specifies the type of schedule task that is created through the quick create option
in the rich client.
VALID
VALUES
Any schedule task type.
DEFAULT
VALUES
ScheduleTask
DEFAULT
PROTECTION
SCOPE
User preference.

WEB_Applications_List
DESCRIPTION
Lists the applications displayed in the Teamcenter thin client navigation pane.
Applications are categorized for display as primary or secondary.
VALID
VALUES
The format for valid values is application_name:[primary|secondary]
• application_name
The application name, as listed in the thin client toolbar.xml file as values of
the panel tag name attribute.
• [primary|secondary]
Specifies whether the application appears in the primary application list or the
secondary application list in the thin client navigation pane.
DEFAULT
VALUES
myteamcenter:primary
pse:primary
rm:primary
mse:primary
classification:primary
Adhoc Design Context:primary
Design Context:primary
ScheduleManager:primary
DEFAULT
PROTECTION
SCOPE
User preference.

WEB_Nav_Items_List
DESCRIPTION
Lists the sections to be displayed in the Teamcenter thin client navigation pane. The
sections in the navigation pane are displayed in the order listed in this preference.
VALID
VALUES
Valid values for this preference are section tag id attributes in the thin client
toolbar.xml file.
DEFAULT
VALUES
quicklinks
history
favorites
iwantto
DEFAULT
PROTECTION
SCOPE
User preference.

Word_Export_TcTypes
DESCRIPTION
Specifies the object types that are available for selection in the Override Object
Template for list of the Export to Word dialog box. For the current export operation,
the selected object type can be associated with an object template other than that
which is assigned by default.
The user selects the alternative template in the Available Object Templates pane
of the Export to Word dialog box. That template defines which property values are
exported for objects of the selected type.
VALID
VALUES
Accepts one or more strings as values. Each string must be the real name of an
existing object type.
Note For each object type specified in the value, all subtypes are included in the
Override Object Template for list automatically.
DEFAULT
VALUES
SpecElementRevision
FunctionalityRevision
Fnd0SEBlockRevision
Fnd0DiagramRevision
RequirementSpecRevision
DEFAULT
PROTECTION
SCOPE
Site preference.

Rich Client Interface Guide

The following release notes pertain to the Rich Client Interface Guide.
• Using Sort with advanced search
The following note is added to the description of Sort in the Using the Search
view topic:
Note When you sort an advanced search query created with Query Builder,
two internal preferences are created: QRY_<query_name>_SortKeys
and QRY_<query_name>_SortOrder. If you see a query you are using
has sort keys that do not match the sort keys shown in Query Builder
in the rich client, choose Edit®Options to display the Options dialog
box, and then use the Filters pane to select and delete the existing sort
key user preferences for the query.
• No online help links for some views

The Teamcenter rich client displays views when you select an application and
when you use the Window®Show View®Other command to display the Show
View dialog box.
o In the rich client, some views may not respond to requests for online help. In
most cases, these views are described, and most descriptions include links to
additional information.
o The Rich client views topic lists views by category.

This list may contain views that are not available in your installation
because the corresponding applications are not installed.
Some views included in your installation may not be described in the Rich
client views topic.
If the Teamcenter HTML Help Collection is installed, you can display
documentation for most rich client views by selecting an active view using either
of the following methods:
o Press F1.
o Choose Help®Current Application.
To display information about a view when the Teamcenter HTML Help Collection
is installed, but help is not found for the current rich client view, do the following:
1. Choose Help®Help Library or press Ctrl+F1.
2. Expand Using Teamcenter Interfaces and Managing Basic Objects.
3. Select Rich Client Interface Guide.
4. Choose Managing the Teamcenter client interface®Views available to rich

client application perspectives®Rich client views.

5. Select the appropriate category or scroll to the listing for the view for which
you want documentation.
o If a link is available for more information, click the link.
o If a link is not available for information, use the online help Search
capability.
Note For a more-focused search, use Advanced Search with the this
wording or phrase option.
Schedule Manager Guide

The following release notes pertain to the Schedule Manager Guide.
• List of Reporting and Analytics package reports does not match those
provided in Teamcenter
The list of Reporting and Analytics package reports does not match those
provided in Teamcenter in the Schedule reports topic.
To correct the problem, the following list of reports will replace the existing
list of reports:
o Baseline Comparison
The Baseline Comparison report allows you to compare two baselines
of a specific schedule. The comparison shows how many times the plan
was changed between the two baselines and also the number of on-time
completions of tasks. It shows two dial charts depicting the status of
the baseline comparison and allows you to drill down to look at detailed
comparisons.
o Big Picture
A Big Picture report uses a Gantt format to provide an overlaid management
rollup report. This lets you identify inconsistencies easily and identify
interrelationships across multiple, related endeavors.
o Cross Schedule Tasking

A Cross Schedule Tasking report provides an overview of member tasking
across the specified schedules. This report can be filtered by date range,
status, members, and schedules.
o Deliverable Task
A Deliverable Task report displays the progress of the schedule deliverables
in a schedule.
o Milestone Analysis
A Milestone Analysis report displays schedule slippage in days between
baseline finish dates and scheduled finish dates for all baselines in a
particular workplace.

o Milestone Trend Analysis

The Milestone Trend Analysis report shows the trend of various milestones
in a schedule. This report has the milestone dates on the Y axis and the
reporting dates on the X axis.
o MTR
The MTR report shows a Gantt chart for the selected schedules with
milestones plotted on the schedule timeline itself. The color of the milestone
depends on the milestone status. For example, if a milestone is late, the
color of the milestone in the chart is red. The user can filter on-time period,
schedules in that time period, and milestones in the selected schedules.
o Percent Complete Late

The Percent Complete Late report allows you to find the percentage of late
and complete within the scheduled dates. This report shows two dial charts,
one depicting the percentage of complete tasks and the other showing the
percentage of late tasks.
o Resource Workload
The Resource Workload report shows the task workload of users per month
across all the schedules. This report follows color-coding conventions based
on certain rules. For example, if the workload goes beyond 100 percent, it
is shown in red. This report allows you to drill down to the schedule level
to see the workload of the users for each schedule. User assignments for
schedule tasks should be done only for users, groups, or disciplines and
should not be assigned tasks. This report functions correctly only if the
resource assignment is done with users.
o Schedule Baseline
A Schedule Baseline report displays the difference between a schedule and
a selected baseline. A schedule baseline represents a snapshot of a schedule
at a specific time. This report lets you see how a schedule compares with the
schedule as originally planned, and lets you assess which tasks are overdue
and which tasks are complete early.
o Schedule Overview
A Schedule Overview report displays schedule summary information,
including milestones, overdue tasks, and members participating in the
schedule.

o Schedule Versus Actual

The Schedule Versus Actual report shows a comparison of scheduled and
actual tasks for a certain schedule. This report comprises a pie chart and a
bar chart. The pie chart shows the number of late, early, and on-time tasks.
The bar chart shows the duration of the scheduled and actual tasks.
o Task
A Task report provides a list of tasks assigned to the selected resource.
o Workflow Countdown
A Workflow Countdown report displays the progress of the workflow tasks
in a schedule.
• Saved query functionality is limited

The following note about saved query use will be added to the Export audit logs
or process history to Microsoft Excel topic:
Note You can only run a saved query from My Teamcenter. The saved query
functionality is meant to be executed only when the Schedule tasks
folder is expanded in My Worklist. You cannot run this query from
anywhere else in the system.
• Schedule Membership dialog box is incorrect

The Schedule Membership dialog box is incorrect in the Assigning resources
to schedules and tasks topic.
To correct the problem, a new Schedule Membership dialog box will replace
the old one.
• Description of effort-driven scheduling is incomplete

The Shifting resources within a schedule topic does not provide a complete
description of all ways effort-driven scheduling can be managed. Information
about setting task type to other options besides Fixed Duration should be
included. In addition, more information about the logic used in recalculating
tasks and schedules (duration) when resources are changed will be added to
help users decide between the available options and settings. These issues will
be reviewed and the documentation will be updated at the next release of the
Teamcenter Help Collection.

Service Planner Guide

The following release note pertains to the Service Planner Guide.
• Service Plan is missing from the most recently used (MRU) list
The following note will be added to the Opening the most recently used object and
Create a service plan topics:
Note If the business object display rule for the Item business object is hidden
in the Business Modeler IDE, Service Plan does not show up in the most
recently used (MRU) list.
For more information about setting business object display rules, see
the Business Modeler IDE Guide.
Site Consolidation Guide

The following release notes pertain to the Site Consolidation Guide.
• TCFS references are obsolete
All references to Teamcenter File Services (TCFS) will be removed from the
What can be done when using the sitcons_replicate_mgr and there is failure to
connect? topic.
TCFS was made obsolete in Teamcenter 8.1. All file service functionality is now
performed through File Management System (FMS).
• sitcons_fix_ixr utility is missing arguments

The following -dryrun and -report arguments will be added to the syntax and
argument list for the sitcons_fix_ixr utility reference topic:
SYNTAX
sitcons_fix_ixr -u=user-name {-p=password | -pf=file} [-g=group]
{-f=fix_records | delete_records} [-inputfile=file-name]
[-target_site=site-name] [-source_site=site-name]
[-report=file-name] [-dryrun] [-h]
ARGUMENTS
-report
Specifies the absolute path and file name of the report file. The
report file contains fixes required for export and publish records
(IXR, ITXR and PARs) at a third site and the source site.
If this argument is not specified, the report file is generated in
the transient volume directory.
-dryrun
Generates the report file only. The candidate objects are
searched and listed in the report. The report file contains fixes
required for export and publish records (IXR, ITXR and PARs)
at a third site and the source site.
If this argument is specified, the -f argument function is
ignored. No deletions or updates are performed.

Structure Manager Guide

The following release notes pertain to the Structure Manager Guide.
• Creating a configuration item
The following changes will be made to the Creating a configuration item topic:
o The following sentence will be added to the end of the first paragraph:
The Configuration Item check box appears in the New Item wizard
only if it has been enabled using the Business Modeler IDE.
o The second paragraph will be replaced by the following:

Alternatively, you can convert an existing item to a configuration by
changing the value of its Configuration Item? property from False to
True. You can edit the item properties by right-clicking the item and
choosing Edit Properties and clicking the All link.
o Replace the first sentence in the note with the following:

Perform the following steps to add the Configuration Item check
box to the New Item wizard.

Substance Compliance Solution Guide

The following release notes pertain to the Substance Compliance Solution Guide.
• Configuring Global Services on JBoss 7.1.1
The following information will be added to the Configure the Global Services
Framework topic:
1. Open the JBoss-installation/standalone/ /configuration/standalone.xml

file and add the following entries for CPM:
<subsystem xmlns="urn:jboss:domain:naming:1.1">
<bindings>

<lookup name="TCCPMReactor" lookup="java:global/TcGS EAR name
/cpmconnector/
TCCPMReactorBean!com.tccpmreactor.TCCPMReactorHome"/>
<lookup name="TCCPMSOABox" lookup="java:global/ TcGS EAR name
/cpmconnector/
TCCPMSOABoxBean!com.teamcenter.globalservices.connection.
ConnectionBoxHome"/>
<lookup name="CPMSOABox" lookup="java:global/ TcGS EAR name
/cpmconnector/
CPMSOABoxBean!com.teamcenter.globalservices.connection.
ConnectionBoxHome"/>
</bindings>
</subsystem>
2. Create the data source from the JBoss console instead of modifying the
standalone.xml file directly.
3. Use ojdbc6.jar as the database driver file name.
• Incorrect substance compliance status

The example in the Verifying if a part or BOM is environmentally compliant topic
incorrectly mentions that the substance compliance status of the lamp for RoHS
regulation is Unapproved PASS. The correct substance compliance status
received after a substance compliance check is Unapproved FAIL.
An Unapproved PASS substance compliance status is received when a part
has no materials defined or has unknown substances.

System Administration Guide

The following release notes pertain to the System Administration Guide.
Resource tier logging topic.
• Setting the Transient_Volume_RootDir preference

Add the following note to the end of the File Management System®Administering
FMS®Administering transient volumes® Determining the transient volume
ID for a different server context topic:
Note The Transient_Volume_RootDir preference allows the configuration
of transient volume locations for multiple platforms. Typically, one
value represents the location of a transient volume on a UNIX system
and the other a transient volume on a Windows system. Teamcenter
distinguishes the values based on the path name separator (/ for UNIX,
\ for Windows). If you use only one platform, you can delete the other
value. Multiple values can be specified but are not required.
If the values specified for the Transient_Volume_RootDir preference
have identical values, Teamcenter displays the following error message:
Duplicate transientvolume configuration elements were found for
attribute id with value attribute_value

Systems Engineering Guide

The following release notes pertain to the Systems Engineering Guide.
• Microsoft Office 2010 support for importing unstructured requirements
Changes will be made to the following topics under Developing requirements:
o Importing unstructured requirements from Microsoft Office 2003 or 2007

Mentions of specific Office versions will be removed from the topic title.
A mention of Office 2010 will be added to the first sentence of the text.
Below the first paragraph, the following note will be added:

Note For Word and Excel 2010, both the 32-bit and 64-bit versions
are supported.
o Prerequisites for installing the flat file add-ins

The following items will be added to the list of prerequisites:
For Office 2010:

◊ Microsoft Windows XP or later
◊ Microsoft Office 2010 Professional
◊ Microsoft Office 2010 Primary Interop Assemblies
◊ Microsoft .NET Framework 3.5 (Service Pack 1)
◊ Microsoft VSTO 2010 for Office 2010

For languages other than English, install the VSTO language pack
for that language.
◊ Microsoft Windows Installer 3.0 or later
o Install the flat file add-ins

In step 1:
Mentions of specific Office versions will be removed from the action

statement.

The following rows will be added to the existing table:
Office Office
version product Location of setup.exe file
2010 Word <TC_KIT_ROOT>\tc\flatfileimport\
(32-bit) office2007\Word\setup.exe
2010 Word <TC_KIT_ROOT>\tc\flatfileimport\
(64-bit) office2007\Word_x64\setup.exe
2010 Excel <TC_KIT_ROOT>\tc\flatfileimport\
(32-bit) office2007\Excel\setup.exe
2010 Excel <TC_KIT_ROOT>\tc\flatfileimport\
(64-bit) office2007\Excel_x64\setup.exe
o Customizing identifier tags for objects and trace links

Mentions of specific Office versions will be removed from the second
sentence.
The following rows will be added to the existing table:
Office Office Location and name of XML configuration

version product file
2010 Word %PROGRAMFILES%\TcWord2k7DocImp\
(Windows TcWord2K7DocImp.dll.config
32-bit)
Excel %PROGRAMFILES%
\TcExcel2k7WorkbookImp\
TcExcel2K7WorkbookImp.dll.config
2010 Word %PROGRAMFILES(x86)%\TcWord2k7DocImp\
(Windows (32-bit) TcWord2K7DocImp.dll.config
64-bit)
Excel %PROGRAMFILES(x86)%
(32-bit) \TcExcel2k7WorkbookImp\
2010 Word %PROGRAMFILES%\TcWord2k7DocImp\
(Windows (64-bit) TcWord2K7DocImp.dll.config
64-bit)
Excel %PROGRAMFILES%
(64-bit) \TcExcel2k7WorkbookImp\

o Configuring the common settings

The following changes will be made to the default value of the Parser
parameter:
For Word:
"Teamcenter.TcIDToIDParser.WordIDParser;
<Word_flatfile_install_folder>\TcIDToIDParser.dll"
For Excel:
"Teamcenter.TcIDToIDParser.ExcelIDParser;
<Excel_flatfile_install_folder>\TcIDToIDParser.dll”
• References to Microsoft Office Help on regular expressions

The following changes will be made to the Using regular expressions topic under
Developing requirements:
o Hyperlinks to specific topics in Microsoft Office Word Help will be replaced

by the following plain text:
For more information and examples of using regular expressions in Word,
see Microsoft Office Word Help.
o Hyperlinks to specific topics in Microsoft .NET Help will be replaced by the

following plain text:
For more information and examples of using regular expressions in Excel,
see Microsoft .NET Help.
• No integration between live Office and Client for Office add-ins

In Exporting Systems Engineering data®Exporting data to Microsoft Office
Word®Live integration with Word output mode, insert the following note at the
end of the topic:
Note There is no integration between live Office and Client for Office add-ins.
When you use Systems Engineering within the rich client, the live Office
add-in disables the Microsoft Office save option and displays its own save
button. When saving a requirement dataset in the embedded Microsoft
Word window, use the live Office save button, not the save button in
the Client for Office add-ins tab.
If you attempt to save a requirement dataset using the Client for Office
menu, Client for Office does not recognize the Teamcenter object context
and does not know where the dataset originates in Teamcenter.

Teamcenter Environment Manager Help

The following release notes pertain to the Teamcenter Environment Manager Help.
• Additional fields in the Volume Information panel
In Teamcenter Foundation®Creating a volume, insert the following description
next to the Serving FSC value:
These fields are displayed if your configuration does not include an FMS server
cache (FSC).

The Teamcenter Foundation®Teamcenter administrative user topic contains a
caution about characters not allowed in passwords. Replace the caution with
the following:
or vertical tab.
characters:
!@$%’": ;.<>(){}
o Teamcenter Foundation®Configure the database for Teamcenter Foundation
o Quick preconfigured installation®Teamcenter corporate server and two-tier

rich client
o Quick preconfigured installation®Teamcenter corporate server and

.NET-based server manager
o Quick preconfigured installation®Teamcenter corporate server and

J2EE-based server manager
o Repeatable Digital Validation®Configuring an RDV database
o Repeatable Digital Validation®Database engine selection for Repeatable

Digital Validation
o Upgrade®Upgrade information

Teamcenter Glossary
The following release notes pertain to the Teamcenter Glossary.
• Removal of Teamcenter File Services (TCFS) glossary entries

Teamcenter File Services (TCFS) was made obsolete in Teamcenter 8.1. All file
service functionality is now performed through File Management System (FMS).
Therefore, the following glossary entries will be removed:
TCFS
See Teamcenter File Services (TCFS).
Teamcenter File Services (TCFS)

File services that enable the Organization application to create volumes and
perform other administrative functions. TCFS also supports file access for
legacy versions of NX and Teamcenter lifecycle visualization.
Thin Client Interface Guide

The following release notes pertain to the Thin Client Interface Guide.
• Controlling the display of visualization toolbars in the thin client

The following information will be added to the Viewing 2D images and 3D
models topic:
You cannot turn off every visualization toolbar from the toolbar area of the thin
client viewer. At least one toolbar is always displayed.
Transition Guide
The following release notes pertain to the Transition Guide.

projects topic.

Note You can perform mapping of Teamcenter Enterprise to Teamcenter

in several different scenarios using most of the project examples in
the mapping_designer_projects.zip file. See the readme files for
details about what scenarios the examples provide.

Upgrade Guide
The following release notes pertain to the Upgrade Guide.
• Run cleanup_psdata utility after upgrade
The description of the cleanup_psdata utility is incorrect in the Upgrade
Guide. Also, this utility is run after upgrade, not before upgrade.
Replace the contents of the Remove duplicate variants topic with the content
that follows, and move this topic from its current path:
Upgrading a Teamcenter corporate server®Prepare the corporate server for
upgrade
To the following path:
Upgrading a Teamcenter corporate server®Complete the upgrade
Remove duplicate variants

If you use variants, you can determine whether you have duplicate variants
by running the cleanup_psdata utility. Duplicate variants occur when
two variant objects have the same name and are owned by the same item.
Duplicate variants can cause the importing or exporting of variants to
fail. To avoid this and any other potential problems that may arise due
to duplicate variants, Siemens PLM Software recommends cleaning up
duplicate variants.
The cleanup_psdata utility generates a report of duplicate variants to
assist in removing them. The utility reports duplicates based on data
conditions. You must have administrative privileges to run this utility.
To generate a duplicate variants report, open a Teamcenter command
prompt and type the following command:
cleanup_psdata [-u=user-name] [-p=password] [-g=group-name]
-duplicate_variants -report_file_path=path
Replace path with a valid local drive path for the report files.
This command generates a file named
duplicate_variants_report_timestamp.csv, which contains a report of all
duplicate variant objects with UIDs of variant options, variant revisions,
numbers of expressions referring to duplicate options, and other information.

• Run postupgrade utility

The following procedure will be added to the Upgrading Teamcenter Express or
Teamcenter Rapid Start to Teamcenter topic. This procedure must be performed
after completing the upgrade from Teamcenter Rapid Start 10.1 or Teamcenter
Express 9.1 to Teamcenter 10.1.
1. Download the PostUpgradeTcUtility.zip file from http://support.ugs.com.
2. Extract the .zip file on your local machine.
3. Copy the extracted contents (PostUpgradeTcUtility.bat and

PostUpgradeTcUtility.jar) to the Teamcenter 10.1 TC_ROOT folder.
4. Open a Teamcenter command prompt by choosing Start→All

Programs→Teamcenter 10. Browse to the TC_ROOT directory and select
the PostUpgradeTcUtility.bat file.
5. In the dialog box that opens, enter the path to the old TC_DATA directory
and the DBA user credentials. Click Next.
6. After the utility completes successfully, the PostUpgradeTcUtility Executed

Successfully... message box appears. Click OK to close the box.
Validation Manager Guide

The following release notes pertain to the Validation Manager Guide.
• Override notifications are sent through operating system mail
By default, validation override notifications are sent through operating
system mail. To send notifications through Teamcenter mail, set the
TC_VALIDATION_send_envelope_for_override preference to TRUE.

TC_VALIDATION_send_envelope_for_override
DESCRIPTION
Determines if validation override notifications are sent via operating system mail or
Teamcenter mail.
VALID
VALUES
TRUE Sends validation override notifications via Teamcenter mail.
FALSE Sends validation override notifications via operating system
mail.
DEFAULT
VALUES
FALSE
DEFAULT
PROTECTION
SCOPE
Site preference.
Volume Management Guide

The following release notes pertain to the Volume Management Guide.
Introduction to migrating data topic.

Utilities Reference
The following release notes pertain to the Utilities Reference. A complete description
of each new utility follows the notes.
• bmide_generate_datamodel_doc_report
The bmide_generate_datamodel_doc_report topic will be changed as follows:
o The -sourceReleaseVersions argument listed in the Syntax section will

be shown as follows:
[-sourceReleaseVersions=[Tcrelease | all]
o The -sourceReleaseVersions argument in the body of the topic will appear

as follows:
-sourceReleaseVersions
Specifies a comma-separated list of Teamcenter versions to generate a
comparison, for example, -sourceReleaseVersions=Tc820,Tc830. For
a complete list of the Teamcenter versions to use with the argument, use
the -h argument to see the help text for the utility.
To generate a report for all versions, specify
-sourceReleaseVersions=all.
• build_fts_index
The build_fts_index utility will be updated in the Query utilities topic of the
Utilities Reference.
For more information about the Autonomy full-text search engine and the
build_fts_index utility, see Application Administration Guide.
The content in the Teamcenter 10.1 Release Bulletin is updated and replaces
the comparable content in the Utilities Reference.
• cleanup_userinbox
The cleanup_userinbox utility will be added to the Workflow utilities topic of
• data_share
The following paragraphs will be added following the last paragraph of the
description for the data_share utility topic:
The behavior of the utility for project relationships on replica objects can be
controlled by the TC_sync_projects_with_owning_site preference. This
preference is not created by the Teamcenter installation process. To change the
default behavior of shared project relationships, you must create the preference.
• data_sync
The following paragraphs will be added following the last paragraph of the
description for the data_sync utility topic.

The behavior of the utility for project relationships on replica objects can be
controlled by the TC_sync_projects_with_owning_site preference. This
preference is not created by the Teamcenter installation process. To change the
default behavior of shared project relationships, you must create the preference.

build_fts_index
Builds keyword indexes for the Autonomy search engine on an object-by-object basis.
These indexes enable the Teamcenter full-text keyword search and can index both
the properties of Teamcenter dataset objects and the contents of dataset files.
• If a dataset file is not of a document type supported by Autonomy, the utility
invokes a user-specified filter program to convert the file to a supported format.
• You do not need to specify languages to index. The Autonomy software

automatically detects the language used in a file, and Teamcenter determines
the metadata language.
• A file attached to a dataset must contain enough words for the Autonomy
software to detect the language.
Note Before running this utility, add the TC_fts_indexed_types preference
to the database. This preference defines a list of the dataset types that
you want to index. For more information about managing options and
preferences, see the Rich Client Interface Guide.
For more information about all the preferences required to index the
Autonomy search engine, see the Application Administration Guide.
Autonomy supports a wide range of file types for word processing, spreadsheet,
and presentation graphics applications.
WORD
PROCESSING
The following word processing file types are supported:
• HTML
• SGML
• XML
• TEXT
• RTF
• WML
• Adobe PDF
• ASCII text
• ANSI text
• Unicode V2.x
• Microsoft RTF
• Microsoft Word for Windows V3.x and later

• Microsoft Word Mac V4.x to V6.x
• Microsoft Word PC V2.0 to V5.5
• Microsoft Word 2007 (MSWordX)
• Quark QXD
SPREADSHEET
The following spreadsheet file types are supported:
• Microsoft Works V3.x and later
• Microsoft Excel V3.x and later
• Microsoft Excel 2007 (MSExcelX)
PRESENTATION
GRAPHICS
FORMATS
The following presentation graphics file formats are supported:
• Shockwave Flash (with Autonomy Flashslave)
• Microsoft PowerPoint V4 and later
• Microsoft PowerPoint 2007 (MSPowerpointX)
SYNTAX
build_fts_index.exe [-u=user-id {-p=password | -pf=password-file}
-g=group] | -type=variable_name | -workdir=work_directory |
-autonomydir= autonomy_directory | -filenumber=number_of_objects |
-f=[index | delete | update | remove] | -query=query_name |
-entry=entry_name | -value=entry_value | -report | -lsd [-h]
ARGUMENTS
-u
Specifies the user ID.
This is generally infodba or another user with administration privileges. If this
argument is used without a value, the operating system user name is used.
Note If Security Services single sign-on (SSO) is enabled for your server, the -u
and -p arguments are authenticated externally through SSO rather than
being authenticated against the Teamcenter database. If you do not supply
these arguments, the utility attempts to join an existing SSO session. If no
session is found, you are prompted to enter a user ID and password.
-p
Specifies the password.
If used without a value, the system assumes a null value.
If this argument is not used, the system assumes the user-ID value to be the
password.
This argument is mutually exclusive with the -pf argument.

-pf
Specifies the password file. If used without a value, the system assumes a null
value. If this argument is not used, the system assumes the user-ID value to be
the password.
For more information about managing password files, see the Utilities Reference.
This argument is mutually exclusive with the -p argument.
-g
Specifies the group associated with the user.
If used without a value, the user’s default group is assumed.
-type
Specifies the dataset type to index. Specified dataset types must be defined by the
TC_fts_indexed_types preference.
If this argument is not specified, all dataset types defined by the
TC_fts_indexed_types preference are indexed.
This argument can be specified multiple times to index multiple dataset types in a
single utility session, for example:
-type=Text -type=HTML
Optionally, where the WSOM_find_list_separator preference value is set to the
semicolon (;), this syntax can be used:
-type=Text;HTML
Note If the TC_fts_indexed_types preference is used, the
WSOM_find_list_separator value must be set in the tc_env
file.
-workdir
Specifies the full path to the directory under which an autonomy subdirectory is
created to store all exported dataset files and any immediate files to be indexed
by Autonomy.
• This directory must have large scratch spaces to support indexing of a large
number of datasets in a single run.
• All exported files and any immediate files are removed from the directory after
the utility is run.
• The user must have the write privilege into the work directory.
If this argument is not specified, the default is the current directory.
-autonomydir
Specifies the full path to the directory on the Autonomy server under which an
subdirectory is created to store all exported dataset files and any immediate files to
be indexed by Autonomy.

Note If the Teamcenter server and Autonomy server are on different

hosts, you must set UNC paths. Otherwise, the system uses
TC_fts_shared_tmp_dir_wnt, TC_fts_shared_tmp_dir_unix, and
TC_fts_shared_tmp_dir_autonomy_path values.
-filenumber
Specifies the number of objects that can be indexed in one Autonomy call. If this
argument is not specified, the default file number is 600. The maximum value is
1200 and the minimum is 1.
-f
Specifies one of the following options:
• index
Indexes objects for all languages.
• delete
Deletes invalid index entries from the Autonomy database.
This option does not support the -query argument.
• update
Deletes invalid index entries, if applicable, and regenerates new entries if
datasets are not yet indexed. This option supports the cases in which datasets
have either been modified or created after the last index or were not indexed.
Siemens PLM Software recommends using the -update option after the entire
database has been indexed using the -index option.
• remove
Removes index entries for specific types. For example, if the Text type is indexed,
but is no longer a supported index type, you can use -f=remove -type=Text to
remove all the index entries for the Text type.
If this argument is not specified, the default operation is f=index.

-query
Defines the name of the Teamcenter saved query that can be run to find all dataset
objects that need to be indexed.
This argument is useful when you select a few individual datasets to be indexed with
special options, such as a different language type.
• Datasets returned by the query are indexed only if their dataset types are
defined by the TC_fts_indexed_types preference.
• Invalid dataset types are ignored.
• Items must use the -query argument to be indexed, and the type must be
defined by the TC_fts_indexed_types preference.
Note When used with the -f argument, -query works only with the -f=index
and -f=update options.

-entry
Specifies the user entry name for the saved query for which the search value is
being defined.
-value
Specifies the value corresponding to the entry name.
Note The -entry and -value arguments must be supplied in pairs.
-report
Prints all objects that failed to process.
-lsd
Index or update from the last save date.
-h
Displays help for this utility.
EXAMPLES
• The following example indexes all dataset types defined by the
TC_fts_indexed_types preference:
$TC_BIN/build_fts_index
-u-=user-name -p=password -g=group-name\
Note If a query is not included, each use of the build_fts_index utility

indexes all datasets.
• The following example indexes Text type datasets. Only the dataset files with
txt extensions are indexed.
-u=user-name -p=password -g=group-name\
-type=Text
• The following indexes dataset files with the txt extension returned by the
specified query:
–query=query-name
–entry=”Owning User”
–value=user-name
–entry=”Modified After
-value=\
Note Teamcenter can automatically update the index whenever an indexed

object is created, modified, or deleted:
1. In the rich client, choose Edit®Options.
2. Set the TC_fts_real_time_indexing search preference to true.
• The following creates index entries in the Autonomy database for dataset objects
modified after the specified date (in this case, 11-Aug-2011):
–query=”Dataset...”

–entry=”Modified After”
–value=”11-Aug-2011”
Note The query value must exactly match a name value as shown in Query
Builder.
For information about using Query Builder, see the Query Builder Guide.
• The following example deletes invalid index entries from the Autonomy database
for dataset types defined by the TC_fts_indexed_types preference:
-f=delete
• The following example deletes invalid index entries from the Autonomy database
for Text type datasets:
-f=delete
-type=Text
• The following example deletes all index entries from the Autonomy database
for Text type datasets:
-f=remove
-type=Text
• The following example indexes Text type datasets modified after the last time
the utility was executed:
-lsd
-type=Text
• The following example updates indexes for Text type datasets modified after
the last time the utility was executed:
-f=update
-type=Text
Note The lsd argument is valid only with the index and update options.

cleanup_userinbox
Consolidates two or more My Worklist inboxes of a user into a single inbox, preserving
the resource pool subscriptions and surrogate lists of each. If two inboxes have the
same surrogate, it is indeterminate which effective start and end dates are kept.
SYNTAX
cleanup_userinbox [-u=user-id {-p=password | -pf=password-file} -g=group-name]
[-report=file-name] [-dryrun] [-v] [-h]
ARGUMENTS
-u
Specifies the user ID.
This is generally infodba or another user with administration privileges. If this
argument is used without a value, the operating system user name is used.
Note If Security Services single sign-on (SSO) is enabled for your server, the -u
and -p arguments are authenticated externally through SSO rather than
being authenticated against the Teamcenter database. If you do not supply
these arguments, the utility attempts to join an existing SSO session. If no
session is found, you are prompted to enter a user ID and password.
-p
Specifies the user’s password.
If used without a value, the system assumes a null value. If this argument is not
used, the system assumes the user-ID value to be the password.
This argument is mutually exclusive with the -pf argument.
-pf
Specifies the password file. If used without a value, the system assumes a null
value. If this argument is not used, the system assumes the user-ID value to be
the password.
For more information about managing password files, see Manage password files.
This argument is mutually exclusive with the -p argument.
-g
Specifies the group associated with the user.
If used without a value, the user’s default group is assumed.
-report
Specifies the output file for the report. If this argument is not specified, it is written
to the standard output.
-dryrun
Generates a report of the changes to be made but does not update the database.
Actions that would be performed are displayed.
-v
Verbose mode. Provides information about the My Worklist inboxes processed. This
argument is recommended.

-h
Displays help for this utility.
ENVIRONMENT
As specified in Manually configuring your environment for Teamcenter utilities.
FILES
As specified in Log files produced by Teamcenter.
RESTRICTIONS
None.
EXAMPLES
• To generate a report about which changes would be made without actually
updating the database:
cleanup_userinbox -v -dryrun
• To consolidate the tcadmin user’s inboxes and display the report in the standard
output:
cleanup_userinbox -u=tcadmin -p=tcadmin
• To consolidate the tcadmin user’s inboxes and display the report in the rpt_file
file:
cleanup_userinbox -u=tcadmin -pf=pswd_file -report=rpt_file
Web Application Deployment Guide

The following release notes pertain to the Web Application Deployment Guide.
In Teamcenter Web application deployment®Basic deployment® Deploy on
WebSphere application server, insert the following note:
Note If you deploy a Web application that contains the Teamcenter - Online
Help solution, set the context root for the Web application in WebSphere
to the enterprise tier ID for the Web application. This is the value of
the Deployable File Name context parameter or the Enterprise
Application Lookup ID context parameter. Make sure you include the
file name (file-name.war) when specifying the context root.
What’s New
The following release notes pertain to the What’s New.
• Correction to argument names for EPM-validate-target-objects handler
In the Managing changes and workflow® Workflow handler, argument, argument
values, and keyword name changes topic, replace the row that describes the
EPM-validate-target-objects handler with the following:
New argument
Handler name beginning in Argument name prior to name beginning in
Teamcenter 10.1 Teamcenter 10.1 Teamcenter 10.1
EPM-validate-target-objects -allowed_type -include_type

-disallowed_type -exclude_type

• Changed default display value of Boolean properties

The following will be added to the Changed default display value of Boolean
properties topic:
For more information about customizing server code, see the Server
Customization Programmer’s Guide. For more information about customizing
Java code, see the Client Customization Programmer’s Guide.
• Validation Manager does not support multifield keys

In Administering Teamcenter® Validation Manager enhancements, remove the
following sentence:
Validation Manager also supports multifield keys.

Index
Numerics/Symbols PLM XML . . . . . . . . . . . . . . . . . . . . 4-30

2D Markup toolbar . . . . . . . . . . . . . . . 4-60 Release notes . . . . . . . . . . . . . . . . . . 4-30
3D PDF report . . . . . . . . . . . . . . . . . 3-112 Stock material management . . . . . . 3-145
3D PDF reports Thin client . . . . . . . . . . . . . . . . . . . . 4-30
GD&T symbols not displaying Thin client support . . . . . . . . . . . . . 3-148
correctly . . . . . . . . . . . . . . . . . . . 4-75 Unincorporated changes . . . . . . . . . 3-145
Naming problem . . . . . . . . . . . 4-71, 4-77 Work packages . . . . . . . . . . . . . . . . 3-146
4D planning . . . . . . . . . . . . . . . . . . . 3-112 AIX
4GD Release notes . . . . . . . . . . . . . . . . . 4-183
Support in manufacturing . . 3-102, 3-116 Allocation IC Information panel . . . . . . 4-81
4th Generation Design . . . . . . . . . . . . 3-34, Ampersand characters . . . . . . . . . . . . 4-170
3-92, 3-97, 3-100, 4-28–4-29 appbar_title_contents preference . . . . . 3-51
Assign Collaborative ID button . . . . . 4-28 Appearance update manager . . . . . . . 4-187
Cacheless searches . . . . . . . . . . . . . . 3-96 Apple Macintosh MacOS
Effectivity . . . . . . . . . . . . . . . . . . . . 3-94 Release notes . . . . . . . . . . . . . . . . . 4-190
Partition Membership icon . . . . . . . . 4-29 Applet error, Microsoft Word or
Partitions . . . . . . . . . . . . . . . . . . . . 3-95 Excel . . . . . . . . . . . . . . . . . . . . . . . 4-168
Product Configurator . . . . . . . . . . . . 3-98 Application Administration Guide . . . 4-193
Relation Browser . . . . . . . . . . . . . . . 4-29 Application bar . . . . . . . . . . . . . . . . . . 3-51
Release notes . . . . . . . . . . . . . . . . . . 4-28 arrayLength attribute cannot be
Revising design elements . . . . . . . . . 4-28 changed . . . . . . . . . . . . . . . . . . . . . . 4-19
Saved query for partition templates . . 4-28 askLOVLength() ITK deprecation . . . . . . 2-8
Transition to . . . . . . . . . . . . . . . . . . 3-98 Assembly item . . . . . . . . . . . . . . . . . 4-159
Variants . . . . . . . . . . . . . . . . . . . . . 3-95 Attachments view . . . . . . . . . . . . . . . . 4-74
Attribute Exchange, issues after
mapping . . . . . . . . . . . . . . . . . . . . . . 4-42
A
attributeType attribute cannot be
Access control over preferences and changed . . . . . . . . . . . . . . . . . . . . . . 4-19
options . . . . . . . . . . . . . . . . . . . . . . . 3-28 Audit Manager . . . . . . . . . . . . . 3-32, 4-203
Access Manager . . . . . . . . . . . . . . . . . . 4-6 Audit log export . . . . . . . . . . . . . . . . 4-31
Sequences rule . . . . . . . . . . . . . . . . . 4-24 Deprecation of audit files . . . . . . . . . . 2-4
Access Manager rule conditions . . . . . . 3-34 Deprecation of legacy CICO (checkin or
ACLs missing in Teamcenter Rapid checkout) files . . . . . . . . . . . . . . . . 2-4
Start . . . . . . . . . . . . . . . . . . . . . . . . 4-10 IBM DB2 . . . . . . . . . . . . . . . . . . . . . 4-31
Activities view, Manufacturing viewer Legacy workflow obsolete . . . . . . . . . 2-16
license . . . . . . . . . . . . . . . . . . . . . . . 4-72 Audit Manager application deprecated . . 2-2
Administration release notes . . . . . . . 4-146 Audit Manager release notes . . . . . . . . 4-30
Adobe Acrobat files . . . . . . . . . . . . . . 4-160 Auditing workflow processes . . . . . . . . 3-71
Adobe Reader . . . . . . . . . . . . . . . . . . 4-163 Authorized data access license
Adobe Reader X . . . . . . . . . . . . . . . . . 4-46 categories . . . . . . . . . . . . . . . . . . . . . 3-35
Aerospace and Defense Auto update product views . . . . . . . . . . 4-59
Configuration audits . . . . . . . . . . . 3-147 Auto VI processing changes . . . . . . . . 4-103
Finish management . . . . . . . . . . . . 3-147 Automatic assembly graphics
Location code management . . . . . . . 3-145 positioning . . . . . . . . . . . . . . . . . . . 3-118
Multifield support . . . . . . . . . . . . . 3-145
PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin Index-1

Index
Automatic refresh disabled . . . . . . . . . 4-71 Cascading LOVs not supported in live Excel
Automotive Edition and live Word . . . . . . . . . . . . . . . . . 4-139
Release notes . . . . . . . . . . . . . . . . . . 4-30 CATDrawing name . . . . . . . . . . . . . . . 4-53
CATIA
B Site checkout . . . . . . . . . . . . . . . . . . 4-53
CCABase items . . . . . . . . . . . . . . . . . 4-141
Background processing of workflows . . . 3-69 CFMOccEffMode preference . . . . . . . . . 4-71
Base Name not supported . . . . . . . . . 4-100 CGM files . . . . . . . . . . . . . . . . . . . . . . 4-57
Baseline error messages . . . . . . . . . . 4-104 Change Manager
bl_attachments property . . . . . . . . . . 4-224 Save As action . . . . . . . . . . . . . . . . . 4-33
bmide_postupgradetotc utility . . . . . . . . 2-7 Change Manager release notes . . . . . . . 4-32
BMP files, in PDF reports . . . . . . . . . . 4-76 Change Viewer . . . . . . . . . . . . . . . . . . 3-70
BOM Change Viewer obsoletion . . . . . . . . . . 2-15
Line columns . . . . . . . . . . . . . . . . . . 4-79 Check out, transfer to other user, Client for
Markup . . . . . . . . . . . . . . . . . . . . . 4-122 Office . . . . . . . . . . . . . . . . . . . . . . . . 3-42
Restructuring . . . . . . . . . . . . . . . . . 4-80 Checkout
BOM Change . . . . . . . . . . . . . . . . . . . 4-32 Failure . . . . . . . . . . . . . . . . . . . . . . 4-84
BOM line, remove does not work . . . . 4-102 Claim tasks . . . . . . . . . . . . . . . . . . . . 3-70
Briefcase Browser . . . . . . . . . . . . . . . . 3-87 Classification . . . . . . . . . . . . . . . . . . . 4-35
Briefcase Browser, non-English help . . . 4-31 Classified instance . . . . . . . . . . . . . . 4-38
Browser issues . . . . . . . . . . . . . . . . . . . 4-4 Datasets . . . . . . . . . . . . . . . . . . . . . 4-35
Browser title bar . . . . . . . . . . . . . . . . . 3-51 ICS XML export . . . . . . . . . . . . . . . . 4-36
Budget templates . . . . . . . . . . . . . . . 4-133 Import and export failure . . . . . . . . . 4-38
build_fts_index utility . . . . . . . 4-198, 4-260 PLM XML . . . . . . . . . . . . . . . . . . . . 4-37
build_fts_index, upgrade issue . . . . . . . 4-18 Root node names . . . . . . . . . . . . . . . 4-24
Bulk object creation . . . . . . . . . 3-143–3-144 Search . . . . . . . . . . . . . . . . . . . . . . 4-78
Bulk update of object properties . . 3-33, 3-35 Translation privilege . . . . . . . . . . . . 4-38
Bullets and numbering, Microsoft Classification Administration
Word . . . . . . . . . . . . . . . . . . . . . . . 4-120 Key ID . . . . . . . . . . . . . . . . . . . . . . 4-36
Business Modeler IDE . . . . . . . . . . . . 4-155 Upgrade . . . . . . . . . . . . . . . . . . . . . 4-24
Mapping Designer . . . . . . . . . . . . . . 3-12 Classification data, loading issues . . . . . 4-35
Multifield keys . . . . . . . . 3-25–3-26, 3-107 Classification query . . . . . . . . . . . . . . . 3-44
Published flag . . . . . . . . . . . . . . . . 4-158 cleanup_userinbox utility . . . . . . . . . . 4-266
Release notes . . . . . . . . . . . . . . . . . 4-155 Clear Repositioning check box . . . . . . 4-106
Save as . . . . . . . . . . . . . . . . . . . . . . 3-11 ClearanceExe . . . . . . . . . . . . . . . . . . . 4-92
Business object constants Client credential too weak error, SUSE
Fnd04GDObjectSelectionCriteria . . 4-205 Linux . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Fnd0OBJIOSuppportedType . . . . . . 4-205 Client for Office . . . . . . . . . . . . . 4-39, 4-42
Buttons not responsive, duplicate mappings Access to all core Microsoft Office file
message . . . . . . . . . . . . . . . . . . . . . . 4-41 types . . . . . . . . . . . . . . . . . . . . . 3-42
Custom datasets . . . . . . . . . . 4-40, 4-130
C Enhancements . . . . . . . . . . . . . . . . . 3-41
Microsoft Office 2010 support . . . . . . 3-41
Cacheless search Refresh . . . . . . . . . . . . . . . . . . . . . 4-129
Product-scoped . . . . . . . . . . . . . . . 3-132 Script error message . . . . . . . . . . . . 4-39
Cacheless searches . . . . . . . . . . . . . . . 3-96 Transfer object reservations, Client for
cacheless_search_utility . . . . . . . . . . . 3-132 Office . . . . . . . . . . . . . . . . . . . . . 3-42
CAE Manager Word setting for correct document
CAE structure creation and comparison display . . . . . . . . . . . . . . . . . . . . 4-43
enhancements . . . . . . . . . . . . . . 3-138 Client for Office release notes . . . . . . . . 4-39
Structure attribute Client for Office, problem with properties text
enhancements . . . . . . . . . . . . . . 3-137 box . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
cae_geometry_fix utility . . . . . . . . . . . . 4-21 Clipboard button . . . . . . . . . . . . . . . . 4-165
Calendars in Schedule Manager . . . 4-4, 4-99 Clone
Index-2 Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

Index
Stable identifiers . . . . . . . . . . . . . . . 4-65 Customization

Code page 932 . . . . . . . . . . . . . . . . . . 4-178 Release notes . . . . . . . . . . . . . . . . . 4-154
Cold Backup and Restore . . . . . . . . . . . . 2-5 Customization release notes . . . . . . . . 4-154
collect_garbage utility . . . . . . . . . . . . 4-152 Customize the perform signoff user
combine_audit_files utility . . . . . . . . . . . 2-7 interface . . . . . . . . . . . . . . . . . . . . . . 3-70
Command suppression
Dynamic contributions . . . . . . . . . . 4-145 D
Command Suppression
Release notes . . . . . . . . . . . . . . . . . 4-145 Data Exchange
User interface supports hiding only Dataset, transferring . . . . . . . . . . . . 4-45
commands added to the menu Monitoring interface . . . . . . . . . . . . . 4-45
bar . . . . . . . . . . . . . . . . . . . . . . 4-145 Ownership not updated in ODS . . . . . 4-45
Command Suppression application user Release notes . . . . . . . . . . . . . . . . . . 4-45
interface supports hiding only commands Data model deprecation . . . . . . . . . . . . . 2-9
added to the menu bar . . . . . . . . . . . 4-145 Data model obsoletion . . . . . . . . . . . . . 2-24
Commands, main toolbar . . . . . . . . . . 4-162 Data sharing
Compare content . . . . . . . . . . . . . . . . 4-119 4GD . . . . . . . . . . 3-89–3-90, 3-100–3-101
Compare with prior . . . . . . . . . . . . . . 4-119 Briefcase files . . . . . . . . . . . . . . . . . 3-87
Comparing requirement content in Teamcenter Enterprise . . . . . . . . . . . 3-91
Word . . . . . . . . . . . . . . . . . . . . . . . . 3-83 Data synchronization . . . . . . . . . . . . 4-148
Complying Object pane, arranging in Systems data_share utility . . . . . . . . . . . . . . . 4-178
Engineering Traceability view . . . . . . 3-82 Database query . . . . . . . . . . . . . . . . . . 4-96
Compound property values, export/ Datasets
import . . . . . . . . . . . . . . . . . . . . . . 4-174 Transferring . . . . . . . . . . . . . . . . . . 4-45
Condition task . . . . . . . . . . . . . . . . . . 3-61 Date button . . . . . . . . . . . . . . . 4-84, 4-162
Conditions on PSOccurrences . . . . . . . 3-106 Date Control dialog box . . . . . . . . . . . . 3-49
Configuration DB2
Preferences . . . . . . . . . . . . . . . . . . . 3-30 Release notes . . . . . . . . . . . . . 4-15, 4-180
Configuration preferences Servers . . . . . . . . . . . . . . . . . . . . . . 4-15
TC_VALIDATION_send_envelope_for_ Deep copy rules . . . . . . . . . . . . . . . . . . 3-12
override . . . . . . . . . . . . . . . . . . 4-257 Default configuration rule invalid
Configuration release notes . . . . . . . . 4-145 error . . . . . . . . . . . . . . . . . . . . . . . . 4-170
Configurations - Attribute Exchange dialog Default values after upgrade . . . . . . . 4-225
box . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41 define_auditdefs utility . . . . . . . . . . . . . 2-7
Constraints view . . . . . . . . . . . . . . . . . 4-76 Defining Object pane, arranging in Systems
Content controls Engineering Traceability view . . . . . . 3-82
Bullets and numbering, Microsoft Deleting e-mail in Outlook . . . . . . . . . . 4-46
Word . . . . . . . . . . . . . . . . . . . . 4-120 Deprecated
Content Management . . . . . . . . . . . . . 3-77 ERP Connect Toolkit handlers . . . . . . . 2-6
Data model deprecation . . . . . . . . . . 2-11 ERP Connect Toolkit preferences . . . . . 2-6
Old saved queries . . . . . . . . . . . . . . . 4-44 Preferences . . . . . . . . . . . . . . . . . . . 2-13
Pre-upgrade steps . . . . . . . . . . . . . . 4-25 Deprecation
SCORM package issues . . . . . . . . . . 4-44 Announcements . . . . . . . . . . . . . . . . . 2-1
Topic types . . . . . . . . . . . . . . . . . . . 4-44 askLOVLength() ITK . . . . . . . . . . . . . 2-8
Upgrade . . . . . . . . . . . . . . . . . . . . . 4-25 Cold Backup and Restore . . . . . . . . . . 2-5
Upgrade issues . . . . . . . . . . . . 4-25–4-27 Data model . . . . . . . . . . . . . . . . . . . . 2-9
XMetal validation error . . . . . . . . . . 4-45 ERP Connect Toolkit . . . . . . . . . . . . . 2-6
Content Management saved queries, Functions . . . . . . . . . . . . . . . . . . . . . 2-8
upgrade . . . . . . . . . . . . . . . . . . . . . . 4-25 Global Services BPEL engine
cookie-http-only flag . . . . . . . . . . . . . 4-150 endpoint . . . . . . . . . . . . . . . . . . . 2-22
Copy Reference action . . . . . . . . . . . . 4-132 Hot Backup and Recovery . . . . . . . . . . 2-5
Correlation IDs . . . . . . . . . . . . . . . . . . 4-82 Java classes . . . . . . . . . . . . . . . . . . . . 2-9
Create actions, post hook . . . . . . . . . . 4-162 Rich client on IBM AIX . . . . . . . . . . . 2-17
Custom notes, attaching to trace links . . 3-83 tc.h header file . . . . . . . . . . . . . . . . . . 2-5

Index
Teamcenter on HP-UX Itanium . . . . . . 2-6 EPM-set-property handler . . . . . . . . . 4-144

Teamcenter Services . . . . . . . . . . . . . 2-9 ERP Connect Toolkit . . . . . . . . . . . . . . . 2-6
Utilities . . . . . . . . . . . . . . . . . . . . . . 2-7 Error after deleting project . . . . . . . . 4-146
Derived characteristic value . . . . . . . . . 4-68 Errors, marshalling . . . . . . . . . . . . . . 4-138
Design requirements, NX parts . . . . . . 3-84 Ethernet MAC addresses, Sun
Diagram enhancements for functional and Solaris . . . . . . . . . . . . . . . . . . . . . . 4-186
logical models . . . . . . . . . . . . . . . . . . 3-81 Excel
Dimensional Planning and Validation Column names . . . . . . . . . . . . . . . . 4-125
Defining inspection process . . . . . . . 3-140 Direct server connectivity . . . . . . . . 4-128
Directories Edit mode . . . . . . . . . . . . . . . . . . . 4-128
POM_TRANSMIT_DIR . . . . . . . . . 4-223 Import . . . . . . . . . . . . . . . . . . . . . 4-120
Disk space requirements . . . . . . . . . . . . 1-6 Live . . . . . . . . . . . . . . . . . . . . . . . 4-121
Display names . . . . . . . . . . . . . . . . . 4-177 Excel export . . . . . . . . . . . . . . . . . . . 4-132
DISPLAY_Param_In_NotesText Excel Import, LOVs . . . . . . . . . . . . . . 4-131
preference . . . . . . . . . . . . . . . . . . . . 4-234 Excel Live . . . . . . . . . . . . . . . . . . . . 4-120
DisplayName constant . . . . . . . . . . . . 4-126 Export and import audit logs . . . . . . . 4-203
DITA objects, changes . . . . . . . . . . . . . 4-26 Export to Live Excel . . . . . . . . . . . . . . . 4-3
Division character . . . . . . . . . . . . . . . 4-166 Export To Word dialog box . . . . . . . . . 4-114
Document Management Exporting markups . . . . . . . . . . . . . . 4-130
Release notes . . . . . . . . . . . . . . . . . . 4-46 Exporting object data
Document management E-mail . . . . . . . . . . . . . . . . . . . . . . 3-84
enhancements . . . . . . . . . . . . . . 3-74–3-76 Word, copying snapshot of output to
Documentation notes dataset . . . . . . . . . . . . . . . . . . . . 3-84
Getting Started with Extensions for Office
Manufacturing . . . . . . . . . . . . . 4-211 Administrative privileges required . . 4-48,
Getting Started with Workflow . . . . 4-213 4-120
Domain assignment for child Patch upgrade for add-in files . . . . . . 4-47
diagrams . . . . . . . . . . . . . . . . . . . . . 3-79 Release notes . . . . . . . . . . . . . . . . . . 4-47
Download hyperlink not available . . . . . 4-89 External references, import
Duplicate error messages . . . . . . . . . . 4-104 specifications . . . . . . . . . . . . . . . . . . 4-113
Duplicate feature . . . . . . . . . . . . . . . 4-109
Duplicate mappings message . . . . . . . . 4-41 F
Dynamic lists of values (LOVs) . . . . . . . 3-13
Dynamic participants . . . . . . . . . . . . 4-144 Favorites list . . . . . . . . . . . . . . . . . . 4-171
FCC size . . . . . . . . . . . . . . . . . . . . . . 4-66
E FCC_PROXYPIPENAME environment
variable . . . . . . . . . . . . . . . . . . . . . 4-227
E-mail, exported object data . . . . . . . . . 3-84 Features, manufacturing . . . . . . . . . . 3-119
EDA File Locator . . . . . . . . . . . . . . . . . . . . 4-56
64-bit issues . . . . . . . . . . . . . . . . . 4-141 Files
Java issues . . . . . . . . . . . . . . . . . . 4-141 POM Transmit Schema . . . . . . . . . 4-223
Edit properties . . . . . . . . . . . . . . . . . 4-174 Filtering workflow processes . . . . . . . . 3-71
Effectivity . . . . . . . . . . . . . . . . . . . . . 3-94 Firefox, see Mozilla Firefox
Embeds column . . . . . . . . . . . . . . . . . 4-79 Flat file . . . . . . . . . . . . . . . . . . . . . . 4-127
Enterprise BOP . . . . . . . . . . . . . . . . 3-119 Flat file add-ins . . . . . . . . . . . . . . . . . 4-117
Environment variables Fnd04GDObjectSelectionCriteria business
FCC_PROXYPIPENAME . . . . . . . . 4-227 object constant . . . . . . . . . . . . . . . . 4-205
TC_TMP_DIR . . . . . . . . . . . . . . . . 4-228 Fnd0AllowSameParamReqMutipleTime
TC_USER_LIB . . . . . . . . . . . . . . . 4-228 global constant . . . . . . . . . . . . . . . . 4-206
TC_USER_MSG_DIR . . . . . . . . . . . . 4-19 Fnd0Icon business object constant . . . 4-118
TCCS_CONFIG . . . . . . . . . . . . . . . 4-227 Fnd0OBJIOSuppportedType business object
TCCS_CONFIG_HOME . . . . . . . . . 4-227 constant . . . . . . . . . . . . . . . . . . . . . 4-205
TCEDA_JAVA_HOME . . . . . . . . . . 4-141 Folder length problem . . . . . . . . . . . . 4-141
TCEDA_JRE_HOME . . . . . . . . . . . 4-141 Full-text search

Index
Configuring . . . . . . . . . . . . . . . . . . 4-194 GMS_tcxml_string_separator

File types . . . . . . . . . . . . . . . . . . . 4-198 preference . . . . . . . . . . . . . . . . . . . . . 4-23
Installing . . . . . . . . . . . . . . . . . . . 4-193 GRM_create postactions . . . . . . . . . . 4-155
Functional models, diagram Guided component search connection
enhancements . . . . . . . . . . . . . . . . . . 3-81 points . . . . . . . . . . . . . . . . . . . . . . . . 4-97
Functions, deprecated . . . . . . . . . . 2-8, 2-19
H
G
Handlers . . . . . . . . . . . . . . . . . . . . . . . 2-6
Hardware requirements . . . . . . . . . . . . . 1-6
Gantt views . . . . . . . . . . . . . . . . . . . . 4-73
Help . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Garbage collection . . . . . . . . . . . . . . . 4-152
Hidden dialog boxes . . . . . . . . . . . . . 4-188
GD&T symbols . . . . . . . . . . . . . . . . . . 4-77
Hierarchical numbering, Relation
GDE
Browser . . . . . . . . . . . . . . . . . .. . . . 3-83
Element . . . . . . . . . . . . . . . . . . . . . 4-80
Hot Backup and Recovery . . . . . . . . . . . 2-5
Structure . . . . . . . . . . . . . . . . . . . . 4-81
HP-UX . . . . . . . . . . . . . . . . . . . .
. . . 4-180
General Relationship Management (GRM)
ODS . . . . . . . . . . . . . . . . . . . .
. . . 4-180
relations, Visio diagrams . . . . . . . . . . 3-79
Release notes . . . . . . . . . . . . . . . . . 4-180
generate_loadfsccache_tickets utility . . 2-31
Getting Started with Document
Management . . . . . . . . . . . . . . . . . . 4-210 I
Getting Started with Document Management,
enhancements . . . . . . . . . . . . . . 3-74–3-76 Icons . . . . . . . . . . . . . . . . . . . . . . . . 4-118
Getting Started with ICS XML export . . . . . . . . . . . . . . . . . 4-36
Manufacturing . . . . . . . . . . . . . . . . 4-211 ICS_instance_image_revision_rule
Getting Started with Teamcenter . . . . 4-213 preference . . . . . . . . . . . . . . . . . . . . . 4-35
Enhancements . . . . . . . . . . . . . . . . . 3-43 IDs . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Getting Started with Teamcenter, iman_relation text incorrect . . . . . . . . 4-177
enhancements . . . . . . . . . . . . . . . . . . 3-43 Impact Analysis view . . . . . . . . . . . . 4-161
Getting Started with Workflow . . . . . . 4-213 Implemented By relationship . . . . . . . . 4-80
Global constants Import failure
Fnd0AllowSameParamReqMutipleTime . . 4-206 Classification . . . . . . . . . . . . . . . . . . 4-38
Global Services Import specifications, external
Autopopulated nonmandatory references . . . . . . . . . . . . . . . . . . . . 4-113
fields . . . . . . . . . . . . . . . . . . . . . 4-54 import_dfa_file utility . . . . . . . . . . . . . 2-31
BPEL engine endpoint . . . . . . . . . . . 2-22 Importing
Deadlocks . . . . . . . . . . . . . . . . . . . . 4-53 Keywords . . . . . . . . . . . . . . . . . . . 4-127
ODE EAR file . . . . . . . . . . . . . 4-50–4-51 In-context overrides . . . . . . . . . . . . . 4-106
Ownership not updated in ODS . . . . . 4-45 Incorrect display name . . . . . . . . . . . 4-177
Release notes . . . . . . . . . . . . . . . . . . 4-49 Incremental change . . . . . . . . . . 3-88, 3-118
Sample BOD does not display revision Occurrence group . . . . . . . . . . . . . . . 4-78
number . . . . . . . . . . . . . . . . . . . 4-53 Revision . . . . . . . . . . . . . . . . . . . . 4-110
Xalan JAR files . . . . . . . . . . . . . . . . 4-49 Visualization Illustration Batch . . . 4-142
Global Technical Access Center Incremental change icon . . . . . . . . . . 4-102
(GTAC) . . . . . . . . . . . . . . . . . . . . . 1-3–1-4 Inspection process improvements . . . . 3-140
GM Overlay install_event_typesutility . . . . . . . . . . . 2-7
Character set . . . . . . . . . . . . . . . . . 4-188 Installation
Release notes . . . . . . . . . . . . . . . . . . 4-54 DB2 . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Template . . . . . . . . . . . . . . . . . . . . 4-179 FMS client cache (FCC) . . . . . . . . . . 4-16
UNIX . . . . . . . . . . . . . . . . . . . . . . 4-188 In general . . . . . . . . . . . . . . . . . . . . . 1-1
GM Overlay, UGMASTER autocreate Japanese SJIS . . . . . . . . . . . . . . . . . 4-12
failure . . . . . . . . . . . . . . . . . . . . . . . 4-54 TCCS . . . . . . . . . . . . . . . . . . . 4-12, 4-16
GMS_expired_or_locked_ada_licenses_bypass Teamcenter 10.1 . . . . . . . . . . . . 1-1, 4-12
preference . . . . . . . . . . . . . . . . . . . . . 4-90 Windows 8 . . . . . . . . . . . . . . . . . . . . 4-12

Index
Windows Server 2012 . . . . . . . . . . . . 4-12 IOR references . . . . . . . . . . . . . . . . . 4-61

WinZip not supported . . . . . . . . . . . . 4-13 Legacy product views . . . . . . . . . . . . 4-66
Installation issues in thin client . . . . . . . 4-4 Motion . . . . . . . . . . . . . . . . . . . . . . 4-64
Internationalization Opening duplicate document . . . . . . . 4-59
Languages . . . . . . . . . . . . . . . . . . . . . 1-5 Over-the-Web Installer . . . . . . . . . . . 4-16
Release notes . . . . . . . . . . . . . . . . . 4-172 Part reconciliation . . . . . . . . . . . . . . 4-65
Internet Explorer, thin client issue . . . . 4-79 Postscript printer installation . . . . . 4-201
IORs, Lifecycle Visualization . . . . . . . . 4-61 Release notes . . . . . . . . . . . . . . . . . . 4-55
IPA structure . . . . . . . . . . . . . . . . . . . 4-74 Supported configurations . . . . . . . . . 4-16
IS NULL operator . . . . . . . . . . . . . . . . 4-95 Unable to launch . . . . . . . . . . . . . . . 4-67
isArray attribute cannot be changed . . . 4-19 Lifecycle Visualization with Security
iSeries . . . . . . . . . . . . . . . . . . . . . . . . 4-67 Services . . . . . . . . . . . . . . . . . . . . . . 4-62
Issue Manager Line balancing variant
improvements . . . . . . . . . . . . . . . . . 3-61 support . . . . . . . . . . . . . . . . . 3-113–3-114
isTransient attribute cannot be Linux
changed . . . . . . . . . . . . . . . . . . . . . . 4-19 Appearance update manager . . . . . . 4-187
Item IDs . . . . . . . . . . . . . . . . . . . . . . . 3-25 Crash . . . . . . . . . . . . . . . . . . . . . . 4-187
item_to_part_design utility . . . 4-109, 4-152 Release notes . . . . . . . . . . . . . . . . . 4-187
ItemRevision checkout . . . . . . . . . . . . . 4-85 Lists of values . . . . . . . . . . . . . . . . . . 4-147
Dynamic . . . . . . . . . . . . . . . . . . . . . 3-13
J Live Excel
Cascading LOVs not supported . . . . 4-139
Japanese characters . . . . . . . . . . . . . 4-178 Live Word
Java classes, deprecated . . . . . . . . . . . . 2-9 Cascading LOVs not supported . . . . 4-139
JT file issues in Teamcenter Client for Multi-choice properties not
Office . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 supported . . . . . . . . . . . . . . . . . 4-139
JT files . . . . . . . . . . . . . . . . . . . . . . . . 4-66 Validations . . . . . . . . . . . . . . . . . . 4-122
Load Operations command . . . . . . . . . . 4-76
K Load Selection command . . . . . . . . . . . 4-76
Localization
Key ID . . . . ............ . . . . . . . . 4-36 Multibyte . . . . . . . . . . . . . . . . . . . 3-142
Key IDs . . . ............ . . . . . . . . 3-25 Platforms . . . . . . . . . . . . . . . . . . . . . 1-5
Keywords . . ............ . . . . . . . 4-127 Text incorrect . . . . . . . . . . . . . . . . 4-177
Keywords in a requirements Localized properties . . . . . . . . . . . . . 4-172
document . ............ . . . . . . . 4-114 Logical assignments, import/export . . . 3-119
Logical models, diagram
L enhancements . . . . . . . . . . . . . . . . . . 3-81
Login Service . . . . . . . . . . . . . . . . . . 4-149
lastsaveddate.txt, upgrade issue . . . . . . 4-18 Lookup table . . . . . . . . . . . . . . . . . . . . 3-12
LDAP_member_list_attr preference . . 4-148 Lost data, Microsoft Windows . . . . . . . 4-185
ldapsync utility . . . . . . . . . . . . . . . . . 4-148 LOV types supported for Excel
Legacy product views . . . . . . . . . . . . . 4-66 Import . . . . . . . . . . . . . . . . . . . . . . 4-131
License categories for Authorized data LOV values, search criteria . . . . . . . . 4-169
access . . . . . . . . . . . . . . . . . . . . . . . . 3-35 LOVs
Lifecycle Viewer Translations . . . . . . . . . . . . . . . . . 4-175
Reconcile dialog box . . . . . . . . . . . . . 4-66
Status bar . . . . . . . . . . . . . . . . . . . . 4-67 M
Lifecycle Visualization
32-bit on 64-bit system not Macintosh MacOS
supported . . . . . . . . . . . . . . . . . . 4-16 Release notes . . . . . . . . . . . . . . . . . 4-190
Auto update failure . . . . . . . . . . . . . 4-59 Macintosh, PDFs on . . . . . . . . . . . . . . 4-46
FCC size . . . . . . . . . . . . . . . . . . . . . 4-66 MacOS
Group/role switch . . . . . . . . . . . . . . . 4-60 Release notes . . . . . . . . . . . . . . . . . 4-190
Installation . . . . . . . . . . . . . . . . . . . 4-16 viewer file associations . . . . . . . . . . 4-190

Index
Macros . . . . . . . . . . . . . . . . . . . . . . . 4-134 Internet Explorer 8 support

Mail_send_file_attachments_activated deprecated . . . . . . . . . . . . . . . . . . 2-2
preference . . . . . . . . . . . . . . . . . . . . 4-236 Windows XP support deprecated . . . . . 2-2
Maintenance, Repair, and Overhaul Microsoft Word
Default disposition . . . . . . . . . . . . . . 4-70 Applet error . . . . . . . . . . . . . . . . . . 4-168
Physical part . . . . . . . . . . . . . . . . . . 4-70 Auto-recovery feature . . . . . . . . . . . 4-133
Release notes . . . . . . . . . . . . . . . . . . 4-68 Embedded window . . . . . . . . . . . . . 4-126
Service discrepancies . . . . . . . . . . . . 4-68 Icon for duplicate objects . . . . . . . . 4-134
Stored option set . . . . . . . . . . . . . . . 4-69 Minimize ribbon . . . . . . . . . . . . . . . . . 4-42
Manufacturing author license, Modal dialogs, rich client . . . . . . . . . . 4-167
capabilities . . . . . . . . . . . . . . . . 4-72–4-73 Monitoring interface . . . . . . . . . . . . . . 4-45
Manufacturing Execution System Motion . . . . . . . . . . . . . . . . . . . . . . . . 4-64
Integration . . . . . . . . . . . . . . 3-109, 3-150 Mozilla Firefox
Manufacturing features . . . . . . . . . . . 3-119 Reporting and Analytics . . . . . . . . . . 4-94
Manufacturing Process Planner Multi-choice properties not supported in live
BOM line columns . . . . . . . . . . . . . . 4-79 Word . . . . . . . . . . . . . . . . . . . . . . . 4-139
Insert Level dialog box . . . . . . . . . . 4-109 Multi-Site
Pseudofolders . . . . . . . . . . . . . . . . . 4-74 Progress bar . . . . . . . . . . . . . . . . . . 4-83
Release notes . . . . . . . . . . . . . . . . . . 4-71 Release notes . . . . . . . . . . . . . . . . . . 4-82
Repair Broken Links dialog box . . . . . 4-79 Vendor management support . . . . . 4-140
Manufacturing viewer license, Multi-Site Collaboration, support for Visio
capabilities . . . . . . . . . . . . . . . . 4-72–4-73 diagrams . . . . . . . . . . . . . . . . . . . . . 3-80
Mapper lookup table . . . . . . . . . . . . . . 3-12 Multi-Site Collaboration, support for Visio
mapping_designer_projects directory . . 4-49 diagrams . . . . . . . . . . . . . . . . . . . . . 3-91
mapping_designer_projects_TCEC Multi-Site environment with negative site
directory . . . . . . . . . . . . . . . . . . . . . . 4-49 IDs . . . . . . . . . . . . . . . . . . . . . . . . . 4-221
Markup Manager task pane . . . . . . . . . 4-46 Multi-Site not supported with Schedule
Marshalling error . . . . . . . . . . . . . . . 4-138 Manager . . . . . . . . . . . . . . . . . . . . . . 4-98
Mass updates of structures . . . . 3-61, 3-105 Multi-Structure Manager
Massive Model Visualization (MMV) . . . 4-57 Release notes . . . . . . . . . . . . . . . . . . 4-83
Master locales . . . . . . . . . . . . . . . . . . 4-176 Multibyte support . . . . . . . . . . . . . . . 3-142
material_import utility . . . . . . . . . . . 4-218 Multifield keys . . . . . . . . . . . . . 3-33, 3-107
MATLAB integration . . . . . . . . . 3-86, 4-116 Application support . . . . . . . . . . . . . 3-26
Mechatronics Process Management In general . . . . . . . . . . . . . . . . . . . . 3-25
Editing a GDE element . . . . . . . . . . 4-80 Server support . . . . . . . . . . . . . . . . . 3-27
GDE structure . . . . . . . . . . . . . . . . . 4-81 Systems Engineering object
Release notes . . . . . . . . . . . . . . . . . . 4-79 definitions . . . . . . . . . . . . . . . . . 3-85
Microsoft TC_MFK_DEFAULT_DOMAIN
Office . . . . . . . . . . . . . . . . . . . . . . . 4-86 preference . . . . . . . . . . . . . . . . . 3-27
Windows, lost data . . . . . . . . . . . . . 4-185 Multiple value mode . . . . . . . . . . . . . . 4-84
Word . . . . . . . . . . . . . . . . . . . . . . . 4-136 Multivalued properties . . . . . . . . . . . . 4-85
Microsoft Excel My Teamcenter
Applet error . . . . . . . . . . . . . . . . . . 4-168 Microsoft Office documents . . . . . . . . 4-86
Microsoft Office Release notes . . . . . . . . . . . . . . . . . . 4-84
Client for Office access to all core file Save button . . . . . . . . . . . . . . . . . . . 4-87
types . . . . . . . . . . . . . . . . . . . . . 3-42 Text file . . . . . . . . . . . . . . . . . . . . . . 4-86
Microsoft Office 2010 support, Client for Viewer pane . . . . . . . . . . . . . . 4-86–4-87
Office . . . . . . . . . . . . . . . . . . . . . . . . 3-41 My Teamcenter (2007) . . . . . . . . . . . . . 3-50
Microsoft Office Word, comparing requirement
content . . . . . . . . . . . . . . . . . . . . . . . 3-83 N
Microsoft Office, custom datasets . . . . 4-40,
4-130 Named References dialog box . . . . . . . . 3-50
Microsoft Windows Negative site IDs . . . . . . . . . . . . . . . 4-221
32-bit support deprecated . . . . . . . . . . 2-1 Network Folders . . . . . . . . . . . . . . . . . 2-18

Index
New Activity command . . . . . . . . . . . . 4-73 Group administrator privilege

New budget definition . . . . . . . . . . . . 4-133 issue . . . . . . . . . . . . . . . . . . . . 4-148
New Process command, Manufacturing author Release notes . . . . . . . . . . . . . . . . . 4-148
license . . . . . . . . . . . . . . . . . . . . . . . 4-72 Outdated files in TC_USER_MSG_
New Workarea command . . . . . . . . . . . 4-72 DIR . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
NX Over-the-Web Installer . . . . . . . . . . . . 4-13
Lifecycle Visualization . . . . . . . . . . . 4-16 Ownership not updated in ODS . . . . . . 4-45
NX Integration . . . . . . . . . . . . . . . . . . 4-98
Launch error . . . . . . . . . . . . . . . . . . 4-88 P
NX component . . . . . . . . . . . . . . . . . 4-88
Release notes . . . . . . . . . . . . . . . . . . 4-88 Parameter definition objects . . . . . . . . 4-165
NX_Supports_VISSC preference . . . . . 4-237 Parametric note . . . . . . . . . . . . . . . . 4-136
Part Data does not autopopulate . . . . . . 4-92
O Part-CAD alignment, automating . . . . 3-104
Password, valid characters . . . . 4-216–4-217,
Object properties, update . . . . . . . 3-33, 3-35 4-224, 4-253
Obsolete Passwords, whitespace not
Data model . . . . . . . . . . . . . . . . . . . 2-24 allowed . . . . . . . 4-216–4-217, 4-224, 4-253
Functions . . . . . . . . . . . . . . . . . . . . 2-19 PDF issues, Manufacturing Process
Preferences . . . . . . . . . . . . . . . . . . . 2-24 Planner . . . . . . . . . . . . . . . . . . . . . . 4-73
Utilities . . . . . . . . . . . . . . . . . . . . . 2-31 PDF markup . . . . . . . . . . . . . . . . . . . 4-46
Obsolete features PDF reader, UNIX . . . . . . . . . . . . . . . 4-188
My Teamcenter (2007) . . . . . . . . . . . 2-18 PDF reports
Network Folders . . . . . . . . . . . . . . . 2-18 2D file types . . . . . . . . . . . . . . . . . . 4-76
Teamcenter proxy server for GD&T symbols . . . . . . . . . . . . . . . . 4-77
WebDAV . . . . . . . . . . . . . . . . . . . 2-18 GD&T symbols not displaying
Obsoletion correctly . . . . . . . . . . . . . . . . . . . 4-75
Change Viewer . . . . . . . . . . . . . . . . 2-15 Low quality images in PDF reports . . 4-76
Global variables in appr.h file . . . . . . 2-17 Naming problem . . . . . . . . . . . . . . . 4-77
PIE_init_module ITK . . . . . . . . . . . . 2-19 PER_CLIENT activation mode
Occurrence effectivities, export issues . . 4-71 deprecated . . . . . . . . . . . . . . . . . . . . . 2-2
Occurrence trace links . . . . . . . . . . . . 4-115 PER_CLIENT setting . . . . . . . . . . . . . 4-15
ODE Performance testing . . . . . . . . . . . . . 4-146
EAR file, deploying on WebLogic . . . . 4-50 Permission denied . . . . . . . . . . . . . . . . 4-15
EAR file, deploying on WebSphere Persistent Object Model, see POM
7 . . . . . . . . . . . . . . . . . . . . . . . . 4-51 PIE_init_module ITK obsoletion . . . . . . 2-19
ODS does not start automatically on PIPMEAPPEARANCE_3 index
Linux . . . . . . . . . . . . . . . . . . . . . . . . 4-51 unique . . . . . . . . . . . . . . . . . . . . . . 4-103
ODS service, SUSE Linux . . . . . . . . . . 4-51 Platform-specific release notes . . . . . . 4-180
ODS startup error . . . . . . . . . . . . . . . . 4-50 PLM XML
ODS support . . . . . . . . . . . . . . . . . . . 4-180 Service Planning, export/import . . . . 4-77
Office 2010 PLM XML import/export . . . . . . . . . . 4-171
Macros . . . . . . . . . . . . . . . . . . . . . 4-124 PLM XML release notes . . . . . . . . . . . . 4-90
Security settings . . . . . . . . . . . . . . 4-137 POM
Office, Microsoft Transmit schema files . . . . . . . . . . 4-223
Client for Office access to all core file POM_TIMESTAMP table blocking
types . . . . . . . . . . . . . . . . . . . . . 3-42 sessions . . . . . . . . . . . . . . . . . . . . . . 4-13
Open Items list . . . . . . . . . . . . . . . . . 4-161 POM_TRANSMIT_DIR directory . . . . 4-223
Operating systems, release notes . . . . 4-180 POM_TRANSMIT_DIR variable on
Options and variants . . . . . . . . . . . . . 3-107 Windows . . . . . . . . . . . . . . . . . . . . . 4-223
Options, controlling access to . . . . . . . . 3-28 Pool manager . . . . . . . . . . . . . . . . . . 4-180
ORA-12801 error, Oracle . . . . . . . . . . . 4-17 Post hook ignored for create actions . . 4-162
Oracle error ORA-12801 . . . . . . . . . . . 4-17 PostScript printer installation . . . . . . 4-201
Organization PowerPoint datasets . . . . . . . . . . . . . 4-166

Index
PowerPoint file remains read-only . . . . 4-42 Published flag on C++ code . . . . . . . . 4-158
PowerPoint files . . . . . . . . . . . . . . . . 4-160
Preferences . . . . . . . . . . . . . . . . . . . . 4-225 Q
Change Manager . . . . . . . . . . . . . . . 4-33
Deprecated . . . . . . . . . . . . . . . . . . . 2-13 Query Builder
Deprecated ERP Connect Toolkit . . . . . 2-6 Quick search . . . . . . . . . . . . . . . . . . 4-91
Multiple value entry . . . . . . . . . . . . . 4-84 Release notes . . . . . . . . . . . . . . . . . . 4-91
Obsolete . . . . . . . . . . . . . . . . . . . . . 2-24 Query utilities
PSECopyAbsOccDuring build_fts_index . . . . . . . . . . . . . . . 4-260
VICreation . . . . . . . . . . . . . . . . 4-106 Quick search . . . . . . . . . . . . . . . . . . . . 4-91
PSECopyArrangementsDuring
VICreation . . . . . . . . . . . . . . . . 4-106 R
PSECreateVISameType . . . . . . . . . 4-106
SE_Trace_Report_Layout . . . . . . . . . 3-82 RDV
TC_config_rule_name . . . . . . . . . . . 4-170 Release notes . . . . . . . . . . . . . . . . . . 4-92
TC_fts_indexed_types . . . . . . . . . . . 4-198 Realized By relationship . . . . . . . . . . . 4-80
Vis_Doc_OpenOption . . . . . . . . . . . . 4-59 Reconcile dialog box . . . . . . . . . . . . . . 4-66
Preferences, controlling access to . . . . . 3-28 Red
Primary Interop Assemblies (PIA) . . . 4-114 Datasets . . . . . . . . . . . . . . . . . . . . 4-166
primary_entry . . . . . . . . . . . . . . 3-30, 3-40 Red Hat Enterprise Linux
Pro/ENGINEER . . . . . . . . . . . . . . . . 4-109 issues . . . . . . . . . . . . . . . . . . . . 4-50–4-51
Problem viewing Global Services displayed refactoring GRM_create postactions . . 4-155
content . . . . . . . . . . . . . . . . . . . . . . 4-215 Reference designators . . . . . . . . . . . . 4-139
Process assignment lists . . . . . . . . . . 4-144 Refreshing views . . . . . . . . . . . . . . . . 4-134
Process History view . . . . . . . . . . 3-62, 3-71 Registry scripts, Security Services
Product Configurator . . . . . . . . . . . . . . 3-98 configuration . . . . . . . . . . . . . . . . . . . 4-62
Product views . . . . . . . . . . . . . . . . . . 3-106 Relation Browser . . . . . . . . . . . . . . . 4-130
Product-scoped cacheless searches . . . 3-132 Relation Browser, hierarchical
Progress bar, Multi-Site . . . . . . . . . . . . 4-83 numbering . . . . . . . . . . . . . . . . . . . . 3-83
Project Relationships . . . . . . . . . . . . . . . . . . . 4-80
Designating multiple project team Repair Broken Links dialog box . . . . . . 4-79
administrators . . . . . . . . . . . . . . 3-35 Repeatable Digital Validation
Release notes . . . . . . . . . . . . . . . . . . 4-90 Release notes . . . . . . . . . . . . . . . . . . 4-92
Removing object . . . . . . . . . . . . . . . . 4-90 Save button in Platform Designer . . . 4-92
Usability improvements . . . . . . . . . . 3-35 Report Builder
Project team member, removing . . . . . 4-147 Release notes . . . . . . . . . . . . . . . . . . 4-93
Project, deleting . . . . . . . . . . . . . . . . 4-146 Upgrading . . . . . . . . . . . . . . . . . . . . 4-93
Properties Reporting and Analytics
Dialog box . . . . . . . . . . . . . . . . . . . . 4-85 Database query . . . . . . . . . . . . . . . . 4-96
Editing . . . . . . . . . . . . . . . . . . . . . 4-174 Databases . . . . . . . . . . . . . . . . . . . . 4-94
Localizing . . . . . . . . . . . . . . . . . . . 4-172 Filter conditions . . . . . . . . . . . . . . . 4-95
Property Finder Formatter search results Firefox browser . . . . . . . . . . . . . . . . 4-94
issue . . . . . . . . . . . . . . . . . . . . . . . 4-161 IS NULL operator . . . . . . . . . . . . . . 4-95
Proxy server for WebDAV . . . . . . . . . . . 2-18 Passwords . . . . . . . . . . . . . . . . . . . . 4-93
PS files, in PDF reports . . . . . . . . . . . . 4-76 Release notes . . . . . . . . . . . . . . . . . . 4-93
PSECopyAbsOccDuringVICreation Saved query . . . . . . . . . . . . . . 4-95–4-96
preference . . . . . . . . . . . . . . . . . . . . 4-106 Scheduled tasks . . . . . . . . . . . . . . . . 4-95
PSECopyArrangementsDuringVICreation Search . . . . . . . . . . . . . . . . . . . . . . 4-95
preference . . . . . . . . . . . . . . . . . . . . 4-106 REQ_create_object_template . . . . . . . 4-127
PSECreateVISameType preference . . . 4-106 REQ_default_object_template preference, live
Pseudofolders . . . . . . . . . . . . . . . . . . . 4-74 Word . . . . . . . . . . . . . . . . . . . . . . . 4-112
PSOccurrences, defining . . . . . . . . . . 3-106 req_migrate_fulltext utility . . . . . . . . 4-111

Index
Requirement documents, autosave disabled in Calendar . . . . . . . . . . . . . . . . . . 4-4, 4-99

Word . . . . . . . . . . . . . . . . . . . . . . . 4-133 Data model deprecation . . . . . . . . . . 2-10
Requirements Release notes . . . . . . . . . . . . . . . . . . 4-98
NX part design and validation . . . . . . 3-84 Site Consolidation . . . . . . . . . . . . . 4-151
Requirements, comparing content in Summary task . . . . . . . . . . . . . . . . . 4-99
Word . . . . . . . . . . . . . . . . . . . . . . . . 3-83 With Multi-Site . . . . . . . . . . . . . . . . 4-98
Reservation, transfer to other user, Client for Schedule Manager objects . . . . . . . . . . . 4-6
Office . . . . . . . . . . . . . . . . . . . . . . . . 3-42 Schedule Manager, LOV values . . . . . . 4-99
Resource Browser Schedule task change folders . . . . . . . . 3-71
Release notes . . . . . . . . . . . . . . . . . . 4-97 ScheduleTaskClassNameToCreate . . . 4-238
Support for mixed unit classes . . . . . 4-97 SCORM package, title not saved . . . . . . 4-44
Resource Manager SE_Trace_Report_Layout, Teamcenter
Release notes . . . . . . . . . . . . . . . . . . 4-97 preference . . . . . . . . . . . . . . . . . . . . . 3-82
Review tasks . . . . . . . . . . . . . . . . . . . 3-70 SE_Trace_Report_Layout, Teamcenter
Rich client preference . . . . . . . . . . . . . . . . . . . . . 3-82
Create dialog box . . . . . . . . . . . . . . . 3-46 Search
Datasets . . . . . . . . . . . . . . . . . . . . 4-166 Errors . . . . . . . . . . . . . . . . . . . . . . . 4-91
Firewall issues, Windows Server Full-text . . . . . . . . . . . . . . . 4-193–4-194
2008 . . . . . . . . . . . . . . . . . . . . . 4-184 Search criteria, import/export . . . . . . 3-119
Hiding commands . . . . . . . . . . . . . 4-162 Search, LOV not populated . . . . . . . . 4-169
Lite Edition . . . . . . . . . . . . . . . . . . . 4-14 Security Services . . . . . . . . . . . . . . . 4-149
Modal dialogs . . . . . . . . . . . . . . . . 4-167 Security Services profile settings . . . . . 4-62
Obsolete on IBM AIX . . . . . . . . . . . . 2-17 Sequences Access Manager rule . . . . . . 4-24
Options and Preferences . . . . . . . . . . 3-48 Show unconfigured . . . . . . . . . . . . . . 3-106
PowerPoint . . . . . . . . . . . . . . . . . . 4-166 Simpgen translator . . . . . . . . . . . . . . 4-151
Preference changes . . . . . . . . . . . . 4-170 Simulation Process Management
Ready status . . . . . . . . . . . . . . . . . 4-166 Launch tool enhancements for multifield
Release notes . . . . . . . . . . . . . . . . . 4-159 keys . . . . . . . . . . . . . . . . . . . . . 3-134
Slow logon in four-tier . . . . . . . . . . 4-184 Out-of-date notification
XRT style sheets . . . . . . . . . . . 3-46, 3-48 improvements . . . . . . . . . . . . . . 3-136
Rich client enhancements Packages for creating CAE data . . . 3-135
Options and Preferences . . . . . . . . . . 3-48 Structure comparison
Summary view . . . . . . . . . . . . . . . . . 3-46 enhancements . . . . . . . . . . . . . . 3-137
Rich Client Interface Guide . . . . . . . . 4-242 Structure management enhancements for
Rich client user interface . . . . . . . . . . . 3-45 multifield keys . . . . . . . . . . . . . 3-134
Rich client utilities Usability enhancements incorporating
identify_non_structure_edges . . . . . 3-132 multiple views . . . . . . . . . . . . . 3-136
qsearch_process_queue . . . . . . . . . . 3-132 Site
Roll up variants . . . . . . . . . . . . . . . . 3-108 Check out . . . . . . . . . . . . . . . . . . . . 4-53
Root model hierarchy, problem . . . . . . . 4-68 Consolidation . . . . . . . . . . . . . . . . 4-151
Route tasks . . . . . . . . . . . . . . . . . . . . 3-70 Site Consolidation release notes . . . . . 4-151
Rule conditions for Access Manager . . . 3-34 Sites
Russian locales, TEM text display Synchronizing definitions . . . . . . . . 4-222
problem . . . . . . . . . . . . . . . . . . . . . 4-175 Smart card authentication . . . . . . . . . 4-149
Snapshot dataset, Word export . . . . . . . 3-84
S Software requirements . . . . . . . . . . . . . 1-6
Solid Edge data, issues viewing . . . . . . . 4-2
Save as . . . . . . . . . . . . . . . . . . . . . . . 3-11 Spatial searches . . . . . . . . . . . . . . . . 3-105
Save As functionality . . . . . . . . . . . . . . 3-54 Specification Manager . . . . . . . . . . . . 4-100
Save As operation . . . . . . . . . . . . . . . 4-160 Standard text . . . . . . . . . . . . . . . . . . 3-111
Save button . . . . . . . . . . . . . . . . . . . . 4-87 Status
SaveAs operation . . . . . . . . . . . . . . . 4-177 Rich client . . . . . . . . . . . . . . . . . . . 4-166
Saved query . . . . . . . . . . . . . . . . 4-95–4-96 Stop running this script prompt, thin
Schedule Manager . . . . . . . . . . . . . . . . 3-78 client . . . . . . . . . . . . . . . . . . . . . . . . 4-79

Index
Structure filtering BOM lines . . . . . . . . . . . . . . . . . . . 4-135

Closure rules . . . . . . . . . . . . . . . . . 3-109 Cascading LOVs not supported . . . . 4-139
Structure Manager . . . . . . . . . . . . . . 4-101 Data model obsoletion . . . . . . . . . . . 2-24
BOM reports . . . . . . . . . . . . . . . . . 4-105 Importing requirement specifications with
BOM restructuring . . . . . . . . . . . . . 4-80 SpecElement subtypes . . . . . . . . 4-137
Clear Repositioning check box . . . . . 4-106 Macros . . . . . . . . . . . . . . . . . . . . . 4-134
com.teamcenter.rac.pse.PSEAppplication. Multi-choice properties not
MRUEntries preference . . . . . . . 4-101 supported . . . . . . . . . . . . . . . . . 4-139
Date properties . . . . . . . . . . . . . . . 4-104 Properties . . . . . . . . . . . . . . . . . . . 4-137
Edit in Place . . . . . . . . . . . . . . . . . . . 4-3 Reference designators . . . . . . . . . . . 4-139
Export to Live Excel . . . . . . . . . . . . . . 4-3 Time-out . . . . . . . . . . . . . . . . . . . . 4-136
Four-tier server session time-out . . . 4-110 Systems Engineering and Requirements
Implemented By relationship . . . . . . 4-80 Management
Incremental change . . . . . . . 4-109–4-110 Compare content . . . . . . . . . . . . . . 4-119
Issue switching NX arrangements . . 4-108 Compare with prior . . . . . . . . . . . . 4-119
Precise entry removed . . . . . . . . . . 4-107 Excel Import wizard . . . . . . . . . . . . 4-120
Realized By relationship . . . . . . . . . . 4-80 Flat file add-ins . . . . . . . . . . . . . . . 4-117
Refresh . . . . . . . . . . . . . . . . . . . . . 4-110 Icons . . . . . . . . . . . . . . . . . . . . . . . 4-118
Release notes . . . . . . . . . . . . . . . . . 4-101 Release notes . . . . . . . . . . . . . . . . . 4-111
Saving structures . . . . . . . . . . . . . . 4-104 Traceability reports . . . . . . . . . . . . 4-117
Usability enhancements . . . . . . . . . 3-107
Structure Manager, cross section viewer stays T
active . . . . . . . . . . . . . . . . . . . . . . . . 4-55
Structure search . . . . . . . . . . . . . . . . 3-111 tc_config_attr_mapping utility . . . . . . . . 2-8
Structure Search . . . . . . . . . . . . . . . . 3-110 TC_config_rule_name preference . . . . 4-170
Studies . . . . . . . . . . . . . . . . . . . . . . . 3-115 TC_fts_default_AND_operator
Study template . . . . . . . . . . . . . . . . . . 4-72 preference . . . . . . . . . . . . . . . . . . . . . 4-84
Style sheets . . . . . . . . . . . . . . . . . . . . 3-52 TC_fts_indexed_types preference . . . . 4-198
Subclasses not displayed in Open/Insert dialog tc.h header file deprecation . . . . . . . . . . 2-5
box . . . . . . . . . . . . . . . . . . . . . . . . . 4-116 TC_LSBLT_SIZE environment
Subprocesses in workflow . . . . . . . . . . 3-69 variable . . . . . . . . . . . . . . . . . . . . . 4-115
Subscription Monitor . . . . . . . . . . . . . 4-152 TC_MFK_DEFAULT_DOMAIN
Subscription Monitor release notes . . . 4-152 preference . . . . . . . . . . . . . . . . . . . . . 3-27
Subscriptions, during upgrade . . . . . . . 4-18 TC_TMP_DIR environment
Subsystems with same name at different variable . . . . . . . . . . . . . . . . . . . . . 4-228
levels, problem . . . . . . . . . . . . . . . . . 4-68 TC_USER_LIB environment
Summary variable . . . . . . . . . . . . . . . . . . . . . 4-228
Task in Schedule Manager . . . . . . . . 4-99 TC_USER_MSG_DIR environment
Sun Solaris variable . . . . . . . . . . . . . . . . . . . . . . 4-19
Ethernet MAC addresses . . . . . . . . 4-186 TC_USER_MSG_DIR, outdated files . . . 4-19
Release notes . . . . . . . . . . . . . . . . . 4-186 TC_VALIDATION_send_envelope_for_
Supplier data exchange . . . . . . . . . . . . 3-87 override preference . . . . . . . . . . . . . 4-257
Support announcements . . . . . . . . . . . . 2-1 TcCheckoutReserverOnly preference . . . 4-27
SUSE Linux TCCS_CONFIG environment
Release notes . . . . . . . . . . . . . . . . . 4-187 variable . . . . . . . . . . . . . . . . . . . . . 4-227
SUSE Linux issues . . . . . . . . . . . 4-50–4-51 TCCS_CONFIG_HOME environment
Symbol display . . . . . . . . . . . . . . . . . 4-111 variable . . . . . . . . . . . . . . . . . . . . . 4-227
Synchronize data directories . . . . . . . . 4-22 TCEDA_JAVA_HOME variable . . . . . 4-141
Synchronizing TCEDA_JRE_HOME variable . . . . . . 4-141
POM transmit schema files . . . . . . . 4-223 TcPublishing
Site definitions . . . . . . . . . . . . . . . 4-222 Assets . . . . . . . . . . . . . . . . . . . . . . 4-142
System administration release Classification search . . . . . . . . . . . . 4-78
notes . . . . . . . . . . . . . . . . . . . . . . . 4-146 TCRS-Create-Print-Requests handler . . . 4-8
Systems Engineering TCRS-setstatus-EO-folder handler . . . . . 4-8

Index
Teamcenter Viewing Lifecycle Visualization data

Deprecated on HP-UX Itanium . . . . . . 2-6 in . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Install or upgrading . . . . . . . . . . . . . . 1-1 Thin client interface preferences
Preferences appbar_title_contents . . . . . . . . . . . . 3-51
SE_Trace_Report_Layout . . . . . . 3-82 WEB_title_contents . . . . . . . . . . . . . 3-52
Services . . . . . . . . . . . . . . . . . . . . . . 2-9 Thin client, enhancements . . . . . . . . . . 3-43
Teamcenter administrator Thin client, script prompt in Internet
password . . . . . 4-216–4-217, 4-224, 4-253 Explorer . . . . . . . . . . . . . . . . . . . . . . 4-79
Teamcenter Automotive Edition–GM Overlay ThinClient-GlobalOrg role . . . . . . . . . 4-177
Release notes . . . . . . . . . . . . . . . . . . 4-54 Third-party products
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54 Applications support information . . . . 1-3
Teamcenter Client for Microsoft Office, Release notes . . . . . . . . . . . . . . . . . 4-180
enhancements . . . . . . . . . . . . . . . . . . 3-41 TIF files, in PDF reports . . . . . . . . . . . 4-76
Teamcenter Client for Office Time and Process Gantt views . . . . . . . 4-73
JT file issues . . . . . . . . . . . . . . . . . . . 4-2 Time-out . . . . . . . . . . . . . . . . . . . . . 4-136
Teamcenter documentation Trace link icon removed . . . . . . . . . . . 4-133
New . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Trace links, attaching custom notes . . . 3-83
Obsolete . . . . . . . . . . . . . . . . . . . . . . 3-4 Traceability across Teamcenter
Revised . . . . . . . . . . . . . . . . . . . . . . . 3-3 domains . . . . . . . . . . . . . . . . . . . . . . 3-80
Teamcenter EDA Traceability report, blank column . . . . 4-131
Folder path problem . . . . . . . . . . . . 4-141 Traceability report, duplicate child . . . 4-131
Release notes . . . . . . . . . . . . . . . . . 4-141 Traceability reports . . . . . . . . . . . . . . 4-117
Teamcenter Integration for NX Traceability view, Systems Engineering,
Download hyperlink not available . . . 4-89 arranging pane layout . . . . . . . . . . . . 3-82
Release notes . . . . . . . . . . . . . . . . . . 4-88 TraceLink class obsoletion . . . . . . . . . . 2-24
Teamcenter lifecycle visualization Two-tier mode . . . . . . . . . . . . . . . . . . . 4-15
iSeries . . . . . . . . . . . . . . . . . . . . . . 4-67 typeAndRuleForProcessConfiguration
Teamcenter proxy server for WebDAV . . 2-18 preference . . . . . . . . . . . . . . . . . . . . . 4-75
Teamcenter Rapid Start Typed reference properties . . . . . . . . . 4-157
ACLs missing . . . . . . . . . . . . . . . . . 4-10
TC_MFK_DEFAULT_DOMAIN preference U
value required . . . . . . . . . . . . . . . . 4-1
What’s new . . . . . . . . . . . . . . . . . . . . 3-5 UNIX systems
Workflow handler issues after GM Overlay . . . . . . . . . . . . . . . . . . 4-188
upgrading . . . . . . . . . . . . . . . . . . . 4-8 Hidden dialog boxes . . . . . . . . . . . . 4-188
Teamcenter Rapid Start upgrade Release notes . . . . . . . . . . . . . . . . . 4-188
issues . . . . . . . . . . . . . . . . . . . . . . . 4-256 Update object properties . . . . . . . 3-33, 3-35
Teamcenter status shown in system Upgrade
tray . . . . . . . . . . . . . . . . . . . . . . . . 4-164 Failure logs . . . . . . . . . . . . . . . . . . . 4-21
Technical help . . . . . . . . . . . . . . . . . . . . 1-4 Import of objects may cause data
TEM problem in Russian locales . . . . . 4-175 corruption . . . . . . . . . . . . . . . . . . 4-20
Template precedence, live Word . . . . . 4-112 In general . . . . . . . . . . . . . . . . . . . . . 1-1
Templates . . . . . . . . . . . . . . . . . . . . . 4-22 Outdated files in TC_USER_MSG_
Templates, document generation DIR . . . . . . . . . . . . . . . . . . . . . . 4-19
process . . . . . . . . . . . . . . . . . . . . . . 4-123 PIPMEAPPEARANCE_3 index . . . . 4-103
Text file . . . . . . . . . . . . . . . . . . . . . . . 4-86 Report Builder . . . . . . . . . . . . . . . . . 4-93
Thin client . . . . . . . . . . . . . . . . . . . . 4-168 Upgrade Guide
Enhancements . . . . . . . . . . . . . . . . . 3-43 Teamcenter Rapid Start upgrade
Favorites list . . . . . . . . . . . . . . . . . 4-171 issues . . . . . . . . . . . . . . . . . . . . 4-256
Installation issues in . . . . . . . . . . . . . 4-4 Upgrade, Content Management
Preference changes . . . . . . . . . . . . 4-170 issues . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Problems with ampersands . . . . . . . 4-170 Upgrading
Release notes . . . . . . . . . . . . . . . . . 4-168 Content Management . . . . . . . . 4-25–4-27
User names, ampersands . . . . . . . . 4-170 Usability release notes . . . . . . . . . . . . 4-28

Index
Use temporary folders per session . . . 4-184 Visio diagrams

UTF-8 . . . . . . . . . . . . . . . . . . 3-142, 4-178 Domain assignment, child
Utilities diagrams . . . . . . . . . . . . . . . . . . 3-79
bmide_postupgradetotc . . . . . . . . . . . . 2-7 General Relationship Management (GRM)
cae_geometry_fix . . . . . . . . . . . . . . . 4-21 relations . . . . . . . . . . . . . . . . . . . 3-79
combine_audit_files . . . . . . . . . . . . . . 2-7 Multi-Site Collaboration support . . . 3-80,
data_share . . . . . . . . . . . . . . . . . . 4-178 3-91
define_auditdefs . . . . . . . . . . . . . . . . . 2-7 Visualization Illustration
Deprecated . . . . . . . . . . . . . . . . . . . . 2-7 Incremental change . . . . . . . . . . . . 4-142
generate_loadfsccache_tickets . . . . . . 2-31 Modular variant configurations . . . . 4-142
install_event_types . . . . . . . . . . . . . . 2-7 Release notes . . . . . . . . . . . . . . . . . 4-142
item_to_part_design . . . . . . . 4-109, 4-152
ldapsync . . . . . . . . . . . . . . . . . . . . 4-148 W
material_import . . . . . . . . . . . . . . . 4-218
Obsolete . . . . . . . . . . . . . . . . . . . . . 2-31 Web Browser application . . . . . . . . . . 4-164
Obsolete utilities WEB_Applications_List . . . . . . . . . . . 4-239
import_dfa_file . . . . . . . . . . . . . 2-31 WEB_default_url_autoconfirm preference,
Release notes . . . . . . . . . . . . . . . . . 4-152 creating . . . . . . . . . . . . . . . . . . . . . . 4-56
tc_config_attr_mapping . . . . . . . . . . . 2-8 WEB_Nav_Items_List . . . . . . . . . . . . 4-240
Utilities Reference . . . . . . . . . . . . . . 4-258 WEB_status_icons preference . . . . . . 4-154
Utility WEB_title_contents preference . . . . . . . 3-52
build_fts_index . . . . . . . . . . . . . . . 4-198 WebKey account . . . . . . . . . . . . . . . . . . 1-4
WebLogic
V Global Services ODE EAR file . . . . . . 4-50
HTTP-only flag . . . . . . . . . . . . . . . 4-150
Validation Manager . . . . . . 3-34, 3-86, 3-100 WebSphere
Validation preferences Global Services . . . . . . . . . . . . . . . . 4-50
TC_VALIDATION_send_envelope_for_ ODE EAR file . . . . . . . . . . . . . . . . . 4-51
override . . . . . . . . . . . . . . . . . . 4-257 Weld points . . . . . . . . . . . . . . . . . . . 3-119
Validation requirements, NX parts . . . . 3-84 Windows
Variables 2003 Server . . . . . . . . . . . . . . . . . . 4-184
POM_TRANSMIT_DIR . . . . . . . . . 4-223 32-bit support deprecated . . . . . . . . . . 2-1
TCEDA_JAVA_HOME . . . . . . . . . . 4-141 Internet Explorer 8 support
TCEDA_JRE_HOME . . . . . . . . . . . 4-141 deprecated . . . . . . . . . . . . . . . . . . 2-2
Variant Item Creation . . . . . . . . . . . . 4-106 Release notes . . . . . . . . . . . . . . . . . 4-184
Variants . . . . . . . . . . . . . . . . . . 3-95, 3-107 Windows XP support deprecated . . . . . 2-2
Rolling up . . . . . . . . . . . . . . . . . . . 3-108 Windows service and the POM_TRANSMIT_
Variants view . . . . . . . . . . . . . . . . . . 4-159 DIR variable . . . . . . . . . . . . . . . . . . 4-223
Vendor management . . . . . . . . . . . . . 4-140 WinZip . . . . . . . . . . . . . . . . . . . . . . . 4-184
Vendor Management Word
Multifield keys . . . . . . . . . . . . . . . . . 3-33 Auto-recovery feature . . . . . . . . . . . 4-133
Vendor Management supports multifield Icon for duplicate objects . . . . . . . . 4-134
keys . . . . . . . . . . . . . . . . . . . . . . . . . 3-33 Live . . . . . . . . . . . . . . . . . . . . . . . 4-121
Vertical scroll bar . . . . . . . . . . . . . . . 4-164 Word, comparing requirement
Viewer content . . . . . . . . . . . . . . . . . . . . . . . 3-83
Pane . . . . . . . . . . . . . . . . . . . . 4-86–4-87 Word_Export_TcTypes preference . . . . 4-241
Viewer file associations, MacOS . . . . . 4-190 Word_Show_Display_Name
Viewer issues preference . . . . . . . . . . . . . . . . . . . . 4-126
Solid Edge data . . . . . . . . . . . . . . . . . 4-2 Workflow
Viewing Lifecycle Visualization data in thin Argument changes . . . . . . . . . . . . . . 3-63
client . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Audit . . . . . . . . . . . . . . . . . . . . . . . 3-71
Vis_Doc_OpenOption preference . . . . . . 4-59 Background processing . . . . . . . . . . . 3-69
Visio Change Viewer . . . . . . . . . . . . . . . . 3-70
Interface . . . . . . . . . . . . . . . . . . . . 4-130 Claim tasks . . . . . . . . . . . . . . . . . . . 3-70

Index
Customize the perform signoff user Workflow handlers

interface . . . . . . . . . . . . . . . . . . . 3-70 Issues after upgrading from Teamcenter
Data model deprecation . . . . . . . . . . 2-24 Rapid Start . . . . . . . . . . . . . . . . . . 4-8
Filtering workflow processes . . . . . . . 3-71 Workflow utilities
Handler name changes . . . . . . . . . . . 3-63 cleanup_userinbox . . . . . . . . . . . . . 4-266
Keyword name changes . . . . . . . . . . 3-63 Workflows . . . . . . . . . . . . . . . . . . . . . . 4-6
Process assignment lists . . . . . . . . . 4-144
Process History view . . . . . . . . 3-62, 3-71 X
Progress tracking . . . . . . . . . . . . . . . 3-62
X11 fonts . . . . . . . . . . . . . . . . . . . . . . 4-58
Review tasks . . . . . . . . . . . . . . . . . . 3-70
Xalan JAR files . . . . . . . . . . . . . . . . . . 4-49
Route tasks . . . . . . . . . . . . . . . . . . . 3-70
XMetal validation error . . . . . . . . . . . . 4-45
Save toolbar button . . . . . . . . . . . . 4-143
Schedule task change folders . . . . . . 3-71
Signoff task . . . . . . . . . . . . . . . . . . 4-144 Z
Subprocesses . . . . . . . . . . . . . . . . . . 3-69 ZIP files . . . . . . . . . . . . . . . . . . . . . . 4-184
Workflow Condition task . . . . . . . . . . . 3-61

TC 10 1 Release Bulletin PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

TC 10 1 Release Bulletin PDF

Transféré par

Droits d'auteur :

Formats disponibles

Teamcenter 10.

This software and related documentation are proprietary to Siemens Product

2 Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

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

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

Support announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Teamcenter 10.1 release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin 3

Documentation release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-192

4 Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

1 Before you begin

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

Installing or upgrading Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Teamcenter and compatible third-party software versions . . . . . . . . . . . . . . . 1-3

Global Technical Access Center (GTAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Available Teamcenter 10.1 platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Hardware, software, and disk space requirements . . . . . . . . . . . . . . . . . . . . . 1-6

Using documentation . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin

1 Before you begin

Before you begin

• What’s new announcements

Installing or upgrading Teamcenter

o Articles describing new installation features.

o Release notes describing workarounds for known installation problems.

PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin 1-1

o Release notes describing workarounds for known upgrade problems.

Also see the Upgrade Guide.

1-2 Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

Teamcenter and compatible third-party software versions

• Compatibility for relinking customizations and paths.

Typically, operating system manufacturers assure run-time binary compatibility

PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin 1-3

Global Technical Access Center (GTAC)

• Frequently asked questions

• Product defect reports

• Patches and technical documentation

• Tips pertaining to Teamcenter customization, performance, and administration

• Product information, customer success stories, and user conference presentations

1-4 Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

Available Teamcenter 10.1 platforms

Teamcenter 10.1 is translated into the following language locales on all

PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin 1-5

Hardware, software, and disk space requirements

Required hard disk space for Teamcenter configurations

Using PDF files

1. Itanium platforms only. PA-RISC hardware is not supported.

1-6 Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

Teamcenter PDF online help collection

UNIX or Linux systems:

PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin 1-7

Searching the PDF help collection

• Network host (UNC path):

Using the PDF online help collection in Firefox Web browsers

• Turn off the popup blocker (Tools®Options®Content).

1-8 Teamcenter 10.1 Release Bulletin PLM00001 K (01-037134-0101)

Using HTML files

Teamcenter HTML online help collection

• If you want to view the Teamcenter online help library in HTML

PLM00001 K (01-037134-0101) Teamcenter 10.1 Release Bulletin 1-9

Overview of feature support announcements . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Deprecated feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1