Beruflich Dokumente
Kultur Dokumente
My Teamcenter Guide
Publication Number
PLM00046 I
Proprietary and restricted rights notice
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Figures
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Overview of My Teamcenter
The My Teamcenter application is the workspace you use to manage your product
information. My Teamcenter serves as the main access point for many commonly
used functions, such as object creation, checkin/checkout, task management, and
query execution in both the rich client and the thin client. The My Teamcenter Guide
presents the full range of capabilities provided in the rich client.
• The Teamcenter thin client is a Web-browser interface you can use to navigate
to various Teamcenter objects and functions. Access is available to the same
Teamcenter server and data as the rich client uses. No thin client software
is required on a Teamcenter client. The thin client interface can be used to
perform many of the same tasks you can perform in the rich client interface.
However, there are fewer distinct applications available in the thin client, and
administrative tasks cannot be performed in this interface.
For information about the capabilities provided by the thin client, see the Thin
Client Interface Guide.
For an overview of Teamcenter functionality and clients, see Getting Started with
Teamcenter.
o In applications that use multiple views, you can add and rearrange views to
display multiple sets of information simultaneously within a perspective.
o You can save a rearranged perspective with the current name, or create a
new perspective by saving the new arrangement of views with a new name.
In some Teamcenter applications, using rich client views and view networks, you
can navigate to a hierarchy of information, display information about selected
objects, open an editor, or display properties.
o Views that work with related information typically react to selection changes
in other views.
o Any view can be opened in any perspective, and any combination of views
can be saved in a current perspective or in a new perspective.
o A view network consists of a primary view and one or more secondary views
that are associated. View networks can be arranged in a single view folder
or in multiple view folders.
o Objects selected in a view may provide context for a shortcut menu. The
shortcut menu is usually displayed by right-clicking.
For information about using the shortcut menu, see Shortcut menus.
Note If your site has online help installed, you can access application and view
help from the rich client Help menu or by pressing F1. Some views, such
as Communication Monitor, Print Object, and Performance Monitor,
are auxiliary views that may be used for debugging and that may not be
displayed automatically by any particular perspective.
For more information about auxiliary views, see the Client Customization
Programmer’s Guide.
For more information about perspectives and views and changing the layout of your
rich client window, see the Rich Client Interface Guide.
2 My Teamcenter fundamentals
2 My Teamcenter fundamentals
• Search for objects, both in your local site database and at remote sites, using
predefined queries.
My Teamcenter views
The Teamcenter rich client provides the My Teamcenter perspective consisting of
multiple views designed to provide access to the latest Teamcenter features and
functionality.
By default, the My Teamcenter perspective displays the Home component view
beside the navigation pane, and the Summary, Details, Impact Analysis, Viewer,
JT Preview, and Process History views. Additional views can be used in the My
Teamcenter perspective, such as the MS Word, Search, and Simple Search views.
For a list of views provided with the My Teamcenter perspective, choose
Window®Show View®Other to display the Show View dialog box, and then expand
the Teamcenter folder.
Component views
The Teamcenter Component view is opened by default by several Teamcenter
perspectives.
Component views support standard navigation functionality such as expand,
expand-all, and double-click, as well as standard context-specific shortcut menus.
In the My Teamcenter perspective, the default component view is the Home view,
and every object opened in My Teamcenter gets its own component view.
When you open an object in My Teamcenter, a new component view opens with
the opened object as the root.
This view lets you navigate the content of the opened object. For example, opening
My Worklist from the navigation pane opens an instance of the component view
with your worklist as the root node. Similarly, opening the Newstuff folder opens a
component view with your Newstuff as the root node and clicking My Projects opens
a component view with your current project as the default node.
A component view includes the following elements:
• View menu
Contains:
o The Move menu, for moving selected objects to a different level in the tree
display.
Up moves a selected folder up (for example, closer to the top-level folder) to
the area of the tree that you specify.
Down moves a selected folder down to a location that you specify.
Top moves a selected folder to the top of the tree.
Bottom moves a selected folder to the bottom of the tree.
Summary view
The Summary view lets you see properties for a selected object and edit attributes
such as name or description for supported items for which you have appropriate
permissions.
The configuration and contents of the Summary view vary according to the
information display configured for type of object selected.
• The Summary view toolbar includes buttons to let you check out and edit the
properties of objects, check in and save edited properties, cancel checkout, or
save changes and keep checked out.
• The area at the top of the view displays basic information about the selected
object.
• The Summary view may include the following expandable and collapsible areas:
o One or more Properties areas
• Tabs, such as Overview, Attachments, and History are displayed, as needed and
as configured, to organize information about the selected object.
• Action buttons, such as Copy, Save As, Revise, and Submit for Review are
displayed. The location of these buttons vary based on the objects selected.
• When the functionality is enabled, you can see when other users are available
for instant messaging with Microsoft Office Communicator. You can view the
current status of the owning and last modified users, and you can click the
Microsoft Office Communicator symbol in Teamcenter to initiate communication.
• Within a specified area, the groups of objects within each tab (object sets) are
configured in the XRT style sheet. Each group of information can be configured
to display in table, list, tree, or thumbnail format. Each can also be supported
by action command buttons such as Cut and Copy.
For information about creating object sets, see the Client Customization
Programmer’s Guide.
• With objects selected in the table, you can right-click a column head to display
the shortcut menu.
Note The default display order for column contents in most views is specified by
the Teamcenter server. In the rich client, you can click a column header to
cycle through ascending, descending, and server default order. For rich client
Teamcenter component (tree) views and for the Search Results view, use
Edit®Options to display the Options dialog box, and then select UI and click
the General tab to select a Tree displaying order option.
• Column
Displays the Column Management dialog box. Use this dialog box to select
properties to display and column order.
o Select Default and click Apply to restore the default column configuration
to the Details view table display. This restores columns removed by the
right-click Remove this column command.
• Sort
Provides three levels of sorting.
• Filter
Displays the Auto Filter dialog box with available condition expressions.
o The ALL option displays properties for all the children of the object currently
selected in the component view.
o You can use the Filter Condition Editor to create condition expressions for
filtering the display.
o Expressions cannot be edited after they are listed in the Auto Filter dialog
box, but they can be deleted.
o Teamcenter retains your filter condition expressions until you delete them.
To create conditions, click Add a new search condition to display the Filter
Condition Editor.
o To expand the expression with additional conditions, use the ADD and OR
operators.
o Click OK to add the condition expression to the Auto Filter dialog box.
• Find In Display
Displays the Find In Display dialog box that lets you find objects based on
property names and search values.
• Print Table
Lets you print to either HTML/Text using the Teamcenter Print dialog box, or
Graphics, using the system printers.
o With Headers
o Without Headers
o For Query
This option displays the Select Columns For Query dialog box in which you
can select specific properties to copy.
• Objects to Word
Displays the Export To Word dialog box. You can specify:
o Output: Static Snapshot, Live Integration with Word, Export for Markup
o Live options: Export for structure editing and work offline, Check out
objects before export
Note The checkout applies to all objects being exported. You should use
this option carefully if you are exporting a large set of objects or
perhaps an entire specification.
o Template override
To use a Word export template other than the default, select a template from
the Specification Templates list or select an object type from the Override
Object Template for: list. If you select an object type from the Override
Object Template for: list, you then select a template from the Available
Object Templates list to add to the table.
o Copy URL
The URL Generated message is displayed, confirming that the URL for the
export document is in your Windows Clipboard and showing the URL details.
Note The Copy URL button is unavailable if you select more than
one object to export.
o OK
Generate the export Word file.
• Objects to Excel
Displays the Export To Excel dialog box. You can specify:
o Object Selection
Either Export Selected Objects or Export All Objects in View.
o Output Template
Either Export All Visible Columns or Use Excel Template.
When you export all visible columns to Excel, the relation column is not
exported because the relation is not a property on the object.
The Use Excel Template option provides access to a list of templates.
o Output
Either Static Snapshot, Live integration with Excel (Interactive), Live
integration with Excel (Bulk Mode) or Work Offline and Import.
Note Export using work offline mode exports properties such as item_id,
object_name and the real type name so that the data can be
imported correctly to Teamcenter. These properties are exported
even if they are not specifically selected.
Only numeric and string properties are supported for import
from Excel. Read-only, reference, and relation properties should
be marked as Ignored in the Excel control file sheet. Run-time
properties also are not supported for work offline.
o To check out objects while exporting to live Excel, select Check out objects
before export.
Note The checkout applies to all objects being exported. You should use
this option carefully if you are exporting a large set of objects or
perhaps an entire specification.
o Copy URL
The URL Generated message is displayed, confirming that the URL for the
export document is in your Windows Clipboard and showing the URL details.
Note Copy URL is unavailable if you select more than one object to
export.
o OK
Generate the export Excel file.
• Objects to CSV
Displays the Export To CSV dialog box to export Teamcenter data in
comma-separated value (CSV) format. You can specify:
a. To add a column, select a property from the Available Properties list and
click the Add to Displayed Columns button .
3. (Optional) Click the Move Up and Move Down buttons, to the right of the
Displayed Columns list, to adjust the order of the displayed columns.
4. Click Apply to apply the configuration to the current view, or click Save to save
the configuration for later use.
Note You can use the Apply Column Configuration command on the view
menu to:
• Apply a saved configuration.
You can use the Save Column Configuration command on the view
menu to save the current configuration of the table display.
Viewer view
The content displayed in the Viewer view depends on the type of the object selected
in the current component view or in the Details view.
• To display the form attributes, select a form object in a component view or in
the Details view.
• To display Microsoft Office datasets in the Viewer view, display the Viewer view
and then click the dataset in the component view.
Note When you double-click a dataset, the stand-alone Microsoft Office
application is launched with the dataset. If you then click the dataset in
the component view to display the contents of the dataset in the Viewer
view, you cannot save changes to the dataset from the stand-alone
application.
o For Microsoft Office 2010, use the Microsoft Let me fix it myself method
available at http://support.microsoft.com/kb/982995.
Note The patches are designed for systems using Internet Explorer 7 and
Internet Explorer 8.
If the patch installer displays a message indicating the fix does not
apply to your operating system or application version, use the Let me
fix it myself method described on the link pages to create the registry
file manually and apply the patch.
Embedded Word is not supported when running the 32-bit version of
Microsoft Word with the 64-bit Teamcenter rich client.
For information about the working with 2D and 3D data, see Getting Started
with Product Visualization.
For information about creating and working with snapshots, see the Lifecycle
Visualization Integration Guide.
• To display the object properties for the item or item revision with no associated
displayable datasets, select the item or item revision.
Note When the functionality is enabled, you can see when other users are
available for instant messaging with Microsoft Office Communicator.
You can view the current status of the owning and last modified
users, and you can click the Microsoft Office Communicator symbol in
Teamcenter to initiate communication.
• To display Web Link object properties in the Viewer view, select a URL link
object in a component view.
Note When you select a URL link object, Teamcenter automatically opens a
Web Browser view to display the Web page associated with the object.
• To display the content of a text file or PDF file in the Viewer view, or to display or
edit standard office files such as Microsoft Word or Excel files in the Viewer view,
click on the dataset object in a component view or a Details view.
Note This functionality depends on your system settings for browsing
documents in the same window.
For example, to enable editing of a Microsoft Word document in the
Viewer view in a Teamcenter client on a Windows XP system, open a My
Computer window and choose Tools→Folder Options. In the Folder
Options dialog box, select the DOC extension for the registered file type,
and then click Advanced to display the Edit File Type dialog box. For the
Open action, select Browse in same window.
• 2D Markup
Create 2D markups.
• 2D Measurement
Perform 2D measurements.
• 2D Multipage
Navigate among pages in multiple-page 2D images or documents.
• 2D Viewing
Pan, zoom, rotate, and flip 2D images.
• 3D Markup
Create 3D markups.
• 3D Measurement
Perform 3D measurements.
• 3D Navigation
Pan, rotate, and zoom 3D models.
• 3D PMI
View and manipulate PMI in your model.
• 3D Section
Create 3D cross sections.
• 3D Selection
Select parts and pick part entities.
• 3D Standard Views
Examine your model from preset viewing angles.
• ECAD Base
Manipulate the view of ECAD document layers, control layer color and visibility,
search, and create reports.
• ECAD Markup
Create ECAD markups.
• ECAD Multipage
Navigate among pages in multiple-page schematic documents.
• ECAD Viewing
Pan, zoom, rotate, and flip image.
• Print
Print documents.
Use this preference to specify the default Viewer view configuration by defining
which Generic Relationship Management (GRM) rules to expand and the viewer
to use for each type of object specified in the preference.
• <viewer-config-ID>.VIEWERCONFIG
Use this preference to specify an alternate Viewer view configuration instead
of the defaultViewerConfig.VIEWERCONFIG preference. This preference
defines which Generic Relationship Management (GRM) rules to expand, and
the viewer to use for each type of object specified in the preference.
• Viewer.VIEWERCONFIGTOLOAD
Use this preference to specify the Viewer view configuration to load. This
preference must point to a .VIEWERCONFIG preference name.
By default, this preference points to the
defaultViewerConfig.VIEWERCONFIG preference. To point to an alternate
preference, enter a <viewer_config_id>.VIEWERCONFIG preference name.
For information about how to define a custom viewer, see the Client Customization
Programmer’s Guide.
The Impact Analysis view responds to the current selection in the active component
view and provides the following functionality:
• Search Text box and Find button. Search supports the following actions:
o Press Enter or click the Find button to start a search.
o Press F3, Page Down, or Down to find the next matching object.
• Open button to display the Open by Name dialog box that lets you use names,
wildcard characters, and revision level to find objects. You can copy found objects
to the clipboard, load all found components into the table, and step through
found components in groups.
• Where
Select either Referenced or Used.
• Depth
Select One Level, All Levels, or Top Level.
• Where-Used/Referenced Report
Note
The Impact Analysis view lets you disable and enable responsiveness
to selections in other views, so you can keep the currently selected root object
in the view while you investigate other objects in other views.
This option returns all instances and classes found in the database that
contain references to the selected instance.
For more information, see the Preferences and Environment Variables
Reference.
My Teamcenter menus
Menu commands are available in an initial installation of the Teamcenter software.
Note The My Teamcenter menu commands available at your site may differ based
on site-specific configuration, customization, and application integration.
File menu
Use File menu commands to create and manage your data objects, close an
application, and exit the rich client.
Command Purpose
New Creates a wide range of Teamcenter objects.
For File→New menu command descriptions, see File New menu.
Opens for viewing and editing a selected data object—folder, item,
Open item revision, or dataset—in the default application for that object
or file type.
Open With Opens a dialog box to let you select an application for viewing a
selected data object or file.
View Opens for viewing a selected data object—folder, item, item
revision, or dataset—in the default application.
View With Opens a dialog box to let you select an application for viewing a
selected data object.
Command Purpose
View/Markup Lets you work with:
• Microsoft Word files to view, create, or update markups using
Microsoft Word.
Command Purpose
Creates Teamcenter objects such as items, folders, forms,
Item datasets, URL links, IDs, item elements, BOM view revisions,
structure contexts, collaboration contexts, and work contexts, as
well as interface definition, process variable, connection, signal,
process, change, envelope, CAE item, and schedule objects.
For File→New→Item menu command descriptions, see File New
Item dialog box.
Creates a graphical representation of an aggregation of objects.
Folder
Creates a data object used to display product information
Form (properties) in a predefined template. Forms can be used to create
an electronic facsimile of a hardcopy form.
Creates a Teamcenter data object used to manage data files
Dataset created by other software applications. Each dataset can manage
multiple operating system files, and each dataset references a
dataset tool object and a dataset business object.
Creates a data object used to access a Web resource. The URL
URL (uniform resource locator) is an address that is used as a link
to access a Web resource within Teamcenter or in a separate
browser.
Creates alternate identifiers and alias identifiers used to
ID communicate information about items and item revisions.
Alias identifiers store part numbers and other attribute
information for similar parts, and they can be associated with
many items or item revisions. Alias IDs can store information
about external entities and can also be used to maintain a cross
reference of the relationships between other manufacturer’s part
numbers and the part numbers used by your organization.
Alternate identifiers store information about part numbers
and attributes of the same part from different perspectives.
Alternate IDs let different user communities identify and display
an item or item revision according to their own rules rather
than according to the rules of the user who created the object.
Assigning alternate identifiers to a part at different stages of
development and production allows you to maintain a history of
the life cycle of the part.
Command Purpose
Item Element Creates objects to represent design or manufacturing features
that are not defined as part of the physical structure in the BOM.
Features are implemented as item elements, sometimes called
general design elements (GDEs). For information about specific
item element feature types, see the appropriate application
documentation. For example, HRN_ objects correspond to wiring
harness design objects in Teamcenter.
For more information about working with wiring harness objects,
see the Wiring Harness Design Tools Integration Guide.
BOMView Creates a revision of a BOM view.
Revision When an item is an assembly of other items, its assembly
structure is represented by a BOM view, which is a data object
distinct from the item in order to support multiple views
functionality. The structure of the assembly item may change
between successive revisions of the item. Therefore, the actual
structure information of an item revision is stored in a BOM view
revision referenced by that item revision.
For more information about creating a BOM view revision object,
see Getting Started with Product Structure.
Structure Creates a configurable structure data object that consists of
Context one or more root objects sharing the same configuration. For
example, it may be one or more BOMs or assembly structures and
their configurations. The configuration of the structure context
is defined by a configuration context. The structure objects may
have occurrence groups, items, and item revisions.
For more information about structure contexts, see Getting
Started with Product Structure.
Configuration Saves a configuration consisting of revision rules or variant rules
Context that you can retrieve and assign to a structure context.
For more information about configuration contexts, see the
Multi-Structure Manager Guide.
Collaboration Creates a data object containing one or more structure and
Context configuration contexts.
For more information about collaboration contexts, see the
Multi-Structure Manager Guide.
Command Purpose
Work Context Creates a profile that a user assumes to complete a specific
assignment. Work contexts are created from a combination of
user name, group, role, and project; however, it is not necessary
to include all four of these elements in the definition of a work
context. For example, if a task can be performed by anyone,
regardless of their group and role, the work context specifies
only the project to which the context applies. If a task can be
performed only by a user with a specific role within a group, the
work context definition specifies the project, group, and role, but
not a specific user.
For more information about work contexts, see Managing work
contexts.
Service Creates new objects for use in the Service Manager application.
Request
Service Creates new objects for use in the Service Request Manager
Catalog application.
Connection Creates the object that defines the connectivity between two or
more terminals in a physical model.
Command Purpose
Issue Report Used to track and fix problems with a product. An issue report
object contains information about the problem, including relevant
parts, snapshots, and reference data.
For more information about creating issue report objects, see
the Issue Manager Guide.
Use the File→New→Item menu command to display a dialog box with options to
create new objects.
Note The available new item options vary according to preference settings and
the applications installed and enabled at your site. The following table lists
descriptions of typical items.
Command Purpose
Creates objects that can have attached starting files for
DMTemplate creating objects of other item types. These template objects are
application specific and can include any kind of starting files
and preview or thumbnail image files, useful for engineering
applications such as NX.
Creates items with relations to Microsoft Office applications
Document such as Microsoft Word, Microsoft Excel, and so on.
Represents functional breakdown of a product. In this case,
Functionality you can use an item to represent a function.
For more information about this type of item, see Getting
Started with Mechatronics Process Management.
Creates any sort of standard item object in Teamcenter.
Item
Paragraph, Create Paragraph, Requirement, and RequirementSpec
Requirement, and requirements objects for use with Systems Engineering.
RequirementSpec
For more information about these options, see the Systems
Engineering Guide.
Review_Pckg For Teamcenter Rapid Start, creates a review package object.
Edit menu
Use the Edit menu commands to perform basic editing tasks on selected objects,
view and/or change user settings and preferences, and to move selected objects
around in the tree structure.
Note You must have read and write privileges to the objects you want to cut, copy,
or paste.
Command Purpose
Cut Removes a selected data object reference from the current location
and places it on the clipboard. You must have read privileges on
the object and write privileges on its container to move or remove
an object.
Copy Replicates a data object reference in another application. You
must have read privileges for the selected object that you want to
copy. You can also create a copy by dragging the object to another
Teamcenter application.
Command Purpose
Copy Copies a selected workflow process to your Teamcenter clipboard.
Workflow
Process Note Choose Copy or Copy Workflow Process to accomplish
your goal with a selected task. If you choose Copy, just
that task is copied to the clipboard. If you choose Copy
Workflow Process, the root process is copied to the
clipboard.
Paste Moves a data object reference from the clipboard to the current
location in the data object area. It is important to select the
proper destination for the data object reference before choosing
the Paste menu command. You must have read and write
privileges to the destination object.
Note If your administrator has defined mandatory properties
for the type of relation by which the pasted object
reference (secondary object) is associated to the primary
object, a dialog box lets you define attribute values for
the objects.
Paste Special Allows you to specify a relation type rather than using the default
paste relation when pasting an object reference into an item or
item revision.
Note If your administrator has defined mandatory properties
for the type of relation by which the pasted object
reference (secondary object) is associated to the primary
object, a dialog box lets you define attribute values for
the objects.
Properties For selected single editable objects, displays the Check-Out dialog
box, and then displays the Edit Properties dialog box for the
selected object.
For selected multiple editable objects, displays the Check-Out
dialog box, and then displays the Common modifiable properties
dialog box for the selected objects.
Delete Deletes a selected data object from the database. You must have
delete permission for the object to use this command. You can also
use the Explore Selected Components option (available in the
Delete dialog box) to select related objects for deletion by either
selecting them from the tree or applying type/relation rules.
Note You cannot delete from the database an object that is
referenced in multiple locations. Therefore, to delete an
object from the database, you may need to perform a
where-referenced search to locate all references to the
object, then contact all the owners of the references and
ask them to delete their references to the object. When
there are no remaining references, you can delete an
object for which you have delete permission.
Command Purpose
Command Purpose
User Setting Provides access to the User Setting dialog box used to:
• View, define, or change company and group profile information
for a user.
View menu
View menu commands let you refresh your display, with hierarchical information,
and see object access and user information.
Command Purpose
Refresh Reads information from the database and updates the information
displayed in the workspace area.
Refresh Refreshes the information displayed in the workspace area.
Window
Access Allows you to view, change, and/or apply access permissions for
a selected object.
Named Allows you to view, upload, or download the name references of
References a selected dataset.
You can use the function buttons in the dialog box to cut or copy
a selected reference to the clipboard and paste references from
the clipboard.
Current Users Displays a table containing information relating to all currently
logged-on user sessions. Users with dba privileges can also use
this command to purge dead user sessions.
For information about how a user with dba privileges creates and
manages user accounts, see the Organization Guide.
Allows you to view, update, or print the properties of a selected
Properties data object.
Audit Allows you to view audit logs based on site-defined audit
definition objects.
Organization Displays your Teamcenter organizational structure including the
groups in your enterprise, the roles in each group, and the users
assigned to each role.
For information about how a user with dba privileges creates and
manages the information displayed in the organization chart, see
the Organization Guide.
Effectivity Lets you display the Effectivity dialog box to let you create, edit,
copy, and delete effectivities for an item. Also lets you view
effectivity mappings of revisions for configuration items.
Tools menu
Use the Tools menu commands to perform actions on objects, such as checking them
in and out, and to create and manage address lists and generate reports.
Command Purpose
Check-In/Out Reserve exclusive access to one or more objects and/or their
attachments by locking the objects in the database upon checkout.
You restore access to the objects using check-in. Only your
administrator is allowed to circumvent the security that these
menu commands provide.
ID Display Rule Sets the display rule for items and item revisions based on
alternate identifier context.
Command Purpose
Process Attach the selected structure to a Workflow process or change.
Change
Selector
Project Assigns or removes objects from projects.
For more information about projects, see the Project and Program
Guide.
Validation Lets you run validation agents and view results. Agents validate
the attributes of relevant targets under a selected data object,
using third-party software applications, based on criteria
established by your local administrator.
Review Issue Lets you investigate issues to determine whether they must be
fixed immediately, can be rejected, or can be deferred.
For more information about managing issues, see the Issue
Manager Guide.
Assign Work Lets you assign a profile that a user assumes to complete a specific
assignment. Work contexts are created from a combination of
Context user name, group, role, and project.
Manage Global Lets you work with global alternates. A global alternate part is
Alternates interchangeable with another part, regardless of where the part
is being used in the product structure.
For more information about global alternates, see the Structure
Manager Guide.
Creates a new dataset based on your work-in-progress (WIP)
Baseline design and attaches a copy of the currently configured structure
to that dataset.
For more information about creating a baseline, see Getting
Started with Product Structure.
Resource Pool Allows you to subscribe to a resource pool.
Subscription
Remote Inbox Allows you to subscribe to inboxes based on the Teamcenter
Subscription registry.
Subscribe Allows you to create subscriptions.
You can also access this menu command from a shortcut menu
by right-clicking a data object.
Note This menu command must be enabled by your Teamcenter
administrator.
Subscription Allows you to manage (query, edit, and delete) persistent
Manager subscriptions.
You can also access this menu command from a shortcut menu
by right-clicking a data object.
Command Purpose
Add Design to Opens the Add Design to Product wizard that guides you through
adding your CAD design to an installation assembly attached to
Product an architecture breakdown element.
For information about adding designs to products, see the
Platform Designer Guide.
Add Part to Opens the Add Part to Product wizard that guides you through
adding an enterprise resource planning (ERP) part to an
Product
architecture breakdown element.
For information about adding parts to products, see the Platform
Designer Guide.
Multi-Site Controls the data shared with participating sites in a distributed
Collaboration network. Multi-Site Collaboration allows you to publish and
unpublish objects, send objects for remote export or remote
checkout, register or unregister item identifiers, and synchronize
objects, components, and assemblies.
• Publishing an object makes that object available to other
Teamcenter sites. When you publish an object, a publication
record is created in the Object Directory Service (ODS) that
can be read and searched by other sites. Until you publish an
object, it can be seen only by the local owning site. Other
Teamcenter sites are not aware that the object exists.
Command Purpose
about the Access Manager rules that control publishing
privileges.
Command Purpose
Open Live Lets you use Microsoft Excel to change the values of editable
properties for selected objects by generating an interactive Excel
Excel file that is synchronized with the Teamcenter database.
For more information about working in live Excel files, see the
Extensions for Microsoft Office Guide.
Compare For comparing two requirements or comparing a requirement
Contents or specification to a previous versions, lets you start and end
comparisons, or compare to a previous object.
For more information about comparing requirement content, see
the Systems Engineering Guide.
Trace Report Displays complying or defining objects related to a selected
linking or data object.
For more information about trace links and complying objects, see
Linking objects using trace links.
Check Index Displays the status of the full-text search index for the selected
Status objects and also allows you to refresh the index for these objects.
Site Provides access to menu commands for Check-Out to site,
CheckInOut Check-In from site, and Cancel Check-Out to site.
Localization Lets you export, import, and filter objects for localizations.
For more information about exporting localization files, see the
Localization Guide
Reports Lets you select an option:
• Report Builder Reports launches the Report Generation
wizard.
Command Purpose
Part/Design Lets you specify the selected item revision to be the primary
representation or reset the primary representation of the part.
If no appropriate item revision is selected, the system displays
a message prompting you to select an item revision under part
representations.
Actions menu
The Actions menu contains commands used for setting the actions of tasks. All
commands on the Actions menu require privileged user status to function.
If a task is designated to process in the background, all actions except Perform and
Assign are processed in the background. The Perform and Assign action execute
in the foreground.
Note The Actions menu is displayed in My Teamcenter when My Worklist is
selected from the Quick Links section in the navigation pane.
Command Description
Perform Displays the Perform dialog box for the selected task. The contents
of the dialog box varies depending on the task selected.
Assign Reassigns the selected task to another user.
Start Manually starts a task. This command works only in certain
circumstances.
For more information, see Start a paused task.
Complete Manually completes a task, if it is in either the Started or
Pending states.
Suspend Moves a selected task to a Suspended state. The only valid action
from a Suspended state is Resume.
Resume Moves a selected task from a Suspended state to the previous
state.
Promote Places the selected task into a Skipped state, and starts the
successor tasks in the workflow process. For Review and Route
tasks, the successor task can be either along the approve or reject
path, depending on the user’s selection.
Undo Changes a selected task state from Started, Completed, or
Skipped to a Pending state.
Stand-In Allows you to perform the task while allowing the original user to
retain control.
Autoset When the selected item or task has a work context defined, sets
Current your user settings so you can work with the current item or task.
WorkContext
For more information about work context, see Managing work
contexts.
Window menu
Use the Window menu commands to open a new application window and customize
your desktop.
Command Purpose
Open This command is not used by default. If enabled at your site, this
Perspective command allows you to open alternate collections of view panes.
Show View Allows you to open alternate views.
Depending on the configuration at your site, a variety of views
may be available.
1. Choose Window®Show View®Other to display the Show View
dialog box.
3. Select a view.
4. Click OK.
Command Purpose
Security
Standard Eclipse functionality.
Teamcenter
Show traditional style tabs
Select to display rectangular tabs instead of rounded tabs.
Minimum characters for view title
Specifies the minimum number of characters displayed in view
titles prior to putting titles into the associated view list.
Search
Select to set a wide range of search options.
For information about setting search options, see the Rich
Client Interface Guide.
View Network Presentation
Select to set colors and patterns for view networks.
For information about changing view network color and pattern
presentation options, see the Rich Client Interface Guide.
Note Most Teamcenter application options and preferences are
set in the Options dialog box. Choose Edit→Options to
display the Options dialog box.
For more information about options and preferences, see
the Rich Client Interface Guide.
Toolbar Displays or hides the toolbar. A check mark indicates that the
toolbar is displayed under the menu bar.
Navigation Displays or hides the navigation pane. A check mark indicates that
Pane the navigation pane is displayed.
Full Screen Alternates between full-screen display and adjustable-window
display.
Translation menu
Use Translation menu commands to translate:
• CAD data files to 3D or 2D file formats for viewing in Teamcenter lifecycle
visualization.
• Document dataset files from Microsoft Word format to zipped files and PDF files.
Note The Translation menu is displayed only when Dispatcher is installed and
configured.
For information about installing, configuring, and administering Dispatcher,
see Getting Started with Dispatcher (Translation Management).
Command Purpose
Translate Displays the Translation Selection dialog box with columns
indicating the name of the object being translated, the dataset
type, the provider of the dataset type, and the translator to service
the request.
For more information about using the Translate command, see
Translating dataset files.
Note When you choose the Translate menu command without
an appropriate dataset selected, the system displays a
dialog box with a message describing the error.
Administration Displays the Request Administration dialog box and queries the
Console database to retrieve translation processes.
For information about administering Dispatcher, see Getting
Started with Dispatcher (Translation Management).
Help menu
You can use the Help menu commands to access the online help index, see
view-specific help, and find information about the application that is currently
running in the rich client interface.
Online help is not always installed, and for some views, online help is not available
from the Help→Current Application menu command, the F1 key, or both.
When online help for a view is not available from the function key or menu command,
follow these steps:
1. Choose Help→Help Library.
• If help is installed, a browser displays the help collection.
4. Locate the view for which you are seeking online help and click the link to
display additional information.
For more information about the viewing online help, see Getting Started with
Teamcenter.
Shortcut menus
When you select an object in a rich client view, you can often use the right mouse
button to display a shortcut menu containing commands relevant to the currently
active application or the currently selected object. The shortcut menu is dynamic;
the available commands reflect the current context.
Shortcut menu commands are referenced and described in procedure and reference
documentation in context of the application or object selection to which the
commands apply.
Note On some Linux platforms, you must hold down the right mouse button while
you select the desired command.
Command Purpose
Copy Lets you copy a Teamcenter reference to a selected image,
Reference Microsoft Excel, or JT dataset and paste that reference into a
Microsoft Word document.
For more information about adding a dataset reference to a Word
document, see the Systems Engineering Guide.
New Change When an item revision is selected, displays the New Change
in context in context dialog box. You can select the type of change to be
created, such as a problem report or a change request.
For more information about creating change objects, see the
Change Manager Guide.
New Creates a new object of a selected type.
Cut Removes a selected data object reference from the current location
and places it on the clipboard. You must have read privileges on
the object and write privileges on its container to move or remove
an object.
For more information about cutting, copying, pasting, and
deleting data objects, see the Rich Client Interface Guide.
Copy Replicates a data object reference in another application. You
must have read privileges for the selected object that you want to
copy. You can also create a copy by dragging the object to another
Teamcenter application.
For more information about cutting, copying, pasting, and
deleting data objects, see the Rich Client Interface Guide.
Command Purpose
Paste Moves a data object reference from the clipboard to the current
location in the data object area. It is important to select the
proper destination for the data object reference before choosing
the Paste menu command. You must have read and write
privileges to the destination object.
For more information about cutting, copying, pasting, and
deleting data objects, see the Rich Client Interface Guide.
Note If your administrator has defined mandatory properties
for the type of relation by which the pasted object
reference (secondary object) is associated to the primary
object, a dialog box lets you define attribute values for
the objects.
Pin to Launch Adds the selected object to the default launch pad.
Pad
For information about using the Launch Pad application, see the
Rich Client Interface Guide.
Unpin from Removes the selected object from the default launch pad.
Launch Pad
For information about using the Launch Pad application, see the
Rich Client Interface Guide.
Resequence Resequences a structure.
Structure
Generate Creates item reports generated in the context of one or more
Report selected objects. Item reports generate in multiple output formats
and follow PLM XML standards allowing integration with
third-party reporting tools.
For more information, see Generate an item report on a Teamcenter
object.
Send To Selects an object in a navigation view; use the Send To shortcut
menu command to choose an application to open with the object
selected.
Note For example, you can send a structure to Structure
Manager from My Teamcenter. Teamcenter opens
Structure Manager, loads the structure, and then applies
the default revision rule.
• When an empty Structure Manager window is already
open, Teamcenter loads the structure into it, and then
applies the default revision rule.
Command Purpose
Check In/Out Reserves exclusive access to one or more objects and/or their
attachments by locking the objects in the database upon checkout.
You restore access to the objects using checkin. Only your
administrator is allowed to circumvent the security that these
menu commands provide.
For more information, see Overview of checkout and checkin.
Purge Permanently removes old versions of a dataset from the database.
You can select whether to purge all old versions or specific
versions of a dataset.
If sequence functionality is enabled and the latest sequence is
selected, the system removes all nonimmune sequences of an item
except for the latest sequence. If a sequence other than the latest
sequence is selected, only the selected sequence is purged.
Make Immune Specifies an item revision sequence cannot be deleted from the
system by a purge or checkin action.
The Make Immune command is not available for the latest
sequence. The system displays an error message dialog if you try
to make the latest sequence immune.
Remove Removes immunity from an item sequence. The item can then be
Immunity deleted from the system during a purge or checkin operation.
The Remove Immunity command is not available for the latest
sequence. The system displays an error message dialog if you try
to remove the latest sequence.
Refresh Reads information from the database and updates the information
displayed in the workspace area.
Edit Properties For selected, single editable objects, displays the Check-Out
dialog box, and then displays the Edit Properties dialog box for
the selected object.
For more information, see the Overview of object properties.
View Allows you to view the properties of a selected data object.
Properties For more information, see Overview of object properties.
Properties on Lets you edit and save properties on custom relations.
Relation
• When one secondary object is selected, this command displays
the Properties dialog box showing the relation between the
selected secondary object and the related primary object.
Command Purpose
Allows you to view, change, and/or apply access permissions for
Access a selected object.
For more information about access permissions, see the Access
Manager Guide.
Project Assigns or removes objects from projects.
For more information about projects, see the Project and Program
Guide.
License Lets users attach or detach licenses:
• Users with IP Admin privileges can use the Attach or Detach
commands to manage licenses for authorized data access
(ADA) for intellectual property (IP) data objects.
For information about associating licenses with data objects
for intellectual property security, see the relevant topics in
the Security Administration Guide.
Command Purpose
Multisite For data shared with participating sites in a distributed network,
Synchronization lets you update objects, components, and assemblies.
For more information about sharing data in a distributed
network, see the Multi-Site Collaboration Guide.
Subscribe Allows you to create subscriptions.
You can also access this menu command from a shortcut menu
by right-clicking a data object.
For more information, see Subscriptions overview.
Subscription Allows you to manage (query, edit, and delete) persistent
Manager subscriptions.
For more information, see Subscriptions overview.
Add To Lets you add selected objects to your Favorites list in the
Favorites navigation pane.
For more information about using favorites, see the Rich Client
Interface Guide.
Compare For comparing two requirements or comparing a requirement
Contents or specification to a previous versions, lets you start and end
comparisons, or compare to a previous object.
For more information about comparing requirement content, see
the Systems Engineering Guide.
My Teamcenter toolbar
Several buttons to access functionality are located on the My Teamcenter toolbar.
Button Purpose
This button is active when an application is loading or
Soft Abort when the system is processing data for a task. However,
the soft abort operation is a logical interrupt that can
be performed only when the system encounters an
interruption between two processes. The following
examples illustrate some situations in which you can use
the soft abort button:
• Creating a folder
When a folder is created, the system creates the folder,
pastes the folder, and opens the folder (if Open on
Create is selected). The only points in this process at
which the Soft Abort button can be used to stop the
process are between when the folder has been created
and is about to be pasted or when the folder has been
pasted and is about to be opened.
Button Purpose
• Deleting objects
When objects are deleted, the system loads the objects
and then deletes them. The only point in this process
at which the Soft Abort button can be used to stop the
process is between when the object is loaded and when
it is deleted, or if deleting multiple objects, the process
can be stopped between when the previous object has
been deleted and the next object is loaded.
• Running searches
When a query is run, the system executes the query
and then loads the objects. The only point at which
the operation can be stopped is after the query has
run but before the objects are loaded.
Cut Removes a selected data object reference and places it on
the clipboard. You must have read privileges on the object
and write privileges on its container (object folder, item
revision) to cut an object reference.
Duplicates an object reference. You must have read
Copy privileges for the object that you want to copy.
Tip You can create a copy of an object reference in a
different application by dragging the object from
My Teamcenter to the other application.
Pastes the contents of the clipboard into the selected
Paste container object.
Delete Deletes a selected data object.
Opens your Home folder in the My Teamcenter window.
Open Home folder
Open Worklist Opens My Worklist in My Teamcenter.
Refresh selected Refreshes the display in your rich client window.
object
Open selected object Opens a selected data object—folder, item, item revision,
or dataset—to access product information.
Display accessibility Allows you to select a user and view, change, or apply
access permissions for a selected object.
Button Purpose
Add Design to Launches the Add Design to Product wizard, which allows
you to select products and designs, identify architecture
Product elements, and select named variant expressions.
For more information, see the Platform Designer Guide.
Add Part to Product Launches the Add Part to Product wizard, which allows
you to select products and parts, identify architecture
elements, and select named variant expressions.
For more information, see the Platform Designer Guide.
Navigation Pane Display or hide the navigation pane.
For more information about working with the navigation
pane, see the Rich Client Interface Guide.
Open Search View Displays the Search pane used to execute database
queries.
For more information about search functionality, see the
Rich Client Interface Guide.
Open Simple Search Displays the Simple Search pane used to build business
View object searches based on one or more property values.
For more information about simple search functionality,
see the Rich Client Interface Guide.
Displays the Folders pane (also called the tree pane).
Folders
Back Let you navigate between loaded Teamcenter rich client
applications.
Forward
• Teamcenter mail lets you to send mail from within the Teamcenter interface,
including attachments and links, to other Teamcenter users. You can also send
e-mail from Teamcenter to recipients who are not Teamcenter users by specifying
a valid SMTP address.
Teamcenter mail is delivered to the Mailbox in your Home view in My
Teamcenter.
• Teamcenter rich client and thin client users can see when other users are
available for instant messaging with Microsoft Office Communicator. Teamcenter
users can view the current status of the owning and last modified users and
can click the Microsoft Office Communicator symbol in Teamcenter to initiate
communication.
For information about configuring Teamcenter mail and about configuring external
e-mail for subscription notification, see the Application Administration Guide.
2. Choose File→New→Envelope.
3. Use one of the following methods to enter the addresses in the To box:
• Type the addresses of the users, groups, address lists, or external recipients
in the To and/or CC boxes.
Note To send external mail, you must specify a valid SMTP address.
b. Type search criteria in the Search box to search by user ID, group, or
address list.
c. Click one of the following buttons to execute the search: User ,Groups
, or Address List .
d. Select the users, groups, or address lists that you want to receive the
message, and click the To or CC buttons.
Tip You can remove recipients from the lists by selecting the user
and clicking the Remove button (–). In addition, you can create a
new address list by clicking the Launch Address List button
and following the instructions described in Create an address list.
e. Click OK.
4. In the New Envelope dialog box, type the subject of the message in the Subject
box.
6. (Optional) Click the Add button to the right of the Attachments section to
copy items from the clipboard as attachments.
Note Attachments are Teamcenter objects and are only valid when sending
Teamcenter mail. Teamcenter objects cannot be sent as attachments
of external mail messages.
Address lists
Address lists can contain any combination of valid Teamcenter users and groups.
In addition, external e-mail addresses and other Teamcenter address lists can be
used as entries in address lists.
You can create address lists when selecting mail recipients by clicking the Launch
Address List Dialog button located beneath the search results pane in the Select
Recipients dialog box.
2. Type the name of the address list in the text box under the Address List pane,
and click the Add button .
3. Type the names of the members or select the members, users and/or groups, that
you want to add to the address list. The members that you add to the address
list display in the Member(s) pane.
• Type the name of the user or group and click the Add button.
• Perform the following steps to select members to add to the address list:
a. Place the cursor in the New Member box, and click the Organization
button .
c. Expand the tree, select the groups and/or users, and click OK.
The system displays the name of the user and/or group in the Member(s)
pane and the Organization Selection dialog box closes.
4. Click Close.
3. Type the names of the members or select the members, users and/or groups, that
you want to add to the address list. The members that you add to the address
list display in the Member(s) pane.
• Type the name of the user or group and click the Add button.
• Perform the following steps to select members to add to the address list:
a. Place the cursor in the New Member box, and click the Organization
button .
c. Expand the tree, select the groups and/or users, and click OK.
The system displays the name of the user and/or group in the Member(s)
pane and the Organization Selection dialog box closes.
4. Click Close.
5. To remove a user or group from the address list, select the member in the
Member(s) list and click the Remove button.
The system displays a confirmation message.
6. Click Yes to delete the selected member from the address list, click No to cancel
the delete operation, or click Close to cancel the operation and close the dialog
box.
2. In the Address List, select the name of the address list that you want to delete
and click the Remove button.
The system displays a confirmation message.
3. Click Yes to delete the selected address list, click No to cancel the delete
operation, or click Close to cancel the operation and close the dialog box.
Find and replace property values and add prefixes and suffixes . . . . . . . . . . . . 3-6
Find/Replace additional properties options . . . . . . . . . . . . . . . . . . . . . . . 3-6
o Click Cancel or press Alt+C to cancel changes and close the dialog box.
For object properties, the Properties dialog box can incorporate a Check-Out and
Edit button that lets you quickly check out an object and edit applicable information
in an Edit Properties dialog box.
You can then:
• Click Save and Check-In or press Alt+I to save changes, check in the object,
and close the dialog box.
• Click Save or press Alt+S to save the changes and retain the dialog box.
Note If you click Save or press Alt+S, and then click Cancel Check-Out or
press Alt+O, the changes are reverted and the checkout status for the
object is canceled.
• Click Cancel Check-Out or press Alt+O to cancel the checkout without saving
the changes and close the dialog box.
The system displays the properties of the selected object in the Edit Properties
dialog box. The properties that can be modified vary from object to object, and
you must have write access to make modifications.
Note You cannot change ownership of the selected object from the Properties
dialog box. You must use the Change Ownership option on the Edit
menu.
The Common Modifiable Properties dialog box displays only those modifiable
properties that are common to all of the selected objects.
4. Select the cells corresponding to the property values that you want to modify.
You can select a single cell, multiple cells in the same column, or all cells in a
column. To select all cells, click the column header.
Note The ID properties of multiple objects cannot be modified, because
duplicate object IDs are not permitted in Teamcenter.
5. In the Additional Options box at the top of the dialog box, enter or select
a new value.
• This area displays either a box or a list depending on whether the values
associated with the selected properties are strings or lists of values.
• When using the box to enter string values, you can click Cancel Changes
to revert to the last submitted value at any time prior to submitting the
changes.
7. (Optional) Use the Additional Options feature to find and replace values or add
prefixes and suffixes. For more information about this feature, see Find and
replace property values and add prefixes and suffixes.
Find and replace property values and add prefixes and suffixes
• When modifying string properties, you can click Additional Options to find
and replace a specific text string or add a prefix or suffix to a property value.
Note The system displays the Change Owner/Group dialog box when the
Additional Options feature is used to modify the Owner or Group ID
properties.
For more information about changing object ownership, see Managing object
protection.
Option Description
Replace With Specifies the text string that replaces the text designated in
the Find What box. The replacement takes place only when
the Replace or Replace All options are selected. Values
entered in this box are retained and displayed the next time
you open the dialog box.
Suffix Specifies a suffix to be added to the values of the selected
properties. Values entered in this box are retained and
displayed the next time you open the dialog box.
Pattern Specifies that the characters in the Find What box will be
considered as a pattern to be matched during the search.
Entire Word Specifies that all of the characters in the Find What box must
be present to be considered as a match in the search.
Case Sensitive Specifies that the case of the characters in the Find What box
must be matched during the search.
Clear button Clears the contents of the dialog box.
Replace • Adds the string in the Prefix box to the values of the
selected properties in the table.
• Click Check-Out and Edit or press Alt+E to check out the objects.
• Click Cancel or press Alt+C to cancel changes and close the dialog box.
Note The Properties dialog box for a dataset may display read-only boxes for
relationships such as UG Expressions, UG WAVE Geometry, and various
others. These boxes, which are normally blank, are used to display
relationship information stored in the database.
• Click Check-Out and Edit or press Alt+E to check out the objects.
• Click Cancel or press Alt+C to cancel changes and close the dialog box.
2. Drag the column to the desired position in the table and release the mouse
button.
The column appears in the new position.
3. Select the primary property to be sorted on from the list in the Sort By section.
Select Ascending or Descending to designate how to sort the property values.
5. Click OK to sort the property values in the table display or click Cancel to close
the Sort dialog box without sorting the property values.
1. Right-click a column header in the table pane and choose Insert column(s).
The Change Columns dialog box appears.
2. Double-click a category and select the object type for the properties you want to
display.
Note Display only the properties that you view or change frequently. The
more properties that are displayed, the longer it takes to expand folders
and items.
3. Select the property you want to add to the table pane display from the Available
Columns list and click the Add the selected columns from Available Columns
to Displayed Columns button .
The selected property appears in the Displayed Columns list.
Tip You can also double-click the property in the Available Columns list to
add it to the Displayed Columns list.
4. Repeat step 3 for all property columns you want to add to the table pane display.
5. Click Apply to insert the columns into the current table pane display.
Note You can use the Save Column Configuration command on the Table
Function Menu to save the current table pane display, including the
columns you inserted.
You can use the Apply a Column Configuration command on the Table
Function Menu to apply a saved configuration to the table pane display,
or modify a saved configuration.
6. (Optional) Click Save to save the properties you added to the Displayed
Columns list.
2. Click Yes to remove the column from the table pane display.
c. To check out objects while exporting to live Excel, select Check out
objects before export.
Note The check out applies to all objects being exported. You should
use this option carefully if you are exporting a large set of objects
or perhaps an entire specification.
d. Under Output Template, select a template from the Use Excel Template
list.
• To open a file:
o In the box, enter the new value, and then press the Enter key.
For a date or numeric property, the value must match the valid
format for the property.
For a text property, any keyboard characters are valid, except that
the Name property value cannot contain double quotation marks.
You can also select the cell and enter the new value directly.
Note If you create an Excel formula, you can automatically update values
in all dependent cells when you change the value in a precedent cell.
For more information, see Microsoft Excel Help.
b. Select the destination cell, and then choose Excel’s Edit→Paste menu
command.
Note If you cut the value and paste it into a different row, the value
remains with the source object in the database. Therefore, the
value is not moved in the Teamcenter client.
• To hide or show rows, click the button in the heading of a property column,
and then select a filtering criterion from the popup list.
• If you click No, the file remains on your computer as a temporary file.
• If you click Yes, Excel displays the Save As dialog box, in which you assign
the file name, file type, and location. The file remains interactive with Excel
Live after you exit.
For more information about working in live Excel files, see the Extensions for
Microsoft Office Guide.
For more information about editing object properties in live Word, see Editing
object properties.
With the default object template applied, the output Word document contains the
following Teamcenter property values for each requirement and paragraph object:
• The Name property value is the object name.
o This value is formatted in a Word heading style with a numbered outline
level.
o The heading occupies a nested content control at the top of the main content
control for the object.
o If you edit the heading, the Requirements pane displays a red asterisk (*) to
the right of the object.
The asterisk indicates that changes are pending for the object.
• The Body Text property value is the rich text content of the requirement or
paragraph object.
Note If you are working in a live Word export file, it may include a URL link
to body text. In this case, click the link to access and review or edit the
requirement content.
o Each Word paragraph occupies a nested content control within the main
content control for the object.
o If you place the cursor within the nested content control, the Requirements
pane displays a red asterisk (*) to the right of the object.
The asterisk indicates that changes are pending for the object. However, the
asterisk appears whether or not you edit the Body Text property value.
Note Word content controls do not support multiple selection of LOV values
that are defined in arrays. Only one value can be selected per array.
You can change, copy, move, or delete a value by placing the cursor inside the related
content control and using Word editing features.
• Any updates you make and save to the requirements content in live Word are
reflected in Teamcenter.
• Edits are not applied to the corresponding objects until you commit the changes
to Teamcenter. You can cancel the edits by closing the document without saving
it.
For more information about committing changes to Teamcenter, see the Client
for Microsoft Office Guide.
Caution • Edits made outside of a content control are not applied to objects in
Teamcenter. Such edits become static content in the document.
Relation properties
Objects are associated by relations.
For example, datasets (secondary objects) are associated with item revisions
(primary objects) using relation objects. The meaning of the secondary object may
vary from one context to another. Properties on relations enable you to record
information specific to the association or context in which the object is used.
Your administrator can create custom attributes (properties) to apply to relation
business objects in the system.
A single item can be associated to multiple items or contexts. Objects are associated
by relations, and the meaning of the relation may vary from one context to another.
For information about creating relation business objects and adding properties to
relations, see the Business Modeler IDE Guide.
2. Select the secondary object items that you want to paste on the primary object
item and choose Edit→Copy.
3. Select the primary object item with which you want to associate the secondary
business object and choose Edit→Paste special.
The Paste dialog box appears, displaying a list of relations.
4. Select the relation that you want to use to associate the primary and secondary
business objects.
5. Click OK.
6. If there are any visible attributes defined on the relation, the Enter the Values for
Properties on Relation dialog box appears. Enter the values for the attributes.
Note If you click the Apply All button, the values provided for the first relation
are set for the other relations if you selected multiple secondary object
items. Click Next to enter different values for the other relations.
7. Click Finish.
Note The Finish button is available only when values have been provided for
all mandatory attributes.
The secondary business object is pasted on the primary business object through the
selected paste relation business object.
Note You can either choose Edit→Paste or drag the secondary business objects to
the primary business object to associate the secondary and primary business
objects through the default paste relation of the primary business object.
You can perform the same actions in the My Navigator, CM Viewer, and
Details panes of the Structure Manager.
4. Click OK or Apply.
3. Select the cells corresponding to the property values that you want to modify.
You can select a single cell, multiple cells in the same column, or all cells in a
column. To select all cells, click the column header.
When using the box to enter string values, you can click Cancel Changes to
revert to the last submitted value at any time prior to submitting the changes.
Delete a relation
1. Open My Teamcenter.
2. Select the secondary object that has a relation with a primary business object.
3. Right-click the secondary object and choose Cut, choose Edit→Cut or click to
cut the relation between the primary and secondary objects.
2. Remove any existing information from the Query Builder boxes by clicking the
Clear button.
3. In the Name box, type the name of the query. The name of the query must be
unique.
5. From the Modifiable Query Types list, select Local Query as the query type.
6. Click Search Class to select the target class for the query.
The Class Selection dialog box appears.
7. Specify the desired search class by selecting an entry from the Class Selection
dialog box. For example, select Item.
10. Click the Search Class button to select the referencing class for the
query.
11. Type the name of the relation business object and click or scroll through the
tree structure and select the relation business object. Relation business objects
appear as a subclass of ImanRelation. Close the dialog box after selection.
The POM schema in tree format appears in the Class Attribute Selection dialog
box.
12. In the Class Attribute Selection dialog box, select the referencing object. For
example, select primary_object by double-clicking the node.
Note You can also select the secondary object as the referencing object.
13. The referencing object, in this case, primary_object, and class, Newrelation,
appear in the Attribute Selection area.
14. Select the attributes of the referencing object on which you want to build query
clauses.
The attribute appears in the Search Criteria table.
Note The display name of the attribute is
Relation_business_object¬referencing_object¬attribute_name, for
example, Newrelation¬ ¬primary_object¬ ¬Attribute1. The ← symbol
indicates a reversed-reference relationship.
15. In the Attribute Selection section, select the other referencing object. In this
case, select secondary_object in the Attribute Selection section.
The Class Selection dialog box appears.
Note If you selected primary object in step 12, select the secondary object in
this step. If you selected secondary object in step 12, select the primary
object in this step.
16. Select the class and click OK. For example, select Item.
17. To include other attributes of a relation, select the attributes in the Attribute
Selection section.
The attribute appears in the Search Criteria table.
1. Open My Teamcenter.
2. Locate the quick search input field, execute button, and menu
4. Click the Select a Search button on the Search view toolbar and choose More.
5. In the Change Search dialog box, expand the System Defined Searches folder.
6. Select the appropriate properties on the relation query and click OK.
The Search pane displays the search attributes associated with the relation
query.
• For more information about creating business object display rules, see
the Business Modeler IDE Guide.
You can classify data to restrict object access based on intellectual property and
international distribution requirements.
For information about using classification functionality, see the Classification Guide.
Teamcenter provides mechanisms for rules-based and object-based protection, and
for authorized data access (ADA) for intellectual property (IP) and international
traffic in arms regulation (ITAR).
For more information about functionality for ADA and ITAR support, see the
Security Administration Guide.
Rules-based protection
Rules provide security for your Teamcenter data by:
• Controlling access to data on a global basis.
• Granting privileges to the data according to the users’ IDs and their session
context (the group and role they used to log on).
Note Rules do not control the creation of objects. They only determine what
operations can be performed on existing objects.
The condition and value identify the set of objects to which the rule applies; the ACL
defines the privileges granted to users (accessors).
User actions against objects cause the rule tree to be evaluated to dynamically build
an access control list for the object. The ACL controls permissions for the object and
determines who (accessors) can do what (actions) to the object.
Object-based protection
Object-based protection uses access control lists (ACLs) to create exceptions to
rules-based protection on an object-by-object basis.
Object ACLs are most useful when you need to:
• Grant wider access to a specific object.
Accessors
Controlling access to every object in the database on a user-by-user basis is
impractical. Therefore, Teamcenter uses the concept of accessors to grant or deny
privileges to clusters of users who share certain common traits (for example, they
perform the same function or work on the same project).
• Privileges define the actions an accessor is allowed to perform on a particular
object.
• You work with access control lists (ACLs) to view, modify, add, or delete privileges
on an object.
• You can grant or deny various types of access privileges on an object you own
if you have the proper permissions on that object.
Accessor precedence
It is important to understand that certain accessors take precedence over other
accessors. Generally, the more restrictive the accessor, the higher precedence it has
over other accessors. For example, world is the least restrictive of all accessors
but has the lowest precedence; owner is the most restrictive of all accessors but
has the highest precedence. If there is ever a conflict between these two accessors,
Teamcenter enforces privileges granted or denied to the owner before those granted
or denied to the world. The following figure shows accessors in order of precedence.
Site ownership
All the previous information concerning accessors, accessor precedence, and
privileges applies to information and users sharing the same Teamcenter database.
However, your enterprise may have several databases or sites operating at several
different facilities. To share product information across multiple sites, one site must
be designated as the owner of each object. This is referred to as site ownership.
Site ownership is important if you want to transfer ownership of an object from
your site to another Teamcenter site when objects are exported. Site ownership
determines which site can modify an object after it has been exported.
1. In My Teamcenter, select the object affected by the access rule and choose
View→Access.
Tip You can also right-click the object and choose Access from the shortcut
menu or you can click on the toolbar.
The Access dialog box appears, showing the privileges that the logged-on user
has to the selected object.
2. To view privileges assigned to your other roles and groups, select the role or
group from the lists in the Access dialog box.
The system updates the Access table to reflect the privileges of the selected
group and role.
3. To view the privileges of a different user, select the user, group, and role from the
lists in the Access dialog box.
The system updates the Access table to reflect the privileges of the selected
user, group and role.
For information about verifying the effect of access privileges, see the Access
Manager Guide.
2. To view the privileges of a different user, select the user, group, and role from the
lists in the Access dialog box.
The Access dialog box shows the user smith has Read and Write privileges but
does not have Delete privileges to the 000017/A item.
1. Select an object in a tree pane or component view and click Access on the
toolbar or right-click the object and choose Access.
The system displays the Access dialog box, showing the access properties
assigned to the owner of the object.
Note Master forms inherit access privileges from the parent item or item
revision. Therefore, changing access privileges to an item or item
revision affects the privileges on the master form.
2. Click Get access control list. in the lower-right corner of the Access dialog
box to display the ACL Control List dialog box.
b. Choose the accessor type that you want to add to the list.
5. Double-click the blank box in the ID of Accessor column to access the list of
predefined accessor IDs, and choose an ID from the list.
1. Select an object in the tree or component view, and click the Access button
on the toolbar or right-click the object and choose Access.
The system displays the Access dialog box.
Note Master forms inherit access privileges from the parent item or item
revision. Therefore, changing access privileges to an item or item
revision affects the privileges on the master form.
2. Click the Get access control list. button in the lower-right corner of the
Access dialog box.
The system displays the ACL Control List dialog box.
3. In the ACL Control List dialog box, choose the entry that you want to modify.
Note You can only change entries you have created or entries you have been
given permission to change by the Teamcenter administrator.
4. Grant or deny privileges for the type of accessor by double-clicking in the column
corresponding to the privilege you want to modify.
2. Click Get access control list. in the lower-right corner of the Access dialog
box to display the ACL Control List dialog box.
3. Select the row with the access control entry (ACE) that you want to delete
from the list and click the Remove selected access control entry from ACL.
button.
The object line is deleted from the Access Control List.
Repeat this step until you have deleted the ACEs that you want to remove.
4. Click OK.
5. Select the cells in the Owner column that correspond to the objects for which you
want to change ownership. You can select a single cell, multiple cells, or all cells
in the column. To select all cells, click the column header.
7. Select the user in the tree to whom you want to grant ownership of the selected
objects. The following features in the Change Owner/Group dialog box can be
used to locate a user:
Organization Tree Displays the groups, roles, and users comprising your
site’s organization. When the search feature is used, the
results are displayed in this tree.
Find Groups Initiates a search for groups in the organization based
on text entered in the box to the left of the button.
Find Roles Initiates a search for roles in the organization based on
text entered in the box to the left of the button.
Find Users Initiates a search for users in the organization based on
text entered in the box to the left of the button.
Reload Restores the organization tree to its original state.
Organization Tree
The Owner box in the table is updated with the new user; however, the change is
not yet updated in the database.
8. Click Apply to update the owner column in the Common modifiable properties
dialog box and retain the dialog, or click OK to update the owner column and
exit the dialog box.
• Click Save to commit the changes to the database and keep the objects
checked out.
3. To change ownership of only the object displayed in the dialog box (no
attachments or components), go to step 5.
5. Select the new owner of the objects by clicking New Owning User.
The Organization Selection dialog box displays your site’s organization tree.
6. Traverse the tree to locate and select the user who will be assigned ownership
of the objects, and click OK.
The Organization Selection window closes and the system displays the name
of the user that you selected on the New Owning User button in the Change
Ownership dialog box.
7. Save the information in the database or cancel the change ownership operation.
• Click OK to assign ownership to the new user and close the dialog box.
The symbol in the right margin of the dialog box (across from the
selected object) indicates that the change ownership process was successfully
completed. If an error occurs during the ownership change process, the error
icon is displayed for that object. You can double-click the icon to display
details about the error.
• Click Cancel to close the dialog box without changing ownership of the
objects.
Defining attached data for item revisions created from item revisions . . . . . . . 5-15
Rules for copying related objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
• Item revisions are data objects used to manage changes (revisions) to items.
The Item type is the parent type for many objects, including document, part, and
design types.
• A document in Teamcenter represents all revisions of a real-world document.
This item type supports documentation for products, processes, standards, and
other aspects of a business, typically from applications such as Microsoft Word,
Microsoft Excel, and so on.
For more information, see Document management basics.
• A part is a business object in the product structure. Each part may have one or
more CAD designs associated with it. The part is managed by the company’s
part releasing system; it is typically revised and releases separately from the
associated design. A part may have one or more business owners.
• A design is a CAD design solution that implements a business part. Each part
may be implemented by one or more CAD designs. Likewise, a CAD design may
implement more than one part. Certain parts do not require a design solution,
for example, paint and glue. A design may have one or more business owners.
Note Anyone who manages parts and designs separately must align the
CAD designs and the BOM at appropriate times, using the techniques
described in Aligning CAD designs and parts.
Items can contain other data objects including other items and folders. You can
group and organize product information for each product, part, or component. An
item always contains the same data objects, regardless of which user’s workspace
displays the item.
Note Some applications provide specific items. For example, the Teamcenter
simulation process management applications use CAEModel items,
CAEGeometry items, and others. For information about application-specific
items, see the relevant application documentation.
For information about Teamcenter simulation process management
applications, see the Simulation Process Management Guide.
Item
Item Master (Form)
ItemRevision
ItemRevision Master (Form)
• Item
Collects data that is globally applicable to all revisions of the item.
• ItemRevision
Collects data that is applicable to a single revision of the item.
Note The item types displayed in this dialog box are controlled by your
administrator. You may be unable to create item types that are visible
to you in your workspace.
At this point, you have provided all of the information necessary to define the
item.
7. Click Next to move to the next step and further define the item, or click Finish to
create the item immediately.
9. Click Finish.
Note The item is not created until you click Finish.
Note To create an alternate or alias identifier for the new item, select the item
and choose File®New®ID to display the New ID dialog box.
If an administrator specifies Item, Folder, or Form as values for the
TC_Enable_legacy_create preference, the legacy dialog boxes for creating
those objects are displayed. The legacy dialog boxes for creating Item,
Folder, or Form objects let you specify identifiers during creation of the
objects.
Business objects
Business objects are the fundamental objects that model business data.
Tip Business objects were formerly known as types in Engineering Process
Management.
You can create an instance of any business object in the rich client by using the
File→New→Other menu.
All available business objects are listed in this menu, including custom business
objects created using the Business Modeler IDE.
For information about working with business objects, see the Business Modeler
IDE Guide.
4. Click Next.
5. Provide required information and click Next to populate any other associated
fields as needed.
6. Click Finish to create the new business object, or click Cancel to exit without
creating the new business object.
For example, when you add a new item revision to an item, the new item revision is
automatically defined as a revision relation.
The automatically defined relation types are:
• Revision
• Alternate ID
• TC_validation
If validation process is enabled at your site, this relation is established between
the item revision and the validation_master form.
• IMAN_Drawing
Specifies the relationship between an NX part and a drawing dataset.
Note Your site may be configured to automatically create relation types other
than those listed here.
Note Some relations may not display in the My Teamcenter Impact Analysis
view or the Relation Browser application views unless the relationship is
added to a preference.
For more information about the Relation Browser application perspective,
see the Relation Browser Guide.
order is applied to each rule condition, rather than to the entire rule. Ascending and
descending ordering can also be applied when all revisions are displayed.
Item revisions that do not match the filtering criteria are stored in the More folder
under the item.
Note Click the More folder to display the list of item revisions. You can select
an item revision from the list and the system opens it in a separate tab in
the My Teamcenter window.
8. Select an option from the Rule list, either Working, In-Process, Release Status,
or Configured by.
Tip To access the Rule list, double-click the box in the Rule column for the
applicable row.
10. (Optional) Enter an integer in the Limit box, representing the number of
matching item revisions to display.
Note An integer greater than one is not valid for some rules and conditions. In
that case, you cannot change the value in the Limit box.
11. (Optional) Use the up-arrow and down-arrow buttons to set the precedence of
the display rules in the table.
12. Click OK to create the display rule and exit the dialog box or click Apply to
create the display rule and retain the dialog box.
Revision Status
000509/A Release status: Pending
000509/B Release status: Pending
000509/C Release status: Pending
000509/D Release status: Released
000509/E Release status: Released
000509/F In-Process
000509/G Working
000509/H Working
Without applying display rules, all of these revisions appear under the item in the
My Teamcenter tree display.
The image shows the rules used to display (in ascending order) only the latest
released item revision with status equal to Pending, all item revisions with status
equal to Released, and the latest Working revision in the My Teamcenter tree
for the Item item type.
Revision Status
000509/C Release status: Pending
000509/D Release status: Released
000509/E Release status: Released
000509/H Working
The remaining revisions shown in Display rules example with equal to status are
placed in the More folder under item 000509.
When the rules in the Display rules example with not equal to status image are
applied, the system displays the revisions shown in the following table.
Revision Status
000509/E Release status: Released
000509/D Release status: Released
000509/H Working
000509/G Working
The remaining revisions shown in Display rules example with not equal to status are
placed in the More folder under item 000509.
3. In the Options dialog box, click Search and use the Search on Keywords box to
find the site preference for which you want to create a user or group preference,
for example, TC_QRY_Item Revision – Latest Working_REVRULE.
Note To remove the revision rule, you can specify None as the preference
value.
4. Click New.
5. Use the same name as the site preference and select the scope, and provide the
desired revision rule.
6. Click Create.
There are now two preferences for the saved query, one governing the site and
another for the selected scope applicable to the group or user that created the new
preference.
The tri-pane window displays the Item tree (upper-left) and Item Revision tree
(lower-left), as well as the standard panes and views (right).
• When you open an item, the item and all its related item revisions are displayed
in the Item tree, and the latest item revision is displayed in the Item Revision
tree.
• When you open an item revision, the associated item and all related item
revisions are displayed in the Item tree, and the item revision that you opened is
displayed in the Item Revision tree.
2. Choose File→Open.
The selected object appears in the tri-pane window.
2. Choose File→Open.
3. Select the item or an item revision from the tree in the upper-left or lower-left
pane in the tri-pane window.
4. Click Revision selection on the toolbar between the upper and lower panes.
5. Select the filter to be applied to the display list using the Released, In-Process,
or Working buttons, or select a revision rule from the Revision Rule list.
The item revisions matching the filtering criteria are displayed in the dialog box,
arranged from latest to earliest revision.
6. Select an object in the Revision selection list to display it in the Item Revision
pane.
For more information about revision rules, see Getting Started with Product
Structure.
Defining attached data for item revisions created from item revisions
When you create item revisions using the Save As and Revise menu commands,
you can copy objects related to the original item revision forward to the new item
revision, as follows:
• You can selectively copy the objects, regardless of relation type.
• You can copy the object references from one item or item revision to another.
• You can copy objects from one item or item revision to another as new objects
rather than as references to objects.
Objects that can be copied as new objects include:
o Datasets
o Forms
o Folders
o Item revisions
• Deep copy rules determine which related objects are copied when a specific
item revision type is used as the basis for a new revision. If these rules are
implemented at your site, it is possible that you cannot select or deselect objects
to be copied forward, depending on how the rules are implemented.
• Your administrator can also implement rules to copy secondary datasets to a new
revision when the primary dataset is copied forward.
Note Secondary datasets are those related to a particular dataset type by a
specific relation type.
2. Click the Define Attached Data link in the left pane of the Revise dialog box.
The system displays the Define Attached Data form in the right pane of the
dialog box.
• The left side of the form displays the Source tree containing the objects
related to the selected item revision.
Note The symbols to the right of the objects indicate the default copy
option for that object. The default copy options are derived from site
rules and may be overridden depending on site implementation.
• The right side of the pane displays the Destination tree containing the
resulting item revision with the objects copied according to the default
copy option.
3. (Optional) To override the copy option for an object, click the button to the right
of the object and select a different copy option from the Copy Options menu.
Tip If the button is disabled, you do not have permission to change the copy
option for that object.
Copy as Object Creates a new object of the same type and relation to the
parent object. Objects created by this method are totally
independent of the parent object. Therefore, any changes to
the copied object are not reflected in the original object.
Copied objects appear in bold in the Destination tree and can
be renamed.
Copy as Copies the object as a reference to the original object. All
Reference changes to the reference copy affect the original object.
The names of attachments that are copied as references cannot
be modified.
Don’t Copy Allows you to selectively copy objects from one revision to
another. Objects that are designated as Don’t Copy appear
with a line through them in the Destination tree.
Relate to Latest Allows you to relate the selected object to the latest item
revision with an Is Represented By relation.
Revise and Allows you to revise the selected object and relate the
Relate to Latest new object revision to the latest item revision with an Is
Represented By relation.
Note If the Relate to Latest or Revise and Relate to Latest option is enabled,
it is a required action. These options are only available if you are
revising an object, not when you are performing a Save As action.
The actions performed when you select these options are configured by
your administrator using the Business Modeler IDE. For example, they
may allow you to relate a part object to the latest item revision of the
corresponding design, or to revise the part object and relate it to the
latest item revision of the design.
5. Click Next to assign the revision to a project or click Finish to create the new
item or item revision.
Note For more information about copy options for related objects, see Defining
attached data for item revisions created from item revisions.
The Save As menu command creates new items from existing items or item revisions.
The copy options for the objects related to the item revision differ depending on
whether an item or item revision is selected as the basis for the new item.
• When you use an item as the basis, most of the objects related to the selected
item revision are copied as references. The exceptions are the item revision
master and BOM view revision. These are copied as new objects.
Caution If your administrator has set a deep copy rule for a specific item
revision type, you must select the item revision (rather than the
item) when using the Save As command.
• When you use an item revision as the basis, you have the option to copy the
related objects as references, as new objects, or not to copy the selected objects.
Note If your administrator has set a deep copy rule for an item revision type,
that rule does not affect associated classification objects in the legacy
Save As dialog box. For revising, copying, or with the Save As menu
command, the behavior for classification objects is controlled by the
ICS_ico_action_after_saveas preference setting.
1. Select an item in the tree or Details table to be the basis of the new item.
3. Click Assign to automatically generate the next available item ID and revision,
or manually enter an item and revision ID.
Note The Assign button is available only if naming rules and automatic
generation have been implemented for the selected object type.
5. (Optional) Click Next to display the Define Attached Objects page, which lets
you define how attached objects are copied and related to the new item revision.
For each attached object, click the Copy Option value and select the appropriate
option from the list.
Note The objects related to the selected item revision, with the exception of
the item revision master and BOM view revision objects, are copied to
the new item revision as references.
6. (Optional) Click Next to display the Related Objects information page, where
you can provide information such as project identifiers, user data, and serial
numbers.
1. Select an item revision in the tree or Details table to be the basis of the new
item and item revision.
7. (Optional) Click Next to display the Define Attached Objects page, which lets
you define how attached objects are copied and related to the new item revision.
For each attached object, click the Copy Option value, such as Reference Copy
or Object Copy, and then select the appropriate option from the list.
Note The objects related to the selected item revision, with the exception of
the item revision master and BOM view revision objects, are copied to
the new item revision as references.
Note To create additional identifiers and specify display options for the newly
created item revision, select it and choose File®New®ID.
If an administrator specifies true as a value for the
TC_Enable_LegacySaveAs preference, the legacy dialog boxes
for creating objects are displayed. The legacy dialog boxes let you specify
identifiers during creation of the objects.
Mandatory steps required to create a new item revision are indicated by a red
asterisk. Once the mandatory steps are performed, the new revision is created. You
can then continue through the remaining steps in order, select individual steps from
the list, or exit the wizard. It is not necessary to work through the steps sequentially,
nor is it necessary to complete all of the steps.
Steps in the Revise dialog box:
Mandatory steps required to create a new revision are indicated by a red triangle.
Once the mandatory steps are performed, you can continue through the remaining
steps in order, select individual steps from the list, or exit the wizard.
• You do not have to work through the steps sequentially, nor is it necessary to
complete all of the steps.
• If mandatory item revision master attributes are defined for the item business
object, values must be entered before the system can create the item.
Note The Name and Description boxes may contain an initial value determined by
property rules implemented at your site. You can replace this value, but you
cannot specify a null value by clearing the box. If you clear the box, the initial
value is reapplied to the property when you save the new item revision.
The Revision_Name_Based_On_ItemRevision site preference specifies
whether revision names displayed in the rich client Revise dialog box are
based on item revision names or item names. The default behavior creates
revision names based on item revision names.
2. Choose File®Revise.
The system displays the Revise dialog box.
At this point, you have provided all of the information necessary to create the
item revision.
5. Click Next to move to the next step and further define the item revision or click
Finish to create the item revision immediately.
Tip The item revision is not created until you click Finish. If mandatory item
revision master attributes are defined for the item type, you must click
Next and enter attribute information before you can click Finish.
• Define the open, display, and checkout options for a new object
1. Click the Enter Additional Item Information or Enter Additional Item Revision
Information link in the left pane of the dialog box.
Note If the Enter Additional Item Information or Enter Additional Item
Revision Information links are unavailable, these forms are disabled for
the business object.
The system displays the input boxes in the right pane of the dialog box.
Mandatory attributes are indicated by a red asterisk in the upper-right corner of
the box.
3. Click Next to continue to the next step or click Finish to create the item or item
revision immediately.
4. Enter an item ID, revision, and name for the alternate ID, or click Assign to
automatically generate the item ID and revision identifiers.
Tip It may be necessary to resize the dialog box to view the Assign button.
Note The Assign button is available only if naming rules and automatic
generation have been implemented for the selected object type.
5. Click Next to move to the next step and further define the item or click Finish to
create the item or item revision immediately.
For more information about alternate identifiers, see Overview of alternate and
alias identifiers.
3. To further define the item, click Next or click Finish to create the new item
or item revision.
Note This feature is available only if attributes have been defined for the selected
alternate ID type.
1. Click the Assign to Projects link in the left pane of the dialog box.
The system displays the list of projects to which items can be assigned.
2. Select one or more projects from the Projects for Selection list.
3. Click the right-arrow button to move the projects to the Selected Projects list.
4. Click Next to move to the next step and further define the item, or click Finish to
create the item or item revision immediately.
Tip Once an object is created, you can add it to other projects using the
Tools→Project→Assign menu command.
Note You can assign objects to projects only if you are a privileged project team
member.
The Owning Project box, which is read-only, displays your current project.
This becomes the owning project for the item. To set your current project,
choose Edit→User Settings and select a project from the Project list.
For more information about project team members, see Project
administrators and team members.
For more information about owning project functionality, see Creating
associations using Owning Project functionality.
Define the open, display, and checkout options for a new object
1. Click the Define Options link in the left pane of the dialog box.
The system displays the open, display, and checkout options.
2. Select Show as new root to open the item in a component view when it is created.
3. If you created an alternate identifier for the item, you can use the alternate
identifier as the default display object. Select Use item identifier as default
display and Use revision identifier as default display to set the alternate
identifier as the default display object.
4. Select Check Out Item Revision on Create to put a checkout lock on the
associated item revision when the item is created.
Tip To remove the checkout lock from the item revision after the item is
created, select the item revision object and choose Tools→CheckInOut.
You can either check in the item revision or cancel the checkout.
You can use the Save As menu command to create a copy of an item revision and
its component objects (as defined using deep copy rules), but baselines provide the
advantage of capturing product data without stopping work or creating a new,
unnecessary, revision of the item. Additionally, baselines can capture an entire
assembly structure.
Baselines of configured product structures must be created using Structure Manager.
For more information, see Getting Started with Product Structure.
Baselines are related to the item revision from which they were created using an
IMAN_baseline relationship. The component objects and attachments are related
to the baseline via standard object relationships, such as IMAN_specification and
IMAN_requirement.
2. Choose Tools→Baseline.
The Baseline dialog box appears.
• The baseline revision ID and job name for the new baseline are generated
automatically, according to rules defined for your site, and cannot be
modified.
• The description matches that of the base item revision and can be modified.
4. Select the release process to be applied to the baseline from the Baseline
Template list.
Release processes, which vary from site to site depending on business rules, are
used to associate a release status with the baseline.
For more information about baseline process templates, see the Workflow
Designer Guide.
You can enter an alphanumeric string that represents the baseline label.
Teamcenter uses the label you enter as the name of the baseline folder.
Note This box is only displayed if your site uses baseline labels.
• Select Dry Run Creation and click Apply to validate the baseline before
it is created.
The system displays a report of the proposed baseline structure that can be
printed using standard Teamcenter print features.
Hide baselines
1. Choose Edit→Options.
The Options dialog box appears.
2. Select Item.
For example, when the released status on baseline item revisions is Pending,
you display the latest baseline revisions by setting the rule, Released Status,
equal to the condition, Pending, and set the limit to the maximum number of
baselines you want to display.
For more information about how to set an item revision display rule, see Set
an item revision display rule.
8. Click OK.
The hierarchy tree pane displays the latest baselines up to the limit set.
4. In the applicable boxes, type a new name, revision, or description for the checked
out object.
5. Click Save to save the changes and retain the dialog box. Or, click Check In to
save the changes and close the dialog box. Or, click Cancel Check-Out to cancel
the checkout without saving the changes and close the dialog box.
Note If you click Save, then Cancel Check-Out, the changes are reverted and
the checkout status for the object is cancelled.
If you click Save, this does not check in the object. You must click
Check-In to complete the change.
• Items and item revisions can also be deleted individually, along with their
related components such as forms and datasets.
Delete an item
1. Select the item in the tree and click Delete on the toolbar or choose Edit→Delete.
The system displays a confirmation message in the Delete dialog box.
3. (Optional) Click the Delete item and all child items below it button to delete
the item and all components in the item structure.
For information about how to delete an item and all child items below it, see
Delete an item and all of its child components.
4. Click Yes to delete the item and related revisions and components, or click No to
cancel the delete operation.
• When the check box is selected, all sequences of the item revision are deleted
by the delete operation.
4. Click Yes to delete the item revision, sequences, and related components or
click No to cancel the delete operation.
3. In the Explore dialog box, select the related objects, using one of the following
methods:
• By individual selection
a. Double-click the top-level object to expand the tree and view the object
components.
c. Click Update the selection in the tree based on rules to update the
selections in the tree.
Note Rules can be removed from the table by selecting the row and
clicking Remove selected rules.
4. Click OK to accept the related objects and return to the original operation.
5. Click Yes to delete the item and selected components or click No to cancel the
delete operation.
• Neither the item nor any of its revisions can be checked out.
2. In the Delete dialog box, click Delete item and all child items below it .
The system builds a representation of the structure and analyzes the components
to determine if they are candidates for deletion.
Note This process can take a significant amount of time depending on the size
of the structure. You can stop the process by clicking Abort.
When the process is complete, the Delete Below dialog box appears.
• The tree in the left pane displays the item/item revision structure and
related components. Items and item revisions are preselected for deletion.
The right pane of the dialog box lists type and relation combinations that
can be used to select components, as defined by your preference settings.
Both the Type and Relation lists include the Any option, which allows you to
select all instances of a specific object type, regardless of relation, or to select
all instances of a specific relation, regardless of object type.
Apply rule filters, as follows:
c. Click Update the selection in the tree based on rules to update the
selections in the tree.
Note Rules can be removed from the table by selecting the row and
clicking Remove selected rules.
4. Click Yes to delete the item and selected components or click No to cancel the
delete operation.
3. For more information about the types of operations you can perform, see the
Change Manager Guide.
4. In the appropriate boxes of the Mass Update wizard, search for the parts to be
included in the mass update.
• Target
The part on which to base the change. The target part is used to identify the
assemblies that are impacted by the mass update.
• Replacement/Add
The part to be replaced or added to the target part, depending on the
operation selected for the mass update. Defining a replacement part is not
required if you are removing a part or performing a manual update.
• Change object
The change object in which to store the parts, the requested updates, and the
results of the mass updates.
Note o The boxes that appear depend on the operation you selected.
5. Beneath each part, click Add to Newstuff folder to store the results of the
update in the Newstuff folder.
Note Select the Add to Newstuff folder to ensure you have an update history.
You can use Audit Manager to view who performed the operation.
6. Click Next.
7. In the Select column of the Select the impacted Parts to update dialog
box, select the impacted assemblies you want to update. You can only select
assemblies to which you have write permission.
There are many reasons why you cannot edit an assembly, including
not having write access to it, the assembly does not belong to you, or
the mass update operation does not perform that type of replacement
or substitution (for example, the part already has an alternate
substitute or it is the preferred substitute).
Review the operations for any limitations on substitutes.
• To remove all table keyword filters in the Where Target is used text
box, click Erase.
• To select all assemblies, click Select All and, to clear the selection of
all assemblies, click Deselect All.
8. Click Next.
The Review the Mass Update and Execute, Save or Cancel page appears.
If you selected to store the results in the Newstuff folder, the mass updates appear
as shown in the figure.
For more information about the folders, see the Change Manager Guide.
• The Dataset object represents an actual data file on the operating system or
in Teamcenter. Datasets are typically authored content of some sort, such as
Microsoft Office files or CAD data files.
• You can digitally sign a PDF file stored as a dataset named reference file with
Adobe Acrobat and Adobe Reader.
New style sheets let you configure create dialog boxes and summary display
for Document objects.
The Digital Sign Dataset ACL rule grants the owning user and owning group
digital signing privileges for the dataset object.
Note Digital signing is supported only for PDF datasets created in Teamcenter
10.1 or later.
o In the Adobe Reader, the PDF file must have Enable Usage Rights
for Digitally Sign enabled.
• You can use create style sheets provided for Document objects to customize the
New Business Object wizard in the rich client and thin client to streamline
the document creation process.
Two user interface dialog boxes added to the New Business Object wizard support:
• Attaching files to a dataset for a new object.
o Template files are checked out and downloaded to the appropriate directories
only when no files are attached during creation of the item revision and
when you select the Check-Out Item Revision on Create check box to check
out the item revision at creation.
o You can check out item revision objects with IRDC configured, and you can
download the attached source dataset files to local specified directories. The
relation between the checked-out item revision and the derived visualization
datasets is deleted.
Note If you select only the dataset attached to the item revision to check
out, the download dialog box is not displayed and the associated
files cannot be downloaded.
o When you check in item revision objects governed by IRDC, the checkin
process:
Uploads local files that have been downloaded through checkout.
If the search mode is specified in the IRDC, the system searches the user’s
local system to get the derived visualization files for checkin.
o When revising item revision objects controlled by IRDC that have Check-Out
Item Revision on Create enabled, you can download the attached source
dataset files to local specified directories.
• When you cancel checkout of item revision objects with IRDC, the downloaded
local files are deleted.
• When you delete item revision objects with IRDC, if the Delete Files setting in
the IRDC object is set to false, the attached dataset of the item revisions are
not deleted.
Note Teamcenter provides a sample document management project that contains
examples of dispatcher service configurations and IRDCs.
For information about importing the sample document management project,
see the Business Modeler IDE Guide.
Creating documents
Depending on how document management is implemented at your site, you can
create documents with or without item revision definition control (IRDC) objects that
specify templates and behaviors for specific document types.
Style sheets are provided for create dialog boxes and summary display for
Document objects.
Rendering documents
You render item revisions containing a datasets to translate the associated files an
alternate formats. For example, you can render an item revision with an attached
Microsoft Office dataset file to derive an Adobe PDF dataset file.
After the translation (rendering) is finishes, the derived dataset appears under
the item revision. The derived dataset is generated based on IRDC values set by
the administrator.
3. Check out the item and add a dataset with a file of a type that should be
rendered by the IRDC control.
• Users can create user setting that takes precedence over the site setting.
For example, your Acrobat Markup Tool, PDF_Tool, and MSWord
specifies using Acrobat, then Reader, then MSWord, in that order.
When markup capabilities are enabled and the user has markup privilege, the user
can:
• Select one or more items, item revisions, or dataset objects, then choose
File→View/Markup to launch an external or embedded application to display the
related document and its associated markups.
• Update the status field of a markup dataset with any text string. The value is
typically open, approve, or close.
For information about configuring view and markup functionality, see Getting
Started with Document Management.
• X
Closes the dialog box without launching an application.
Note You must have appropriate privileges to use the File→View/Markup menu
command. For information about configuring view and markup functionality,
see Getting Started with Document Management.
• Adobe Reader
Note The PDF file must have Enable Usage Rights for Digitally Sign enabled.
Use Adobe Acrobat or Adobe LiveCycle Reader Extensions to enable
usage rights for PDF files.
Digital signing is supported only for PDF datasets created in Teamcenter
10.1 or later.
For more information about digital signing, see Getting Started with Document
Management.
Siemens PLM Software recommends these methods for signing Teamcenter PDF
documents:
• Sign documents with no markup.
Note If you sign documents containing markups, those markups are embedded
in the signed PDF file.
The initial configuration for digital signing of PDF files is set to not include
markups as follows:
• User-specified stamps.
• Printer Name
Displays the name of the printer specified by the selected print configuration.
• Number of Copies
Specifies the number of copies to print. This field requires a positive integer
between 1 and 99.
• Collate
When two or more copies are printed, this checkbox specifies whether the printed
pages are collated.
• User Stamp
Specifies text for a user stamp to be applied in addition to any existing system
stamp configuration.
For more information about creating system stamp configurations, see the
Business Modeler IDE Guide.
• Paper Size
Lists available paper sizes as provided by the selected print configuration object.
• Page Range
Specifies a range of pages to print.
• Color
Specifies Color or Monochrome printing.
• Print To Scale
Specifies the scaling factor, from 0.000001 to 100.0, applied to an image when it’s
printed.
With standard fit-to-page functionality, the image size is adjusted to fit the paper.
When Print To Scale is used, the image is adjusted to the scale value.
o A value of 1.0 means the image prints at a 1:1 scale factor. For example, a
square image that measures 5 inches on each side is printed 5 inches per
side on the paper, regardless of the paper size. If the paper size is smaller
than 5 inches, the image is cropped.
o A value of 2.0 means the image prints at a 2:1 scale factor. In this case, a
square image that measures 5 inches on each side is printed as a 10 inch
image and cropped to fit the paper, if necessary.
o A value of 0.5 reduces the printed image size, so the image that measures 5
inches on each side is printed at 2.5 inches per side.
• Print Stamp
Provides a list to specify whether the print stamp applies to the first page, the
banner page, or all pages.
• Orientation
Specifies the paper orientation of best fit, portrait or landscape.
o Best Fit
The image is rotated 90 degrees, if necessary, so the long side of the image
matches the long side of the paper.
o Portrait
No rotation is performed.
o Landscape
By default, the image is rotated left 90 degrees.
Note Default rotation direction can be configured in Vis Print.
• Banner Page
Specifies whether to print a page including the defined stamps and listing
additional data as specified by the vvcp setup. The Banner Page box that has
the following values: Off, Single, and All Files.
• Item create
During item creation, attach an image file to the item.
For more information, see Create an item using the New Item dialog box.
Explicit checkin is not required as an automatic checkin occurs during item
creation.
• Update thumbnails
Update Thumbnail functionality allows you to change the source dataset of the
thumbnail and remove thumbnails from the item revision.
You must perform an explicit checkout and checkin after this action.
For more information, see Update a thumbnail graphic.
o Explicit checkin is not required as the item revision being associated already
has a thumbnail.
3. In the Update Thumbnail dialog box, choose the new thumbnail source.
4. You can also select thumbnail display for the item revision by choosing any of
the following options:
• None: No thumbnails are displayed.
• Click OK.
• Navigate from a vendor object to associated commercial parts and vendor parts.
• Display vendor parts in product structures according to rules, with support for
BOM compare to view changes to vendor part relations.
Note After you freeze a commercial part, you cannot change the preferred status
for the vendor part.
For information about vendor management preferences, see the Preferences and
Environment Variables Reference.
1. Create Vendor objects and specify the vendor role as Supplier, Manufacturer,
or Distributor.
2. Define the company locations from which that each vendor supplies parts.
5. Populate the product structure (BOM) with commercial parts. The associated
vendor parts are now visible on the Vendor Parts pane of Structure Manager.
6. Define Bid Package objects with line items related to commercial parts and
vendor quotes.
Note Ensure you relate the objects or the results may be unreliable. For example,
commercial part items are related to vendor part items, although they are
not shown in the Vendor Parts pane in Structure Manager.
• Vendor
Supplies one or more vendor parts with attributes for locations and contacts.
Business enterprises may maintain a list of approved vendors (approved vendor
list or AVL) outside of Teamcenter, for example, in a Microsoft Excel spreadsheet.
• CompanyLocation
Lets you record information for a particular site or facility, including the name
(required), Web site, address, region, location code, location type, and notes. A
company location can be related to any number of company contacts.
• CompanyContact
Specifies an individual in a company and lets you record standard contact
information. First name and last name values are required.
• VendorPart
Acts as a vendor representation of a part.
A vendor part:
o Is obtained from a single vendor, not multiple vendors.
o Has a vendor part name assigned by the vendor or assumes the company’s
name for the part.
Vendor parts can be qualified with a status, for example, preferred, backup,
approved, or obsolete. This allows your company to always use the best source of
vendor parts. It also allows you to grade the overall product BOM.
For more information about product structure, see Getting Started with Product
Structure.
Note A VendorPart object cannot be sent to Structure Manager because
the VendorPart object type is not intended to be included in an OEM
product structure. Instead, a CommercialPart object should be
included in the structure. A CommercialPart object is an internal
representation of a sourced part, while a VendorPart object is a vendor
representation of the part.
• CommercialPart
• BidPackage
Contains package line items you supply to vendors who submit quotes. Bid
packages can be assigned to selected projects or programs.
• BidPackageLineItem
Comprises a BOM line representing a part or assembly with associated context
rules, if any.
• Quote
Contains the vendor’s response to a bid package line item. The vendor offers
(attaches) vendor parts that satisfy each line item in the bid package.
Note When you create a vendor management object, such as a commercial part,
vendor part, or vendor, the system creates organizational folders, called
pseudofolders , to display related objects. For example, when you create a
CommercialPart object, the system creates pseudofolders to display related
vendors and vendor parts. Similarly, for a Vendor object, the system creates
folders to display related commercial parts and vendor parts. Finally, for
VendorPart objects, folders are created for commercial parts and vendors.
• Supplier
Makes parts to order for the OEM.
1. In this context, your company is referred to as the original equipment manufacturer (OEM).
• Manufacturer
Makes parts for the general market.
You can create the necessary role types for your business with the Organization
application.
For more information, see the Organization Guide.
Note The Teamcenter administrator can set a TC_Role-Type_info_form
preference to define a custom form for a vendor role.
If you define a custom form for a role and you select that role during creation
of a new vendor, the system dynamically loads that form. For example, if
you have a custom form for the supplier role and a valid form type, such as
SupplierInfo, you can set the value of the TC_Supplier_info_form site
preference to SupplierInfo.
3. Type values for Part ID, Revision ID, Name, and an optional Description; click
Next.
Note You can click Assign to automatically generate Part ID and Revision ID.
5. Provide additional attribute values as needed, and click Finish to create the
commercial part object.
Note The default value for the revision master form Make or Buy attribute is
2 (Buy).
3. Type values for Vendor Part Number, Vendor Part Name, and an optional
Description; click Next.
4. Type or select a value for Vendor ID, type an optional value for Location, and
click Next.
To select a value for Vendor ID, click the Search button beside the Vendor ID box
to display the Open by Name dialog window.
Type either the name of the vendor or the vendor ID and click the Find button. If
duplicate vendors exist with the same vendor ID, the Item Resolution dialog box
appears allowing you to select the appropriate vendor.
5. Provide additional attribute values as needed, and click Finish to create the
vendor part object.
2. Drag-and-drop a vendor part into the Vendor Parts folder of the Commercial
Part revision.
3. Type values for Vendor ID, Revision ID, Name, and an optional Description,
and click Next.
Note You can click Assign to automatically generate Vendor ID and Revision
ID.
5. Provide additional attribute values as needed and click Finish to create the
vendor object.
3. Type values for Bid Package ID, Revision ID, Name and an optional value for
Description and click Next or click Finish to create the bid package and bid
package revision object.
Note
The system also creates an empty line item pseudofolder under the bid
package revision object.
3. Type values for the Name box and an optional value for the Description box.
4. Enter the Part/Assembly value to specify the commercial part to which the
line item refers.
5. Enter the Configuration Context value to specify the configuration and variant
rules for export.
6. Type a value in the Quantity box for the number of parts required.
Note
The line item is created with a pseudofolder for quotes. Quotes are
typically added automatically by importing data, but you can also add a
quote by selecting and copying a Vendor object, and selecting the line item
and choosing Vendor Management→Add Quote from the shortcut menu or
the Tools menu. In the Add Quote dialog box, provide the Name value and
other values, and paste the value for Vendor in the indicated area.
2. Choose File→New→Other.
The system displays the New Business Object dialog box.
3. Select Company Location from the list of business objects and click Next.
4. Type the values for Name (required) and type the values for the following
optional fields:
• Location Code
• Location Type
Select a value from the menu for Location Type:
• Street
• City
• State/Province
• Postal Code
• Country
• Region
• URL
• Description
3. Type values for Vendor Part Number, Vendor Part Name, and an optional
Description; click Next.
4. Type or select a value for Vendor ID, type an optional value for Location, and
click Next.
To select a value for Vendor ID, click the Search button beside the Vendor ID box
to display the Open by Name dialog window.
Type either the name of the vendor or the vendor ID and click the Find button. If
duplicate vendors exist with the same vendor ID, the Item Resolution dialog box
appears allowing you to select the appropriate vendor.
6. Provide additional attribute values as needed and click Finish to create the
vendor part object.
2. Drag a location from the vendor to the Provide From Locations folder of
the vendor part.
Note The system either verifies that the location is a child of the vendor that
is providing the vendor part or displays an error message.
3. Choose Edit→Cut.
2. Choose View→Properties.
When a property is updated, it overwrites the object with the new value.
Delete a location
1. In My Teamcenter, expand the Locations folder under a vendor.
3. Choose Edit→Delete.
This removes the location from the list of associated locations for the vendor from
the database.
2. Choose File→New→Other.
The system displays the New Business Object dialog box.
3. Select Company Contact from the list of business objects and click Next.
4. Type values for Title, First Name (required), Last Name (required), Suffix, Phone
(business/home/mobile), Fax, Pager, Email, and Description.
The system creates the contact object and associates it to the selected vendor or
company location using the ContactInCompany relation.
2. Choose View→Properties.
2. Select a location.
2. Select a location.
Delete a contact
1. In My Teamcenter, expand the Contacts folder.
3. Choose Edit→Cut.
This removes the contact from the list of associated contacts in the database.
Delete a vendor
1. In My Teamcenter, select the vendor you want to delete.
2. Choose Edit→Cut.
If a vendor is deleted, the associated locations and contacts are also deleted.
• If the part is not already classified, the system prompts you to classify it.
Select the particular class where you want to classify that object.
2. Choose File→New→Dataset.
The system uploads the associated files and displays the dataset under the
pseudofolder.
Define the default display identifier for an item or item revision . . . . . . . . . . . 8-6
You enable display of alternate and alias identifiers by using shown item relations.
Separator and context length associated with the identifiers can be configured.
For more information, see Define alias ID and alternate ID as a shown relation.
Note In a default configuration, you can use the Search view to find items
by specifying the alternate identifier. To search based on Alternate
ID and Context criteria to find items that have been published to the
Object Directory Service (ODS), choose Change Search→System Defined
Searches→Remote. Also, your system administrator can add the identifier
and context to Item and Item Revision saved queries.
To search alternate identifier values in Structure Manager, use an Item or
Item Revision search. To display alternate identifier values in Structure
Manager, you must edit a preference to add the column to the BOM line
display table; an administrator can use the Business Modeler IDE to add
a title for the new column.
For information about making product structure searches, see the Structure
Manager Guide.
Warning The alias identifier feature (accessed from the Revise and New Item
dialog boxes or using the New→ID command on the File menu)
is a replacement for the alias object feature accessed by choosing
File→New→Alias. These features must not be used together in the
same database.
• The identifier attribute cannot be modified if any revision of the item has been
released.
• If you want to use custom attributes for identifiers, your administrator must
create two new classes, one for the identifier and one for the identifier revision.
These new classes should be based on the identifier class.
For information about defining contexts, creating types, identifier classes and
defining identifier context rules, see the Business Modeler IDE Guide.
For more information about alternate identifier rule characteristics, see the Business
Modeler IDE Guide.
Alias identifiers
Alias identifiers store part numbers and other attribute information for similar
parts, and they can be associated with many items or item revisions.
Alias IDs let you store information about external entities.
For example, alias IDs can be used to do any of the following:
• Store parts according to internal naming conventions and also according to the
naming conventions of other companies, such as suppliers.
Alternate identifiers
Alternate identifiers store information about part numbers and attributes of the
same part from different perspectives. They allow different user communities to
identify and display an item or item revision according to their own rules rather
than according to the rules of the user who created the object.
Assigning alternate identifiers to a part at different stages of development and
production allows you to maintain a history of the lifecycle of the part.
Both alias and alternate identifiers are created within a context. The context is used
to denote a specific organizational focus, such as a supplier or a department in your
organization. You can also use identifiers to store custom information, such as a
supplier’s name and address or cost data.
Alternate identifiers have the following characteristics:
• An alternate ID identifies only one item or item revision in the database.
• Once created, the context and owning item revision cannot be modified.
• The identifier cannot be modified if any revision of the alternate has been
released.
• The item alternate cannot be deleted if any of the revision alternates cannot be
deleted.
Alternate IDs let you define additional identifiers for an item that are then useful for
setting up appropriate display contexts. For example, the design department can
use item IDs, but other departments or other companies may have other IDs. A
single item can be assigned any number of IDs, each unique within its context and
controlled and assigned by its own naming rules.
The following example shows possible alternated IDs for an item:
MyItem123
123456789@dept01
K9999999999@company01
0000-9999999@company02
• A user in department 01 can set the display context to see all items with their
dept01 number.
• A manager that deals primarily with company 01 can set the context to show all
items with the company01 ID values.
2. Choose File→New→ID.
The system displays the New ID dialog box.
4. Select the context for the new ID from the Select context shortcut menu.
9. Click Next.
If attributes are defined for the ID type, the system displays the Enter Additional
ID Information pane. Mandatory attributes are indicated by a red asterisk in the
upper-right corner of the box.
14. (Optional) Select one or both of the Use item identifier as default display and
Use revision identifier as default display options to set the new identifier as the
default display for the item or item revision.
2. Expand the General folder (in the left pane) and select the Item node.
The system displays the item options in the right pane of the dialog box.
4. Select the Alias IDs and Alternate IDs relations in the Available Relations list
and click Add.
The system displays the relations in the Shown Relations list.
5. Click Apply.
Alias ID and alternate ID objects are displayed in My Teamcenter.
Note Use the same procedure to display the identifier under the item revision
node.
2. Expand the General folder (in the left pane) and highlight the Identifier node.
The system displays the identifier options in the right pane of the dialog box.
5. Click Apply to save the change and retain the dialog box, or click OK to save the
change and exit the dialog box.
3. Right-click the item or item revision for which the alternate identifier will
become the default.
The system displays the Item Object shortcut menu.
6. If necessary, click Check Out and Edit to enable the arrows for the Paste
command.
7. Click the arrow next to the value of the id_dispdefault property and choose
the Paste option.
The alternate ID is now the default display for the item or item revision and is
displayed according to your identifier display rule settings.
Display rules can be associated with multiple contexts. The selected contexts are
evaluated by the system in the order in which they appear in the Selected Contexts
list, from top to bottom. If an item or item revision alternate identifier exists that
corresponds to the first context in the list, that identifier is displayed in your
workspace. If none match the first context, the next context is evaluated and if an
alternate identifier exists, it is displayed. This continues until a context is found
that matches one of the alternate ID contexts defined for the item or item revision.
For more information about ID context rules, see the Business Modeler IDE Guide.
If the item or item revision does not have alternate identifiers corresponding to any
of the contexts in the display rule, the Use Default option, found on the Id Display
Rules dialog box, lets you specify that the default identifier specified for the item
or item revision should be displayed. If no default identifier is specified, the initial
identifier attribute of the item or item revision is displayed as specified by your
default display identifier settings.
Note Default identifiers are specified when an alternate item or item revision
identifier is created, or they can be defined as a property of the item or item
revision using the Properties dialog box.
3. Click OK.
The system displays a confirmation dialog box stating that the rule will be
changed and the currently displayed data will be affected by the new rule.
4. Click OK.
The system closes the confirmation dialog box and the Id Display Rules dialog
box.
2. Click Create.
The system displays the Create ID Display Rule dialog box.
3. Type a name for the display rule in the Rule Name box.
This is the only requirement for creating a rule. However, if you do not select a
context, the initial ID attributes of the items and item revisions are displayed.
4. Select one or more contexts from the Available Contexts list and click Add (+).
The system displays the context, or contexts, in the Selected Contexts lists.
5. (Optional) Change the order of the contexts using the up-arrow and down-arrow
buttons.
The contexts in the Selected Contexts list are evaluated in order, from top to
bottom, to determine which identifier is displayed.
6. (Optional) Select the Use Default check box to display either the default or initial
identifier attributes for objects that do not fit any of the selected contexts.
7. Click OK.
The system displays the new rule in the Rule List pane.
8. To set this rule as your current display rule, select the rule and click Set Current.
The system displays a confirmation dialog box stating that the rule will be
changed and the currently displayed data will be affected by the new rule.
9. Click OK.
The system closes the confirmation dialog box.
2. Click Add.
The system displays the Add Id Rule dialog box.
3. Select the owner of the rules you want to add from the Select User list.
4. Select the rules that you want to add to your list. You can select a single rule
or multiple rules.
5. Click OK.
The dialog box closes and the rules are displayed in your rule list.
3. Click OK.
The dialog box closes and the rules are displayed in your rule list.
Modifying identifiers
You can use the Viewer tab or Properties dialog box to modify the properties of
alternate and alias identifier objects.
Once assigned, the context of the object cannot be modified. If any of the alternate
revision IDs are released, the alternate ID cannot be modified. In addition, you
cannot convert an alias identifier to an alternate identifier.
4. Click Apply.
4. Click Apply to modify the properties and retain the dialog box, or click OK to
modify the properties and exit the dialog box.
4. Click Yes to delete the alternate ID/alternate revision ID. Click No to cancel the
delete operation.
Note You cannot delete the last alternate revision ID of an alternate ID, you must
delete the entire alternate ID.
2. Right-click and choose Copy from the shortcut menu, or choose Edit→Copy.
3. Select the item or item revision for the new alias ID.
6. Click OK.
The system pastes the identifier object to the item or item revision with an alias
ID relationship.
9 Managing datasets
Open a dataset using a tool other than the tool defined for the dataset type . . . 9-7
9 Managing datasets
Managing datasets
Datasets manage data files created by other software applications. When you
double-click a dataset to open it, the system launches the software application
associated with the dataset instead of expanding a container.
When your administrator configures Teamcenter for your enterprise, other software
applications can be encapsulated. These application data files can then be managed
from inside a Teamcenter session. If your administrator has encapsulated other
software applications (Microsoft Word, Microsoft Excel, and so on), those icons also
appear in Teamcenter.
Your administrator can also configure Teamcenter document management
functionality to simplify interactions with datasets by configuring behaviors for
rendering, printing, and marking up documents, and for generating thumbnail
images.
For information about working with document management in Teamcenter, see
Getting Started with Document Management.
You can use the Purge command on the Edit menu to completely and permanently
remove old versions of a dataset from the database. You can select whether to purge
all old versions or specific versions of a dataset. To purge a dataset, you must have
read, write, and delete privileges on the versions of the dataset that you want
to purge.
2. Choose Edit→Latest.
Note By default, the Edit→Latest menu command is not displayed. To enable
site-wide display of this command, the administrator must set the site
preference TC_suppress_Edit_Latest_Menu to True.
3. Click Yes to retrieve the latest version of the selected dataset or click No to
cancel the operation and close the dialog box.
When you attempt to delete a UGALTREP dataset, the system displays the
following message:
UGALTREP is in use in a UG/Manager assembly, so may not be removed.
Note The exact use of UGMASTER and UGPART datasets is highly dependent
on how your enterprise uses various features of NX and is beyond the scope
of this discussion. Refer to the NX Help for additional information about
UGMASTER and UGPART behavior and usage.
2. Modify the contents of the dataset, and click Save to create a new dataset
version.
Note Files associated with datasets can be modified from within Teamcenter.
When modifications are saved in the native application, a new version of
the dataset is created in Teamcenter.
3. (Optional) Cut, copy, paste, upload, and download named reference files, or edit
the name of the reference file.
Note If an empty dataset is opened, a zero-length file is created as a named
reference. The name of this file is based on the dataset name, and hyphens
in the dataset name are converted to underscores. This is the only time that
such a conversion takes place. For example, when a file is imported as a
named reference, any hyphens in the file name remain and are not converted
to underscores.
Creating datasets
You can create a dataset using menu commands or by dragging a file from an
operating system file manager onto a Teamcenter folder, an item, or an item revision.
In addition to being able to select dataset type before you import files, you can also
select files to import before selecting a dataset type.
This applies to the New Dataset dialog box displayed by the File®New Dataset menu
command, and to the Enter Attach Files Information pane displayed by File®New
wizards, such as the New Item wizard.
• When you select a dataset type, and then click the import button, only the files
that match the selected dataset type are displayed.
• When you select Import first, only the dataset types that match the selected file
name extensions are available.
If you select a dataset type that contains more than one named reference that
matches the available file extensions, the Select Reference Type dialog box
is displayed.
• To use the Shift key for multiple file selection, the site must implement the
com.teamcenter.rac.common.filesSelector extension.
Naming rules that control the format of the Dataset ID, Name, and Revision number
may be in effect at your site. These rules are managed by your administrator using
the Business Modeler IDE application.
For more information, see the Business Modeler IDE Guide.
Note A Microsoft Office dataset file created in Teamcenter is created as a plain
text file. The first time you save the file you are prompted to convert the
file to the standard format.
3. Type a descriptive name (up to 128 ASCII characters) in the Name box.
This name is used as a label in the object area.
Tip It is good practice to keep the names short so that you can see the entire
name in the My Teamcenter tree.
4. (Optional) Type a description (up to 240 ASCII characters) to help identify this
dataset in the Description box.
7. Select a dataset type from the Type bar by clicking the icon.
If the type names are truncated, click the arrow located in the upper-left corner
of the Type bar, and then select a type from the list.
The Type bar displays the dataset types that you use the most.
If you do not see the type you are looking for, click More to display all defined
dataset types.
Note The dataset types displayed in this dialog box are controlled by your
administrator. Therefore, you may be unable to create dataset types that
are visible to you in your workspace.
8. Select the Tool Used option to edit the dataset file if more than one option
is available.
9. To select a file, click the button to the right of the Import box.
The Upload File dialog box appears.
10. Navigate to the file to be imported, select the file, and click Upload.
The system closes the Upload File dialog box, and the path to the file appears
in the Import box.
Note The type of file that you import must match the dataset type selected in
step 7.
11. Select Open on Create to launch the tool associated with the dataset and
immediately open the file upon creation.
2. In a file system window, select the file to add and drag it over the Teamcenter
folder, item, or item revision.
The New Datasets for Multiple Files dialog box is displayed.
• Type a description (up to 240 ASCII characters) to help identify this dataset
in the Description box.
• Change the values in the Dataset Type, Reference, and Tool Used boxes.
4. Click OK.
The system displays the new dataset object under the drop-target object.
4. Leave the name value as it appears, or type a descriptive name (up to 132 ASCII
characters) in the Name box.
Note You can also create a new dataset from a file by using the Import option
in the New Dataset dialog box.
3. Select the version of the dataset that you want to open from the Version combo
box.
4. Expand the Tools node in the tree to see the dataset files, and select the file
that you want to open.
Open a dataset using a tool other than the tool defined for the dataset
type
1. Select the dataset in the tree or Details table.
3. Select a file under the tool you want to use to open the dataset file. Expand the
Tool node in the tree to see the dataset files.
Open an NX dataset
1. Select the dataset or item revision with which the dataset is associated from the
tree or Details tabbed page.
Deleting datasets
Selecting a data object and choosing Delete from the Edit menu completely and
permanently removes that object from the database. Once a data object is deleted, it
cannot be recovered. Therefore, you are always prompted to confirm that you really
want to delete the object. You must have read, write, and delete privileges on an
object that you want to delete.
3. Choose Edit→Delete.
2. Choose Edit→Purge.
The system displays the Purge dialog box.
3. Click Yes to purge all other versions of the dataset or click No to cancel the
operation and close the dialog box.
• Named references are Teamcenter objects that relate to a specific data file. In
other words, a named reference is a file attached to a dataset. For example, you
create and select a dataset in the rich client, right-click to display the shortcut
menu, and choose Named References. You can then click Upload to associate
files to the dataset object.
Note Administrators define named references in the Business Modeler IDE
dataset type References tab.
For information about creating a dataset business object, see the
Business Modeler IDE Guide.
When you upload a file in the rich client, you select the dataset type along with
the file that you want to upload.
The named reference includes:
o Reference name
The reference type associated with the named reference.
• A single dataset object can have one or more named references. To view the
named references of a dataset from the rich client, select the dataset and choose
View®Named References, or right-click and choose Named References.
• A dataset type must have at least one named reference associated with it. A
named reference defines the file information that can be added to this dataset
type.
dataset file from Teamcenter. A dataset type contains a list of tools that can
operate on the dataset. This list is known as the dataset references.
• A tool action specifies Teamcenter activity for a dataset. Tool actions are defined
on the dataset type and usually at least the Open action is defined. When no
tool actions are defined for a dataset, an error message is displayed when you
try to open the dataset in Teamcenter.
Note Administrator users can add named references using the import_file utility.
For information about the import_file utility, see the Utilities Reference.
3. Click Upload.
The system displays the Upload File dialog box.
4. Select the type of file to be uploaded. (This list of references is defined by your
administrator as part of the dataset type definition process.)
5. Navigate to the file to be uploaded, select the file, and click Upload.
The system closes the Upload File dialog box, and the file is displayed in the list
of named references.
6. After you finish adding files, click Close to exit the dialog box.
3. Select the rows containing the reference files to be exported and click Download.
The system displays the Downloading File dialog box.
2. Choose Translation→Translate.
The Translation Selection dialog box shows the selected objects for translation.
3. In the Translation Selection dialog box, choose appropriate values from the
Provider and Service lists.
5. If you want to specify translator arguments and other properties, click Next.
Teamcenter shows the Translation Selection dialog box for the service.
6. In the Translation Arguments section, you add, modify, or delete Key and Value
arguments.
7. In the Priority and Time Properties section, you can set the following options:
a. Time
Choose the time for the translation to start.
Click the Admin Time and Date properties button to display the Date
and Time dialog box.
In the Date and Time dialog box, type the translation start time and click OK.
b. Priority
Choose the priority for the translation task.
c. Repeating
Choose this option if you want to repeat the translation.
Note The Repeating option does not appear by default. You must set
the ETS.Repeating_UI.<ProviderName>.<ServiceName>
preference to TRUE to display the repeating tasks functionality.
9. If you want to specify translator arguments and other properties for the
remaining objects, click Next.
• Full geometry is loaded incrementally as you expand the model structure in the
assembly tree, or when you hold the Shift key and select in the viewing window.
For information about enabling the Simpgen translator in Teamcenter, see the
Dispatcher Server Translators Reference Guide.
The Simpgen translator lets you create JtSimplification datasets.
1. In My Teamcenter, select an item revision.
2. Choose Translation→Translate.
3. In the Translation Selection dialog box, select the simpgen service, and then
click Next.
5. In the Priority and Time Properties section, specify the appropriate values for
translation time, priority, and translation repeating schedule options.
8. After the translation is complete, the translated file appears in the item revision.
For information about working with JtSimplification data, see Working with 3D
Models.
Note The VIS_simpgen_admin_group site preference specifies user group
authority to run the Simpgen translator from the Teamcenter Translation
menu.
For more information about this preference, see the Preferences and
Environment Variables Reference.
2. In My Teamcenter, select the item revision containing the JT model from which
you want to generate MMV data.
3. Choose Translation®Translate.
4. In the Translation Selection dialog box, select the mmvindexgen service, and
then click Next.
6. In the Priority and Time Properties section, specify the appropriate values for
translation time, priority, and translation repeating schedule options.
3. In the Translation Selection dialog box, select the appropriate values for the
Provider and Service lists.
4. Select the translation time, priority, and translation repeating schedule options
from the Date and Time Properties section.
7. After the translation is complete, the translated CAD file appears in the item
revision.
If your site has the Teamcenter lifecycle visualization embedded viewer installed,
you can view the translation result in the Viewer data pane in My Teamcenter or in
the Viewer tab in Structure Manager.
2. Choose File→New→Folder and in the New Folder dialog box, enter a name for
the folder, for example, my_pcb_folder.
The new folder appears within the Home folder structure.
4. Choose File→New→Item and in the New Item dialog box, select PCBCircuit.
5. In the New Item dialog box, click Next, and then click Assign to name the new
item, for example circuit, and then click Finish.
6. Click Close.
7. Expand the my_pcb_folder folder and select the circuit item revision.
Note The my_pcb_folder folder and circuit item revision are sample names.
10. In the Import File dialog box, select the CAD file you want to import into My
Teamcenter and then click Import.
11. Click OK to close the New Dataset dialog box and your file is imported as the
new dataset type.
13. In the Select translator for dataset dialog box, in the Provider section, select
UGS.
14. In the Translator section, select a translator that can translate your native
CAD file.
18. Select the desired gencad item and click Refresh. Close this dialog box when
the translation is finished.
Note The gencad translator is one of about 40 PCB CAD translators
supported by the software.
19. To display the new XFATF file, select the circuit node, right-click and choose
Refresh.
The XFATF item revision appears in the Demo folder.
20. If the CAD file in a PCBCircuit item contains multiple PCB designs (for example,
panelized circuits), after translation the child items of the PCBCircuit item are
created. Each child item contains translated version of an individual PCB design.
Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Sequence accumulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Sequence preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Sequence ID display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Query for sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Set sequence immunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Delete and purge sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
• The Check-Out option locks an object in the database so that only you can
modify it.
• The Check-In option releases the lock, allowing other users to access the object.
• Only your administrator can circumvent the security that the checkout function
provides.
• Implicit checkout occurs when you double-click to open a dataset from the rich
client or click Edit beside a dataset file in the thin client. Implicit checkout only
occurs if the object is not already checked out. Checkin occurs automatically
when you close the document.
For more information, see Implicit checkout.
The following objects can be checked into and out of the database:
• Folders
• Datasets
• Forms
Explicit checkout
When you check out an object by using the Check-In/Out commands on the Tools
menu, or when you use the Check-Out and Edit button in a view, you explicitly check
out the object from the database. Explicit checkout ensures exclusive modification
access to an object.
You define the checkout directory by choosing Edit→Options and setting the General
Check-In/Check-Out options.
You can set the Export files on checkout option to YES to lock the dataset for
everyone, including the person who holds the checkout.
• When a dataset is checked out during export, the named references are
downloaded to a local operating system directory and can be modified locally
outside of the Teamcenter environment.
• When the dataset is checked into the database, any modifications to the named
reference files are automatically uploaded to the database.
Note If your site has the TC_Auto_Checkout preference set to OFF, you must
use Export files on checkout to save modifications to a dataset named
reference. The downloaded named reference can be modified outside
Teamcenter. When modification is complete, the dataset must be checked in
through Teamcenter.
Implicit checkout
When you double-click a dataset object in Teamcenter, the system automatically
creates an implicit checkout to ensure that two processes are not allowed to
simultaneously update the dataset.
Implicit checkout differs from explicit checkout in the following ways:
• Implicit checkout is automatic and occurs when you open a dataset for
modification. When the modifications are completed, the dataset is automatically
checked back into the database.
• Users included on notification lists are not notified when implicit checkout
takes place.
• An implicit checkout in the Viewer view is released when you select a different
object while the Viewer view is active. The checkout lock is not released if you
only select another view such as the Summary or Details view.
Note The implicit checkout lock is released automatically when you return
to Viewer and close the object, or select another object to open in the
Viewer view.
o Click OK to automatically check out the object, save it, check in the object,
and close the dialog box.
• When you already have the object checked out, the Properties dialog box displays
the Save, Check-In, Cancel Check-out, and Close buttons.
• When an object is checked out by another user, the Properties dialog box displays
the Close button.
2. Click the Reservation link located in the lower-left portion of the dialog box.
The Checked Out by box displays the name and site of the user who has checked
out the object.
2. Choose Tools→Check-In/Out→Check-Out.
The system displays the Check-Out dialog box.
3. If you want to check out only those objects displayed in the dialog box (no
attachments or component objects), go to step 5.
4. (Optional) Check out component objects or attachments along with the selected
objects.
5. Click Yes (in the Check-Out dialog box) to check out the selected objects.
The button in the right margin of the dialog box (opposite the object) indicates
whether the process was successfully completed. If an error occurs during the
process, the error button is displayed for that object. You can double-click
the error button to display details about the error.
Check in an object
1. Select one or more objects that are currently checked out or select a checked-out
part or assembly represented by a BOM line in Structure Manager.
The Check-In option unlocks objects in the database, including assemblies in
Structure Manager, that were previously checked out.
Note If you use this option to check in a replica item revision and have
added data to the item revision prior to checking it back in, the system
perceives the new data as being owned by the site that owns the item
revision rather than being owned by the author at the local site.
For more information, see the Multi-Site Collaboration Guide.
2. Choose Tools→Check-In/Out→Check-In.
The Check-In dialog box appears.
3. If you want to check in only those objects displayed in the dialog box (no
attachments or component objects), go to step 5.
5. Click Yes (in the Check-In dialog box) to check in the selected objects.
The button in the right margin of the dialog box (opposite the object) indicates
whether the process was successfully completed. If an error occurs during the
process, the error button is displayed for that object.
You can double-click the error button to display details about the error.
3. Click Yes to cancel the checkout, or click No to stop the cancellation operation.
• The checkout is canceled immediately.
• The Details table CO- Checked Out column entry changes to blank.
• Site name and user ID of remote users who have checked the object out
of the database
3. To add yourself to the list, click Add (+). To remove yourself from the list, click
Remove (–).
Your name is added or removed from the list.
Sequences
You use sequences if your business requires additional management of progress
within revisions.
• A sequence is an iteration of the object, complete with properties and relations.
A sequence of a file is similar to a version of a file, but the sequence encompasses
all information about the object.
When you create an item revision, an initial sequence, to which Teamcenter assigns
an initial sequence ID, is also created. This sequence becomes the active, or default,
sequence.
• Checkout actions increment the sequence ID for the item revision, with the most
recent sequence ID becoming the default.
• The default sequence is the only sequence you can check in and check out.
Attempting to check out a nondefault sequence results in an error.
• Only one sequence can be active at any given time for an item revision.
Sequence accumulation
Teamcenter limits by object type the number of sequences stored in the database.
At checkin, the system automatically removes the oldest sequence when you reach
the limit.
Note Your administrator can use the TCDefaultKeepLimit preference to specify
the number of sequences retained in the system.
• When you create a new item revision, such as when you revision A to revision
B, all sequences are removed from the new revision and the new revision starts
with the first sequence ID.
• You can set immunity for sequences to prevent their automatic removal.
The system displays an error message if you attempt to exceed the established
limit. To add a new sequence after you reach the limit, you must remove at least
one sequence by using either the Delete or Purge actions.
For information about using search queries to retrieve sequences, see Query
for sequences.
For information about removing sequences, see Delete and purge sequences.
Sequence preferences
The following preferences affect sequence behavior:
• TCDefaultKeepLimit
• TCDefaultKeepLimitByType
Determines the number of sequences the system maintains for the specified
business object.
• TCCheckoutReserveOnly
Specifies for business objects whether a restore copy is not created during
checkout.
Sequence ID display
The system displays the sequence ID appended to the item ID and revision,
separated from the item revision by a semicolon (;). The sequence ID is followed by a
hyphen (–) and the object name. For example, the sixth checkin for item revision
000186/A of part P_AX32 is displayed as follows:
000186/A;6–P_AX32
By default, the system only displays the active sequence, but you can display all
sequences for an item using a search query.
For example, a query for All Sequences returns sequence information in the
following format:
000186/A;3–P_AX32
000186/A;4–P_AX32
000186/A;5–P_AX32
000186/A;6–P_AX32
For information about using search queries to retrieve sequences, see Query for
sequences.
o A purge used with a previous sequence selected removes only the selected
sequence, but only if it is not marked immune from purge.
For more information about making a sequence immune, see Set sequence
immunity.
For information about using search queries to retrieve sequences, see Query for
sequences.
For information about most import and export commands, see the Data Exchange
Guide. Additional references for specific types of data sharing are noted where
those types of data are described.
Briefcase provides an alternative method of sharing data with suppliers or other
unconnected Teamcenter sites. A Briefcase package file contains the selected object,
such as an assembly, and its related components and data, in an archive format.
The PDX export process packages Teamcenter data in a file format that is usable
by applications that support the PDX format. You can also import PDX packages
into Teamcenter and, if you have a configured a PDX tool in Teamcenter, open the
package into the tool.
You can import and export data that in PLM XML format. When you export objects
in PLM XML format, the transfer mode determines what data is exported. You can
also track your PLM XML exports using Application Interface mode.
For more information about transfer modes, see the PLM XML/TC XML Export
Import Administration Guide.
Note While exporting workflow templates from a site using PLM XML, some of the
associated objects such as named ACLs, saved queries, and release statuses
do not get exported for security reasons. Therefore, when the exported file is
imported at another site, these associated objects are not imported/created.
Named ACLs must be manually created and synchronized between sites.
Saved query and release status objects can be exported/imported separately
using PLM XML, and this method should be used to synchronize these
objects between sites. During PLM XML import, if the process encounters
these object types, a warning message is written to the log file indicating
that these objects must be synchronized independently. The log file is named
plmxml_log_#.log and is located in the log directory.
You can import objects from other sites in to your database even if you do not
have a direct network connection to the site; however, you must have a directory
containing data exported from the other site. This directory must be the output of
an object export operation (as opposed to simple file export operation) using one
of the following object export methods:
• Teamcenter export
• STEP export
Object export allows you to export objects in Teamcenter format or STEP format.
When you export an object in Teamcenter or STEP format, you move all internal
data associated with that object. For example, if you export an item, you export
all its relations (for example, item revisions, BOM view revisions, item master,
and any exportable requirement, specification, manifestation or reference objects)
in one operation.
With Supplier Relationship Management (SRM), when an original equipment
manufacturer (OEM) sponsor needs to exchange data with a supplier who does not
have a Teamcenter installation, the sponsor can select items in My Teamcenter to
share with the supplier. The sponsor’s e-mail address is required, and the sponsor
can optionally type a reason for the export and can specify a transfer option set.
For information about configuring export to SRM, see the Data Exchange Guide.
For information about JT import and export, see the PLM XML/TC XML Export
Import Administration Guide.
For information about importing and exporting Systems Engineering structures, see
the Systems Engineering Guide.
Export an object
1. Select the objects to be exported.
2. Choose Tools→Export→Objects.
The system displays the Export dialog box.
4. Enter the path to the directory containing the objects to be exported in the
Parent Directory box.
(Optional) Click Browse to locate the directory.
5. Specify the name of the export directory in the Export Directory box.
6. (Optional) Type comments related to the export operation in the Reason box.
7. Use the buttons to the right of the Target Sites list to select the Multi-Site
Collaboration export destinations for the objects.
9. Click OK to export the objects in the Object List and close the dialog box.
2. Choose Tools→Export→Objects.
The system displays the Export dialog box.
4. Enter the path to the directory containing the objects to be exported in the
Export Directory box. (Optional) Click Browse to locate the directory.
5. Specify the name of the export file in the Export Filename box.
6. (Optional) Enter comments related to the export operation in the Export box.
8. (Optional) Select the View Log File option to view the log file when the export
operation is complete.
10. Click OK to export the objects in the Object List and close the dialog box.
• To export property data for one object at any level, select only the object.
Note Data is exported also for all direct children and lower level
descendants of the selected object.
• To export property data for two or more objects, use the standard Windows
functions for multiple selection.
Note o You can select multiple objects at the same level or at different
levels.
Caution The Live integration with Word output mode ignores landscape
orientation in specification templates. The page layout is portrait
orientation in all live Word documents.
• Export for Markup generates a Word document containing the markups for
the selected requirement specification or requirement revision.
Caution Siemens PLM Software does not support markups when different
Microsoft Office versions are used. For example, if a markup
comment is created in Microsoft Office 2007, it does not open
in Microsoft Office 2010.
For more information about working in live Word offline documents, see
the Client for Microsoft Office Guide.
o Check out objects before export explicitly checks out the selected
objects from Teamcenter before the live Word document is generated.
You reserve access to the objects until you check them in, either when
you commit changes to the structure or cancel the changes.
Note The Check out objects before export option is unavailable by
default. You can enable the option by setting a preference in
the Options dialog box.
4. To use Word export templates other than the defaults, do the following under
Template Override:
Warning Do not select a template that was created in Microsoft Word 2003.
Only templates created in Microsoft Word 2007 or 2010 can be used
for export.
If you have questions about your site’s Word export templates,
consult your Teamcenter administrator.
Warning If you select the Live integration with Word output mode,
you must select an object template that contains the
{%object_name} property keyword. Otherwise, you cannot edit
structure data in live Word.
• The Copy URL button is unavailable if the Check out objects before
export option is selected.
2. Choose Tools→Import→Objects.
The system displays the Import dialog box.
4. In the Importing Object box, click Browse to locate and select a folder or
file from the system directory.
5. If you selected a directory or file containing Teamcenter objects, the objects are
displayed in the Object List. Select the objects that you want to import using
one of the following methods:
• Click the check boxes to select individual objects in the list.
• Click All But to select all objects except those that are currently selected.
Note The report options are offered in addition to the operation log file.
Generate Generates a report listing the objects that were imported. The
Import system displays the report after the successful completion of the
Report import operation.
Preview Performs a "dry run" of the import operation. The resulting report
Import lists the objects that would be imported, as well as any problems
Report that are encountered.
Continue Allows the import operation to continue if errors are encountered
on Error while importing optional objects. All objects are considered
optional except those with the following relation types:
Requirement
Specification
Item Master
Item Revision Master
7. Click Apply to start the import operation and retain the dialog box, or click OK
to start the import operation and exit the dialog box. When the import operation
has successfully completed, you can review the log file.
1. Select the container object into which the objects will be imported.
2. Choose Tools→Import→Objects.
The system displays the Import dialog box.
4. Type the path to the folder containing the STEP file that you want to import in
the Importing Object box, or click Browse to locate and select a folder from
the system directory.
Once a STEP file is selected, the directory path of the selected file is displayed
in the Importing Object box.
The STEP file and all included references are displayed in the Include Reference
section of the dialog box.
5. Review the objects selected for import, as displayed in the Include Reference list.
• If the list accurately reflects the objects that you want to import, click Apply
to start the import operation and retain the dialog box, or click OK to start
the import operation and exit the dialog box.
• If the list does not accurately reflect the objects that you want to import, click
Cancel and begin the process again.
When the import operation has successfully completed, you can review the
log file.
3. In the Export Directory box, select the directory in which to place the PLM XML
file. Click Browse to locate the directory.
4. Specify the name of the export file in the Export Filename box.
6. (Optional) Click Select Languages to display the Language Selection dialog box
for the languages configured at your site.
• The Available Languages box lists the languages you can select as additional
languages for export.
• The Select Languages box lists the preconfigured languages for the selected
transfer mode.
c. Click OK or Apply.
The languages selected for export are displayed in the Languages box.
Note If you change the transfer mode, the Languages entries remains
unchanged. You can use the Language Selection dialog box
again to add or remove more languages.
8. (Optional) Select Open PLM XML File to view the file when the export operation
is complete.
10. Click OK to export the objects in the Object List list and close the dialog box.
When the export completes, a dialog box displays.
If the export was successful, you can click Yes in the dialog box to view the
log file for the export.
If there were errors during the export, the dialog box lists the errors. Click Yes
to view information about the errors that occurred.
Note Exports that completed without errors in past versions may now show
errors. Previously, unless the PLMXML_log_file_content preference was
set to detailed, errors did not display. The detailed error information now
displays in the log file by default. Setting the PLMXML_log_file_content
preference to detailed produces detailed information of all objects (those
successfully exported and those exported with errors).
2. Choose Tools→Export→Objects.
The system displays the Export dialog box.
Name Description
Description Describes the application interface (optional).
Name Description
Import Transfer Mode Specifies the transfer mode used when objects are
Name imported into your database.
For more information about transfer modes, see the
PLM XML/TC XML Export Import Administration
Guide.
Export Transfer Mode Specifies the transfer mode used when objects are
Name exported from your database.
For more information about transfer modes, see the
PLM XML/TC XML Export Import Administration
Guide.
Target Sites Specifies the sites to which objects will be exported
when this application interface is used.
Active Incremental Specifies the incremental change into which objects
Change will be imported. The buttons to the right of the
Active Incremental Change box enable you to create
an incremental change object, search for a change,
or select from the most recently used changes. In
addition, the Information button allows you to view or
modify the active change.
For more information about incremental change
objects, see Getting Started with Product Structure.
7. Click OK to export the objects in the Object List and close the dialog box.
3. Select PLM XML File (.xml) from the Files of type list.
4. Navigate to the directory containing the file and select the file.
The system displays the file name in the Directory name box.
5. Click Select.
The system displays the path to the selected file in the Importing Object box
of the dialog box.
8. Click Apply to start the import operation and retain the dialog box, or click OK
to start the import operation and exit the dialog box.
The system imports the data as follows:
• By default, the imported object has no container reference. You can use
relevant search criteria to find the imported object and so you can copy it to
a folder.
For information about using search criteria for finding imported PLM XML
data, see the Rich Client Interface Guide.
• To have Teamcenter import objects into your Newstuff folder, create the
PLMXML_put_objects_in_newstuff_on_import preference and set the
value to TRUE. Imported objects are placed in a folder with the same name
as the imported XML file.
Note If object names or IDs are encountered that exceed the character limit
for those boxes in Teamcenter, the name and/or ID is truncated when
imported into Teamcenter.
When the import completes, a dialog box appears. You can click Yes in the dialog
box to view the log file for details on the import and information about any
errors that occurred.
Note Import results can vary, depending on the localization status of property
values and the languages involved.
• If the PIE_allow_import_with_different_sml preference is set to
true, import is allowed even though the site master language from the
exporting site is not the same as at the importing site.
• If some of the languages represented in the PLM XML file are supported
in the importing site, the nonsupported languages are ignored for import
and are logged in the importer log.
• You can view unsupported languages in the import log file. If there is no
language information in the XML file, the PLM XML file contents are
imported into the database based on your data entry preferences.
• You can import localized property values of objects from a PLM XML file.
The language marked with as primary is imported as attribute master
language. All other languages are imported as translation values with
respective language information.
2. Type the reason for importing the remote object in the Reason box.
3. Click Import Remote Option Settings to access the Import Remote Options
dialog box.
For information about options, see Preferences for importing remote objects.
• Click No to return to the Import Remote Options dialog box, then click No in
the Import Remote Options dialog box to cancel the operation.
The system displays the Remote Import Progress dialog box. The object
name, operation, and progress status of both active and completed remote
import operations are displayed in the dialog box until it is closed. Once closed,
completed operations are no longer displayed.
• IMAN_master_form
• IMAN_requirement
• IMAN_specification
The references included for import are displayed on the Advanced tabbed
page of the Import Remote Options dialog box.
The references displayed in this list are determined by the
values of the TC_relation_required_on_transfer and
TC_relation_required_on_export preferences.
Running validations
User can view the generated validation results associated with the target, view the
detailed report file stored in the results or delete the selected results. Validation
results can also be used as the basis to determine whether a target conforms to
standards and can be released.
The Tools→Validation→Run Validations menu command lets you specify validation
checkers under an agent to verify the selected targets by performing the validation
process defined by the agent. The validation process can store the results of the
validation process as validation results associated with the selected targets.
Note Validation Manager requires special setup and configuration with third-party
validation tools and Teamcenter workflow processes. This feature may not
be available at your site. For more information, see your local administrator.
1. Select one or more folders, items, item revisions, reuse design element, or shape
design elements in the My Teamcenter or Structure Manager tree.
3. Choose a validation agent from the Available Validation Agents shortcut menu.
Note If the user defined the agent class names with the
TC_VALIDATION_run_validation_hidden_agents preference, the
corresponding agent revisions are hidden from the list.
4. Select one or more validation checkers in the left pane of the Run Validations
dialog box.
• If a validation checker item revision is mandatory, it is marked with a red
star at the end. If the TC_VALIDATION_mandatory_checkers_required
preference is set to True, after you select an agent revision, all the
mandatory validation checkers under it are automatically added into the
Selected Validation Checkers tree, and they cannot be removed from it
unless you select another agent revision.
• If you select the top agent revision node from the Available Validation
Checkers tree and click the button, all validation checkers are added into
the Selected Validation Checkers tree.
• If you deselect the top agent revision node from the Selected
Validation Checkers tree, all the validation checkers nodes under the
5. Review the Selected Objects pane at the bottom of the window to confirm the
objects on which the validation is run.
6. Click OK.
The system displays a status message to indicate the validation process has
started.
Note If Validation Manager applications are not configured, a message
dialog box appears, and you are instructed to contact your Teamcenter
administrator.
If you have write access to the selected item revision, the system attaches a
validation result summary to the item revision. This summary lists the result of
each specific validation, either Pass or Fail.
Note If you want to run validation under single sign-on mode, you must first
install Security Services and configure it on the rich client and the server.
For directions, see the Security Services Installation/Customization manual.
• NX.5 or earlier version
Configure the TC_BIN\ug_check_part.bat/pl file according to the
comments inside the file before running validation from the client side or
the server side.
• After NX 7.5
If you want to run validation from the client side, no more configuration
is required. Use the standard ug_check_part.bat/pl file under the
TC_BIN directory.
If you want to run validation from the server side, there are two ways to
configure it before running validation:
1. In My Teamcenter, expand the item revision, and open the Validation Results
Summary object to view all the results for the item revision.
3. Click Open.
The log content appears automatically unless there are multiple files under the
validation result log dataset. If so, the system displays the Validation Reports
dialog box.
Note Some validations may not return report files. Also, a report file must
correspond by its file extension to one of the accepted file types defined
by the TC_VALIDATION_FILE_TYPES preference.
4. If there are multiple files under the validation result, select the report file from
the list and click Open.
o The viewer pane contains result filters, a result table, and a collapsible
information area.
o You can add or remove columns from the result table at run time.
When you select a target object from My Teamcenter, you can use four ways to start
the Validation Results Viewer view:
• In any application, right-click an object and choose Send To→Validation Results
Viewer.
The Validation Results Viewer view is displayed for the selected object in
Validation Manager.
• Click the HOME toolbar button in Validation Manager and select an object.
The associated validation results are displayed in the Validation Results Viewer
view.
Note The system does not traverse child BOM lines when you view validation
results from the Structure Manager window. Only selected BOM lines are
listed in the navigator tree in the Validation Results Viewer view. To view
validation results from the entire Structure Manager tree or subtree, expand
the tree in Structure Manager and select all expanded BOM lines.
By default, the Validation Results Viewer view and Selected Workspace Object
view are not shown in Validation Manager perspective. Only when you use these
methods to start the Validation Results Viewer view to see results can the two views
be displayed.
When you select a workspace object or multiple objects from My Teamcenter,
and choose Send To→Validation Results Viewer, it not only opens the Selected
Workspace Objects View, but also opens the Validation Results Viewer. If you
select multiple objects and send them to the Validation Result Viewer view, multiple
Selected Workspace Object Views are opened just like you send multiple objects to
My Teamcenter. The selected folders, items, and revisions are displayed in Selected
Workspace Object View similar to My Teamcenter.
Summary view options include:
Option Description
Agent Displays the validation agent. Results generated from the
selected validation agent are listed in the results table.
Checker Displays validation checker names. Results generated from
selected validation checker (for example, an NX Check-Mate
checker) are listed in the results table.
Target Type Lists the validation target dataset types. Results with selected
validation target dataset type are listed in the results table.
Button Description
Show Sets the display of out-of-date results. Display is enabled by
Out-of-Date default.
Show Sets the display of up-to-date results. Display is enabled by
Up-to-Date default.
Show Not-Run Lists all targets that are not validated against selected validation
checkers.
Show Passed Sets the display of items that pass validation.
Show Failed Sets the display of items that fail validation.
Data Description
Validation Lists the datasets associated with the item revision for which
Target the validations were performed.
Validation Displays the checkers that are run.
Name
Data Description
Validation Lists the validation agent. A check that belongs to this validation
Agent agent is performed against the target object, for example, the
NX Check-Mate agent.
Override Indicates the override status of the validation result: Pending,
Request State Approved, or Rejected.
Validation Date Lists the date and time each validation was performed.
Up-to-date Specifies whether validation was run on the current target object.
Validation Indicates a Pass or Fail result for each validation performed. If
Result the current result is overridden from fail to pass, it shows pass,
and vice versa.
Validation Displays the validation user ID string.
User
Note You can customize the Summary view by modifying the validation result
summary rendering style sheet. For example, a link to a requirement object
can be added and displayed for a selected RDDV result. Click the link and
the requirement objects appear in a window.
For more information about rich client customization, see the Client
Customization Programmer’s Guide.
Note The results table is implemented based on the standard Teamcenter table
tree. You can add or remove columns, sort tables per column, and so on.
For more information about validation rules, see Validation Manager Guide.
The evaluated status descriptions include:
Status Description
Evaluation The validation results pass the rule evaluation.
passes
Result out of The part Last-Modified Date is later than the date that the
date due to validation was performed, and the result was saved into
part changed Teamcenter.
Status Description
Result failed The validation result status fails for a mandatory check.
Parameter The validation passes and is up-to-date, but the parameter
verification verification fails. Parameters listed in the validation rule are
failed verified by first comparing the name and value pairs with the
validation_parameters attribute of validation result object
and then the log file if the first step returned a fail decision.
Result not The validation result is not found. The validation is not performed
found or the result is not saved into Teamcenter.
Missing result The validation result log dataset or file is missing. This failure
log file is checked only when a validation rule contains a parameter
condition.
• VO - Validation Result
Displays all validation results from the specified search criteria.
For more information about generating Report Builder summary and item reports,
see the Report Builder Guide.
Note The Teamcenter administrator must use the Organization application to add
members to the validation administration group and the override approver
role.
• Temporary
The approved override request applies only to the validation result until
the test reruns and validation result updates. The system automatically
removes the approved override request and updates the validation result
after the test reruns.
e. Type a reason for the override request in the Detailed Reason box.
Note In the Create Override dialog box, the Category, Brief Reason,
and Detailed Reason inputs are optional unless Override Reason
Is Mandatory is selected in the New Agent dialog box when the
administrator creates an agent object.
User list or change to a different decision user, notification mails are sent to
the current selected decision user and/or the previous selected decision user.
Note If the company’s best practice is to approve or reject an override
request from the Validation Manager application, specify a user
from the Override Decision User list when creating a request, so
the suggested approver is notified to review the request. On the
other hand, if the company’s best practice is to approve or reject an
override request in a workflow process, leave the Override Decision
User box blank, because the workflow already has a separate
notification mechanism.
3. Click OK.
• The system displays Override Request Status as Pending.
3. Check the Override Request State column for the override status of the
validation result.
• Pending
The override is awaiting review.
• Approved
The reviewers accept the override. The Result column shows the override
result.
• Rejected
One or more of the reviewers deny the request. The Result column shows
the original validation result.
4. View the detail status and provide comments in the Detail Information box.
a. Select one result in the Results Viewer view.
3. Click Yes.
Note Only the original request user can delete an override request.
5. Click OK.
The updated Validation Results Viewer view appears.
• When the override request is rejected, the Override Request State column
indicates the Rejected status, and the Result column displays the original
status.
The signoff team members can now perform the override approval task.
Create a result override approval process and select the signoff team
1. Choose New→Process.
After the select-signoff-team task is complete, the process continues in the workflow
and members of the signoff team receive the signoff task.
2. Choose Actions→Perform.
The system displays the Signoff Decision dialog box.
5. Click OK.
• An e-mail notifying the old approver and the new approver that their
assignments have changed includes this message:
You are no longer the approver of this override request.
• An e-mail notifying the requester that the override request has been approved
includes this message:
Your override request is approved by [Approver].
• An e-mail notifying the requester that the override request has been rejected
includes this message:
Your override request is rejected by [Approver].
• An e-mail notifying the approver and the requester that the override request has
been deleted includes this message:
The override request is deleted.
See comment on the Result Detail panel.
• An e-mail notifying the approver that the override request has been updated
includes this message:
The override request is updated by [Requester].
• VAL-check-validation-result-with-rules
• VAL-set-condition-by-check-validation-result
• The item revision after revise does not display the validation results summary.
There are two methods you can use if you want to copy as object the validation
results summary and the associated validation results when the target dataset
is copied as object.
• Siemens PLM Software recommends that you set the deep copy rule for the
ItemRevision business object to the ValidationMaster Form related object to
CopyAsObject for the TC_Validation relation type.
For more information, see Copy validation results by setting the deep copy rule
for ValidationMaster Form to CopyAsObject.
• An alternative method, which is not recommended, is to set the deep copy rule for
the ValidationMaster Form related object to NoCopy and use the predefined
Copy_Validation_Results extension.
For more information, see Copying validation results by assigning a Business
Modeler IDE predefined extension.
Note You must use one method or the other; you cannot use both.
2. On the ItemRevision tab, add or edit the deep copy rules for the
ValidationMaster Form business object with the following settings:
• The Operation Type is Revise or Save As.
This ensures the validation result summary is not copied as reference but
re-created based on the copied validation results.
For more information about setting deep copy rules, see the Business Modeler IDE
Guide.
1. In the Business Modeler IDE, open the ItemRevision business object, click the
Deep Copy Rules tab, and verify the following settings for the UGMASTER
attached business object.
2. On the Deep Copy Rules tab, verify the following settings for the
ValidationMaster Form attached business object.
For more information about transfer mode context string, defining and using transfer
modes, as well as how to export and import objects, see the PLM XML Export Import
Administration Guide.
• The report files may not appear if environment variables are not defined properly
to display named references.
3. Select the XML extension for the XML Document file type.
4. Click the Advanced button to display the Edit File Type dialog box.
5. Select the open option and click Edit to display the Editing action for type: XML
Document dialog box.
3. Select .xml from the list and click the Change program button.
13 Using workflows
13 Using workflows
Note For ease of use, Siemens PLM Software recommends using My Teamcenter
to initiate and complete workflow processes because the entire procedure
can be accomplished from within your inbox in My Worklist. You can also
initiate workflows from the Workflow Viewer application.
Workflow elements
Workflows pass documents, information, and tasks between participants during the
completion of a particular process. A workflow process can be large and complicated
or simple and straightforward.
Note Certain privileged users can perform administrative actions in a process,
such as removing a user who is no longer with the company. A privileged user
may be the responsible party, the process owner, or a member of a system
administration group. You may be a privileged user in certain processes but
only be able to perform standard user actions in other processes.
• Acknowledge
Contains select-signoff-team and perform-signoffs
tasks. The Decision options are Acknowledged and
Not Acknowledged.
• Route
Contains Review, Acknowledge and Notify tasks.
Interactive tasks Tasks that require user interaction display in the affected
user’s worklists. Different types of tasks have different
interactive requirements. Typical tasks include:
• select-signoff-team
The assigned user is required to select a signoff team to
sign off the target object of the task.
• perform-signoffs
Assigned users are required to review and sign off the
target object of the task.
• Do
The assigned user is required to review and perform
the task instructions, then mark the task complete.
• Notify
The assigned user is required to reply.
Process tasks Tasks that perform noninteractive functions, such as
branching the workflow, specifying query criteria, and error
handling. When you view a workflow using the Process
View, these tasks are displayed. These tasks require no
user interaction, so they do not appear in user worklists.
Parent processes Workflow processes can contain child workflow processes.
In these situations, the initial workflow process is the
parent workflow process, and it contains a subprocess.
Parent workflow processes are dependent upon
subprocesses; they cannot complete until the subprocess
completes.
• To view the progress of tasks in a workflow in which you are not a participant,
use Workflow Viewer.
To view processes in Workflow Viewer, use the Send To command from the
My Teamcenter shortcut menu, from the Search Results view, and from the
Referencers tab.
For more information about viewing workflow processes, see the Workflow Viewer
Guide.
Task states
The actions you can perform on a task are determined by the current task state.
Task states control and coordinate execution of individual tasks in a process. Tasks
are always in one of the defined states described in the table. The symbol associated
with each task is displayed in the upper-left corner of the task box in the process view.
Workflow participants
A process initiator is a user who initiates a workflow process. A responsible party is a
user with a workflow task in an inbox.
• When you initiate a workflow process, you are the process owner. The root task
of the process is placed in your inbox, and you become the responsible party.
• When a task assigned to a user arrives in the user’s inbox, that user becomes
the responsible party.
Whenever any task in the process is not explicitly assigned to another user,
person, or resource pool, Teamcenter defaults responsibility for the task to the
process owner.
• If your inbox contains unviewed tasks, the inbox name is highlighted and the
number of unviewed tasks is displayed.
• Each inbox contains two folders, Tasks to Perform and Tasks to Track.
My Worklist
Gordon, Jack (jgordon) Inbox
Tasks to Perform
000002/A;1–Item2 (perform-signoffs)
000004/A;1–Item4 (Author Technical Recommendation)
Tasks to Track
Note The Tasks to Perform and Tasks to Track folders associated with remote
inboxes cannot be expanded in the tree. To access these folders, click the link
corresponding to the Inbox.
• Black
The task has no duration.
• Green
The task has a duration that has not yet been exceeded.
• Red
The task has a duration that has been exceeded.
When a task is completed, it moves from the Tasks to Perform list to the Tasks
to Track list.
Note • Duration is based on the start date plus time. The duration includes
weekends and holidays and is based on a 7-day week.
• Task names are displayed with the process name first, followed by the task
name in parentheses. In addition, the corresponding tree-node symbol identifies
the task type.
• The names of tasks that have not been viewed are displayed in bold text. This
applies only to tasks that are started or suspended.
• Tasks are not considered to have been viewed by users when they reassign the
task.
• Signoff tasks are not considered to have been viewed by users when they
delegate signoff to another user unless the user is the responsible party, in which
case the task is considered viewed.
My Worklist
Gordon, Jack (jgordon) Inbox
Tasks to Perform
000002/A;1–Item2 (perform-signoffs)
Targets
000002/A;1–Item2
References
Parent Processes
000004/A;1–Item4 (Author Technical Recommendation)
Tasks to Track
Note The Route task contains a Review task, an Acknowledge task, and a Notify
task. The Route task contains both signoff team subtasks.
The Route task also lets you specify the action for each user: Review,
Acknow (for acknowledge), or Notify.
You can select a signoff team either by completing predefined profiles or by ad hoc
selection.
Signoff Team
Profiles Predefined profiles
Engineering/Designer/1
*/Standards Engineer/2
Users Ad hoc selection
Address Lists
The requirements of the selected workflow template determine the method used
to select a signoff team.
• Predefined profiles
An administrator defines profiles and associates them with workflow processes.
When you initiate a workflow process that contains predefined signoff profiles,
you must select the specified number of users for each specified group and role.
For example, a typical workflow can include predefined signoff profiles that
require one user who is a member of the Engineering group and whose role
is Designer, and two users who are members of any group and whose role is
Standards Engineer.
• Ad hoc selection
Ad hoc selection allows the initializing user, address list members, and resource
pool members to add users to the signoff team individually. When the task
template contains predefined signoff profiles, the ad hoc selections make
one-time-only additions to the required signoff team. When the task template
does not contain predefined signoff profiles, the ad hoc additions are the entire
signoff team.
2. (Optional.) If you know you have additional tasks to perform before you can
perform the current task, you can create a subprocess from this task. The
subprocess must complete before the current task can complete.
For more information about creating a subprocess, see What are workflow
subprocesses?.
3. Click the Viewer tab, and then click the Task View option at the top of it.
• Predefined profiles are listed in the Profiles folder.
• The group, role, and user name of the assigned members is displayed for
group/role/#, where # indicates the number of users required on the signoff
team for that particular group and role.
• You can replace group and role with an asterisk (*) to represent all groups
and roles.
7. Repeat the previous steps to assign the required number of users to the selected
signoff team.
Note Quorum requirements are displayed in the Review Quorum pane. You
must select the specified numbers of users for each predefined profile
before you can complete this task.
b. Select the additional users you want to add to the signoff team.
10. Select the Ad-hoc done check box to indicate you have completed your
signoff team member selections.
The task is complete and the Viewer tab now displays No View Data Available.
2. (Optional.) If you know you have additional tasks to perform before you can
perform the current task, you can create a subprocess from this task. The
subprocess must complete before the current task can complete.
For more information about creating a subprocess, see What are workflow
subprocesses?.
The system displays the Signoff Team tree in the left pane of the window.
d. Select a user, then click Add to assign the user to the signoff team.
e. Repeat the previous steps to assign additional users to the signoff team.
c. Click Add.
• The address list appears in the Signoff Team tree.
• The group, role, and user values for each member are listed below the
selected address list.
6. Select the Ad-hoc done check box to indicate you have finished adding
signoff team members.
7. Click Apply.
The task is complete and the Viewer tab now displays No View Data Available.
• The task breakdown tree displays the group/user profiles of the signoff team.
• The Signoff Quorum box displays the number of users who must sign off
to complete the task.
4. Click Close.
• When you are a member of the signoff team, the perform-signoffs subtask
appears in your worklist. Each member of the signoff team is responsible for
reviewing the target object, then indicating a decision.
o For Acknowledge tasks, the decision can be Acknowledged or Not
Acknowledged.
• If your company’s business practices dictate that you must be logged on under
a specific group and role to complete a perform-signoffs task, the system
displays a message and allows you to change your group and role to match the
task requirements.
• When the functionality is enabled, you can see when other users are available
for instant messaging with Microsoft Office Communicator. You can view the
current status of other users on the signoff list, and you can click the Microsoft
Office Communicator symbol to initiate communication.
For information about configuring Teamcenter instant messaging with Microsoft
Office Communicator, see the Application Administration Guide.
2. Click the Viewer tab, and select the Task View option.
The system displays the Perform Signoff pane listing process information.
• Responsible Party
When the Responsible Party entry displays as an active link, you can
reassign the parent task by clicking the link and selecting a new group,
role, and user.
Reassigning the task transfers ownership of the parent task to the selected
user, making that user the Responsible Party for the task. It does not,
however, transfer your signoff responsibility.
• Instructions
When the Instructions link is displayed, there are instructions for the task.
You can view the instructions by clicking the link.
• Attachments
When there are attachments to the workflow process, you can view them by
clicking the Attachments link.
The system displays the Attachments dialog box. Target and reference
attachments are listed beneath the signoff task in the task tree.
• All Comments
If the All Comments entry is present and is as an active link, comments are
written for the task. You can view the comments by clicking the link.
3. (Optional) If you are a privileged user because you are the process owner, the
responsible party, or a member of the administration group, you can delegate
your signoff responsibility for the perform-signoffs subtask to another user.
Note If you are selected to a signoff team based on your inclusion under a
signoff profile, you can only delegate the perform-signoffs subtask
to another user who can match your signoff profile group and role.
Otherwise, you can delegate the perform-signoffs subtask to any other
user.
b. Select a new user from the Group, Role, and User lists.
c. Click OK.
Teamcenter assigns the task to the specified user and the task is placed in
their Tasks to Perform folder.
b. Select an option.
• If perform-signoffs is a subtask of an Acknowledge task, select
Acknowledged or Not Acknowledged.
d. Click OK.
If user authentication is required to complete the task, type your password
in the Password box, and click OK.
Note This authorization is determined by the creator of the process
template. If your site employs Security Services, you must use the
Security Services password rather than your Teamcenter password.
The task is complete and the Viewer tab now displays No View Data Available.
Complete a Do task
2. (Optional.) If you know you have additional tasks to perform before you can
perform the current task, you can create a subprocess from this task. The
subprocess must complete before the current task can complete.
For more information about creating a subprocess, see What are workflow
subprocesses?.
3. Click the Viewer tab and select the Task View option.
7. Click Apply.
The task is complete and the Viewer tab now displays No View Data Available.
• You can complete Condition tasks that are in a pending state. However, this
prevents the task from appearing in the assigned user’s Inbox.
Performing an automatic Condition task while it is pending preempts the query
results, allowing you to override the query and manually set the task to True
or False.
• If you perform a Condition task while it is still in a pending state, you can return
to the task and reset the True/False/Unset setting at any point before the
task reaches a started state.
Note Condition tasks can be configured to proceed automatically during the
workflow process. Such tasks display milestones in the workflow process
but have no associated user actions.
2. (Optional) If you know you have additional tasks to perform before you can
perform the current task, you can create a subprocess from this task. The
subprocess must complete before the current task can complete.
For more information about creating a subprocess, see What are workflow
subprocesses?.
3. Click the Viewer tab and select the Task View option.
4. Complete the task according to the instructions in the Task Instructions box.
5. Set the Task Result to True or False, based on the requirements listed in
the Instructions box. This setting determines whether the workflow process
continues along the true or false branch from the Condition task.
Setting the condition path to Unset prevents the task from completing and
pauses the workflow process.
Note An Unable to Complete check box is displayed when a failure path is
defined for the Condition task. Select the Unable to Complete check
box to proceed to the failure path.
Note If your site employs Security Services, you must use the Security
Services password rather than your Teamcenter password.
The task is complete and the Viewer tab now displays No View Data Available.
2. Click the Viewer tab and select the Task View option.
Note The selected custom task varies depending on the form and other tasks
in the process.
3. Complete the steps listed in the dialog box, following instructions provided by
the system administrator.
Click the button provided to complete the task and close the dialog box.
The task is complete and the Viewer tab now displays No View Data Available.
b. Click the Viewer tab, and then choose the Task View option at the top of
the Viewer pane.
d. Select a group, role, and user to whom the task will be assigned.
f. Click Add.
The system displays the user information and action assigned to that user
beneath the task node in the process tree.
g. Click Modify to change the group, role, or user definition for a particular
user or to modify the user action.
2. Display the members of an entire address list and assign individual review,
acknowledge, and notify responsibilities:
a. Select the route task in your Tasks to Perform folder.
b. Click the Viewer tab, and select the Task View option at the top of the Viewer
pane.
c. Select the Address Lists option to display the Address Lists list.
f. Click Add.
The system displays the address list in the Signoff Team tree.
3. (Optional) Modify or set the quorum value for Review and Acknowledge tasks
in the Rev Quorum and Acknow Quorum boxes.
4. Select the Ad-hoc done check box to indicate you have completed the task
assignments.
5. Click Apply.
The task is complete and the Viewer tab now displays No View Data Available.
For more information about setting permissions, see the Access Manager Guide.
For more information about the EPM-set-rule-based-protection workflow handler,
see the Workflow Designer Guide.
2. Choose Actions→Promote.
The Promote Action Comments dialog box appears.
4. If the task is a Review or Route task and it has a reject path, click either the
Approve or Reject decision to determine the path you want the workflow process
to follow.
This helps you to expedite the review process where you want to move the
workflow process along despite rejections.
5. Click OK.
The selected task moves to the Skipped state and the next task in the process is
started. The comments you entered are listed in the audit file.
• Demoting a Review task voids any signoff decisions that have been
made.
2. Choose Actions→Undo.
The system displays the Demote Action Comments dialog box.
3. Type your comments in the box. These comments appear in the audit file.
2. Choose Actions→Start.
The system displays the Start Action Comments dialog box.
3. Type your comments in the box. These comments appear in the audit file.
Suspend a task
1. Select the task you want to suspend.
Note Suspended tasks stop a process from moving forward.
2. Choose Actions→Suspend.
The system displays the Suspend Action Comments dialog box.
3. Type your comments in the box. These comments appear in the audit file.
Resume a task
1. Select the desired suspended task.
Note Resuming a suspended task restores it to the state it was in prior to
being suspended.
2. Choose Actions→Resume.
The system displays the Resume Action Comments dialog box.
4. Click OK to move the task to the state that it was in prior to being suspended.
Note If a task is designated to process in the background, the move to the
prior state might be delayed.
Abort a task
1. Select the task you want to cancel and choose Actions→Abort.
Note Aborting cancels a task without attempting to complete it.
• The Responsible Party box displays the responsible party for the selected
task.
This box cannot be modified.
• The Named ACL box displays the named ACL assigned to this task (if any).
This box cannot be modified from this dialog box, although you can open the
Named ACL dialog box for reference.
For more information about named ACLs and Access Manager best practices,
see the Access Manager Guide.
• For Review and Acknowledge tasks, the Signoffs Quorum box displays the
number of users who must approve the Signoff task to reach a quorum, the
recipients, and other information such as the due date and duration.
You can set Recipients in this dialog box, but you cannot set or modify other
values, including the quorum value. The quorum value is set when the
workflow process is initiated.
• If a Condition task is selected, the Condition Result box displays the result
of the query, either True or False. If a query has not yet been defined, the
result is listed as unset.
5. Click Close.
3. Click the Attachments Panel tab at the bottom of the dialog box.
The system displays the Attachments pane with a tree listing of all target
attachments and references.
4. Click Expand All Folders or Collapse All Folders to view the contents of the
Handler tree.
7. Click Close.
• The initiator of the process uses this framework to assign to other users the
responsibility of signing off tasks.
• A process template can include workflow handlers that automate some or all of
the assignments.
For more information about workflow handlers, see the Workflow Designer Guide.
4. Click the Process Template list to view process templates and make a selection.
• To view only those process templates assigned to your group, select the
Assigned option.
Note The CR_allow_alternate_procedures preference determines whether
this property is displayed and whether you can select alternate workflow
processes from the New Process Dialog dialog box using the Process
Template Filter list.
6. Click the Attachments tab to view or assign target and reference attachments.
It is not necessary to assign target data at the initiation of a process.
7. Click the Process Template tab to view the process template selected as the
basis of the new process.
B. Use the Resource Pool Options criteria and search capabilities to select
the responsible party.
D. Repeat the previous steps to assign a responsible party for other tasks
in the process.
• Profiles limit the pool of users that can be assigned to the task.
The system displays the Profiles node when user profiles were
defined as part of the process template.
e. (Optional) Modify or set the quorum value for Review and Acknowledge
tasks in the Rev Quorum and Acknow Quorum boxes.
1. Select the objects in other sources that you want to add to the paste list. For
example, objects displayed as the result of a search or those displayed in an
open rich client application.
2. Select either the Targets or References folder on the Attachments tab of the
New Process dialog box.
3. Click Advanced Paste, located at the bottom of the New Process dialog box.
The system displays the Advanced Paste dialog box.
4. Select one or more of the following options in the Advanced Paste dialog box:
• From Prior Search
Displays all open search results that are open in your session in which you
have selected objects. You can select one or more searches from the list.
• From Referencers
Displays a list of My Teamcenter objects, such as prior searches and the
Home folder. You can select one or more objects from the list.
• From PSE
Displays open BOM windows.
c. Click GO to collect the elements and add them to the paste list.
• From Application
Displays the active applications in your session.
Select an application to add all objects currently selected in that application
window to the paste list.
The system displays a check mark to the left of the source button to indicate that
objects from that source have been added to the paste list.
5. Click OK.
The system pastes the object references into the selected attachment folder.
Generally, any user can create a workflow subprocess from a task within their
worklist. This functionality is not limited to privileged users.
Note Access to create workflow subprocesses is governed by the Access Manager
Has Class (Task) rule and the Task Named access control list (ACL).
The same permissions allowing you to perform the task allows to create
a subprocess from the task.
When you create a workflow subprocess from an in-process task in your worklist, you
create a dependency between the selected task in the parent process and the newly
created subprocess. The targets of the active parent workflow process are carried
over if you check the Inherit Targets box.
6. Click the Process Template list to view available workflow process templates
and make a selection.
Your selection determines the workflow that will be initiated as a workflow
subprocess.
7. (Optional) Select the Inherit Targets check box if you want the new workflow
subprocess to include all the targets of the parent workflow process.
8. (Optional) Click the Attachments tab to view or assign target and reference
attachments.
9. (Optional) Click the Process Template tab to view the process template selected
as the basis of the new process.
c. Assign users:
A. Expand the task node in the tree to begin to assign the responsibility
of performing each task to users.
If the selected task requires users, or users of a specific/group role
profile, to perform the task, the Users node or Profiles node appears
under the task.
B. Select the task, or if available, the Users or Profiles node within the task.
E. The action that the selected users are responsible for display next to
the Action option.
The action list is based on the task type. 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.
F. Click Add.
The system displays the user information and action assigned to that
user beneath the task node in the process tree.
Teamcenter applies the assignment list to the tasks in the process. Users are
displayed as nodes in the process tree, and the action assigned to the user is
displayed to the right of the tree under the Actions heading.
Note The select-signoff-team and perform-signoffs subtasks associated with
Route, Review, and Acknowledge tasks are not displayed in the tree.
b. Use the Group, Role, and User lists to select the responsible party.
d. Repeat the previous steps to assign a responsible party for other tasks in
the process.
• The Profiles node, displayed when user profiles are defined as part of the
process template, lets you limit the pool of users that can be assigned
to the task.
g. (Optional) Modify or set the quorum value for Review and Acknowledge
tasks in the Rev Quorum and Acknow Quorum boxes.
6. (Optional) To save modifications to the process assignment list, select the Save
Modifications Back to List check box.
Note You can only save modifications to personal process assignment lists.
Shared lists can be modified, but the changes cannot be saved.
7. Click Assign.
Teamcenter sends the tasks to the Tasks to Perform folders of the assignees.
Claim a task
You can claim a task from a resource pool or another user whose worklist you have
access to. This reassigns the task to you and makes you the responsible party. This
is a simpler way of reassigning a task to yourself using the Assign action.
1. Click My Worklist.
2. Click the task you want to claim from either a resource pool you are subscribed
to or another user’s worklist that you have access to.
5. In the Claim Perform Signoff dialog box, select the user you want to claim the
task from and click Claim.
If the Claim button is not active after selecting a user, you cannot claim the
task from that user.
The task appears in your worklist, and you become the responsible party for the task.
Reassign a task
If you are the responsible party or a privileged user, you can reassign any task that
has not already been started.
For example, if you are the initiator of a process, the tasks of selecting a signoff
team and performing signoffs are automatically assigned to you. You may want to
reassign one or both of these tasks to another user.
Note • You can only reassign a task to another user who meets the group and
role criteria defined for the selected task.
• If you want to reassign the task to yourself, use the Claim Task menu
command instead.
For more information about claiming tasks, see Claim a task.
2. Choose Actions→Assign.
The Assign Responsible Party dialog box appears.
3. If the Responsible Party entry contains a link, you can reassign the responsible
party for this signoff task. Reassign the responsible party by clicking the link
next to this entry.
The Assign Responsible Party dialog box appears. The Organization and
Project Teams lists display the available groups, roles, and users to which you
can reassign the task.
4. Select the desired group, role, or user. You can only reassign the selected task to
a user who meets the group and role criteria required by the task.
b. Select individual tasks to be reassigned, or click the Select All the Tasks
button to select all displayed tasks.
Note Click the Clear the Selection button to clear selections you have
made in the tree.
6. Click OK or click Cancel at any time to cancel the operation without making
changes to the database.
2. Choose Actions→Assign.
The system displays the Assign Responsible Party dialog box.
3. Use the Organization or Project Teams tab to select the responsible party.
Note You can only reassign tasks to a user who meets the group and role
criteria specified for the task.
b. Select individual tasks to be reassigned, or click the Select All the Tasks
button to select all displayed tasks.
Note Click the Clear the Selection button to clear selections you have
made in the tree.
• When a task is reassigned to a user other than the process owner, the process
owner and the responsible party are different users.
The user who initiates the workflow process must select a signoff team. As the
process progresses, a select-signoff-team task appears in the Tasks to Perform
folder of the process initiator’s Inbox each time a task requiring a signoff team
reaches a Started state.
Tasks that require signoff teams include:
• Review tasks
• Acknowledge tasks
• Route tasks
When you are assigned a select-signoff-team task, you select users as signoff team
members who are assigned the responsibility of signing off a target object, such as
a document.
• You can assign signoff responsibility to an entire address list or resource pool
of users, as well as individual users.
• You can select a signoff team in the Task Hierarchy tree and the Task Flow pane.
A green light in the upper left hand corner of the task node indicates that a signoff
team has been assigned.
• When a role under a group is selected with Any Member or with All
Members, choose Specific Group or Any Group.
5. Click OK.
For more information about task state symbols and descriptions, see Task states.
To use Workflow Viewer to view the progress of tasks in a workflow in which you are
not a participant, use the Send To→Workflow Viewer shortcut menu command from
the Search Results view, the Referencers tab, or My Teamcenter.
For more information about viewing workflow processes, see the Workflow Viewer
Guide.
• To view the current task, rather than the entire process, you can select the Task
View option.
• Private lists can be created by any user and are only visible to that user.
4. (Optional) Select the Create Shared List check box. This option is only available
to members of the DBA group and to group administrators.
b. Use the Group, Role, and User lists to select the responsible party.
d. Repeat the previous steps to assign a responsible party for other tasks in
the process.
Assign users:
a. Expand the task node in the tree to begin to assign users to review,
acknowledge, or receive notification of a task.
The system displays the Users node and the Profiles node.
The Users node allows you to assign resources using an ad hoc selection
process.
Profiles limit the pool of users that can be assigned to the task.
The system displays the Profiles node when user profiles were defined as
part of the process template.
g. (Optional) Modify or set the quorum value for Review and Acknowledge
tasks in the Rev Quorum and Acknow Quorum boxes.
7. Click Create.
The system displays the process assignment list in your My Lists folder.
2. Select a list from the My Lists folder. If you are a group administrator you can
modify lists contained in the My Group Lists folder, as well as those contained
in the My Lists folder. If you are a member of a DBA group, you can modify
lists contained in any of the folders.
c. Use the Group, Role, and User lists to select the responsible party.
e. Repeat the previous steps to assign a responsible party for other tasks in
the process.
The Users node allows you to assign resources using an ad hoc selection
process.
Profiles limit the pool of users that can be assigned to the task.
The system displays the Profiles node when user profiles are defined as
part of the process template.
g. (Optional) Modify or set the quorum value for Review and Acknowledge
tasks in the Rev Quorum and Acknow Quorum boxes.
2. Select the old group member from the organization tree by clicking the button to
the right of the Old Group Member box.
The system displays the Select Group Member dialog box.
4. Select the new group member by clicking the button to the right of the New
Group Member box.
The system displays the Select Group Member dialog box.
6. Click Next.
The system displays all process assignment lists that include the user designated
as the old group member.
7. Select the lists in the Lists Found section and click Add (+) to move the lists
to the Selected Lists section.
Teamcenter replaces the user in these lists.
8. Click Finish.
The system displays the Replace Success dialog box.
You can use Import and Export options in the Create/Edit Assignment List dialog
box to import and export process assignment lists (PALs) in PLM XML format.
• Exporting a process assignment list also exports its associated workflow
template.
o When the Overwrite Duplicate Assignment Lists check box is not selected, a
PAL with the same name as one at the importing site is not imported.
o When the Overwrite Duplicate Assignment Lists check box is selected, and
you import a PAL that has the same name as one at the importing site:
The PAL successfully overwrites the one at the importing site if at least
one resource is assigned to the PAL and a workflow template with the
same origin_id property exists at the importing site.
Note • Duration is based on the start date plus time. The duration includes
weekends and holidays, and is based on a 7-day week. For times
exceeding a single week, you should include the nonwork days in the
duration time.
1. From your inbox in My Worklist, select a task in the Tasks to Track or Tasks
to Perform folder.
5. Enter integer values in one or more of the following boxes to specify the duration:
• Years
• Weeks
• Days
• Hours
• Minutes
After you set a duration for the task, you must create a list of recipients to
receive late notices by Teamcenter mail if the task becomes overdue. You can
specify individual users or assign multiple users to the task using address lists.
6. Define the recipient list by typing a comma-separated list of user names in the
Recipients box in the Task Properties dialog box or as follows:
a. Click Set to the right of the Recipients box.
The system displays the Select Recipients dialog box.
b. Locate a user, group, or address list by entering the name, or a partial name
and wildcard character, in the Search box and clicking the User, Group, or
Address list button. You can display all users, groups, or address lists by
entering an asterisk (*) in the Search box.
The system displays the search results in the area beneath the Search box.
c. Select the users, groups, or address list from the results and click To.
d. Click OK to accept the recipient list and exit the Select Recipients dialog box.
The system displays the names of the recipients in the Recipients box of the
Task Properties dialog box.
1. From your inbox in My Worklist, select a task in the Tasks to Track or Tasks
to Perform folder.
b. Select the month in which the task becomes due. Click the right-arrow
button to move forward in the calendar. Click the left-arrow button to move
backward in the calendar.
d. Type the hour and minute by which the task must be completed in the h and
m boxes. Use the 24-hour clock format; for example, type 1:30 p.m. as h: 13
m: 30. If you do not specify another time or clear the boxes, the current
time is entered. If you clear the boxes, the time is set to 0 and no required
completion time is set for the task.
e. Click OK to accept the due date and time and close the calendar.
You have set a due date for the task. Next, you must create a list of recipients
to receive late notices by Teamcenter mail if the task is not performed by the
due date. You can specify individual users or assign multiple users to the task
using address lists.
4. Define the recipient list by typing a comma-separated list of user names in the
Recipients box in the Task Properties dialog box or as follows:
a. Click Set to the right of the Recipients box.
The system displays the Select Recipients dialog box.
b. Locate a user, group, or address list by entering the name, or a partial name
and wildcard character, in the Search box and clicking the User, Group, or
Address list button. You can display all users, groups, or address lists by
entering an asterisk (*) in the Search box.
The system displays the search results in the area beneath the Search box.
c. Select the users, groups, or address list from the results and click To.
d. Click OK to accept the recipient list and exit the Select Recipients dialog box.
The system displays the names of the recipients in the Recipients box of the
Task Properties dialog box.
• In the Impact Analysis view, select the workflow task, and then click Delete.
Note Deleting a task in the workflow, deletes the entire workflow process.
• Work contexts are created from a combination of user name, group, role, and
project; however, it is not necessary to include all four of these elements in the
definition of a work context.
o If task can be performed by anyone, regardless of their group and role, the
work context specifies only the project to which the context applies.
o If a task can be performed only by a user with a specific role within a group,
the work context definition specifies the project, group, and role, but not a
specific user.
5. Select any combination of group, role, user, and project from the lists.
6. (Optional) Select the Subgroup Members Allowed check box. When this option
is selected in addition to specifying a group for the work context, Teamcenter
allows members of subgroups of the specified group to perform the task.
7. (Optional) Select the User Setting Modifiable check box. When this option is
selected, users can modify the user settings associated with this work context.
Note The default setting for this option is controlled by the
TC_wc_setting_modifiable_default preference.
For more information, see the Preferences and Environment Variables
Reference.
8. Click OK.
3. Find the work context by typing its name or partial name and wildcard in the
Name box and click Find.
The system displays the first page of work contexts that match the search
criteria. Click the right-arrow or left-arrow buttons to load the next or previous
page of results.
4. Select the work context from the list and click Apply or OK.
Teamcenter assigns the work context to the selected item, item revision, or
workflow task.
Note In addition to using this method, you can assign a work context to an
object by selecting the work context object in a tree or table, copying to
the clipboard, and pasting to another object.
Note Work contexts that are not referenced by another object can be deleted from
the database.
• All users can subscribe to resource pool inboxes; however, they can only perform
tasks if they are valid members of the group or are assigned the appropriate role.
Note Administrators can use the
EPM_resource_pool_restrict_subscription preference to restrict
users to subscribe only to resource pools belonging to groups and roles in
which the user is a member.
For more information about this preference, see the Preferences and
Environment Variables Reference.
• Tasks assigned to a resource pool appear in the Tasks to Perform folder and the
Tasks to Track folder of the appropriate resource pool inbox. Any member of the
resource pool can then accept responsibility and perform the task. All members
of a group, role, or role-in-group can take ownership of the assignment. The
assignment is delivered to the Tasks to Perform folder for all members.
2. Define the group and role for the resource pool worklist:
a. Click Accessible to list the groups and roles to which you belong. As a
member of the resource pool’s defined group and role, you are able to access
and perform tasks assigned to the resource pool.
b. Click All to list all groups and roles. If you are not a member of the resource
pool’s defined group and role, you are not able to access and perform tasks
assigned to the resource pool.
c. Select the group and role you want assigned to the resource pool.
5. Click Unsubscribe a Resource Pool (x) to remove a resource pool from the
My Worklist tree.
6. Click Cancel at any time to close the dialog box without making changes to
the database.
• Multiple surrogate users can be defined for a single task; however, only a single
user can be the active surrogate for the task at any given time.
• Surrogate users are automatically granted all access privileges afforded to the
original responsible party or approver.
o Any user can be designated as a surrogate, but only a user who belongs to
the group and role specified by the task profile can perform a task.
o Any user can take responsibility for a task, even if that user does not match
the group and role profile of the task.
Note You cannot define special access control lists (ACLs) for a surrogate user.
• Group administrators can define surrogates for any user within their group.
If you do not have administrative privileges, you can only define surrogates for
your own tasks.
3. Select the group, role, and user for whom you are defining surrogates.
The dialog box displays surrogates for the selected user in the Current Surrogate
User(s) list.
Note You can choose all roles within a group by selecting the asterisk (*)
rather than selecting a specific role.
5. Set the Surrogate Effective Dates effectivity start date for the surrogate user as
follows:
a. Click the calendar button in the From box to open the popup calendar.
b. Select the month in which the surrogate user becomes effective. Click the
back arrow to scroll to the previous month or click the forward arrow to
scroll to the next month.
d. Select the day the surrogate user becomes effective by clicking the
appropriate square on the calendar.
e. Type the hour, minute, and second at which the surrogate user’s effectivity
begins in the h, m, and s boxes.
Use the 24-hour clock format; for example, type 1:30 p.m. as 13 h, 30 m,
and 00 s.
If you do not specify another time or clear the boxes, the current time is
entered.
f. Click OK to accept the effectivity start date and time and close the calendar.
6. Set the Surrogate Effective Dates effectivity end date for the surrogate user:
a. Click the calendar button in the To box to open the popup calendar.
d. Select the day the surrogate user’s effectivity ends by clicking the appropriate
square on the calendar.
e. Type the hour, minute, and second at which the surrogate user’s effectivity
ends in the h, m, and s boxes.
Use the 24-hour clock format; for example, type 1:30 p.m. as 13 h, 30 m,
and 00 s.
If you do not specify another time or clear the boxes, the current time is
entered.
f. Click OK to accept the effectivity end date and time and close the calendar.
Tip To allow the surrogate user to be effective indefinitely, leave the end
date unset. To reset the effectivity dates, click Reset.
7. Click Add.
The system displays the surrogate user in the Current Surrogate Users list,
the surrogate user is notified via e-mail, and a link is created in the surrogate
user’s inbox.
The link in the surrogate user’s inbox allows the surrogate user to access the
inbox of the user for whom they are acting surrogate.
4. Set the Surrogate Effective Dates effectivity start date for the surrogate user:
a. Click the calendar button in the From box to open the popup calendar.
b. Select the month in which the surrogate user becomes effective. Click the
back arrow to scroll to the previous month or click the forward arrow to
scroll to the next month.
c. Select the year in which the surrogate user becomes effective. Click the
back arrow to scroll to the previous year or click the forward arrow to scroll
to the next year.
d. Select the day the surrogate user becomes effective by clicking the
appropriate square on the calendar.
e. Type the hour, minute, and second at which the surrogate user’s effectivity
begins in the h, m, and s boxes.
Use the 24-hour clock format; for example, type 1:30 p.m. as 13 h, 30 m,
and 00 s.
If you do not specify another time or clear the boxes, the current time is
entered.
f. Click OK to accept the effectivity start date and time and close the calendar.
5. Set the Surrogate Effective Dates effectivity end date for the surrogate user:
You have set the effectivity start date for the surrogate user. Now you must set
the effectivity end date.
a. Click the calendar button in the To box to open the popup calendar.
b. Select the month in which the surrogate user’s effectivity ends. Click the
back arrow to scroll to the previous month or click the forward arrow to
scroll to the next month.
c. Select the year in which the surrogate user’s effectivity ends. Click the
back arrow to scroll to the previous year or click the forward arrow to scroll
to the next year.
d. Select the day the surrogate user’s effectivity ends by clicking the appropriate
square on the calendar.
e. Type the hour, minute, and second at which the surrogate user’s effectivity
ends in the h, m, and s boxes.
Use the 24-hour clock format; for example, type 1:30 p.m. as 13 h, 30 m,
and 00 s.
If you do not specify another time or clear the boxes, the current time is
entered.
f. Click OK to accept the effectivity end date and time and close the calendar.
Tip To allow the surrogate user to be effective indefinitely, leave the end
date unset. To reset the effectivity dates, click Reset.
6. Click Add.
The system displays the surrogate user in the Current Surrogate Users list.
In addition, a link is created in the surrogate user’s inbox. This link allows
them to access the inbox of the user for whom they are acting surrogate. The
surrogate user is notified via e-mail.
3. Select the user to be removed from the Current Surrogate Users list.
4. Click Remove.
1. From your worklist, click the link corresponding to the worklist of the user for
whom you will act as a surrogate.
3. Choose Actions→Stand-In.
The system displays the task name, responsible party, and surrogate user in the
Surrogate Actions dialog box.
• Stand-In
Allows you to perform the task while allowing the original user to retain
control.
• Release
Releases the active surrogate from the task. At this point, the active
surrogate cannot perform the task without first reclaiming it.
When you select the Release to Responsible Party option, the checkout on
the target object is transferred from the active surrogate to the responsible
party (original user), and the system releases the checkout status from the
surrogate user and reassigns it to the original user.
• Transfer Check-Out(s)
Transfers checkout of the target objects from the original user to the active
surrogate when you select the Stand-In option.
5. Click OK.
Teamcenter designates the user as the active surrogate and grants the surrogate
all privileges assigned to the original user. The system indicates that there is
an active surrogate for the task by displaying the surrogate task symbol in
the task display.
• Group administrators can modify Out of Office Assistant settings for members
of their group.
For more information about resource pools, see Using resource pools.
Note • The Out of Office Assistant menu command is available only when My
Worklist is selected.
• The Out of Office Assistant does not reassign existing tasks in your
inbox. These tasks must be manually reassigned using the Assign
command on the Actions menu.
• If you clear both the start and end dates (in other words, set them to
null), the Out of Office Assistant is turned off.
2. Select the user, group, and role for whom these settings apply. You must be an
administrator to change another user’s out of office status.
3. Set the Out of Office Dates absence beginning date and time by performing
the following steps:
a. Click the calendar button next to the From box to open the calendar. The
calendar initially shows the current day, month, and year.
b. Select the month in which your absence begins. Click the right-arrow
button to move forward in the calendar. Click the left-arrow button to move
backward in the calendar.
d. Type the hour, minute, and second at which your absence begins in the h,
m, and s boxes.
Use the 24-hour clock format; for example, type 1:30 p.m. as 13 h, 30 m,
and 00 s.
e. Click OK to accept the date and time and close the calendar.
4. Set the Out of Office Dates absence ending date and time by performing the
following steps:
a. Click the calendar button next to the To box to open the popup calendar. The
calendar initially shows the current day, month, and year.
b. Select the month in which your absence ends. Click the right-arrow button to
move forward in the calendar. Click the left-arrow button to move backward
in the calendar.
d. Type the hour, minute, and second at which your absence ends in the h,
m, and s boxes.
Use the 24-hour clock format; for example, type 1:30 p.m. as 13 h, 30 m,
and 00 s.
Note If you are unsure of your return date, leave the date blank. Your
assigned tasks are forwarded until you reset your status.
e. Click OK to accept the date and time and close the calendar.
Note If you clear both the start and end dates (in other words, set them to
null), the Out of Office Assistant is turned off.
5. Set the New Task Recipient by selecting the group, role and user name of the
person to whom the assigned tasks will be forwarded. If the system indicates the
selected person is out of office, that person cannot be selected as a recipient.
6. Click OK.
o System Requirements
o Configuration Overview
• Chapter 6, Troubleshooting.
Remote inboxes let you interact with workflow tasks that originated at remote sites.
• When you have a user account at a remote site, you can subscribe to that site
to access your inbox, called your remote inbox, and access tasks assigned to
you at the remote site.
• After you subscribe to your inbox at a remote site, your local site worklist
displays a remote site link you can use to launch a client to let you access the
remote site inbox.
Note The remote site link also shows the number of tasks in your worklist at
the remote site.
• Remote site links in the local site worklist cannot be expanded in the local tree
display.
• When you click the link to the remote site, Teamcenter launches a full, separate
Teamcenter session to display the remote inbox.
Note The remote site link launches the client specified by the
TC_external_default_launch_ui setting.
o thin
Displays the remote site in the thin client.
This is the default setting.
o rich
Displays the remote site in the rich client.
o dynamic
Displays the remote site in the same type of client used to access
the link to the remote site.
• Sites with remote inboxes to which you are already subscribed are listed
as Selected Inboxes.
• Sites with remote inboxes to which you are not already subscribed are listed
as Available Inboxes.
3. When the subscriptions are listed correctly, click OK or Apply, and the system
displays the Subscribe Remote Inbox dialog box. This dialog box shows the
progress of each subscription request.
o When you have completed the data modification, use the standard Check-In
option at the local site to undo the checkout at the remote site, move the
modified data to the remote site.
This checks in the data at the remote site.
• Remote Export lets you access read-only replicas of data. If necessary, you can
also use this command to transfer site ownership of the data required to perform
your tasks.
2. Select the object to check out from the remote site, and choose Tools→Multi-Site
Collaboration→Send→Remote Checkout.
The system displays the Remote Checkout dialog box.
• Comments
Type the reason for the checkout request.
• Target Site
From the list of available sites, choose the site to which the object should
be sent.
Click Home on the right side of the Target Site box to choose sites from the
list.
• OK to remote checkout?
Displays the status of objects being remotely checked out.
4. Click Yes.
The system displays the current options in the Remote Checkout Options
Settings dialog box.
2. In the remote site client, select the object to export as a read-only replica.
• Target Sites
From the list of available sites, select the site to which the object should
be sent.
Click Home to the right of the Target Site box to select sites from the list.
• OK to remote export?
Displays the status of objects being remotely exported.
5. Click Yes.
The system displays the current options in the Remote Export Options Settings
dialog box.
• System messages
• Buttons
For information about working with properties files, see the Client Customization
Programmer’s Guide.
• If there is no audit data for the business object, the view displays a No process
history data available for selected object. message.
• If the selected object has passed through more than one workflow process, you
can choose which process to display from the list to the right of the tab.
In the Process History view, you can review the progress of a workflow or schedule
and do the following:
• Determine the progress of an object in a schedule or workflow and who has
responsibility for the object.
3. (Optional) Click the Move Up and Move Down buttons, to the right of
the Displayed Columns list, to adjust the order of the displayed columns.
4. Click Apply to apply the configuration to the current view, or click Save to save
the configuration for later use.
Note You can use the Apply Column Configuration command on the view
menu to:
• Apply a saved configuration.
You can use the Save Column Configuration command on the view
menu to save the current configuration of the table display.
Process reports
The following audit reports are available when you choose the
Tools®Reports®Report Builder Reports menu command in My Teamcenter:
• Audit - Workflow Attachment Report
Displays all attachment object details for the specified workflow process.
• WF - Filtered Audit
Displays the start, complete, approve, and rejected actions for the specified
workflow process. For more detailed information about this set of actions,
including group and role of the performer and assignee information, use Audit
-Workflow Summary Report.
• WF - Items In Process
Displays the items currently in a workflow process and where they are in their
respective processes.
• WF - Objects In Process
Displays the objects currently in a workflow process and where they are in their
respective processes.
• WF - Signoffs
Displays the signoff results and comments for the specified object in a workflow
process. For more detailed information, use Audit - Workflow Signoff Report.
• WF - Unfiltered Audit
Displays all actions and their statuses for the specified workflow process. For
more detailed information about this set of actions, including group and role of
the performer and assignee information, use Audit - Workflow Detailed Report.
• For an interactive live Excel file that is connected to Teamcenter, select Live
integration with Excel (Interactive).
• For a live Excel file that is not connected to Teamcenter, select Live
integration with Excel (Bulk Mode).
You can accumulate changes and later connect the file to Teamcenter.
• To export the data to an Excel file that also contains import processing
information on a separate sheet, select Work Offline and Import.
• To check out objects while exporting to live Excel, select Check out objects
before export.
Note The checkout applies to all objects being exported. Use this option
carefully if you are exporting a large number of rows.
The export file is generated and the URL Generated message is displayed,
confirming that the URL is in your Windows Clipboard and showing the URL
details.
o ADA License
o Structure Manager
o Multi-Structure Manager
o Schedule Manager
o Workflow Viewer
o Organization
For more information, see View audit logs in the Summary view.
• Run predefined audit reports or create new reports, using the Report Builder
application.
For more information, see My Teamcenter Guide.
o ADA License
o Structure Manager
o Multi-Structure Manager
o Schedule Manager
o Workflow Viewer
o Organization
Legacy audit information is only accessible from a button in the Audit Logs tab in
the Summary view when a legacy audit file is present.
The audit logs are grouped in the Summary view as follows:
Process reports
The following audit reports are available when you choose the
Tools®Reports®Report Builder Reports menu command in My Teamcenter:
• Audit - Workflow Attachment Report
Displays all attachment object details for the specified workflow process.
• WF - Filtered Audit
Displays the start, complete, approve, and rejected actions for the specified
workflow process. For more detailed information about this set of actions,
including group and role of the performer and assignee information, use Audit
-Workflow Summary Report.
• WF - Items In Process
Displays the items currently in a workflow process and where they are in their
respective processes.
• WF - Objects In Process
Displays the objects currently in a workflow process and where they are in their
respective processes.
• WF - Signoffs
Displays the signoff results and comments for the specified object in a workflow
process. For more detailed information, use Audit - Workflow Signoff Report.
• WF - Unfiltered Audit
Displays all actions and their statuses for the specified workflow process. For
more detailed information about this set of actions, including group and role of
the performer and assignee information, use Audit - Workflow Detailed Report.
Microsoft Excel opens a temporary file. You can create a permanent file by choosing
File→Save As in Excel to display the Save As dialog box.
If you save a live Excel file, you can open it later in My Teamcenter to reconnect
it to the database.
Note Values that you cannot change in Teamcenter are unavailable in the cells
of the live Excel file.
The export to Excel option is not available on UNIX clients.
• If you select an object, the object ID, name, revision, and object type are
displayed in the Search Criteria section.
• To select a project, select a project you have access to from the Project list.
• If you want to search for a different object, click the Clear button to clear
the existing search criteria and then type the object ID, name, and revision
in the Audit Log dialog box.
3. (Optional) Specify additional search criteria, such as event type, user ID, and
date created.
4. (Optional) Click the Advanced tab and type criteria to construct a query based
on property values.
Note The Advanced tab does not display any information if there are no
logged properties in the audit definition object.
c. Select the properties for which you require audit logs from the Available
Properties list, and click the button to move the property to the Selected
Search Criteria list.
Note You can add up to 20 properties in the Selected Search Criteria list.
d. To search for properties based on old or new values, in the Selected Search
Criteria list, enter the old value in the Old Value column and the new value
in the New Value column.
e. Click Find.
Audit logs that match your selected criteria appear.
5. Click Find.
The system displays the audit logs that match the search criteria.
Property value changes are shown in the User Data column of the audit log. The
User Data column shows the property name, the old value of the property, and
the new value of the property.
The old value of the property is the same as the new value of the property if
the property value does not change.
Note Only persistent properties of objects are tracked. Run-time, compound,
and relational properties are not tracked by Audit Manager.
• For any selected item assigned to a project, the hierarchy can be followed up to
the top-level folder and can be expanded to display lower levels of the hierarchy,
as configured by the project administrator.
• Project data filtering can also be applied in the absence of a project smart folder
hierarchy. You can filter project data based on object type.
For information about defining projects, see the Project and Program Guide.
Note When an administrator sets the program security attribute to true on
a project, the project is considered to be a program and is subject to
program-level access rules.
Programs offer all the basic features of projects, but in addition you can:
• Control access to program data at a higher level than typically applied
to project data.
Privileged Team
Team Administrator Team Members
Members
Gordon, Jack Jones, Paul Franklin, Wendy
Belcher, Sarah Tracey, Don
Smith, William
The My Projects view is similar to My Teamcenter views but with the following
differences:
• Project Smart Folder Hierarchy
Displays the smart folder hierarchy as configured by the administrator, and
provides a filter button to display the Apply filters dialog box.
Note The Apply filters dialog box lets you apply filtering based on source
types, properties, and values.
You select a project from the hierarchy to display information in the other My
Projects panes.
• Summary
The summary view consists of two tabs:
o Project Data
Displays the filtered objects assigned to the selected project.
o Team
Displays the project team associated with the selected project.
Note The content of the My Projects view varies when you install Consumer
Packaged Goods.
For more information, see Getting Started with Consumer Packaged Goods.
• Filters defined in My Teamcenter cannot be saved for future use. You must add
and remove them as required.
• Only one filter criteria can be applied to an abstract smart folder . If multiple
filters are applied to an abstract smart folder, no project data is displayed.
2. In the My Projects view, expand a project object to view the data associated
with the project.
Note Objects are displayed according to the project smart folder hierarchy
configuration defined by the project administrator and/or by any filters
that you apply.
If a smart folder hierarchy is configured for your project, you see folders
when you expand your project. Expand these folders to reveal your
project data.
4. Click the filter button to apply a filter to refine the list of objects for the
selected project.
The Apply filters dialog box appears.
6. Choose filter criteria by clicking the Source Type, Property, and/or Value cells
and selecting a value from the list.
For example, you can add a filter to display the project data owned by the
Engineering group.
Note You can remove rows from the filter table by clicking the Remove the
selected filter button . Click the Clear the filters button to remove
all values from the table.
Find projects
1. Click Search on the toolbar or select Advanced from the perform search
menu at the top of the navigation pane.
4. Click Clear all search fields to clear the contents of the search form boxes.
5. Type the project search criteria in the applicable search form boxes.
1. Click Search on the toolbar or select Advanced from the perform search
menu at the top of the navigation pane.
4. Click Clear all search fields to clear the contents of the search form boxes.
5. Type the project search criteria in the applicable search form boxes.
• You have a current project set when you create a new Teamcenter workspace
object. To set your current project in My Teamcenter, choose Edit→User Settings.
On the object creation wizard Assign to Project page, the Owning Project property
is displayed, but not yet assigned.
• After the item is created, the Owning Project property is populated and can be
seen in the Details view when you add the Owning Project column to the display.
• You can use the Assign to Project page to assign the object being created to one
or more projects, but the Assign to Project step is not required for the data
to be assigned to the owning project.
After objects have been created, you can assign them to projects by selecting the
objects from a hierarchy tree, a Details table, or the Search Results view.
Note You can select from different lists of values (LOVs) for a property depending
on which project the object is assigned to.
For more information about selecting different property values from an LOV
based on assigned project, see the Project and Program Guide.
For more information about assigning objects to projects, see Assign objects to
projects from the tree or Details table.
Teamcenter administrators and project administrators can add tor remove multiple
objects for a project by using the update_project_bom utility.
3. Select the project or projects to which the objects will be assigned and move
them to the Selected Projects list using the right-arrow button. To select all
projects in the list, click the double-arrow button.
4. Click Apply to assign the objects to the projects and retain the dialog box. Click
OK to assign the projects and exit the dialog box.
2. Select the project or projects to which the objects will be assigned and move
them to the Selected Projects list using the right-arrow button. To select all
projects in the list, click the double-arrow button.
3. Select the objects to be assigned by selecting either Current Page or All Found
Objects.
4. Click Apply to assign the objects to the projects and retain the dialog box. Click
OK to assign the projects and exit the dialog box.
2. Perform the steps described in Assign objects to projects from the tree or Details
table, beginning with step 2.
The propagation rules are valid when the following actions take place in Teamcenter:
• When an item or item revision is assigned to a project or program, the related
objects are also assigned.
• When a related object is cut from the object assigned to the project or program,
the related object is removed from the project or program.
Generally, you propagate secondary items that are related to the primary item by a
Specifications, Manifestations, Attaches, or AltReps relationship. Secondary
items related to primary items by Requirements and References relationships
generally do not need to be implicitly propagated to the project or program.
• Manifestation
• AltRep
• EC_affected_item_rel
• EC_solution_item_rel
For more information about defining propagation rules and configuring assignment
of related (secondary) objects to projects, see the Project and Program Guide.
• Forms
• Datasets
For example, Teamcenter can be configured to assign new item revisions to the
current project or program of the user who creates the new item revision.
Note Your current project or program is defined in the User Settings dialog box.
You can choose Edit→User Setting to change your current project or program.
For more information about removing objects from projects, see Remove objects
from projects.
• If you select a single object, the system displays the Remove an Object from
Projects dialog box.
The projects in which the selected objects are assigned, and in which you are a
privileged member, are displayed in the Projects for Selection list.
3. Select the project or projects from which the objects will be removed and move
them to the Selected Projects list using the right-arrow button.
Note To select all projects in the list, click the double-arrow button.
• To remove the projects and exit the dialog box, click OK.
Subscriptions overview
Subscriptions let you receive notification, in near real time using Teamcenter mail,
when data is modified by another user or as the release status of an item revision
changes. You can:
• Create subscriptions to objects that provide Teamcenter mail notification when
modifications are made to the object or when the status of the object changes.
• Create subscriptions that notify you when a secondary object, such as a dataset,
is created relative to the primary object, such as the item or item revision.
Teamcenter refers to these changes and additions of secondary objects as events.
• A base item revision is released with any release status other than a specified
status.
• Event initiated by
• Time of event
• Site name
• Email_Not_Send
Indicates the notification mail is not sent.
To access notification mail history. choose the View→Audit→View Audit Logs menu
command to display the Viewing the audit logs dialog box. And then, under Event
Type Name, specify Email_Send or Email_Not_Send to view notification status.
Event types
An event type defines an event whose occurrence on an object can be tracked with a
subscription.
• When the event occurs relative to the target object, the subscriber is notified.
• The list of available event types displayed during the creation of a subscription
depends on the event types that are mapped to the selected target object type.
o When you subscribe to an item revision, which can be the target of a
workflow process, the Event Type list includes the workflow event types such
as process initiated, assign, start, and complete.
Create a subscription
Note To enable notification by e-mail:
1. Set mail gateway preferences:
• TC_subscription=ON to enable display and use of the
Tools®Subscribe menu command.
2. Ensure the E_Mail address fields for the Persons objects associated to
users to be notified are set correctly in the Organization application.
For information about creating and editing Person objects, see the
Organization Guide.
To create a subscription:
1. (Optional) Select one or more subscribable objects in the tree or Details table.
3. In the Details Group area, select Create Subscription for Object or Create
Subscription for Object Class, and then click Next.
Note If no object is initially selected, only Create Subscription for Object
Class is available.
Button State
No pending refresh notification.
For more information about preferences, see the Preferences and Environment
Variables Reference.
You can configure refresh notification as follows:
• Configure type-based subscriptions using the
TC_refresh_notify_subscribe_to_types preference. These subscriptions
are created each time you log in to Teamcenter.
• Specify the time interval for obtaining refresh notification using the
TC_refresh_notify_pull_time_interval preference.
4. Click OK.
The system creates the subscription, which is valid for the duration of your
Teamcenter session.
Note Object-based refresh notification subscriptions are valid only for your
current session. When you log off of Teamcenter, the subscription
expires. You can specify a duration for a subscription using the
Subscription Manager.
2. Either select specific objects from the list and click Refresh Selected or click
Refresh All to refresh the entire list.
The system refreshes the objects that are loaded in your current session.
All users can access the Subscription Manager. Your role determines the level of
functionality that is available. Only system administrators can modify and delete
subscriptions on behalf of another user.
Teamcenter queries the database to retrieve the information that displays in the
Subscription table. You can rearrange the order of columns in the table by clicking
on the column head and moving it to the desired location. You can also print, add,
and remove columns, such as:
• Target
• Subscriber
• Event Type
• Expiration Date
• Execution Time
Use the lower portion of the pane to enter search criteria. The search criteria is
based on the object, subscriber, event type, expiration date, execution time.
2. Click the General tab and define the search criteria, either Object, Subscriber,
and/or Event Type.
4. (Optional) Refine your search criteria by clicking the Advanced tab and choosing
one of the following options:
Expiration Date Searches for subscriptions that expire within a date range.
Range
No Expiration Date Searches for subscriptions that do not have an expiration
date.
Execution Time Searches for subscriptions with execution times within a
Range specified range.
Execute Searches for subscriptions with no execution times.
Immediately
5. Click Find.
Modify a subscription
1. Choose Tools→Subscription Manager.
2. Select the row in the table corresponding to the subscription that you want to
modify and click the Modify button.
3. Modify the information in the Expiration Date, Execution Time and/or Event
Type boxes. Other modifiable boxes may appear depending on the event type
selected. The Notify and Subscriber boxes appear for the system administrator
to modify.
Note You cannot modify the values in the Target Object box.
4. Click OK.
Delete a subscription
1. Choose Tools→Subscription Manager.
2. Select the row in the table corresponding to the subscription that you want
to delete and click the Delete button.
16 Managing forms
Create a form from a predefined form type using the legacy dialog box . . . . . . 16-3
16 Managing forms
• Informative information is what you see in read-only boxes in the form. You
cannot modify this information.
Forms contain information about the objects to which they are attached. Companies
typically use forms to:
• Capture and store information for work orders, change orders, or change notices.
This is the most common use of forms.
To view a form in the rich client, select the form object and choose the Viewer view.
Note For form objects, the Form_double_click preference value can be set to
either View or Edit to cause the double-click action on a form to open that
form in either edit or view mode.
an ItemRevision Master form object is created automatically. You can enter data
in the item master and item revision master forms when you create an item or by
opening an Item Master or ItemRevision Master form object.
Note • Master forms inherit access privileges from the parent item or item
revision, so if you change access privileges to an item or item revision
you affect the privileges on the master form.
You can use the TC_MASTERFORM_DELEGATE environment
variable to change this default behavior.
For more information, see the Preferences and Environment Variables
Reference.
You create forms in the rich client using one of the following methods:
• Choose File→New→Form to create a stand-alone form object in a container (like
a folder) or a form associated with an item or item revision object. You select the
form type from the list.
• Choose File→New→Item. When you create an item, at least two form objects are
also created: the item master and item revision master.
6. Click Finish to save the form in the database, or click Cancel to close the dialog
box without creating the form.
Create a form from a predefined form type using the legacy dialog box
Note The TC_Enable_Legacy_Create preference specifies whether the
legacy dialog box or the generic dialog box is displayed for the rich client
File®New®Form menu command objects. If the legacy dialog box is
enabled, use the following procedure.
5. Select a form type from the Type bar by clicking the button in the display. If the
type names are truncated, click the arrow located in the upper-left corner of the
icon display and then select a type from the list.
The Type bar displays the form types that you use the most. If you do not see the
type you are looking for, click More to display all defined form types.
Note The form types displayed in this dialog box are controlled by your
administrator. Therefore, it is possible that you may be unable to create
form types that are visible to you in your workspace.
6. Click OK to save the form in the database and close the dialog box, or click Apply
to save the form in the database and retain the dialog box.
5. Select the form in your Newstuff folder and cut or copy it.
6. Choose the destination container and paste the form using the Paste button or
Edit→Paste.
1. In the My Teamcenter tree, select two forms of the same type to which you have
read access.
Tip You can select a single form and Teamcenter automatically compares the
selected form with the form associated with the previous item revision, if
one exists.
The system displays the Form Compare Results dialog box listing the properties
and their values for each form.
Note Extra spaces or a change in the order of values is considered a difference
and is presented as such.
2. Choose File→New→URL.
The system displays the New URL dialog box.
3. Enter a name for the new URL object in the Name box. Up to 20 characters
are allowed for the URL name.
4. Enter the URL of the Web page that you want to access via this object in the
URL box.
The maximum number of characters allowed for the URL is 512. The input
format of the URL depends on your browser. For example, when using Microsoft
Internet Explorer, the following formats are valid:
http://www.your-site.com
www.your-site.com
your-site.com
5. (Optional) Enter a description of the URL in the Description box. The maximum
number of characters allowed for the description is 240.
6. (Optional) Select Open on Create if you want to display the Web page when you
finish creating the URL object.
7. Click OK to create the URL object and exit the dialog box.
The system displays the new URL object within the selected container in the
My Teamcenter tree.
• Select the object and choose File→Open to display the content in the default
local browser.
• Select the object and use the Viewer view to display the Web Link object
properties.
Teamcenter automatically opens a Web Browser view to display the Web page
associated with the object.
5. Click Save.
6. Click Close.
18 Managing collaboration
context objects
18 Managing collaboration
context objects
Each structure context may include one or more root objects, each of which may be
an occurrence group, an item or an item revision. The item revision may include
objects derived from an item or another item revision. You can attach data objects
to collaboration context and structure context objects.
You can open a collaboration context or a structure context several ways, for
example, by dropping the object on Multi-Structure Manager in the navigation pane.
Within each structure context, you can browse the structure, modify its content, and
create relationships with other structures.
For more information about managing collaboration contexts or structure contexts,
see the Multi-Structure Manager Guide.
4. (Optional) Select the Open on Create check box to open the collaboration context
in a new tab.
5. Click Next.
8. Click Finish.
The system displays the context as a top-level line in the tree.
• No variant rule.
• No closure rule.
The structure context may be a composition, depending on the type of context you
select. Items in a composition structure may have relationships to other structures
or to absolute occurrences and occurrence groups.
Note You can also create a new structure in the Multi-Structure Manager
application.
If you want to add existing structure contexts to a collaboration context, do
this in the Multi-Structure Manager application.
For more information, see the Multi-Structure Manager Guide.
Teamcenter places the types of structure context you previously created in the
Most Recently Used list.
3. Click Next.
b. Type the name or part of the name of the configuration context in the Name
box.
c. Click Find.
The system displays the contexts matching the name criteria in the table.
7. Click Finish.
Note You can also create a structure context with the Multi-Structure Manager
application.
For more information, see the Multi-Structure Manager Guide.
• IDC files contain the configuration of a structure at the time the IDC is created.
2. From the list on the left, select the type of IDC you want to create.
3. Type the name and optional description of the intermediate data capture, then
choose the appropriate transfer mode name from the list.
4. Click OK or Apply.
Teamcenter validates the objects you selected. If any of the objects cannot be
captured, the system displays an error message; otherwise, it creates the PLM
XML file containing the IDC.
2. Select the type of IDC you want to create in the list on the left.
3. Type the name and optional description of the intermediate data capture, then
choose the appropriate transfer mode name from the list.
4. Click OK or Apply.
Teamcenter validates the objects you selected. If any of the objects cannot be
captured, The system displays an error message; otherwise, it creates the PLM
XML file containing the IDC.
Edit an IDC
You can edit the content of an IDC at any time, for example, by adding or removing a
root object, or by updating it to a new state.
If you change a file that an IDC references, Teamcenter keeps a copy of the original
file so the integrity of the IDC is maintained.
1. Select an IDC and use the Send To shortcut menu command to select the
Multi-Structure Manager application.
• Click Add State and create a new state from the captured root objects.
• Click Remove State and remove a state from the captured root objects.
• Click Update State to update the IDC from the currently selected root objects.
2. Paste the IDC under the root object, if one is open. If no root object is open, the
IDC itself becomes the root object. In this case, the IDC is visible.
3. If the IDC contains more than one state of the structure, choose the desired
state from the Captured States list.
20 Managing manufacturing
documentation
20 Managing manufacturing
documentation
Creating a portfolio
Portfolios act as a container for work instructions or product manuals and supporting
documents, such as a table of contents, cover or trailer pages, and header and footer
information. Portfolios may contain a reference to a publishing page or generic
page or to an embedded generic page. You can use portfolios to store document
structure information, print multiple publishing pages, and export portfolio contents
to HTML or PDF.
You generate portfolios in Manufacturing Process Planner, Part Planner,
Multi-Structure Manager, Service Planner, or Plant Designer. You manage portfolios
in My Teamcenter only.
When managing a portfolio:
• Use container nodes to add an organizational hierarchy to the portfolio. Think
of container nodes as chapters in a book, in which you can separate and group
documents. Container nodes are useful for multiple levels in the table of
contents.
• Create generic pages for any information page to add to the portfolio, such as
cover or trailer pages. Generic pages are not considered publishing pages and
Teamcenter does not apply headers and footers to them.
o Create
Add a new supporting document that Teamcenter embeds in the portfolio.
You can only create and embed generic pages.
o Embed
Copy a supporting document into the portfolio.
2. Using the menu commands within the Viewer view, do one of the following:
• Choose Actions→Create and select Container Node.
• On the Technical Portfolio toolbar, click the Create table of contents button
.
2. Select an area in the portfolio to place the header and footer page.
3. Using the menu commands within the viewer, do one of the following:
• Choose Actions→Create, Actions→Insert Reference or Actions→Embed,
and select Header/Footer Definition Page.
4. Using the commands in the new window, choose Insert→Portfolio Export Tag
and select one of the following:
• Date
• Long Date
• Pages
6. When you have placed all desired export tags, choose File→Post to Technical
Portfolio.
7. Click Close.
2. Right-click the header and footer page in the portfolio tree and choose Open.
5. Click Close.
3. Click the Find a page by name button and type the name of the work instruction
that you want to add.
4. Click Open. The work instruction you chose appears in the tab.
3. Click OK.
The Report Definition wizard displays the status of the export operation.
Note Name lists the supporting documents in the portfolio; Status indicates if
the supporting documents were exported.
4. Click Next.
The system displays the Create Report Output dialog box.
2. Using the menu commands in the viewer, choose File→Publish PDF to Database
Teamcenter creates the PDF and attaches it to the portfolio dataset. You can
view it in the viewer.
3. Enter the parameters for the Schedule the Batch Process step.
• Select Immediate to initiate the task at the current date and time. Clicking
Finish on any page without previously selecting scheduling parameters also
initiates the task immediately.
• Select Periodical to schedule a task that recurs at a specific date and time.
You can specify a recurrence pattern on a daily, weekly, monthly, or yearly
basis.
3. Using the menu commands within the Portfolio pane, do one of the following:
• Choose Actions→Create, Actions→Insert Reference or Actions→Embed,
and select Generic Page.
• On the Technical Portfolio toolbar, click the Create generic page button .
• Parametric requirements
Represent the requirements established by the Standards Engineering
organization that conform to the design practices of a program. Parametric
requirements are often maintained in a library for use by all designers.
Teamcenter provides you with features to manage requirements using trace links.
Through trace links, requirements are connected to objects in other Teamcenter
applications, as appropriate for the product design.
Custom notes can be created in the context of another object such as a requirement,
a part, or a manufacturing object such as a process or operation. Notes are used to
capture issues, actions, questions, or other ad hoc types of information.
For more information about managing requirements, see the Systems Engineering
Guide.
2. Choose File→New→Item.
3. In the New Item dialog box, select the RequirementSpec item type.
4. Click Next.
The system displays the Define basic information for new item pane.
5. Type an item ID, revision ID, and name for the requirement specification, or click
Assign to automatically generate the item ID and revision identifiers.
Note The Assign button is active only if naming rules and automatic
generation are implemented.
7. Click Next.
The Define additional item information pane appears.
9. Click Next.
The Define additional item revision information pane appears.
11. (Optional) In the left pane of the New Item dialog box, click the Assign to
Projects or Programs link.
The system displays the list of projects or programs to which the requirement
specification can be assigned.
Note You can assign objects to projects or programs only if you are a privileged
team member.
12. (Optional) Select one or more programs from the Projects or Programs for
Selection list and move them to the Selected Project or Program list.
13. (Optional) Click Next or click the Define Options link in the left pane of the
New Item dialog box.
The new requirement specification is created in the current folder and opens in
Systems Engineering.
Create a requirement
1. Open My Teamcenter.
2. Select the requirement specification item revision node under which you want to
create the requirement.
3. Choose File→New→Item.
4. In the New Item dialog box, select the Requirement item type.
5. Click Next.
The system displays the Define basic information for new item pane.
6. Type an item ID, revision ID, and name for the requirement, or click Assign to
automatically generate the item ID and revision identifiers.
Note The Assign button is active only if naming rules and automatic
generation are implemented.
8. Click Next.
Create a paragraph
1. Open My Teamcenter.
2. Select the requirement object under which you want to create the paragraph.
3. Choose File→New→Item.
4. In the New Item dialog box, select the Paragraph item type.
5. Click Next.
The system displays the Define basic information for new item pane.
6. Type an item ID, revision ID, and name for the paragraph, or click Assign to
automatically generate the item ID and revision identifiers.
Note The Assign button is active only if naming rules and automatic
generation are implemented.
8. Click Next.
Only one trace link of a given subtype is allowed between the same two objects in the
same direction. However, in a given direction between two objects, you can create as
many trace links as the number of available trace link subtypes.
Note Trace link is a subclass of the allocation class.
For more information about allocations, see Getting Started with Product
Structure.
For more information about trace links, see the Systems Engineering Guide.
• You must make multiple object selections from only one structure at a
time. You cannot select an object in one structure, and then switch to
another structure and select additional objects.
• In either direction between two objects, you can create as many trace links as
the number of available trace link subtypes.
When you create a trace link, you can accept the default subtype, Trace Link.
Or, you can assign a custom subtype, created in the Business Modeler IDE by a
Teamcenter administrator.
• Custom subtypes let you create two or more trace links between the same objects
in the same direction, if you assign a different subtype to each trace link.
For example, a trace link from defining requirement A to complying requirement
B has the Trace Link subtype.
A second defining trace link, with the custom subtype S, can be created from
requirement A to complying requirement B.
• Trace links of the same subtype are allowed in both directions between the same
objects. For example:
Defining requirement A is linked to complying requirement B, with the Trace
Link subtype assigned to the trace link.
You can create a trace link of the same subtype to link requirement B, as the
defining object, back to requirement A as the complying object, completing
circular trace links.
For more information about enabling in-context mode, see the Manufacturing
Process Planner Guide.
2. Select the source object, or select multiple objects by using the standard
Windows functions.
Note If you select only one source object, you can create trace links to multiple
target objects. If you select multiple source objects, you can create trace
links to only one target object.
3. Choose Tools→Trace Link→Start Trace Link, click the Start Trace Link
Creation button on the toolbar, or right-click the selection and choose Trace
Link→Start Trace Link.
4. Select the target object, or select multiple objects by using the standard Windows
functions.
Note If you select only one source object, you can create trace links to multiple
target objects. If you select multiple source objects, you can create trace
links to only one target object.
5. Specify the trace link subtype and name by doing one of the following:
• To accept the default subtype and name, choose Tools→Trace Link→End
Trace Link, click the End Trace Link Creation button on the toolbar, or
right-click the selection and choose Trace Link→End Trace Link.
a. Choose Tools→Trace Link→End Trace Link..., click the End Trace Link
Creation with Subtype button on the toolbar, or right-click the
selection and choose Trace Link→End Trace Link....
The Create Trace Link dialog box appears.
b. In the list of subtypes on the left, select the subtype to assign to each
trace link.
c. In the Name box, type the name to assign to each trace link.
A trace link symbol is displayed for each defining and complying object. The
symbol appears next to the object or in the Trace Link column, depending on the
application where you view a given object.
Note Trace link symbols are not displayed for objects in My Teamcenter.
To determine whether trace links exist on these objects, add the Has
Tracelink property column in the Details view.
For each object in the Details view, the Has Tracelink column displays
one of the following values:
You can view the defining and complying path for trace linked objects in the
Traceability view or by generating a traceability report.
For more information about viewing trace links in the Traceability view, see
Systems Engineering Guide or Run a traceability report.
• The Traceability Matrix view displays the assignments between two selected
structures.
• Run an accountability check to compare two structures to ensure all lines in the
source structure are consumed in the target structure.
For example, you can compare a requirement structure against a product
structure, or compare a requirement structure against a manufacturing process
structure.
• In the Teamcenter Relation Browser view, you can view the trace link
hierarchies in a requirement structure.
For more information about using the Relation Browser view, see the Rich Client
Interface Guide.
• The report shows the defining and complying objects for the trace links
related to the selected objects.
• The report also includes a column showing the context for the defining and
complying occurrence objects, if applicable.
• If any trace links exist on the parent item to the selected workspace or
occurrence objects, or on revisions of the workspace or occurrence objects,
those objects and the associated trace link symbols are included in the report.
Note
• The direct trace link symbol indicates that the trace link relates
to the selected object itself.
• The indirect trace link symbol indicates that the trace link relates to
a revision or item that is associated with the selected object.
• The symbols for direct trace link on occurrence and indirect trace
link on occurrence are also indicated on the report, where applicable.
• For an interactive live Excel file that is connected to Teamcenter, click Live
integration with Excel (Interactive).
• For a live Excel file that is not connected to Teamcenter, click Live integration
with Excel (Bulk Mode).
You can accumulate changes and later connect the file to Teamcenter.
• To export the data to an Excel file that also contains import processing
information on a separate sheet, click Work Offline and Import.
• To check out objects while exporting to live Excel, select Check out objects
before export.
Note The checkout applies to all objects being exported. Use this option
carefully if you are exporting a large set of objects or perhaps an
entire product structure.
For information about managing and creating Excel export templates, see the
Systems Engineering Guide.
Note • Copy URL is unavailable if you select more than one object to export.
Excel opens a temporary file. You can create a permanent file by choosing File→Save
As in Excel to display the Save As dialog box.
If you save a live Excel file, you can open it later in My Teamcenter to reconnect
it to the database.
Note Values that you cannot change in Teamcenter are unavailable in the cells
of the live Excel file.
Note When deleting a trace link on an occurrence object, you must consider the
context of the occurrence.
Tip You can use the following procedure to delete trace links from one or more
workspace or occurrence objects at a time.
2. Click the Delete Trace Link button at the bottom of the traceability report or
Traceability view or press the Delete key.
the primary object and the custom note or custom note revision is the secondary
object.
• The text for custom note data is specified in the Body Text property of the note
revision. You use MS Word to create and edit the content of a custom note.
• Custom notes are attached directly to an object, and not underlying occurrences.
You can view additional information about the custom note by displaying the
Custom Notes view. To display the custom notes using the Custom Notes view,
select the custom note or the object with the custom note and choose Window®Show
View®Other®Systems Engineering®Custom Notes or click the Show Custom
Notes button on the toolbar.
2. Choose File→New→Other.
Note You can also choose File→New→Item to create the object using the New
Item dialog box.
4. Type the revision ID, revision, and name for the custom note.
Note You must type a name for the custom note in the Name box. If you leave
the Requirement ID and Revision boxes blank, the values are filled in
automatically when you click Finish to create the custom note.
6. Click Finish.
A new custom note is created in the selected folder in My Teamcenter or attached
to the selected object.
2. Right-click the custom note or the custom note revision that you want to attach
and click Copy.
6. Click OK.
Plain text a. Right-click the custom note revision and choose Edit
format Properties.
The Check-Out dialog box appears.
d. Click Yes.
The Edit Properties dialog box appears.
f. Scroll to the Text box and type the custom note. For
example:
Verify axel tolerance using company standard test methods.
h. Click Yes.
The custom note is checked in and the new text appears
in Body Cleartext property displayed on the Overview
tab in the Summary view.
Rich text Note To open the dataset in rich text format, you must
format have Microsoft Office 2007 installed on your
machine.
a. Double-click the Full Text dataset associated with
the note revision, or select the dataset and choose
File→Open.
The note opens in Microsoft Word 2007.
Note Before you can create full text dataset,
Teamcenter must be configured correctly.
For more information, see the Systems
Engineering Guide.
2. Select the custom note revision that you want to revise and choose File→Revise.
The Revise dialog box appears.
3. (Optional) In the Define the basic information for the new item revision pane,
type the name of the new revision.
4. (Optional) Type a description of the revision and choose a unit of measure for
the revision.
5. Click Next.
The Define additional item revision information pane is displayed.
7. Click Next.
The Define attached objects pane displays the source revision and attachments
and the destination revision and attachments. By default, all objects are copied
forward to the new (destination) revision.
8. (Optional) Click the Copy as object option set button to the right of each object
in the revision tree and select the desired copy option.
Don’t Copy
Allows you to selectively copy objects from one revision to
another. Objects that are designated as Don’t Copy appear
with a line through them in the Destination tree.
Copy as Object
Creates a new object of the same type and relation to the
parent object. Objects created by this method are totally
independent of the parent object. Therefore, any changes to
the copied object are not reflected in the original object.
Copied objects appear in bold in the Destination tree and
can be renamed.
Copy as Reference
Copies the object as a reference to the original object. All
changes to the reference copy affect the original object. The
names of attachments that are copied as references cannot
be modified.
9. Click Next.
The Select projects or programs that you want to assign new object to pane
is displayed.
12. (Optional) Set the open, display, or checkout option for the new revision.
1. Select the custom note or custom note revision object you want to delete.
2. Choose Edit®Delete or click the Delete button on the toolbar or press the Delete
key.
Teamcenter displays a request for confirmation.
3. Click Yes.
Note The standard rules for deleting an item or item revision apply to deleting a
custom note or custom note revision.
• The parameters for the requirement are specified in the Body Text property
of the requirement revision.
Note Requirement text cannot be modified after it is saved. You must create a
new revision of the parametric requirement and make changes to the
Body Text property of the new revision.
• The text of the requirement revision contains text, parameters, and applicable
values using the syntax shown below.
text [parameter name: parametric value1 delimiter parametric
value2 delimiter... parametric value n]
Example Round all sharp corners to [Radius: 0.4, 0.5, 0.6] inch
and heat treat to [Temperature: 200, 220, 230] degrees Fahrenheit.
• The default delimiter for parameters in the requirement text is a comma (,).
However, your Teamcenter administrator can configure the delimiter to use
a different character.
1. Choose File→New→Item.
The New Item dialog box appears.
2. In the New Item dialog box, select the Parametric Requirement item type.
3. Click Next.
The system displays the Define basic information for new item pane.
4. Type an item ID, revision ID, and name for the standard note, or click Assign to
automatically generate the item ID and revision identifiers.
Note The Assign button is active only if naming rules and automatic
generation are implemented.
6. Click Next.
The Define additional item information pane appears.
8. Click Next.
The Define additional item revision information pane appears.
10. (Optional) In the left pane of the New Item dialog box, click the Assign to
Projects or Programs link.
The system displays the list of projects or programs to which the parametric
requirement can be assigned.
Note You can assign objects to projects or programs only if you are a privileged
team member.
11. (Optional) Select one or more programs from the Projects or Programs for
Selection list and move them to the Selected Project or Program list.
12. (Optional) Click Next or click the Define Options link in the left pane of the
New Item dialog box.
You can double-click the new parametric requirement item to open it in Systems
Engineering and display the new parametric requirement as the root structure.
1. Open My Teamcenter.
6. Click Yes.
The Edit Properties dialog box appears.
7. Click the All link in the Edit Properties dialog box, and scroll to the Body Text
box.
8. In the Body Text box, type the note using the following syntax:
text [parameter name: parametric value1 delimiter parametric
value2 delimiter ..... parametric value n]
Example Round all sharp corners to [Radius: 0.01, 0.02, 0.03] inches
and heat treat to [Temperature: 100, 120, 130] degrees Fahrenheit.
Note The delimiter used when specifying parametric values is defined by your
Teamcenter administrator.
9. Click Save.
Note You cannot modify the text after it has been saved. To update parameters,
you must create a new revision of the parametric requirement.
1. Open My Teamcenter.
5. Click OK.
The parametric requirement revision is attached to the selected object (item or
item revision) through the Parametric Requirements Lists relation.
Note If the requirement is not visible under the item or item revision to which it is
attached, you must specify Parametric Requirements Lists as a shown
relation for the item and item revision. To do this:
1. Choose Edit→Options.
6. Click OK.
2. Select the parametric requirement revision that you want to revise and choose
File→Revise.
The Revise dialog box appears.
3. (Optional) In the Define the basic information for the new item revision pane,
type the name of the new revision.
4. (Optional) Type a description of the revision and choose a unit of measure for
the revision.
5. Click Next.
The Define additional item revision information pane is displayed.
7. Click Next.
The Define attached objects pane displays the source revision and attachments
and the destination revision and attachments. By default, all objects are copied
forward to the new (destination) revision.
8. (Optional) Choose copy options for the objects related to the source revision by
clicking the icon to the right of the object in the tree.
Don’t Copy
Allows you to selectively copy objects from one revision to
another. Objects that are designated as Don’t Copy appear with
a line through them in the Destination tree.
Copy as Object
Creates a new object of the same type and relation to the parent
object. Objects created by this method are totally independent of
the parent object. Therefore, any changes to the copied object are
not reflected in the original object.
Copied objects appear in bold in the Destination tree and can be
renamed.
Copy as Reference
Copies the object as a reference to the original object. All changes
to the reference copy affect the original object. The names of
attachments that are copied as references cannot be modified.
9. Click Next.
The Select projects or programs that you want to assign new object to pane
is displayed.
12. (Optional) Set the open, display, or check-out option for the new revision.
2. Right-click the revision of the parametric requirement that will replace the
revision attached to the item or item revision, and choose Copy.
3. Expand the item or item revision and select the parametric requirement revision
that you want to replace.
6. Click OK.
The parametric requirement revision attached to the item or item revision is
replaced by the new revision of the requirement.
22 Managing schedules
22 Managing schedules
2. Choose Schedule in the right pane and click Next to display the following figure.
a. In the Schedule Information section, enter a value for Schedule ID, Revision
ID, and Name.
Optionally, enter a value for Name, and then click Assign to have Schedule
Manager enter values for Schedule ID and Revision ID.
b. (Optional) If you selected the Use an existing Schedule template for this
new Schedule check box, you can also select the Background Copy check
box to create the schedule in the background to increase system performance.
c. If you selected the Use an existing Schedule template for this new Schedule
check box, click the Template button to select the schedule template.
Teamcenter displays the Choose a Schedule Template dialog box.
Select a schedule template or master schedule template from the list and
click Select.
d. (Optional) If you selected the Use an existing Schedule template for this
new Schedule check box, you can change the start date of the new schedule
from the template start date by clicking the Shift Date calendar button.
f. The Time Zone section contains the default time zone. Click the arrow to
display a list of values.
g. Click the Start Date calendar and select the start date and time for the
schedule calendar. You can set the date, hour, and minutes. If you base your
schedule on the start date, you create your tasks from the start date forward.
Click the Finish Date calendar and select the finish date and time for the
schedule calendar. You can set the date, hour, and minutes. If you create
your schedule on the finish date, you build your tasks from the finish date
backward.
Note All tasks and milestones for the schedule must fall within the start
and finish dates. After the schedule is created, you can change the
start and finish dates using the Properties dialog box.
For more information about the schedule calendar, see the Schedule
Manager Guide.
h. In the Schedule Options section, you can select the following check boxes:
• Is Schedule Template
Specifies this schedule is a schedule template. Schedule templates are
used as a basis for other schedules.
For more information about creating schedule templates, see the
Schedule Manager Guide.
• Published
Specifies this schedule is published. Published schedules allow other
users access to the schedule. By default, this option is selected.
Only the owner of the schedule can publish or unpublish a schedule at
any time using the Schedule Properties dialog box. To deny access to
the schedule to other users, keep it unpublished. Publish it when you are
ready for others to view or edit it.
Note Certain functions, such as the schedule calendar, cannot be
changed after a schedule is published. If changes to the schedule
are necessary, unpublish the schedule, make changes, and then
republish the schedule.
To unpublish a schedule:
A. Right-click the schedule in Schedule Manager and choose
Edit®Properties.
B. In the Properties dialog box, locate the Published option and select
False.
C. Click Save.
• Is Schedule Public
• Is Percent Linked
If you select this option, the following rules apply:
o If you change the work completed, the percentage completed changes
to equal the percent of scheduled work completed.
4. Click Finish.
Schedule Manager creates the new schedule and it appears under the folder that
was selected when you chose File→New→Schedule. You can move the schedule
from the current folder to another folder.
Note Cloning of schedules is not allowed.
Delete a schedule
Deleting a schedule deletes all tasks, dependencies, costs, and resource assignments
in that schedule.
1. In My Teamcenter, select the schedule to delete.
Note You cannot delete the schedule from within Schedule Manager.
2. Choose Edit→Delete.
• The person who creates a schedule can always view the schedule.
• A person who is member of the schedule only views the schedule if the
Published schedule option is set.
• A person who is not a member of the schedule only views the schedule if the
Published and Public schedule options are set.
5. Click OK.
Teamcenter displays the Find Schedule(s) dialog box.
At minimum, you must enter a Schedule Name. However, wild cards are
permitted. To display all schedules, enter an asterisk (*) in the Schedule Name
box.
Caution The ALL button lists attributes that may not be applicable to
schedule management.
5. Click OK.
o Late
o Needs Attention
Note Schedule Manager does not automatically change the task status
to Needs Attention.
Preference Description
scheduling_graph_dataSource Specifies data source for resource graph.
When set to randomSample, the system
uses a random sample generator. When set to
TeamcenterDB (default), the system uses the
Teamcenter database.
Warning This preference must be set to
TeamcenterDB in a production
environment.
scheduling_graph_dataSource_filter Specifies the filtering method used when
creating resource graphs.
• none
No filter applied (default)
• selection
Filter for selected schedules
• current
Filter for the current schedule
scheduling_graph_date_format Specifies data format in resource graph. Valid
values can be any patterns that describe date
and time format. The default value for this
preference is EEE, MMM d.
scheduling_graph_domain_interval Specifies the marked intervals on the domain
axis. Valid values are any segmented time line
value such as day (default), week, or integer
values such as 1 for a day or 7 for a week. Valid
values include day, week, month, 1440, and
10080.
scheduling_graph_domain_label_vertical Specifies the orientation of the domain labels.
When set to true (default), the label orientation
is vertical. When set to false, the orientation
is horizontal.
scheduling_graph_font_name Specifies a font name. Valid values can be a font
name or font family name. The default varies by
system type (Windows or Linux).
Preference Description
scheduling_graph_font_size Specifies a font size. Valid values are any
appropriate integer number. The default value
is 5.
scheduling_graph_font_style Specifies font style. Valid values are 0 (default)
for normal style, 1 for bold text, 2 for italic text,
and 3 for bold and italic text.
scheduling_graph_histogram_single_color Specifies single or multiple color bars in the
graph. When set to true (default) a single color
is used. When set to false, multiple colors are
used.
scheduling_graph_reference_calendar Specifies the calendar type to use for domain
(x = days) and range (y = availability/work
allocation) axes in the resource graph.
scheduling_graph_task_legend Enables legend display. When set to true, the
system displays legends for stacked bars. When
set to false (default), no legends are displayed
for stacked bars.
Note If this preference is set to true, tooltips
do not include schedule and load
information.
scheduling_graph_view Specifies whether to use scroll bars in the view.
Valid values are classic, to view the graph with
scroll bars, and native (default), to view the
graph without scroll bars.
TC_current_role Can be set to true or false to specify how
members of the ResourceGraphViewers role
have read access to all schedules.
If the TC_current_role preference is set to
false, a member of the ResourceGraphViewer
role has read access to all schedules, even when
the ResourceGraphViewer role is not the
user’s current role.
If the TC_current_role preference is set to
true, a member of the ResourceGraphViewer
role has read access to all schedules only when
the ResourceGraphViewer role is that user’s
current role.
The default value is false.
Note Changing the TC_current_role
preference has an impact outside of as
it alters how the core access rules are
evaluated.
For more information, see the Access
Manager Guide.
B. Select columns in the Available Columns list and click > to copy them to
the Displayed Columns list.
D. Click Apply after you specify the columns to display in the program view.
e. Click Next.
a. Select schedules from the Available Schedules list and click > to copy them
to the Selected Schedules pane. To select all available schedules, click >>.
Note You cannot select schedule templates for program view.
To remove schedules from the Selected Schedules list, select the schedules
and click <. To remove all schedules, click <<.
You can also use the Search box to search for a particular schedule.
b. Click Next.
a. Select a value from the And/Or box to specify whether the next filter
condition is in addition to (And) the previous condition or instead of (Or)
the previous condition.
c. Select a value from the Condition box, for example, Less than, Greater
Than, Equal To, Between.
Note The type of field being filtered changes the display of filtering
conditions.
e. Click OK.
Set the ProgramViewFilterProperties preference to specify the list of
attributes for schedule and schedule task objects displayed in the New
Program View wizard Filter dialog box in Schedule Manager.
f. Click Next.
This is the only time you can select the Schedules option. Because of the
system hierarchy, it must be selected as the highest grouping or not at all.
If you select a grouping condition, summary tasks are removed from the
Gantt chart.
b. To group date, time, and numerical columns by range, click the Range button
to the right of the corresponding Field Name box.
The Select Range dialog box appears. The From and To input boxes for this
dialog box vary depending on the type of box selected.
C. Click Done.
Note If a task lies in two ranges, it is grouped in the lower range. For
example, if a numerical column has the following ranges specified:
0–1, 1–2, 2–3, a task having value 1 could be in both the 0–1 and 1–2
ranges, but the Program view always places it under 0–1.
d. Under Cell background, select a background color for this grouping level.
A. Click the Cell background button that corresponds to the group.
B. When the Pick A Color dialog box appears, select a display color that you
want to represent for this group node in the program view.
C. Click OK.
B. Under Field Name, select the attribute you want rolled up.
If you select an attribute that you have not selected with the attribute
chooser, it is automatically added to the program view.
C. Under Rollup, select a rollup condition. For example, if you set Field
Name to xyz, you can select sum to add the values of this attribute for
each task in the group.
E. Click Done.
f. In the first Then By row under Field Name, select another attribute by which
you want to group information.
g. Repeat the process for the remaining attributes you want to group.
Note To delete a group by selection, select the blank from the list. If you
delete a group by selection, all groups under the one you delete are
also deleted.
5. Click Finish.
Teamcenter creates the new program view.
6. Either select the program view and double-click to send to Schedule Manager, or
right-click the program view and choose Send To→Schedule Manager.
Note You may not have to complete this step if the Open on Create check
box is selected.
23 Producing reports
23 Producing reports
• Trace link traceability reports let you display defining and complying
relationships for an object.
For information about traceability reports, see Tracing downstream and
upstream paths.
• A search compare report lets you compare search results to the results of other
searches or to the contents of your Home, My Worklist, or Newstuff containers.
For more information about search compare reports, see the Rich Client Interface
Guide.
• When you import Teamcenter objects you can generate a variety of reports.
For more information about import reports, see Import a Teamcenter object.
• When you work with embedded software, you can generate hardware and
software compatibility reports for electronic control units.
For more information about hardware and software compatibility reports, see
the Embedded Software Solutions Guide.
which provides report definitions for cross schedule tasking, baseline, and
overview data, let you generate Report Builder reports that can be formatted
using style sheets and that can reflect data in the context of one or more selected
items.
Note Teamcenter reporting and analytics (Reporting and Analytics) reports
can be imported into Teamcenter and then executed in My Teamcenter.
You can view the Reporting and Analytics dashboard by installing the
Dashboard application.
For more information, see Report Builder Guide.
For information about creating and managing Report Builder reports, see the
Report Builder Guide.
For more information about Schedule Manager reports, see the Schedule
Manager Guide.
For information about creating and managing Report Generator reports, see
the Report Generator Guide.
4. Click Next.
5. Fill in criteria for the query. Only the objects that match the query are placed
into the report.
• To select the display locale, select the locale from the Report Display Locale
list.
• If you want to choose the format for the report, click the arrow in the Report
Stylesheet box to select a stylesheet.
• If you want to save the report as a file, select Create Dataset and type a
name in the Dataset Name box.
6. Click Finish.
If you did not choose a style sheet, the report is displayed in your default XML
application. If you chose an HTML spreadsheet, the report is displayed in a
Web browser.
If you saved the report as a dataset, the report file is saved in your default Home
folder, for example, Newstuff.
2. Select a report.
Note If you choose a Reporting and Analytics report, only Finish is
available. When you choose Finish, you are logged on to the Reporting
and Analytics BuildNPlay application. Enter any additional filter
information and choose Show Report.
3. Click Next.
4. Fill in criteria for the query. Only the objects that match the query are placed
into the report.
5. If you want to choose the format for the report, click the arrow in the Report
Stylesheet box to select a style sheet.
6. If you want to save the report as a file, select Create Dataset and type a name in
the Dataset Name box.
7. Click Finish.
If you did not choose a style sheet, the report is displayed in your default XML
application. If you chose an HTML spreadsheet, the report is displayed in a
Web browser.
If you saved the report as dataset, the report is saved in your default Home
folder, for example, Newstuff.
After aligning the structures, you publish the occurrence data. You publish
occurrence data between source and destination absolute occurrences of two
representations. Teamcenter takes a snapshot of the source occurrence data and
creates a publish link to the destination occurrence. For example, you can publish
transform and shape information from a source design occurrence to a destination
part occurrence. If the source occurrence data is already published, Teamcenter
updates the snapshot with the new information.
A publish link may associate a source design occurrence with more than one target
part occurrence. For simplicity, the following procedures assume you are working
with a single target part occurrence, but multiple targets are permitted depending
on your product structure.
Caution Before aligning items, ensure that master forms are attached to all item
and item revision business objects. Otherwise, the alignment process
may be unsuccessful.
Note If you associate multiple targets, Teamcenter may automatically mark one of
the part occurrences as primary, based on an assessment of the maturity
of the design occurrence and its latest revision.
For information about checking design maturity level, see Getting Started
with Product Structure.
You create and view associations in My Teamcenter. You can also publish links in
Multi-Structure Manager.
For more details about publishing links in Multi-Structure Manager, see the
Multi-Structure Manager Guide.
For conceptual information about aligning designs and parts in structures, see
Getting Started with Product Structure.
• Drag the design revision onto the Representations folder of the part revision.
• Copy the design revision and paste it onto the Representations folder of the
part revision.
• Copy the design revision, select the Represented By relation of part revision,
and choose Paste Special.
Similarly, each design revision has a Representation For folder attached to it that
may contain part revisions. You can only view the contents of this folder; you cannot
paste a part revision into it to create an association.
Note When you revise a part, you can decide whether to carry forward associations
with design revisions in the Define Attached Objects pane in the Revise
wizard. By default, associations are carried forward; that is, the design
revisions in the Is Represented By relation, but you can edit the
association during the revision process.
Conversely, when you revise a design, the associations with part revisions
are not carried forward by default. You can change this behavior by adding
the TC_Is_Represented_By,Part Revision,LookLeft string to the
AutoCopyRel business constant. If the design is associated with multiple
revisions, only the latest mature revision is carried forward.
Your business processes determine whether a design revision is considered
mature.
For information about design maturity, see Getting Started with Product
Structure.
• To view the properties of all part revisions in the Representation For folder,
select the folder itself and choose View→Properties.
Tip Consider adding the IsPublishLinkSource, IsPublishLinkTarget, and
PublishedDataFrom columns to the properties table to allow easier
identification of publish links.
2. You add WheelPart1/A to the product and want to visualize this occurrence.
WheelPart1/A is already aware of its shape from the primary design
representation, so only its position in the product is necessary for correct
visualization.
4. You can now visualize the occurrence of WheelPart1 using the published
position information (transform) and the visualization information (JT file) from
the primary design representation.
In certain circumstances, the shape must also be published from the design
occurrence, including:
• When there are multiple representations of the part
For example, a flexible part may have alternate representations, each
of which is a different design. The SpringPart part may have three
different designs—NormalSpringD (the primary representation),
CompressedSpringD, and StrechedSpringD. If you publish
CompressedSpringD, you should choose to publish the transform and shape or
the primary representation (NormalSpringD) is shown.
3. Select a process variable type from the bar in the left of the window.
6. (Optional) Select the Open on Create check box to open the process variable
after it is created.
7. Click OK or Apply.
The system creates the process variable and displays it within the containing
object.
3. Select an item element type from the bar in the left of the window.
Note The system displays all defined item element types except those specified
for exclusion by the GDE_exclude_list preference.
6. (Optional) Select the Open on Create check box to open the item element after
it is created.
7. Click OK or Apply.
The system creates the item element and displays it within the containing object.
4. Click Next.
The system displays the connection information pane.
Note The Name and Description boxes may contain an initial value
determined by property rules implemented at your site. You can replace
this value, but you cannot specify a null value by clearing the box. If you
clear the box, the initial value is reapplied to the property when you
save the new connection.
7. Click Next.
The system displays a confirmation dialog box.
10. Click Next. The system displays the connection revision master form in the
right pane of the dialog box.
For more information about alternate identifiers, see Overview of alternate and
alias identifiers.
b. Choose one or more projects from the Projects for Selection list, and use the
arrow buttons to move them to the Selected Projects list.
b. Select the Open on Create check box to open the connection once it is created.
2. Choose File→New→Connection→Non-Revisable.
The system displays the New Link dialog box.
Nonrevisable connections are also referred to as GDELink objects. In the
context of wire harness modeling, nonrevisable connections are used to model
connectivity that is internal to an electrical connector or device.
6. (Optional) Select the Open on Create check box to open the connection after
it is created.
7. Click OK or Apply.
The system creates the connection and displays it within the containing object.
Create a signal
1. Select a containing object for the signal.
2. Choose File→New→Signal.
The system displays the New Signal dialog box.
4. Click Next.
The system displays the signal information pane.
Note The Name and/or Description boxes may contain an initial value
determined by property rules implemented at your site. You can replace
this value, but you cannot specify a null value by clearing the box. If you
clear the box, the initial value is reapplied to the property when you
save the new signal.
5. Enter a signal ID, revision, and name, or click Assign to automatically generate
the signal ID and revision identifiers. The Assign button is available if naming
rules and automatic generation are implemented for the selected object type.
Tip It may be necessary to resize the dialog box to view the Assign button.
b. Choose one or more projects from the Projects for Selection list, and use the
arrow buttons to move them to the Selected Projects list.
b. Check the Open on Create check box to open the signal once it is created.
A Glossary
A Glossary
accessor
Access Manager component that grants or denies privileges to clusters of users who
share certain common traits (for example, perform the same function or work on
the same project).
ACE
See access control entry (ACE).
ACL
See access control list (ACL).
action handler
Handler used to extend and customize workflow task actions. Action handlers
perform such actions as displaying information, retrieving the results of previous
tasks (inherit), notifying users, setting object protections, and launching applications.
See also task handler.
alias ID
Identifier of a part that is similar to the current part. You can use it as a substitute
part in the product structure. Contrast with alternate ID.
alternate ID
Different identifier for the current part, but one that represents the same part.
Different organizations and suppliers can have their own part numbers. With
alternate IDs, you are able to find the part you are looking for using your naming
scheme. Contrast with alias ID.
AM
See Access Manager (AM).
AP212
See STEP AP212.
application
Related functional elements collected and arranged in a software package, designed
to accomplish specified tasks. See also perspective.
approver
User who has a signoff in a workflow process regardless of role and group
membership. In Access Manager, the approver accessor is used to allocate privileges
that apply to all signoffs (for example, read access). See also RIG approver, role
approver, and group approver.
assembly
Compound object that is assembled from other objects and may add additional
information to their interpretation.
• In the context of an assembly, other assemblies are called subassemblies, while
noncompound objects are called components.
attribute
Named storage variable that describes an object and is stored with the object. Users
can search the database for objects using object attributes.
In an object, an attribute is a name/value pair; in the database, an attribute is a field.
bid package
Contains line items supplied to vendors to submit quotes.
BOM view
Teamcenter object used to manage product structure information for an item.
BVR
See BOM view revision (BVR).
change
Temporary or permanent change to a configuration, design requirement, or
documentation.
change order
Teamcenter object that references the problem, originating change requests,
solutions, and related information. A change order contains sufficient information to
incorporate the change.
change request
Teamcenter object that requests a change, reference the problem, proposed solutions,
and related information. A change request contains sufficient information to allow a
decision to proceed further with the change.
change type
Template of a change process. Change types are created by a system administrator
using the Business Modeler IDE.
Change Viewer
Teamcenter application used to manage the process of controlling changes to a
product’s definition and configuration. Change Viewer provides an auditable history
of the objects used in a process, making an object’s uses traceable. A site can use
Change Viewer to propose, incorporate, review, and approve changes. Change
Viewer can also be used to track and report change history and to notify members of
changes to their organization.
Closure Rule
Rule that controls the scope of the translation of data imported to and exported from
Teamcenter. Closure rules specify how the data structure is traversed by specifying
the relationships of interest and the actions to occur when these relationships are
encountered.
collaboration context
Teamcenter object that holds a collection of data contained in structure and
configuration contexts. This data allows you to capture multiple different
Teamcenter structures in one container. You can open a collaboration context in
the Multi-Structure Manager application, in Manufacturing Process Planner, or in
Part Planner. You can also use a collaboration context to collect data to share with
a third-party application. See also structure context.
Command Suppression
Teamcenter application that enables the system administrator to control the
display of menu and toolbar commands within Teamcenter applications. Command
Suppression allows suppressing the display of commands for an entire group
hierarchy or a specific role within the hierarchy, for entire groups of users, and for
users who are assigned a role within a group. It also allows suppressing the display
of specific commands on a designated menu or the display of entire menus.
CommercialPart
Business object type related to a Part object type by a structure relation. A
commercial part is made externally by a vendor who resells, builds, or designs and
builds the part for the OEM (original equipment manufacturer). Commercial parts
may be off-the-shelf market parts or custom-designed parts. A commercial part is
a part whose form, fit, and function may be satisfied by one or more vendor parts
that the OEM may source from one or more vendors.
component
• Objects used to build up an assembly or subassembly.
configuration rule
Rule that configures a structure. There are two kinds of configuration rules: revision
rule and variant rule.
connection
Object that defines the connectivity between two or more terminals in a physical
model.
container object
Any Teamcenter object used to hold other objects and organize product information.
For example, folders and items are container objects.
Content Management
Teamcenter application that enables users to manage SGML and XML information
stored in a Teamcenter database and publish documents in multiple formats
using SGML/XML editing and publishing tools. Content Management is used to
collect and publish content, storing the content as components that can be reused
in multiple publications, while links are maintained between components. The
application includes processes for structuring publications so that they can be stored,
published, and used for different purposes. Content Management also stores and
manages graphics for use in publications, provides content revision control, and can
incorporate Teamcenter workflows to facilitate the content development process.
dataset
Teamcenter workspace object used to manage data files created by other software
applications. Each dataset can manage multiple operating system files, and each
dataset references a dataset tool object and a dataset business object.
dataset tool
Teamcenter object that is the tool used to create or modify a dataset.
document
Subtype of an item that represents all revisions of a real-world document. This
item type supports documentation for products, processes, standards, and other
aspects of a business, typically from applications such as Microsoft Word, Microsoft
Excel, and so on.
document management
Management of real-world documents through the use of item revision definition
configuration (IRDC) objects to configure document management behavior. IRDC
simplifies user interaction with information and reduces the need for users to
understand the Teamcenter data model and relationship model. See also item
revision definition configuration (IRDC) objects.
Do task
Task template that includes the EPM-hold handler, which stops the task from
automatically completing when the task is started. This template has a customized
dialog box that allows administrators to set a check box to indicate when the task is
complete.
effectivity rule
Rule used to set effective dates on released products and processes with a released
status.
envelope
Teamcenter workspace object that represents a mail message sent by a Teamcenter
user. Envelopes can be used to send workspace object references as well as text
messages.
feature
Physical or geometric object associated with a product, component, or part.
Alternatively, a logical attribute of a product, component, or part. Examples: a weld
point, a signal, or a geometric pattern. A feature may be represented by a generic
design element (GDE) in a BOM. See also generic design element.
• FMS file caching enables placing the data close to the user, while maintaining a
central file volume and database store.
FMS
See File Management System (FMS).
folder
Graphical representation of an aggregation of objects, such as a group, class, or
subclass. For easy distinction in the class hierarchy, each of these aggregations has
a different type of folder icon associated with it: a group folder icon, a class folder
icon, or a subclass folder icon.
form
Teamcenter workspace object used to display product information (properties) in a
predefined template. Forms are often used to create an electronic facsimile of a
hardcopy form in Teamcenter. See also master form.
FSC
See FMS server cache (FSC).
FSC group
Group of server caches defined in the FMS master configuration file.
GDE
See generic design element.
group (Organization)
Organizational grouping of users at a site. Users can belong to multiple groups
and must be assigned to a default group.
group administrator
User with special maintenance privileges for a group.
group approver
User who is a signoff in a workflow process with a specific group of users. In Access
Manager, the group approver accessor is used in Workflow ACLs and matches the
signoff definition (that is, group) for the release level associated with the Workflow
ACL. The group approver accessor ensures that only signoffs are given privileges, not
a user who matches the group. See also approver, RIG approver, and role approver.
group preference
Teamcenter preference applying to an entire group.
harness
Assembly of insulated conductors formed to a predetermined pattern or
configuration; also called a wiring harness.
item
Workspace object generally used to represent a product, part, or component. Items
can contain other workspace objects including other items and object folders.
item relation
Description of an association between a Teamcenter item and a piece of information
that describes or is related to the item.
item revision
Workspace object generally used to manage revisions to items.
Lifecycle Visualization
Visualization components available in the rich client, the thin client, and as a
stand-alone application. A scalable solution for the viewing and analysis of 2D and
3D product data, Lifecycle Visualization is available in a number of configurations
to meet the requirements of different organizations.
ManufacturerPart
Business object type that is related to a CommercialPart object type by a Satisfies
relation. A manufacturer part, which can be obtained from one or more vendors, has
a part number assigned by the actual builder of the part. The ManufacturerPart
object is represented in the Teamcenter user interface by the term Vendor Part.
master form
Teamcenter workspace object used to display product information (properties) in
a predefined template. Master forms are used to display product information in
a standardized format.
master FSC
FMS server cache that reads the master configuration file directly from the FMS
master host. An FSC is configured either to read the master configuration file
directly from the master host or to download it from another FSC with access to it.
master object
Controlling object in a Multi-Site Collaboration network.
When an object is created and saved, that instance is the master object until it
is exported with transfer of ownership. There can be only one master object in a
Multi-Site Collaboration network, and only the master object can be modified. If
a master object is replicated, it cannot be deleted until all replicated objects are
deleted.
metadata
Object description in the Teamcenter database.
Multi-Site Collaboration
Teamcenter capability that allows the exchange of data objects among several
Teamcenter databases. Transfer of objects among databases is controlled by daemon
processes running on designated servers. Objects are replicated by exporting them
from their original database and importing them into the requesting database.
Configuration of Multi-Site Collaboration is optional.
named ACL
Named group of access controls. See also access control list (ACL).
named reference
File types that are managed by a dataset. Datasets are the only workspace objects
that use named references.
naming rule
Business rule that defines the naming conventions for the string property value in
different type objects. Naming rules can be attached to the following properties:
• Item ID, item revision ID, and name in item types
• Dataset name, ID, and revision number in dataset types
• Name form types
navigation pane
Rich client framework component that displays buttons of the applications available
for use in the rich client. Clicking the application button launches the application.
object-based protection
Use of access control lists to create exceptions to rules-based protection on an
object-by-object basis. Object access control lists are most useful for either granting
wider access or limiting access to a specific object.
object chooser
Displays objects appropriate for linking with another Teamcenter product. In
determining the objects to display, the object chooser considers the security rights of
the person accessing the Teamcenter product. See also remote workflow.
object launcher
Launches another Teamcenter product from a linked object. Each Teamcenter
product has an object launcher. See also remote workflow.
ODS server
See object directory services server.
ODS site
See object directory services site.
Organization
Teamcenter application that enables a system administrator to create and manage
critical Teamcenter files and database entries. It is the point of access for creating a
company’s virtual organization and for performing system administration activities
such as volume creation, maintenance, and site administration. Organization
enables creation and management of person, user, role, and group definitions;
definition of the hierarchical structure of the Teamcenter organization; management
of data volumes; and establishment and maintenance of Teamcenter sites.
owner
User that owns an object, initially the user who created it. Ownership can be
transferred from the owner to another user. An object owner usually has privileges
that are not granted to other users (for example, the privilege to delete the object).
owning group
Group that owns an object, usually the group of the user creating the object. Because
users commonly share data with other members of a group, additional privileges may
be granted to the owning group (for example, the privilege to write to the object).
owning site
Multi-Site Collaboration site where the master object resides. The owning site is the
only site where the object can be modified.
part
Business object type that can participate in a structure as an assembly or component,
with or without attached datasets. In Teamcenter, a business item managed in a
company’s part releasing system. Typically, the assembly or component is designed
and built by the OEM.
person
Definition containing real-world information about each Teamcenter user, such as
name, address, and telephone number. Person definitions are stored as simple text
strings so that they can be easily changed and updated. The name must be unique.
perspective
Container in the rich client user interface for a set of views and editors collected to
accomplish specified tasks. See also view.
PLM XML
Siemens PLM Software format for facilitating product life cycle interoperability
using XML. PLM XML is open and based on standard W3C XML schemas.
Representing a variety of product data both explicitly and via references, PLM
XML provides a lightweight, extensible, and flexible mechanism for transporting
high-content product data over the Internet.
preference
Configuration variable stored in a Teamcenter database and read when a Teamcenter
session is initiated. Preferences allow administrators and users to configure many
aspects of a session, such as user logon names and the columns displayed by default
in a properties table.
process structure
Hierarchy of manufacturing processes and operations with a sequenced relationship
that together describe how a related product is manufactured. Compare with
product structure.
process template
Blueprint of a workflow process defined by placing workflow and/or change
management tasks (for example, do, perform signoff, route, and checklist) in the
required order of performance. Additional process requirements, such as quorums
and duration times are defined in the template using workflow handlers.
product structure
Hierarchy of assembly parts and component parts with a geometric relationship
between them, for example, a bill of materials (BOM). Variant and revision rules
define the generic BOM. This BOM can then be loaded to display the configured
variant.
product view
Saved configuration of the assembly viewer, including the selection of objects, zoom
factor, rotation angle, and pan displacements.
project
Basis for identifying a group of objects available to multiple organizations, such as
project teams, development teams, suppliers, and customers for a particular piece
of work.
Project administrator
Teamcenter super user with unrestricted access to administer projects they create
using the Project application. A Project administrator creates, modifies, and deletes
project information and team members.
property rule
Business rule that allows an administrator to control access to and the behavior of
object properties.
pseudofolder
Special container in Teamcenter that stores and displays item and item revision
relations in My Teamcenter. See also smart folder.
published object
Object available to other sites in a Multi-Site Collaboration network. Publishing an
object creates a record in the ODS site database that can be read and searched by
other sites. Until an object is published, it can be seen only by the owning site.
Query Builder
Teamcenter application that enables a system administrator to create and maintain
customized searches for objects in the Teamcenter databases, both local and remote.
Saved queries are subject to standard object protection and can be accessed by users
through the search feature in My Teamcenter.
query form
Predefined query used in My Teamcenter to quickly search the database without
building a custom query. Query forms limit search criteria to boxes displayed in the
form. Accessing additional search capabilities requires building a custom query.
quorum
Number of users who must vote to approve a task for that task to be approved.
quote
Response to bid package line items.
registry file
Properties (.properties) file that contains the user-defined configuration settings
(keys and values) that are relative to how the application displays and performs
in the Teamcenter rich client. Each application registered in the rich client has a
.properties file known as a registry file.
relation
Description of an association between a Teamcenter object and a piece of information
that describes or is related to the object.
release status
Status associated with a workspace object when it is released through a workflow
process.
remote workflow
Teamcenter component that enables users to create links between Teamcenter
objects and objects in other Teamcenter products, such as Teamcenter portfolio,
program and project management. Users can then launch the linked Teamcenter
product from within either the rich client or the thin client.
render
Process that invokes the data translations specified for an item, such as a document
revision, to generate derived visualization data. Translate is an action on a dataset.
Render is an action taken on an object, such as a document. See also translate.
replicated object
Copy of master object residing at sites within a Multi-Site Collaboration network.
See also master object.
review task
Task template that includes the select-signoff-team and perform-signoffs subtasks.
Each subtask contains a unique dialog box for executing the process.
revision filter
Filter used to configure the display of items and item revisions based on established
revision rules.
revision rule
Parameter set by the user that determines which revision of an item is used to
configure product context.
rich client
Java-based user interface to Teamcenter installed on user workstations. The rich
client accesses Teamcenter databases using a remote or local server. Compare to
thin client.
RIG approver
User who is a signoff in a workflow process with a specified role and group. In
Access Manager, the RIG approver accessor is used in Workflow ACLs and matches
the signoff definition (that is, role in group) for the release level associated with
the Workflow ACL. This accessor ensures that only signoffs are given privileges,
not a user who matches the role in group. See also approver, group approver, and
role approver.
role
Function-oriented cluster of users that models skills and/or responsibilities. The
same roles are typically found in many groups. In Access Manager, role is an accessor
used to grant privileges to all users with the same skills and/or responsibilities
regardless of project.
role approver
User who is a signoff in a workflow process with a specific role. In Access Manager,
the role approver accessor is used in Workflow ACLs and matches the sign-off
definition (that is, role in group) for the release level associated with the Workflow
ACL. This accessor ensures that only signoffs are given privileges, not a user who
matches the role. See also approver, group approver, and RIG approver.
role in group
Specific role in a specific group. In Access Manager, role in group is an accessor
used to grant privileges to all users with the same skills and/or responsibilities
in the same group.
role preference
Teamcenter preference applying to an entire role.
root
Starting point of a hierarchy. Hierarchies are usually displayed as hanging trees
with the root of the structure at the top and the leaves at the bottom.
rule handler
Handler used to integrate workflow business rules into Enterprise Process Modeling
processes at the task level. Rule handlers attach conditions to an action. See also
task handler.
rules-based protection
Conditions or rules that control who can or cannot access objects. These rules are
global (that is, they affect the entire Teamcenter site) and are enforced by the Access
Manager. These rules are defined by a system administrator.
rule tree
Access Manager component the system administrator uses to grant users access to
Teamcenter objects. It is a tree of rules and access permissions that when processed
determines the access that each user has to a specified object.
Security Services
Services that eliminate prompts for logon credentials when users switch Teamcenter
products within a user session. Authentication is performed by an external identity
service provider, such as lightweight directory access protocol (LDAP), instead of
the Teamcenter product. At a site that deploys multiple Teamcenter products and
Security Services, users log on once to access all participating Teamcenter products.
signal
Physical representation of a message or an information flow being generated,
processed, or conveyed within an electrotechnical system.
site
Individual installation of Teamcenter comprising a single Teamcenter database,
all users accessing that database, and additional resources such as hardware,
networking capabilities, and third-party software applications (tools) required to
implement Teamcenter at that site.
site ID
Unique identifier of a Teamcenter site. The site ID is used to generate internal
identifiers for Teamcenter objects that must be unique throughout an enterprise.
Once established, site IDs should not be modified.
site name
Unique name of a Teamcenter site stored in the database as a user-defined character
string.
site preference
Teamcenter preference that applies to the entire site.
smart folder
Pseudofolders configured in a hierarchical structure used to apply hierarchical levels
of filtering to project data. See also pseudofolder.
STEP AP212
Standard for the Exchange of Product Model Data (STEP) for the Industrial
Automation Systems and Integration – Product Data Representation and Exchange
international standard (ISO 10303). This standard provides a framework through
which industries can exchange and share product information within and between
enterprises. AP212 is an application of this standard and describes the information
necessary to customize electrotechnical products.
structure context
BOM or assembly structure contained in a collaboration context. The structure
context can contain occurrence groups, items, and item revisions. See also
collaboration context.
Structure Manager
Teamcenter application that enables creation of generic product structures that can
be configured to show the product structure that is in production, effective on a
certain date, used by a particular customer, and so forth. Structure Manager enables
creation and modification of a product structure and its associated occurrence data,
display of a product structure in a multilevel indented format, and viewing graphics
tightly coupled to the structure for easy identification of a component by location in
the structure or in the embedded viewer.
subscription
Combination of a workspace object and an event for which a Teamcenter user
requests notification of occurrence. Teamcenter notifies a subscribed user when the
event occurs in association with the object. Users can subscribe to objects from
Teamcenter applications, such as My Teamcenter and Structure Manager.
Subscription Manager
Tool used to find, delete, and modify active subscriptions.
system administrator
Teamcenter user who is a member of the system administration group.
task (workflow)
Fundamental building block used to construct a process. Each task defines a set of
actions, rules, and resources used to accomplish that task.
task handler
Small Integration Toolkit program or function. Handlers are the lowest level
building blocks in Enterprise Process Modeling. They are used to extend and
customize tasks. There are two kinds of handlers: action handlers and rule handlers.
See also action handler and rule handler.
task template
Blueprint of a workflow task.
Teamcenter option
See preference and user preference.
thin client
Teamcenter user interface that provides a streamlined browser-based view of product
information stored in a Teamcenter database. The thin client is configured in the
Web tier, which creates and serves its Web pages to the client. Compare to rich client.
transfer mode
Objects composed of rules that configure PLM XML import and export operations.
Transfer mode allows users to import and export data with little knowledge other
than the name of the transfer mode object.
translate
Process that converts data from one file format into another file format. In the
context of Teamcenter document management, source data is converted to derived
visualization data formats. The conversion is based on available translators.
Translate is an action on a dataset. Render is an action taken on an object, such as a
document. See render.
unpublished object
Object not available to other sites in a Multi-Site Collaboration network. Users
can unpublish previously published objects so they are once again accessible only
to the owning site.
user
Definition that is the mechanism by which Teamcenter identifies and interacts with
each user. User definitions contain a name (derived from the person definition), user
ID, operating system name, and password.
user preference
Teamcenter preference applying to a specific user.
variant condition
• Rules applicable to one component in a product structure.
variant rule
Collection of option values used in determining the variant of the BOM to be
configured (for example, car type = GLS, engine = 1200, gearbox = manual).
vendor
Business object type; provider of parts or services. In Teamcenter, a vendor can take
on one or more roles. Role definitions are not fixed in the data model, and can be
adjusted to meet customer business mode. Vendor roles, for example, can include:
• Distributor: Resells, but does not make, parts.
vendor management
Software functionality used to model vendor contributions to a product by letting
users capture information about the vendors and the vendor parts they provide to
satisfy the form, fit, and function of commercial parts.
VendorPart
Business object type that is related to a CommercialPart object type by a Satisfies
relation. A vendor part can be obtained from one or more vendors, but the actual
builder of the part assigns a part number.
view
Software element in a rich client user interface perspective. It provides the ability to
navigate hierarchies of information, display information about selected objects, open
an editor, or display properties. See also perspective.
work context
Object containing user, group, role, and project requirements for a particular task.
Work contexts streamline the definition of the correct user settings required to
perform tasks. For example, a user typically assigned three types of tasks can create
three work contexts reflecting the required group/role settings. Rather than logging
out and logging back in with the required group/role settings, right-clicking a task
displays the user’s defined work contexts. Selecting the appropriate work context
automatically changes the user’s group/role settings. Work contexts can also define
the current project, if project functionality is used at the site.
workflow
Automation of the concept that all work flows through one or more business
processes to accomplish an objective. Using workflow, documents, information, and
tasks are passed between participants during the completion of a particular process.
Workflow Designer
Teamcenter application that enables administrators to graphically design workflow
process templates, incorporating company business practices and procedures into
the templates. Teamcenter users initiate workflow processes using these templates.
Workflow Viewer
Teamcenter application that enables users to view the progress of a workflow
process. Users are not required to be participating members of the process being
viewed. Depending on preference settings, Workflow Viewer also allows ad hoc
process modification. See also ad hoc process modification.
working revision
Revision that can be changed by a user with write privileges. No record of
intermediate states of a working revision is maintained by Teamcenter.
world
All users regardless of group or role.
Baseline menu command . . . . . . . . . . . 2-28 Check-Out and Edit button . . . 3-1, 5-28, 8-6
Baseline_auto_remote_checkout_allowed Checkin and checkout, data . . . . . . . . . 10-1
preference . . . . . . . . . . . . . . . . . . . . . 5-27 Checkout
Basic tasks, My Teamcenter . . . . . . . . . . 2-1 Canceling . . . . . . . . . . . . . . . . . . . . 10-7
Between objects . . . . . . . . . . . . . . . . . 3-15 Defining checkout directory . . . . . . . . 10-2
BidPackage business object . . . . . . . . . . 7-4 Differences between implicit and
BidPackageLineItem business object . . . . 7-4 explicit . . . . . . . . . . . . . . . . . . . . 10-3
Bills of materials Explicit . . . . . . . . . . . . . . . . . . . . . . 10-2
Exporting . . . . . . . . . . . . . . . . . . . 11-15 Implicit . . . . . . . . . . . . . . . . . . . . . . 10-2
Importing . . . . . . . . . . . . . . . . . . . 11-15 Owner . . . . . . . . . . . . . . . . . . . . . . . 10-4
View variant conditions . . . . . . . . . 11-16 Transferring . . . . . . . . . . . . . . . . . . 10-7
BOM view revision, New . . . . . . . . . . . 2-20 Checkout history . . . . . . . . . . . . . . . . . 10-7
Briefcase Choice property value . . . . . . . . . . . . . 3-12
Exporting . . . . . . . . . . . . . . . . . . . . 11-1 Classifying
Importing . . . . . . . . . . . . . . . . . . . . 11-1 Commercial parts . . . . . . . . . . . . . . 7-14
Business Modeler IDE extensions to copy Vendor parts . . . . . . . . . . . . . . . . . . 7-14
validation results . . . . . . . . . . . . . . 12-15 Close menu command . . . . . . . . . . . . . 2-18
Business Object (Other), New . . . . . . . . 2-22 Close Perspective command . . . . . . . . . 2-33
Business object, creating . . . . . . . . . . . . 5-6 Collaboration context, capturing in
Business objects . . . . . . . . . . . . . . . . . . 7-3 IDC . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
BidPackage . . . . . . . . . . . . . . . . . . . . 7-4 Collaboration Context, New . . . . . . . . . 2-20
BidPackageLineItem . . . . . . . . . . . . . 7-4 Columns
CommercialPart . . . . . . . . . . . . . . . . . 7-4 Inserting in table panes . . . . . . . . . . 3-10
CompanyContact . . . . . . . . . . . . . . . . 7-3 Removing . . . . . . . . . . . . . . . . . . . . 3-10
CompanyLocation . . . . . . . . . . . . . . . 7-3 Repositioning . . . . . . . . . . . . . . . . . . 3-9
Quote . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Commands
Vendor . . . . . . . . . . . . . . . . . . . . . . . 7-3 Assign . . . . . . . . . . . . . . . . . . . . . . . 2-32
VendorPart . . . . . . . . . . . . . . . . . . . . 7-3 Autoset Current WorkContext . . . . . . 2-32
Buttons, toolbar . . . . . . . . . . . . . . . . . 2-40 Complete . . . . . . . . . . . . . . . . . . . . . 2-32
Perform . . . . . . . . . . . . . . . . . . . . . . 2-32
C Promote . . . . . . . . . . . . . . . . . . . . . 2-32
Resume . . . . . . . . . . . . . . . . . . . . . . 2-32
CAD file translation . . . . . . . . . . . . . . 9-11 Stand-in . . . . . . . . . . . . . . . . . . . . . 2-32
CAE items Start . . . . . . . . . . . . . . . . . . . . . . . . 2-32
Geometry . . . . . . . . . . . . . . . . . . . . . 5-1 Suspend . . . . . . . . . . . . . . . . . . . . . 2-32
Model . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Undo . . . . . . . . . . . . . . . . . . . . . . . 2-32
New . . . . . . . . . . . . . . . . . . . . . . . . 2-22 Commercial parts
Cancelling checkout requests . . . . . . . . 10-7 Classifying . . . . . . . . . . . . . . . . . . . 7-14
Change notification Creating . . . . . . . . . . . . . . . . . . . . . . 7-5
Objects . . . . . . . . . . . . . . . . . . . . . . 15-3 CommercialPart business object . . . . . . . 7-4
Status changes . . . . . . . . . . . . . . . . 15-3 Company contacts
Change ownership menu command . . . . 2-26 Creating . . . . . . . . . . . . . . . . . . . . . 7-11
Change, New . . . . . . . . . . . . . . . . . . . 2-22 Deleting . . . . . . . . . . . . . . . . . . . . . 7-13
Changing Editing . . . . . . . . . . . . . . . . . . . . . . 7-12
Object ownership . . . . . . . . . . . . 4-9–4-10 Company location properties, editing . . 7-11
Check in an object . . . . . . . . . . . . . . . . 10-5 Company locations
Check In/Out shortcut menu Creating . . . . . . . . . . . . . . . . . . . . . . 7-8
command . . . . . . . . . . . . . . . . . . . . . 2-38 Deleting . . . . . . . . . . . . . . . . . . . . . 7-11
Check Index Status menu command . . . 2-31 CompanyContact business object . . . . . . 7-3
Check out an object . . . . . . . . . . . . . . . 10-4 CompanyLocation business object . . . . . . 7-3
Check out objects before export, option Compare Contents menu command . . . . 2-31
Export to Word dialog box Compare Contents shortcut menu
Word export procedure . . . . . . . . 11-5 command . . . . . . . . . . . . . . . . . . . . . 2-40
Check-In/Out menu command . . . . . . . 2-27 Comparing forms . . . . . . . . . . . . . . . . 16-4