Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

EVAM View Configuration Custom Fields and

michaelward
Tera Guru

When configuring an AI Search application for a new Employee Center portal, and when reviewing how taxonomy topics are displayed relative to AI Search results, I came across two things for which I need an explanation. 

 

1.  The "Knowledge Search Results" view configuration in EVAM has custom fields (ai_search_teaser_title,ai_search_teaser_text, document_index,topics,child_docs) that include 'topics'.  This "topics" field is used in the view template as one of the headers displayed in a result.  I would expect to go to an AI search index and see this in field mappings.  In this case, go to "Knowledge Table" search index and a field mapping would show "topics".   Or, I would see a "topics" field actually on the table itself.  However, there is neither, so what simple magic trick am I missing here?   What is "topics" referencing here?  There is a simple "topic" field on the kb_knowledge table, but it refers to a simple String choice list.  

 

2.  In the same scenario, that being out of the box AI search configuraiton for Employee Center and dealing with taxonomy topics, a search result potentially has a "topics" facet when viewing results.  The facet fields for this configuration are "kb_knowledge.topic_level_0,sc_cat_item.topic_level_0,sn_lc_course_item.topic_level_0".  What is "topic_level_0"?  What is documented to explain this as it is not a field on the kb_knowledge table and there is nothing in the field mappings of any indexed source that I can see.  

 

This feels like something baked into the EVAM and/or AI Search configurations that is either not documented well (like EVAM view templates), or I am just flat missing some explanation somewhere. 

 

Thanks for the help. 

1 REPLY 1

Vinicius5
Tera Contributor

Michael, did you have any solution for this? I'm having the same problem understanding this.