Ai Search - Exact match page

M_iA
Kilo Sage

We are using AI search in our portal. We have dedicated pages for knowledge and case information.

However, when using the search bar and the AI search finds an exact match and we click on the record, it takes the user through to the record on the form page.

 

How do I configure the exact results page routing in Ai search?

 

Thanks

1 ACCEPTED SOLUTION

M_iA
Kilo Sage

I reached out to Hi on this and the issue is fixed in Utah. But backported to SD patch 4 where you can update the typeahead widget to disable exact match

View solution in original post

19 REPLIES 19

I contacted ServiceNow Support about issues we're seeing the Exact Match and got this reply.

 

The PRB 'PRB1610555' is fixed in Tokyo patch 4. That's right but we have to manually add this line of code enable-exact-match="false" in the sn-search-combobox.

The reason why we need to manually add is. The ability to turn off the Exact match is to apply a manual update to the widget. There is currently no mechanism to disable the feature via configuration(from base code). This is under consideration for a future release.

I've attached the updated Typeahead Search widget XML provided by Now Support.  We prefer importing this as to cloning the widget and updating all the pages that reference the original widget.


Susan Williams, Lexmark

Thanks for this, Susan! 


Best regards,
Sebastian Laursen

Surabhi7
Tera Contributor

Hi,

We are also facing same issue, do you know in which version of Utah this is fixed?

Thanks in advance.

 

Surabhi

Hi @Surabhi7 - Did you find an answer for this? We are also in Utah and facing same issue, where exact match on employee center is not working. We are unable to edit the typeahead widget to enable exact match as it is read only, and are reluctant to cloning this due to the amount of pages it is on

M_iA
Kilo Sage

It appears that the issue is now presenting itself in the vancouver release. Even with exact match on the typeahead serach widget being set to false.

 

I have raised a further support ticket to try and find out what has happened.