One of the biggest staff complaints I'm getting since upgrade to 1.9.3 is the default change from start with to contains, especially in vet names and appointment reasons.

I went to a lot of trouble to design reasons (and vet names) that started with a unique one or two letters. So "co" <enter> was Consultation, "re" <enter> was Review Consultation, "di"  <enter> was Discharge Consultation and so on (we actually had those as macros in the previous v1.7 to speed data entry and reduce typing and clicks).

Now a "co" <enter> brings up every conceivable variation of consultation reason, so you need to scroll down list to select the one you want, increasing clicks and time spent.

I actually did read the documentation <g!>.

All I've found is "This project will make contains matching the default for queries that won't adversely affect performance."

"The contains search will be enabled by configuring a flag within the QueryFactory.properties file for each of the relevant archetypes.  This will default to false if not specified."

I've had a look in QueryFactory.properties but there's no flag there that I can see to de-specify to make start with the default. 

Tim also said "You will be able to turn the contains searches on and off, but not in a convenient manner as they are configured via a properties file. The server needs to be restarted for the changes to take effect."

Am I looking in the wrong place (webapps\openvpmsWEB-INF\classes)?