The ServiceMax Org-wide Profile Configuration contains a Common Global org wide setting "GBL017" which can be configured with the following search Operators "Starts With, Contains,Exact Match, Ends With". Unfortunately, this setting is ORG wide so changing it impacts all SFM Search lookups so they all default to whatever this setting is and the user can always override the default "Search Operator" setting in the SFM lookup search window. This idea would like to keep the "GBL017" setting but also allow the "Search Operator" to be configured inside the SFM Transaction Designer for the specific SFM Search Lookup so it will default the Search Operator to whats defined in SFM lookup and still allow it to be overrode like it works today. For example, an Admin could define the SFM lookup for the Installed Product object to be "Exact" which will has a lot better performance compared to using "Contains" especially when some customers have millions of Installed Products. If the SFM lookup "Search Operator" is not explicitly defined then it would default to using the "GBL017" parameter.
What is the underlying problem do you intend to solve with this idea?
Flexibility at the SFM level. Better performance and quicker to return results when using Exact match for some searches, compared to using "Contains" especially when some customers have millions of Installed Products.
How is the problem being addressed today, if at all?