- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2022 11:31 PM
Hi, All
My client is using search suggestions in the service portal.
However, it will not work unless I enter at least 3 characters in the search box.
This limitation is very inconvenient for me because I often use two Kanji characters when searching for Japanese words.
Is it possible to change this setting?
If you know how to change it, please let me know.
Solved! Go to Solution.
- Labels:
-
AI Search
-
Search
-
Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2022 11:45 PM
Hi
The minimum number of characters which must be typed before is decided based on these properties: ('glide.service_portal.typeahead.min_length' and 'glide.service_portal.typeahead.wait_ms' .
Existing ServiceNow customers can use historical data in the text_search or sp_log tables to seed the Search Suggestion tables to provide initial suggestions for the Service Portal and Now Mobile.To do that you can use the scheduled jobs provided by ServiceNow:
- To populate suggestions for Now Mobile use Populate Suggestions to avoid Cold Start - Mobile Requestor.
- To populate suggestions for a portal use Populate Suggestions to avoid Cold Start - Portals.
So, if you have your 2 kanji characters stored in text_search or sp_log tables, then it would probably show you.
Whenever the user searches anything it is stored in sys_search_event table.The Build Search Suggestions scheduled job turns those search strings into search suggestions and stores them in the sys_search_suggestion table. By default, the scheduled job runs daily. You can customize it according to your instance.
But ideally you have to enter at least 3 characters to search!!
Mark my answer correct & Helpful, if Applicable.
Thanks,
Sandeep
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2022 11:42 PM
Hi, this community article
Optimizing the Service Portal Typeahead search widget - Now Platform - Article - ServiceNow Communit...
indicates that the char limit is set by this system property
'glide.service_portal.typeahead.min_length'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2022 11:45 PM
Hi
The minimum number of characters which must be typed before is decided based on these properties: ('glide.service_portal.typeahead.min_length' and 'glide.service_portal.typeahead.wait_ms' .
Existing ServiceNow customers can use historical data in the text_search or sp_log tables to seed the Search Suggestion tables to provide initial suggestions for the Service Portal and Now Mobile.To do that you can use the scheduled jobs provided by ServiceNow:
- To populate suggestions for Now Mobile use Populate Suggestions to avoid Cold Start - Mobile Requestor.
- To populate suggestions for a portal use Populate Suggestions to avoid Cold Start - Portals.
So, if you have your 2 kanji characters stored in text_search or sp_log tables, then it would probably show you.
Whenever the user searches anything it is stored in sys_search_event table.The Build Search Suggestions scheduled job turns those search strings into search suggestions and stores them in the sys_search_suggestion table. By default, the scheduled job runs daily. You can customize it according to your instance.
But ideally you have to enter at least 3 characters to search!!
Mark my answer correct & Helpful, if Applicable.
Thanks,
Sandeep
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2024 10:16 PM - edited ‎06-18-2024 10:19 PM
Hello @Community Alums,
I have also facing same issue in my instance when search with the 3 characters of catalog item in CSM portal.
Please check the below question.
https://www.servicenow.com/community/csm-forum/search-can-t-lookup-for-the-first-3-characters-of-a-catalog-item/m-p/2965288/page/1
Do you have any idea about the 'AI Search for Customer Portals'(sn_csm_aisp) plugin? Is this required for resolving this search related issue on the CSM portal?
Any help resolving this search issue would be greatly appreciated.
Thank You!