|
The following topic only applies when your Search Mode preference is set to Simple. This is the default value. For information on Advanced mode searches, see Advanced Mode Searching.
|
Name: ABC*
Results include the following object names:
• ABC
• ABC DEF GHI
• ABC–DEF.GHI
Name: *ABC
Results include the following object names:
• ABC
• 123ABC
• 123 456 ABC
Name: *ABC*
Results include the following object names:
• ABC
• 123ABCDEF
• ABCDEF
• 123ABC
|
Name: 12?4
Results include the following object names:
• 1234
• 12A4
Name: ??345
Results include the following object names:
• 12345
• AB345
Name: ABC 12?*
Results include the following object names:
• ABC 123
• ABC 123_45
• ABC 123 456
|
|
The examples above are entered into the Name field, and therefore illustrate a database search: Keyword searches, specifically when using Windchill Index Search, would behave differently in some situations. For more information, see the section “Unique Wildcard Behavior in Indexed Keyword Searches” below. |
|
When you perform a non-indexed search, using asterisk (*) in between strings accounts for space as well.
|
|
When performing object search using attribute values, objects other than the CAD documents are stored in the database after trimming the spaces around the attribute values, such as Name, Number, etc. However, the CAD documents attributes are not trimmed and are accepted as they are in the respective CAD tools. Hence, while performing a search for CAD objects, you must either provide the exact search term (with the trailing space) or a trailing wildcard character (for example, "1234*").
|
Keyword Variable
|
Indexed Search Behavior
|
||||
---|---|---|---|---|---|
Leading asterisk (*)
|
A leading asterisk (*) in the Keyword field or in a global search limits the search to indexed file content and to the mapped attribute values (Name and Number by default) and other object attributes values. . Without the leading asterisk, the keyword would be compared against all attribute fields.
For example, if you enter nitin* as a keyword for an indexed search, the results would include the following:
• Objects whose name or number includes “Nitin” or “Nitin” followed by one or more characters (for example, “NitinDesign.”)
• Objects with content files that include “Nitin” or “Nitin” followed by one or more characters (for example, “Nitin0123.”)
• Objects created or modified by a user named “Nitin.” (Or any other attribute value that might include “Nitin” or “Nitin” followed by one or more characters.)
Whereas if you enter *nitin, the search would return:
• Objects whose name or number includes “Nitin” or “Nitin” preceded by one or more characters (for example, “01Nitin”).
• Objects that have content files and/or attributes other than Name and Number which include the word “Nitin.”
For more information, see the advanced search use case scenario Keyword Searches Using Wildcards.
|
||||
Leading or trailing question marks (?)
|
A question mark (?) at the beginning or end of a keyword search string can be replaced by zero or one character.
For example, if you search for specification?, the results would include “specification,” “specifications,” and “SpecificationA.”
Similarly, ?end would return “end,” “bend,” and “send.”
|
||||
Spaces
|
When used in a single keyword search, a wildcard cannot substitute for white space between multiple strings.
For example, a search for product*specification would successfully return results for the following:
• product001specification
• product_specification
• ProductSpecification
However, it would fail to return the following results:
• Product Specification
• Product001 Specification
• Product%%Specification
|