I don't know how it does it, but the Form & App Objects Guide (for 7.5) does state that automatic complete is case insensitive by default, and that's the way it works for us, even without FTS (on Oracle, too).
David Durling University of Georgia > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Frank Caruso > Sent: Friday, June 08, 2012 1:13 PM > To: arslist@ARSLIST.ORG > Subject: Case Insensitive FTS > > ITSM 764sp2 > > Maybe its Friday and I am not seeing the obvious.... > > Trying to figure why some fields that have a menu attached and are > configured for Auto Complete work case insensitive. We are running on > Oracle, which is case sensitive, and using the FTS product. But there are some > certain fields that are not marked for FTS but menus attached to those fields > allow for case insenstive searches. > > For example, OOTB, the Template field on the Incident form. A user can type > a partial match using any case and the Auto Complete produces results. > When I look at the underlying field on the Incident Template form it is not > marked as an FTS field. If open the underlying form and search using the > Template name field, the search is case sensitive. > > So how does the Auto Complete allow for case insensitive matching? > > Thank you > > Frank > > __________________________________________________________ > _____________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 > www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
