Vision's search limitation on Asterisks and Spaces
Using multiple search phrases in Processbook or Datalink was simply separating items by an asterisk . . . "Phrase1Phrase2*"
Since Vision has Asterisks unable to match space characters the above search will return no results where there are any spaces between the phrases. The equivalent search phrase now must be "Phrase1 Phrase2".
This seems to be a step in the wrong direction on making searches more intuitive and easier, especially considering the YEARS of habit trained into people on proper search techniques within Processbook and Datalink. It also seems to be a very confusing state of affairs that Datalink/Processbook and Vision have a very fundamental difference in search functionality. Even if Datalink/Processbook don't have Visions functionality (like no longer having to be order specific), at the very least Vision should be able to support the search techniques used in Datalink/Processbook.
I'm not set on any one particular solution, however one possible suggestion is to allow an asterisk to match a space character again. Then instead of spaces in the search field representing separate search phrases, have search phrases be separated by commas. "Phrase1Phrase2" would then be equivalent to "Phrase2,Phrase1*"
In PI Vision 2020, a new search service was introduced that has a new experience. The default behavior searches for an exact match on text entered (accounting for spaces) at the beginning of search results, by adding an asterisk to the end of your search string. There is also a global setting on the PI Vision server that can be set that turns off all implicit asterisks.
For additional information on PI Vision 2020, please see the release announcement here:
Matt Voll commented
thank you for the clarification . . . having coached MANY engineers through this confusing search behavior, i am very keen to try this out . . . and i'll be sure to let you know if i still find it problematic ;)
Sorry for not clarifying - the new search experience also accounts for spaces in your search text. So searching for "a b c" will only return results that start with "a b c", accounting for the spaces.
Matt Voll commented
please don't mark this complete. What you are describing does not address the main issue here. Implicit asterisks, regardless of there existence, are not the issue. The problem and confusion stems from whether a space character can be search for or not. Currently spaces CANNOT be searched for and this can be very problematic.