AI Search field settings & mapping and EVAM configuration in service portal

[kushi1]

Hi All,

Can anyone guide me with below queries on AI search in portal:

1. What is the use of Field settings and mapping in AI search indexed source. Even without setting up these fields,I can display the results in the portal.

2.How does not searchable and no text index attribute work while searching in service portal

EX: When i set a kb_category field with not_searchable attribute value true , its displaying result in portal

3.what is use of custom fields in EVAM configuration , when i already have table fields to use in view template while displaying results.

May i please know backend logic or how the above features works and how is it useful to get started in our requirements?

Thanks,

Pooja

[Gerard Dwan]

Hi Pooja, 

Great questions. I like to look at existing configurations to explain some of these topics. 

1) These field mappings help in two ways. First, AI Search treats title, text, and sort_by_date differently than the default field mapping. So it's helpful to provide context to AI Search one what these items are. Additionally, if there is an item that isn't on the table, you can use a dot-walk-field to place it on the table. 

2) This is described well here in this question (sorry I didn't see your post first!). 

3) Exactly, custom fields are for items that are not on the table directly. Based on the image above, it would be the title (available as ai_search_teaser_title , so that it's highlighted), text (available as ai_search_teaser_text , also so that it's highlighted), and taxonomy. This example for Knowledge shows the teaser title and text. 

Hope this helps! 

[twinstars]

Is the order of the custom fields, i.e. ai_search_teaser_title, ai_search_teaser_text used in building the AI search suggestions, or how can I configure the fields for AI search suggestions? Thanks!