---
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


---

# Search Application Configuration form

# Search Application Configuration form {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Search Application Configuration form

The Search Application Configuration form in ServiceNow enables you to create and manage configurations for AI Search applications.
This form is essential for defining how your search application behaves, including which search engine it uses, how results are displayed, and specific features like typo handling and exact match behavior.
Show full answer Show less  

## Key Features

* **Name:** Assign a name to your search application configuration for easy identification.
* **Search Engine:** Choose between AI Search or Zing search engines. This selection must align with your search application's Enable AI Search setting to avoid errors.
* **Search Profile:** When AI Search is selected, specify a search profile to guide search behavior.
* **Search Results Limit:** Set the maximum number of results per page and the minimum for query resubmission to broaden results if too few are returned (default is 10).
* **Genius Results Limit:** Define how many Genius Result answer cards appear (up to 10), including carousel display for multiple cards when set to 2 or more.
* **Attachment Limit:** Control how many grouped attachments show by default under a parent search result, with additional attachments hidden until expanded.
* **Enable Typo Handling:** Optionally auto-correct search query terms based on a typo dictionary to improve search accuracy (available only with AI Search).
* **Enable Exact Match:** Enable exact matching to directly display a record when the search term matches the Number field, bypassing the results page. Note: This feature is not supported in portals.
* **Show Parent for Attachment Results:** Choose whether attachment search results display inline with their parent results or separately.
* **Filter Genius Results by Tab:** When enabled, Genius Result answers respect the selected source facet filter, returning answers only from the selected source(s).
* **Show Search Results Count:** Option to display counts of search results for facets on the results page, enhancing user insight into result distribution.

## Practical Considerations for ServiceNow Customers

