Text search views control format of global search results for tables
Summarize
Summary of Text Search Views Control Format of Global Search Results for Tables
Thetextsearch viewfor a table in ServiceNow dictates how global search results are presented. It organizes multiple elements for each search result based on the table's configured textsearch list view. If a specific textsearch view is not available, the system defaults to the table's form view.
Show less
Key Features
- Title: The title appears as the first line of the search result and links to the corresponding record. It is derived from the first non-number string field in the textsearch list view. If no string field is found, "No title" is displayed.
- Field List: This is the second line, showing up to 10 field name-value pairs, separated by a pipe character. It uses fields from the textsearch list view that do not conflict with the title or description criteria.
- Description: This optional third line displays if there is a string field exceeding 100 characters in length, excluding the title. If no such field exists, this line will not appear.
Key Outcomes
By using the textsearch view, ServiceNow customers can effectively control how their global search results are formatted, ensuring relevant and concise information is presented. Adjustments to the glide.ui.textsearch.view system property allow for customization of search result formatting, enhancing user experience and efficiency in locating records.
The text_search view for a table determines how global search displays results from that table.
Results displayed by global search include multiple elements. For each search result, the system populates these elements with values of fields included in the table's text_search list view.
| Element | Description | Matching criteria |
|---|---|---|
| 1. Title | The title is the first line of the search result block. It links to the matching record of the search result. | Global search uses the first string field in the table's text_search list view that is not the number field. If there is no matching string field or the contents of the field is empty, the system displays the text "No title" in the session language. For example, in the default text_search view for the Incident table, the short description field satisfies the title criteria. Global search uses this field as the search result title. |
| 2. Field list | The field list is the second line of the search results. It displays field name-value pairs, separated by the pipe character, for up to 10 fields. | Global search uses the first 10 fields in the table's text_search list view that don't match the title or description criteria. For example, in the default text_search view for the Incident table, the number, opened, caller, priority, state, category, and assignment group fields satisfy the field list criteria. Global search displays the names and values for these fields in the search result field list. |
| 3. Description | The description is the third line of the search results. This line is optional and may not appear for all search results. | Global search uses the first string field in the table's text_search list view that is not the title and is over 100 characters in length. If no field matches these criteria, the search results omit this line. For example, in the default text_search view for the Incident table, the description field satisfies the description criteria. Global search uses this field as the search result description. |
By default, the system uses the text_search list view for a table to format global text search results for that table. If a text_search view doesn't exist for the table, the system instead formats search results using the table's default form view. Implementers can specify which view the system uses to format search results by modifying the value of the glide.ui.text_search.view system property.