Teamcenter 8.3 Release Bulletin: Publication Number PLM00001 G (01-037134-083)

Teamcenter 8.
3 Release Bulletin
Publication Number
PLM00001 G (01-037134-083)
Proprietary and restricted rights notice
This software and related documentation are proprietary to Siemens Product

Lifecycle Management Software Inc.
© 2010 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
All trademarks belong to their respective holders.
2 Teamcenter 8.3 Release Bulletin PLM00001 G (01-037134-083)

Contents
Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2
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 8.3 platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Hardware, software, and disk space requirements . . . . . . . . . . . . . . . . . . . . . 1-5
Using documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Support and certification announcements . . . . . . . . . . . . . . . . . . . . . . . 2-1

Deprecated feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Obsolete feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
What’s new for Teamcenter 8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

New Teamcenter applications and solutions . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
New Teamcenter documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Configuring Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Administering Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Using Teamcenter interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Managing changes and workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Sharing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Managing product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Managing manufacturing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Visualizing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Managing CAE data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Repeatable Digital Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Managing quality data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Managing Maintenance, Repair, and Overhaul data . . . . . . . . . . . . . . . . . . . . 3-34
Customizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Teamcenter industry solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Teamcenter 8.3 product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Teamcenter 8.3 documentation release notes . . . . . . . . . . . . . . . . . . . . . . . . 4-114
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
PLM00001 G (01-037134-083) Teamcenter 8.3 Release Bulletin 3

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

Using PDF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Using HTML files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
PLM00001 G (01-037134-083) Teamcenter 8.3 Release Bulletin

Chapter
1 Before you begin
This release bulletin contains the following information:

• Support and certification announcements
Important announcements about the release, including a list of deprecated and
obsolete features.
For more information, see Support and certification announcements.
• What’s new announcements

Descriptions of new features.
For more information, see What’s new for Teamcenter 8.3.
• Release notes
Workarounds for known problems.
For more information, see Release notes.
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:
– Brief articles describing new installation features.
For more information, see What’s new for Teamcenter 8.3.
– 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 G (01-037134-083) Teamcenter 8.3 Release Bulletin 1-1

Chapter 1 Before you begin
• If you are upgrading from Engineering Process Management or an earlier

version of Teamcenter, see the following:
– Announcements of the deprecation or obsoletion of Teamcenter features.
For more information, see Deprecated feature announcements and Obsolete
feature 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.
– Release notes describing workarounds for known upgrade problems.

For more information, see Upgrade.
Also see the Upgrade Guide.
For more information about installing or upgrading Teamcenter, see the following:
• Maintenance pack and patch installation information is documented in the
Installation on UNIX and Linux Servers Guide and the Installation on Windows
Servers Guide. If you are installing a maintenance pack on to an existing
installation, see Installing Teamcenter maintenance packs, or if you are installing
a patch on to an existing installation, see Installing Teamcenter patches.
Note
You can create a new installation of Teamcenter from a maintenance pack
version. If you do so, see either the first-time installation instructions or
the upgrading instructions, whichever is appropriate for your situation.
• For general guidelines and best practices for a Teamcenter system administrator
to follow when deploying a new or upgrading an existing Teamcenter system,
see the latest available version of the Teamcenter Deployment Guide. To obtain
a copy, go to the following Web site:
http://support.ugs.com/docs/teamcenter/
Note
You must have a WebKey account to access the Web site.
1-2 Teamcenter 8.3 Release Bulletin PLM00001 G (01-037134-083)

Before you begin
Teamcenter and compatible third-party software versions

The Siemens PLM Software Certification Database
(http://support.ugs.com/online_library/certification/) documents the minimum
version of operating systems, compilers, databases, client browsers, and other
third-party software with which this product is compatible. Because Teamcenter
releases are asynchronous with the release of compatible third-party software,
Teamcenter customers can acquire and install a newer version of third-party
software before Siemens PLM Software has the opportunity to certify it.
Siemens PLM Software’s standard policy with respect to new versions of operating
systems, compilers, databases, client browsers, and other third-party software relies
on the manufacturers’ guarantees. If the manufacturer guarantees that the new
version of its product is binary-compatible with the preceding version, Siemens
PLM Software expects our products to function properly when running on the new
version. Our experience shows that virtually no problems are encountered when
executing Teamcenter with a third-party version later than the version on which
we completed our certification testing.
Siemens PLM Software will make a reasonable effort to support Teamcenter running
on a later version and to work with you to resolve any difficulty that may arise but
will not, in most cases, complete the testing required to state Teamcenter software is
certified.
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 the successive versions of their operating systems. We make a reasonable
effort to support Teamcenter running on a later version of an operating system. To
a lesser degree, operating system manufacturers provide similar assurances when
relinking or rebuilding executables and libraries with new versions of the compilers.
In cases where compatibility does not exist between old and new compiler versions,
all customization incorporated into the Teamcenter base product must be linked
using the version of the compiler with which Teamcenter has been released. This
also applies to the installation of Teamcenter patches.
To summarize, Teamcenter may run on a newer version of an operating system, but
customizations and patches may need to be compiled and linked on an earlier version.
For information about the lowest version of software with which this product runs,
see the Siemens PLM Software Certification Database. Although Teamcenter may
run using a lower level of software, keep in mind that we strongly discourage
running at lower levels and that we do not provide support to anyone doing so.
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.ugs.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.ugs.com/webkey/

Before you begin
Available Teamcenter 8.3 platforms

The following distribution images are available as part of Teamcenter 8.3:
Teamcenter 8.3 for HP Risc
Teamcenter 8.3 for HP Itanium
Teamcenter 8.3 for IBM AIX
Teamcenter 8.3 for Sun Solaris Sparc
Teamcenter 8.3 for Microsoft Windows
Teamcenter 8.3 for Linux SUSE 64
Teamcenter 8.3 for Over-the-Web installation, All Platforms
Teamcenter 8.3 Embedded Visualization, All Platforms
Teamcenter 8.3 Publications, All Platforms
Teamcenter 8.3 is supported in the following language locales on all server-supported

platforms:
Chinese Simplified
Chinese Traditional
Czech
English
French
German
Hebrew
Italian
Japanese
Korean
Russian
Spanish
Hardware, software, and disk space requirements

For information about system hardware and software requirements for Teamcenter
8.3, see the Siemens PLM Software Certification Database:
http://support.ugs.com/online_library/certification/
The following table shows the required disk space for the platforms certified by
Teamcenter.
Corporate Two-tier rich

Platform server client Web tier
Hewlett-Packard 3.0 GB Not certified 3.0 GB
HP-UX (Itanium)
Hewlett-Packard 3.0 GB Not certified 3.0 GB
HP-UX
IBM AIX 2.0 GB 450 MB 3.0 GB
SUSE Linux 2.0 GB 300 MB 3.0 GB
Sun Solaris 2.5 GB 300 MB 3.0 GB
Microsoft Windows 1.5 GB 450 MB 4.5 GB

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.htm 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.
To search the entire PDF collection, click the Search button in the Teamcenter
PDF Help Collection page. This launches Adobe Reader and loads the search index
for the collection. In the Search dialog box in Adobe Reader, type the text you
want to find.
You can view these guides using Adobe Acrobat Reader, which you can download free
from Adobe at http://www.adobe.com.
If you want to share the PDF collection on your network, copy the 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.
Note
• Viewing Adobe Acrobat files requires Adobe Acrobat Reader, which you
can download free at http://www.adobe.com. Viewing Adobe Acrobat files
within a Web browser requires the appropriate Adobe Acrobat plug-in
for your Web browser.
• If you share the Teamcenter PDF Help Collection on a Web (HTTP)

server, you cannot search the entire PDF collection. The collection search
functionality works only when you share the PDF collection from a file
system location. For collection search capability, access the PDF collection
in a Web browser using a URL with file protocol, for example:
– Local host:
file:///D://PDF/index.htm
– Network host (UNC path):

file://///host/PDF/index.htm
• If you want to open PDF files directly, browse the PDF\pdf directory
(Windows systems) or the PDF/pdf directory (UNIX/Linux systems) on
the documentation distribution media. To open the PDF collection search,
open the PDF index file, tc83.pdx, in this directory. This launches Adobe
Reader and loads the search index for the collection.

Before you begin
Using HTML files

The HTML directory on the documentation installation media contains HTML
versions of the manuals.
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
Several features of the online help system require the display of popup
windows; for example, searching the online help collection and viewing
graphics. 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.

Chapter
2 Support and certification

announcements
Deprecated feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

General deprecated feature announcements . . . . . . . . . . . . . . . . . . . . . . 2-1
Deprecated utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Deprecated ITK functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Deprecated services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Deprecated Java classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Deprecated Global Services features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Deprecated data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Deprecated Content Management data model . . . . . . . . . . . . . . . . . . 2-12
Deprecated Requirements Manager data model . . . . . . . . . . . . . . . . . 2-14
Deprecated Schedule Manager data model . . . . . . . . . . . . . . . . . . . . . 2-14
Deprecated Workflow data model . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Deprecated Workflow handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Obsolete feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

General obsolete feature announcements . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Obsolete utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Obsolete preferences and environment variables . . . . . . . . . . . . . . . . . . . 2-25
Obsolete ITK functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Obsolete Workflow handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

Chapter
2 Support and certification

announcements
Certification announcements include notices about recommended use of this version,

as well as announcements of the deprecation or obsolescence of features.
Deprecated feature announcements

As Siemens PLM Software enhances Teamcenter, some features are deprecated or
obsoleted. Deprecation identifies items that will be removed in a future version
of Teamcenter.
The following features will be no longer certified or supported in a future version
of Teamcenter.
General deprecated feature announcements

The following features are deprecated in Teamcenter 8.3.
• Deprecation of support for XML-based manufacturing reports
(First published Teamcenter 8.3)
Beginning with Teamcenter 9, manufacturing reports in the Manufacturing
Process Planner application will no longer support the option to use XML-based
reports. Only PLM XML-based reports will be supported.
PLM XML is currently the default schema; it can be overridden by modifying
the cmereport properties file as described in the Customizing reports topic of
the Report Generator Guide. If you are using this setting and have created
custom reports, you must migrate your custom style sheets to PLM XML.
• Deprecation of certification for Visio 2003 in TcPublish

Beginning with Teamcenter 9, Teamcenter Publish will no longer support
Microsoft Visio 2003. Visio 2007 and Visio 2010 (32-bit only) are certified.

Chapter 2 Support and certification announcements
• Deprecation of certification for Sun Java System Application Server

In Teamcenter 9, Sun Java System (which is being rebranded as Sun Glassfish)
will not be certified on any operating systems supported by Teamcenter 9. This
termination of certification applies to both the Glassfish Server Open Source
Edition and the commercially licensed Oracle Glassfish Server. Additionally, the
GTAC certification tables indicate that the Sun Java System is certified for
Teamcenter 2007.x and Teamcenter 8.x. This certification, however, is limited
to Windows and Solaris operating systems. Other operating system platforms
are not certified.
Following are the certifications:
– For Teamcenter 2007.1 and 2007.2, Sun Java Web Server 6.1 SP5 is
supported on Windows and Solaris.
– For Teamcenter 8.x, Sun Java System Application Server 9.1 is supported on
Windows and Solaris.
• Deprecation of headless application support

Beginning at a future Teamcenter version, use of the rich client Java libraries
(including the Java kernel APIs) will be supported only for additions and
extensions to the rich client itself. Alternative clients, such as headless
applications (whether they present a user interface or not), will be supported
only by the Teamcenter Services client libraries.
This affects all techniques described in the Write a headless application and
Writing headless programs topics, which will be removed from the Rich Client
Customization Programmer’s Guide.
For more information about Teamcenter Services, see the Services Guide.
• Deprecation of Application Integration Environment (AIE)

The Application Integration Environment (AIE) is deprecated in Teamcenter 8.2
and will no longer be supported in Teamcenter 9. Instead of AIE, the Teamcenter
Services framework must be used for integrating applications with Teamcenter.
For more information about the Teamcenter Services framework, see the
Services Guide.

Support and certification announcements
• Deprecation of certification for Microsoft Office 2003 and Teamcenter

Microsoft Office for Rich Client
Beginning at Teamcenter 9.0, the following integration options for Teamcenter
will not certify Microsoft Office 2003:
– Teamcenter’s Client for Microsoft Office
– Teamcenter Extensions for Microsoft Office
– Teamcenter Compatibility
These integrations will certify Microsoft Office 2007 and 2010.
• Legacy audit file deprecation

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)
Workflow
User administration
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 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.
• Deprecation of the Genius4000 to Resource Manager migration program

The Genius4000 to Resource Manager migration program will no longer be
delivered starting with Teamcenter 9. If you must migrate Genius4000 data
from Teamcenter 9 onwards, you must do so by installing Teamcenter 8.x (or
earlier) and migrating the data using the Genius data migration utility found in
that installation. Once the data is migrated, you can do one of the following:
– Upgrade the Teamcenter 8 database to the appropriate Teamcenter version.
– Export the migrated data and import it into the appropriate Teamcenter
version.

• Deprecation of the tc.h header file

In Teamcenter 8.1, the tc.h file is deprecated and will be removed in Teamcenter
10. 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>.
• Deprecation of global variables defined in appr.h

(First published Teamcenter 8 MP1)
The external global variables defined in the appr.h file are deprecated, and
replacement getter methods will be provided in Teamcenter 8.1. All the
customizations that require these variables must use the 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.
• Deprecation of Change Viewer

The Change Viewer application is deprecated and will be removed from
Teamcenter 10. Change Viewer is renamed Change Viewer Classic and a new
Change Manager application is added. If you are new to Teamcenter or have
not previously used Change Viewer Classic, use the new Change Manager
application.
If you used Change Viewer Classic, you have options to migrate your change
processes to Change Manager.
For more information about migrating to Change Manager, see the Migrating to
Change Manager appendix in the Change Manager Guide.
Also, if you previously used Change Viewer Classic and need to continue to use
it in the short term, two preferences are available to enable Change Viewer
Classic functionality:
Enable_Create_Classic_Change
Enable_Show_Classic_Change
To access preferences in the rich client, choose Edit→Options→Index.

For more information about these preferences, see the Preferences and
Environment Variables Reference and the Change Manager preferences appendix
in the Change Manager Guide.
Incremental change is unaffected with the following exceptions:

– Double-clicking an incremental change in My Teamcenter does not open it in

Change Viewer Classic. The Summary pane is displayed instead.
– The Send To→CM Viewer shortcut menu command is not available.
– Set the incremental change effectivity in Structure Manager instead of

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

incremental change instead of Change Viewer Classic.
• Deprecation of eIntegrator Admin application

The eIntegrator Admin application (IM12860) will be removed in Teamcenter 9.
Instead of eIntegrator Admin, use the functionality in Global Services to perform
live exchange and to map data with external databases.
• Deprecation of Report Designer

(First published Teamcenter 2007.1.5)
Siemens PLM Software announces the deprecation of the Report Designer
application. Report Designer will still be supported in Teamcenter 8, however,
support will be dropped in a future version. Customers are encouraged to use
the Report Builder application to develop reports in the future.
For more information about Report Builder, see the Report Builder Guide.
The Report Designer perspective is hidden in the rich client. If you want to
show the Report Designer perspective, remove ReportDesigner from the list of
values defined for the Hidden Perspectives preference. To access preferences
in the rich client, choose Edit→Options→Index.
For more information about this preference, see the Preferences and Environment
Variables Reference.

• Deprecation of certification for the Hewlett-Packard HP-UX operating

system on PA-RISC hardware
Certification for the HP-UX operating system on PA-RISC hardware is
deprecated. This includes all clients and servers. Hewlett-Packard announced
the deprecation of HP-UX on the PA-RISC hardware platform and is moving
server implementations to the HP-UX Integrity platform based on the Intel
Itanium2 platform. More information about HP-UX PA-RISC deprecation is
available on the Hewlett-Packard Web site:
http://h71028.www7.hp.com/ERC/downloads/4AA0-5390ENW.pdf
Certification for the HP-UX PA-RISC rich client is discontinued at Teamcenter 8.
Certification for HP-UX PA-RISC servers will be discontinued at Teamcenter 9.
The HP-UX Integrity platform is certified for Teamcenter 8 servers. See the
following site for specific operating system version certification and restrictions:
• Deprecation of rich client on UNIX-based operating systems

The Teamcenter rich client is deprecated for these operating systems:
– HP-UX on PA-RISC hardware
– Sun Solaris
– IBM AIX
Demand has decreased for Teamcenter clients on UNIX-based operating

systems. UNIX hardware vendors now concentrate on servers instead of
desktops. Certification for the HP-UX PA-RISC rich client is discontinued with
Teamcenter 8 and certification for the Solaris rich client will be discontinued
with Teamcenter 9. Certification for the rich client on AIX will continue with
Teamcenter 9, but will be discontinued in a future release beyond Teamcenter 9.
Only the Teamcenter rich client on UNIX systems is deprecated. The Teamcenter
thin client and Teamcenter server-side components on UNIX will still be certified.
Siemens PLM Software recommends using either Windows-based or SUSE
Linux-based systems for Teamcenter rich client.
See the following site for specific operating system version certification:
• Deprecation of Application Interface Web Service (AIWS)

The Teamcenter Application Interface Web Service is deprecated and will be
discontinued at Teamcenter 9. Use the AI Service provided as part of the
Teamcenter service-oriented architecture (SOA) to develop new clients with
the same application integration constructs. For more information about SOA,
see the Services Guide.

• Deprecation of schematics in Structure Manager

(First published Teamcenter 8)
The ability to view schematic diagrams in the Structure Manager viewer is
deprecated. Replacement of this functionality is targeted in a future release
based on an integration with Microsoft Visio and Teamcenter.
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 8.3.
• Deprecated Workflow utilities
The following utilities were deprecated in Teamcenter’s engineering process
management 9.1 and are obsolete in Teamcenter 8.3:
– upgrade_workflow_objects
There is no replacement utility.
– upgrade_motif_workflow_templates
There is no replacement utility.
– append_procedure
Use the plmxml_import utility instead.
• Deprecation of the generate_loadfsccache_tickets utility

The generate_loadfsccache_tickets is deprecated and is replaced by the
load_fsccache utility.
• Deprecation of the import_dfa_file utility

The import_dfa_file utility will be obsolete in Teamcenter 9. The
import_dfa_file utility corrupts data model objects managed by the Business
Modeler IDE. If you use this utility, you may corrupt the data model and the data
may become inaccurate. Use the Business Modeler IDE to create and manage
the objects that were previously managed by this 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 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
release.

Deprecated Global Services features

The following Global Services features are deprecated.
• Deprecation of the GS2GS Connector
The GS2GS connector is deprecated. The BPEL process partner links
functionality of Global Services provides the same functionality as the GS2GS
connector. Use the bundled ODE BPEL engine to accomplish the same
functionality as the GS2GS connector.
• Deprecation of the Global Services Framework – Web Services

Connector
The Teamcenter Global Services Framework – Web Services Connector is
deprecated. This connector’s functionality is replaced by the BPEL process
partner links functionality of Global Services.
The Web Services Connector will be obsolete at Teamcenter 10.
• Deprecation of the Global Services Connector

The Teamcenter 8.1 Global Services – Global Services Connector is deprecated.
This connector will be removed in a future version of Global Services. This
connector’s functionality is replaced by partner links provided through the
Teamcenter 8.1 Global Services Framework - Ode BPEL web application
solution.
• Deprecation of the Global Services BPEL engine endpoint

The BPEL 1.1 engine Global Services supplies is deprecated will be removed at
a future version. This functionality is replaced by the ODE BPEL 2.2 engine
supplied through the Teamcenter 8.1 Global Services Framework - Ode BPEL
web application solution. As a result, the following Global Services invocation
endpoint is also deprecated:
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 a future version. For the deprecation
period, the old endpoint forwards appropriately to the new endpoint.
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>

• Deprecation of the Global Services Teamcenter 2007 Rich Client

Connector
The Teamcenter 8 Global Services – Teamcenter 2007 Rich Client Connector is
deprecated. This connector will be removed in a future release of Global Services.
In most cases, you can use the Teamcenter 8 Global Services – Teamcenter 8
SOA connector in place of this connector.
• Deprecation of the Global Services Teamcenter Engineering 2005/2007

Connector
The Teamcenter 8 Global Services – Teamcenter Engineering 2005/2007
Connector is deprecated. This connector will be removed when Teamcenter
Engineering 2007 is no longer supported.
• Deprecation of the Global Services Teamcenter Engineering v9

Connector
The Teamcenter 8 Global Services – Teamcenter Engineering v9 Connector is
deprecated. This connector will be removed when Teamcenter Engineering V9
is no longer supported.
• Deprecation of the Global Services Teamcenter 8 Connector

The Teamcenter 8 Global Services – Teamcenter 8 Connector is deprecated. This
connector will be removed in a future release of Global Services.
• Deprecation of the Global Services SAP Connector

The Teamcenter 8 Global Services – SAP Connector is deprecated. This
connector will be removed in a future release of Global Services.

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 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 business objects
There is no migration planned for the following business objects; they are simply
not needed without the separate Content Management Web server. These objects
will be removed at Teamcenter 9.0.
Deprecated business object Replacement business object

DCt_CacheInd None
DCt_CntntRevwItm None
DCt_CntntRevwItmRevision None
DCt_CompPolicy None
DCt_CompPolTbl None
DCt_Permissions None
DC_PublParamTbl None
DCt_SearchCriteria None
DCt_Workspace None
• 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
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 Requirements Manager data model

The following Requirements Manager data model is deprecated.
• TraceLink class is deprecated
The TraceLink class, as extended from the ManagedRelation class, is
deprecated since Teamcenter 8.0. The class feature has been migrated to the
new trace link FND_TraceLink class under the TCRelation class. Also, a
migration utility has been provided and all trace link instances will be migrated
to new trace links during database upgrade.
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

ScheduleDeliverable SchDeliverable
TaskDeliverable SchTaskDeliverable
• Deprecated Schedule Manager properties on business objects

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 Workflow data model

The Workflow data model includes some business objects that are no longer used.
These are marked as deprecated and will be removed in Teamcenter 9.
• Deprecated Workflow business objects

EPMInheritance None
EPMTaskDefinition EPMTaskTemplate
EPMTaskStatus ReleaseStatus
OLD_EPMBRHandler EPMBRHandler
OLD_EPMBusinessRule EPMBusinessRule
OLD_EPMHandler EPMHandler
ReleaseLevel EPMReviewTask
ReleaseLevelDefinition EPMReviewTaskTemplate
RLMAccessDefinition None
SignoffList None
Deprecated Workflow handlers

The following Workflow handlers and tasks are deprecated.
• check-process-completion
The Sync task and related check-process-completion handler is deprecated
and will be obsolete in Teamcenter 10. Obtain equivalent functionality by
creating subprocesses from parent processes.
For more information, see the Workflow Designer Guide.

Obsolete feature announcements

As Siemens PLM Software enhances Teamcenter, some features are deprecated or
obsoleted. Obsolescence identifies items that are either removed from Teamcenter or
may be removed without further notice.
The following features are no longer supported in Teamcenter.
General obsolete feature announcements

The following features are obsolete in Teamcenter 8.3.
• RDVUseNewVariantModel global constant is obsolete
The RDVUseNewVariantModel global constant was deprecated in Teamcenter
2007.1 MP8 and is obsolete at Teamcenter 8.2.
• Digital Dashboard plug-in to Business Modeler IDE is obsolete

The third-party component upon which the Business Modeler IDE Digital
Dashboard plug-in is based is obsolete and is no longer available in a version
compatible with the content of Teamcenter 8.1. As a result, the plug-in has been
obsoleted and removed from the distribution.
Other log file analysis tools and scripts can be applied to log files either as
written by the Teamcenter process or after collection by the Log Manager in
the log volume.
Siemens PLM Software intends to enhance log files to use industry standard
formats in future versions of Teamcenter. This enables the use of commercial
and open source log file analysis tools.
• Image Import utility is obsolete

Support for the Image Import utility is obsolete in Teamcenter 8.1. The Image
Import utility is located on the Teamcenter installation CD-ROM in the
additional_applications folder.
• JT assembly format for import and export is obsolete

Export and import of a JT assembly format using PLM XML is obsolete and was
removed after Teamcenter 8.1. Instead, use the PLM XML format rather than
the JT assembly format. This exports and imports JT files, along with the PLM
XML file containing the item information and assembly relationships.

• Certification for SUSE Linux Enterprise Server (SLES) 9.0 is obsolete

Certification for version 9.0 of SUSE Linux Enterprise Server (SLES) is
discontinued at Teamcenter 8.1. Teamcenter will certify only version 10 SP2 and
later for both clients and servers starting with Teamcenter 8.1.
For a listing of certified platforms for Teamcenter, see the certification table
at the following URL:
• Certification for AIX 32-bit servers and clients is obsolete

Teamcenter will certify only 64-bit servers and clients on the AIX operating
system starting with Teamcenter 8.1. For a listing of certified platforms for
Teamcenter, see the certification table at the following URL:

• The AutoCopyRel and AutoRevise business object constants are now

obsolete
In Teamcenter 2007.1, the AutoCopyRel and AutoRevise business object
constants were introduced to support the requirement to automatically revise
and relate the related object during a Revise operation of an ItemRevision
business object. These two constants are now obsolete.
Beginning in Teamcenter 8, do not use the AutoCopyRel and AutoRevise
business object constants. The functionality provided by these two business
object constants are replaced by deep copy rules. In Teamcenter 8 the deep copy
rules are enhanced to support this behavior using the Relate To Latest and
Revise and Relate to Latest actions.
Keep in mind the following upgrade considerations:
– Upgrading from Engineering Process Management to Teamcenter 8
If you are upgrading from Engineering Process Management to Teamcenter
8, you do not have to do anything, since these constants were available only
in Teamcenter 2007.1.
– Upgrading from Teamcenter 2007.1 to Teamcenter 8

If you are upgrading from Teamcenter 2007.1 to Teamcenter 8, you may have
constant attachments for the AutoCopyRel and AutoRevise business
object constants. Per the new upgrade process, the customer template project
must first be upgraded in the Business Modeler IDE client before upgrading
the database. During upgrade of the customer template project in the
Business Modeler IDE client, migration utilities are written to automatically
handle converting the AutoCopyRel and AutoRevise constants to deep
copy rules. After upgrading the customer template project, the same
template is packaged and supplied during database upgrade. The database
upgrade process ensures that your AutoCopyRel and AutoRevise business
objects constants are correctly converted to deep copy rules. Therefore, the
customer upgrading from Teamcenter 2007.1 to Teamcenter 8 does not have
any other manual steps to perform. By following the standard Teamcenter
upgrade process, the system ensures that your current behavior supported
by the business objects continues to be supported by deep copy rules after
upgrade of your template and database.
For more information, see the Business Modeler IDE Guide.

• Maturity_Level preferences are obsolete

All preferences of the item-revision-business-objectMaturity_Level format (such
as DesignRevision_Maturity_Level) are replaced by the MaturityStatuses
business object constant.
In Teamcenter 2007.1, the item-revision-business-objectMaturity_Level
preference was introduced to configure maturity status for ItemRevision
objects. This preference is obsolete in Teamcenter 8 and is replaced by the
MaturityStatuses business object constant.
The capability to configure the determination of the maturity status of
an ItemRevision object is supported through the MaturityStatuses
business object constant in the Business Modeler IDE instead of the
item-revision-business-objectMaturity_Level preference.
Keep in mind the following upgrade considerations:
– Upgrading from Engineering Process Management to Teamcenter 8
No action is required because the
item-revision-business-objectMaturity_Level preference was introduced
only in Teamcenter 2007.1.
– Upgrading from Teamcenter 2007.1 to Teamcenter 8

Migration utilities are written to convert the
item-revision-business-objectMaturity_Level preferences to
MaturityStatuses business object constant attachments. If you have
preferences that use the item-revision-business-objectMaturity_Level
format, you must follow the steps to migrate these preferences as described
in the Migrate preferences to data model objects topic in the Business
Modeler IDE Guide.
As part of the steps performed prior to the upgrade process, you would
extract the preferences from your database and perform migration in
the Business Modeler IDE using the Preferences Migration wizard. After
the preference migration in the Business Modeler IDE, a file named
cleanup_preferences.txt is generated. This file must be invoked from your
custom upgrade script to remove the preferences from your database.

• Data Integration Services (DIS) Adapter

The Data Integration Services Adapter (DIS Adapter) has been completely
removed from Teamcenter. Teamcenter’s integration with the Lifecycle
Visualization viewers is now based upon a service-oriented architecture (SOA).
This new integration is installed automatically with Teamcenter and no
additional steps are required to work with visualization data in the Teamcenter
8 managed environment.
Lifecycle Visualization viewers from earlier releases are not supported by and
cannot communicate with Teamcenter 8. However, the Teamcenter 8 stand-alone
viewers can communicate with DIS-enabled servers from previous Teamcenter
releases.
• Obsolete Web tier context parameters

The following Web tier context parameters are obsolete in Teamcenter 8:
AdapterAdministrator
EnableAutoSaveLocation
FileUploadDirectory
JtCache.BatchPopulate
JtCache.BatchPopulateFirstTime
JtCache.BatchPopulateIntervalHours
JtCache.Limited.BackupIntervalMinutes
JtCache.Limited.CapacityMB
JtCache.Limited.CleanFirstTime
JtCache.Limited.CleanIntervalHours
JtCache.Limited.Enable
JtCache.Limited.Path
JtCache.Limited.SisterStatusNameList
JtCache.Limited.SisterSynchInterval
JtCache.Limited.StatusName
JtCache.Populator.BackupIntervalMinutes
JtCache.Populator.Path
JtCache.Populator.QueueName
JtCache.World.BackupIntervalMinutes
JtCache.World.CapacityMB
JtCache.World.CleanFirstTime
JtCache.World.CleanIntervalHours
JtCache.World.Enable
JtCache.World.Path
JtCache.World.PopulatorUser
JtCache.World.SisterStatusNameList
JtCache.World.SisterSynchInterval
JtCache.World.StatusName
Mask.RefSetNames.ItemRev
PasswordFile
SessionPurgeFrequency
SessionTimeout
TcEngExcludeFiles
TcEngExcludeFilesExtFromSave

TcEngExcludeObjectTypes
TcEngExcludeTypesFromSave
TcEngMetaDataStamp
TcEngProperties
VVI.DirectModel.Document
VVI.ImageView.Document
VVI.PDFView.Document
VVI.TempFolder
VVI.Vis3DLayer
VVI.VisView.Session
VVI.VisView.SessionPackage
• Obsolete live Excel export functionality

Teamcenter’s Extensions for Microsoft Office does not generate a live Excel sheet
for the Excel 2003 application. However, it continues to generate a static sheet
for Excel 2003. Users should have Excel 2007 installed to use the live feature.
• Certification for Teamcenter EMC Content Storage media type is

obsolete
Certification for the EMC-based Content Storage media type is no longer
included in Teamcenter. Backup and recovery functionality remains as a
supported capability in Teamcenter but without certification for the EMC
Content Storage media type.
The following features are impacted:
– Content Storage media type in the rich client
– Content Storage media type usage in Backup/Recovery applications

(object_backup and object_recover utilities)
– Content Storage type usage in audit logging
– EMC Business Modeler user exits
– Content Storage type integration code in the

ar_content_storage_media_api.c and ar_content_storage_media.h
files
• Obsolete bookmark launch functionality for Lifecycle Visualization

(First published Teamcenter Engineering 2005 SR1)
The legacy functionality that launches Lifecycle Visualization from the rich client
and thin client using bookmarks is obsolete. This functionality is superseded by
the functionality that launches Lifecycle Visualization using the VVI file, which
is based on the PLM XML launch mechanism and Data Integration Services
Adapter technology. The IMAN_show_open_in_pv_button preference that
enables the functionality is also removed.

• Adobe will no longer certify its SVG Viewer plug-in for Internet
Explorer
As of January 2009, Adobe will no longer certify or enhance its SVG Viewer
plug-in for Internet Explorer. Siemens PLM Software is planning to replace this
technology in the thin client, but we recommend that you continue to use it to
enable the visualization of workflow processes and supersedure part history.
• Removal of Multiple View Editor (MVE)

The Teamcenter Multiple View Editor is removed from Teamcenter 8 due to
the low customer base implementation and duplication of functionality in
Multi-Structure Manager.
• Users can no longer change a translation request priority

(First published Teamcenter 2007.1.)
Users can no longer change the priority of a submitted translation request in
the translation administrator console.
Administrators can change priorities as well as translation execution times in
the translation administrator console.
• Property rules are replaced by the property constants framework

(First published 2007.1)
Property rules are replaced with the property constants framework.
Property constants data model elements support true inheritance of every
feature of the property rule. The existing property rules data model did not
allow you to override a specific feature of the rule without also setting the other
features. Once a property rule is created, all features are set and any inherited
rule subsequently created from a higher business object in the hierarchy likely
would not pass its new feature values past this property rule to business objects
below. The new property constants provide a robust framework to support
custom overrides on every feature of the rule.
Migration utilities are incorporated in the upgrade scripts to perform migration
of all existing property rule objects in your database to the property constants
framework. The existing functions used to retrieve the property rules on the
server are deprecated.

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:

• apply_naming_rule
• 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’s lifecycle visualization mockup
installation.
• 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

• object_backup
Use the Hot Backup over FMS feature instead.
• make_datasettype
• object_recover
• migrate_action_rules_to_bmf
• migrate_alias
• migrate_complex_property_rules
• migrate_type_display_prefs
• purge_mirror_volumes
• 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_variants
• upgrade_workflow_objects

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 Index 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:

• 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
• Cfg_Att_add_props_of_form_types
• CM_default_displayed_pseudofolders
• CM_ProblemReportRevision_displayed_pseudofolders
• CM_ChangeRequestRevision_displayed_pseudofolders
• CM_ChangeNoticeRevision_displayed_pseudofolders
• CM_Cm0DevRqstRevision_displayed_pseudofolders
• DEEPCOPY_keep_name_list
• EDA_CadenceBOMOptionDefault
• EDA_GatewayCombinedBOMOptionDefault
• EDA_GatewayPcbBOMOptionDefault
• EDA_GatewaySchematicBOMOptionDefault
• EDA_GenerateViewable
• EDA_MentorBOMOptionDefault
• EDA_PadsBOMOptionDefault

• EDA_SecondaryItems
• GMS_offline_use_TcGS
This preference is for internal Siemens PLM Software use only.
• GMS_site_checkin_after_import
This preference was for internal Siemens PLM Software use only.
• 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 manual.
• ItemCreation.NoRevMasterForm
For workarounds, see the release note about this obsolete preference in the
Business Modeler IDE release notes later in this manual.
• <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
• PortalDesignContextCLRServers
Use the RDVClearanceProxyServers preference instead.
• PSE_absocc_compound_properties
• PSE_add_props_of_item_form_types
• PSE_add_props_of_rev_form_types
• PUBLISHEDOBJECT_object_extended_attrs
• QRYColumnsShowWidthPref
• QRY_display_details
• QRY_number_of_favorites
• QRY_output_options
• QUOTA_active

• QUOTA_logging_level
• QUOTA_minimum_lifetime
• QUOTA_unload_percentage
• QUOTA_unload_threshold
• <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_Security_Level
• TcSequenceIdVisible
• TC_show_open_in_pv_button
• TC_Socket_Bucket_Size
• TC_VALIDATION_MANDATORY_CHECKERS
• TC_VALIDATION_PROGRAM
• TC_validate_nfs_accessibility
• TC_vmu_version
• TC_VOLUME_ACCESS_LOG
• <type>_createprops
• <type>_DisplayProperties
• <type>_viewerprops
• View_line_display_props
• view_view_valid_occurrencetypes
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.
• Obsolete Workflow ITK functions
The following Workflow ITK functions were deprecated in Teamcenter’s
engineering process management 9.1 and are obsolete in Teamcenter 8.3.

Obsolete Workflow ITK function Replacement ITK function

CR_add_reference_objects EPM_ask_root_task and
EPM_ask_attachments
CR_add_target_objects EPM_ask_root_task and
EPM_ask_attachments
CR_ask_current_release_level EPM_ask_current_release_level_task
and EPM_ask_review_task_name
CR_ask_release_levels EPM_get_type_tasks
CR_ask_reference_objects EPM_ask_root_task and
EPM_ask_attachments
CR_ask_target_objects EPM_ask_root_task and
EPM_ask_attachments
CR_create_job EPM_create_process
CR_demote_job EPM_ask_current_release_level_task
and EPM_demote_task
CR_demote_target_objects EPM_ask_current_release_level_task
and EPM_demote_task
CR_initialize_job EPM_create_process
CR_initiate EPM_create_process
CR_promote_job EPM_ask_current_release_level_task
and EPM_promote_task
CR_promote_target_objects EPM_ask_current_release_level_task
and EPM_promote_task
CR_remove_reference_objects EPM_ask_root_task and
EPM_ask_attachments
CR_remove_target_objects EPM_ask_root_task and
EPM_ask_attachments
CR_set_decision EPM_ask_current_release_level_task
and EPM_set_decision
EPM_create_job EPM_create_process
EPM_initialize_job EPM_create_process
Obsolete Workflow handlers

The following Workflow handlers are obsolete.
• EPM-attach-item-revision-targets
This handler is replaced by the EPM-attach-related-objects handler.

Chapter
3 What’s new for Teamcenter 8.3
New Teamcenter applications and solutions . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

ADA License application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Service Planner application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
New Teamcenter documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Configuring Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Improvements to the Mapping Designer . . . . . . . . . . . . . . . . . . . . . . 3-4
Improved memory management in dispatch libraries . . . . . . . . . . . . . 3-4
Administering Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Enhanced authorized data access license control . . . . . . . . . . . . . . . . . . . 3-5
Volume allocation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Volume failover during file import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Using Teamcenter interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Adobe Illustrator interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
DesignContext in the thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Teamcenter integration with Microsoft Office Communicator . . . . . . . . . . 3-9
View/edit and checkout/checkin enhancements . . . . . . . . . . . . . . . . . . . . 3-10
Managing changes and workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Modifying active workflow processes by editing the workflow template . . . . 3-11
Importing/exporting process assignment lists (PALs) . . . . . . . . . . . . . . . . 3-12
Restricting resource pool subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Customizing the Process Template list . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Sharing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Replicating structured context objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Global Services Web Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
HTTPS support for data transfers through Global Services . . . . . . . . . . . . 3-14
Data Exchange support for standard data model transfer . . . . . . . . . . . . . 3-14
Site consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
High-speed Data Exchange enhancements . . . . . . . . . . . . . . . . . . . . . . . 3-16
Managing product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Multiple effectivities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Effectivity customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
3D snapshot (product view) preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Units converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
DesignContext performance enhancements . . . . . . . . . . . . . . . . . . . . . . . 3-19
Structure search in Multi-Structure Manager . . . . . . . . . . . . . . . . . . . . . 3-20

