try to use AI Search on service portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-20-2024 10:41 PM - edited ‎12-25-2024 10:29 PM
Searching two terms with space yields incorrect results. Initial result count is low, however clicking on header shows quite high count. When endusers without roles try to use AI Search on service portal, this happens.
Can this be fixed?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-22-2024 07:43 AM
Hello @mareahG ,
Could you please provide a screenshot of the AI search result you are facing, recently we had a fix and if it's similar I can help you fix it?
Thanks & Regards,
Nishchitha KS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-22-2024 09:47 AM
Hi @mareahG!
This is confusing AI Search behavior, but let me explain:
Lets assume you searched for "Request Access", the AI ​​Search engine tokenizes your search and transforms it into two words: "Request", "Access".
At first, in all tab you will notice that the search engine looked for results that appear the two words together, the search engine uses the "&" operator to carry out this search, as if it were "Request" & "Access" so it appears less results.
When you click on a tab, the search engine no longer uses the "&" operator, from now on it uses the "OR" operator, so your search becomes "Request" OR "Access", thus creating a search with much more results because the words are being searched separately.
This is standard AI Search behavior, but it's actually quite confusing, so Servicenow is working to improve it in the Yosemite version.
The workaround is to turn off tab count in Search Application, this prevents this behavior of using the "OR" operator when clicking on a tab, thus bringing only the most relevant results.
If my answer helped you in any way, please mark it as correct/helpful 🙂
Regards,
Isaac Vicentini.
MVP 2025 ✨
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-22-2024 09:56 AM
Hello @mareahG
We have received a Defect communication regarding this. The issue is fixed in Washington Patch 5 Hotfix 1 and above.
Please refer the known error article (requires login)
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1651332
Please mark this answer as helpful and correct if helped. This benefits both community and me.
Kind Regards,
Ravi.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-25-2024 06:29 AM
Are you sure the Hotfix you mentioned is even related to what @mareahG reported?
We are having the exact same issue and @Isaac Vicentini is spot on with the explanation.