190 views

 

Search Engine URL changes of new Text Search

 

Overview

If using the new search functionality starting from Jakarta, the legacy exact match search bookmarks or search engines are not going to work. Here are some of the ways to configure your search results to make it work.

 

URL changes for new Text Search


Legacy search uses textsearch.do to perform the search, as shown in the example URL below

 

https://<yourInstance>.service-now.com/textsearch.do?sysparm_search=search_term

 

search_term can be task record number (for Exact Match search) or any text that would like to get the results. This is also the place you would replace it with %s for Chrome search engine.

 

The new search is slightly different if you use the same URL to search it will redirect to $sn_global_search_results.do, Example URL

 

https://<yourInstance>.service-now.com/$sn_global_search_results.do?sysparm_search=search_term

 

The search_term defined here is similar to the legacy search but if the search term includes a record number for a task record, it is considered as a search term. Due to which it searches for the term and provides relevant results but does not directly go to the record.

 

In order to use the Exact match feature for text search, please use the below link

 

https://<yourInstance>.service-now.com/text_search_exact_match.do?sysparm_search=search_term

 
This link can be used for both searching the term and exact match search. If term matches a valid task record number, it will take you to the respective task record. For any other term, it automatically redirects to $sn_global_search_results.do and searches it there.

 

Switch to Legacy search


Please use the documentation to switch back to legacy search

https://docs.servicenow.com/bundle/jakarta-platform-administration/page/administer/search-administration/task/revert-to-legacy-global-search.html

Article Information

Last Updated:2018-03-15 04:31:07
Published:2018-03-15