cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Inconsistent search behavior with wildcards

Inconsistent search behavior with wildcards

PTC needs to audit their various search interfaces and enforce a standard when it comes to if wildcards are required or not.  Users are opening tickets thinking the system is broken because they are used to interfaces that don't require a wildcard then can't understand why they are getting no results when using another interface.

 

1. Aerospace, project manager, engineers and government overseers

2. Windchill PDMLink 11.1 M20 CPS 22

3,4. Users are assuming system is broken because not all search interfaces behave the same with wildcards.  When adding parts to a structure, wildcard is automatically used (ie user does not have to use '*' to get multiple results).  When updating CAGE Code, users get no results without '*'.

5. Trust and focus.  We want our users to trust the system they're working in.  We need our developers to focus on real issues instead of answering semi-regular questions on why users aren't getting the search results they need.

2 Comments
olivierlp
Community Manager
Status changed to: Acknowledged

Hello,
Thank you for your idea and the information provided.

ChrisHare
6-Contributor

So there's this Search preference that explains the behavior we're seeing:

 

Implicit Wildcards for Search in Structures
Default: Yes
Visibility: User
Description: Determines whether wildcards are implicit in structure-related search windows, such as Insert Existing.
• When set to Yes, wildcards are assumed at the beginning and ending of search criteria.
• When set to No, wildcards are not assumed, but you can manually enter wildcards to return a broader range of search results.
*This preference applies to structure-related searches only.