You are viewing limited content. For full access, please sign in.

Question

Question

Recommendations on optimizing the Full Text search in WebLink

asked on April 18, 2013 Show version history

Used Case Scenario:

When designing custom searches for Weblink there isn’t an option to require at least one template field be populated before a text search can be executed.  Allowing the public to navigate to the search pane and select their own search options is expecting too much of the public so Search Forms need to be used.  Because the user is not required to populate a template field their search is conducted across the entire system which we know is not a best practice and can bring the system to its knees.  How would you recommend we avoid such issues and keep Weblink operating optimally?

 

We are looking for some recommendations on this issue that we are coming across for a client. They have mid-sized public portal using Web Link. Please let us know if there are some recommendations or best practices that you have for optimizing these searches without crashing the system and pushing users to use Fields as a part of their searches.

0 0

Answer

APPROVED ANSWER
replied on April 22, 2013 Show version history

There are a couple of ways to make sure that your text searches are being combined with a template/field search in a WebLink custom search.

 

The most direct way would be to add both a text search and a field search, and make sure the field search is marked as required:

 

(WebLink view)

 

(WebLink designer view)

 

 

Another way would be to use a Template search type, have the input type be “List”, and don’t include a blank value in the list. This will force a template to be chosen along with the text search:

 

(WebLink view)

 

(WebLink designer view)

 

 

Using some combination of the above, you should be able to ensure that users make a relevant template/field choice along with their text search. 

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.