|
**Enable Global Text Search** \(**glide.ui.text\_search.enable**\)
|
Option to enable global search in Core UI and UI15.- Type: Boolean
- Default value: **true**
- Supported values:
- **true**: Global search is enabled in Core UI.
- **false**: Global search is disabled in Core UI.
**Note:** When Next Experience is enabled, this system property has no effect. To enable or disable the Unified Navigation search field in Next Experience, set the **glide.ui.polaris.global\_search** system property described in [Next Experience system properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/pol-sys-properties.md).
|
|
**List of roles \(comma-separated\) that can use the Global Text Search capability** \(**glide.ui.can\_search**\)
|
Comma-separated list of user roles that allow access to global search. To enable global search for users with a role, add the role to this list.- Type: String
- Default value: **itil, text\_search\_admin, admin**
|
|
**List of tables \(comma-separated\) that won't appear as options when setting up Global Text Search tables** \(**glide.ui.no\_text\_search**\)
|
Comma-separated list of tables that don't appear as options when defining text search groups for Core UI. Examples are system or maintenance tables.- Type: String
- Default value: **sys\_audit, sys\_event, ecc\_queue, ecc\_event, syslog, syslog\_transaction, sys\_journal\_field, sys\_audit\_relation, ecc\_agent\_log, ecc\_mi\_result, sysrule\_escalate\_history, sys\_user\_token, sys\_time\_dimension, sys\_attachment\_doc, sys\_audit\_delete**
|
|
**Number of Global Text Search matches returned per table** \(**glide.ui.text\_search.rowcount**\)
|
Maximum number of matching records previewed for each table on the global text search results page. Users can select a table to see all matching results for that table.- Type: Integer
- Default value: 10
**Note:** This system property only controls the global text search preview limit in Core UI. In Next Experience UI, you can set the global search preview limit by editing the **Now Experience Search Configuration** record in the Workspace Global Search Configurations \[sys\_aw\_global\_search\_config\] table.
|
|
**Global Text Search background color for Knowledge Base results** \(**css.textsearch.kb.background.color**\)
|
Background color for Knowledge article global text search results. This property only affects display of results on the legacy global search results page.- Type: String
- Default value: **\#f0f7f9**
|
|
**Global Text Search background color for Catalog results** \(**css.textsearch.catalog.background.color**\)
|
Background color for Catalog global text search results. This property only affects display of results on the legacy global search results page.- Type: String
- Default value: **\#ffffdd**
|
|
**Form view to use for Global Text Search exact match - blank means Default view** \(**glide.ui.text\_search.match\_view**\)
|
Name of the form view that global text search uses to display exact match results. If no value is specified, global text search uses the default form view. For information on creating and managing views, see [View management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/view-management-overview.md).
- Type: String
- Default value: \(empty\)
|
|
**List and form view to use for Global Text Search results. Blank means default view** \(**glide.ui.text\_search.view**\)
|
Name of the list view that global text search uses to format results for each searched table. If no value is specified, global text search uses the default list view. For information on creating and managing views, see [View management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/view-management-overview.md).
- Type: String
- Default value: **text\_search**
|
|
**Query method for global text search. Run a query for each table, for each base class \(parent table\), against a single index regardless of table \(requires text index regeneration\), or let GlideRecord handle the query \(simple\). With the Zing text search engine, the preferred value is "simple"** \(**glide.ir.query\_method**\)
|
Query method to use for global text search.**Note:** The **base**, **single**, and **table** values aren't supported. Leave this system property set to its default **simple** value.
- Type: Choice list
- Default value: **simple**
- Available values:
- **base**: Run a search query for each base class. This value is no longer supported.
- **simple**: Let GlideRecord handle the search query.
- **single**: Run a search query against a single text search index. To use this method, you must regenerate text search indexes. This value is no longer supported.
- **table**: Run a search query for each searchable table. This value is no longer supported.
|
|
**The maximum number of results that will be returned during a text index search. This limits the number of records that will be extracted from the text index and displayed** \(**glide.lucene.base\_result\_max**\)
|
Maximum number of results that global text search will return when searching a text search index.**Note:** When the query method is set to **simple**, this property is ignored.
- Type: Integer
- Default value: 100
|
|
**The maximum number of entries that will be retrieved from the text index. Only the table that is involved will be returned from the text index for all entries that are between the value specified for maximum results and this value. This is done so that it can be indicated that more results exists for any given table that are going to be displayed** \(**glide.lucene.base\_hits\_max**\)
|
Maximum number of entries that global text search will retrieve from a text search index.**Note:** When the query method is set to **simple**, this property is ignored.
- Type: Integer
- Default value: 500
|
|
**Number of simultaneous processes \(1 to 16\) used when searching though multiple groups in a global search** \(**glide.ts.global\_search.parallelism**\)
|
Number of concurrent threads global text search uses when searching multiple search groups. Each search group requires one thread.Set this value to yield optimal results for your search group configuration. For example, if you have five search groups and four threads, the first four groups run in parallel and the fifth group starts when one of the first four groups finishes. This setup may work well if one of the groups is much larger than another. Similarly, if you have five search groups, setting this value higher than five yields no benefits.
- Type: Integer
- Default value: 4
|