When using advanced search with multiple attributes - specifically when one is a date, you can get inconsistent results.
If user selects All Types or selects types without a number attribute then that attribute is skipped during the comparision and the results of other criteria comparison is used. In one example, a search used a number and date criteria on All Types. Because some of the searchable types do not have a number attribute only the other criteria - the date criteria is checked on objects of those types. If the date criteria matches on an object whose type does not have a number attribute the object is considered a match.
This is inconsistent to what the user experience should be. If the user defines a search using both a number AND a date, you would expect both criteria to be evalueated.
There is a parameter com.ptc.windchill.search.client.overrideAndOrOperator that can change the search behavior when multiple parameters are provided, but does not help in this scenario.
I would like to see the user presented with more options (i.e an "advanced settings" popup) where the user could implicitly specify how to address And/Or behavior, how to address if the attribute does exist (when using All Types,etc), or other variables in how to assemble the query. I know this makes it more complicated for the user, but it allows the user to clearly define what the query is, and how it should be execute.