* Ensure the Search Engine setting matches the Enable AI Search option on your search application to prevent configuration errors.
* Use the Search Results Limit to manage performance and user experience by controlling how many results appear and when queries broaden automatically.
* Leverage Genius Results and their carousel feature to highlight relevant AI-generated answer cards effectively.
* Enable Typo Handling to improve search accuracy, especially in environments with frequent user input errors.
* Be cautious with Exact Match in portals due to potential navigation issues; it is primarily suited for workspace environments.
* Use attachment grouping to present related attachments more intuitively within search results.
* Utilize filtering of Genius Results by source facet to tailor AI-generated answers to the user's context and selected data sources.
* Displaying search result counts for facets can improve user navigation and understanding of search data distribution.  
The Search Application Configuration form enables you to create a search application configuration for an AI Search application.
For details on creating or modifying a search application configuration for use with AI Search, see [Create a search application configuration for AI Search](https://www.servicenow.com/docs/bU~8xikxXqfv71rW_BAdSg "Create a search application configuration to specify AI Search as the search engine for a ServiceNow AI Platform application. Select a search profile for the application to use. Configure the application's settings for refinement and display of search results.").  
{#search-app-config-form-ais__search-app-config-table__entry__2}

| Field | Description |
|-|-|
| Name | Name for the search application configuration. Type: string |
| Search Engine | Search engine to use in the ServiceNow AI Platform® search application that links to the search application configuration. Type: choice list Default value: AI Search Supported values: * AI Search: Use AI Search as the search engine for the application. Select this search engine if your search application has the Enable AI Search option enabled. * Zing: Use the Zing text indexing and search engine as the search engine for the application. Select this engine if your search application has the Enable AI Search option disabled, or if it lacks this option. {#search-app-config-form-ais__ul_c5p_bh3_gnb} Note: If your search engine selection conflicts with your search application's Enable AI Search setting, the system displays an error message. Before changing search engines, first make sure that your search application has the proper Enable AI Search setting. |
| Search Profile | Search profile to use for searches in the application. This field appears only when you select AI Search as the application's search engine. Type: reference to a record from the Search Profile \[ais_search_profile\] table |
| Search Results Limit | Maximum number of search results the application should display on each search results page. This limit also specifies the minimum number of search results each query should return. When a search query returns less than this number of results, AI Search attempts to broaden the result set by automatically resubmitting the query with modified parameters. For more details on query resubmission, see [Automatic search query resubmission](https://www.servicenow.com/docs/cqJpNeKksotzWRnR_jDkpg "When a search query returns too few results, AI Search automatically modifies and resubmits it with the goal of returning at least the desired number of results."). Type: integer Default value: 10 Supported values: 0 or positive |
| Genius Results Limit | Maximum number of Genius Result answer cards the application should display on the search results page. This field appears only when you select AI Search as the application's search engine. Type: integer Supported values: 0 or positive When Genius Results Limit is set to 2 or greater and a search returns multiple Genius Result answers, the answer cards display in a carousel. You can scroll the carousel and select the answer card you want to take action from. Note: Search applications display a maximum of 10 answer cards per search query. If you set this limit to 11 or more, the search application still displays a maximum of 10 answer cards. Starting with version 6 of [ServiceNow Otto for AI Search](https://www.servicenow.com/docs/KKrNY4Mlb8okLL6_t88tFQ "The ServiceNow Otto for AI Search application combines the power of search with a large language model (LLM) to provide actionable AI-generated or AI-selected answers in user searches. By constraining the context passed to the LLM, ServiceNow Otto for AI Search can increase the likelihood that LLM responses are grounded in indexed content."), installing ServiceNow® Otto for AI Search makes the value of this field default to 10 instead of 1 when you create a search application configuration or edit an existing one. |
| Attachment Limit | Maximum number of grouped attachments to display by default on a parent search result when attachment grouping is specified in Show parent for results that are attachments. Attachments beyond this limit are hidden by default and only shown when you select Show more in the parent search result's attachments list. Type: integer Default value: 5 Supported values: 0 or positive |
| Enable Typo Handling | Option to auto-correct search query terms to match terms found in the search profile's typo handling dictionary. This field appears only when you select AI Search as the application's search engine. For more details on typo handling auto-correction configuration and behavior, see [Typo handling](https://www.servicenow.com/docs/g21GoEvGiHwb9MC3XfCgzg "AI Search replaces misspelled search query terms with auto-correction terms derived from indexed content. Configure typo handling dictionary settings to control derivation of auto-correction terms."). Type: true \| false Supported values: * true: Auto-correct search query terms in the search application. * false: Don't auto-correct search query terms in the search application. {#search-app-config-form-ais__ul_dfq_b4h_5fc} |
| Enable Exact Match | Option to use exact matching in the search application. When this option is selected, if a search result's Number field exactly matches the search, the application displays the record or document associated with that search result, bypassing the search results page. Exact matching also bypasses any custom matchers defined for the search application. Important: Exact match is not supported in portals. If you enable this option for a portal, users searching in that portal may experience navigation issues. Exact match behavior is controlled by the com.snc.agent_workspace.global_search.typeahead.exact_match_request_criterion_regex system property. This property's value is a Java regular expression pattern. Only search queries that match the regular expression pattern are evaluated as possible exact record matches. For details on Java regular expression pattern syntax, see [the Javadoc for the java.regex.util.Pattern class](https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/util/regex/Pattern.html). Type: true \| false Default value: true Supported values: * true: Use exact matching in the search application. * false: Don't use exact matching in the search application. {#search-app-config-form-ais__ul_b2g_wmh_5fc} |
| Show parent for results that are attachments | Option to display attachment search results inline with their parent results on the search application's results page. If cleared, attachment search results display separately from their parent results. For more details on the effects of attachment grouping, see [Grouping attachment search results with their parent search results](https://www.servicenow.com/docs/JQl7LOmhTrniPwj_G1n3Dw "Search application administrators can control whether attachment search results appear grouped with their parent search results or whether they display on their own. By default, AI Search displays attachments grouped with their parent search results."). Type: true \| false Default value: true Supported values: * true: Group attachment search results inline with their parent results in the search application. * false: Display attachment search results separately from their parent results in the search application. {#search-app-config-form-ais__ul_t2b_rnh_5fc} |
| Filter Genius Results by tab | Option to filter Genius Result searches based on the selected source facet bucket. In a search application that has this option enabled, when you select a source from the application's source facet, Genius Result searches honor the source filter and so can only return results from the selected source. This means that only Genius Result configurations that include information from the selected source can generate Genius Result answers in the search application. Genius Result configurations that don't include information from the selected source don't return any search results and thus can't generate Genius Result answers. As an example, suppose you select the Knowledge source facet bucket in a search application that has this option selected. With that Knowledge source selection applied, Q\&A Genius Results, which include information from the Knowledge source, can still find search results and generate Genius Result answers. But Catalog Item Genius Results, which include information from the Catalog Item source which isn't selected, can't find search results and so can't generate Genius Result answers. Note: The Summary Genius Results configuration (from the ServiceNow Otto for AI Search ServiceNow Store application) includes information from multiple sources, so it can generate Genius Result answers no matter which source is selected. To learn more about Summary Genius Results, see [Summary Genius Results](https://www.servicenow.com/docs/CS5LDmcfHQLxqDypQy2rXQ "Summary Genius Results use an LLM to generate search and chat responses that synthesize information from knowledge articles, Service Catalog items, and other available content types."). |
| Show Search Results Count | Option to display search result counts for facets on the search application's results page. For more details on this option, see [Show search result counts for facets on the results page for a search application](https://www.servicenow.com/docs/0av7J6O05uJAXuWkJMqF7g "Display search result counts for facets on the results page for AI Search applications that use Seismic components. Search result counts for facets show the number of matching search results for each source facet bucket."). Type: true \| false Default value: true Supported values: * true: Display search result counts for facets on the search application's results page. * false: Don't display search result counts for facets on the search application's results page. {#search-app-config-form-ais__ul_b1x_5nh_5fc} |
[Table 1. Search Application Configuration form]

{#search-app-config-form-ais__search-app-config-table}