Configuring AI Search for Next Experience on tableIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Steps to configure AI Search for Next Experience so that a custom or extended table (e.g., a task-based table) is indexed and searchable, and results are correctly navigable from the search UI. Ensure ServiceNow instances with AI Search Next Experience Search enabled This article outlines the end-to-end configuration required to enable AI Search for a table, map it correctly to a data source, configure the result template and navigation action, and link everything to a Search Profile. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Step 1: Create a Data Source for the required tableNavigate to AI Search > Data Sources and create a new data source pointing to the incident_task table.Path: ais_datasource.do Step 2: Configure Field Settings & MappingOpen the newly created data source and configure the Field Settings and Mapping tab to map the relevant fields for search indexing.Path: ais_datasource_field_attribute_list.do Step 3: Create the Search Source MappingCreate a Search Source record and associate it with the incident_task data source created in Step 1.Path: ais_search_source_list.do Step 4: Create the Template (EVAM View Config)Set up a Composite Data Template Predicate under the EVAM (Experience View and Action Mapping) view configuration for the table.Path: sys_ux_composite_data_template_predicate_list.do Step 5: Assign the Navigation Action under EVAM View ConfigUnder the EVAM predicate created in Step 4, map the Action Assignment to the existing out-of-box Navigation action.Path: sys_ux_predicate_m2m_action_assignment_list.do Step 6: Link with the AI Search Profile and PublishAssociate the configuration with the relevant AI Search Context Profile (search_engine = ai_search), then publish the profile to activate the changes.Path: sys_search_context_config_list.do Post-configuration:Once published, validate the AI Search results for the incident_task table in the Next Experience UI. If results do not appear as expected, revisit field mapping (Step 2) and the search source configuration (Step 3). Note: Steps 4–6 (EVAM/Navigation setup) apply specifically to enabling in-context navigation from search results in the Next Experience UI and may be skipped if only backend search indexing is required.