Vision's search limitation on Asterisks and Spaces
Using multiple search phrases in Processbook or Datalink was simply separating items by an asterisk . . . "*Phrase1*Phrase2*"
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. "*Phrase1*Phrase2*" would then be equivalent to "*Phrase2*,*Phrase1*"