Type-Ahead Supplies Results After Inconsistent Input String Lengths or Not At All For Some Words in Forgeless (CAS) Based Applications (Doc ID 1980279.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 11.1 and later
Information in this document applies to any platform.

Symptoms

After upgrading from ATG with Endeca 11.0 to 11.1, the auto-suggest feature in the store front's search field is not working as expected, for certain words.

Certain other words do not exhibit the same behavior - after starting a search, suggestions appear after three characters* are typed.

There are no error messages associated with this behavior.

The Dgraph request logging is consistent with auto-suggest functionality as intended.

After 3 characters are typed into the search box, Dgraph requests appear for each of the test terms.

In other words, the request logs are showing the wildcard search '*' after each query, starting at 3 letters.

(E.g., for Oracle, there are requests logged for search at Ora*, Orac*, Oracl*, etc.)

This results in a requirement to type the entire word before results are obtained.

*Note: Three characters is the configured value for the purposes of this Article.

Cause

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Type-Ahead Supplies Results After Inconsistent Input String Lengths or Not At All For Some Words in Forgeless (CAS) Based Applications (Doc ID 1980279.1)

Applies to:

Symptoms

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!