Managing manufacturing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Creating a 3D PDF report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Manufacturing Resource Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Creating work instructions using a standard text library . . . . . . . . . . . . . 3-22
Accountability check enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Importing manufacturing features from external systems . . . . . . . . . . . . . 3-23
Finding product views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Time analysis enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Subclass support in manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Resequencing structures ignoring PERT flow . . . . . . . . . . . . . . . . . . . . . . 3-25
Visualizing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 3-26

Base and above . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 3-26
Control the visibility state of visited parts . . . . . . . . . . . . . . . .. . . . 3-26
3D view clipping planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 3-26
Reorganized 3D viewing preferences . . . . . . . . . . . . . . . . . . . . .. . . . 3-26
Support for product views . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 3-27
Lifecycle Visualization Startup Accelerator . . . . . . . . . . . . . . . .. . . . 3-27
Viewing JT watermarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 3-27
Standard and above . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 3-27
Enhancements to simplify creating and editing 3D text markups . . . . 3-27
Professional and above . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 3-28
True Shading save support . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 3-28
Apply True Shading effects without materials . . . . . . . . . . . . . .. . . . 3-28
Managing CAE data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

Simulation tool configuration and launch output file management
enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
CAE item wizard enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Repeatable Digital Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

Cacheless search enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Structure context enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
QPL harvester enhancements for NX 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Valid overlays only enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Managing quality data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

Document Markup Language (DML) support . . . . . . . . . . . . . . . . . . . . . . 3-33
Enhanced software support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Managing Maintenance, Repair, and Overhaul data . . . . . . . . . . . . . . . . . . . . 3-34

Service planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Customizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

Setting Multi-Site export status for dataset objects . . . . . . . . . . . . . . . . . 3-35
Reorganizing the tcapps rich client plug-in . . . . . . . . . . . . . . . . . . . . . . . 3-35
New ITK method for dynamically adding pre/post actions on meta
operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Teamcenter industry solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Contract Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Automotive Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Teamcenter 8.3 Release Bulletin PLM00001 G (01-037134-083)

Chapter
3 What’s new for Teamcenter 8.3
There are many new features available in Teamcenter 8.3; you can find detailed
descriptions of these in their related functional categories.
New Teamcenter applications and solutions
New Teamcenter documentation
Configuring Teamcenter
Administering Teamcenter
Using Teamcenter interfaces
Managing changes and workflows
Sharing data
Managing product structures
Managing manufacturing data
Visualizing products
Managing CAE data
Managing Maintenance, Repair, and Overhaul data
Customizing Teamcenter
Teamcenter industry solutions

Chapter 3 What’s new for Teamcenter 8.3
New Teamcenter applications and solutions

There are new applications. For information about these new applications, see the
following topics:
• ADA License
For more information, see the Authorized Data Access License Guide.
• Service Planner
For more information, see the Service Planner Guide.
ADA License application

The new ADA License application contains some functionality that was in the
Organization application in previous versions. The new Authorized Data Access
License Guide supports this new application.
Teamcenter provides the ADA License application for administering International
Traffic in Arms Regulations (ITAR), intellectual property (IP), and exclude licenses.
The ADA License application provides enhanced control and new attributes for
these licenses.
For information about the enhancements, see Enhanced authorized data access
license control.
Service Planner application

The Service Planner application supports service planning capabilities within
Teamcenter. Service Planner is a separately licensed application that is installed as
an optional overlay on top of the standard Teamcenter product. Service Planner lets
users create and manage service plans, service requirements, work cards, activities,
and other information to support the service planning process. The new Service
Planner Guide supports this new application.
For more information about Service Planner, see the Service Planner Guide.

What’s new for Teamcenter 8.3
New Teamcenter documentation

The following describes new documentation features for Teamcenter 8.3.
• New Search button in the PDF collection.
• On the PDF Collection launch page, a new button for Search is added. Click
Search to launch Adobe Reader and load the search index for the PDF
collection. In the Search dialog box in Adobe Reader, type the text you want to
find.
Note
The Search button is available only when you access the PDF Collection
from a local drive or a network file system path. The Search button is not
available if you access the PDF Collection from a Web server.
For more information about viewing and using PDF files, see Using PDF
Files in the Release Bulletin.
• The following table lists new Teamcenter documentation deliverables in

Teamcenter 8.3.
Name Description
Authorized Data Access This guide describes ADA License, a new application
License Guide that supports International Traffic in Arms (ITAR),
intellectual property (IP), and exclude licenses that
Teamcenter uses to control access to objects that are
subject to these requirements. You use the ADA
License application to enable, disable, and perform
other configuration actions on licenses.
Service Planner Guide This guide describes Service Planner, a new
application that supports service planning capabilities
within Teamcenter. Service Planner lets users create
and manage service plans, service requirements, work
cards, activities, and other information to support the
service planning process.
Transition Guide This guide describes how to install and configure
Teamcenter Data Exchange and Teamcenter
Enterprise components and provides supported
business process descriptions.
Lifecycle Visualization This guide provides information about configuring
Integration Guide and using the Lifecycle Visualization integration with
Teamcenter.

Configuring Teamcenter
The following are new features for configuring Teamcenter 8.3.
Business Modeler IDE

The Business Modeler IDE is a tool for configuring the Teamcenter data model. The
following are new and changed Business Modeler IDE features.
Improvements to the Mapping Designer
The Mapping Designer is an application in the Business Modeler IDE that

administrators can use to map data model from one product lifecycle management
(PLM) system to another, for example, from Teamcenter Enterprise to Teamcenter.
You can perform the following new tasks in the Mapping Designer:
• Specify raw XPath language expressions in filtering conditions.
• Import factors that already exist in a project.
Improved memory management in dispatch libraries
The footprint for all dispatch libraries is reduced by removing multiple inheritance
from the dispatch class hierarchy. Because of these enhancements, the logon memory
footprint is reduced, thereby improving logon performance.
The autogenerated code templates are changed. As a result, if you have custom
server code customizations, you must regenerate the custom server code and rebuild
the custom server libraries.
Use the Business Modeler IDE to regenerate code and build libraries. To regenerate
code, in the Business Objects view, right-click the project containing the code and
choose Generate Code→C++ classes. To rebuild the libraries containing server code,
choose Project→Build Project.

Administering Teamcenter
The following are new Teamcenter administration features.
Enhanced authorized data access license control

Teamcenter provides the new ADA License application for administering
International Traffic in Arms Regulations (ITAR), intellectual property (IP), and
exclude licenses. The ADA License application provides enhanced control of data
access in the rich client for the following actions:
• Lock (also known as freeze) an unexpired license to prevent its application to
workspace objects.
• Query for and view workspace objects associated with a locked license for
licenses that have not reached their expiration date.
• Unlock and unexpire license to allow its use.
• Add users and groups to unlocked licenses that have not expired.
• Remove users and groups from licenses.
• Add subgroups to unlocked licenses that have not expired when the
ADA_enable_subgroups preference is set to true.
• Remove subgroups from licenses when the ADA_enable_subgroups preference

is set to true.
• Add qualifying Code of Federal Regulations (CFR) information to an ITAR

license.
• Query and view the license audit log that contains information about all actions
associated with a license.
• Export or print audit log data in Microsoft Excel or comma-separated values

(CSV) format.
Additionally, in My Teamcenter, you can:

• Attach an unexpired and unlocked license to a workspace object.
• Detach a license from a workspace object.
• Add Authorizing Paragraph information to an attached ITAR license.
A user with the ITAR_ADMIN, IP_ADMIN, or the new

Administer_ADA_Licenses privilege can perform administration actions in
this application. The required privilege is determined by the value of the new
ADA_license_administration_privilege site preference. The default value for
this preferences is set to ITAR_ADMIN. The ADA License application opens in edit
mode (buttons are enabled) only for the group and role combinations configured to
access the ADA License in the Authorization application. Users in other groups or
with other roles have read-only access to the application.

The following new attributes on licenses can be viewed from both the rich client
and thin client:
• lock_date (displayed as Lock Date)
• qualifying_cfr (displayed as In Accordance With)
The ear_paragraph attribute (displayed as Authorizing Paragraph) on

workspace objects can be viewed from both the rich client and thin client. If the
ITAR license attached to a workspace object exists at an importing site, the license
at the importing site is attached to the workspace object on import.
The audit log feature is enhanced to provide a record of the group of the user
performing a license related action and the details of workspace objects that have
a license attached or detach. It also includes error codes and error messages that
result when an attach or detach license action fails.
The following command line utilities have new arguments to support these
enhancements:
• ada_util
• audit_archive
For more information, see the Utilities Reference.
Volume allocation rules

Teamcenter provides volume reallocation rules with which administrators can define
volume storage criteria based on business data. The new volume reallocation rules
are defined in an XML file and managed with the new -rulesfile and -outrulesfile
arguments for the move_volume_files utility.
For example, consider a site using both CAD and JT files. Because JT files are
volatile and can be recovered from the CAD file if lost, they are on a different backup
schedule. The administrator decides to store all JT files in a different volume than
the CAD files. Rules can be written in the XML file specifying different target
volumes for the JT and CAD files. Each time the utility is run, JT and CAD files
not already stored in the respective target volume are moved to the appropriate
destination. The utility can be run manually or as a cron job.
The new volume reallocation rules do not affect any existing default volume settings
or default local volume settings.
Volume failover during file import

Teamcenter provides file import failover, allowing administrators to define a failover
volume for use when the default importing volume exceeds a specified capacity.
Configure file import failover using the new TC_Volume_Failover_Volume_Name,
TC_Volume_Failover_Trigger, and TC_Volume_Status_Resync_Interval
preferences.
For more information about configuring file import volume failover, see the System
Administration Guide.
For more information about the volume failover preferences, see the Preferences
and Environment Variables Reference.

Using Teamcenter interfaces

The following are new features for Teamcenter interfaces.
Adobe Illustrator interface

Designers in retail industries, such as Consumer Packaged Goods and Apparel,
can use Adobe Illustrator to access Teamcenter without running the Teamcenter
rich client or thin client. You can edit and create Teamcenter objects of the Adobe
Illustrator dataset type directly from Adobe Illustrator.
Caution
The Adobe Illustrator interface is not appropriate for the heavy-duty design of
parts and assemblies.
To enable the interface, you log on to Teamcenter through one or both of the following:
• A network drive mapped to a Teamcenter server URL in Windows Explorer
Note
The proxy server for the Teamcenter WebDAV service must be installed.
• Teamcenter’s Network Folders

For more information about getting started with Network Folders, see the
Network Folders Guide.
After logging on, you can:

• Open Teamcenter datasets in Adobe Illustrator from:
– Adobe Illustrator’s Open dialog box
The dialog box shows a preview of the selected dataset.
– The mapped network drive in Windows Explorer
– Teamcenter’s Network Folders
• Edit existing Adobe Illustrator datasets and save changes in Teamcenter.

• Create new datasets in Teamcenter with Adobe Illustrator’s Save As dialog box.
Note
If Network Folders is installed, additional options are available on a shortcut
menu in Network Folders, in the network drive, and in the Adobe Illustrator
Open dialog box:
• Check out datasets from Teamcenter.
• Check in datasets to Teamcenter.
• Cancel a checkout.
• Transfer a checkout to another user.
• View checkout history.
For more information about checking objects out of and into Teamcenter, see
the Network Folders Guide.
DesignContext in the thin client

The DesignContext application allows you to make fast searches for background
parts within certain filter criteria specified by the user, for example, proximity,
zone, occurrence notes, and so on.
This functionality is available in the thin client as a single page, rather than the
three-window wizard approach in the rich client.
Thin client DesignContext is targeted at consumer users. Therefore, the following
limitations are designed:
• No interoperability with any CAD system.
• No synchronization operations with Structure Manager.
• No clearanceDB integration.
• The existing implementation of ad hoc configuration (QuickLaunchToVis)

functionality in the thin client is available but supports only JT-based and
NX-based QPL search engines.
• If there are any stubbed objects found in the search results, the thin client only
displays them as stubs; it does not provide an option to import the stubbed
objects.
For more information about DesignContext in the thin client, see the Thin Client
User Interface Guide.
For more information about DesignContext in general, see Getting Started with RDV.

Teamcenter integration with Microsoft Office Communicator

Teamcenter rich client and thin client users can use Microsoft Office Communicator
to see when other users are available for instant messaging.
Teamcenter users can view the current status of the owning and last modified
users, and, from within a Teamcenter application, can initiate communication using
Microsoft Office Communicator.
This capability:
• Is supported only on Windows systems with Microsoft Office Communicator 2007.
• Lets you access all available Microsoft Office Communicator features.
• Is available in Teamcenter and is enabled and controlled by preference settings.

– The OCS_use_presence_display preference specifies whether the
functionality is integrated withTeamcenter.
– The OCS_use_email_property preference specifies whether to use the

e-mail ID from the e-mail ID field of the user Person object.
– The OCS_company_email_domain(domain) preference value specifies a

domain name if the OCS_use_email_property preference value is false.
• For the rich client, integration is implemented in:

– My Teamcenter Summary view
– My Teamcenter Viewer view
– Workflow perform-signoffs panes
– Requirements Manager
– Structure Manager
• For the thin client, integration is supported only for Microsoft Internet Explorer
and is implemented in:
– My Teamcenter Summary page
– Workflow perform-signoffs dialog boxes

Note
Microsoft Office Communicator must be installed and running on your
computer to use the Teamcenter integration with Microsoft Office
Communicator.
• If you try to use this feature when Microsoft Office Communicator is not
installed and running on your computer, Teamcenter displays the symbol
color corresponding to the Microsoft Office Communicator Presence
Unknown status.
• If you try to use the Teamcenter integration with Microsoft Office

Communicator to contact a user for whom the system cannot find an
e-mail ID, the system displays a message listing possible reasons for the
inability to continue the communication.
For information about configuring Teamcenter instant messaging with Microsoft

Office Communicator, see the Application Administration Guide.
View/edit and checkout/checkin enhancements

The following functionality is added for the rich client:
• View functionality enhancements:
– For editable objects, the Properties shortcut menu command is renamed
View Properties.
– In the View dialog box for a checked-out object, the Checkin button is
renamed to Save and checkin.
• Edit functionality enhancements:

– A Properties command is added to the Edit menu.
– For editable objects, an Edit Properties command is added to the shortcut

menu.
– In the Edit dialog box for a checked-out object, the Checkin button is
renamed to Save and checkin.
The following functionality is added for the rich client and the thin client:
• For forms, the value of the Form_double_click preference determines whether
a double-click action on a form opens it in edit mode or view mode.
For information about viewing and modifying object properties, see the Rich Client
Interface Guide.

Managing changes and workflows

The following are new Change Viewer and Workflow features.
Modifying active workflow processes by editing the workflow template

Administrators can now update all active workflows processes based on a particular
workflow template by editing the workflow template. When an administrator edits a
workflow template, and then selects the Set Stage to Available checkbox to change
its stage from Under Construction to Available, a dialog box appears in which
the administrator must indicate whether to apply the edits to all active workflow
processes based on the template. By selecting Yes in the dialog box, each active
process based on the workflow template is updated as follows:
• If the edits in the workflow template occur later in the workflow than the active
workflow process has reached, the edits are applied to the workflow.
• If the edits in the workflow template occur earlier, and the active workflow has
already passed the place where the edits were made, the edits do not take effect,
unless the task/path is re-executed using backward branching/loops or when a
task is demoted.
• If the edits in the workflow template impact an active task, the edits are applied
after the task completes and only take effect if the task is re-executed.
• If the edits delete the currently active task, the next task is started.
Updates to active workflows can be applied in real-time or in the background. Use

the background method when updating a larger number of active workflow processes.
Active workflow processes can also be updated in a similar manner when updated
versions of a workflow template is imported, either through the Workflow Designer
application or using the plmxml_import utility.
For more information, see the Utilities Reference.
This functionality is enabled by the new EPM_enable_apply_template_changes
site preference.

Importing/exporting process assignment lists (PALs)

You can now export/import process assignment lists (PALs) with PLM XML, using
the new Import and Export options in the Create/Edit Assignment List dialog box.
Exporting a PAL also exports its associated workflow template.
Importing a PAL also imports its associated workflow template. Importing a PAL
generates the following behavior:
• When the associated workflow template already exists at the importing site, the
workflow template is not imported. Only the PAL is imported and linked to the
existing workflow template.
Note
The existence of the workflow template is confirmed by whether a
template of that name exists.
• If a PAL of the same name already exists at the importing site, it is overwritten
if the Overwrite Duplicates checkbox is selected. If the checkbox is not selected,
the PAL is not imported.
• If resources assigned to the tasks within the PAL do not exist at the importing
site, the resources are not created and the task assignment is skipped in the
PAL. If none of the resources exist, the PAL is not imported.
For more information about process assignment lists, see the Rich Client Interface
Guide.
Restricting resource pool subscription

You can now restrict a users subscription access to resource pools, allowing users to
subscribe only to resource pools belonging to groups/roles of which they are a member,
using the new EPM_resource_pool_restrict_subscription site preference.
Note
This preference setting is not asserted retroactively.
For example, in a situation where the setting is OFF and users have
subscribed to resource pools of which they are not members, changing the
setting to ON does not remove the existing subscriptions. Only future
subscriptions are restricted.

Customizing the Process Template list

You can create custom filtering of the Process Template list in Workflow Designer
by writing your own code. Use the applytemplatefilter extension point (stored in
the com.teamcenter.rac.tcapps plug-in) to define customized workflow template
filtering. The custom filtering runs on top of the shipped workflow template filtering
functionality.
Customization with the new extension point allows for advanced workflow template
filtering based on object class, object attributes, and/or the status applied to the
target object.
For more information, see the Rich Client Customization Programmer’s Guide.
Sharing data
The following are new data sharing features.
Replicating structured context objects

Teamcenter allows you to control replication of a structure context
object (SCO) on release of assembly through a new workflow handler
(OBJIO-release-and-replicate). This feature uses PLM XML, Dispatcher, and
Multi-Site Collaboration functionality together to replicate released assemblies
to participating sites. The participant sites form defines the sites that receive
the replicated SCO and stores them in the Teamcenter database. A translator
produces the PLM XML output for the SCO that lists all component item revisions
in the SCO. Multi-Site Collaboration uses the list to identify and import required
item revisions on the importing site. You can control what is replicated using the
TC_assembly_xml_relation and TC_replication_exclude_types preferences.
The existing data_share utility, used in context of the Dispatcher Framework
(replicateplmxml, plmxmlbasedsync and importobjects translators) provides
the SCO replication functionality.
For more information about SCOs enhancements, see Structure context
enhancements.
For more information about controlled replication of SCOs, see the Multi-Site
Collaboration Guide, Preferences and Environment Variables Reference, and Utilities
Reference.

Global Services Web Manager

Global Services provides Web browser base interface that allows you to configure
connectors, site mapping, data mapping, and security services in your Data
Exchange environment. It also provides information about the current configuration
include File Management System (FMS) configuration. This interface is available
from the Configuration menu at the top of the Global Services Web portal.
Using this interface, you can update or add configuration files to the Global Services
data store. It eliminates the need to download, manually edit, and upload many
of the Global Services data store files. It also provides the proper elements and
attributes for the configuration parameters, eliminating the possibility of errors
when entering tags manually. If a value for a parameter must match a parameter in
another configuration file, both files are updated from the single entry that prevents
errors in the matching parameters.
You can access help for the individual panes of the interface online through the
Web browser.
For more information about Global Services Web Manager, see the Global Services
Configuration Guide.
HTTPS support for data transfers through Global Services

Teamcenter provides support for secure data exchange between Teamcenter systems
using Teamcenter Global Services, when these systems are configured for one-way
SSL HTTPS communication. The Teamcenter products include Teamcenter and
Teamcenter Enterprise.
For more information about Global Services SSL support, see the Web Application
Deployment Guide.
Data Exchange support for standard data model transfer

Teamcenter Global Services provides generic import and export framework using
TC XML and provides support, through closure rules, for the complete Teamcenter
standard (out-of-the-box) data model with the following limitations:
• Non-POM objects and classes cannot be imported.
• Nonpersistent objects and classes cannot be imported.
• Run-time properties cannot be imported.
• Administrative objects are not imported but are referenced.
This allows Global Services to transfer any metamodel compliant class. Any custom
classes that are metamodel compliant and are complete (provide a complete TC XML
export file) are supported for Data Exchange transfers.
For more information about Global Services transfers, see the Data Exchange Guide.

Site consolidation
Site consolidation is the process used by an enterprise to reduce the number of
Teamcenter sites supported by that enterprise. A typical large enterprise may
reduce a dozen sites to one or two sites.
Site consolidation is a process organized in three phases:
• Preparation
The preparation phase involves data collection, in-depth analysis, and specific
readiness steps to ensure site definition, product, and volume data is ready
for consolidation.
Note
The preparation phase can take several weeks or months.
• Execution
The execution phase consists of multiple increments based on the business
drivers for the consolidation activity.
• Cleanup
The cleanup phase involves the final cleanup, retirement, and, optionally,
decommissioning of the source site, including activities such as volume data
relocation, ownership conflict resolution, and Object Directory Service (ODS)
configuration/cleanup.
All involved sites (source, target, and third sites) must be operating at the
same appropriately licensed Teamcenter version level, which includes the site
consolidation tools. The involved third sites are those that have shared Teamcenter
data with the source site. You can determine these using the Multi-Site Assistant
(MSA) sharing profile analysis. The site consolidation tools must be run at these
sites during the cleanup phase.
For information about site consolidation, see the Teamcenter Site Consolidation
Guide, which is available through the Global Technical Access Center (GTAC).
For more information about Global Services transfers, see the Data Exchange Guide.

High-speed Data Exchange enhancements

Teamcenter provides enhanced Data Exchange transfer performance for Teamcenter
and Teamcenter Enterprise sites:
• Parallel transfer transactions
Teamcenter products participating in a Data Exchange environment support
parallel transfer transactions (swarming) between two PLM systems. A transfer
transaction is divided into smaller subtransaction containing chunks of related
data objects (islands). These subtransactions are executed simultaneously by
separate processes to decreases the total time for the transaction to complete.
The chunk size and number or subtransactions are configurable to allow you to
optimize the performance of your systems. The subtransactions are orchestrated
and monitored by Global Services.
• Enterprise connection throttling

You can configure the maximum number of connections to a specific Teamcenter
Enterprise site. This prevents the number of Global Services connections to the
Teamcenter Enterprise from degrading transfer performance.
• Flip-the-switch ownership transfer

Teamcenter provides a mechanism to execute a bulk ownership transfer of
replicated objects from the owning site to a site participating in your Data
Exchange environment that contains replicas. This is accomplished by creating
a Switch object that groups objects in a reference transfer, allowing the objects
ownership to be transferred in bulk at a later time.
• Inheritance-based standard maps

The Mapping Designer supports inheritance-based factors in all Teamcenter
supplied (COTS) maps. This allows you to extend the standard (out-of-the-box)
map projects to support your custom attributes and classes by adding new
factors instead of editing existing mapping factors.
• Site consolidation support for parallel transfers

Site consolidation transfers support swarming in a Data Exchange environment
as described previously.
For information about site consolidation, see the Teamcenter Site Consolidation
Guide, which is available through the Global Technical Access Center (GTAC).
For more information about Data Exchange transfers, see the Transition Guide.

Managing product structures

The following are new product structure features.
Multiple effectivities
Teamcenter allows you to configure product structure occurrences of an assembly
based on specified multiple end items and the unit effectivity ranges for each of those
end items. This enhancement allows you to perform impact analysis more quickly; it
eliminates the duplicate work required to maintain different product structures and
complicated manual reconciliation. In previous versions, you could only configure
a product structure to a single end item and a unit number against the end item.
A combination of multiple end items and range of units for each end item used to
configure product structure occurrences is referred to as a multi-unit configuration.
This enhancement allows you to:
• Specify multi-unit configurations and save them as effectivity groups in the
database.
• Save a combination of effectivity groups and revision rule as a configuration

context. You can use the saved configuration context to apply the effectivity
groups and revision rule to configure occurrences.
• View the configured structure in Lifecycle Visualization, CAD programs, and the
embedded viewers of appropriate rich client applications.
• Configure occurrences by matching the occurrence effectivity with the multi-unit

configuration.
• Configure occurrences that are added and deleted by incremental changes by

matching the incremental change effectivity with the multi unit configuration.
Multi-unit configuration does not support the following features:

• Revision configuration, with or without revision effectivity
• Nested effectivity
• Date-based effectivity configuration
• Appearance or occurrence group configuration
• Editing forms, notes, find numbers, and other nonoccurrence data in the context
of incremental changes
• Viewing or editing of the configured product structure in the thin client
• Viewing matching range information for configured occurrences
• Tracking changes to the occurrence order number property on the BOM line
with redlining

You can access this enhancement in My Teamcenter, Structure Manager,

Multi-Structure Manager, and Manufacturing Process Planner.
For more information about multiple effectivities and multi-unit configuration, see
the Structure Manager Guide.
Effectivity customization
You can customize Teamcenter’s behavior when the user applies or sets occurrence
effectivity (sometimes called structure effectivity) on a BOM line.
To allow customization of the behavior when setting effectivity on an occurrence,
the bl_occ_effectivity BOM line property is modifiable, and a setter method is
provided on this property. Use the setter method of the property to attach an
extension point if required.
The CFMOccEffMode preference must be set to upgrade or maintenance to
use this enhancement, not to legacy.
For more information about how to define a setter method for attaching extension
points to a run-time BOM line property, see the Business Modeler IDE Guide.
3D snapshot (product view) preview

The following enhancements are made to the preview and interpretation of product
views (3D snapshots):
• You can optionally create a high-quality 2D image of each product view and use
it in the product view gallery instead of a thumbnail image. This high-quality
image allows you to analyze the content of the product view without needing to
open it.
Depending on the setting of the Business Modeler IDE VisPVImageCapture
constant, Teamcenter can silently create the 2D image each time a product view
is created or updated. Alternatively, you can manually create 2D images when
required. This enhancement may also be deselected if you want to continue to
use thumbnails in the product view gallery.
You can define a standard size, resolution, and file format for all 2D images in
the product view properties file. Alternatively, you can manually enter those
parameters each time you create or update a product view.
• A shortcut menu command allows you to display the product structure

configuration applied when the product view was created, including the revision
rule and variant rule.
Find these enhancements in the product view gallery of Structure Manager,

Multi-Structure Manager, Manufacturing Process Planner and Part Planner.
For more information, see the Structure Manager Guide.

Units converter
A unit converter dialog box in Structure Manager allows you to optionally specify
a quantity for a product structure (BOM) line in a user-defined unit of measure
(UOM). For example, the default UOM for the item may be kg (kilograms) but you
want to view the specified value in lbs (pounds).
To enable this feature, the administrator must set the
Fnd0PSEQtyConversionDSName and Fnd0PSEEnableQtyConversionUOM
Business Modeler IDE constants and create an XML file specifying all the UOM
conversion rules that are valid at your site.
For more information, see the Structure Manager Guide and the Application
DesignContext performance enhancements

The configure to load enhancement allows you to optionally load only those BOM
lines that are configured by the selected variant rule. This feature allows quicker
loading of large structures if you are not interested in lines that are unconfigured
by the variant rule.
In this mode, you can use the Structure Manager View→Enable Filtering
Unconfigured due to Classic Variants menu command to enable the configure to
load feature. When the feature is enabled, the Variant Rule dialog box shows a check
box indicating if the current BOM window is in configure to load mode. When you
click the OK or Apply button on this dialog box, the BOM window is in configured
according to the current selection of the dialog box. If you change the selection, it
applies only to subsequent expansions. The View→Show Unconfigured Variants
command is also disabled.
If you do not enable this mode, all lines are loaded including those unconfigured by
the current variant rule. This is the default behaviour and most suitable when
you are interested in viewing lines that are unconfigured due to variants lines as
well as configured lines.
This enhancement is available only if you configure structures with classic variants
and have implemented the new variant model.
Enable or disable the configure to load feature with the
PSEEnableFilteringUnconfigdDueToClassicVariantsPref preference; use
the ConfigureToLoadEnableDefaultVariantConfig preference to enable or
disable the Filter unconfigured BOM lines due to Classic Variants check box in
the variant configuration dialog box.
For more information, see the Structure Manager Guide.

Structure search in Multi-Structure Manager

You can search very large structures without the need to previously load them.
The search is done efficiently, in the background, and only relevant results are
reported back to you. Teamcenter displays results of the search as a list of matching
structure lines in a new view called the Structure Search view. When you select an
entry, Teamcenter highlights the structure lines in the structure tree and in the
embedded viewer.
You can perform a search based on objects, forms, occurrences, and classification
attributes. Search can also include spatial information. A spatial search allows
you to enter search criteria as numerical values or by dragging a search box in the
assembly viewer to find those objects that are within these spatial boundaries.
You can combine different types of searches, such as a spatial search with an
attribute search, to further refine the search.
For more information about using the Structure Search view, see the Multi-Structure
Manager Guide.
Managing manufacturing data

The following are new features for managing manufacturing data.
Creating a 3D PDF report

To assist you in creating work instructions, you can generate a 3D PDF report that is
based on a template that an administrator creates with Adobe Live Cycle Designer.
By default, Teamcenter delivers a template that includes:
• Assembly steps (operation list)
• Description (displayed according to the assembly step selected from the list
of assembly steps)
• Consumed parts (displayed according to the assembly step selected from the
list of assembly steps)
• Assigned tools (displayed according to the assembly step selected from the list
of assembly steps)
• Graphical window that displays 3D data with all the graphical capabilities such
as zoom, rotate, pan, and animation

• Toolbar that includes:

– Mouse functions (such as rotate or zoom)
– List of views (snapshots) available
– Toggle mode tree button
– Render mode
– Lighting
The toolbar is common to all reports.
You can modify this template or create a new one to reflect your needs.
The 3D PDF report is a monolithic file that can easily be viewed on any desktop that
has the free Acrobat Reader installed. The report is rich with dynamic views and
3D data and is, therefore, self-explanatory and can reduce errors. You can use it to
fulfil various needs from basic collaboration between different departments to shop
floor work instructions.
Find this preview feature in the Manufacturing Process Planner. This feature will
become productive in Teamcenter 9.0.
For more information, see the Documentation Release Notes in the Teamcenter 8.3
Release Bulletin.
Manufacturing Resource Library

The Manufacturing Resource Library is a collection of tools and resources that are
based on DIN 4000 and DIN 4003 standards. You can import this library into
Resource Manager and use these tools in the CAM integration. This library offers:
• A classification hierarchy with new tool types.
• An open structure for vendor catalogs.
• Up-to-date graphic macros and part family templates to easily create graphics
of your tools.
• Coordinate systems within the part family templates to allow for mating.
• An NX Library event handler for tool access from NX.
For more information about installing this library, see the Installation on Windows
Servers Guide.

Creating work instructions using a standard text library

You can use standard text functionality to create work instructions. The work
instructions are associated with operations or processes in the Manufacturing
Process Planner process structure. The benefits of standard text are:
• Standardization and consistency of work instructions throughout the entire
organization.
• Content management through the ability to write once only and reuse the same
text many times.
• Easy maintenance of up-to-date work instructions when products are

upgraded—make a single change in a procedure and propagate the change
through all the relevant documents.
Typically, there are three roles involved in creating work instruction documents.
Administrator Responsible for creating and maintaining standard text and
work instruction templates.
Librarian Responsible for creating and managing standard text, folders,
and libraries. Librarians author standard text as generic
elements to reuse in varying contexts.
Planner or engineer Responsible for creating work instructions comprised of
standard text as building blocks and additional text, graphics,
and symbols, as required.
Teamcenter offers you two new views to create the standard text and author work
instructions. Both these views use Microsoft Word 2007 SP2 as their text editor.
• Standard Text view
This interface enables users (typically the librarian) to create standard text
comprised of short text segments and symbols that a manufacturing engineer
later uses as building blocks for work instructions. Using the standard text
editor, you can edit text, symbols, data, and graphics, as necessary.
• Work Instruction view

This interface enables users (typically the manufacturing engineer) to author
work instructions and to associate them with a process or operation. Using the
work instruction editor, you can insert standard text (following a search of the
standard text library for the appropriate segments), text, data, and graphics, as
necessary. You can also define data collection elements in the work instructions
to be filled in by the workshop operator using the manufacturing execution
system (MES), capturing the as-built data.
Standard text features are installed as part of the Teamcenter client installation.
The administrator must import various templates before you can use the standard
text feature. The administrator can edit these templates or create alternative
templates according to the requirements of your organization.
For more information, see the Manufacturing Process Planner Guide.

Accountability check enhancements

The accountability check is one of the tools used to help align or reconcile two
structures. You can use it, for example, to check that all parts in the EBOM are
assigned to the MBOM and can configure it to check for the alignment of specific
object attributes. You can also use the accountability check to compare such
structures as product-to-process or process-to-process.
The following enhancements have been introduced for the accountability check:
• You can now filter out (based on closure rules) objects in a structure that are not
of interest in an accountability check. You can filter based on:
– Object type, occurrence type, or attribute.
– Level – all levels below a defined level in the structure are excluded from
the scope of the check.
• Teamcenter automatically expands the structure using closure rules so that

you do not have to do this manually.
• The accountability check can compare net occurrence effectivity.
• An Accountability Check view that displays the results of the accountability

check. This view allows you to show any combination of results (for example,
only partial match, or partial match and effectivity match) in a compact manner.
You can also select colored lines in the view and they are automatically selected
in the source or target structure. Many standard view capabilities are available
in the Accountability Check view, such as adding columns to the view tables.
Find these enhancements to the accountability check in Manufacturing Process

Planner only.
For more information about using the accountability check, see the Manufacturing
Process Planner Guide.
Importing manufacturing features from external systems

To assist you with managing and processing weld points and datums during the
rough planning stages of the body-in-white process, you can import a list of weld
points and datums from an external CAD system in Manufacturing Process Planner.
The import is carried out using PLM XML. After the import, you can view connected
parts or manage the weld points in the Manufacturing Features View.
Note
Currently, the Manufacturing Features View supports weld points only.
Datums will be supported in a future version.
For more information about importing these features, see the Manufacturing Process
Planner Guide.

Finding product views

After creating product views, there are many situations that may require finding
all product views associated with a particular part so that you can easily update
them. For example:
• A part in the original product structure may be replaced by another part. You
must then update all product views containing the replaced part.
• A part’s geometry or transformation data may change.
• A part may be removed from the product structure.
• A part may be moved from one operation to another or from one subassembly to
another.
• You may want to re-create a product view based on an existing one.
The Find Product Views menu command helps you to quickly find all the required
product views. Find this command in Manufacturing Process Planner.
For more information, see the Manufacturing Process Planner Guide.
Time analysis enhancements

The Time pane in Manufacturing Process Planner assists you in time analysis for
your processes, operations, and activities. The following enhancements are made:
• You can now populate the allocated time of a process based on its calculated time
(that is, its allocated time from lower level). When populating, you can select a
start level in the structure from which this calculation begins.
• When critical path mode is turned on, you can display the length of the critical
path.
• The Populate Allocated Time dialog box is enhanced to allow you to:
– Populate by a list of time properties that you can prioritize.
– Populate up to a specified level.
– Populate zero values.
For more information about analyzing time, see the Manufacturing Process Planner
Guide.

Subclass support in manufacturing

Teamcenter now supports subclasses when creating the following objects:
• Activities
• Occurrence groups
• Structure contexts
• Collaboration contexts
• Configuration contexts
This allows you to add a new mandatory attribute to one of these business objects
in Business Modeler IDE, and then see this attribute in the New dialog box when
creating the object in Teamcenter.
When you create any new object of the type listed, you can select from all subclasses
of that object that have been created in Business Modeler IDE from within a newly
designed New xxx dialog box.
Find the new dialog boxes within the manufacturing applications, as well as in
applications that support collaboration contexts such as Multi-Structure Manager
and My Teamcenter.
Caution
Teamcenter uses the legacy New dialog boxes for creating occurrence
groups and configuration contexts. These do not show additional attributes.
Therefore, if you define a mandatory field for a subclass of these, you must
also define a default value or Teamcenter cannot generate the object.
Resequencing structures ignoring PERT flow

When you add an object to the process structure, you often need to add it between
existing objects. You can do this by giving the new object a find number that falls
between the existing objects. When the existing objects have no number space
between them, you need to resequence the structure. For example, you have the
existing numbers 11,12,13 and must change these to 10,20,30. You can now do
this without using PERT flows.
Find this feature in Manufacturing Process Planner and Part Planner.
For more information about using this feature, see the Manufacturing Process
Planner Guide or the Part Planner Guide.

Visualizing products
Teamcenter’s lifecycle visualization includes the following new features and
enhancements. The following descriptions are categorized by product configuration.
Base and above

The following new features are included in the Base product configuration.
Control the visibility state of visited parts

Two new 3D viewing features give you greater control over the visibility state of
visited parts: Visited On and Invert Visited. These features replace the Loaded
On option from earlier releases.
The concept of visited parts is slightly different from that of loaded parts. Visited
parts are parts that you have explicitly made visible during the current work
session. Loaded parts are parts that have been loaded by the application yet not
necessarily displayed.
You can use the Visited On feature to display all of the parts that you have made
visible at any point during the session.
You can use the Invert Visited feature to simultaneously hide all visited parts that
are currently displayed and show all visited parts that are currently turned off.
This feature is similar to the Reverse Blank All option available in the Teamcenter
Structure Manager, Multi-Structure Manager, and Manufacturing Process Planner
embedded viewers.
For more information on display options for 3D models, see Working with 3D Models.
3D view clipping planes

You can add a near and a far clipping plane to the 3D Viewing window. Interactive
controls enable you to manipulate the position of the clipping planes to reveal hidden
portions of 3D models, such as different locations on a factory floor or within a ship
assembly.
For more information on clipping the 3D Viewing window, see Working with 3D
Models.
Reorganized 3D viewing preferences

The 3D viewing preferences are reorganized for greater usability.
The Perspective Field of View options previously located on the General page of the
Preferences dialog box are moved to the View Clipping dialog box, which you can
access via the View Clipping button on the 3D Standard Views toolbar.
The Window preferences previously located on the Display page of the Preferences
dialog box are moved to the General page.
To display the 3D viewing preferences, right-click an empty area of the viewing
window and select Preferences or choose View→Preferences.
For more information on 3D viewing preferences, see Working with 3D Models.

