Check out the brand new AI Search Setup page, and more!, in the Xanadu release

[Victor Chen]

New AI Search admin setup page

Navigate to "AI Search Admin Home to see the new AI Search setup page. Here you can view and configure search applications, monitor indexed documents and queries analytics, and learn more about AI Search with Resources. You can also configure Now Assist in AI Search genius results to your search profile from here. 

Dynamic result improvement rules for more personalized search

You can now boost documents based on user's context, which provides a more personalized search. When you create a Boost Rules in Result Improvement Rules (in Search Profile related list), you can now select a user property for boosting. This can be, for example, by user's country, city, or organization. Knowledge articles that contain the user's country etc., in the title or content will be boosted. See below screenshot for an example. 

To facilitate with the boost action, there is also now a new provided Synonym dictionary, "User Context Synonym Dictionary", that provides synonyms between countries and cities. In the "Synonyms" related list, click "Link Existing" to select the provided synonym dictionary. 

Don't forget to publish your search profile after making any changes. 

BONUS: New Search preview

Literally named in the navigator, "Search Preview (New)", you can now preview AI Search by Search Application. Here, you can preview facets, search suggestions, and Genius Result appearance.

Upgrade to the Xanadu release to try out these new features! Want to learn about What's new in Virtual Agent in the Xanadu release - find out here!

[spencerspeas]

In case anyone else encounters a similar issue in the future, you may be frustrated to find the "Search as user" field appears to only show a small set of users in the input. I can never find the user I am looking for. In my client's greenfield instance we ran into this issue.

I found that the sys_property

glide.graphql.gliderecord.maxResults.limit

controls this field and many others.  By default (even if the property is not defined in your instance) this limit is 1000, therefore you will only ever see a maximum of 1000 records available in this user lookup field. 

If this is an obstacle for you, I'd recommend TEMPORARILY changing this property to accommodate the size of your user table. In my client's instance with only 20k users, it dramatically increased the page load time to about 1 minute in a subprod environment. I completed my testing, and quickly reverted this property back to 1000 to regain page load time. 

[spencerspeas]

I later learned that in addition to changing the mentioned sys_property, the data source in the UI Builder config for the "Preview( AI Search Preview UI)" page also contains a gliderecord max number of records. I also needed to adjust this value to match my updated sys_property.

In my screenshot below, you see that there is a limit applied on the data source's GlideRecord query in addition to the default glide.graphql.gliderecord.maxResults.limit of 1000. 

My updated sys_property: 

Confirmation after changing both values: