Академический Документы
Профессиональный Документы
Культура Документы
Publication Number
PLM00031 J
Proprietary and restricted rights notice
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Localization button
Clicking the Localization button displays the Language Translations dialog box
that lists existing translation values.
The presence of the Localization button indicates the dialog box content can
be localized. For example, if the master locale is set to English, you can add a
translation for an employee information query. Using the Localization button, you
can perform the following tasks:
• View the existing localization text.
• Add a translation value for a new locale without altering the master value of
the property.
• Remove a translation value without altering the master value of the property.
For more information about the Localization button, see the Localization Guide.
Character array
Date
Date array
Double
Float array
Integer
Integer array
Logical
Logical array
Short
Short array
String
String array
Typed reference
Untyped reference
External reference
Note
Note array
Typed relation
Untyped relation
Class
Element Description
Boolean Rules The Boolean rules (AND/OR) are used to combine clauses to
create a custom query. When you use AND clauses together,
both must be satisfied to return a match (both this clause
and that clause). When you use OR clauses together, either
can be satisfied to return a match (either this clause or that
clause). Keyword clauses do not support the OR rule.
Note The indented search feature only supports AND
clauses.
For more information about the indented search
feature, see the Rich Client Interface Guide.
Attributes The selected database attribute displays in this box.
User Entry L10N Key Specifies the localization key used to look up user entry
names. The localization key-value pairs are defined in the
qry_user_entry_names_locale.xml file. The value in this
column can be modified and must be unique within the
search criteria definition.
User Entry Name Displays the query box names as they appear in
the search form. The user name is the value of the
localization key entered in the User Entry L10N Key
column. If the key-value pair is not defined in the
qry_user_entry_names_locale.xml file, the user entry
name is the same as the key entered in the User Entry L10N
Key column. The value in this column cannot be modified.
Logical Operators Matching values can be equal to, not equal to, less than,
or greater than the value specified in your search clause.
Matching values can also be null or not null. These
conditions are called logical operators. You must specify one
of the following logical operators in each search clause.
Logical
operator Description
= Equal to.
!= Not equal to.
> Greater than.
>= Greater than or equal to.
Element Description
< Less than.
<= Less than or equal to.
IS_NULL Indicates that the reference
attribute value must be blank (not
set).
IS_NOT_NULL Indicates that the reference
attribute must have a value.
You can search for ranges of values using the >, >=, <, <=
logical operators or invert search criteria using the != logical
operator.
Default Value Default values can be specified for the query clauses.
Default values can be entered as a text string or selected
from the associated list of values, where applicable. After
the value is set, press Enter to save the default value.
This box is required only when you do not specify the
user entry name, unless the logical operator IS_NULL or
IS_NOT_NULL is used.
The following keyword variables can be used to display
default values in the query form:
• $USERID
• $USERNAME
• $GROUP
• $TODAY
Note Siemens PLM Software recommends the following when using the Search
Criteria pane:
• For each clause, make certain the User entry L10N key value is unique.
• When you use AND and OR clauses together, the search result displays
unexpected results. Therefore, use the AND operator (rather than the
OR operator) and place multiple default values in the Default value
column separated by a semicolon, as shown in the following example.
Element Description
Attribute The selected database attribute appears in this box.
User Entry L10N Key Specifies the localization key used to look up user entry
names. The localization key-value pairs are defined in the
qry_user_entry_names_locale.xml file. The value in this
column can be modified and must be unique within the
search criteria definition.
User Entry Name Displays the query box names as they appear in
the search form. The user name is the value of the
localization key entered in the User Entry L10N Key
column. If the key-value pair is not defined in the
qry_user_entry_names_locale.xml file, the user entry
name is the same as the key entered in the User Entry L10N
Key column. The value in this column cannot be modified.
Order By Specifies the sort order or overrides a default sort order
defined for a saved query. Each attribute can be set to
arrange in either Ascending or Descending order.
For more information about using the Order By tab, see Specify sort order for a
saved query.
If your site has online help installed, you can access application and view help from
the rich client Help menu or by pressing F1.
For more information about rich client perspectives and views, see the Rich Client
Interface Guide.
• Referenced-by queries
Once created, query definitions can be exported and saved as XML files that can be
shared with other Teamcenter sites. Conversely, query data saved in XML files can
be imported into Teamcenter. The XML files are parsed and verified before the
data is imported.
For more information, see Importing and exporting query definitions.
• Export query definitions saved as XML files, which can be shared with other
Teamcenter sites.
For more information about these tasks, see Creating customized searches using
Query Builder, Managing the query hints file, and Importing and exporting query
definitions.
Create queries
1. Click the Clear button to remove existing information from the Query
Builder boxes.
6. Specify the desired search class by selecting an entry from this dialog box.
Tip You can significantly expand or narrow the focus of your query depending
on the class you select. It is best to limit the search to the lowest possible
class in the hierarchy.
To locate a class, type the class name (or partial name and wildcards) in the box
at the top of the dialog box, and click the Search button . The number of
classes matching your search are displayed at the bottom of the dialog box, and
the first result is highlighted in the tree.
To navigate through the results:
8. Double-click to select at least one of the attributes in the Attribute Selection tree.
Direct attributes of the class are displayed in the tree. Reference classes and
attributes can be accessed by double-clicking the Referenced By node in the
attribute tree.
9. Specify the desired search criteria. You must specify the following required
search criteria boxes:
• Attribute
• Logical operators
4. Click the Show Hints button in the saved query properties pane.
The system displays the hints pane.
5. Click the Choose Hint button located at the top of the hint pane.
The system displays the choose hint pane containing the directory of query hints.
6. Expand the Item Queries folder, select Item to Item Master Form, and click OK.
The dialog box closes and the system displays the selected hint in the hint pane.
The first entry in the hint is the base class, followed by the traversal steps, ending
with the attribute of the item master form class that is added to the query clause.
8. To locate the Item class, type Item in the search box and then click the Search
button .
The Item class is highlighted in the schema tree of the Class/Attribute Selection
dialog box.
10. The Item to Item Master Form hint traverses the schema to the project_id
attribute from the Item Master Form. To add this attribute to the query
definition, click the Add Clause to Table button.
The system adds the clause to the table. For more information, see Using search
criteria clauses.
11. If you want to search for project_id attribute of the Item Master Form, click
the Find in Tree button.
The system expands the tree in the Attribute Selection pane to display the
Project ID attribute.
12. Double-click any of the other attributes to add them to the clause table.
You can use other hints to add more clauses to the query table by selecting a new
hint and repeating the previous steps.
Note Only those hints applicable to the selected search class are available in
the choose hint pane.
3. Select Keyword Search Query from the Modifiable Query Types list.
4. Click the Search Class button to select the target class for the query.
The Class Selection dialog box displays the POM schema in tree format.
6. Add the Keywords attribute to the Search Criteria table by either double-clicking
the attribute in the tree or by selecting it in the tree and clicking the Add button
.
The system displays the attribute (tc_fts_keyword) and default operator (=)
in the table.
The system adds the query to the saved queries tree. The query form is also
available in the System Defined Searches list in My Teamcenter.
For more information about searching the Teamcenter database using saved
queries, see the Rich Client Interface Guide.
3. Change the information in the Description box, Search Class box, and/or Search
Criteria table columns.
4. Click the Search Class button to select the target class for the query.
The Class Selection dialog box displays the POM schema in tree format.
7. Click the Display Settings button and select All Attributes. Add the Release
Status attribute to the Search Criteria table by selecting it in the tree and
clicking the Add button .
The attribute and default operator (IS_NULL) are displayed in the table.
8. Change the operator from IS_NULL to IS_NOT_NULL by clicking the right corner
of the operator cell and selecting IS_NOT_NULL from the list.
4. Click the Search Class button to select the target class for the query.
The Class Selection dialog box displays the POM schema in tree format.
Dataset
Revision Anchor [ RevisionAnchor ]
ref_names
Tool Used [ Tool ]
Classification
ref_types
Format
References
8. Click the Search Class button to select the referencing class for the
query.
The Class Selection dialog box displays the POM schema in tree format.
10. Expand the WorkspaceObject class and select the ItemRevision class by
highlighting it and closing the dialog box.
The referencing class and its attributes are displayed in the Class Attribute
Selection dialog box.
Note Only those attributes that may reference the objects of the class being
queried, in this case the Dataset class, are displayed in the dialog box.
12. Select the attributes of the referencing class on which you want to build query
clauses. In this case, locate and double-click the Name attribute. The attribute
is displayed in the Search Criteria table. Note that the display name of the
attribute is ItemRevision←IMAN_specification.object_name. The ¬ symbol
indicates a reversed-reference relationship.
13. Type a key name in the User Entry Key box. This makes the User Entry Key
unique when you perform a query from the My Teamcenter search pane.
The system adds the query to the saved queries tree. The query form is also
available in the System Defined Searches list in My Teamcenter.
For more information about searching the Teamcenter database using saved
queries, see the Rich Client Interface Guide.
• Define a query that restricts the search to Bolt but makes a subset of Bolt
attributes (for example, Length and Radius) available as the search criteria.
• Define a query that restricts the search to item and makes item attributes and
bolt attributes through the IMAN_classification reference be available as
the search criteria.
1. Select a Classification class from the class schema using the Class Selection
dialog box, accessed by clicking the Search Class button .
Note When creating a saved query, the search class must have at least
one own attribute (an attribute not inheriting from its parent class).
Otherwise, the search returns objects from its parent class, rather than
the specified class.
The Classification hierarchy used by Query Builder is exactly the same as the
Classification hierarchy used in the Classification applications. The highest level of
the hierarchy represents groups that do not contain attributes and cannot be used
in a search. These group nodes are shown with a different icon. The nodes below
the group level correspond to a Classification class. The class level nodes can
be used to build saved queries.
After a Classification attribute is selected from the Attribute Selection tree, its
internal attribute ID is shown as Attribute name in the Search Criteria table while
its attribute display name is shown as User Entry Name in the Search Criteria table.
You can modify the user entry name if required.
A Classification object (ICO) is attached to a Teamcenter object through the
Tc_classification relationship. This Tc_classification relationship is shown as one
of the attributes for a Teamcenter class whose instances are classified. For such
a Teamcenter class (for example, item and item revisions), you can expand its
Tc_classification attribute in the Attribute Selection tree to access the Classification
attributes. In doing so, you build a saved query that combines Classification
attribute search criteria and Teamcenter attribute search criteria.
Note When you double-click the Tc_classification attribute, only the Classification
hierarchy is shown in the Class Selection dialog box to enable you to select
a Classification class and use its attributes to build query clauses.
1. Create a query.
2. Next to the Search Criteria section, click the Order By tab, and then select an
attribute to display the Order By tab.
3. Click the Search Class button to select the target class for the query.
The Class Selection dialog box displays the POM schema in tree format.
5. Expand the WorkspaceObject class and select the Folder class by selecting
it and closing the dialog box.
Folder is displayed on the Search Class button, and the Folder class and its
attributes are displayed in the Attribute Selection pane.
Managing queries
You can manage queries by either modifying them or deleting them.
Modify a query
1. Select a query from the saved queries tree.
Information about that query is displayed in the boxes on the right side of the
window.
2. Change the information in the Name, Description, or Search Class box, and/or
Search Criteria table columns.
Delete a query
1. Select a query from the saved queries tree.
3. Click Yes to delete the query from the database and remove it from the saved
queries tree.
User
Nationality
mailbox [ Folder ]
Person [ Person ]
TTCDate
• Parent classes.
When all attributes for the Search Class are displayed, inherited attributes are
also displayed in the Attribute Selection box.
Attribute Selection box
User
Owning Site [ POM_imc ]
pid
object_properties
lsd
timestamp
Status
user_data_source
• Reference classes.
When classes related to the Search Class are displayed, the reference class
attributes are also displayed in the Attribute Selection box.
Attribute Selection box
Nationality
Mailbox [ Folder ] Reference class
Person [ Person ] Reference class
Owning Site [ POM_imc ]
pid
object_properties
lsd
timestamp
• Referenced by classes.
When classes related to the Search Class are not displayed, the Referenced By
attribute is used to locate additional reference classes to display in the Attribute
Selection box.
Attribute Selection box
• Attribute user interface display names or the attribute real database names.
Display Settings
Class Attributes
All Attributes
Display Names
Real Names
• The attributes with the plus symbol refer to another class in the class
structure, which may have direct attributes, or may have more attributes with
plus symbols.
Display Settings
Class Attributes
All Attributes
Display Names
Real Names
3. Populate the Attribute Selection list with the attributes required to build the
search criteria. The attributes are either class attributes, parent class attributes,
or reference class attributes. Reference classes are classes related to the search
class. To list reference class attributes:
• Double-click references with the plus symbol to list more attributes or
to open the Class Selection Dialog. Double-click a class from the Class
Selection Dialog to add the class and its attributes to the Attribute Selection
list.
4. Double-click attributes without the plus symbol to directly add them to the
Search Criteria table.
• QRY_query_name_SortOrder
Determines the sort order of query results. This preference must be used in
conjunction with the QRY_query_name_SortKeys preference, which determines
the class attributes used to sort query results.
• TC_QRY_xxx_REVRULE
Specifies the revision rule applied to search results for searches against
ItemRevision and its subclasses.
• TC_QRY_search_by_rev_rule
Locates the latest item revisions based on revision rules. For example, when
querying to locate the latest working item revision, you can set this preference
to Latest Working before conducting your query.
• TC_QRY_display_latest_dataset_only
Displays only the latest version of dataset objects when you set this preference to
1 before conducting your query.
• Search_result_load_all_limit
Specifies the maximum number of loaded searches. The default value is 400.
The Search Criteria table example finds users that meet the person name and user
ID criteria values entered by the user.
Double-click an attribute in the Attribute Selection box to add it to the Search
Criteria table.
The combination of the User Entry L10N Key and Default Value elements dictate
how the search criteria is presented to the user.
1. The User Entry L10N Key has a value and the Default Value is blank.
Result: The attribute displays in the saved query for the user to populate.
2. The User Entry L10N Key has a value and the Default Value has a value.
Result: The attribute displays in the saved query with the default value. The
user can change the default value in the saved query pane.
3. The User Entry L10N Key is blank and the Default Value has a value.
Result: The attribute does not display in the saved query. The value is
evaluated in the query.
Note When the User Entry L10N Key is blank, the Default Value must have
a value.
1. The user ID of the owning user of the WorkspaceObject is the user logged
on and executing the query.
Result: The attribute displays the user ID of the current user in the saved
query. The query looks for workspace objects owned by the value of the user ID.
2. The name of the owning group of the WorkspaceObject is the current group of
the user logged on and executing the query.
Result: The attribute displays the group name of the current user in the saved
query. The query looks for workspace objects owned by the value of the group
name.
2. Click the Gain Precedence button to move the clauses up or click the Lose
Precedence button to move the clauses down.
3. Continue clicking the buttons until the clauses are moved to the position you
want.
• Hints
Contain four fields: name, description, search class, and query clause. The
hint name is the text you see in the hint tree. The description is the tool tip
displayed when the user hovers the mouse over the hint. The search class is
the origin of the query, and the query clause is the hint that provides the path
to the attribute.
The simplest way to obtain the query clause is to copy it from the Query Builder
Search Criteria table from an existing query and paste it into the XML file.
<ImanQueryHintFile>
<!-- =============================================== -->
<!-- ========= item hints ========================== -->
<!-- =============================================== -->
<folder name="Item Queries" description="Query Hints for Item Relationships">
<hint name="Item to Item Revision" description="adding item revision criteria to the item
search" class="Item" hint_text="ItemRevision<-items_tag.item_revision_id"/>
<hint name="Item to Item Master Form" description="adding master form criteria to the item
search" class="Item" hint_text="Form:IMAN_master_form.ItemMaster:data_file.project_id"/>
<hint name="Item to Item Revision Form" description="adding criteria from an item
revision master form into the item search" class="Item"
hint_text="ItemRevision<-items_tag.Form:IMAN_master_form_rev.ItemVersionMaster:data_file.project_id"/>
<hint name="Item to IMAN_Specification" description="adding criteria from an underlying
item revision’s dataset to the item search" class="Item"
hint_text="ItemRevision<-items_tag.Dataset:IMAN_specification.format_used"/>
<hint name="Item to IMAN_Aliasid" description="adding criteria from an associated alias
identifier to the item search" class="Item"
hint_text="Alias:IMAN_aliasid.alias_id"/>
</folder>
<!-- =============================================== -->
<!-- ========= item revision hints ================= -->
<!-- =============================================== -->
<folder name="Item Revision Queries" description="Query Hints for Item Revision Relationships">
<hint name="Item Revision to IMAN_Specification" description="adding dataset criteria
to the item revision search" class="ItemRevision"
hint_text="Dataset:IMAN_specification.format_used"/>
<hint name="Item Revision to Item Revision Master Form" description="adding master
form criteria to the item revision search" class="ItemRevision"
hint_text="Form:IMAN_master_form_rev.ItemVersionMaster:data_file.project_id"/>
<hint name="Item Revision to Item" description="adding item criteria to the item revision
search" class="ItemRevision" hint_text="items_tag.item_id"/>
</folder>
<!-- =============================================== -->
<!-- ========= dataset hints ================= -->
<!-- =============================================== -->
<folder name="Dataset Queries" description="Query Hints for Dataset Relationships">
<hint name="Specification Dataset to owning Item Revision" description="adding item revision
criteria to the specification dataset search" class="Dataset"
hint_text="ItemRevision<-IMAN_specification.object_name"/>
<hint name="Dataset with unknown relation to Item Revision" description="adding item
revision criteria to the dataset search" class="Dataset"
hint_text="ImanRelation<-secondary_object.ItemRevision:primary_object.object_name"/>
</folder>
<!-- =============================================== -->
<!-- ========= folder hints ================= -->
<!-- =============================================== -->
<folder name="Folder Queries" description="Query Hints for Folder Relationships">
<hint name="Contents to owning Folder" description="adding folder criteria
to the content object search" class="WorkspaceObject"
hint_text="Folder<-contents.object_name"/>
<hint name="Folder to Contents" description="adding content object criteria
to the folder search" class="Folder" hint_text="contents.object_name"/>
</folder>
<!-- =============================================== -->
<!-- ========= product structure hints ================= -->
<!-- =============================================== -->
<folder name="Product Structure Queries" description="Query Hints for Product
Structure Relationships">
<hint name="Assembly to child Components (Imprecise Structure)"
description="adding child component item criteria to the assembly item
revision search" class="ItemRevision"
hint_text="structure_revisions.PSOccurrence<-parent_bvr.Item:child_item.item_id"/>
<hint name="Child Components to Assembly (Imprecise Structure)"
description="adding assembly item
revision criteria to the child component item search" class="Item" hint_text=
"PSOccurrence<-child_item.parent_bvr.ItemRevision<-structure_revisions.object_name"/>
<hint name="Assembly to child Components (Precise Structure)" description="adding child
component item revision criteria to the assembly item revision search" class="ItemRevision"
hint_text="structure_revisions.PSOccurrence<-parent_bvr.ItemRevision:child_item.object_name"/>
<hint name="Child Components to Assembly (Precise Structure)" description="adding assembly
item revision criteria to the child component item revision search" class="ItemRevision" hint_text
="PSOccurrence<-child_item.parent_bvr.ItemRevision<-structure_revisions.object_name"/>
</folder>
<!-- =============================================== -->
<!-- ========= workspace object hints ============== -->
<!-- =============================================== -->
<folder name="Workspace Object" description="Query Hints for Workspace Objects">
<hint name="Contents to owning Folder" description="adding folder criteria to the content
2. Click the Browse button to locate the XML file containing the definition
you want to import.
The system displays the Read Query Definition dialog box.
5. Click OK to load the query in the saved query tree and dismiss the Import dialog
box.
5. Type a name in the File name box, including the .xml file extension.
5 Application notes
5 Application notes
Attribute index
If there are more than 5,000 instances of the search class to be found, you must add
an index to the attribute on which you are searching. Doing this helps the search
performance. However, if the table is very small (that is, the class has less than 500
instances), a full-table scan is more effective than an index scan.
If you do not create an index on an attribute, a full-table scan of the Oracle table
automatically takes place. This affects the System Global Area (SGA) of the Oracle
server. SGA is the portion of memory where Oracle caches the queries and their
execution plan. You can use the following command to add an index to an attribute:
$TC_BIN/install -add_index
6 Best practices
6 Best practices
Best practices
Best practices have been identified for Query Builder. Use these procedures to
address common tasks, such as exporting saved searches to another Teamcenter
installation.
3. Click the Search Class button to select the target class for the query.
The Class Selection dialog box displays the POM schema in tree format.
5. In the Attribute Selection pane, click the Display Settings button. From the
Display Settings dialog box, select All Attributes and Display Names.
• Name
• Description
• Type
c. From the Print dialog window, click the Save button to save the
definition to a user-specified file.
a. Open Query Builder from the new Teamcenter installation and click the
Import button.
b. Select the saved query file to be imported and click Verify and then OK.
c. When the file is displayed, click the Create button to create the query.
A Glossary
A Glossary
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.
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.
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.
key
Field in a record holding unique data that identifies the record from all other records
in the file or database. Each key value must be unique in each record.
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.
My Teamcenter
In the Teamcenter rich client and thin client, application that is the main access
point for managing product information. My Teamcenter provides the functionality
for creating objects in the Teamcenter database, querying the database for objects,
checking in and checking out objects, and managing tasks. Users can also open
objects, automatically launching the related application.
Each user has a personal My Teamcenter window that displays product information
as graphical objects. Although users share product information across the enterprise,
they organize this information individually in personal workspaces.
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.
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.
POM
See persistent object manager (POM).
properties
Keys and values that specify the configuration settings for an application in the
Teamcenter rich client.
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.
relation
Description of an association between a Teamcenter object and a piece of information
that describes or is related to the object.
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.
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.
value
Content of a field or variable. It can refer to alphabetic, numeric, or alphanumeric
data.
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.
A K
Assigning precedence to search criteria Keyword search queries . . . . . . . . . . . . . 2-6
clauses . . . . . . . . . . . . . . . . . . . . . . . 2-21
Attribute index . . . . . . . . . . . . . . . . . . . 5-1 L
Attribute Selection pane . . . . . . . . . . . . 1-2
Attributes . . . . . . . . . . . . . . . . . . . . . . 1-4 Language Translations dialog box . . 1-2–1-3
Localization button . . . . . . . . . . . . . 1-2–1-3
B
M
Best practices . . . . . . . . . . . . . . . . . . . . 6-1
Export saved searches to another Modifying queries . . . . . . . . . . . . . . . . 2-16
Teamcenter installation . . . . . . . . . 6-2
Restore My Saved Searches folder . . . . 6-1 O
Operators
C IS_NOT_NULL . . . . . . . . . . . . . . . . . 2-7
Class Attribute Selection dialog box . . . . 2-9 IS_NULL . . . . . . . . . . . . . . . . . . . . . 2-7
Class Selection dialog box . . . . . . . . . . . 1-3
Class/Attribute Selection dialog box . . . . 2-4 P
Class/Attribute Selection dialog box . . . . 1-2
Classification attribute queries . . . . . . . 2-11 Panes
Configuring Query Builder . . . . . . . . . . . 1-1 Attribute Selection . . . . . . . . . . . . 1-2, 1-4
Creating Hint . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Queries . . . . . . . . . . . . . . . . . . . . . . . 2-1 Saved Queries tree . . . . . . . . . . . . 1-2–1-3
Saved queries . . . . . . . . . . . . . . . . . 2-11 Saved query properties . . . . . . . . . 1-2–1-3
Search Criteria . . . . . . . . . . . . . . 1-3, 1-6
Perspectives
D In general . . . . . . . . . . . . . . . . . . . . . 1-8
Defining search criteria . . . . . . . . 2-20–2-21 Prerequisites for Query Builder . . . . . . . 1-1
Deleting queries . . . . . . . . . . . . . . . . . 2-16
Q
E Queries
Enabling Query Builder . . . . . . . . . . . . . 1-1 Based on existing definitions . . . . . . . . 2-7
Export saved searches to another Teamcenter Classification attributes . . . . . . . . . . 2-11
installation . . . . . . . . . . . . . . . . . . . . . 6-2 Creating . . . . . . . . . . . . . . . . . . . 1-2, 2-1
Creating using hints feature . . . . . . . . 2-3
Definition window . . . . . . . . . . . . . . . 1-2
H Deleting . . . . . . . . . . . . . . . . . . . . . 2-16
Hints, creating queries using . . . . . . . . . 2-3 Modifying . . . . . . . . . . . . . . . . . . . . 2-16
Referenced-By . . . . . . . . . . . . . . . . . . 2-8
Restore My Saved Searches folder . . . . 6-1
I
Revision rule . . . . . . . . . . . . . . . . . . 2-12
IS_NOT_NULL operator . . . . . . . . . . . . 2-7 Sort order . . . . . . . . . . . . . . . . . . . . 2-12
IS_NULL operator . . . . . . . . . . . . . . . . 2-7 Subclass on typed reference . . . . . . . 2-12