Support for product views
You can now browse and find product views in applications that support them,
including the rich client and the thin client, and then open them in the stand-alone
application viewer or the Lifecycle Viewer. The product view is automatically
converted into a standard visualization snapshot so that it can be modified in that
application.
For more information on opening product views in the stand-alone application viewer
or the Lifecycle Viewer, see the Lifecycle Visualization Integration Guide.
Lifecycle Visualization Startup Accelerator
You can speed up the initial start of Teamcenter viewers on Windows. Teamcenter
Visualization Startup Accelerator is a small Windows application that pre-loads
key visualization dynamic link libraries (DLLs) when you start your computer.
Installing Startup Accelerator is an option when you install Teamcenter 8.3. If
the application is installed, a Startup Accelerator icon appears in the Windows
taskbar notification area.
For more information on using the Startup Accelerator, see Getting Started with
Product Visualization.
Viewing JT watermarks
JT files now support watermarks, which are typically used to protect proprietary
content. Watermarks can consist of images, text, or both.
For more information about viewing watermarks, see Working with 3D Models.
Standard and above

The following new feature is included in the Standard product configuration.
Enhancements to simplify creating and editing 3D text markups

There are now Basic and Advanced modes for creating and editing 3D text markups
in the Markup Text and Edit Text dialog boxes. In both modes, you can type and
edit directly in the text window. Basic mode has a simple user interface and is
recommended for most text markups. Switching to Advanced mode is recommended
for adding callouts, part names, and metadata attributes. You can switch between
Basic and Advance at any time.
For more information about creating 3D markups, see Working with 3D Models.

Professional and above

The following new features are included in the Professional product configuration.
True Shading save support
You can now use 3D snapshots, session files, and PLM XML to save and restore all of
the True Shading settings, including occurrence specific material assignments.
For more information about True Shading, see Working with 3D Models.
Apply True Shading effects without materials
You can now turn True Shading material settings and global reflections on or off
independently of other effects. For example, you can retain the original appearance
of your model while displaying a floor shadow.
For more information about controlling the display of True Shading materials, see
Working with 3D Models.

Managing CAE data

The following new features are included for managing CAE data.
Simulation tool configuration and launch output file management

enhancements
The management of output files resulting from a simulation tool launch is enhanced
to allow more flexible placement of the output files into datasets attached to
related item revisions and to provide more control over the naming of items,
item revisions, and datasets that are created through this mechanism. The
simulation administrator can use these additional configuration options from the
Edit→Configure Simulation Tools menu command in CAE Manager. The user sees
the impact of these additional configuration options when launching simulation tools
using the Tools→Launch Simulation Tool menu command in CAE Manager.
For more information about these enhancements, see the Teamcenter for Simulation
Guide.
CAE item wizard enhancements

Teamcenter provides the capability to declare object properties in the
CreateDescriptor tab in the Business Modeler IDE. These properties are exposed
at the time these objects are created in the rich client. Teamcenter for Simulation
provides a specialized wizard for creating items and item revisions that are subtypes
of CAEItem. This wizard exposes properties of these subtypes of items that are
declared in the CreateDescriptor tab. In addition, this wizard provides steps
for establishing certain references to other item revisions by leveraging CAE
relationship types. When this wizard is called from CAE Manager, the wizard
presents logical defaults for these references based on what item revisions are
currently selected and/or loaded in CAE Manager.
For more information about these enhancements, see the Teamcenter for Simulation
Guide.

Repeatable Digital Validation

Repeatable Digital Validation (RDV) automates some of the design and modeling
activities that occur during the development of a product. The RDV tools allow you
to accurately model specific product assembly configurations and use the results
with analytical and visualization tools to facilitate learning and decision making.
Cacheless search enhancements

The following enhancements are made to the cacheless (quick spatial) search
mechanism:
• Plane zone searches may be performed in the DesignContext application. You
can query for BOM lines that are above, below, or intersect with a specified
criterion plane.
For more information, see the DesignContext Guide.
• Classification searches may be combined with cacheless spatial searches in the

DesignContext and Structure Manager applications.
For more information, see the DesignContext Guide and Structure Manager
Guide.
• You can use the create_or_update_bbox_and tso utility to query NX datasets

for bounding box data. This utility may now be used in two translation modes:
– NXBBOXFORM
Queries for all NX datasets in the database that have no UGPART-BBOX
form.
– NXBBOXTOBOX
Queries for all NX datasets in the database that have no bounding box data.
You can also delete all boxes associated with an assembly.

For more information, see the Utilities Reference Guide.
• The qsearch_process_queue utility allows you to query or update the queue

of spatial search updates. You can list the queue entries, process entries, or
clear the queue. You can also list, clear, or check index boxes for all objects or
selected objects.
For more information, see the Utilities Reference Guide.
• The QS_MAX_QUERY_EXECUTION_TIME_FOR_BOTTOMUP preference

allows you to set a maximum time for each query to execute and return results.
For more information, see the Preferences and Environment Variables Reference
Guide.

• Additional SOA services:

– isSpatialSearchAvailable
Checks the availability of spatial data for the assembly of a specified top item.
– getAssemblyBoundingBox
Gets the bounding boxes for specified items.
For more information, see the Services Guide.
• The cacheless search mechanism may switch from a bottom-up traversal of the
database (the default mode) to top-down traversal after a predefined interval, if
it identifies that this action may provide results more quickly.
Note
Top-down traversal may not provide results more quickly than bottom-up,
depending on your data.
• Teamcenter ceases to process spatial indexes if it detects that the current spatial
index volume encompasses the latest bounding box volumes. If it detects a
significant change in volume, it updates the spatial indexes.

Structure context enhancements

Structure context objects (SCOs) can be used to store the recipe of virtual product
context configurations in the Teamcenter database. The following enhancements are
made to SCOs created for this purpose:
• Valid overlays only (VOO) and TruShape search (TSS) data is stored in the SCO.
The DesignContext user interface is modified to support these enhancements.
• SCOs can be replicated at remote sites using Multi-Site Collaboration. The

start_sco_dispatcher utility is added and the rdv_context_download
utility is modified to provide this capability. In addition, the queryscos,
rdvcontextdbdownload, and rdvcontextnondbdownload translators
supporting this capability can be installed with Teamcenter Environment
Manager (TEM).
• The PLM XML data generated for a SCO contains the item ID, revision ID,
last modified date, item type, and owning site of the product context. Any
additional user attributes may be passed as an additional argument to the
start_sco_dispatcher utility.
These enhancements permit specific portions of a vehicle program to be shared

between responsible sites in a controlled manner.
For more information, see Getting Started with RDV and the DesignContext Guide.
QPL harvester enhancements for NX 6.0

NX 6.0 and later versions are not supported on Sun Solaris platforms,
only on Microsoft Windows. The surfacing steps of the QPL harvester
process are enhanced to run on any platform, including Microsoft Windows
systems; other steps in the process are run on Sun Solaris, as before. The
UGII_USE_NEW_SURFACE_FILE_FORMAT environment variable must be set
to TRUE on the client to use this enhancement. The NX Load Smart Lightweight
Data customer default must be disabled.
Note
This enhancement does not affected the harvesting of data from sources other
than NX.
For more information, see Getting Started with RDV.
Valid overlays only enhancement

If you implement the cacheless search engine, valid overlays only (VOO) filters are
now applied to the search results before they are returned to the DesignContext
application. As a result of this enhancement, Teamcenter no longer creates BOM
lines that do not match the specified VOO criteria, resulting in a faster display of
search results. The DesignContext application no longer displays a dialog box listing
the lines that were removed from the search results because they did not match
the VOO criteria.
For more information, see Getting Started with RDV and the DesignContext Guide.

Managing quality data

Dimensional Planning and Validation (DPV) is a quality management solution
you can easily integrate into your Teamcenter environment. DPV enables the
extended enterprise to collect, manage, dimensionally analyze, and report on quality
measurement information. The following are new DPV features.
Document Markup Language (DML) support

DPV now supports measurement data in DML format, including creating features
and parsing scripts.
For more information, see Dimensional Planning and Validation Administration
Guide.
Enhanced software support

DPV now supports Oracle 11 and Microsoft SQL Server 2008 R2.
For more information on system requirements, see the Dimensional Planning and
Validation Administration Guide.

Managing Maintenance, Repair, and Overhaul data

The following new application is available for managing Maintenance, Repair, and
Overhaul data.
Service planning
The Service Planner application supports service planning capabilities within
Teamcenter. Service Planner is a separately licensed application that is installed as
an optional overlay on top of the standard Teamcenter product. Service Planner lets
users create and manage service plans, service requirements, work cards, activities,
and other information to support the service planning process.
You can use Service Planner to:
• Create and manage service plans for a neutral product.
• Create service partitions within a service plan to organize service requirements.
• Create and manage service requirements to define the maintenance that can be
performed on a product.
• Create service requirements to address particular fault codes.
• Define frequencies for service requirements to determine when the work needs
to be done.
• Set up dependencies or relations between service requirements.
• Define applicability between service requirements and neutral parts.
• Create and manage work cards to determine how the work needs to be done.
• Manage the work process flow by sequencing work cards to be done in a

particular order or determine work that can be done in parallel.
• Create and manage activities that provide more detailed information about
the planned work.
• Create characteristic definitions and attach them to neutral parts, work cards, or
activities to define data that should be recorded as part of the maintenance.
• Define the particular skill level needed to perform or sign off the service work.
• Define any expendable materials or tools needed to perform the service work.
• Create notices and attach them to work cards or activities to provide additional
information, such as any notes, warnings, or cautions related to the planned
work.

• Manage the time estimates for the planned work.
• Create and manage the work instructions.
• Import and export Service Planner data in PLM XML format.
• Manage Service Planner data in a Multi-Site Collaboration environment.
For more information about Service Planner, see the Service Planner Guide.
Customizing Teamcenter
The following are new Teamcenter customization features.
Setting Multi-Site export status for dataset objects

You can override the USER_is_dataset_exportable user exit to confirm export
status for dataset objects using Multi-Site Collaboration. The user exit accepts
input parameters such as the dataset object tag and target site. Using these input
parameters, custom code can return the decision whether to export the dataset. You
must use standard user exit implementation to work with the user exit.
For more information, see the Server Customization Programmer’s Guide.
Reorganizing the tcapps rich client plug-in

The code files for the rich client applications are held in the
TC_ROOT\portal\plugins directory. The primary plug-in file is the
com.teamcenter.rac.tcapps plug-in.
The code files for applications that are in the com.teamcenter.rac.cme.*
package are moved from the com.teamcenter.rac.tcapps plug-in to the
com.teamcenter.rac.cme.legacy plug-in. The affected applications include
Manufacturing Process Planner, Multi-Structure Manager, Plant Designer, Part
Planner, and Resource Manager.
Moving these files reduces the size of the com.teamcenter.rac.tcapps plug-in.
For more information about rich client customizations, see the Rich Client
Customization Programmer’s Guide.

New ITK method for dynamically adding pre/post actions on meta

operations
The METHOD_attach_action ITK method allows you to add pre/post
customizations dynamically (programmatically) on meta business object operations.
(These operations are under the Operations tab of a business object in the Business
Modeler IDE.) This ITK method should not be used for any legacy business object
operations (because legacy business object operations use existing ITK methods).
This is not intended for any property operations.
Note
Use the Business Modeler IDE to add any pre/post customization on any
operation whenever possible.
Following is sample code depicting the use of the ITK method. In this example a
post extension is added. (Note that for the post_condition_handler item, the
enum value is 3.)
METHOD_id_t method;
method.id = 0;
METHOD_attach_action("Item", "finalizeCreateInput#Teamcenter::CreateInput,*",
3, post_condition_handler, 0);
tag_t item_reva = NULLTAG;
tag_t item = NULLTAG;
ITEM_create_item( "" , "test" , "Item" , "A" , &item , &item_reva );
When the item is created by the ITEM_create_item method, the corresponding

post_condition_handler handler is called:
// post_condition_handler sample code
static int post_condition_handler( METHOD_message_t *, va_list args )
{
std::string str_item_id;
std::string str_item_name;
std::string str_typeName;
bool isNull;
ResultStatus resstatus;
Teamcenter::CreateInput* createInput = va_arg(args, Teamcenter::CreateInput*);
if (createInput)
{
resstatus = createInput->getString("item_id", str_item_id,isNull);
resstatus = createInput->getString("object_name", str_item_name,isNull);
printf("In post_condition_handler() object_name=%s\n", str_item_name.c_str());
resstatus = createInput->getBusinessObjectName(str_typeName);
}
return 0;
}
For more information about this method, see the Integration Toolkit Function
Reference.

Teamcenter industry solutions

The following are new features in Teamcenter industry solution applications.
Aerospace and Defense

Aerospace and Defense provides a data model template that supports the aerospace
and defense manufacturing industry.
The following are new and changed Aerospace and Defense features.
Contract Data Management

You can now manage, initiate review processes, and monitor correspondence for
procurement documents, such as design information, drawings, status reports,
purchase orders, and so on.
Contracts represent a statement of work in a program. This statement of work lists
one or more data requirement items (DRIs). The pro forma of the data requirement
items are described in the data item description (DID) document. The DIDs list
the type of data to be provided, the time of delivery, and the format in which it is
delivered. The deliverable attached to the contract is looped through a contract
event for reviewing.
With this feature, you can:
• Create data item descriptions (DIDs) to define and describe the data that must
be furnished by the supplier.
• Create contracts.
• Create and attach data requirement items (DRIs) to contracts.
• Generate submittal delivery schedules for the DRIs. The application generates
the submittal delivery schedule using Schedule Manager.
• Monitor correspondence related to contracts and submittal.
Contract data management is available as part of the core Teamcenter installation.

For more information about managing contract data, see the Aerospace and Defense
Solution Guide.
Automotive Edition
Automotive Edition provides localization capability in the Teamcenter Automotive
Edition/GMO client for the following elements:
• Type names
• Relation names
• Property names
• LOV values and LOV value descriptions

Chapter
4 Release notes
Teamcenter 8.3 product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Installation and upgrade release notes . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
General installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Lifecycle Visualization installation . . . . . . . . . . . . . . . . . . . . . . . 4-4
Online help installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
General upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Access Manager upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Classification upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Usage release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Change Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Client for Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Data Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Extensions for Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Global Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Integration for Office and Network Folders . . . . . . . . . . . . . . . . . . . . 4-26
Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Maintenance, Repair, and Overhaul . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Manufacturing Process Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Mechatronics Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Multi-Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Plant Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Report Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Requirements Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
Schedule Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
Specification Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
Structure Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63
Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
Vendor management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
Visualization Illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
Administration release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
General administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Teamcenter File Services and FMS administration . . . . . . . . . . . . . . . 4-75
Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Customization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
Thin client customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
ITK customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
Teamcenter interfaces release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
Adobe Illustrator interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
Rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-91
Thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
Internationalization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
Third-party release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99
IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99
Microsoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99
Mozilla Firefox Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-101
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102
Platform-specific release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103
Hewlett-Packard HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103
IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106
Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-107
Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109
SUSE Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111
UNIX platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-112
Teamcenter 8.3 documentation release notes . . . . . . . . . . . . . . . . . . . . . . . . 4-114

Business Modeler IDE Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114
Change Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116
Classification Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116
Classification Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-118
Client for Microsoft Office Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-118
Command Suppression Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-118
Data Exchange Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-119
Extensions for Microsoft Office Guide . . . . . . . . . . . . . . . . . . . . . . . . . . 4-120
Frequently Asked Questions for Teamcenter . . . . . . . . . . . . . . . . . . . . . 4-120
Getting Started with Electronic (EDA) Lifecycle Management . . . . . . . . . 4-121
Getting Started with Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-121
Setting access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-121
Enable graphics creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-121
Building tool assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-122
Build a tool assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-122
Understanding propagated attributes . . . . . . . . . . . . . . . . . . . . . . . 4-125
Map vendor catalog tools to customer hierarchy . . . . . . . . . . . . . . . . 4-126
Install NX templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-126
Enable tool retrieval from Teamcenter to NX . . . . . . . . . . . . . . . . . . 4-127
Retrieve a tool fromTeamcenter in NX . . . . . . . . . . . . . . . . . . . . . . . 4-127
Getting Started with Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-127
Installation on UNIX and Linux Clients Guide . . . . . . . . . . . . . . . . . . . 4-128
Installation on UNIX and Linux Servers Guide . . . . . . . . . . . . . . . . . . . 4-128
Installation on Windows Clients Guide . . . . . . . . . . . . . . . . . . . . . . . . . 4-129
Installation on Windows Servers Guide . . . . . . . . . . . . . . . . . . . . . . . . . 4-130
Manufacturing Process Planner Guide . . . . . . . . . . . . . . . . . . . . . . . . . 4-131
Configuring a 3D PDF report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-131
Teamcenter 8.3 Release Bulletin PLM00001 G (01-037134-083)

Install the prerequisite software . . . . . . . . . . . . . . . . . . . . . . . . 4-132
Preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-132
Install the 3D PDF report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-133
Verify installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
Locating the log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
Create a 3D PDF report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
Install live PRC export mode with Lifecycle Visualization . . . . . . 4-134
Switch between live and stub operation modes . . . . . . . . . . . . . . 4-135
Multi-Site Collaboration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-135
Organization Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-136
Platform Designer Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-136
PLM XML Export Import Administration . . . . . . . . . . . . . . . . . . . . . . . 4-137
Preferences and Environment Variables Reference . . . . . . . . . . . . . . . . . 4-138
MENEWMFG_DefaultDatumJTDatasetName . . . . . . . . . . . . . . . . . 4-139
REQ_default_object_template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-139
REQ_default_spec_template_for_export . . . . . . . . . . . . . . . . . . . . . . 4-140
REQ_default_spec_template_for_view . . . . . . . . . . . . . . . . . . . . . . . 4-140
REQ_import_keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-140
SM_PV_FILTER_SHOW_SCHEDULES_ON_EMPTY . . . . . . . . . . . 4-141
TC_relation_export_on_transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-141
Report Builder Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-143
Requirements Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-143
Rich Client Customization Programmer’s Guide . . . . . . . . . . . . . . . . . . 4-144
Rich Client Interface Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144
Schedule Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-146
Server Customization Programmer’s Guide . . . . . . . . . . . . . . . . . . . . . . 4-146
Structure Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-147
System Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-147
Teamcenter Publish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-149
Thin Client Interface Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-149
Transition Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-152
Upgrade Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154
Utilities Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154
convert_replica_files_to_stubs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-157
item_to_part_design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-159
pdx_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-163
pom_audit_manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-165
Web Application Deployment Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-167
What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-167
Workflow Designer Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-169
AI-process-export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-170
AI-process-import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-171

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

The following notes are new as of Teamcenter 8.3.
Installation and upgrade release notes

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

• Installing four-tier rich client on Microsoft Windows requires
administrative privileges
When running Teamcenter Environment Manager (TEM) on Microsoft Windows,
the four-tier rich client feature appears unavailable. Mousing over the feature
indicates that you have to have administrative privileges to install it. The
feature should be installed by nonadministrative users.
How to work around or avoid
1. Copy the media to an editable location.
2. Locate the install\modules\feautre_rac4t.xml file.
3. Edit the file and change the value of the <admin> tag from true to false.
4. Save the file.
5. If you already have an installation and you are attempting to add the four-tier
rich client, you can find the file in TC-ROOT\install\install\modules.

Chapter 4 Release notes
• 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

Release notes
• 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.
DB2 installation
The following release notes pertain to IBM DB2 installation.

• Certification for IBM DB2
Teamcenter 8 MP1 adds certification for the IBM DB2 v9.5 database on the AIX,
Windows, and Linux SUSE platforms. Currently DB2 is not certified on the
Solaris or HP-UX platforms.
The default database option during installation for Teamcenter is updated to
DB2 for the certified OS platforms. Other certified databases can be selected
during the installation process if desired.
• 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.
• Embedded viewer installation reports file registration error
During installation or uninstallation of the Teamcenter embedded viewer, if
Microsoft Visio is not present on the host, the installer displays the following
error:
Files(s) failed to self-register:
C:\Program Files\Common Files\UGS Shared\TcVis\VP3DGeomAssetData.dll;
C:\Program Files\Common Files\UGS Shared\TcVis\VPVisioAddin.dll

Dismiss the error message and proceed. If there are no other errors, the
installation succeeds. The error occurs because Microsoft Visio is not present.
You will not be able to view Microsoft Visio files in Teamcenter.
• Lifecycle Visualization and rich client viewer versions must match

With Teamcenter 8, the stand-alone Lifecycle Visualization and rich client
viewers are released together and you must use the same release version for
each. For example, mixing an earlier Teamcenter 8 rich client installation with
a later Lifecycle Visualization installation may cause the rich client viewer to
stop working.
The versions must remain in tandem, or you must copy the
SingleEmbeddedViewer.jar file from the Program folder in Lifecycle
Visualization to the plugins folder in the rich client. The old JAR file must be
completely replaced. Upgrading the rich client installation to a later version of
the viewer automatically upgrades any stand-alone viewer already installed.
• 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.

Release notes
Online help installation
The following release notes pertain to installation of Teamcenter online help.

