---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-administration
Release :
- australia
ft:locale :
- en-US
ft:publication_title :
- Australia ServiceNow AI Platform Administration
ft:clusterId :
- platadm
bundleId :
- platadm
workflow :
- Platform
---
# AI Search Genius Result Configuration form
# AI Search Genius Result Configuration form {#ariaid-title1}
Release version: Australia
Updated September 10, 2026
 4 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of AI Search Genius Result Configuration form
The AI Search Genius Result Configuration form allows ServiceNow customers to create and manage Genius Result configurations for AI Search profiles.
These configurations define how specific search queries trigger customized Genius Results, enhancing search relevance and user experience.
Show full answer Show less
## Key Features
* **Name:** Assign a unique name to each Genius Result configuration for identification.
* **Trigger Condition:** Choose when the configuration activates:
* **Always:** Triggers on every search query.
* **NLU:** Triggers when search intent matches a linked and published Natural Language Understanding (NLU) model intent.
* **Term:** Triggers only on exact matches of specified query terms in the defined order.
* **Term Field:** Specify exact query terms if the Term trigger is selected.
* **Application:** Automatically sets the application scope for the configuration.
* **Active Status:** Activate or deactivate the configuration; inactive configurations do not trigger.
* **Processor Script Template:** Provides sample server-side script functions to guide request and response processor scripting.
* **AI Search Request Processor:** Server-side script that receives a GeniusResultContext object and must return a GeniusResultAnswer object with a search query. This script runs before AI Search computes results and can define up to three Genius Result answer cards. This field is required if the response processor is not provided.
* **AI Search Response Processor:** Server-side script executed after AI Search computes results. It returns a GeniusResultAnswer object containing key-value data maps for display on Genius Result answer cards. This field is required if the request processor is not provided.
* **Return Fields:** Lists the fields to display on the Genius Result answer cards. Required if the response processor is used. If only the request processor is populated, default fields display automatically, with an option to specify additional fields.
## Practical Use and Considerations
* Linking and publishing NLU models is necessary for NLU trigger conditions to function.
* Exact term matching requires the search query to match specified terms precisely and in order.
* Scripts use scoped JavaScript APIs (GeniusResultAnswer and GeniusResultContext) to define and manipulate search queries and results. Avoid using GeniusResultContext.getMatchingDocuments() in request processor scripts as it returns no results pre-search computation.
* Proper activation of configurations ensures they trigger appropriately during searches.
* Return fields enable customization of the data shown on Genius Result cards, improving result relevance and user interface clarity.
The AI Search Genius Result Configuration form enables you to create a Genius Result configuration for use in your AI Search search profiles.
For details on creating or editing a Genius Result configuration, see [Create a Genius Result configuration](https://www.servicenow.com/docs/keDuVZAaFuouBlvTBUpXRw "Create a Genius Result configuration, set its trigger condition, and configure the results displayed on its answer card.").
{#genius-result-cfg-form-ais__table_wqk_ttg_trb__entry__2}
| Field | Description |
|-|-|
| Name | Name for the Genius Result configuration. |
| Trigger condition | Condition that triggers evaluation of the Genius Result configuration. Supported values: * Always: The Genius Result configuration triggers for every search query. * NLU: The Genius Result configuration triggers when the search query's detected intent matches an [NLU model](https://www.servicenow.com/docs/access?context=nlu-models&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) intent. To use this trigger condition, you must link the NLU model and one or more of its intents to your Genius Result configuration. For instructions, see [Link an NLU model and intents to a Genius Result configuration](https://www.servicenow.com/docs/bde75A4qYVoRikAG2dxp_Q "Specify the NLU model and intents to use for a Genius Result configuration with an NLU trigger condition."). Note: For an NLU trigger condition to function, the NLU model must be published. You can verify NLU model status by navigating to AllAI SearchSearch Query SettingsSearch Intents. * Term: The Genius Result configuration triggers when the search query exactly matches a specified set of query terms. Note: Exact matching means that the search query must contain only the specified terms in the specified order. For example, if you define conference room as the trigger term, a search for conference room triggers the Genius Result condition but searches for hotel conference room or room conference don't trigger it. {#genius-result-cfg-form-ais__ul_xqk_ttg_trb} |
| Term | Term that triggers the Genius Result configuration when it exactly matches the search query. This field appears only when you select Term from the Trigger condition field. |
| Application | Application scope for the Genius Result configuration. This field is automatically set. |
| Active | Option to activate the Genius Result configuration. Inactive Genius Result configurations never trigger. |
| Processor script template | Sample server-side script function. Use the code displayed in this field as a basis for your AI Search request processor and AI Search response processor scripts. This field is automatically set. |
| AI Search request processor | Server-side script function that takes a GeniusResultContext object as its parameter. The function must return a GeniusResultAnswer object that contains a search query. Up to three results from this search query display as Genius Result answer cards. Note: This field is required if AI Search response processor isn't populated. You can copy the code from the Processor script template to use as a starting point for your script function. When a search query triggers the Genius Result configuration, the system executes this script and then sends both the triggering search query and the scripted search query to the AI Search back end for computation of search results. To define a search query, use the GeniusResultAnswer.setTable(), GeniusResultAnswer.addSearchPhrases(), and GeniusResultAnswer.setSearchPhrase() API methods. For details of API methods usable in this script function, including examples of use, see the [GeniusResultAnswer](https://www.servicenow.com/docs/access?context=GeniusResultAnswerScopedAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US) and [GeniusResultContext](https://www.servicenow.com/docs/access?context=GeniusResultContextScopedAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US) scoped JavaScript API descriptions. Note: The GeniusResultContext.getMatchingDocuments() API method returns no results when invoked in an AI Search request processor script, since the script is executed before AI Search computes results for the triggering search query. Don't use this method in your request processor scripts. |
| AI Search response processor | Server-side script function that takes a GeniusResultContext object as its parameter. The function must return a GeniusResultAnswer object that defines one or more maps of key-value pairs. You can display these key-value pairs on the Genius Result answer card by specifying them as Return fields. Note: This field is required if AI Search request processor isn't populated. You can copy the code from the Processor script template to use as a starting point for your script function. When a search query triggers the Genius Result configuration, the system executes this script after AI Search computes search results. To define your map of key-value pairs, use the GeniusResultAnswer.addDataMap() API method. Each key-value pair represents a field name and value that you can display on the Genius Result answer card using the Return fields list. For details of API methods usable in this script function, including examples of use, see the [GeniusResultAnswer](https://www.servicenow.com/docs/access?context=GeniusResultAnswerScopedAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US) and [GeniusResultContext](https://www.servicenow.com/docs/access?context=GeniusResultContextScopedAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US) scoped JavaScript API descriptions. |
| Return fields | Comma-separated list of fields to display on the Genius Result answer card. This field is required if AI Search response processor is populated. Behavior depends on which processor script field is populated: * If AI Search response processor is populated, you must use this field to specify the names of fields defined in your GeniusResultAnswer response object that you want to display on the Genius Result answer card. * If AI Search response processor isn't populated, the Genius Result answer card automatically displays the common AI Search index fields: * ai_search_parent_title * ai_search_teaser_text * ai_search_teaser_title * record_class_name * sys_id * table {#genius-result-cfg-form-ais__ul_brk_ttg_trb} You can optionally use this field to specify any additional AI Search index fields that you want to display for search results shown on the Genius Result answer cards. To view the list of AI Search index fields, see [AI Search index fields](https://www.servicenow.com/docs/yeol_iG~sF1vbdkgZorIog "List of fields available on records in the AI Search index. AI Search populates these fields with values from source record fields during indexing."). {#genius-result-cfg-form-ais__ul_ark_ttg_trb} |
[Table 1. AI Search Genius Result Configuration form]
{#genius-result-cfg-form-ais__table_wqk_ttg_trb}
*[\>]: and then