• Using Mozilla Firefox 3.0.5 with the UNC path for online help
Most customers install and launch the documentation HTML using the http://
protocol, which is fully supported. However, Mozilla Firefox 3.0.5 has a default
security setting that prevents the help from launching correctly from a UNC
path (file:///).
To change this setting, you must change the value of the
security.fileuri.strict_origin_policy preference:
1. In the address bar, type about:config.
2. In the Filter box, type security.fileuri.

The security.fileuri.strict_origin_policy preference is displayed. It is set to
true by default.
3. Double-click the value to toggle it to false.
4. Exit the browser and restart it. If you check the settings, you see that the
value is set to false.
• WebLogic 9.1 deployment of Teamcenter with online help fails

When installers of Teamcenter thin client include the Teamcenter - Online Help
solution and attempt to deploy the tc.war or tc.ear files using WebLogic 9.1, the
deployment fails. The exception error message in WebLogic 9.1 states:
Probably the string length of the path of the file being extracted was too long
WebLogic 9.1 cannot handle long path names found in some books in the
Teamcenter online help collection.
Use WebLogic 10 or 10.3.

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 Engineering or Teamcenter.
• Teamcenter 2007.2 users upgrading to Teamcenter 8 must upgrade to
Teamcenter 8.2
Teamcenter 2007.2 adds classes to the object model to support visual report
definitions from NX 7.5. The same functionality is added to Teamcenter 8.2.
These classes are not included in Teamcenter 8 through Teamcenter 8.1.
If you upgrade from Teamcenter 2007.2 to Teamcenter 8, you must upgrade to
Teamcenter 8.2 because Teamcenter 8 through 8.1 do not include visual report
definition classes.
• 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 8 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

Release notes
5. Regenerate the schema file using:

install –regen_schema_file infodba password dba
After the upgrade to Teamcenter 8, 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.

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.
• Vault and TCM released rule ACL tables modified

(First published (First published Teamcenter Engineering 9.1.2)
The Vault and TCM Released Rule ACL tables deny read privilege for external
group members to released data owned by other groups. To implement similar
access rules for external groups in your custom Access Manager rule tree, use
the Vault ACL table definition as an example.
• Manual modifications required to Access Manager rule tree for Project

(First published Teamcenter Engineering 9.0)
Access Manager provides the following rules for use with the Project application:
– The In Project rule supports the security rules on objects assigned to a
Teamcenter project.
– The Owning Group Has Security rule supports the security rules on
objects owned by the groups of a particular security category.
In addition, the Owning Group rule is extended to support wildcard input. If

you are upgrading from Teamcenter’s engineering process management 8.1.1.x
to Teamcenter 2007, you can take advantage of these new features by manually
adding these rules into the Access Manager rule tree. For examples, see the
default Access Manager rule tree.
For more information, see the Access Manager Guide and the Project and
Program Guide.

Release notes
Classification upgrade
The following release note pertains to the administration 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.
Usage release notes

The following release notes pertain to the usage of Teamcenter.
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.

Change Manager
The following notes pertain to usage of Change Manager.

• 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>

Release notes
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>
<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.
• Key ID edit in Classification Administration key-LOV
Key ID changes in the key-LOVs in Classification Administration are considered
new entries. Therefore, the localization data associated with that key entry is
lost upon saving. There is a similar impact if the key ID is changed in PLM
XML and SML.
To preserve the localization data after a key ID change, click the Localization
button of that entry. Upon saving after editing, the localization data is added
as the localization data for the edited key ID entry.
• Workflow status of latest item revision lost after item is sent to

Classification
(First published Teamcenter 8,3)
If an item has its latest item revision in a workflow and you send the item to
Classification from the My Teamcenter perspective, when you switch back to My
Teamcenter, the status symbol is not displayed with the latest item revision.
To see the correct status of the item revision, refresh the latest item revision
using the View→Refresh menu.
• 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.
– 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.
– 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.

Release notes
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:
– 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.
– 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.

• Multi-Site sharing for Classified Workspace objects

The same object can be classified multiple times in the same class in a Multi-Site
sharing environment.
To duplicate the problem:
1. At the Site1 location, classify the Item1 object (or any other
WorkspaceObject object) in the C1 class.
2. Perform a remote export (or import) operation to transfer ownership of the

Item1 object to the Site2 remote site, excluding the Classification relation.
3. On the Site2 location, classify the Item1 object under the C1 class.
4. Perform a remote export (or import) operation again to transfer ownership of

Item1 back to Site1 but include the Classification relation this time.
On the Site1 location, the Item1 object has two classification objects in class
C1. Having two objects can lead to inconsistency.

To avoid this inconsistency, when performing an ownership transfer during
remote export or import, you can select the Classification relation to be
included in the export or import along with the WorkspaceObject object.
• Classification does not work on thin client with Mozilla Firefox 3

If you use the Mozilla Firefox 3 Web browser for the thin client and attempt to
use the Classification application, a blank page is displayed.
Use Internet Explorer instead of Firefox, or install the Internet Explorer plug-in
for Firefox on the Windows platform.
• Classification tree is not visible on the thin client using Safari 3

If you use the Safari 3 Web browser for the thin client and try to use the
Classification application, the classification tree is not shown.

Release notes
• 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’s Client for Microsoft
Office.
• Changing group and role when Security Services is enabled
With Security Services is enabled, log onto Teamcenter using the rich client and
change your group and role settings. Then open an Office dataset with Client for
Office enabled. The appropriate Office application is launched and the Client for
Office add-in is loaded, but the default group and role settings are applied rather
than the settings that were changed in the rich client.
From the Teamcenter tab of the Office application, click Current Settings and
select Session to display a dialog box allowing the user to change the group
and role settings. Ensure that user is logged on with the correct group and
role settings. The user can change the group and role settings if the current
settings are not desired.
• 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.
• Teamcenter tab buttons apply to the open Teamcenter document

Buttons on the Teamcenter tab of the Microsoft Office ribbon are tied to the
open Teamcenter document.
If no Teamcenter document is opened, you cannot view its properties, check in,
check out, revise, submit to workflow, and so on.
You can perform these actions on items, datasets, and so on using the shortcut
menu from the Browse or Folder View controls. These actions are tied to the
selection context and not the opened document.

Release notes
• 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:
– Each document opens in a separate Word window and the taskbar shows
the individual document names.
– All Client for Office features for Word are enabled.
• Cannot save changes for a checked-out Outlook dataset

Using Client for Office, a user opens a Microsoft Outlook e-mail dataset, edits
the e-mail message, and chooses the Save command on the Teamcenter menu.
The changes cannot be saved to the same dataset.
Choose Save As to save a copy of the message to Teamcenter as a new dataset.
• No integration between live Office and Client for Office add-ins

Using Requirements Manager within the rich client, the user opens a
requirement in the embedded Microsoft Word window and makes edits to save.
When the requirement dataset is opened in the embedded Word window, the
Client for Office add-ins tab is displayed. When the user attempts to save the
requirement dataset using the Client for Office menu, Client for Office does not
recognize the Teamcenter object context and does not know where this dataset
originates in Teamcenter.
Do not use the Teamcenter menu. When the document is opened from the rich
client, the live Office add-in disables the Office save user interface and presents
its own save button. The user should use this save button (not the Teamcenter
save user interface).

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

• Export fails
Export fails and the rich client hangs if the rich client cache is cleared prior
to performing a PDX export, Briefcase export, or remote export using Global
Services from a client configured with Content Management.
Close the rich client and perform the export action again. The export process
runs to completion.
This issue can also be avoided by closing the Progress Monitor view. The problem
does not occur if the rich client does not contain the Content Management client.
• Switching to the Content Management perspective

If you open the Content Management perspective and switch back to the My
Teamcenter perspective, some menu commands in the File→New menu are
missing.
While the My Teamcenter perspective is open, log off Teamcenter and log back in.
• Inoperable items in the Content Management user interface

Choose File→New→New Content Management Permissions. In the resulting
dialog box, the following permissions are inoperable:
xdShowViewContentInbox
xdShowPdmView
xdShowPdmResourcesView
xdShowProjectOrgansiationFolderView

These items will be operational in a future version.

Release notes
• Incorrect tool tips in a Content Management dialog box

In the Create Language Item dialog box, tool tips do not match behavior.
• S1000D is supported only if the Content Management Web server is

running on Windows or LINUX platforms
S1000D is supported only if the Content Management Web server is running on
Windows or LINUX, because the SGML parser is not available on the other
platforms.

Data Exchange
The following release notes pertain to Data Exchange.

• Unable to see child parts under Uses Part relation in Teamcenter
Enterprise
The relation of one child part is missing under the uses part relation for the
second revision of the assembly. Perform the following steps to duplicate the
problem:
1. Create a simple assembly having two child parts in CATIA and save to
2. Check in the assembly to a vault with product documents and all components.
3. Freeze the assembly and both the child components.
4. Make a new revision of an assembly and its child parts.
5. Drag and drop the revised assembly and child parts into the CATIA
workbench. (Do not query the assembly after revision.)
6. Load the new revision of the assembly in CATIA.
7. Modify the part geometry and save the assembly into Teamcenter Enterprise.
8. Query the assembly and expand the uses part relation.
1. Create a simple assembly having two child parts in CATIA and save to
2. Check in the assembly to vault with product documents and all components.
3. Freeze the assembly and both the child components.
4. Make a new revision of an assembly and its child parts.
5. Query the assembly and expand the uses part relation. Verify all child parts
in the new revision are under the uses part relation.
6. Drag and drop the revised assembly and child parts to the CATIA workbench.
7. Load the new version of the assembly in CATIA.
8. Modify the part geometry and save the assembly to Teamcenter Enterprise.
9. Query the assembly and expand the uses part relation. You should now see
all child parts under the uses part relation.

Release notes
• 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.
• Object Directory Services (ODS) operations not supported between

Teamcenter and Teamcenter Enterprise sites
All Data Exchange operations related to the Object Directory Services (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.
• Teamcenter to Teamcenter and Briefcase transfers through Data

Exchange support NX and JT CAD data only
Standard Teamcenter Data Exchange supports exporting and importing CAD
data only when it is NX and JT data.
Do not attempt to transfer other types of CAD data.

Extensions for Office
The following release notes pertain to the use of Extensions for Office.
• 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:
– Office 2007:
TcO2K7Preprocessor.dotm
– 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.

Release notes
Global Services
The following release notes pertain to Global Services software.

• WebSphere 7 and ODE 1.3.3 are incompatible
WebSphere 7 and ODE 1.3.3 are incompatible. Therefore, the Data Exchange
solution and the BPEL engine of Global Services are not supported with
WebSphere.
User either a WebSphere 6.1.0.9 application server or ODE 1.3.4. The Global
Services framework itself is supported on WebSphere 7.
• Horizontal scroll bar may be hidden

When the contents in the main window of the sample Global Services user
interface is wider than the browser, a horizontal scroll bar is available but may
be hidden from view.
Use the vertical scroll bar on the right to scroll down to see the horizontal scroll
bar. If you do not see a horizontal scroll bar, the content of the page being
displayed is wider than the browser.
• 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:
– 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.
– 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.
• NoSuchMethodError exception when using Teamcenter Engineering 9

and Teamcenter Engineering 2005/2007 connectors in the same EAR file
Global Services does not support including these two connectors in the same Web
application (EAR file).
Using the Web Application Manager, build a Web application (EAR file) with all
of the required Global Services solutions but without one of the Teamcenter
Engineering connectors. Build a second EAR file that contains the Teamcenter
Engineering connector not included in the first EAR file. Ensure that you provide
different Deployable File Name values. The two EAR files can be deployed in the
same application server without causing errors. For more information about Web
tier installation, see the Installation on Windows Servers Guide or Installation
on UNIX and Linux Servers Guide.
• 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.

Release notes
• Sample Teamcenter item BOD cannot be used for update

The supplied sample Teamcenter item BOD cannot be used for update because
the units of measure (UOM) attribute is not marked as updateable.
Modify the sample Teamcenter item BOD to include the following:
<default-value>null</default-value>
<update-able>true</update-able>
• Global Services conversion tool shows an error but conversion succeeds

Output from the Global Services conversion tool shows an exception similar to
the following when converting Teamcenter Integrator 7.x files:
D:\stagingDir\lib>java -jar convert.jar d:\accelis_1_dsj_7a2\
filteredsrc\core\runtime\bos\AccelisMessage.xml d:\stagingDir\lib\am.xml
2006/11/13-16:45:59,877 UTC MLD Log init: com.teamcenter.mld version 0.0.3d
(2005-06-06)2006/11/13-16:45:59,877 UTC MLD Log init: Instance configuraton
hierarchy object: org.apache.log4j.Hierarchy@1e0cf702006/11/13-16:45:59,887
UTC MLD Log init: Configured to Global log4j LoggerRepository:
org.apache.log4j.Hierarchy@b6ece5, local hierarchy: org.apache.log4j.
Hierarchy@1e0cf702006/11/13-16:45:59,897 UTC MLD Log init: Note: com.
teamcenter.mld Log initialization did not find any log4j configuration file(s)
in directory D:\stagingDir\lib\.
Failed to get data store com.edsplm.plmi.config.ConfigurationError:
FATAL ERROR CFG01040: Failed to load the configuration information.
’com.edsplm.plmi.config.ConfigurationError: FATAL ERROR CFG01040:
Failed to load the configuration information. ’
at com.edsplm._plmi.config.InitialConfig.initialize(InitialConfig.java:69)
at com.edsplm._plmi.config.InitialConfig.getInstance(InitialConfig.java:79)
at com.edsplm._plmi.config.AccelisConfig.getRuntimeLocation
(AccelisConfig.java:347)
at com.edsplm.plmi.config.AccelisDataStoreFactory.<clinit>
(AccelisDataStoreFactory.java:35)
at com.edsplm._plmi.log.LoggerFactory.<clinit>(LoggerFactory.java:44)
at com.edsplm.plmi.log.LoggerFactory.getLogger(LoggerFactory.java:80)
at com.edsplm.plmi.log.LoggerFactory.getLogger(LoggerFactory.java:52)
at com.edsplm._plmi.jaxb.JAXBUtil.<clinit>(JAXBUtil.java:34)
at com.teamcenter.globalservices.config.Convert.main(Convert.java:80)
runtime location = UNSPECIFIED LOCATION
Converted XML written to d:\stagingDir\lib\am.xml
</clinit>
</clinit>
</clinit>

No workaround is required. The conversion succeeds and the converted files are
available to use.

Integration for Office and Network Folders
The following release notes pertain to the use of Teamcenter’s Integration for
Microsoft Office and Teamcenter’s Network Folders.
• Dataset created from the thin client not available in Network Folders
When using WebDav, datasets of the Text type are created without named
references in either the thin client or the rich client and are not visible in
Network Folders.
Ensure that Text datasets are created with a named reference in the clients.
• Clicking No in the delete shortcut dialog box deletes a dataset

When using Network Folders, deleting the windows shortcut and canceling the
dialog box appears to trigger a Teamcenter delete.
Do not create shortcuts using Network Folders objects.
• Uninstalling Integration for Office may fail

During the installation of Integration for Office through Internet Explorer, it
may create a conflict folder under the C:\Windows\Downloaded Programs
Files directory. When this occurs, uninstalling Integration for Office from the
Control Panel Add or Remove Programs application may fail, showing the
following error message:
could not locate INF file

Download the UninstallTcOffice.bat file from the InstallTcOffice.html page
and save it anywhere on the local disk. Close all Microsoft Office or Internet
Explorer windows and run the UninstallTcOffice.bat file.
• New revision does not attach the same datasets as the original revision
If you create a new revision, it does not contain datasets that have the attach
relation to the original item revision.
If a revision contains datasets with the attach relation, use the rich client or
thin client to revise the item.

Release notes
• Document management with Network Folders and Microsoft Office

Value and description pairs consistently appear regardless of the Options setting
when using Microsoft Office.
In Teamcenter rich client, you can edit an LOV preference to hide the description.
In Integration for Office and Windows Explorer, the LOV value/description pairs
are always displayed regardless the preference setting.

Lifecycle Visualization
The following release notes pertain to usage of Lifecycle Visualization.
• 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.
• 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 standalone 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.

Release notes
If you see a reconcile dialog box in these situations, you can ignore it, and do not
need to update the references.
• Sending legacy product views to the rich client Lifecycle Viewer

When sending legacy product views to the rich client Lifecycle Viewer (or
standalone 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.
• Installing a PostScript printer in Windows

Beginning with Teamcenter 8.3 Lifecycle Visualization, the PostScript printer is
no longer automatically installed on Windows (all platforms).
You must have administrative permission to perform this workaround.
After installing Lifecycle Visualization 8.3, check for the existence of the
PostScript Printer in the Printers section of the Control Panel. If the PostScript
Printer 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.
If the Windows can’t verify the publisher of this driver software message is
displayed, click Install this driver software anyway.
If you did not install the PostScript printer before using Teamcenter 8.3 Lifecycle
Visualization or later, the application attempts to install it at runtime. You
need administrative privileges to run the InstallPrinter.bat file and you may
see the message noted above.

• Toolbar buttons show incorrect behavior

When a viewer is open in the Lifecycle Viewer and another perspective, switching
from the Lifecycle Viewer to the other perspective does not give focus to the new
viewer. This issue is similarly described in deferred PR 6097869. At this point,
clicking the native toolbar buttons is unresponsive or displays incorrect behavior.
Click inside the viewer region (forcing focus) prior to using the native toolbar
buttons.
• Refresh issue when switching from the Lifecycle Viewer to the My

Teamcenter Viewer tab
On Solaris systems only, 2D images do not display when switching from the
Lifecycle Viewer to the My Teamcenter Viewer tab. To duplicate the problem:
1. View 2D data in the Viewer tab of My Teamcenter.
2. Send the 2D data to the Lifecycle Viewer.
3. Switch back to the My Teamcenter Viewer tab.

Sometimes this results in a gray Viewer tab although the 2D image is
selected in tree.

If you see a Viewer tab that is gray, use one of the window grips surrounding the
viewer area and resize the viewer. Upon resizing, you should see the viewer area
being drawn correctly.
• 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.

Release notes
• Navigator window appears blank on UNIX

On UNIX, the Navigator window in the Lifecycle Viewer appears blank or gray.
If you are working in the Lifecycle Viewer and see a blank or grey Navigator
window, close the Navigator window. To re-open the window, open the Window
menu. Choose Show View→Other, and under the Visualization folder, select
Navigator and click OK.
• Rich client hangs on UNIX systems

On UNIX systems, the Lifecycle Viewer modal dialog boxes can hide behind the
Teamcenter rich client application, causing the application to appear that it has
hung. If you are working with the Lifecycle Viewer and an action has caused the
rich client to no longer draw correctly (refresh), or you can no longer interact
with it, it may be due to a modal viewer dialog box that needs to be dismissed.
Move the Teamcenter rich client application to see if a viewer dialog box can be
found behind it. Once the dialog box is dismissed, the Teamcenter client should
resume normal operations.
• .vvi file not found on Windows Vista machines if Lifecycle Visualization

is set to run as administrator
If you double-click a .vvi file in Windows Explorer on a Vista machine or send
it from Structure Manager within Teamcenter, you may see the following error
message:
Windows cannot find "filename.vvi". Make sure you typed the
name correctly, and then try again.

Ensure the Lifecycle Visualization executable VisView.exe is not set to run
as an administrator by right-clicking either the VisView.exe file in Windows
Explorer or the Lifecycle Visualization shortcut and choosing Properties. In
Privilege Level, ensure the Run as Administrator check box is cleared.
• .vvx file type not recognized as a file associated with Lifecycle

Visualization
Certain file types, including .vvx files, do not appear to be associated with
Lifecycle Visualization after running the application.
Run Lifecycle Visualization as an administrator at least once to register the
entire set of file types. To run Lifecycle Visualization as an administrator,
right-click the Lifecycle Visualization shortcut and choose Run as administrator.
After the main application window displays, the application should close.

• Moving markup entities in Lifecycle Visualization creates temporary

graphics artifacts on Windows Vista
If you click and drag markup entities in Lifecycle Visualization, a gray shadow
follows the trail of the mouse and disappears when you release the left mouse
button.
Change the theme in Vista from Windows Vista to Windows Classic.
• 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.
• Some product views created in Teamcenter 2005 SR1 do not retrieve

after upgrade to Teamcenter 2007
Product views created in Teamcenter 2005 SR1 that were captured after turning
on the entire assembly at the root node do not appear when they are launched
after upgrading to Teamcenter 2007. Product views captured after the visibility
state was selected at the part level, however, do appear.
Make the entire model visible after loading the product view.
• 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.

Release notes
Maintenance, Repair, and Overhaul
The following notes pertain to usage of Maintenance, Repair, and Overhaul.

• 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.
• 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:
– 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.
– 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.
• PLM XML import of partitions

When importing a partition structure into Teamcenter, only the partition root is
imported. The structure itself is not imported.
Currently, there is no workaround for this problem. A fix will be provided in
Teamcenter 8.3.0.1.

Release notes
• Clone of standard text information does not work

Cloning of the following types does not copy the standard text information that
is in the structure. These types are accessed from the File→New→Standard Text
menu and the File→New→From Template menu:
Standard Text Library
Standard Text Folder
Standard Text Element
Process
Operation

Modify the following preferences:
Product.Template.Cloning
Process.Template.Cloning
Process.Template.Ignoring_Consumes
Process.Template.Mapping_Consumes
Process.Template.Referencing_Consumes
Add the following lines above the *:*:OccType.*:Reference line:

*:*:OccType.Mes0MEDCD:Clone
*:*:OccType.Mes0MEPF:Clone
*:*:OccType.Mes0MESTX
This allows you to clone the Standard Text elements and the data collection
elements. This solution supports cloning of:
Standard Text Library
Standard Text Folder
Standard Text Element
However, cloning Process or Operation is not complete. Whereas the standard

text elements and the data collection elements are cloned, the form in-context of
the process or operation (the data collection properties override) is not copied.
• 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.

• Accountability check does not work with IDC

Accountability check does not support comparing IDC structures. This is due to
major infrastructure changes to improve the functionality of the accountability
check feature.
• Some properties of a WeldPoint object cannot be modified

Some properties of a WeldPoint object (such as Hold_time, Max_current,
Metal_comb, and so on) are defined in the cmtemserver template and
therefore cannot be modified if this template is not installed.
Install the cmtemserver template using the Business Modeler IDE. This
template is used to customize the eM-Server Integration.
• Variant condition added to a part does not appear in the process window
If you add a variant condition to a part in the product structure, it does not
immediately appear on the assigned line in the process window.
Choose View→Refresh.
• Assigned occurrence for GDE link is not accurate after Manufacturing

Process Planner is reopened
If you use a GDE and then remove the GDE line, the assigned occurrence shows
the link is broken. If you close and reopen the Manufacturing Process Planner
application, the link is not broken. If you search for the object in the other pane,
the removed GDE line reappears with a Java error displayed in the Quantity box.

Release notes
• 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.
• 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.

Release notes
• 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.
• Mechatronics Process Management sample ITK program/utility issue

If you run the mechatronics_system_test program (packaged with sample
files) to create Mechatronics Process Management objects in the database and
then try to delete the data using Delete option, the program may fail.
Delete the data using the rich client.

Multi-Site
The following release notes pertain to Multi-Site implementation.

• Negative site IDs
On January 1 2010, the pool of positive integers that are automatically assigned
to newly created databases ran out.
If you have an existing installation that has not been upgraded in accordance
with Software Field Bulletin-Teamcenter-5058 (SFB 5058), you cannot create
a new database.
If you have an updated installation, or you have installed a Teamcenter version
that already contains the necessary code fixes, be aware that all site IDs
generated for new sites created on or after January 1, 2010 are negative integers.
This is especially important for customers who work with sites that are part of a
Multi-Site federation.
If you have an existing installation that has not been upgraded in accordance
with SFB 5058, read the SFB and the detailed documentation it references and
upgrade your system accordingly.
If your site is part of a Multi-Site federation, you will inevitably deal with sites
that have negative site IDs whether it is your own site or a federated remote
site. Remember that in all Teamcenter dialog boxes, command line arguments,
configuration files, and so on where the site ID is entered, you must prefix the
site ID with the minus sign (–) for newly created databases. Failure to do so
results in an incorrect Multi-Site configuration.
For more information, go to the following URL:
http://download.ugs.com/sfb/sfb-teamcenter-5058.txt
• Autopublish of item with alternate identifiers

If you set the Autopublish feature, whenever an item or its subtypes is created,
they are published to the given Autopublish site. But during the publish
operation, alternate identifiers are not sent as part of the publishing information.
Publish the item again manually to publish the alternate ID information.

Release notes
• 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.
• Sharing data with pre-Teamcenter 2007.1 MP3 databases causes variant

expression block and variant condition errors
If you share data between a Teamcenter 2007.1 MP3 site and a site with an
earlier version of Teamcenter or Teamcenter Engineering, you may receive
errors if you use an item revision variant expression block or an occurrence
variant condition.
Run the following utilities on the pre-Teamcenter 2007.1 MP3 database:
install -mod_attr infodba infodba dba ItemRevision variant_expression_block
POM_attr_follow_on_export +
install —mod_attr infodba infodba dba ItemRevision variant_expression_block
POM_null_is_valid +
install —mod_attr infodba infodba dba PSOccurrence variant_condition
POM_attr_follow_on_export +
install —set_attr infodba infodba dba PSOccurrence variant_condition
NULLTAG
install —mod_attr infodba infodba dba PSOccurrence variant_condition
POM_null_is_valid —

• Remote checkin behavior

If you attach a local object to a replica using remote checkout, upon remote
checkin the attached local object can be transferred with ownership, can be sent
as replica, or can be opted not to be sent at all. You can configure this behavior
from the user interface and preference. From the Remote Checkin dialog box
advanced options, you can select a relation to be transferred with ownership.
The option to send as replica is not yet available in the user interface. Therefore,
a relation listed in the TC_remote_checkin_relation_send_as_replica
preference is sent as replica.
When you select a particular relation from the user interface, the following table
explains the behavior to local attached behavior.
Relation included Relation specified

in user interface in preference Behavior
Yes Yes Transfer of ownership
Yes No Transfer of ownership
No Yes Sent as replica
No No Not transferred at all
• Remote checkin/checkout and incremental change

Normally the remote checkin of BOMView and BOMViewRevision objects,
which have incremental changes made to them within Structure Manager,
results in the automatic transfer of ownership of the related engineering
change object back to the master site. In the case where the only incremental
changes made are attachment deletes, the engineering change object is not
automatically transferred to the master site and the delete actions are not be
visible in Structure Manager.
Manually transfer the ownership of the engineering change object back to the
master site.
• Multisite licenses
(First published Teamcenter Engineering 2005)
Prior to Teamcenter Engineering 2005, the Multi-Site Collaboration Server
license was checked only when the Object Directory Services (ODS) server
process starts up. Starting with Teamcenter Engineering 2005, all multisite
operations, such as remote import, publication and remote search, checks the
Multi-Site Collaboration server license to make sure that this license was
purchased. If the Multi-Site Collaboration server license is not available, users
get an error message when performing multisite operations. Make certain the
Multi-Site Collaboration server license, as well as the multisite user licenses, are
available prior to deploying multisite in Teamcenter 2007 and future versions.

Release notes
My Teamcenter
The following release notes pertain to My Teamcenter.

• Column configuration in the Details view
When you apply the Default column configuration in the Details view, the
columns displayed can be different from the set of columns that were displayed
before applying any configuration.
Save another configuration that contains columns that are shown by default and
apply it when required. You can also add required columns using the Column
Management dialog box.
• 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.
• Multiple naming patterns not supported in New Business Object wizard

The New Business Object wizard (accessed from the File→New→Other menu)
currently does not support multiple naming patterns.
In the rich client, use the File→New→Item menu command to create items that
have multiple naming patterns.
• 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.

Release notes
• 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.
– 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
– 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–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.
• Validation report gives wrong Total Number, Target, and User results
(First published Teamcenter 2007
When using the validation results query to generate a validation report, the
validation report gives wrong Total Number, Target, and User results.
Use VO – Validation Results search criteria to query the validation results.

Release notes
NX Integration
The following release notes pertain to usage 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:
– Perform a View Fit (Ctrl+F) on the component preview window. The

components to be added are visible in the preview window.
– 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.

• Connections under a harness sometimes move incorrectly

If you export a connection list from NX to Teamcenter with the Export to PDM
menu command, a connection under a harness could move out from under
the harness on subsequent exports to Teamcenter. This typically happens in
connection lists that have more than one harness.
• 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 after canceling previous download

attempt
In the thin client, if you click the hyperlink to download an NX assembly in
the Export Status window and then click the Cancel button, the Download
hyperlink is no longer available.
Always click the Save button after clicking the Download hyperlink.
• 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.

Release notes
• Harness structure corrupted after wire is deleted

The harness structure from the previous revision is corrupted after you delete
the wire from the new revision.
Release the electrical harness when you release the item containing the electrical
harness.
• Harness structure corrupted after adding a harness and connection

A new harness structure is corrupted after you add a harness and connection
using the NX Export to PDM menu command.
The harness structure from the previous revision is corrupted after you delete
the wire from the new revision.
Use variants and options instead of multiple, duplicate harnesses within one
part file.
• Item IDs can be created that are invalid in Teamcenter Integration

for NX
Teamcenter allows characters in the item ID that are not allowed in NX.
Do not create item IDs that contain the following characters:
– Any control character (less than 0x32)

– Double quote (“)
– Asterisk (*)
– Slash (/)
– Backslash (\)
– Colon (:)
– Less than (<)
– Greater than (>)
– Back tic (‘)
– Vertical bar (|)
– Delete character (0x7f)
– Tilde (~)

• NX clone import requires default volumes value from Teamcenter

While performing a Teamcenter Integration for NX import operation, the NX
Information dialog box may display the following message:
No or invalid default volume for User or Group in database.
The Teamcenter default behavior is for the user to inherit the default volume
value from the user’s assigned group. At times, the value from this implicit
assignment does not get passed to the Teamcenter Integration for NX import
operation. This message indicates the Teamcenter value did not pass properly to
the Teamcenter Integration for NX import function.
Manually set the default volume using the Default Volume button in the Groups
pane in the Organization application. This explicitly assigns the volume name
to the user. The value from the explicit assignment is provided to the clone
function and imports function correctly.
Plant Designer
The following release notes pertain to Plant Designer.
• Plant Designer data pane not opening
If you open Plant Designer after opening Manufacturing Process Planner, and
then open a plant item and click the Show / Hide the data panel button, the data
pane is not displayed.
This issue will be resolved in Teamcenter 9.
To avoid the problem in Teamenter 8 versions, perform either of the following:
– Send the structure to Plant Designer and open the data panel before opening
Manufacturing Process Planner.
– Make sure Manufacturing Process Planner has some structure loaded and
click a line in Plant Designer before opening the data panel.
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.

Release notes
Report Designer
The following release notes pertain to the use of Report Designer.

• Report Designer support
Report Designer reports are not supported for 64-bit browsers (for example,
64-bit Internet Explorer on Microsoft Windows 2007) and browsers that do not
support ActiveX controls (for example, Mozilla and Firefox).
• Report style sheet not deleted

The alignment check report cannot be opened in the correct application. For
example, during report generation, you select an option to create a dataset and
the dataset file opens as an XML file regardless of the format you choose. The
report transformation may fail because there is a file in your system similar
to the style sheet; this file may exist because of incorrectly terminated report
generation.
Delete the style sheet file the report uses to transform the data to the required
format. To find the name of the style sheet file, in the report generation
dialog box select the report you are generating. The name of the file is the
same as the one you see in the style sheet selection list. Delete this file in the
TC_TEMP directory if the TC_TEMP environmental variable is set, or under C:
on Windows, or the /tmp directory in UNIX platforms.
• 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
byte_size. If you select the one for Dataset.ref_list.byte_size, the resulting
Property Finder Formatter (PFF) column displayed still has Title of File Size
and has file size data. Thus, 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.

Reporting and Analytics
The following release notes pertain to Reporting and Analytics:
• 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.
• Report problems
The following reports do not function correctly:
BaselineComparison
MTA
MTR
ResourceWorkload
ScheduleVsActual
ScheduleComplete

• 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.

Release notes
• 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.
• No field name appears in error message when creating a connection

in mapper
No field name appears in error message when creating a connection in the
mapper.
After you click the error message, the mapper highlights the field with the error.

Requirements Manager
The following release notes pertain to the use of Requirements Manager.
• 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 Requirements Manager 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]

Release notes
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:

– Add-in: TcO2k7Addin. Connect Friendly Name
– 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.
• Saving from Requirements Manager does not work when autorecovery

is enabled
Saving from Requirements Manager does not work when autorecovery is
enabled. Perform the following steps to reproduce the issue:
1. Ensure that Microsoft Word 2007 is configured for autorecovery every 5
minutes.
2. Export a requirement to live Word for editing.
3. Type some changes in the requirement but do not save them.
4. Wait approximately 5 minutes for the autorecovery message:

Saving AutoRecovery File is Postponed for filename.
5. Click OK and click the Save button.
6. Type some additional text.
7. Wait for the next autorecovery message. This time the message and the
Word title bar displays the file name with the ASD extension.

Manually disable the autorecovery option in Word when using live Word.
1. For Word 2007, click the Office button on the top left corner and select Word
Options.
2. Click the Save tab.

3. Clear the Save AutoRecover information every x minutes check box.
4. Click OK.
• Macro changes for Microsoft Office 2010 users in Excel template

If you use Microsoft Office 2010, and you have user-defined macros in the
Excel template, when you export to Excel using the template, you may 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.

To use Microsoft Office 2010 with user-defined macros in the template, perform
the following steps to edit the macro. There are two options:
– Option 1
1. Make a copy of the user-defined macro code.
2. Copy the Teamcenter macro code from any standard template to the
user-defined template VBA section (macro).
3. Merge the contents of the user-defined macro code and the Teamcenter
macro code. Ensure there is no loss of the Teamcenter macro code.
4. Save the macro and template.
– Option 2
1. Create an item of the ExcelTemplate type.
2. This creates and attaches a standard template to the newly created

Excel template.
3. Edit this template macro code to add the user-defined macro code.
Ensure that there is no loss of Teamcenter macro code.
4. Save the macro and template. In both the cases, when you save the
template, the digital signature of the macro breaks.
• 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:

Release notes
– Microsoft .NET framework 3.5
– Visual Studio Tools for Office Runtime 3.0
– 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.
• Macros created in specification templates are disabled in Microsoft

Word export documents
If macros are stored only in a specification template, you cannot run the macros
in Word export documents based on that template. Instead, Microsoft Word
generates a security alert on the message bar.
Do either of the following:
– In the Word document:

1. On the message bar, click Options.
2. In the Microsoft Office Security Options dialog box, select Enable this
content.
– When creating a macro in a specification template, select All Documents

(Normal.dotm) in the Store macro in list on the Record Macro dialog box.
A macro that is globally available is enabled in export documents based on
the specification template.

• 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.

Release notes
Resource Manager
The following release note pertains to Resource Manager.

• Expand root node in Resource Manager class selection does not work
with double-click
In the Resource Manager application, you may not be able to expand the root
node of the Classification Information dialog box by double-clicking when
classifying a new resource. This happens only if the MRM_NEW class does not
exist and a resource was not previously loaded.
Choose Expand from the shortcut menu.

Schedule Manager
The following release notes pertain to usage of Schedule Manager.

• Schedule deliverables managed outside Schedule Manager
Problems occur when attempting to edit schedule deliverables outside of
Schedule Manager. For example, an error can occur when you check out a
schedule, view the properties from My Teamcenter, and click the Schedule
Deliverables button.
Edit the deliverables within Schedule Manager.
• 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.
• 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.

Release notes
Specification Manager
The following notes pertain to usage of Specification Manager.

• Viewing Interspec specifications in Specification Manager requires
updated templates
Interspec specifications that are imported into Teamcenter can be viewed using
Specification Manager. Specification Manager uses an Microsoft Word template
to provide a rich formatted display of the Interspec specification. One of these
templates is modified to improve the display.
To take advantage of the display, this new template must be loaded manually.
Specification Manager still continues to work as before even if this new template
is not loaded.
Note
If you have already made custom changes to the
SPECMGR_default_CPProcStage_object_template template, you
can ignore following steps.
1. Search for the RequirementsManagement Templates folder.
2. Expand it and you see the ObjectsTemplates folder.
3. Expand the ObjectsTemplates folder and delete the

SPECMGR_default_CPProcStage_object_template template.
4. Run the following utility:

add_specmgr_templates -u=infodba -p=password -g=group
This utility creates an updated version of the specification template that

you previously deleted.

• 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:
– Set the PS_Find_Number_Validation preference to FALSE.
– 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.

Release notes
Structure Manager
The following release notes pertain to Structure Manager.

• 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 item_to_part_design utility topic in
the Utilities Reference documentation release notes in this bulletin.
• 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 significant limitations when used on
structures containing Pro/ENGINEER data. These are tracked by the following
enhancement requests (ERs):
– ER 6150737
The Part Families→Masters command is required in the Duplicate dialog
box.
– ER 6111242
CAD integrations need configurable recursive traversal for dependencies.
Until these limitations are removed in a future Teamcenter release, and

until corresponding changes are made to the Teamcenter Integration for
Pro/ENGINEER, Teamcenter Duplicate should only be used on Pro/ENGINEER
structures for demonstration purposes, or on structures that contain only
assembly-to-part and assembly-to-assembly relationships.


Load structures that contain any of the following data types into the CAD
session for duplication:
– Part family tables
– Multiple levels of external references
– Circular references such as Interchange assemblies and parts
• 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.
• Separation of view and edit properties in Manufacturing Process

Planner and Structure Manager
In Manufacturing Process Planner and Structure Manager, there are not
separate dialog boxes for the view and edit properties functionality for BOM line
properties as there are for properties in My Teamcenter.
Use the Properties dialog box to edit properties.

Release notes
• 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.

Teamcenter EDA
The following release notes pertain to usage of Teamcenter EDA.
• Validation of Teamcenter EDA Mentor Board Station integration

Teamcenter 8.2 will not initially deliver the Teamcenter ECAD Connector
(product code TC31005).
The release of the connector will be handled later. The nonavailability of this
connector for Teamcenter 8.2 will be documented using the standard Sales
Availability Matrix.
• First save from the Teamcenter Gateway for EDA may fail on a new
server
A first save attempt from the Teamcenter Gateway for EDA may fail, and
Teamcenter may crash during BOM generation on a new server installation.
Save the design again. This error occurs only once, when the Teamcenter
Gateway for EDA is used for the first time. You should not encounter this
problem again.
• 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.
• ECAD library does not support importing and exporting items with
the space characters
If an item’s footprint or symbol ID field contains spaces, the ECAD library
cannot import or export the item.
Use the ECAD library tool to replace the spaced with a character.

Release notes
• ECAD library import cannot update properties for existing parts

The ECAD part library uses the Teamcenter Import Export module (TIE) and
Briefcase to import parts into Teamcenter. TIE does not allow updating existing
part properties. If a part is imported from two libraries, it is assigned only to the
first imported library. When users synchronize with a second library, although a
part is in the export list, it is not imported.
Manually update published part properties.
• Mentor Board Station 2005 is not supported on Solaris 10

If you start Mentor Board Station 2005 on a Solaris 10 workstation, it may
generate the following system error:
init_alt_dynld: Unable to find _elf_bndr in ls.so
Mentor Board Station 2005 continues to launch. However, if you then try to
use a Teamcenter EDA integration command, you may get a failure during the
Teamcenter logon.
Currently, Mentor Board Station 2005 is not supported on Solaris 10. The launch
error is known to Mentor Graphics, but there is no known solution for it. Mentor
Board Station 2006 and above is supported on Solaris 10. Teamcenter EDA now
supports both Mentor Board Station 2005 (BS2005) and Mentor Board Station
2006 (2006BSXE); however, only Mentor Board Station 2006 is supported for
Solaris 10.
The version of Mentor Board Station is determined at run time and the EDA
integration configures itself accordingly.

• Teamcenter EDA errors when using Mentor Graphics on UNIX

(First published EDA 2005 SR1)
Teamcenter EDA integrates ECAD design applications, such as Mentor Graphics
and Cadence, with Teamcenter. When using the Teamcenter EDA client with
Mentor Graphics on a UNIX platform, Teamcenter EDA actions fail. The launch
of the Design Manager may also fail.
During the installation of the Mentor Graphics support option within
Teamcenter EDA, files are installed that provide extensions to the Mentor
Graphics Design Manager product. Because of delivery limitations, these files do
not contain the correct operating system file permissions. This condition only
occurs on UNIX platforms (Sun Solaris).
Because some of the files contain incorrect permissions, the user encounters
errors that report that Teamcenter EDA tasks cannot be called because of these
incorrect permissions.
You must manually edit the installation to allow these Mentor Graphics
extensions to be used. Perform the following procedures for each UNIX client
that contains the Teamcenter EDA client code for Mentor Graphics.
To update file permissions, enter the following in a command prompt on Sun
Solaris systems:
cd $MGC_HOME/bin
chmod 755 mti_bom mti_dmgr mti_xbom
cd $TCEDAECAD_ROOT/Mentor_BoardStation/lib
chmod 755 libMTI*

Release notes
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
Vendor role
Commercial part
Vendor part
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
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.

• 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 runtime 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.
• 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.

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.
• Importing preferences in new categories at a scope other than Site
Because categories can only be created at the site level, importing a preference
file that creates new categories and associated preferences with a scope other
than Site poses some issues.
1. The first step differs if there are some site preferences under the category:
– If the category does not contain any site preferences, open the rich client
as an administrator and create the category.
– If the category contains at least one site preference, create a preference

file that contains the new category and only the site preferences. Then
run the import utility using this newly created preference file:
preferences_manager -u=user-name -p=password scope=SITE ...
2. Create one preference file for all the preferences under a scope other than
Site, placing them under their categories.
3. Run the import utility using each preference file and the specific scope.
preferences_manager -u=user-name -p=password scope=selected-scope ...
As a result, all preferences appear under the correct categories.
• Update of the Selection Criteria preference

The Selection Criteria preference uses incorrect format for the default values
and the preference description is confusing.
The values and description on the preference are revised in Teamcenter 8.3.
However, you must run the preferences_manager utility to update the
Selection Criteria preference. Run the utility import mode, and provide an
XML file that contains the Selection Criteria preference content. For example:
preferences_manager -u=user-name -p=password -g=group
-mode=import -scope=SITE -file=pref_file.xml -action=OVERRIDE
Use the following for the pref_file.xml file:

<preferences>
<preference name="Selection Criteria" type="String" array="true" disabled="false">
<preference_description>Sets the criteria used for pre-selection of attachments
for Item Revision objects for Check-in/Out.
For example, for the below case, all the objects of type UGMASTER having a
IMAN_specification relation with the Item Revision object will be pre-selected.
Valid values are in the format TypeInternalName followed by 10 spaces and then,

RelationInternalName.
At all times, one of the two preferences "Selection Criteria" or "Select IR"
must be set, otherwise the "Check-In/Check-Out" of Item Revision objects will not
work. However, this preference’s values take precedence over values of these
other two preferences.
If this preference is not set and "Select IR" preference is set ,then only the
Item Revision objects are selected and not their attachments.</preference_description>
<value>UGMASTER IMAN_specification</value>
<value>UGPART IMAN_specification</value>
</context>
</preference>
</preferences>
Note
The import mode cannot be used with -preference as input, because the
fix involves a change in the preference description, which can be done
only with the file as an input.
• 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.
• Reversing accidental externalization of internally managed user

constructs
When a user construct object (user, group, role, person, or group membership)
exists in both LDAP and in Teamcenter, the default ldapsync utility
synchronization behavior is to set the datasource attribute on that user
construct in Teamcenter to externally manage and synchronize that object with
Teamcenter. This is particularly useful for updating user and person Teamcenter
objects that were synchronized from LDAP in previous Teamcenter versions to
set the new datasource attribute correctly. However, some customers may not
want internally managed user construct objects to be converted to externally
managed. Because externalization of these objects is the default behavior, you
must provide a way to undo that change if it is done accidentally.
You can change the default behavior for each user construct type by removing the
externalize sync flag in the preferences file. See the Preferences and Environment
Variables Reference for more details on the externalize synchronization flag
in the following preferences:
LDAP_sync_group_flags
LDAP_sync_member_flags
LDAP_sync_role_flags
LDAP_sync_user_flags

Release notes
There is no opposite unsynchronize feature to change user construct objects from

externally managed to internally managed. However, the make_user utility
is updated with a special option to set the datasource attribute on specified
user construct objects. Use this feature to reset user construct objects that
were mistakenly externalized during a synchronization process. This option is
intentionally left undocumented in the make_user utility because it should not
be used for any reason except to correct a synchronization error.
The make_user command line option, –datasource=value, sets the specified
data source value (0=Internal, 1=External, 2 =Remote) on the specified user,
person, group, role, and group membership objects. By setting the datasource
attribute to 0 on a user, person, group, role, or group membership object, the
object is returned to internally managed.
The make_user utility also allows attributes to be specified in an input file for
batch processing, and datasource is supported as an attribute for updating
user, person, group, role, and group membership objects. For more information
about the make_user input file for batch processing, see the make_user
documentation in the Utilities Reference manual.
• Slow startup or connection timeout with Apache Tomcat 5

When starting Apache Tomcat 5.0 or Tomcat 5.5, slow startup and high CPU
usage may occur. The following exception from Tomcat may also appear:
ERROR - 2005/10/25-09:16:34,185 UTC { }
Bootstrap com.teamcenter.mld.jmx.ConfigurationListener
java.net.ConnectException: Connection timed out: connect

This error occurs because the default Java JVM garbage collection and heap
memory settings (–Xms and –Xmx) are often too small. Increase the Java
memory heap and garbage collection settings of Tomcat 5 to resolve this issue.

Organization
The following release notes pertain to the Organization application.

• Groups are not displayed in the Select Recipients dialog box
The Name property for groups and roles is marked localizable by default.
If you do not plan to localize the group and role name, you must remove the
Localizable constant on the Name property.
If the names are localizable, you must provide all the translations to ensure
that all users see all the groups and roles in selection panes (for example, when
searching for the group objects in the Select Recipients dialog box within the
File→New→Envelope command).
These are locale-specific searches, and names that are not translated to the user
locale are not displayed in the list. The name translations must be provided to
ensure all users find the objects. During the creation of groups and roles, use the
Localization button to add the locale translations.
Group or role objects need to be created with all the required information.
Consider the Group object creation within the Organization application.
1. Click the Group tree node.
2. Type the name of the group and all other necessary information.
3. Click the Create button.
4. Once the object is created (and therefore selected in the Group tree), click
the Language button next to the group object name.
5. Type the proper translations for all the necessary languages.
By doing this, you have ensured that the created objects will be found by a search.
• Redundant events logged when creating a person

When you create a person, redundant modify events are logged in the audit table
in addition to the create event when Audit Manager is turned on.

Release notes
Teamcenter File Services and FMS administration

The following release notes pertain to the administration of Teamcenter File
Services and FMS.
• Storage of replica files
In Teamcenter 8.2, the following site level preferences were introduced to allow
Multi-Site tools to perform caching in lieu of volume storage:
TC_force_remote_sites_exclude_files
TC_Populate_FSC_Server_Targets
However, there may be times when it is desirable to add remote files to the
volume instead of cache. Library parts, such as common fasteners, are an
example. Therefore, Teamcenter 8.3 should support cache only or volume-only
storage of replica files. Unsetting the preferences allows storage of files in a
volume. However, unsetting the preferences has site-wide impact.
Because setting the preferences has site-wide impact, the scope of preferences is
reset to ALL. This allows the customer to set these preferences as environmental
variables (preferably in the tc_profilevars file) on a local machine and perform
the import of library parts to replica volumes.
• Slow logon performance

Logging in to Teamcenter is very slow.
For the Teamcenter rich client to start up and log on to the Teamcenter server,
hundreds of megabytes of resources must be loaded from the local hard disk
into memory. In the warm case where the files have been recently read into
memory and remain in the RAM file cache of the operating system, this initial
load can take just a few seconds. However, in a cold case such as after reboot of
the client computer, the limiting factor on performance is how quickly the bytes
can be read from the hard disk into RAM.
The following can negatively impact cold file read performance:
– Virus scanning software
Exclude the entire portal folder and all of its subfolders from virus scanning,
as well as the Teamcenter/RAC folder under the user folder where the rich
client workspace folder is maintained.
– Large PATH statement

Minimize the size of your system PATH environment variable and remove
nonlocal folders from the PATH statement.
– Low hard disk space

Ensure the hard drive where the rich client is installed remains
defragmented and never becomes filled over 75 percent of capacity.

– Running applications
Minimize usage of any other resource intensive applications that may be
competing for pages in memory while the rich client is starting up.
– Starting FCC at logon

Start the FMS FCC at operating system logon and keep it running in the
background, so the rich client does not have to start FCC while the rich
client is logging on.
For more information, see the FCC documentation.
One way to achieve near warm startup times in a cold case situation is to
warm the rich client files found under the portal folder using the file warmer
capability of the FCC application.
For more information, see the System Administration Guide.
• FSC fails to start on reboot of UNIX systems

The FMS server cache (FSC) process can fail to start after a reboot of UNIX
systems. This failure can be caused by other services that the FSC process
depends on which have not yet reached an operational state.
For example, the ypbind service can take additional time to start. Because this
service was not operational at the time an attempt was made to start the FSC
service, the su operation failed to switch to the required user to start the FSC.
Correct the reason that the ypbind service is launching slowly. Because
Siemens PLM Software software is not directly contributing to the slow launch
of ypbind service, this resolution must be investigated by the respective IT
departments on a case-by-case basis.
A workaround is to add a pause in the startup script. A sleep value of 120 seconds
was found to be sufficient in test systems. The sleep command must be added to
the startup script in the rcname.d directory. Do not modify the rc scripts under
the $TC_ROOT directory as these scripts are not the ones first called.
Note
Renaming the rc script in the rcname.d directory to force the service to
boot later in the boot order did not provide sufficient time to allow the
ypbind service to start in test systems.

Release notes
• FMS configuration
The following error message appears when the values specified for the
Transient_Volume_RootDir preference have identical values:
Duplicate transientvolume configuration elements were found for attribute id
with value attribute_value

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. The distinction is made 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.

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.
• 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:
– 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.
– 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.

Release notes
• 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:
– 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.
– 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.
– 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
– 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.

Release notes
• Customization of the default search string used in the WebSEAL logon

page FORM causes authentication to fail
After Teamcenter rich client, FMS client cache (FCC), or Teamcenter’s lifecycle
visualization client startup, any action that requires authorization initiates a
request to the IBM Tivoli WebSEAL server. WebSEAL sends an authentication
challenge response to the Teamcenter application, which attempts to detect
the WebSEAL form authentication event prior to initiating Security Services.
This detection process performs a search within the WebSEAL HTML response
to find a specific string. The default search string used in the WebSEAL logon
page FORM post HTML is:
<FORM action=/pkmslogin.form method=post>
The custom search string is:

<FORM method=post action=/pkmslogin.form>
If this string in the WebSEAL logon page HTML has been customized, the
authentication process between Security Services and WebSEAL fails.
– FMS client cache (FCC)

Provides a configuration property within the fcc.properties.template file
that can be used to redefine the search string.
Change the fcc.properties.template file name to fcc.properties, and then
edit the following section to uncomment the Detection Pattern property,
and redefine the pattern.
# Optional property for specifying the string pattern used for detecting
# a WebSEAL form authentication event. The string is searched for in the
# body of HTTP response message sourced by a WebSEAL revere proxy server.
com.teamcenter.fms.websealFormAuthDetectionPattern=
<FORM method=post action=/pkmslogin.form?
– Teamcenter’s lifecycle visualization client

Provides an environment variable that can be used to redefine the search
string. Set the following system or user environment variable prior to
starting the Lifecycle Visualization client:
TCVIS_FORMBASED_AUTH_CHALLENGE_KEY=<FORM method=post action=/pkmslogin.form>
– Teamcenter rich client

Provides a property that can be used to redefine the search string. Set the
following property in the site_specific.properties file prior to starting
the Teamcenter rich client:
webSealFormURL =<FORM method=post action=/pkmslogin.form>
– Teamcenter’s Integration for Microsoft Office

Not supported by WebSEAL proxy. If Integration for Office is included
in the installation with WebSEAL, the file attachments with the
dataset may fail during open or edit operations. To avoid this error,
ensure the useMSOfficeIntegration property is set to false in the
client_specific.properties file.

Utilities
The following release notes pertain to utilities.

• 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.

Release notes
• smlutility utility with some options corrupts data model objects

managed by the Business Modeler IDE
The smlutility –install utility with the following suboptions corrupts data
model objects managed by the Business Modeler IDE:
– ICS
– ICS_BASE
– ICS_SYSD
– ICS_ICM
Do not use this utility with the suboptions to create or update the
Classification-specific parts of the Teamcenter data model. This is controlled by
the Business Modeler IDE. If you use the smlutility –install utility, you may
corrupt the data model and the data may become inaccurate.
The only option still allowed is ICS_UTIL. However, do not use this option
because the schema installed by this utility is not customizable.

Customization release notes

The following release notes pertain to customizing Teamcenter.
Business Modeler IDE
The following release notes pertain to the Business Modeler IDE.
• The ItemCreation.NoMasterForm and ItemCreation.NoRevMasterForm

preferences are obsolete
The NoMasterForm preferences allow users to define a list of types that do
not automatically create Item Master forms. While Item business objects
can be created without master forms, some applications such as Multi-Site
and Part-CAD Alignment depend on the Item business objects having master
forms and do not correctly interpret the Item object without a master form.
Additionally the capability of not creating master forms was not fully tested with
all applications; therefore, it is not safe to use it. If you are currently using these
preferences, Siemens PLM Software strongly suggests that you deconfigure
them and use one of the following workarounds for hiding the master forms. In
the future, Siemens PLM Software plans to reinstate this type of configuration
and test it thoroughly so that you can use it safely. At this time, there is no
scheduled release for this.
To hide master forms in Teamcenter 8.0 and later versions:
– Hide the master form from client dialog boxes for an Item business object or
its subtype:
1. Open the Item business object or one of its children in the Business
Objects view of the Business Modeler IDE.
2. Click the CreateDescriptor tab and select the IMAN_master_form

property.
3. Click the Edit button to the right of the CreateDescriptor table.
4. Select the Required check box and clear the Visible check box.
– To hide the master form for an ItemRevision business object or its subtype,
use similar steps. Set the IMAN_master_form_rev property on the
CreateDescriptor tab of the ItemRevision or its subtype as required and
not visible (that is, select the Required check box and clear the Visible
check box).
– If any of the attributes on the master form are mandatory or if they need
to be edited by the user, you can use the Business Modeler IDE to create a
compound property on the corresponding Item or ItemRevision business
object that points to the attribute on the master form.

Release notes
The preceding workarounds hide the master form from the creation dialog box
but create the master form in the background. To hide the master form from other
screens in the user interface, edit the business-object_DefaultChildProperties
preference to remove the IMAN_master_form or IMAN_master_form_rev
properties.
1. In the rich client, choose Edit→Options and click the Index tab at the bottom
of the Options dialog box and search for the preference for your business
object type (for example, Item_DefaultChildrenProperties).
2. Select the preference from the list on the left side of the dialog box and
remove IMAN_master_form from the Current Values list on the right side of
the dialog box. This hides the master form from the user interface for this
business object and all its child business objects.
• 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.
• Custom attributes for CAE items cannot be accessed from the New CAE
Item wizard
Custom attributes on the primary business object for CAE Items cannot be
accessed from the New CAE Item wizard in My Teamcenter, CAE Manager, or
CAE Structure Designer applications.
Use the Business Objects view in the to view Item or ItemRevision business
objects.
Item is the most common business object under which you create a new business
object. Use the Item business object or its children when you want to create
business objects to represent product parts. When you create a business object
using Item (or one of its children) as the parent, in addition to the new business
object, you can also create an item master form, an item revision, and an item
revision master form.
For more information, see the .
Attributes that are defined on an item master form or a revision master form are
presented on the New CAE Item wizard. The method of putting attributes on
these forms should continue to be used when creating custom item types that are
subtypes of the CAEItem business object and its children.

• Default value for the Enabled property constant is not honored

In the Business Modeler IDE, the default value for the Enabled property
constant is not honored by the system.
Perform the following steps to duplicate the error:
1. When a new custom property is added to a business object in the Business
Modeler IDE, the property has default settings for Enabled and Modifiable
property constants, as shown in the following figure.
Default new custom property settings

Change the setting for the Modifiable constant from Read to Write, as shown
in the following figure.
Modifiable constant changed to write

No changes are made to the Enabled constant, and its value is still false.
2. Deploy the data model to the Teamcenter database.

The custom property value should not be editable in the user interface (such
as the rich client, thin client, or Excel Live). The system does not honor the
user setting and allows users to edit the property value in the user interface.

Override the attachment for the Enabled property constant even though its
value matches with the default value.
1. Change the Enabled property constant value from false to true, as shown in
the following figure. Note that the Overridden column for enabled constant
is checked.

Release notes
Enabled constant changed to true
2. Save the data model.
3. Change the Enabled property constant value back to false, as shown in

the following figure. The property constants table displays that the value
is false and it has been overridden.
Enabled constant changed back to false

Note the difference between the Enabled constant in the first figure and the
last figure. In the first figure, the value for the Enabled constant is false and
the Overridden column is not checked. But in the last figure, the value for
the Enabled constant is false and the Overridden column is checked. This
means the default property constant attachment value has been modified.
4. Save the data model.
5. Deploy the data model to your database and test the user interface. The
property is not be editable in the user interface, and it can still be modified
programmatically.
This workaround is not only for customer-defined properties, but is also intended
for standard Teamcenter (COTS) properties.

• Business object (type) names and class names must contain only
USASCII7 characters
(First published Teamcenter 2007.1 MP7)
Deployment of business objects that have non-USASCII7 characters in the
business object name causes deployment to fail.
Business object (type) names and class names entered in the Business Modeler
IDE while performing data model extensions must be USASCII7 characters only.
This prevents any template install, upgrade, or deployment issues.
In Teamcenter 8.2, the capability to enter localized names for business objects
was provided.
For any existing business object (type) names or existing class names that do not
follow the USASCII7 format, you can use the change_type_name utility (found
on GTAC) to rename the type name to a valid USASCII7 name.

Release notes
Thin client customization
The following release notes pertain to customization of thin client applications.

• Unable to share Item and Item Revision Master Form customizations
between clients
The rich client and the thin client use different mechanisms to customize the
New Item dialog box. Customizing the master forms style sheet in the rich client
no longer presents the same customization in the thin client.
The thin client can customize item creation on the New→Other menu by creating
a CREATERENDERING style sheet that matches the customizations in the
style sheets used by the rich client. The New→Item menu in the thin client can
also be customized to leverage the new style sheet.
ITK customization
The following release notes pertain to Integration Toolkit (ITK) customization.

• WSOM_where_referenced ITK function returns real relation names
instead of display names
In earlier versions of Teamcenter, the WSOM_where_referenced ITK function
returned display names of relations. Because relation display names are
internationalized, this caused some issues in integrations with other third-party
applications.
To address these issues, the WSOM_where_referenced ITK function was
changed to return real relation names instead of display names. These changes
occurred in Teamcenter Engineering 2005 SR1 MP3. However, corresponding
documentation was not updated. This release note formally documents that the
WSOM_where_referenced ITK function returns real relation names instead
of display names.
Update custom code to take into account real relation names being returned
from the WSOM_where_referenced ITK function. This ITK function is
updated in Teamcenter Engineering 2005 SR1 MP3. There is a high possibility
that customers have already noticed these changes and updated custom code
accordingly.

Teamcenter interfaces release notes

The following release notes pertain to using Teamcenter interfaces.
Adobe Illustrator interface
The following release notes pertain to the use of the Adobe Illustrator interface.
• Improve Adobe Illustrator usability issues
The Adobe Illustrator integration has the following issues:
– When you type a new file name for an Adobe Illustrator file in the Save
As dialog box, if the file name contains special characters such as % or (),
problems arise when the file is opened because Adobe Illustrator reserves
these characters for special use.
– You cannot browse into other users’ home folders. Therefore, if you search for
Adobe Illustrator files, those under other users’ Home and Newstuff folders
do not appear in the search results.
– When you drag-and-drop a file from a local disk to Teamcenter, if the file or
dataset already exists in Teamcenter, you are prompted to override it. If you
click Yes, Windows Explorer tries to replace the file or dataset with the
new file. However, if the dataset is not checked out, it is protected by the
Teamcenter server. However, because Windows Explorer does not show the
error message from the server, the file replacement appears to be successful.
This is considered as a vendor problem.
– On Vista and Windows 7, after you log off from Teamcenter from Windows
Explorer, the user credential is cached, and is reused when the mapped
network drive is revisited. This appears to be a vendor problem.
– Do not use special characters such as % or () in the file name.
– In the tcwebdav.iprop file in the TC_DATA directory, a new

hideotherhome entry is introduced. The default value is Yes, which may
be changed to No if you want the old behavior.
– For existing files or datasets always perform a checkout before editing the
files or replacing them using drag-and-drop.
– After logoff, use the Tools→Disconnect Network Drive menu command.

Release notes
Rich client
The following release notes pertain to the use of the rich client.
• 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.
• 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).
• 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.
• Virus scanners may affect four-tier clients

Some virus scanners have a feature to monitor all HTTP communications from
a host. This can affect performance and even reliability. Because Teamcenter
four-tier clients such as the rich client and NX use HTTP to communicate with
the Web tier, they may be adversely affected.
Deactivate this functionality or configure the virus scanner to ignore
communications with the Web tier.

• Embedded viewer displays red background instead of a Microsoft Office

document in the rich client
If you install the rich client on a virtual drive and try to visualize Microsoft
Office 2007 documents in the embedded viewer, you see a red background instead
of the document. This also occurs in the Web Browser application.
Install the rich client on a regular drive on the machine instead of a virtual drive.
• 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 any of the following:
– Use Teamcenter’s Integration for Microsoft Office.
– Make changes in the Viewer pane.
– 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:
– Close the dialog box and open it again.
– 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.

Release notes
Thin client
The following release notes pertain to the use of the thin client.
• Unable to open Excel Report Builder Reports
The Excel Report Builder reports generated in Internet Explorer 6 or 7 do not
open in the Office Excel application, and open in the browser as XML documents.
Generation of Excel reports in the rich client works fine.
Save the generated XML file to the local disk and open, or use the Firefox
browser to generate Excel reports.
• NX export request keeps processing after thin client Export Status

dialog box closes
If you close the thin client Export Status dialog box, the NX export request keeps
processing instead of deleting the request.
Do not delete a request in the thin client. Use the translator administration
console in the rich client.
• PLM XML import/export does not handle import/export of files

associated with a dataset
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.
• Name and description values not set through initial value on a property
rule
(First published Teamcenter Engineering 9.1)
Prepopulation of the Name and Description boxes from the initial value
definition on a property rule is missing for the following dialog boxes:
New Dataset
New Folder

Currently, there is no workaround for this problem. The problem will be fixed in
a maintenance patch.

Internationalization release notes

The following release notes pertain to the internationalization of Teamcenter.
• 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:
– 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.
– 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
• 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.

Release notes
• Tool tip for the View menu is shown in English

The tool tip for the View menu in the upper right corner of Teamcenter views
appears only in English.
This problem is due to a bug in Eclipse and has been reported to Eclipse.
• Language Translations dialog box sometimes hides behind the

properties dialog box
When launching the Language Translations dialog box for localizable properties,
sometimes while selecting either the Locale or Status box, the Language
Translations dialog box may hide behind the properties dialog box. The problem
is partially fixed and may not occur in all places where the Localization button
is shown.
– Minimize the properties dialog box to see the Language Translations dialog
box.
– Move the Language Translations dialog box away from the properties dialog
box.
• Language Translations dialog box Status and Locale box issue

Localization administrators click the Localization button to launch the
Language Translations dialog box to enter localized text for property values.
In the Language Translations dialog box on Linux and Solaris platforms, you
cannot make a selection from the Status or Locale box using the mouse. It
appears the first value is selected by default, and you cannot choose any other
value.
Perform one of the following workarounds:
– Instead of launching the Language Translations dialog box from the

properties dialog box, launch it from the Viewer pane.
– If you choose to launch the Language Translations dialog box from the
properties dialog box, position your mouse on the Status or Locale box and
use the mouse wheel to make a selection.

• 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.

Release notes
• 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.

• Thin client displays non-Western European text incorrectly with

Apache 2 HTTP Server
(First published Teamcenter Engineering 8.1.1)
Apache 2 defaults to Western European encoding. As a result, the thin client
displays non-Western European text incorrectly when Apache 2.x is used as
the HTTP server.
This problem does not occur with Apache 1.3.20. As a work around, Siemens
PLM Software recommends that you comment out the encoding string in the
httpd.conf file (iso-8859-1).

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.
Microsoft
The following release note pertains to Microsoft.

• Data lost when editing Microsoft PowerPoint datasets
When you edit a Microsoft PowerPoint dataset and keep the Microsoft
PowerPoint application running, the dataset changes are not saved.
If you already have a Microsoft PowerPoint session running outside of
Teamcenter, close it.
When editing a Microsoft PowerPoint dataset, close the Microsoft PowerPoint
application after each edit to save the dataset. Otherwise, use Integration for
Office. If the Viewer tab in the rich client is used, make sure to close the Viewer
tab when done. This allows you to successfully save Microsoft PowerPoint
datasets by double-clicking and launching the Microsoft PowerPoint application.
• WEB_use_activex_lov preference setting for Internet Explorer 6

Due to an issue supporting overlapping elements (z-index) in Internet Explorer
6, ActiveX is used to support menus.
Internet Explorer 6 requires the WEB_use_activex_lov preference to be set to
yes.

• Incorrect file name displayed in thin client file download dialog box in
Internet Explorer 6.0
An incorrect file name is displayed in the file download dialog box when
attempting to view a file with a .prt extension from a UGPART dataset from the
thin client in Internet Explorer 6.0.
This appears to be a problem with compression in Internet Explorer 6.0. One
potential workaround is to upgrade to Internet Explorer 7.0 or use a different
browser such as Mozilla Firefox.
If Internet Explorer 6.0 must be used, another potential workaround is to
disable file transfer compression for files with a .prt extension in the FMS
subsystem. To do so, add the FSC_DoNotCompressExtensions property to
the <fscdefaults> element of the fmsmaster configuration files and include the
prt extension in the value as follows:
<fscdefaults>
<property name="FSC_DoNotCompressExtensions"
value="bz,bz2,cab,deb,docx,docm,ear,gif,gz,jar,jpeg,
jpg,jt,lha,lzh,lzo,mp3,mp4,mpg,prt,rar,rpm,sit,
taz,tgz,war,xlsx,xlsm,z,zip" overridable="true" />
</fscdefaults>
After you change the fmsmaster configuration files, either reload the
configuration files or stop and start the FSC servers to use the new value.

Release notes
Mozilla Firefox Web browser
The following release note pertains to the Mozilla Firefox Web browser.
• Moving browser scroll bar makes graphics disappear

If you use the Mozilla Firefox 2.0 Web browser on a Microsoft Windows Vista
64-bit platform for the thin client, moving the browser scroll bar makes the
graphics in the viewer disappear.
Use Internet Explorer instead of Mozilla Firefox.
• Back button works incorrectly with Teamcenter help pages

If you click the Back button when navigating the Teamcenter help system,
Mozilla Firefox returns you to the main collection page instead of the previously
viewed page.
• Teamcenter functionality not supported

The following Teamcenter functionality is not supported by the Mozilla Firefox
Web browser:
– Using the Adobe Scalable Vector Graphics (SVG) Viewer:
◊ In My Teamcenter, click View→Process to view the process in the SVG

viewer.
◊ In the Structure Manager application, select a supersedure and click

View→Supercedure to display genealogy of the part.
– Using ActiveX objects:
◊ In the My Teamcenter and Structure Manager applications,

Actions→Generate Report generates HTML and Excel reports using
the Microsoft XML parser.
◊ Click Edit link next to a dataset object to edit data sets using Microsoft
Office applications (Microsoft Office integration).
– Tree expansion state and search results are not retained in the browser
when the Back button is used. This state preservation is an enhancement in
Teamcenter that applies only to the Internet Explorer browser.

Oracle
The following release notes pertain to Oracle.

• Power saving option of network card on Windows laptop causes error
(First published Teamcenter Engineering 8.1.1)
If you install Oracle and the rich client server on a Windows laptop, and the
network card has a power saving option enabled, this configuration can cause
the rich client server to fail intermittently. The syslog file has an error message
similar to the following:
*** EIM_check_error: code -12571
*** NOTE:: in line 2612 of eim_trans_util.c
+++ (EIM_trans_util) ORA-12571: TNS:packet writer failure

To resolve this problem, you must disable the network card power saving option.

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
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.

Release notes
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.
• Icons on submenus are not displayed on AIX
On the Teamcenter AIX platform, all icons on submenu commands are not
displayed on the menu bar and context menu.
• IBM AIX clients with Teamcenter 8.2

The Teamcenter 8.2 rich client relies on the Eclipse 3.5.1 client platform. This
version of Eclipse is available only as a beta release on the IBM AIX platform.
The Teamcenter 8.2 rich client is fully tested on IBM AIX and is available as a
beta client as it relies on the beta version of Eclipse 3.5.1 for IBM AIX.
Teamcenter will update to the production version of Eclipse 3.5.1 on the IBM
AIX platform after it is available in Teamcenter 8.3.
• Creating a dataset using drag and drop does not work on IBM AIX and
Sun Solaris
On IBM AIX and Sun Solaris, the new dataset wizard is not launched when you
drag and drop file to the rich client.
In the rich client, use the New Dataset command or the Named References
command to import files into a dataset.
• Right-click object to show context menu on IBM AIX

On IBM AIX only, right-clicking items in some rich client applications does
not display the context menu. This occurs because there is a different way
to show context menus between SWT-based perspectives (Eclipse-based) and
Swing-based perspectives.
Right-click and hold down the mouse button to show the context menu for the
following applications (Eclipse-based):
My Teamcenter
Lifecycle Viewer
Change Manager
Relation Browser
Command Suppression
In other applications, right-click and release to show the context menu.

Release notes
Microsoft Windows
The following release notes pertain to Microsoft Windows platforms only.

• 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.
• Null pointer exception on Windows 7

A null pointer exception is thrown when you choose the Edit→Options menu in
the Teamcenter rich client in the Windows 7 environment.
Check where the shell folders point in the Windows registry.
Launch the RegEdit application and navigate to the
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
Explorer\User Shell Folders node.
Select the Personal row under the Name column. In the Data column for this
Personal entry, ensure that the directory exists. If not, create it.
The Personal entry in the registry should be something like:
Name Type Data

Personal REG_EXPAND_SZ %USERPROFILE%\shell-folder-name
Check for this shell folder from Windows Explorer. Typically the
%USERPROFILE% entry should correspond to C:\Users\user-account. If the
shell folder does not exist, create it.
• Double-clicking network folders shortcuts does not work on Windows 7

On a Windows 7 operating system, when you double-click a network folders
shortcut to navigate to Teamcenter, the shortcut does not open to show the
contents. This is a Windows 7 issue. The feature is working as expected on
all other certified platforms.
Do not use the shortcut. Manually browse the network folder.

• 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.
• Critical messages displayed in WebLogic 9.1 console when running

WebDAV
Critical messages are displayed in the WebLogic 9.1 console when running
WebDAV.
To remove these messages, follow the instructions provided by BEA: Steps for
Smart Update:
http://e-docs.bea.com/common/docs91/smart_update/quickrefax.html
WLS Version : 9.1
Patch ID : 917G
Passcode : WPMQRWE4
After applying the patch, add the

–Dweblogic.servlet.security.EnforceValidBasicAuthCredentials=false
parameter to the end of the call command in the startWebLogic.cmd file for
your domain. For additional technical support, contact BEA about CR266407.
• 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.

Release notes
Sun Solaris
The following release notes pertain to the Sun Solaris platform only.
• Symbols do not appear on menus on Solaris or Linux
Client symbols are not displayed for the following menu commands under
the View menu in the Structure Manager or Manufacturing Process Planner
applications:
Show Unconfigured Variants
Show Unconfigured By Occurrence Effectivity
Show Unconfigured Changes
Show GCS Connection Points
Show Suppressed Occurrence
Show/Hide Data Panel
Show/Hide Search Panel
Show/Hide Superseded Revisions
On the Windows platform, the menu commands display a symbol and a check
mark. On Solaris and Linux, the check mark is still displayed.
Add the menu command to the toolbar to display the symbol.
• Teamcenter server termination

A specific combination of Solaris 10 kernel patches may cause abrupt Teamcenter
server termination. The problem has been observed with Teamcenter 8.1 but
potentially can occur with any Teamcenter product deployed on Solaris 10.
Solaris 10 kernel patches 138888-01 or later, or patch 139555-08, may cause
data corruption in applications. In addition, unexpected application failure and
termination on the following UltraSPARC systems may occur: III, III+, IIIi,
IIIi+, IV, and IV+ . For more information, see the following URL:
http://sunsolve.sun.com/search/document.do?assetkey=1-66-269748-1
This has been observed in Teamcenter 8.1 as continuous core dumps from a
four-tier server process.
Install the Solaris patch from the following URL:
http://sunsolve.sun.com/search/document.do?assetkey=1-21-142900-15-1
If this version of the patch has become obsolete, please follow the links in the
documents to find the latest version.

• Configure Sun Solaris to ensure unique Ethernet MAC addresses for

multiple interface cards
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:
– 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
– 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

Release notes
After this reboot, the following shows the expected change in these commands,
showing unique MAC addresses:
– In the output of prtconf –pv:

# prtconf -pv | grep local-mac-address
local-mac-address?: ’true’
– (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.

• Unable to edit text fields
On UNIX and Windows platforms, sometimes you cannot change text in the
editable text boxes in the rich client, including in the Edit Properties dialog box
and the Properties dialog box.
The problem happens due to a focus issue with the windows and is being
followed up with Eclipse and Sun Microsystems. Perform one of the following
to work around the problem:
– Close the Edit Properties dialog box and open it again.
– Click another application or window and click back in the Teamcenter rich
client dialog box. Changing focus usually corrects this problem.
• IDSM servers do not respond on UNIX or Linux platforms

Clients of the IDSM return error messages that state the idsm_version_check
function has failed due to a time-out. For example, the data_share utility may
return the following:
***ERROR: No site available for processing
ERROR STACK:
100202: The IDSM request to site M0417Ha on host hpis04 failed.
: RPC: 1832-008 Timed out
100107: Attempted function idsm_version_check

at site M0417Ha on host hpis04.
If this occurs, the IDSM syslog files contain an error message in this form:
TextServer::TextPool – error-message SharedMemory will not be used.
If you see both these error messages, apply the following workaround.
You can use one of the following methods:
– Follow the procedure in the Starting the pool manager on HP-UX 11i
generates errors release note to resolve the text server shared memory IDSM
error messages.
– In the $TC_BIN/run_tc_idsm script, set the

TC_NO_TEXTSRV_SHARED_MEMORY environment variable to TRUE.
This disables the shared memory functionality and reverts the system
behavior to in-process text storage, which impacts the IDSM servers.

Release notes
• 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.

Teamcenter 8.3 documentation release notes

The following documentation additions and changes will be incorporated in a future
version of Teamcenter.
Business Modeler IDE Guide

The following release notes pertain to the Business Modeler IDE Guide.
• Condition use with verification rules
The following note will be added to step 6 in the Create a verification rule topic.
Note
The only conditions that are available are those with supported
condition signatures or their child types as defined in the selected
functionality object. The condition signature order must match the
selected functionality supported signature order. If there is a selected
applied business object, it must match the condition’s first parameter or
be a subtype of the first parameter.
• Changing TcPLMXML to TC XML

In the Output directory topic, the word TcPLMXML will be changed to TC XML.
• Use USASCII7 character set for naming schema objects

The following note will be added to the Naming objects topic.
Note
Business object (type) names and class names entered in the Business
Modeler IDE while performing data model extensions must be USASCII7
characters only. This prevents any template installation, upgrade, or
deployment issues.
For any existing business object (type) names or existing class names that
do not follow the USASCII7 format, you can use the change_type_name
utility (found on GTAC) to rename the type name to a valid USASCII7
name.
• Reordering of LOVs
The following note will be added to the Add a list of values and the Add values to
an existing LOV topics.
Note
Reordering of LOV values is supported. Prior to Teamcenter 8.3, you could
reorder the LOV values in the Business Modeler IDE, but the order was
not stored in the database. Beginning in Teamcenter 8.3, the LOV values
can be reordered in the template, and the new order is stored in the
database and displayed in the Teamcenter clients that use the LOV.
The LOV values cannot be reordered in filter LOVs, extent types of LOVs,
or tag extent types of LOVs.

Release notes
• Install the Business Modeler IDE to an existing Eclipse environment

The content of the Install the Business Modeler IDE to an existing Eclipse
environment topic will be replaced with the following.
If you already have Eclipse installed, you can install the Business Modeler
IDE into your Eclipse environment. Install the Business Modeler IDE to an
Eclipse environment if you want to install additional plug-ins to aid in your
configuration work.
For more information about Eclipse, see the following URL:
http://www.eclipse.org
Note
If the Eclipse environment already has Business Modeler IDE plug-ins
installed from an earlier release, installing a newer version of Business
Modeler IDE plug-ins in the same environment results in problems
and is not supported. Therefore, when upgrading to a later version of
Teamcenter, install a fresh version of Eclipse and perform the following
procedure.
1. Ensure you have an Eclipse 3.5.0 (Galileo) package installed. To download

Eclipse, see the following URL:
http://www.eclipse.org/downloads/packages/
Siemens PLM Software recommends that you install Eclipse Classic 3.5.0.
2. In the Teamcenter software distribution image, browse to the following

directory:
additional_applications\bmide_plugins
3. Extract all the ZIP files to your Eclipse directory (ECLIPSE_HOME). These
archives contain the plug-ins that are required for running the Business
Modeler IDE.
After unzipping the plug-ins, verify their installation at
ECLIPSE_HOME\plugins.
4. Launch Eclipse by running the eclipse file from the eclipse directory.
When Eclipse opens, set the workspace if asked and close the Welcome
tab if it appears.
5. Choose Windows→Open Perspective→Other and select the Business

Modeler IDE perspective.
The templates are installed in the bmide\templates subdirectory.
Note
Make sure that you select the same templates that are on the server.

Change Manager Guide

The following release note pertains to the Change Manager Guide.
• Enabling the Change Manager in the thin client
The following will be added to the Configure Change Manager row in the Before
you begin topic.
To enable the Change Manager menu commands in the thin client, set the
WEB_Enable_Create_Change preference to true.
Classification Administration Guide

The following release notes pertain to the Classification Administration Guide.
• Replace the lists of transfer modes found in the Using transfer modes topic with
the following.
The following table lists the transfer modes that you can use with Classification
Administration and their purpose.
Select the following transfer mode To export

ICSExportParents A class and all its parents. This
includes attributes, key-LOVs, and
views.
ICSExportParentsWithICOs A class and all its parents, including
all ICOs belonging to the exported
classes. This includes attributes,
key-LOVs, and views.
ICSExportParentsWithPartFamily A class and all its parent classes,
part family templates, and their
member ICOs.
ICSExportParentsWithWSOs A class and all its parents, including
all ICOs and classified objects. This
views.
ICSExportSubtree A class and all its children. This
views.
ICSExportSubtreeWithICOs A class and all its children, including
all ICOs belonging to the exported
classes. This includes attributes,
key-LOVs, and views.
ICSExportSubtreeWithPartFamily A class and all its child classes, part
family templates, and their member
ICOs.
ICSExportSubtreeWithWSOs A class and all its children, including
all ICOs and classified objects. This
views.

Release notes
The following table lists the transfer modes that you can use with Classification
and the information they export.
Select the following transfer mode To export

ICSExportICOs An ICO.
ICSExportICOs_User An ICO with the user class to which
it belongs.
ICSExportICOs_Admin An ICO with its admin class, views,
parents, attributes, and key-LOVs.
ConfiguredDataExportDefault An ICO with the user class to which
it belongs, in addition to the item it
classifies (product data).
• Replace the Remove an image from a group, class, or view procedure with the
following:
1. Select the group, class, or view from which you want to remove an image
and click Edit.
2. Do one of the following:
– To remove an image from a group, click at the bottom of the Group

pane.
– To remove an image from a class, click at the bottom of the Class

Details pane.
– To remove an image from a view, click at the bottom of the View pane.
3. Click Save .
• Understanding access rights

The following topic will be added to Sharing classification hierarchy data.
Assume a class hierarchy is already shared from site 1 to site 2, and you set
the access rights as follows.
When exporting objects, at any exporting site, the importing sites are first
evaluated to see that they can import from this site. Because all potential sites
are available in this organization, when the Import privilege is revoked on
World, it evaluates to site 2 not being privileged to import.
Instead, to allow only the selected users to import or export, use the following
access control list.

Classification Guide
The following release notes pertain to the Classification Guide.
• The object ID search in Classification searches the entire database for the ID you
enter. It does not take the search by type feature into consideration. Therefore,
step 3 of the Search by object ID topic is incorrect and should be removed.
Client for Microsoft Office Guide

The following release note pertains to the Client for Microsoft Office Guide.
• Certification for Microsoft Office 2010 (32-bit version only)
The 32-bit version of Microsoft Office 2010 is certified for Teamcenter’s Client for
Microsoft Office.
Note
– The 64-bit version of Office 2010 is not supported.
– Office 2007 is still certified.
– In Outlook 2007, the Office ribbon does not appear in the main
window as it does in the other Office 2007 applications. The main
window contains a Teamcenter toolbar that gives access to Client
for Office features.
– In Outlook 2010, the Office ribbon appears in the main window. The
Add-ins tab contains a Teamcenter toolbar that gives access to Client
for Office features.
– Other Office versions are not supported, including Office 2003 with
the compatibility pack for the Word, Excel, and PowerPoint 2007 file
formats.
Command Suppression Guide

The following release notes pertain to the Command Suppression Guide.
The following notes will be added to the Suppress commands topic.
• When you use Command Suppression to suppress the Tools menu in My
Teamcenter, the Import menu is remains visible under the Tools menu.
• The following functions do not display in the Tools menu in My Teamcenter;

however, they display in the Command Suppression application:
– Out Of Office Assistant
– Workflow Surrogate
– Subscribe To Refresh Notification
– Subscribe to Refresh

Release notes
Data Exchange Guide

The following release notes pertain to the Data Exchange Guide.
• Check out to a site

Add the following information to the Check out to a site topic.
Site checkout functionality is meant for collaboration between OEM and
suppliers in following use cases only:
– Adding or modifying datasets at a supplier site.
– Adding or modifying components (ps occurrences) at a supplier site.
– Modifying metadata (attribute values) of workspace objects at a supplier

site. Modification of nonworkspace objects and revising item and item
revisions is not supported.
You can perform site checkout on the following list of objects and their subclasses
only:
– Item
– ItemRevision
– PSBOMView
– PSBOMViewRevision
– Form
Ownership of new objects added at supplier site is determined based on the

following criteria:
– New objects created at a supplier site that are part of an existing island from
the OEM are owned by the OEM. For example, a dataset/version added to
an Item/ItemRevision object at a supplier site that is owned by the OEM
is also owned by the OEM.
– New objects created at a supplier site that are part of a new island at
supplier site are owned by supplier, tor example, adding a new Item object
(component) at a supplier site to an assembly owned by the OEM.
Note
Islands are logical groups of objects where the primary object is an item.
For example, the following objects are part of an island.
– Item (primary object of an island)
– ItemRevision
– Dataset
– Form
– Relation
– PSOccurrence
Data Exchange does not support site checkout of Schedule, ScheduleRevision,

ScheduleTask, ScheduleTaskRevision objects, and their related objects.

• CATIA alternate shape

Add the following information to the Transfer option sets topic.
If you intend to transfer CATIA alternate shape representation objects between
Teamcenter sites, you must add the following property set clauses to the
TIEPropertySet property set at the exporting site:
CLASS.POM_alternateSR_userdata:ATTRIBUTE.Shapes_Files:DO
CLASS.POM_alternateSR_userdata:ATTRIBUTE.Shapes_Names:DO
These property clause entries export the Shapes_Name and Shapes_Files

attributes for the POM_alternateSR_userdata object.
Extensions for Microsoft Office Guide

The following release note pertains to the Extensions for Microsoft Office Guide.
The 32-bit version of Microsoft Office 2010 is certified for live Excel and live Word.
Note
– Other Office versions are not supported, including Office 2003 with
the compatibility pack for the Word, Excel, and PowerPoint 2007 file
formats.
Frequently Asked Questions for Teamcenter

The following release note pertains to the Frequently Asked Questions for Teamcenter.
• Can I use instant messaging in Teamcenter?
If the functionality is enabled at your site, Teamcenter rich client and thin client
users can use Microsoft Office Communicator when other users are available
for instant messaging.
Teamcenter users can view the current status of the owning and last modified
users, and, from within a Teamcenter application, can initiate communication
using Microsoft Office Communicator.
For more information about enabling this functionality, see the Application

Release notes
Getting Started with Electronic (EDA) Lifecycle Management

The following release note pertains to the Getting Started with Electronic (EDA)
Lifecycle Management.
In the Export part library using rich client topic, replace step 7 with the following:
7. Click OK to start the export.
A briefcase file is created, which contains a TC XML file and all the data files
associated to the published parts. The TC XML file contains the metadata of the
EDA parts and their related objects.
Getting Started with Manufacturing

The following new topics will be added to the Getting Started with Manufacturing
and pertain to the Manufacturing Resource Library.
Setting access rights

When setting up resource management, Siemens PLM Software recommends you
create one group, for example, a manufacturing group, for all users involved with
resource management. Using this group, you can set up custom read and write
privileges for the group, as well as defining group-specific workflows and business
rules. You should import the Manufacturing Resource Library (with tools and
machines) using this group.
Enable graphics creation

An administrator typically performs this step.
1. In the Teamcenter Environment Manager (TEM), install the Teamcenter
Integration for NX.
2. Restart TEM and install the graphics builder by selecting the NX Graphics
Builder option in the NX Integration section.
3. Run the Manufacturing Resource Library setup program in the

advanced_installations\resource_management\server directory of the
installation image.
For more information about installing the Manufacturing Resource Library with
this option, see the Installation on Windows Servers Guide.
4. Select the Manufacturing Resources — Database Population option and provide

the appropriate input to import tools until you reach the Support GRAPHICS
BUILDER step.
5. Select Tools.
This step installs the part family templates required to create graphics for the
tool components found in the Manufacturing Resource Library.
6. Complete the installation.

Note
When you create graphics using the graphics builder, all part family members
are created with the same item type as the part family template. Therefore,
ensure that your part family templates are of the same item type as the one
you specified during the Manufacturing Resource Library import.
Building tool assemblies
When building new tool assemblies in Resource Manager, search first in your
customer hierarchy to find existing components that you can reuse. If you do not
find any, continue to search in the vendor catalog, and then map that component to
the customer hierarchy.
The following chart shows the approach that enables the maximum amount of reuse
of existing material.
Build a tool assembly
1. Create a new item that represents the root of the new assembly structure by
choosing File→New→Resource or clicking .
2. Specify the item type, for example, MENCTool.
3. Search for components to build the tool structure. You must start with the
machine-side component—that is, a machine adapter or tool holder—and work
toward the cutter or workpiece side.

Release notes
1. Select the parent component below which you want to add the next
component.
2. Search for the next component using the Classification Search Dialog and
click OK.
Tip
Turn on the graphical browser for a more visual search experience.
For more information, see Viewing the tree graphically in the
Classification Administration Guide.
Teamcenter displays the new component as a child of the selected component.
For more information about searching the classification hierarchy, see the
Resource Manager Guide.
3. (Optional) If you put a component in the wrong position in the hierarchy, or

prefer to search in a different order from the assembly structure (for example,
search for the cutter first), cut and paste components to the correct position in
the tool assembly.
4. Attach the propagation start point (PSP) to the cutter by selecting the cutter
and clicking .
5. Click Save .
Teamcenter saves the assembly and propagates the defined attribute values from
all components, starting at the propagation start point (in this case, the cutter),
to the assembly root node. The following figure shows the propagated attributes
in italic font.


Release notes
Note
This procedure works correctly for all existing tool assembly classes in the
Manufacturing Resource Library. If, however, your administrator adds new
classes to the classification hierarchy, the class in which you classify the
resource assembly must be specified as an assembly class in the Classification
Administration application. In addition, the attributes that you want to
propagate to the root node must have the Propagated Property option selected
in the resource assembly class in Classification Administration.
For more information, see the Classification Administration Guide.
Understanding propagated attributes
The following table demonstrates attribute propagation. In this example, the

Test Assembly 1 class is specified to be an assembly class in Classification
Administration. Furthermore, in the assembly class, Attributes 1–5 have the
Propagated Property option selected.
When Teamcenter propagates attributes, it begins at the propagation start point

(PSP), and then travels upward through each parent looking for attributes to
propagate. In the example, the first component it looks at is Component 4. It
contains Attribute 4, which is a propagated attribute, so Teamcenter propagates
Attribute 4 to the resource assembly, Test Assembly 1. Teamcenter then looks at
the parent of Component 4, Component 3, and finds two attributes to propagate.
It then looks at the parent of Component 3, Component 1, and finds Attribute 2
to propagate. Component 1 also contains Attribute 1, but this value has already
been populated by Component 3. When Teamcenter is finished with propagating
attributes, the top-level resource assembly, Test Assembly 1, shows the following
attribute values:
Attribute Propagated from

Attribute 1 Component 3
Attribute 5 contains no value. Although there is a value assigned to this attribute in

Component 2, Component 2 does not lie within the propagation path as it is not
a parent or grandparent of Component 4, the propagation start point. Similarly,
Components 6 and 7 do not lie within the propagation path.

A gray PSP indicates that this PSP is defined in the context of a subassembly. It
is not taken into consideration in the current tool assembly. Subassemblies are
highlighted with a colored background in Resource Manager.
Map vendor catalog tools to customer hierarchy

1. Select the class in the vendor catalog hierarchy that you want to map to a
customer class.
2. Search for and select the appropriate ICO from the vendor class.
3. Click .
4. If there are multiple possible target classes specified in the mapping definition,
the Target Class Selection dialog box is displayed:
a. Choose the desired target class from the list.
b. Click OK.
The New Item dialog box is displayed.
5. Type a unique identifier for the new item in the Item ID box adhering to your
company’s naming conventions or let Teamcenter automatically create a name
for you by clicking Assign.
6. Type a name in the Name box.
7. Select the correct item type from the list, for example, MENCTool.
8. Click OK.
Teamcenter creates a new ICO and item in the customer class and maps attributes
from the vendor class to attributes in the customer class as specified by the mapping
definition in Classification Administration. The new ICO is displayed in the
customer class and its attributes are shown in the Properties pane.
Install NX templates
If you have an empty database with no NX templates installed, you must install
these templates before you can work in the manufacturing environment.
Warning
Do not perform this procedure if you already have templates stored in the
database. They will be overwritten.
Before you perform this step, ensure that the UGSTRUCTURES feature is installed
in your NX installation. When you complete this procedure, the NX templates are
available the first time you enter NX.
1. Open a Teamcenter command prompt window.
2. Type:
cd /d "%UGII_ROOT_DIR%\templates\sample"
tcin_template_setup -u=user -p=password

Release notes
Enable tool retrieval from Teamcenter to NX

An administrator typically performs this step.
1. In the Teamcenter Environment Manager, install the Teamcenter Integration
for NX.
2. Run the Manufacturing Resource Library setup program in the

advanced_installations\resource_management\server directory of the
installation image, selecting the Configure NX Library option.
This step copies the cam_part_planner_mrl.dat configuration file to the
MACH\resource\configuration directory in your NX installation.
Retrieve a tool fromTeamcenter in NX

An NC programmer typically performs this step.
1. If you have not opened a part in NX before, initialize the manufacturing
environment.
a. In NX, create a new part and choose Start→Manufacturing.
NX displays the CAM Session Configuration dialog box.
b. Select cam_part_planner_mrl from the list of possible configurations.

NX displays the Library Class Selection dialog box.
c. Select a CAM operation setup template.
2. Open the machine tool view.
3. Click Create Tool or double-click the root machine.
4. Click Retrieve Tool from Library.

The Library Class Selection dialog box is displayed. This lists the tool assembly
classes found in the Manufacturing Resource Library hierarchy that is stored
in the Teamcenter database.
5. Select the class in which you want to search.

NX displays the Search Criteria dialog box containing a list of attributes
belonging to the class that you selected in the previous step.
6. Narrow your search by entering parameters in the dialog box and click OK.
NX displays a list of results.
7. Select the desired tool assembly and click OK.
Getting Started with Teamcenter

The following release notes pertain to Getting Started with Teamcenter.
In the Data sharing topic, replace the last sentence with the following:
Additionally, Data Exchange supports exporting data in PDX format and can import
and export to any system that supports TC XML format.

Installation on UNIX and Linux Clients Guide

The following release note pertains to the Installation on UNIX and Linux Clients
Guide.
• Four-tier rich client displays logon error in HTTPS mode on Solaris
In Troubleshooting, add the following row to the table of troubleshooting
solutions:
Problem Possible cause Solution

Logon to the The rich client logon cannot 1. Copy your security
four-tier rich client find a valid security certificate certificate into
on Solaris fails in and displays an error similar the keystore for
HTTPS mode to the following: the Java Runtime
Environment
Login was
unsuccessful,: Problems (JRE) used by
encountered logging into the Over-the-Web
TCServer:TcWeb1 Installer for the rich
cause: com.teamcenter.soa. client.
client.SoaRuntimeException:
sun.security.validator.
ValidatorException:PKIX 2. Rebuild and
path building failed: redeploy your rich
sun.security.provider.
certpath.
client distribution
SunCertPathBuilderException: instance.
Unable to find valid
certification path to
requested target
Installation on UNIX and Linux Servers Guide

The following release notes pertain to the Installation on UNIX and Linux Servers
Guide.
• APP_SERVER_PORT context parameter is obsolete
In Web tier context parameters, under Ode BPEL Web application parameters,
remove the row in the table about the APP_SERVER_PORT context parameter.
This parameter is no longer included in Teamcenter.
• DB2 database creation commands are incorrect

In Database server installation®Create a DB2 database for Teamcenter,
some DB2 Command Line Processor commands are incorrect. Correct these
commands as follows:
– Replace the contents of the Create a DB2 Teamcenter database topic with
the following:
Using the DB2 Command Line Processor, enter the following command:
CREATE DB db-name AUTOMATIC STORAGE YES ON ’path’ USING CODESET
UTF-8 TERRITORY US PAGESIZE 32 K

Release notes
Replace db-name with the name or alias of the database to be created.

Replace path with the path or drive on which to create the database.
This is also the storage path or drive associated with the database.
For example:
CREATE DB tcdb2 AUTOMATIC STORAGE YES ON ’D:’ USING CODESET
– In Set DB2 database configuration parameters, replace the command line

example with the following:
UPDATE DB CFG FOR db-name USING STMTHEAP 100000
• Corrections to titles for Common Licensing Server guides

In Teamcenter server installation®Teamcenter preinstallation tasks®Install the
licensing server, replace the last paragraph with the following:
For more information about the Siemens PLM Software Common Licensing
Server, see the Installing Siemens PLM Software Licensing for UNIX, Installing
Siemens PLM Software Licensing for Windows, and Siemens PLM Common
Licensing User Guide documents in the additional_documentation directory
on the Teamcenter 8.3 documentation distribution image.
• Corrections to online help installation steps

In Adding features®Installing Teamcenter online help®Configure online help
access®Configure online help for the rich client using Web Application Manager,
delete steps 4 and 5.
Installation on Windows Clients Guide

The following release note pertains to the Installation on Windows Clients Guide.
• Client for Office and Integration for Office should not be installed on
the same host
In Installing Microsoft Office interfaces®Installing Teamcenter’s Client for
Microsoft Office, replace the note with the following:
Note
Teamcenter’s Client for Microsoft Office and Teamcenter’s Integration for
Microsoft Office should not be installed and used on the same computer.

Installation on Windows Servers Guide

The following release notes pertain to the Installation on Windows Servers Guide.
• APP_SERVER_PORT context parameter is obsolete
In Web tier context parameters, under Ode BPEL Web application parameters,
remove the row in the table about the APP_SERVER_PORT context parameter.
This parameter is no longer included in Teamcenter.
• Path to DB2 redistributable client is incorrect

In Database server installation®IBM DB2 installation and configuration®Install
IBM DB2®Install the DB2 redistributable client, replace the second paragraph
with the following:
To install these drivers, browse to the additional_applications\db2_files
directory in the Teamcenter 8.3 software distribution image and double-click the
setup_DSDRIVER.exe program icon. Proceed through the installation wizard,
accepting the default settings.
• DB2 database creation commands are incorrect

In Database server installation®Create a DB2 database for Teamcenter,
some DB2 Command Line Processor commands are incorrect. Correct these
commands as follows:
– Replace the contents of the Create a DB2 Teamcenter database topic with
the following:
Using the DB2 Command Line Processor, enter the following command:
CREATE DB db-name AUTOMATIC STORAGE YES ON ’path’ USING CODESET
Replace db-name with the name or alias of the database to be created.

Replace path with the path or drive on which to create the database.
This is also the storage path or drive associated with the database.
For example:
CREATE DB tcdb2 AUTOMATIC STORAGE YES ON ’D:’ USING CODESET
– In Set DB2 database configuration parameters, replace the command line

example with the following:
UPDATE DB CFG FOR db-name USING STMTHEAP 100000

In Teamcenter server installation®Teamcenter preinstallation tasks®Install the
licensing server, replace the last paragraph with the following:
Server, see the Installing Siemens PLM Software Licensing for UNIX, Installing
Siemens PLM Software Licensing for Windows, and Siemens PLM Common
Licensing User Guide documents in the additional_documentation directory
on the Teamcenter 8.3 documentation distribution image.

Release notes
• Corrections to online help installation steps

In Adding features®Installing Teamcenter online help®Configure online help
access®Configure online help for the rich client using Web Application Manager,
delete steps 5 and 6.
Manufacturing Process Planner Guide

The following release note pertains to the Manufacturing Process Planner Guide.
Configuring a 3D PDF report

To assist you in creating work instructions, you can generate a 3D PDF report that is
based on a template that an administrator creates with Adobe Live Cycle Designer.
By default, Teamcenter delivers a template that includes:
• Assembly steps (operation list)
• Description (displayed according to the assembly step selected from the list
of assembly steps)
• Consumed parts (displayed according to the assembly step selected from the
list of assembly steps)
• Assigned tools (displayed according to the assembly step selected from the list
of assembly steps)
• Graphical window that displays 3D data with all the graphical capabilities such
as zoom, rotate, pan, and animation
• Toolbar that includes:

– Mouse functions (such as rotate or zoom)
– List of views (snapshots) available
– Toggle mode tree button
– Render mode
– Lighting
The toolbar is common to all reports.
You can modify this template or create a new one to reflect your needs.
The 3D PDF report is a monolithic file that can easily be viewed on any desktop that
has the free Acrobat Reader installed. The report is rich with dynamic views and
3D data and is, therefore, self-explanatory and can reduce errors. You can use it to
fulfill various needs from basic collaboration between different departments to shop
floor work instructions.
Note
Operation names must be unique in the process structure.

Find this preview feature in the Manufacturing Process Planner. This feature will
become available in Teamcenter 9.0.
Install the prerequisite software

1. Install Adobe Acrobat Pro Extended 9.3.3.
For more information, see the Adobe installation documentation.
2. Install Teamcenter’s lifecycle visualization for Teamcenter 8.3 using the

stand-alone installer.
For more information about installing this product, see the Teamcenter Lifecycle
Visualization Installation Guide.
When installing, select the following install features:
• MockUp
• VisAutomationApp
• Convert & Print
• Help & Miscellaneous Features
Preinstallation tasks
1. In the Teamcenter installation, locate the following file:
additional_applications\tcmfggen3dpdf\tcmfggen3dpdf.zip
1. Create a directory to use for this procedure, for example,

3DPDF_installation_root.
2. Copy the tcmfggen3dpdf.zip file to 3DPDF_installation_root and extract it.
3. Set the following user environment variable:

ME3DPDFReportInstall=3DPDF_installation_root
4. If you use the sample files provided in the installation, set the following
environment variable:
TCVIS_DEFAULT_PRCFILE_PATH=3DPDF_installation_root\template
\TC\sample1
5. Copy 3DPDF_installation_root\bin\libtcmfggen3dpdfacro.api to
Acrobat_pro_installation_root\Adobe\Acrobat9.0\Acrobat\plug_ins.
6. Copy 3DPDF_installation_root\javascript\tcmfg3dpdf_acrodefs.js to
Acrobat_pro_installation_root\Adobe\Acrobat 9.0\Acrobat\Javascripts.
7. Start Adobe Acrobat Pro.
8. Exit Adobe Acrobat Pro.

Release notes
Install the 3D PDF report
1. Start the Teamcenter rich client.
2. Set the ME3DPDFReportEnable preference to TRUE.
3. Create a dataset, myPDFDataset, of the PDF type.
4. If you use the PDF templates provided in the installation, import the
3DPDF_installation_root\template\TC\sample1\3DPDF_DefaultTemplate.pdf
file into the dataset.
5. Create a dataset, myStyleSheetDataset, of the CrfXmlStyleSheet type.
6. If you use the PDF templates provided in the installation, import the
3DPDF_installation_root\template\TC\sample1\Structured_PLMXML.xsl
file into the dataset.
7. Create the ME3DPDFReportTemplates preference.

• Scope = Site
• Multiple Values = True
• Type = String
• Values =
DisplayName,myPDFDataset,myStyleSheetDataset,TransferModeName
Where Is
DisplayName The name that is displayed in the PDF
Template list in the Generate 3D PDF
Report dialog box in Teamcenter.
myPDFDataset The dataset you created in step 3.
myStyleSheetDataset The dataset you created in step 5.
TransferModeName The name of the transfer mode used to
collect data for the report.
If you use the templates provided with
the installation, this is the tcm_export
transfer mode.

Verify installation
1. Open a command prompt.
2. Type:
cd 3DPDF_installation_root\bin
tcmfggen3dpdf -h -std
The executable should display help to standard out. If it does not, contact your
Siemens PLM Software technical support representative.
Locating the log file

The log file is located in your %temp% directory. The log file has the following format:
TcMfgGen3DPDF_xxxxx_yyyyy.txt
xxxxx and yyyyy are random numbers.
Create a 3D PDF report

• Choose Tools→Generate 3D PDF Report.
• Select the report to generate.
• Click OK.
Teamcenter generates the 3D PDF report.
Install live PRC export mode with Lifecycle Visualization

You must complete all other installation tasks before performing this procedure.
You only perform this procedure once.
1. Open the following file in a text editor:
Lifecycle Visualization_installation_root_directory\Program\modules.txt
2. Add the following entries, modifying the path to match your installation.
TcVis 8.3 VMU|Lifecycle Visualization_installation_root\Program\ExportStubPRC.dll
TcVis 8.3 VMU|Lifecycle Visualization_installation_root\Program\ExportPRCProto.dll
3. Copy 3DPDF_installation_root\bin\ExportStubPRC.dll to Lifecycle

Visualization_installation_root\Program.
4. Copy 3DPDF_installation_root\bin\ExportPRCProto.dll to Lifecycle

Visualization_installation_root\Program.
5. In the Lifecycle Visualization_installation_root\Program directory, drag

modules.txt to PostReg.exe.
Teamcenter begins registering the modules listed in the modules.txt file.
6. In the Lifecycle Visualization_installation_root\Products\VisAutomationApp

directory, double-click VisAutomationApp.exe.

Release notes
7. After VisAutomationApp.exe has started and run for about 15 seconds, start
the Windows Task Manager and stop the VisAutomationApp process.
Switch between live and stub operation modes

There are two modes of operation available for the 3D PDF.
• In stub mode, the 3D PDF process uses the graphic input files found in the
location specified by the TCVIS_DEFAULT_PRCFILE_PATH environment
variable.
• In live mode, the 3D PDF process generates the PRC and XFDF files from the
Teamcenter structure and product views.
Each mode is supported by a different GraphicsExporter.dll library. By

default, Teamcenter installs the stub mode GraphicsExporter.dll library in the
3DPDF_installation_root\bin directory.
• To switch to live export mode:
1. Perform the installation steps in Install live PRC export mode with Lifecycle
Visualization, if you have not already done so.
2. Copy 3DPDF_installation_root\bin\live\GraphicsExporter.dll to
3DPDF_installation_root\bin.
• To switch back to the stub export mode, copy

3DPDF_installation_root\bin\stub\GraphicsExporter.dll to
3DPDF_installation_root\bin.
Multi-Site Collaboration Guide

The following release notes pertain to Multi-Site Collaboration Guide.
In the Set up multiple IDSM daemons on a single server topic, replace the note
is step 10 with the following:
Note
You must type the full path name, not the environment variable substitution
%TC_ROOT%. The name of the run_tc_idsm batch file must match the
service name, for example, run_tc_idsm_chicago.bat and service name
gs_idsm_chicago.

Organization Guide
The following release note pertains to the Organization Guide.
• Defining users
The following will be added to the Create a user topic.
Note
– Do not use the delimiters defined in the TC_user_delimiters
preference when entering user information in either the Person Name
box or the User ID box. (If the TC_user_delimiters preference is not
set, parentheses ( ) are the default delimiters.) Otherwise, the user
name and user ID appear incorrectly in the Organization List tree.
– If you inadvertently use the characters set in the TC_user_delimiters

preference when you create a user or a person, use the make_utility
utility to correct the user ID and person name delimiters.
Platform Designer Guide

The following release note pertains to the Platform Designer Guide.
Replace the Set a variant rule topic with the following:
In Structure Manager, part solutions are displayed under a LOUHolder object.
Therefore, part solutions are immediately configured when you impose a variant
rule. Platform Designer, however, displays part solutions under their architecture
breakdown element, which is not actually their parent node. The LOUHolder object
is hidden in Platform Designer. For this reason, you must show the part solutions to
configure the structure after you impose the variant rule.
• Choose Tools→Variants→Configure Variants.
• Click Variant Rule on the toolbar. .
The options and values displayed in the dialog box are limited to those set on the
top-level architecture.
2. Display the VOC – Variant Occ Config’d column. This displays the following:
• Y – the line is configured.
• Blank – the line is not configured.
• ? – all the options in the variant condition on the line have not been set in
the variant rule.
3. Display unconfigured part solutions by turning off the View→Unconfigured

Variants menu command.
This is turned on by default.
4. Show the part solutions by clicking the Show/Hide Part Solutions button.

Release notes
Teamcenter displays the part solutions under the architecture breakdown

elements.
5. Configure part solutions.

1. Apply a variant rule.
2. Turn off the View→Unconfigured Variants menu command.
Note
If you apply a new variant rule, changing the existing one, the configured
part solutions (that are configured according to the old variant rule) are
lost. You must click Show/Hide Part Solutions again to see the newly
configured part solutions.
3. Unconfigure part solutions.

1. Turn on the View→Unconfigured Variants menu command.
2. Click Show/Hide Part Solutions.
This allows you to view the unconfigured part solutions under the architecture
breakdown element.
PLM XML Export Import Administration

The following release note pertains to the PLM XML Export Import Administration
Guide:
• The JTDataExportDefault and JTDataImportDefault transfer modes
described in the Working with transfer mode objects topic will be removed. Do
not use these transfer modes, related closure rules, filter rules, or action rules
in any of your PLM XML export/import scenarios. In addition, do not use any
custom code that uses these transfer modes.
For more information, see the obsolete feature announcement in Support and
certification announcements.

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.
• MENEWMFG_DefaultDatumJTDatasetName
The MENEWMFG_DefaultDatumJTDatasetName preference was previously
undocumented. It will be added under the Teamcenter’s manufacturing process
management preferences topic.
• MENEWMFG_DefaultWeldPointJTDatasetName
The name of the MENEWMFG_DefaultJTDatasetName preference is
changed to MENEWMFG_DefaultWeldPointJTDatasetName.
• OCS_use_presence_display
The default value for the OCS_use_presence_display is changed to false.
With the default setting, the Teamcenter integration with Microsoft Office
Communicator functionality is not enabled.
• REQ_default_object_template
The REQ_default_object_template preference was previously undocumented.
It will be added under the Requirements Manager preferences topic.
• REQ_default_spec_template_for_export
The REQ_default_spec_template_for_export preference was previously
undocumented. It will be added under the Requirements Manager preferences
topic.
• REQ_default_spec_template_for_view
The REQ_default_spec_template_for_view preference was previously
undocumented. It will be added under the Requirements Manager preferences
topic.
• REQ_import_keywords
The REQ_import_keywords preference was previously undocumented. It will
be added under the Requirements Manager preferences topic.
• SM_PV_FILTER_SHOW_SCHEDULES_ON_EMPTY
The SM_PV_FILTER_SHOW_SCHEDULES_ON_EMPTY preference was
previously undocumented. It will be added under the Schedule Manager
preferences topic.
• TC_show_checkedout_icon
The default value for the TC_show_checkedout_icon is changed to False.
With the default setting, the checked-out symbol is not displayed in the Structure
Manager and My Teamcenter views. This reduces network and database activity
and therefore improves performance compared to the alternate value.

Release notes
• TC_relation_export_on_transfer preference
The TC_relation_export_on_transfer preference preference is restricted
to interpart relations.
• WEB_Enable_Create_Change
The WEB_Enable_Create_Change preference determines whether
the New→Change→Create, New→Change→Context Create, and
New→Change→Derived Change menu commands are displayed in the thin
client.
MENEWMFG_DefaultDatumJTDatasetName
DESCRIPTION
Specifies the name of the JT dataset that is attached by default to every newly
created datum at import.
VALID
VALUES
The Teamcenter business object type, followed by the control direction and dataset
name, in the following format:
type:control_direction:datasetname
DEFAULT
VALUES
measurement:default:dsname
sphere:default:dsname
pin:default:dsname
SCOPE
Site preference.
REQ_default_object_template
DESCRIPTION
Specifies the default object template for exporting object data to Microsoft Office
Word. An object template determines the data that is exported for each object type.
VALID
VALUES
The name of an existing object template.
DEFAULT
VALUES
Note
This default template is provided with the Teamcenter installation.
SCOPE
Site preference.

REQ_default_spec_template_for_export
DESCRIPTION
Specifies the default specification template for exporting object data to Microsoft
Office Word. This specification template determines the overall layout of the Word
document that is generated during the export process.
VALID
VALUES
The name of an existing specification template.
DEFAULT
VALUES
REQ_default_spec_template
Note
SCOPE
Site preference.
REQ_default_spec_template_for_view
DESCRIPTION
Specifies the default specification template for editing and viewing requirement
content in the Requirements Manager MS Word pane. This specification template
determines the overall layout of the Microsoft Office Word document that is
embedded in the pane.
VALID
VALUES
The name of an existing specification template.
DEFAULT
VALUES
REQ_default_spec_template_for_view
Note
SCOPE
Site preference.
REQ_import_keywords
DESCRIPTION
Defines a list of keywords for importing requirement specifications from Microsoft
Office Word to Requirements Manager. The list contains keywords that occur
in import documents. According to these keywords, the import process parses
Word documents into multiple levels of requirements in requirement specification
structures.

Release notes
VALID
VALUES
Accepts one or more strings as values. Use a comma (,) to separate adjacent strings.
Note
• Strings cannot contain colons (:) or commas.
• Strings containing spaces between characters are processed as single

keywords.
• There is no maximum number of characters per string.
• There is no maximum number of strings.
DEFAULT
VALUES
None.
SCOPE
Site preference.
SM_PV_FILTER_SHOW_SCHEDULES_ON_EMPTY
DESCRIPTION
Indicates whether to display empty schedules.
VALID
VALUES
TRUE
FALSE
DEFAULT
VALUES
TRUE
SCOPE
Site preference.
TC_relation_export_on_transfer
The following restriction pertains to the TC_relation_export_on_transfer
preference.

Restrictions
Caution
This preference is intended to be used for interpart relations, for example,
related objects in NX. To avoid potential problems, do not use any of the
following relations in this preference:
• IMAN_aliasid
• IMAN_master_form
• IMAN_based_on
• IMAN_RES_checkout
• IMAN_RES_audit
• TC_sst_rtype
• TC_checkpoint_rtype
• IMAN_MEAppearance
• IMAN_MERequiredAppr
• IMAN_METarget
• IMAN_MEWorkArea
• IMAN_MEComponent

Release notes
Report Builder Guide

The following release notes pertain to the Report Builder Guide.
• In the Create a summary report definition topic, replace step 3g with the
following:
g. Click the arrow in the Report Format box to select the format for the report,
PLMXML or TCXML.
Select TCXML to see all the Teamcenter attributes. Select PLMXML to see
attributes displayed in PLM XML industry standard names.
• In the Create and item report definition topic, replace step 3g with the following:
g. Click the arrow in the Report Format box to select the format for the report,
PLMXML or TCXML.
Select TCXML to see all the Teamcenter attributes. Select PLMXML to see
attributes displayed in PLM XML industry standard names.
Requirements Manager Guide

The following release note pertains to the Requirements Manager Guide.
The 32-bit version of Microsoft Office 2010 is certified for Requirements Manager.
With Word 2010, for example, you can edit and view requirement content in
an embedded Word window in the MS Word pane, and you can import and
export requirement specification structures. Using Excel 2010, you can export
requirement specification structures to live and static Excel files.
Note
– The MS Word pane displays only Word 2010 and 2007 content.
– Office 2003 (with the compatibility pack for the Word, Excel, and
PowerPoint 2007 file formats) is supported as follows:
◊ Requirements can be opened only in separate Word windows.
◊ Objects can be exported to Excel and Word only in the Static

Snapshot output mode.
– Other Office versions are not supported.

Rich Client Customization Programmer’s Guide

The following release notes pertain to the Rich Client Customization Programmer’s
Guide.
• Removal of action sets
Beginning with Eclipse 3.5, the menu contribution method made the use of
action sets obsolete. Therefore, all references to action sets (seen as ActionSet
in code examples) will be removed from the following topics:
– Teamcenter extension points
– Create a custom Java form assigned to the ItemRevisionMaster form
– Localization of rich client customizations
Rich Client Interface Guide

The following release notes pertain to the Rich Client Interface Guide.
• Adding users to notification lists
The Receiving notification of checkout status topic contains a note that incorrectly
states that users with administrative privileges can add other users to a
notification list. Users with administrative privileges cannot add other users to
a notification list.
• Dataset implicit checkout

The following note will be added to the Using implicit checkout topic:
Note
When a dataset that has no attached files, if you double-click the dataset
or select the dataset while the Viewer view is active, the dataset properties
are displayed, but there is no implicit checkout.
• Using the Viewer view

The following notes will be added to the Using the Viewer view topic:
– Clicking the Save button in the Viewer view does not save a dataset
If you edit a Microsoft Word dataset in the My Teamcenter Viewer view
and click the Save button on the Word toolbar within the Viewer pane, the
changes are not saved to the dataset. You must click the Save button at the
top of the Viewer view. (The Save button on the Word toolbar within the
Viewer pane saves the document to the client machine but does not save
the dataset.)
– Saved changes in Microsoft Office do not appear in the dataset

If you open a Microsoft Office dataset in the Viewer view and then open it
in the Microsoft Office application by double-clicking the dataset while it is
still open in the Viewer view, changes made and saved in the application are
not saved to the dataset. To avoid this, make changes in the Viewer view or
use Teamcenter’s Integration for Microsoft Office.

Release notes
Note
You can have a dataset file open in the Viewer view and then
double-click it in a component or Details view to edit the file outside
Teamcenter, or in Microsoft Excel or Notepad, for example. Changes
are not shown in the Viewer view until you exit the external
application, reload the Viewer view by clicking another object, and
then clicking the edited object.
– Microsoft Office documents open externally instead of in the Viewer

view
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 view, the document is
opened externally in its application (for example, in PowerPoint) and not
embedded in the Viewer view.
This occurs because, 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.
◊ 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
◊ 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.
7. Click OK.
8. Repeat steps 4–6 for the DOCX, PPT, PPTX, XLS, and XLSX
extensions.
– Clicking the Save button in Viewer pane does not save dataset
If you edit a Microsoft Word dataset in the My Teamcenter Viewer view
and click the Save button on the Word toolbar within the Viewer view, the
changes are not saved to the dataset. (The Save button on the Word toolbar
within the Viewer pane saves the document to the client machine but not
the dataset.)

To save the dataset, click the Save button at the top of the Viewer view.
– Opening a Microsoft Excel file in the Viewer view when the file is
already open in Microsoft Excel results in an warning message
By default, Microsoft Excel locks files when the files are opened.
To edit a Microsoft Excel file both inside and outside Teamcenter, you must
open the file in the Viewer view first, as follows:
1. Exit the external Microsoft Excel program.
2. Open the Excel file in the Viewer view, and edit the file.
3. (Optional) Open the Excel outside Teamcenter.
Schedule Manager Guide

The following release notes pertain to the Schedule Manager Guide.
• Getting started
The following preference will be added to the Setting preferences topic.
The SM_PV_FILTER_SHOW_SCHEDULES_ON_EMPTY preference
indicates whether to display empty schedules.
When set to TRUE, empty schedules appear. If you do not want to see the empty
schedules, set it to FALSE.
Server Customization Programmer’s Guide

The following release notes pertain to the Server Customization Programmer’s Guide.
• Create and save paradigm
The following note will be added to the The create operation topic.
Note
The create operation logically creates objects and the save operation
commits the changes to the database. This pattern must be followed
whenever Item object creation is initiated. Following this pattern
requires that any postactions on the create operation should not assume
the existence of the objects in the database. If database interactions like
queries or saving to the database are needed in the postactions, they
must be attached as a postaction to the save message and not the create
message. The save message could be initiated following the create or
modify operation. There is a mechanism to distinguish between the two
cases.
In a future version of Teamcenter there will be a requirement that the
postactions of the create operation should not access the database, and if
any such postactions are found, they must be moved or refactored to the
save operation. The refactoring guidelines will be provided in that version
of Teamcenter.

Release notes
Structure Manager
The following release notes pertain to the Structure Manager Guide.
• The following notes will be added to the Defining units of measure topic.
– When you add a line to the structure, its unit of measure (UOM) is initially
the same as the default UOM for the corresponding item type. You can
subsequently change the UOM of the line, if appropriate.
– If the default UOM of the item is not each, you cannot change the UOM of
the line to each.
– Teamcenter considers the UOM of the line when displaying a quantity value.
If the UOM of the line is each, it displays the quantity value as an integer;
otherwise, it displays a floating (real) value.
Note
When customizing Teamcenter, the special UOM value each is
reserved. If you add another each value, the default Teamcenter
behavior may change.
• The caution in the Create a structure rollup report template topic will be updated
as follows:
Caution
Depending on the report data, certain delimiters cause the columns to be
misaligned when viewed, for example, space and semicolon characters.
Teamcenter displays a warning if this occurs.
System Administration Guide

The following release note pertains to the System Administration Guide.
• Configuring native FSC client proxy in TcServer
The native implementation uses cURL and OpenSSL and requires a compatible
cacerts file. Use one of the following methods to generate a cacerts file that
contains the required certificates.
Note
This cacerts file must be in privacy enhanced mail (PEM) format (which
is not the same format as the Java cacerts file).
– Download the cacerts file.

If your certificate authority (CA) signer is well known, the certificates may
be available from the Internet. Siemens PLM Software recommends you
contact your internal security team.

1. Download a current ca-bundle.crt file from the Internet, or get the

file from your internal security team. The file must be compatible with
cURL and OpenSSL.
The file must contain the certificate chain that can validate the FSC
certificate.
2. Name the file cacerts and save it in the TC_ROOT/bin directory.
– Generate a cacerts file based on the installed Java cacerts file.

If your CA signer certificates are in the Java cacerts file, you can extract
them for cURL and OpenSSL.
1. Extract the trusted certificates in the Java cacerts file in the PEM
format that cURL and OpenSSL requires. For example (Windows):
cd /d %JAVA_HOME%\jre\lib\security
del /q cacerts.pem cacerts.list export.pem
keytool -keystore cacerts -storepass changeit -list | find "trustedCertEntry" | sort >
cacerts.list for /f "delims=, tokens=1" %f in (cacerts.list)
do keytool -export -rfc -alias %f -keystore cacerts -storepass changeit
-file export.pem & echo %f >> cacerts.pem & type export.pem >> cacerts.pem
del /q cacerts.list export.pem
2. Save the file in the TC_ROOT/bin directory.
– Generate a cacerts file with only the certificates required by your CA.
If your CA used new certificates, you must also acquire the signer certificates
from your CA. These must be contained within the cacerts file.
1. Acquire the signer certificates, in PEM format, from your CA.
2. Append the signer certificates into a cacerts file.
3. Save the file in the TC_ROOT/bin directory.
The client (native implementation in TcServer) is now able to communicate

with the FSC.

In Administering Teamcenter licenses, replace the last paragraph with the
following:
Server, see the Siemens PLM Common Licensing User Guide in the
additional_documentation directory on the Teamcenter 8.3documentation
distribution image.

Release notes
Teamcenter Publish
The following release note pertains to the Manufacturing Process Planner Guide,
the Part Planner Guide, the Multi-Structure Manager Guide, the Resource Manager
Guide, the Plant Designer Guide, and the Service Planner Guide.
The following prerequisite information for using Teamcenter Publish replaces the
existing information in the Using Teamcenter Publish topic.
To create or view manufacturing documentation using Teamcenter Publish, install
Microsoft Visio 2007 SP1 or Visio 2010 (32–bit only). Both Visio Standard and Visio
Professional are certified. You can install Visio before or after the Teamcenter
installation. Optionally, with Visio 2007 SP2, you can install the Microsoft Office
2007 Save as PDF add-in, which you can download from:
http://r.office.microsoft.com/r/rlidMSAddinPDFXPS
The Save as PDF feature is included with Visio 2010 and does not require installing
the separate PDF add-in.
Thin Client Interface Guide

The following release notes pertain to the Thin Client Interface Guide.
• Enabling Change Manager
The following note will be added to the Working with change objects topic.
Note
To enable Change Manager menu commands, set the
WEB_Enable_Create_Change preference to true.
• Managing basic data

The following change will be made to the Revise an item topic.
Step 4 will be changed from:
– Click OK or Apply to create the new item revision.
To:
– Click OK to create the new item revision.
• Managing basic data

The following change will be made to the Revise an item revision topic.
Step 4 will be changed from:
– Click OK or Apply to create the new item revision and copy the references to
the objects under it.
To:
– Click Finish to create the new item revision and copy the references to the
objects under it.

• Managing workflows
The following topics will be added to Managing workflows.
Create and edit process assignment lists
When you create a process assignment list (PAL), you set up a list to be used
repeatedly, similar to an e-mail list you set up to help distribute e-mail more
easily. This predefined list helps you assign tasks to specific users in any given
workflow process.
1. Choose Tools→Process Assignment Lists→Create/Edit.

The system displays the Create/Edit Process Assignment Lists dialog box.
2. Type a name for the list in the Name box.
3. Select the list type:
a. Select New to create a new PAL.
b. Select My Lists to add the PAL to your lists.
c. Select My Group Lists to add the PAL to your group lists.
d. Select Other Lists to add the PAL to another list.
4. Select a template from the Process Template list to associate with the PAL.
The system displays actions based on the task type you select. For example,
if a Route task is selected, the Review, Acknowledge, and Notify actions are
displayed. If a Review task is selected, only the Review action is available; if
an Acknowledge task is selected, only the Acknowledge action is available.
5. Select Assign for whichever assignment list and process templates you
select.
The system displays the Assign Resource to Task dialog box.
The Group, Role, and User lists let you select users based on their group
and role within the organization. In addition, when assigning tasks, the only
action that can be assigned is Perform.
6. Select assignments using the Group, Role, and User lists.
7. Click OK.
The system displays the user information and action assigned to that user
beneath the task node in the process tree.
8. Repeat the previous steps to assign other tasks in the process.
9. Click Create.

Release notes
Assign tasks using process assignment lists

To assign tasks using process assignment lists (PALs), you must have previously
created them.
1. Select the task or an object that is currently in the process to assign the PAL.
2. Choose Tools→Process Assignment Lists→Assign.

The system displays the Assigns Process Assignment Lists dialog box.

a. Select the list type to make assignments based on a predefined PAL.
You do not see anything listed under the list types unless PALs have
been created previously for the workflow template being used.
A. Select My Lists to choose a PAL from your lists.
B. Select My Group Lists to choose a PAL from your group lists.
C. Select Other Lists to choose a PAL from another list.
b. Select Assign to assign tasks in the process ad hoc.

The system displays the Assign Resource to Task dialog box.
The Group, Role, and User lists let you select users based on their group
and role within the organization. In addition, when assigning a task, the
only action that can be assigned is Perform.
A. Select assignments using the Group, Role, and User lists.
B. Click OK.
The system displays the user information and action assigned to that
user beneath the task node in the process tree.
C. Repeat the previous steps to assign other tasks in the process.

Transition Guide
The following release notes pertain to the Transition Guide.
• The following information will be added as a new topic.
Audit monitoring
Global Services provides an audit log of transactions during transfers between
Teamcenter Enterprise and Teamcenter that is maintained in the Global
Services database. You can query for transactions using the AuditMonitoring
business object search form in the Global Services portal. The following
transactions are logged:
– Get objects for ownership transfer.
– Transfer ownership to site.
– Update ownership transfer to source site.
• In the Configure sites in Teamcenter topic, change Uses TcPLMXML Payload in

steps 4 and 10 to Uses TcXML Payload.
• The Create Aerospace and Defense option sets topic will be removed. This topic
is applicable to Data Exchange only and does not apply to transfers between
Teamcenter and Teamcenter Enterprise.
• The Stubs topic under the Basic concepts topic will be replaced with the following:
Stubs
The Teamcenter Enterprise exporter exports an object as a stub when:
– An object has previously been exported to a remote site as a full object, and a
subsequent transfer uses the Include Modified Objects Only option.
– The exporting site does not own the object.
– The object is marked as export protected by a condition.
– Message access rules deny access to the object.
– Data swarming is enabled and the exporter spawns new export requests. In
this case, objects that are processed in the spawned export requests are
exported as stubs in the current export transaction.

Release notes
– An inferred delete of relations would occur if the stubs were not included
because they are not part of the current transfer option set; for example, if
a component with three revisions (Rev A, Rev B, and Rev C) is exported
with a transfer option set that specifies the Latest Revision export option
(Rev C), the export content includes the following.
The earlier revisions (A and B) are sent as stubs so the target site is aware
that additional revisions exist. If a subsequent transfer of the component
specifies the All Versions export option, the stubs at the target site are
updated to the full revision A and revision B objects.
If the first transfer specifies the All Versions export option, and a subsequent
transfer specifies the Latest Version export option, the presence of stubs for
revision A and revision B in the subsequent transfer allows the remote site
to know all three revisions still exist and none should be deleted.
• The following caution will be added to the Include Modified Objects Only option
description in the table in step 3 of the Create a transfer option set procedure and
to the Export from Teamcenter topic:
Caution
If data in Teamcenter is replicated to a remote site:
– You cannot delete the replicated objects and synchronize them to
remote sites using the Include Modified Objects Only option. You
must export the full object set to delete the replicated objects.
– You cannot synchronize license_id objects or structure effectivity

using the Include Modified Objects Only option. You must export the
full object set to update this information.

Upgrade Guide
The following release notes pertain to the Upgrade Guide.
• install -acg argument not supported in GM Overlay upgrade
In Troubleshooting Teamcenter upgrade, remove the procedure that uses the
install -acg command. The acg argument is not supported with the install
command.
• Migrate Manufacturing Process Management preferences after upgrade

from Engineering Process Management
In Upgrade from Engineering Process Management®Completing corporate server
upgrade, add the following topic:
Migrate Manufacturing Process Management preferences

Migrate the legacy Show_ME_line_linked_icons preference to the new
MELineLinkedIconsProperty preference:
– If Show_ME_line_linked_icons is set to true, set

MELineLinkedIconsProperty to fnd0bl_assigned_as.
– If Show_ME_line_linked_icons is set to false, leave the default

setting of no value for MELineLinkedIconsProperty.
Utilities Reference
The following release notes pertain to the Utilities Reference. A complete description
of each new utility follows the notes.
• convert_replica_files_to_stubs utility
The convert_replica_files_to_stubs utility has a new -by_plmxml argument,
and the -site_name argument is replaced by the -by_site_name argument.
These arguments are mutually exclusive. Due to a change in behavior, syntax,
and additional examples, a complete description of this utility is provided.
• data_share utility
The following example will be added to the data_share utility information.
– To use the data_share utility to transfer architecture breakdown structures

between sites, you must execute the following four steps sequentially:
1. Push the design assembly.
$IMAN_BIN/data_share -f=send -item_id=<Design Assembly ITEM_ID> -site<REMOTE_SITE_ID>
-exclude=IMAN_reference -exclude=IMAN_based_on -exclude=IMAN_snapshot
-exclude=IMAN_3D_snap_shot -exclude=IMAN_external_object_link
-exclude=TC_Generic_Architecture -bo=VariantExpression, MEAppearancePathNode
-bs=1000 –ldv
2. Push the LOUHOLDER object and synchronize the BOM view revision.
$IMAN_BIN/data_share -f=send -item_id=<ITEM_ID> -site=<REMOTE_SITE> -include_bom
-exclude=IMAN_reference -exclude=IMAN_based_on -exclude=IMAN_snapshot
-bvo -bo=PSOccurrence -bs=20 -bvrsync -report=<IMAN_TMP_DIR>/rpt

Release notes
3. Push the architecture breakdown structure excluding the NVEs.

$IMAN_BIN/data_share -f=send -item_id=<ITEM_ID> -rev=001 -site=<REMOTE_SITE>
-exclude=IMAN_3D_snap_shot -exclude=IMAN_reference -exclude=IMAN_external_object_link
-exclude=IMAN_based_on -evo -bo=MEAppearancePathNode -bs=2000 –ldv
4. Push the NVEs.

$IMAN_BIN/data_share -f=send -item_id=<ITEM_ID> -rev=001 -site=<REMOTE_SITE>
-exclude=IMAN_3D_snap_shot -exclude=IMAN_external_object_link -exclude=IMAN_based_on
-bo=MEAppearancePathNode -bs=2000 –ldv
• import_file utility
The following documentation for the -relationType and
-use_ds_attached_to_rev_only arguments will be added to the
import_utility information:
-relationType
Specifies a relation to use when the IMAN_specification relation is
not appropriate. If the -relationType argument is not specified, the
IMAN_specification relation is used.
-use_ds_attached_to_rev_only
Specifies a dataset based on its name and type, but it considers datasets
attached to the specified item and item revision only. The item and item
revision are specified by the -item and -revision parameters, respectively.
This prevents the utility from referring to datasets with the same name and
type but that are unattached or are attached to another item or revision.
The -use_ds_attached_to_rev_only parameter is particularly useful when
used along with the de=r argument (that is, if you want to revise the existing
dataset instead of creating a new one).
• install_event_types utility
The following argument and example will be added to the install_event_types
utility information:
Arguments
-subscribe
Specifies that the event type can be subscribed to. This is valid only with the
-f=modify argument.
Examples
– To add event type mapping, enter the following command on a single line:
install_event_types -u=infodba -p=infodba -g=dba -f=add -imantype=Item
-imanclass=Item -eventtype=CusEventType â€“subscribe
• pdx_export utility
The pdx_export utility will be documented in the Utilities Reference at the
next full release.

• plmxml_export utility
The first bullet item in the note in the -class argument description for the
plmxml_export utility will be replaced with the following:
Note
– You cannot use the -class argument to export scope rules
(TransferModes, ClosureRules, FilterRules, PropertySets,
ActionRules, and TransferOptionSets). Use the tcxml_export
utility.
• pom_audit_manager utility
The pom_audit_manager utility will be documented in the Utilities Reference
at the next full release.
• site_util utility
The -tcplmxml argument will be replaced by the -tcxml argument. The
-tcplmxml argument description will be replaced with the following:
-tcxml
Specifies the utility uses TC XML payload instead of an object manager.
The command in the last example will be replaced with the following:
site_util -f=create -http=y -tcxml=y
-node_name=http://url_of_the_gs_instance

Release notes
convert_replica_files_to_stubs
Converts existing replica Teamcenter file (ImanFile objects) to pom_stub objects at
the specified remote site, all remote sites, or specified objects at all remote sites; it
purges the corresponding operating system volume files to conserve space. It can
also populate the file server cache (FSC) with replica files.
SYNTAX
convert_replica_files_to_stubs -u=admin-id {-p=password |
-pf=password-file} -g=dba
{[-by_site_name=remote-site-id | ALL] | [-by_plmxml=file-name]} [-verbose]
[-populate_cache] [-query ] [-batch_size=size-value]
[-h]
ARGUMENTS
-u
Specifies the user ID. The user must have administrative privileges.
If this argument is used without a value, the operating system user name is used.
-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. The file must be a single-line ASCII file containing
the password in clear text. Teamcenter Environment Manager prompts you for a
password and creates the password file during installation.
This argument is mutually exclusive with the -p argument.
-g
Specifies the group associated with the user. The group value must be dba to run
this utility.
-by_site_name
Specifies the name of the remote site where replica files are replaced with stubs. If
ALL is specified, replica files at all remote sites are replaced. This argument cannot
be combined with the -by_plmxml argument.
-by_plmxml
Specifies the name of a PLM XML file that contains replica objects to be replaced by
stubs. Only the objects listed in the file are replaced.
You must generate the PLM XML file specified in this argument using the
ConfiguredDataExportDefault or justDatasetsOut transfer modes. Other
transfer modes are not supported.
This argument cannot be combined with the -by_sitename argument.

-verbose
Includes additional information about the process in the utility’s output.
-populate_cache
Populates the FSC with replica files at the sites where replica objects are replaced
with stub objects.
-query
Returns the number of objects that will be converted to stubs.
-batch_size
Specifies the number of objects in each batch that is processed. If this argument is
omitted, all objects are processed in a single batch.
-h
Displays help for this utility.
ENVIRONMENT
As specified in Configuring utilities in the Utilities Reference.
FILES
As specified in Log files in the Utilities Reference.
RESTRICTIONS
The IDSM server must be running when you use this utility.
EXAMPLES
• Replace all replica objects at all sites with stub objects:
convert_replica_files_to_stubs -u=infodba -p=password -g=dba
-by_site_name=ALL
• Replace replica objects at the cologne site and populate the site’s FSC:
convert_replica_files_to_stubs -u=infodba -pf=pwfile -g=dba
-by_site_name=cologne —populate
• Determine the number or replica objects that will be replaced at a site:

convert_replica_files_to_stubs -u=infodba -p=password
-by_site_name=cologne -query
• Replace all replica objects at all sites with stub objects processed in batches of
200 objects:
-by_site_name=ALL -batch_size=200
• Replace replica objects in the stub_replicas.xml file at all sites with stub
objects processed in batches of 200 objects:
–by_plmxml=stub_replicas.xml -batch_size=200

Release notes
item_to_part_design
Converts instances of the Item class and its subtypes to specified instances of the
Part and Design classes or their subclasses or subtypes. Use this utility if you have
existing product structure containing items that you want to convert to separate part
and design (CAD) objects. You must create a text file that provides the necessary
input for the conversion process.
The utility allows you to:
• Convert all objects in the system or a specified set of objects of a given source
type to given target types.
• Specify the source as the Item class or its subtypes and specify the target as the
Part and Design classes, their subclasses, or subtypes.
Caution
After you run this utility, you cannot revert the changes.
You must analyze the impact on business rules (for example, property rules
and GRM rules) of the conversion and then plan accordingly. The utility does
not check the validity of the business rules.
Performance may be poor if you try to convert the entire database or a large
structure. If possible, limit the structure size or the number of objects to
convert.
The following conversions are supported by this utility:

• Item subtypes to Part subtypes
• Item subtypes to Design subtypes
• Item subtypes to Part class
• Item subtypes to Part subclass
• Item subtypes to Design class
• Item subtypes to Design subclass
• Item class to Part class
• Item class to Part subclass
• Item class to Design class
• Item class to Design subclass
The utility operates in three modes:

• type_based

Input from the user is an item class or its subtype, which is a source type.
The user specifies a target type. All objects in the database of source type are
converted to the target type.
• item_id_based
In this mode, the user specifies a comma-separated list of item IDs, together with
the source and the target types. Only the valid item IDs listed in the input file
are converted from the source type to the target type.
• structure_based
The user specifies the item identifier of the top-level item in the structure,
together with the source and the target types. This mode converts all the valid
children of the top-level item to the target type.
The user must create a text file that contains input to the entire conversion process.
SYNTAX
item_to_part_design [-u=user-id -p=password | -pf=password-file -g=group]
-mode=type_based | item_id_based | structure_based -file=input-file-name
[-rf=report-file-name] [-dryRun=true/on | false/off] [-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. This argument is mutually
exclusive with the -pf argument.
If this argument is not used, the system assumes the user-id value to be the
password.
-pf
If used without a value, the system assumes a null value. This argument is mutually
exclusive with the -p argument.
If this argument is not used, the system assumes the user-id value to be the
password.

Release notes
-g
Specifies the group associated with the user.
If used without a value, the user’s default group is assumed.
-mode
Specifies type_based, item_id_based, or structure_based.
-file
This argument is mandatory for all the conversion modes.
Specifies the name of the input file containing conversion parameters, including the
full path. The input file is a list of key-value pairs. The keys indicate the source and
target item types. The input file has the following format:
source_class_name=Item class | SubType
target_class_name=Part/Design class | SubClass | SubType
item_id_list=Name of input file
Ensure you use internal names for the source and target.
-rf
This optional argument specifies the name and location of the report file. If you do
not specify a name and location, the system writes the file to C:\temp on Microsoft
Windows systems or /tmp on other systems. It is not applicable in type_based
mode.
-dryRun
This optional argument causes the utility to validate if the specified items or
structure can be validate, but does not perform the conversion. Valid values are true
or on and false or off (case sensitive). It is not applicable in type_based mode.
-h
RESTRICTIONS
• Execute this utility when no other activity is present on the database.
• This utility changes the type of item object, its revisions, master form, and
revision master form. The storage class of source and target master forms is
assumed to be same.
• The utility converts objects in a particular database. If the objects being

converted are exported to different sites, either the replica of the object must
be deleted before conversion or replica objects also need to be converted in a
similar fashion. If the replica objects are not converted due to change of type,
synchronizing of data does not occur.
• If you use item_id_based mode or structure_based mode, items with export

records or conflicting GRM rules are not converted. They are converted if you
use type_based mode.
• The conversion of item subclass instances is not supported.
• The utility does not support source and target classes or subtypes other than
those listed in the description.

• Any customization of the source object type is not supported after conversion
to the target type.
• If the target is a subclass of Part or Design with custom attributes, those

custom attributes of the converted instance or object are populated with default
values, if any are defined. If none are defined, the custom attributes are null.
EXAMPLES
• The following example uses type_based mode and converts all the objects of a
source type to a target type defined in the Sample.txt file:
item_to_part_design -u=infodba -p=infodba -g=dba
-mode=type_based -file="C:\Sample.txt"
The contents of Sample.txt are:
source_class_name=Item
target_class_name=Part
• The following example uses item_id_based mode and converts all of the valid
items listed in the Sample.txt file from source type to target type. No dry run is
performed, but a report is written to the ReportFile.txt file.
-mode=item_id_based -rf=”C:\temp\ReportFile.txt”
-file="C:\Sample.txt" –dryRun=false
item_id_list=000001,000004,000009,
• The following example uses item_id_based mode and converts all of the valid
items listed in the Sample.txt file from source type to target type. A dry run is
performed, and a report is written to the default location.
-mode=item_id_based -file="C:\Sample.txt" –dryRun=true
The contents of Sample.txt are the same as in the previous example.
• The following example uses structure_based mode and converts all the valid
items and children of the specified item identifier from a source type to a target
type defined in the Sample.txt file. No dry run is performed, but a report is
written to the ReportFile.txt file.
-mode=structure_based
-rf=”C:\temp\ReportFile.txt” -file="C:\Sample.txt"
–dryRun=false -itemId=000008
Note
item_id_list is not required.

Release notes
pdx_export
Exports data in PDX format.
SYNTAX
pdx_export -u=admin-id {-p=password | -pf=password-file} -g=dba
{-item=item-id -rev=item-revision -sitenametarget-site} [-optionset=transfer-option-set]
[-reason=reason-description] [-immediate= {True | False} ] [-notify= {True | False} ]
[-emailaddrs=email-address1, email-ddress2, email-addressn]
[-revisionrule=revision-rule-name] [-bomlevel=level-of-BOM-structure]
[-vendors=vendor–name1, vendor–name2, vendor-namen] [-fileoutput-file-name]
[-usegs= {True | False} ]
[-h]
ARGUMENTS
-u
-p
-pf
-g
this utility.
-item
Specifies the identifier for the item object to export.
-rev
Specifies the revision of the item object to export
-sitename
Specifies the name of the importing (target) site.
-optionset
Specifies the name of the transfer option set to use for the export.
-reason
Allows you to type a description of the export purpose. This argument is limited to
240 characters. If you enter more than 240 characters, the argument is truncated.

-immediate
Specifies whether to schedule the export or perform it immediately. Valid values
are True or False.
-notify
Specifies whether to send a e-mail notification to the users specified in the
-emailaddrs argument. Valid values are True or False.
-emailaddrs
Specifies a comma delimited list of e-mail addresses that are notified of the export.
-revisionrule
Specifies the name of the revision rule to use for the export.
-bomlevel
Specifies the level of BOM to traverse for the export.
-vendors
Specifies a list of vendor names used to filter the content of the exported data. Only
objects associated with a vendor in this list are included in the export file. If this
argument is not specified, objects associated with any vendor are included.
-file
Specifies the name of the output file containing the PDX export data. If the file
exists, it is overwritten.
-usegs
Specifies whether to use Global Services to perform the export.
-h
ENVIRONMENT
FILES
RESTRICTIONS
You must be logged on as a member of the dba group.

Release notes
pom_audit_manager
Specifies which audit events are logged at your site and whether each event type is
audited for all users, specific users, or no users.
The following audit events are stored in POM audit tables, and can be selected for
logging.
Event type Description

POM_AUDIT_purge_audit Purges the audit data.
POM_AUDIT_bad_password_login Fails to log on with a bad password.
POM_AUDIT_bad_password_check Fails a POM_check_password call.
POM_AUDIT_change_password Changes a password.
SYNTAX
pom_audit_manager -u=admin-id {-p=password | -pf=password-file} -g=dba
[-install] [-report=[-before eight-digit-ISO-date]] [-purge=[-before eight-digit-ISO-date]]
[-auditable] [-set=event user {ON|OFF}] [-delete=event user] [-h]
ARGUMENTS
-u
-p
-pf
-g
this utility.
-install
Installs POM auditing functionality.
Use this argument when a new database does not have audit tables installed, such
as a patch release.
-report
Provides a report of all audited events.

Use -before with this argument to filter the report to ignore events after a specified
time
-purge
Purges all auditing events from the system.
Use -before with this argument to filter the purge range, ignoring events after a
specified time.
-before
Filters the behavior of the -report and -purge arguments, limiting their effects to
events occurring before a specified time.
This argument accepts an eight-digit ISO date value. For example, 20071225
specifies December 25, 2007.
This argument can only be used with the -report and -purge arguments.
-auditable
Provides a report of all auditable events.
-set
Specifies an audit event for logging.
This argument accepts the name of a valid audit event, and the name of a valid
user. Alternatively, you can use the ALL keyword for either the audit event name
or the user name.
-delete
Removes the specified audit event from logging.
This argument accepts the name of a valid audit event and the name of a valid
user. Alternatively, you can use the ALL keyword for either the audit event name,
or the user name.
-h
ENVIRONMENT
FILES
RESTRICTIONS
You must be logged on as a member of the dba group.
EXAMPLES
• To generate a report of all auditable events occurring before December 1, 2007,
enter the following command on a single line:
pom_audit_manager -u=infodba -p=secret -g=dba -report -before 20071201
• To purge all auditable events contained in the report generated by the previous
example, enter the following command on a single line:
pom_audit_manager -u=infodba -p=secret -g=dba -purge -before 20071201
• To enable logging of all failed logon attempts due to a failed password by all
users, enter the following command on a single line:
pom_audit_manager -u=infodba -p=secret -g=dba -set POM_AUDIT_bad_password_login ALL ON

Release notes
• To enable logging of all failed POM_check_password calls by all users, enter

the following command on a single line:
pom_audit_manager -u=infodba -p=secret -set POM_AUDIT_bad_password_check ALL ON
• To enable logging of password changes made by infodba, enter the following

command on a single line:
pom_audit_manager -u=infodba -p=secret -set POM_AUDIT_change_password infodba ON
Web Application Deployment Guide

The following release note pertains to the Web Application Deployment Guide.
• Configuring two-way SSL
The following note will be added to the FMS server cache (FSC) SSL client
credentials (two-way SSL) topic:
Note
The com.teamcenter.fms.allowuntrustedcertificates property cannot
be used with two-way SSL. This property can only be used for trusting
one-way SSL self-signed certificates.
What’s New
The following release notes pertain to What’s New.
• Enhanced authorized data access license control
The following preference information will be added to the paragraph below the
second list in the Enhanced authorized data access license control topic.
You can prevent propagation of licenses, IP, and Government
Classification values by setting the ADA_allow_license_propagation,
ADA_allow_ip_classification_propagation, and
ADA_allow_gov_classification_propagation preferences to false.
• Teamcenter 8.3 uses new version of the Common Licensing Server

Teamcenter 8.3 uses a new version of the Siemens PLM Software Common
Licensing Server. This provides the following enhancements to license
management in Teamcenter 8.3:
– Teamcenter 8.3 makes enhanced use of named user licensing, logging

Teamcenter users onto the licensing server by Teamcenter user IDs instead
of operating system user names as in past versions. The previous behavior
prevented auditing of individual users’ activities, particularly when multiple
users shared a client machine, or when connecting using a four-tier client
where all users used the same operating system name of the server machine
to which they connected.

– Teamcenter 8.3 allows a single named user to log on multiple times from
same host without consuming multiple license feature keys. A user can
log on multiple times on the same client and only consume a single license
feature even with a mix of two-tier and four-tier connections. Each logon is
recorded in the log file as a single license usage by the license server. The
host identity is noted as a constant value, TcServer, in each entry.
Note
On Teamcenter servers deployed on Hewlett-Packard HP-UX PA-RISC
systems, these license server enhancements are not available and the
functionality will continue to behave as it has in prior releases where
the operating system name is logged and multiple logons will consume
multiple licenses. For this reason, Siemens PLM Software recommends
you deploy your Teamcenter servers on hardware other than HP-UX
PA-RISC systems.
You can only deploy the Teamcenter license daemon on HP-UX PA-RISC
hardware if all Teamcenter servers are also HP-UX PA-RISC. Since
two-tier clients have a Teamcenter server as part of the install, and
because Teamcenter is not supported on HP-UX PA-RISC clients, you
cannot use two-tier clients with a HP-UX PA-RISC hosted license daemon.
Siemens PLM Software recommends deploying the license daemon on
other hardware, for example, HP-UX Itanium or any other supported
hardware platform to avoid issues.

Release notes
Workflow Designer Guide

The following release note pertains to the Workflow Designer Guide.
• Example usage of the inherit action handler
The following examples will be added to the Examples section of the inherit
handler documentation.
– This example copies the reference attachments from the parent task to the
current task.
Argument Values
CALLER::REFERENCE
– This example copies the signoffs from the previous task to the current task.
The handler is placed on the perform-signoffs subtask of the second Review
task.
Argument Values
PREVIOUS::SIGNOFFS
The following handlers will be added to the next release of the Workflow Designer
Guide.

AI-process-export
DESCRIPTION
Creates a new RequestObject object under the target ApplicationInterface (AI)
object without changing the base references of the AI object.
An AI object is a persistent workspace object that is the repository for the import
and export transactions between Teamcenter and an external application for a
predefined and configured structure. It contains:
• An ordered list of request objects.
• The transfer mode (import or export).
• The root or top-level object of the structures to exchange. This can be any
object that is valid to export from Teamcenter using PLM XML. For example, a
structure context, item, or BOM view revision.
• Tracking information to allow updates of changed data (deltas).
For more information about AIs, see the Rich Client Interface Guide.
Use this handler in workflows containing at least one AI object as a target,
and containing reference attachments such as StructureContext or
CollaborationContext objects, or objects accepted by PLM XML export (such as
BOM views, BOM view revisions, items, and item revisions).
Note
Without a StructureContext or CollaborationContext object, the PLM
XML cannot export a structure, because there is no configuration; only
the workspaceObject is exported. Typically, a StructureContext or
CollaborationContext object is used as a reference attachment.
SYNTAX
AI-process-export
ARGUMENTS
None.
PLACEMENT
Requires no specific placement.
RESTRICTIONS
The attachments must be placed under the root task.
EXAMPLES
To share an existing CollaborationContext object with another application using
PLM XML format, use a workflow template containing this handler. Initiate the
workflow against an AI object, selecting the AI object as the target attachment
and the CollaborationContext object as the reference attachment. The workflow
creates a new RequestObject object. The AI can now be shared with another
application.

Release notes
AI-process-import
DESCRIPTION
Imports the PLM XML associated with the target RequestObject objects.
RequestObject objects are contained within ApplicationInterface (AI) objects.
For more information about working with AIs, see the Rich Client Interface Guide.
SYNTAX
AI-process-import
ARGUMENTS
None.
PLACEMENT
Requires no specific placement.
RESTRICTIONS
The attachments must be placed under the root task.
EXAMPLES
To import the PLM XML associated with a new RequestObject object created
by any client application under an existing AI object, use a workflow template
containing this handler. Initiate the workflow against the AI and select one or more
RequestObject objects as target attachments, including the new RequestObject.
Optionally, also select an ICRevision object as a reference attachment. The
structure is updated with the contents of the PLM XML contained within the
RequestObject object.

Index
Numerics/Symbols askLOVLength() ITK deprecation . . . . . . 2-8

3D snapshot preview . . . . . . . . . . . . . . 3-18 Assigned occurrence . . . . . . . . . . . . . . 4-36
Attributes
Custom . . . . . . . . . . . . . . . . . . . . . . 4-85
A
Shapes_Files . . . . . . . . . . . . . . . . . 4-120
Access Manager Shapes_Name . . . . . . . . . . . . . . . . 4-120
Rule table . . . . . . . . . . . . . . . . . . . . . 4-8 Audit Manager
Rule tree . . . . . . . . . . . . . . . . . . . . . . 4-8 Deprecation of audit files . . . . . . . . . . 2-3
Sequences rule . . . . . . . . . . . . . . . . . . 4-8 pom_audit_manager utility . . . . . . . 4-165
Vault table . . . . . . . . . . . . . . . . . . . . 4-8 Audit monitoring . . . . . . . . . . . . . . . 4-152
Accountability check . . . . . . . . . . . . . . 4-36 Authorized data access license control . . . 3-5
Action handlers Automotive Edition . . . . . . . . . . . . . . . 3-37
AI-process-export . . . . . . . . . . . . . . 4-170 Autopublish . . . . . . . . . . . . . . . . . . . . 4-40
AI-process-import . . . . . . . . . . . . . 4-171 Autorecovery . . . . . . . . . . . . . . . . . . . 4-55
ADA Licenses . . . . . . . . . . . . . . . . . . . . 3-2
ADA_allow_gov_classification_propagation
preference . . . . . . . . . . . . . . . . . . . . 4-167 B
ADA_allow_ip_classification_propagation Base Name not supported . . . . . . . . . . 4-62
preference . . . . . . . . . . . . . . . . . . . . 4-167 BOM
ADA_allow_license_propagation Line columns . . . . . . . . . . . . . . . . . . 4-37
preference . . . . . . . . . . . . . . . . . . . . 4-167 Restructuring . . . . . . . . . . . . . . . . . 4-38
Administration release notes . . . . . . . . 4-71 Bookmarks launch . . . . . . . . . . . . . . . 2-21
Adobe Illustrator . . . . . . . . . . . . . . 3-7, 4-90 Business Modeler IDE
Aerospace and Defense . . . . . . . . . . . . 3-37 Business object constants . . . . . . . . . 2-18
PLM XML . . . . . . . . . . . . . . . . . . . . . 4-9 Digital Dashboard . . . . . . . . . . . . . . 2-16
Release notes . . . . . . . . . . . . . . . . . . . 4-9 Dispatch libraries . . . . . . . . . . . . . . . 3-4
Thin client . . . . . . . . . . . . . . . . . . . . . 4-9 Documentation release notes . . . . . . 4-114
AI-process-export handler . . . . . . . . . 4-170 Enabled property constant . . . . . . . . 4-86
AI-process-import handler . . . . . . . . . 4-171 Installing to Eclipse . . . . . . . . . . . . 4-115
AIWS, deprecating . . . . . . . . . . . . . . . . 2-6 Mapping Designer . . . . . . . . . . . . . . . 3-4
AIX Property rules . . . . . . . . . . . . . . . . . 2-22
64-bit . . . . . . . . . . . . . . . . . . . . . . . 2-17 Published flag . . . . . . . . . . . . . . . . . 4-85
Drag and drop . . . . . . . . . . . . . . . . 4-106 USASCII7 characters . . . . . . . . . . . . 4-88
Eclipse . . . . . . . . . . . . . . . . . . . . . 4-106
Icons not displayed . . . . . . . . . . . . . 4-106
C
Menus . . . . . . . . . . . . . . . . . . . . . 4-106
Release notes . . . . . . . . . . . . . . . . . 4-106 Cacheless search enhancements . . . . . . 3-30
Allocating volume resources . . . . . . . . . . 3-6 CAE items
allowuntrustedcertificates property . . 4-167 Custom attributes . . . . . . . . . . . . . . 4-85
Apache Web servers . . . . . . . . . . . . . . 4-98 Wizard enhancements . . . . . . . . . . . 3-29
Appearance update manager . . . . . . . 4-111 cae_geometry_fix utility . . . . . . . . . . . . . 4-6
Application Integration Environment Calendars in Schedule Manager . . . . . . 4-60
(AIE) . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Cascading LOVs not supported in live Excel
Application Interface Web Service, and live Word . . . . . . . . . . . . . . . . . . 4-58
deprecating . . . . . . . . . . . . . . . . . . . . . 2-6 CATDrawing name . . . . . . . . . . . . . . . 4-24
PLM00001 G (01-037134-083) Teamcenter 8.3 Release Bulletin Index-1

Index
CATIA Customizing the Process Template

Alternate shape . . . . . . . . . . . . . . . 4-120 list . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Integration . . . . . . . . . . . . . . . . . . . 4-20
Required attributes for shapes . . . . 4-120 D
CCABase items . . . . . . . . . . . . . . . . . . 4-66
Certification database . . . . . . . . . . . . . . 1-5 Data Exchange
Change Manager Guide . . . . . . . . . . . 4-116 Briefcase transfers . . . . . . . . . . . . . . 4-21
Change Manager release notes . . . . . . . 4-10 Dataset, transferring . . . . . . . . . . . . 4-21
Change Viewer deprecation . . . . . . . . . . 2-4 Monitoring interface . . . . . . . . . . . . . 4-21
change_type_name utility . . . . . . . . . . 4-88 Object Directory Services . . . . . . . . . 4-21
Checkout failure . . . . . . . . . . . . . . . . . 4-43 Ownership not updated in ODS . . . . . 4-21
Classification Relationship problem . . . . . . . . . . . . 4-20
Classified instance . . . . . . . . . . . . . . 4-15 Release notes . . . . . . . . . . . . . . . . . . 4-20
Firefox problem . . . . . . . . . . . . . . . . 4-14 Data Exchange Guide . . . . . . . . . . . . 4-119
Import and export failure . . . . . . . . . 4-15 Data Integration Services Adapter (DIS
Multi-Site . . . . . . . . . . . . . . . . . . . . 4-14 Adapter) . . . . . . . . . . . . . . . . . . . . . . 2-20
PLM XML . . . . . . . . . . . . . . . . . . . . 4-12 Data model deprecation . . . . . . . . . . . . 2-12
Root node names . . . . . . . . . . . . . . . . 4-9 Data sharing utilities
Safari problem . . . . . . . . . . . . . . . . . 4-14 convert_replica_files_to_stubs . . . . . 4-157
Search . . . . . . . . . . . . . . . . . . . . . . 4-34 convert_replica_files_to_stubs
Translation privilege . . . . . . . . . . . . 4-13 utility . . . . . . . . . . . . . . . . . . . . 4-154
Workflow . . . . . . . . . . . . . . . . . . . . . 4-12 data_share utility . . . . . . . . . . . . . 4-154
Classification Administration import_file utility . . . . . . . . . . . . . . 4-155
Key ID . . . . . . . . . . . . . . . . . . . . . . 4-12 pdx_export . . . . . . . . . . . . . . . . . . 4-163
Upgrade . . . . . . . . . . . . . . . . . . . . . . 4-9 pdx_export utility . . . . . . . . . . . . . 4-155
Client for Microsoft Office Guide . . . . . 4-118 plmxml_export utility . . . . . . . . . . . 4-156
Client for Office . . . . . . . . . . . . . . . . . 4-16 site_util utility . . . . . . . . . . . . . . . . 4-156
Live Office . . . . . . . . . . . . . . . . . . . . 4-17 Data synchronization . . . . . . . . . . . . . 4-72
Outlook dataset . . . . . . . . . . . . . . . . 4-17 data_share utility . . . . . . . . . . . 4-96, 4-154
Word setting for correct document Database query . . . . . . . . . . . . . . . . . . 4-53
display . . . . . . . . . . . . . . . . . . . . 4-17 Datasets
Cloning standard text . . . . . . . . . . . . . 4-35 Attaching . . . . . . . . . . . . . . . . . . . . 4-26
Code page 932 . . . . . . . . . . . . . . . . . . . 4-96 Transferring . . . . . . . . . . . . . . . . . . 4-21
collect_garbage utility . . . . . . . . . . . . . 4-82 DB2
Columns . . . . . . . . . . . . . . . . . . . . . . . 4-43 Release notes . . . . . . . . . . . . . . . 4-3, 4-99
Conditions . . . . . . . . . . . . . . . . . . . . 4-114 Servers . . . . . . . . . . . . . . . . . . . . . . . 4-3
Configure to load feature . . . . . . . . . . . 3-19 Support . . . . . . . . . . . . . . . . . . . . . . . 4-3
Configuring Global Services . . . . . . . . . 3-14 Default volumes value . . . . . . . . . . . . . 4-50
Connections . . . . . . . . . . . . . . . . . . . . 4-48 Defining users . . . . . . . . . . . . . . . . . 4-136
Content Management Deprecation . . . . . . . . . . . . . . . . . . . . . 2-1
Data model deprecation . . . . . . . . . . 2-12 AIWS . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Export fails . . . . . . . . . . . . . . . . . . . 4-18 Announcements . . . . . . . . . . . . . . . . . 2-8
S1000D . . . . . . . . . . . . . . . . . . . . . . 4-19 Application Integration Environment
Switching perspectives . . . . . . . . . . . 4-18 (AIE) . . . . . . . . . . . . . . . . . . . . . . 2-2
Tool tips . . . . . . . . . . . . . . . . . . . . . 4-19 Application Interface Web Service . . . . 2-6
User interface . . . . . . . . . . . . . . . . . 4-18 askLOVLength() ITK . . . . . . . . . . . . . 2-8
Contract data . . . . . . . . . . . . . . . . . . . 3-37 Bookmark launch . . . . . . . . . . . . . . . 2-21
convert_replica_files_to_stubs Business object constants . . . . . . . . . 2-18
utility . . . . . . . . . . . . . . . . . . 4-154, 4-157 Change Viewer . . . . . . . . . . . . . . . . . 2-4
cookie-http-only flag . . . . . . . . . . . . . . 4-79 Data model . . . . . . . . . . . . . . . . . . . 2-12
CREATERENDERING style sheet . . . . 4-89 eIntegrator Admin . . . . . . . . . . . . . . . 2-5
Creating volume allocation rules . . . . . . 3-6 Functions . . . . . . . . . . . . . . . . . . . . . 2-8
Custom attributes . . . . . . . . . . . . . . . . 4-85 Genius4000 to Resource Manager migration
Customization release notes . . . . . . . . . 4-84 program . . . . . . . . . . . . . . . . . . . . 2-3
Index-2 Teamcenter 8.3 Release Bulletin PLM00001 G (01-037134-083)

Index
Global Services BPEL engine Errors, marshalling . . . . . . . . . . . . . . . 4-56

endpoint . . . . . . . . . . . . . . . . . . . . 2-9 Ethernet MAC addresses, Sun
Global Services connectors . . . . . . . . . 2-9 Solaris . . . . . . . . . . . . . . . . . . . . . . 4-110
Headless applications . . . . . . . . . . . . . 2-2 Excel
HP-UX OS on PA-RISC hardware . . . . 2-6 Report Builder Reports . . . . . . . . . . . 4-93
IMAN_show_open_in_pv_button . . . . 2-21 Template . . . . . . . . . . . . . . . . . . . . . 4-56
Java classes . . . . . . . . . . . . . . . . . . . . 2-8 Export failure . . . . . . . . . . . . . . . . . . . 4-18
Microsoft Office 2003 support . . . . . . . 2-3 Export Status dialog box . . . . . . . . . . . 4-93
Report Designer . . . . . . . . . . . . . . . . . 2-5 Extensions for Microsoft Office
Rich client on UNIX-based operating Guide . . . . . . . . . . . . . . . . . . . . . . . 4-120
systems . . . . . . . . . . . . . . . . . . . . 2-6 Extensions for Office
Schematics in Structure Manager . . . . 2-7 Patch upgrade for add-in files . . . . . . 4-22
Sun Glassfish support . . . . . . . . . . . . 2-2 Release notes . . . . . . . . . . . . . . . . . . 4-22
SVG Viewer plug-in . . . . . . . . . . . . . 2-22 Externalization, accidental . . . . . . . . . 4-72
tc.h header file . . . . . . . . . . . . . . . . . . 2-4
Teamcenter EMC Content Storage media F
type . . . . . . . . . . . . . . . . . . . . . . 2-21
Teamcenter Services . . . . . . . . . . . . . 2-8 FCC size . . . . . . . . . . . . . . . . . . . . . . 4-28
Utilities . . . . . . . . . . . . . . . . . . . . . . 2-7 File Management System . . . . . . . . . . 4-77
Visio 2003 support . . . . . . . . . . . . . . . 2-1 File warmer . . . . . . . . . . . . . . . . . . . . 4-75
DesignContext in the thin client . . . . . . . 3-8 Firefox, see Mozilla Firefox
Details panel . . . . . . . . . . . . . . . . . . . 4-43 Folder length problem . . . . . . . . . . . . . 4-66
Digital Dashboard . . . . . . . . . . . . . . . . 2-16 Four-tier
Dimensional Planning and Validation . . 3-33 Clients, virus scanning . . . . . . . . . . . 4-91
Disk space requirements . . . . . . . . . . . . 1-5 Installation . . . . . . . . . . . . . . . . . . . . 4-1
Dispatch libraries . . . . . . . . . . . . . . . . . 3-4 Frequently Asked Questions for
Dispatcher Server . . . . . . . . . . . . . . . . 2-22 Teamcenter . . . . . . . . . . . . . . . . . . . 4-120
Display names . . . . . . . . . . . . . . . . . . 4-96 FSC failure . . . . . . . . . . . . . . . . . . . . . 4-76
Division character . . . . . . . . . . . . . . . . 4-91 FSC_DoNotCompressExtensions
Document Markup Language (DML) property . . . . . . . . . . . . . . . . . . . . . 4-100
support . . . . . . . . . . . . . . . . . . . . . . . 3-33 Functions, deprecated . . . . . . . . . . 2-8, 2-28
Documentation release notes . . . . . . . 4-114
Download hyperlink not available . . . . . 4-48 G
Duplicate feature . . . . . . . . . . . . . . . . 4-63
Dynamic participants . . . . . . . . . . . . . 4-70 Garbage collection . . . . . . . . . . . . . . . . 4-82
GDE
E Element . . . . . . . . . . . . . . . . . . . . . 4-39
Link . . . . . . . . . . . . . . . . . . . . . . . . 4-36
ECAD library Structure . . . . . . . . . . . . . . . . . . . . 4-39
Import failure . . . . . . . . . . . . . . . . . 4-67 generate_loadfsccache_tickets utility . . . 2-7
Spaces in field values . . . . . . . . . . . . 4-66 Genius4000 to Resource Manager migration
Editing running workflow processes . . . 3-11 program . . . . . . . . . . . . . . . . . . . . . . . 2-3
Effectivity Getting Started with Electronic (EDA)
Customization . . . . . . . . . . . . . . . . . 3-18 Lifecycle Management . . . . . . . . . . . 4-121
Framework . . . . . . . . . . . . . . . . . . . 3-17 Getting Started with Teamcenter . . . . 4-127
EIM_check_error . . . . . . . . . . . . . . . 4-102 Glassfish support . . . . . . . . . . . . . . . . . 2-2
eIntegrator Admin deprecation . . . . . . . . 2-5 Global Services
Eliminate unconfigured by variants . . . 3-19 Autopopulated nonmandatory
Embeds column . . . . . . . . . . . . . . . . . 4-38 fields . . . . . . . . . . . . . . . . . . . . . 4-24
Enabled property constant . . . . . . . . . . 4-86 BPEL engine endpoint . . . . . . . . . . . . 2-9
Enabling Configuration . . . . . . . . . . . . . . . . . 3-14
Change Manager . . . . . . . . . 4-116, 4-149 Conversion tool shows an error . . . . . 4-25
Instant messaging . . . . . . . . . . . . . 4-120 Deadlocks . . . . . . . . . . . . . . . . . . . . 4-23
EPM-set-property workflow handler . . . 4-70 NoSuchMethodError exception . . . . . 4-24

Index
Ownership not updated in ODS . . . . . 4-21 Spaces in field names . . . . . . . . . . . . 4-66

Release notes . . . . . . . . . . . . . . . . . . 4-23 import_dfa_file utility . . . . . . . . . . . . . . 2-7
Sample BOD does not display revision import_file utility . . . . . . . . . . . . . . . 4-155
number . . . . . . . . . . . . . . . . . . . 4-24 Importing
Sample Teamcenter Item BOD . . . . . 4-25 PALs . . . . . . . . . . . . . . . . . . . . . . . . 3-12
SSL support . . . . . . . . . . . . . . . . . . 3-14 Preferences . . . . . . . . . . . . . . . . . . . 4-71
Global Services connectors Volume failover . . . . . . . . . . . . . . . . . 3-6
Global Services Connector . . . . . . . . . 2-9 In Project rule . . . . . . . . . . . . . . . . . . . . 4-8
GS2GS connector . . . . . . . . . . . . . . . . 2-9 In-process workflow edits . . . . . . . . . . . 3-11
SAP Connector . . . . . . . . . . . . . . . . 2-11 Incompatible Teamcenter Engineering
Teamcenter 2007 Rich Client connectors . . . . . . . . . . . . . . . . . . . . . 4-24
Connector . . . . . . . . . . . . . . . . . . 2-11 Incorrect display name . . . . . . . . . . . . 4-96
Teamcenter 8 Connector . . . . . . . . . . 2-11 Increased transfer speed . . . . . . . . . . . 3-16
Teamcenter Engineering 2005/2007 Incremental change
Connector . . . . . . . . . . . . . . . . . 2-11 Occurrence group . . . . . . . . . . . . . . . 4-35
Teamcenter Engineering v9 Revision . . . . . . . . . . . . . . . . . . . . . 4-64
Connector . . . . . . . . . . . . . . . . . . 2-11 Visualization Illustration Batch . . . . 4-69
Global Services SSL support . . . . . . . . 3-14 inherit action handler . . . . . . . . . . . . 4-169
Global Technical Access Center Initial value property rules . . . . . . . . . 4-93
(GTAC) . . . . . . . . . . . . . . . . . . . . . 1-3–1-4 install_event_types utility . . . . . . . . . 4-155
GM Overlay Installation
Character set . . . . . . . . . . . . . . . . . 4-113 Business Modeler IDE . . . . . . . . . . 4-115
Template . . . . . . . . . . . . . . . . . . . . . 4-97 DB2 . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
UNIX . . . . . . . . . . . . . . . . . . . . . . 4-113 Embedded viewer . . . . . . . . . . . . . . . . 4-4
Graphics disappear . . . . . . . . . . . . . . 4-101 In general . . . . . . . . . . . . . . . . . . . . . 1-1
Groups Maintenance pack . . . . . . . . . . . . . . . 1-1
Display . . . . . . . . . . . . . . . . . . . . . . 4-74 Online help . . . . . . . . . . . . . . . . . . . . 4-5
Settings . . . . . . . . . . . . . . . . . . . . . 4-16 Teamcenter 8.3 . . . . . . . . . . . . . . 1-1, 4-1
Installation on UNIX and Linux Clients
H Guide . . . . . . . . . . . . . . . . . . . . . . . 4-127
Installation on UNIX and Linux Servers
Hardware requirements . . . . . . . . . . . . . 1-5
Guide . . . . . . . . . . . . . . . . . . . . . . . 4-128
Harness
Installation on Windows Clients
Connection list . . . . . . . . . . . . . . . . . 4-48
Guide . . . . . . . . . . . . . . . . . . . . . . . 4-129
Structure . . . . . . . . . . . . . . . . . . . . 4-49
Installation on Windows Servers
Headless applications . . . . . . . . . . . . . . 2-2
Guide . . . . . . . . . . . . . . . . . . . . . . . 4-130
Help . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Instant messaging . . . . . . . . . . . . . . . 4-120
Horizontal scroll bar my be hidden . . . . 4-23
Integration for Office
HP-UX . . . . . . . . . . . . . . . . . . . . . . . 4-103
Datasets, attaching . . . . . . . . . . . . . 4-26
ODS . . . . . . . . . . . . . . . . . . . . . . . 4-103
Uninstalling . . . . . . . . . . . . . . . . . . 4-26
PA-RISC hardware . . . . . . . . . . . . . . . 2-6
Value/description pairs display . . . . . 4-27
Release notes . . . . . . . . . . . . . . . . . 4-103
Internationalization
Languages . . . . . . . . . . . . . . . . . . . . . 1-5
I Release notes . . . . . . . . . . . . . . . . . . 4-94
IDC . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36 Internet Explorer . . . . . . . . . . . . . . . 4-100
IDSM servers . . . . . . . . . . . . . . . . . . 4-112 Interspec specifications . . . . . . . . . . . . 4-61
Image Import utility . . . . . . . . . . . . . . 2-16 Invalid item IDs, Teamcenter Integration for
iman_relation text incorrect . . . . . . . . . 4-96 NX . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
IMAN_show_open_in_pv_button IS NULL operator . . . . . . . . . . . . . . . . 4-53
preference . . . . . . . . . . . . . . . . . . . . . 2-21 iSeries . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Implemented By relationship . . . . . . . . 4-38 item_to_part_design utility . . . . 4-63, 4-159
Import failure ItemCreation.NoMasterForm
Classification . . . . . . . . . . . . . . . . . . 4-15 preference . . . . . . . . . . . . . . . . . . . . . 4-84

Index
ItemCreation.NoRevMasterForm SUSE Linux Enterprise Server

preference . . . . . . . . . . . . . . . . . . . . . 4-84 (SLES) . . . . . . . . . . . . . . . . . . . . 2-17
ItemRevision checkout . . . . . . . . . . . . . 4-44 Live Excel
ITK customization . . . . . . . . . . . . . . . . 4-89 Cascading LOVs not supported . . . . . 4-58
Obsolete, export for Excel 2003 . . . . . 2-21
J Live Word
Cascading LOVs not supported . . . . . 4-58
Japanese characters . . . . . . . . . . . . . . 4-96 Multi-choice properties not
Java classes, deprecated . . . . . . . . . . . . 2-8 supported . . . . . . . . . . . . . . . . . . 4-58
JT files . . . . . . . . . . . . . . . . . . . . . . . . 4-28 Localization
Platforms . . . . . . . . . . . . . . . . . . . . . 1-5
K Text incorrect . . . . . . . . . . . . . . . . . 4-96
Login Service . . . . . . . . . . . . . . . . . . . 4-78
Key ID . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Logon slow . . . . . . . . . . . . . . . . . . . . . 4-75
Lost data, Microsoft Windows . . . . . . . 4-108
L LOVs
Reordering . . . . . . . . . . . . . . . . . . 4-114
Language Translations dialog box . . . . 4-95 Translations . . . . . . . . . . . . . . . . . . 4-94
Launch output file management
enhancements . . . . . . . . . . . . . . . . . . 3-29 M
LDAP_member_list_attr preference . . . 4-72
LDAP_sync_group_flags preference . . . 4-72 Maintenance
LDAP_sync_member_flags Pack installation . . . . . . . . . . . . . . . . 1-1
preference . . . . . . . . . . . . . . . . . . . . . 4-72 Utilities . . . . . . . . . . . . . . . . . . . . 4-155
LDAP_sync_role_flags preference . . . . . 4-72 Maintenance, Repair, and Overhaul
LDAP_sync_user_flags preference . . . . 4-72 Default disposition . . . . . . . . . . . . . . 4-33
ldapsync utility . . . . . . . . . . . . . . . . . . 4-72 Physical part . . . . . . . . . . . . . . . . . . 4-33
Legacy product views . . . . . . . . . . . . . 4-29 Release notes . . . . . . . . . . . . . . . . . . 4-33
Libraries, dispatch . . . . . . . . . . . . . . . . 3-4 Stored option set . . . . . . . . . . . . . . . 4-33
Lifecycle Viewer make_user utility . . . . . . . . . . . . . . . . 4-72
Gray box . . . . . . . . . . . . . . . . . . . . . 4-30 Managing
Hidden boxes . . . . . . . . . . . . . . . . . . 4-31 Basic data . . . . . . . . . . . . . . . . . . . 4-149
Reconcile dialog box . . . . . . . . . . . . . 4-28 Workflows . . . . . . . . . . . . . . . . . . . 4-150
Status bar . . . . . . . . . . . . . . . . . . . . 4-30 Manufacturing Process Management
Toolbar . . . . . . . . . . . . . . . . . . . . . . 4-30 MENEWMFG_
Lifecycle Visualization DefaultDatumJTDatasetName . . 4-139
Data Integration Services Adapter (DIS Manufacturing Process Planner
Adapter) . . . . . . . . . . . . . . . . . . . 2-20 Assigned occurrence . . . . . . . . . . . . . 4-36
FCC size . . . . . . . . . . . . . . . . . . . . . 4-28 BOM line columns . . . . . . . . . . . . . . 4-37
Installation . . . . . . . . . . . . . . . . . . . . 4-4 Cloning standard text . . . . . . . . . . . . 4-35
Legacy product views . . . . . . . . . . . . 4-29 GDE link . . . . . . . . . . . . . . . . . . . . . 4-36
Navigator window is blank . . . . . . . . 4-31 Insert Level dialog box . . . . . . . . . . . 4-64
Over-the-Web Installer . . . . . . . . . . . . 4-4 Partition import . . . . . . . . . . . . . . . . 4-34
Postscript printer installation . . . . . . 4-29 Release notes . . . . . . . . . . . . . . . . . . 4-34
Release notes . . . . . . . . . . . . . . . . . . 4-28 Repair Broken Links dialog box . . . . . 4-37
Unable to launch . . . . . . . . . . . . . . . 4-32 Separation of view and edit properties
Viewer . . . . . . . . . . . . . . . . . . . . . . . 4-4 functionality . . . . . . . . . . . . . . . . 4-64
Windows Vista . . . . . . . . . . . . . . . . . 4-32 Variant condition . . . . . . . . . . . . . . . 4-36
Linux WeldPoint objects . . . . . . . . . . . . . . . 4-36
Appearance update manager . . . . . . 4-111 Manufacturing Process Planner
Crash . . . . . . . . . . . . . . . . . . . . . . 4-111 Guide . . . . . . . . . . . . . . . . . . 4-131, 4-149
Icons . . . . . . . . . . . . . . . . . . . . . . . 4-109 Mapper, Reporting and Analytics . . . . . 4-53
IDSM servers . . . . . . . . . . . . . . . . 4-112 Mapping Designer . . . . . . . . . . . . . . . . . 3-4
Release notes . . . . . . . . . . . . . . . . . 4-111 Marshalling error . . . . . . . . . . . . . . . . 4-56

Index
Mechatronics Process Management My Teamcenter

Editing a GDE element . . . . . . . . . . 4-39 Adobe Illustrator integration . . . . . . 4-90
GDE structure . . . . . . . . . . . . . . . . . 4-39 Microsoft Office documents . . . . . . . . 4-45
Release notes . . . . . . . . . . . . . . . . . . 4-38 Release notes . . . . . . . . . . . . . . . . . . 4-43
Sample ITK program/utility . . . . . . . 4-39 Save button . . . . . . . . . . . . . . . . . . . 4-46
Memory improvements . . . . . . . . . . . . . 3-4 Text file . . . . . . . . . . . . . . . . . . . . . . 4-44
MENEWMFG_ Validation report . . . . . . . . . . . . . . . 4-46
DefaultDatumJTDatasetName . . . . . 4-139 Viewer pane . . . . . . . . . . . . . . 4-45–4-46
Mentor Board Station . . . . . . . . . . . . . 4-66
METHOD_attach_action ITK . . . . . . . . 3-36 N
Microsoft
2000 . . . . . . . . . . . . . . . . . . . . . . . 4-108 Native FSC client proxy in TcServer . . 4-147
Office . . . . . . . . . . . . . . . . . . . 4-45, 4-92 Network cards, power saving option . . 4-102
Office 2003 . . . . . . . . . . . . . . . . . . . . 2-3 Network Folders . . . . . . . . . . . . 4-26, 4-107
Release notes . . . . . . . . . . . . . . . . . . 4-99 New and changed Teamcenter 8.3
Windows, lost data . . . . . . . . . . . . . 4-108 features . . . . . . . . . . . . . . . . . . . . . . . 3-1
Microsoft Office 2010 New Business Object wizard . . . . . . . . 4-44
Client for Microsoft Office Guide . . . 4-118 New Content Management Permissions dialog
Extensions for Microsoft Office box . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Guide . . . . . . . . . . . . . . . . . . . . 4-120 NoSuchMethodError exception . . . . . . . 4-24
Requirements Manager Guide . . . . . 4-143 Null pointer exception . . . . . . . . . . . . 4-107
Microsoft Office Communicator . . . . . 4-120 NX
Microsoft SQL Server 2008 R2 support in 6.0, QPL harvester enhancements . . . 3-32
DPV . . . . . . . . . . . . . . . . . . . . . . . . . 3-33 Export . . . . . . . . . . . . . . . . . . . . . . 4-93
Minimize ribbon . . . . . . . . . . . . . . . . . 4-16 Lifecycle Visualization . . . . . . . . . . . . 4-4
Modal dialogs, rich client . . . . . . . . . . . 4-92 NX Integration
Monitoring interface . . . . . . . . . . . . . . 4-21 Launch error . . . . . . . . . . . . . . . . . . 4-47
Mozilla Firefox NX component . . . . . . . . . . . . . . . . . 4-47
Classification . . . . . . . . . . . . . . . . . . 4-14 Release notes . . . . . . . . . . . . . . . . . . 4-47
Graphics disappear . . . . . . . . . . . . 4-101
Launching documentation . . . . . . . . . 4-5 O
Release notes . . . . . . . . . . . . . . . . . 4-101
Reporting and Analytics . . . . . . . . . . 4-52 Object Directory Services . . . . . . . . . . . 4-21
Teamcenter functionality not Obsolete
supported . . . . . . . . . . . . . . . . . 4-101 AIX 64-bit server support . . . . . . . . . 2-17
Teamcenter help . . . . . . . . . . . . . . 4-101 Functions . . . . . . . . . . . . . . . . . . . . 2-28
Multi-choice properties not supported in live Image Import utility . . . . . . . . . . . . . 2-16
Word . . . . . . . . . . . . . . . . . . . . . . . . 4-58 Live Excel export for Excel 2003 . . . . 2-21
Multi-Site Preferences . . . . . . . . . . . . . . . . . . . 2-25
Autopublish . . . . . . . . . . . . . . . . . . . 4-40 SUSE Linux Enterprise Server (SLES)
Classification . . . . . . . . . . . . . . . . . . 4-14 support . . . . . . . . . . . . . . . . . . . 2-17
Progress bar . . . . . . . . . . . . . . . . . . 4-41 Utilities . . . . . . . . . . . . . . . . . . . . . 2-23
Release notes . . . . . . . . . . . . . . . . . . 4-40 Web tier parameters . . . . . . . . . . . . . 2-20
Upgrade . . . . . . . . . . . . . . . . . . . . . 4-40 ODE . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Vendor management support . . . . . . 4-69 ODS support . . . . . . . . . . . . . . . . . . . 4-103
Multi-Site Collaboration Office 2010
Dataset import/export . . . . . . . . . . . 3-35 Macros . . . . . . . . . . . . . . . . . . . . . . 4-56
Licenses . . . . . . . . . . . . . . . . . . . . . 4-42 Security settings . . . . . . . . . . . . . . . 4-54
Remote checkin . . . . . . . . . . . . . . . . 4-42 Online help
Multi-Site Collaboration Guide . . . . . . 4-135 Search . . . . . . . . . . . . . . . . . . . . . . . 4-5
Multi-Structure Manager Guide . . . . . 4-149 WebLogic . . . . . . . . . . . . . . . . . . . . . 4-5
Multiple effectivities . . . . . . . . . . . . . . 3-17 Operating systems, release notes . . . . 4-103
Multiple View Editor, removal . . . . . . . 2-22 ORA-12571 error . . . . . . . . . . . . . . . . 4-102
Multivalued properties . . . . . . . . . . . . 4-43 Oracle

Index
ORA-12571 error . . . . . . . . . . . . . . 4-102 REQ_default_object_template . . . . . 4-139

Power saving option error . . . . . . . . 4-102 REQ_default_spec_template_for_
Release notes . . . . . . . . . . . . . . . . . 4-102 export . . . . . . . . . . . . . . . . . . . 4-140
Support in DPV . . . . . . . . . . . . . . . . 3-33 REQ_default_spec_template_for_
Organization view . . . . . . . . . . . . . . . . . . . . . 4-140
Creating a person . . . . . . . . . . . . . . 4-74 REQ_import_keywords . . . . . . . . . . 4-140
Group display . . . . . . . . . . . . . . . . . 4-74 Selection Criteria . . . . . . . . . . . . . . . 4-71
Redundant events logged . . . . . . . . . 4-74 TC_force_remote_sites_exclude_
Release notes . . . . . . . . . . . . . . . . . . 4-74 files . . . . . . . . . . . . . . . . . . . . . . 4-75
Select Recipients dialog box . . . . . . . 4-74 TC_Populate_FSC_Server_Targets . . 4-75
Organization Guide . . . . . . . . . . . . . . 4-136 TC_relation_export_on_transfer . . . 4-141
Ownership not updated in ODS . . . . . . 4-21 TC_remote_checkin_relation_send_as_
Owning Group rule . . . . . . . . . . . . . . . . 4-8 replica . . . . . . . . . . . . . . . . . . . . 4-42
Transient_Volume_RootDir . . . . . . . . 4-77
P Preferences and Environment Variables
Reference . . . . . . . . . . . . . . . . . . . . 4-138
PA-RISC hardware . . . . . . . . . . . . . . . . 2-6 Preventing propagation of license, IP, and
Parallel transfer process . . . . . . . . . . . 3-16 government classification values . . . . 4-167
Part Planner Guide . . . . . . . . . . . . . . 4-149 Pro/ENGINEER . . . . . . . . . . . . . . . . . 4-63
Partition import . . . . . . . . . . . . . . . . . 4-34 Process assignment lists import/
pdx_export utility . . . . . . . . . . 4-155, 4-163 export . . . . . . . . . . . . . . . . . . . . . . . . 3-12
PER_CLIENT setting . . . . . . . . . . . . . . 4-3 Process Template list customization . . . 3-13
Permission denied . . . . . . . . . . . . . . . . . 4-3 Product structure maintenance utilities
Plant Designer item_to_part_design . . . . . . . . . . . . 4-159
Data panel . . . . . . . . . . . . . . . . . . . 4-50 Product views preview . . . . . . . . . . . . . 3-18
Release notes . . . . . . . . . . . . . . . . . . 4-50 Progress bar, Multi-Site . . . . . . . . . . . . 4-41
Plant Designer Guide . . . . . . . . . . . . 4-149 Project
Platform Designer Guide . . . . . . . . . . 4-136 Access Manager rules . . . . . . . . . . . . . 4-8
Platform-specific release notes . . . . . . 4-103 Release notes . . . . . . . . . . . . . . . . . . 4-50
PLM XML Export Import Administration Properties
Guide . . . . . . . . . . . . . . . . . . . . . . . 4-137 Constants . . . . . . . . . . . . . . . . 2-22, 4-86
PLM XML import/export . . . . . . . . . . . 4-93 Dialog box . . . . . . . . . . . . . . . . . . . . 4-44
plmxml_export utility . . . . . . . . . . . . 4-156 Property Finder Formatter search
Plug-ins, tcapps . . . . . . . . . . . . . . . . . 3-35 results . . . . . . . . . . . . . . . . . . . . . . . 4-51
pom_audit_manager utility . . . 4-156, 4-165 Published flag on C++ code . . . . . . . . . 4-85
Pool manager . . . . . . . . . . . . . . . . . . 4-103
PostScript printer installation . . . . . . . 4-29 Q
Power saving option error . . . . . . . . . 4-102
PowerPoint datasets . . . . . . . . . . 4-92, 4-99 QPL harvester enhancements for NX
Preferences . . . . . . . . . . . . . . . . . . . . . 4-71 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
ADA_allow_gov_classification_
propagation . . . . . . . . . . . . . . . 4-167 R
ADA_allow_ip_classification_
propagation . . . . . . . . . . . . . . . 4-167 Realized By relationship . . . . . . . . . . . 4-38
ADA_allow_license_propagation . . . 4-167 Reconcile dialog box . . . . . . . . . . . . . . 4-28
Change Manager . . . . . . . . . . . . . . . 4-10 Red
IMAN_show_open_in_pv_button . . . . 2-21 Background . . . . . . . . . . . . . . . . . . . 4-92
ItemCreation.NoMasterForm . . . . . . 4-84 Datasets . . . . . . . . . . . . . . . . . . . . . 4-92
ItemCreation.NoRevMasterForm . . . . 4-84 Reference designators . . . . . . . . . . . . . 4-58
LDAP_sync_group_flags . . . . . . . . . . 4-72 Relationships . . . . . . . . . . . . . . . . . . . 4-38
LDAP_sync_member_flags . . . . . . . . 4-72 Removal
LDAP_sync_role_flags . . . . . . . . . . . 4-72 Multiple View Editor . . . . . . . . . . . . 2-22
LDAP_sync_user_flags . . . . . . . . . . . 4-72 MVE . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Obsolete . . . . . . . . . . . . . . . . . . . . . 2-25 Repair Broken Links dialog box . . . . . . 4-37

Index
Repeatable Digital Validation . . . . . . . . 3-30 Datasets . . . . . . . . . . . . . . . . . . . . . 4-92

Report Builder Guide . . . . . . . . . . . . 4-143 Deprecated on UNIX-based operating
Report Designer systems . . . . . . . . . . . . . . . . . . . . 2-6
Deprecating . . . . . . . . . . . . . . . . . . . . 2-5 Hangs with the Lifecycle Viewer . . . . 4-31
Property Finder Formatter search Interface . . . . . . . . . . . . . . . . . . . . 4-144
results . . . . . . . . . . . . . . . . . . . . 4-51 Lite Edition . . . . . . . . . . . . . . . . . . . . 4-2
Release notes . . . . . . . . . . . . . . . . . . 4-51 Microsoft Office documents . . . . . . . . 4-92
Report style sheets . . . . . . . . . . . . . . 4-51 Modal dialogs . . . . . . . . . . . . . . . . . 4-92
Support . . . . . . . . . . . . . . . . . . . . . . 4-51 PowerPoint . . . . . . . . . . . . . . . . . . . 4-92
Reporting and Analytics Ready status . . . . . . . . . . . . . . . . . . 4-91
Database query . . . . . . . . . . . . . . . . 4-53 Red background . . . . . . . . . . . . . . . . 4-92
Filter conditions . . . . . . . . . . . . . . . 4-53 Release notes . . . . . . . . . . . . . . . . . . 4-91
Firefox browser . . . . . . . . . . . . . . . . 4-52 Rich client server fails . . . . . . . . . . 4-102
IS NULL operator . . . . . . . . . . . . . . 4-53 Viewer . . . . . . . . . . . . . . . . . . . . . . . 4-4
Mapper . . . . . . . . . . . . . . . . . . . . . . 4-53 Rules
Release notes . . . . . . . . . . . . . . . . . . 4-52 In Project . . . . . . . . . . . . . . . . . . . . . 4-8
Reports problems . . . . . . . . . . . . . . . 4-52 Owning Group . . . . . . . . . . . . . . . . . . 4-8
Saved query . . . . . . . . . . . . . . . . . . 4-53 Owning Group Has Security . . . . . . . . 4-8
Scheduled tasks . . . . . . . . . . . . . . . . 4-52 Table . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Search . . . . . . . . . . . . . . . . . . . . . . 4-52 Running workflow process edits . . . . . . 3-11
preference . . . . . . . . . . . . . . . . . . . . 4-139 S
REQ_default_spec_template_for_export
preference . . . . . . . . . . . . . . . . . . . . 4-140 S1000D Content Management . . . . . . . 4-19
REQ_default_spec_template_for_view Safari Web browser . . . . . . . . . . . . . . . 4-14
preference . . . . . . . . . . . . . . . . . . . . 4-140 Save button . . . . . . . . . . . . . . . . . . . . 4-46
REQ_import_keywords preference . . . 4-140 SaveAs operation . . . . . . . . . . . . . . . . 4-94
Requirements Manager Saved query . . . . . . . . . . . . . . . . . . . . 4-53
Cascading LOVs not supported . . . . . 4-58 Schedule Manager
Data model deprecation . . . . . . . . . . 2-14 Calendar . . . . . . . . . . . . . . . . . . . . . 4-60
Importing requirement specifications with Data model deprecation . . . . . . . . . . 2-14
SpecElement subtypes . . . . . . . . . 4-54 Release notes . . . . . . . . . . . . . . . . . . 4-60
Multi-choice properties not Schedule deliverables . . . . . . . . . . . . 4-60
supported . . . . . . . . . . . . . . . . . . 4-58 Site Consolidation . . . . . . . . . . . . . . 4-60
Properties . . . . . . . . . . . . . . . . . . . . 4-54 SM_PV_FILTER_SHOW_SCHEDULES_
Reference designators . . . . . . . . . . . . 4-58 ON_EMPTY . . . . . . . . . . . . . . . 4-141
Release notes . . . . . . . . . . . . . . . . . . 4-54 Summary task . . . . . . . . . . . . . . . . . 4-60
REQ_default_object_template Schedule Manager Guide . . . . . . . . . . 4-146
preference . . . . . . . . . . . . . . . . 4-139 Schematics in Structure Manager . . . . . . 2-7
REQ_default_spec_template_for_export SCO replication . . . . . . . . . . . . . . . . . 3-13
preference . . . . . . . . . . . . . . . . 4-140 Scroll bar hidden . . . . . . . . . . . . . . . . . 4-23
REQ_default_spec_template_for_view Search errors . . . . . . . . . . . . . . . . . . . 4-91
preference . . . . . . . . . . . . . . . . 4-140 Security Services . . . . . . . . . . . . . . . . 4-78
REQ_import_keywords Selection Criteria preference . . . . . . . . 4-71
preference . . . . . . . . . . . . . . . . 4-140 Separation of view and edit properties
Word export documents, macros functionality . . . . . . . . . . . . . . . . . . . 4-64
disabled . . . . . . . . . . . . . . . . . . . 4-57 Sequences Access Manager rule . . . . . . . 4-8
Requirements Manager Guide . . . . . . 4-143 Server Customization Programmer’s
Resource Manager . . . . . . . . . . . . . . . . 4-59 Guide . . . . . . . . . . . . . . . . . . . . . . . 4-146
Resource Manager Guide . . . . . . . . . . 4-149 Service Planner . . . . . . . . . . . . . . . . . . 3-2
Resource pool subscription restriction . . 3-12 Service Planner Guide . . . . . . . . . . . . 4-149
Restricting resource pool subscription . . 3-12 Service planning . . . . . . . . . . . . . . . . . . 3-2
Rich client Shapes_Files attribute . . . . . . . . . . . . 4-120
Customization . . . . . . . . . . . . . . . . 4-144 Shapes_Name attribute . . . . . . . . . . . 4-120

Index
Simpgen translator . . . . . . . . . . . . . . . 4-80 T

Simulation tool configuration
enhancements . . . . . . . . . . . . . . . . . . 3-29 TC XML . . . . . . . . . . . . . . . . . . . . . . 4-114
Site TC_force_remote_sites_exclude_files
Check out . . . . . . . . . . . . . . . . . . . 4-119 preference . . . . . . . . . . . . . . . . . . . . . 4-75
Consolidation . . . . . . . . . . . . . 3-15, 4-60 TC_Populate_FSC_Server_Targets
site_util utility . . . . . . . . . . . . . . . . . 4-156 preference . . . . . . . . . . . . . . . . . . . . . 4-75
smlutility utility . . . . . . . . . . . . . . . . . 4-83 TC_relation_export_on_transfer
Software requirements . . . . . . . . . . . . . 1-5 preference . . . . . . . . . . . . . . . . . . . . 4-141
Solaris, Teamcenter EDA . . . . . . . . . . . 4-67 TC_remote_checkin_relation_send_as_replica
Specification Manager . . . . . . . . . . . . . 4-62 preference . . . . . . . . . . . . . . . . . . . . . 4-42
SSL support in Global Services . . . . . . . 3-14 tc.h header file deprecation . . . . . . . . . . 2-4
Standard data model transfer tcapps plug-in . . . . . . . . . . . . . . . . . . . 3-35
limitations . . . . . . . . . . . . . . . . . . . . 3-14 TcPLMXML . . . . . . . . . . . . . . . . . . . 4-114
Status TcPublishing
Rich client . . . . . . . . . . . . . . . . . . . . 4-91 Assets . . . . . . . . . . . . . . . . . . . . . . . 4-69
Workflow . . . . . . . . . . . . . . . . . . . . . 4-12 Classification search . . . . . . . . . . . . 4-34
Structure context enhancements . . . . . 3-32 Teamcenter
Structure Manager . . . . . . . . . . . . . . . 3-19 Help . . . . . . . . . . . . . . . . . . . . . . . 4-101
BOM restructuring . . . . . . . . . . . . . 4-38 Install or upgrading . . . . . . . . . . . . . . 1-1
Four-tier server session time-out . . . . 4-65 Services . . . . . . . . . . . . . . . . . . . . . . 2-8
Implemented By relationship . . . . . . 4-38 Tab buttons in Client for Office . . . . . 4-16
Incremental change . . . . . . . . . 4-63–4-64 Teamcenter EDA
NX export . . . . . . . . . . . . . . . . . . . . 4-93 Folder path problem . . . . . . . . . . . . . 4-66
Realized By relationship . . . . . . . . . . 4-38 Gateway . . . . . . . . . . . . . . . . . . . . . 4-66
Refresh . . . . . . . . . . . . . . . . . . . . . . 4-64 Mentor Board Station . . . . . . . . . . . . 4-67
Release notes . . . . . . . . . . . . . . . . . . 4-63 Release notes . . . . . . . . . . . . . . . . . . 4-66
Schematics . . . . . . . . . . . . . . . . . . . . 2-7 Solaris 10 . . . . . . . . . . . . . . . . . . . . 4-67
Separation of view and edit UNIX . . . . . . . . . . . . . . . . . . . . . . . 4-68
properties . . . . . . . . . . . . . . . . . . 4-64 Teamcenter EMC Content Storage Media
Structure Manager Guide . . . . . . . . . 4-147 Type . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Structured context object replication . . . 3-14 Teamcenter Enterprise relationship
Subscription restriction of resource problem . . . . . . . . . . . . . . . . . . . . . . 4-20
pools . . . . . . . . . . . . . . . . . . . . . . . . 3-12 Teamcenter File Services
Summary task in Schedule Manager . . . 4-60 Release notes . . . . . . . . . . . . . . . . . . 4-75
Sun Glassfish support deprecation . . . . . 2-2 Teamcenter Integration for NX
Sun Solaris Connections . . . . . . . . . . . . . . . . . . . 4-48
Ethernet MAC addresses . . . . . . . . 4-110 Default volumes value required . . . . . 4-50
Icons . . . . . . . . . . . . . . . . . . . . . . . 4-109 Download hyperlink not available . . . 4-48
Release notes . . . . . . . . . . . . . . . . . 4-109 Harness . . . . . . . . . . . . . . . . . . . . . 4-48
Server termination . . . . . . . . . . . . . 4-109 Harness structure . . . . . . . . . . . . . . 4-49
Support announcements . . . . . . . . . . . . 2-8 Invalid item IDs . . . . . . . . . . . . . . . . 4-49
Supported data model for transfers . . . . 3-14 Release notes . . . . . . . . . . . . . . . . . . 4-47
SUSE Linux Wire, deleting . . . . . . . . . . . . . . . . . 4-49
Enterprise Server (SLES) . . . . . . . . . 2-17 Teamcenter Publish support of Visio
Release notes . . . . . . . . . . . . . . . . . 4-111 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
SVG Viewer . . . . . . . . . . . . . . . . . . . . 2-22 Teamcenter’s lifecycle visualization
Swarming . . . . . . . . . . . . . . . . . . . . . . 3-16 iSeries . . . . . . . . . . . . . . . . . . . . . . 4-32
Synchronize data directories . . . . . . . . . 4-7 Product views . . . . . . . . . . . . . . . . . 4-32
System Administration Guide . . . . . . 4-147 .vvi file . . . . . . . . . . . . . . . . . . . . . . 4-31
System administration release notes . . . 4-71 .vvx file . . . . . . . . . . . . . . . . . . . . . . 4-31
Teamcenter’s simulation process
management . . . . . . . . . . . . . . . . . . . 3-29
Technical help . . . . . . . . . . . . . . . . . . . . 1-4

Index
Template list customization . . . . . . . . . 3-13 User, construct and access . . . . . . . . . . 4-72

Templates . . . . . . . . . . . . . . . . . . . . . . 4-7 USER_is_dataset_exportable user
Temporary graphics artifacts . . . . . . . . 4-32 exit . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Text file . . . . . . . . . . . . . . . . . . . . . . . 4-44 UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . 4-96
Thin client Utilities
CREATERENDERING style sheet . . 4-89 cae_geometry_fix . . . . . . . . . . . . . . . . 4-6
Customization release notes . . . . . . . 4-89 data_share . . . . . . . . . . . . . . . . . . . 4-96
Excel Report Builder Reports . . . . . . 4-93 Deprecated . . . . . . . . . . . . . . . . . . . . 2-7
Initial value property rules . . . . . . . . 4-93 generate_loadfsccache_tickets . . . . . . . 2-7
Non-Western European languages . . . 4-98 import_dfa_file . . . . . . . . . . . . . . . . . 2-7
NX export . . . . . . . . . . . . . . . . . . . . 4-93 item_to_part_design . . . . . . . . . . . . . 4-63
Release notes . . . . . . . . . . . . . . . . . . 4-93 ldapsync . . . . . . . . . . . . . . . . . . . . . 4-72
Structure Manager . . . . . . . . . . . . . . 4-93 make_user . . . . . . . . . . . . . . . . . . . 4-72
Thin Client Interface Guide . . . 4-149–4-150 Obsolete . . . . . . . . . . . . . . . . . . . . . 2-23
Third-party products Release notes . . . . . . . . . . . . . . . . . . 4-82
Applications support information . . . . 1-3 smlutility . . . . . . . . . . . . . . . . . . . . 4-83
Compatibility . . . . . . . . . . . . . . . . . . 1-3 Utilities Reference . . . . . . . . . . . . . . 4-154
Release notes . . . . . . . . . . . . . . . . . . 4-99 convert_replica_files_to_stubs
TIEPropertySet transfer options . . . . . 4-120 utility . . . . . . . . . . . . . . . . . . . . 4-154
Tomcat . . . . . . . . . . . . . . . . . . . . . . . . 4-73 data_share utility . . . . . . . . . . . . . 4-154
Tool tips in Content Management . . . . . 4-19 import_file utility . . . . . . . . . . . . . . 4-155
TraceLink class deprecation . . . . . . . . . 2-14 install_event_types utility . . . . . . . 4-155
Transient_Volume_RootDir pdx_export utility . . . . . . . . . . . . . 4-155
preference . . . . . . . . . . . . . . . . . . . . . 4-77 plmxml_export utility . . . . . . . . . . . 4-156
Transition Guide . . . . . . . . . . . . . . . . 4-152 pom_audit_manager utility . . . . . . . 4-156
Audit monitoring . . . . . . . . . . . . . . 4-152 site_util utility . . . . . . . . . . . . . . . . 4-156
Create Aerospace and Defense option
sets . . . . . . . . . . . . . . . . . . . . . 4-152 V
Export from Teamcenter . . . . . . . . . 4-153
Include Modified Objects Only . . . . . 4-153 Valid overlays only enhancement . . . . . 3-32
Stubs . . . . . . . . . . . . . . . . . . . . . . 4-152 Validation reports . . . . . . . . . . . . . . . . 4-46
Uses TcXML Payload check box . . . . 4-152 Value/description pairs display . . . . . . . 4-27
Translation, request priority . . . . . . . . 2-22 Variant
Two-tier mode . . . . . . . . . . . . . . . . . . . . 4-3 Condition . . . . . . . . . . . . . . . . 4-36, 4-41
Two-way SSL . . . . . . . . . . . . . . . . . . 4-167 Expression block errors . . . . . . . . . . 4-41
Vault table . . . . . . . . . . . . . . . . . . . . . . 4-8
U Vendor management . . . . . . . . . . . . . . 4-69
Verification rules . . . . . . . . . . . . . . . . 4-114
UGPART . . . . . . . . . . . . . . . . . . . . . 4-100 View menu . . . . . . . . . . . . . . . . . . . . . 4-95
Uninstalling Integration for Office . . . . 4-26 Viewer
Units converter . . . . . . . . . . . . . . . . . . 3-19 Lifecycle Visualization . . . . . . . . . . . . 4-4
UNIX systems Pane . . . . . . . . . . . . . . . . 4-30, 4-45–4-46
GM Overlay . . . . . . . . . . . . . . . . . . 4-113 Virus scanners and four-tier clients . . . 4-91
IDSM servers . . . . . . . . . . . . . . . . 4-112 Viso 2003 support in Teamcenter
Release notes . . . . . . . . . . . . . . . . . 4-112 Publish . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Text boxes . . . . . . . . . . . . . . . . . . . 4-112 Visualization Illustration
Upgrade Incremental change . . . . . . . . . . . . . 4-69
Access Manager rule tree . . . . . . . . . . 4-8 Modular variant configurations . . . . . 4-69
From Teamcenter . . . . . . . . . . . . . . . . 4-6 Release notes . . . . . . . . . . . . . . . . . . 4-69
In general . . . . . . . . . . . . . . . . . . . . . 1-1 Volumes
Upgrade Guide . . . . . . . . . . . . . . . . . 4-154 Allocation rules . . . . . . . . . . . . . . . . . 3-6
Usability release notes . . . . . . . . . . . . . 4-9 Failover for file import . . . . . . . . . . . . 3-6
USASCII7 character set . . . . . . . 4-88, 4-114 VOO enhancement, see Valid overlays only
Use temporary folders per session . . . 4-108 .vvi file . . . . . . . . . . . . . . . . . . . . . . . . 4-31

Index
.vvx file . . . . . . . . . . . . . . . . . . . . . . . 4-31 Null pointer exception . . . . . . . . . . 4-107

Power saving option error . . . . . . . . 4-102
W Release notes . . . . . . . . . . . . . . . . . 4-107
Text boxes . . . . . . . . . . . . . . . . . . . 4-112
Warming files . . . . . . . . . . . . . . . . . . . 4-75 Vista . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Web Application Deployment Guide . . 4-167 WinZip . . . . . . . . . . . . . . . . . . . . . . . 4-107
Web tier context parameters . . . . . . . . 2-20 Wire, deleting . . . . . . . . . . . . . . . . . . . 4-49
WEB_use_activex_lov preference . . . . . 4-99 Word, exporting data . . . . . . . . . . . . . . 4-57
WebKey account . . . . . . . . . . . . . . . . . . 1-4 Workflow
WebLogic Classification . . . . . . . . . . . . . . . . . . 4-12
HTTP-only flag . . . . . . . . . . . . . . . . 4-79 Data model deprecation . . . . . . . . . . 2-15
NoSuchMethodError exception . . . . . 4-24 Signoff task . . . . . . . . . . . . . . . . . . . 4-70
Version 9.1 . . . . . . . . . . . . . . . . . . . . 4-5 Templates . . . . . . . . . . . . . . . . . . . . 3-11
WebDAV . . . . . . . . . . . . . . . . . . . . 4-108 Workflow Designer Guide . . . . . . . . . 4-169
WebSphere 7 . . . . . . . . . . . . . . . . . . . 4-23
WeldPoint objects . . . . . . . . . . . . . . . . 4-36
Z
Windows
2003 Server . . . . . . . . . . . . . . . . . . 4-108 ZIP files . . . . . . . . . . . . . . . . . . . . . . 4-107
Network folders . . . . . . . . . . . . . . . 4-107

Teamcenter 8.3 Release Bulletin: Publication Number PLM00001 G (01-037134-083)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Teamcenter 8.3 Release Bulletin: Publication Number PLM00001 G (01-037134-083)

Загружено:

Авторское право:

Доступные форматы

Teamcenter 8.

This software and related documentation are proprietary to Siemens Product

2 Teamcenter 8.3 Release Bulletin PLM00001 G (01-037134-083)

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

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

Support and certification announcements . . . . . . . . . . . . . . . . . . . . . . . 2-1

What’s new for Teamcenter 8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

PLM00001 G (01-037134-083) Teamcenter 8.3 Release Bulletin 3

1 Before you begin

Installing or upgrading Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Teamcenter and compatible third-party software versions . . . . . . . . . . . . . . . 1-3

Global Technical Access Center (GTAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Available Teamcenter 8.3 platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Hardware, software, and disk space requirements . . . . . . . . . . . . . . . . . . . . . 1-5

Using documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

PLM00001 G (01-037134-083) Teamcenter 8.3 Release Bulletin

1 Before you begin

This release bulletin contains the following information:

• What’s new announcements

Installing or upgrading Teamcenter

– Release notes describing workarounds for known installation problems.

PLM00001 G (01-037134-083) Teamcenter 8.3 Release Bulletin 1-1

• If you are upgrading from Engineering Process Management or an earlier

– Release notes describing workarounds for known upgrade problems.

Also see the Upgrade Guide.

1-2 Teamcenter 8.3 Release Bulletin PLM00001 G (01-037134-083)

Teamcenter and compatible third-party software versions

• Compatibility for relinking customizations and paths.

Typically, operating system manufacturers assure run time binary compatibility

PLM00001 G (01-037134-083) Teamcenter 8.3 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 8.3 Release Bulletin PLM00001 G (01-037134-083)

Available Teamcenter 8.3 platforms

Teamcenter 8.3 is supported in the following language locales on all server-supported

Hardware, software, and disk space requirements

Corporate Two-tier rich

PLM00001 G (01-037134-083) Teamcenter 8.3 Release Bulletin 1-5

Using PDF files

• If you share the Teamcenter PDF Help Collection on a Web (HTTP)

– Network host (UNC path):

1-6 Teamcenter 8.3 Release Bulletin PLM00001 G (01-037134-083)

Using HTML files

PLM00001 G (01-037134-083) Teamcenter 8.3 Release Bulletin 1-7

2 Support and certification

Deprecated feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Obsolete feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

PLM00001 G (01-037134-083) Teamcenter 8.3 Release Bulletin

2 Support and certification

Certification announcements include notices about recommended use of this version,

Deprecated feature announcements

General deprecated feature announcements

• Deprecation of certification for Visio 2003 in TcPublish

PLM00001 G (01-037134-083) Teamcenter 8.3 Release Bulletin 2-1

• Deprecation of certification for Sun Java System Application Server

• Deprecation of headless application support

• Deprecation of Application Integration Environment (AIE)

2-2 Teamcenter 8.3 Release Bulletin PLM00001 G (01-037134-083)