Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Set global text search properties

Log in to subscribe to topics and get notified when content changes.

Set global text search properties

Administrators can control how global text search behaves with system properties.

Before you begin

Role required: admin

Procedure

  1. Navigate to System Properties > Global Text Search.
  2. Set these properties.
    Table 1. UI properties for global text search
    Field Description
    Enable Global Text Search

    glide.ui.text_search.enable

    Default value is true. Clear this option to disable the global text search capability.
    List of roles (comma-separated) that can use the Global Text Search capability.

    glide.ui.can_search

    Default value is itil, text_search_admin, admin. Add a role to enable it to use search.
    List of tables (comma-separated) that will not appear as options when setting up Global Text Search tables.

    glide.ui.no_text_search

    Default value is 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. Tables that do not appear as options when defining search groups. Examples are system or maintenance tables.
    Number of Global Text Search matches returned per table.

    glide.ui.text_search.rowcount

    Default value is 10. Users can click through to see all results for a specific table.
    Global Text Search background color for Knowledge Base results.

    css.textsearch.kb.background.color

    This property only applies to the legacy global search results page. Default value is #FFFFDD.
    Global Text Search background color for Catalog results.

    css.textsearch.catalog.background.color

    This property only applies to the legacy global search results page. Default value is #F0F7F9.
    Form view to use for Global Text Search exact match. Blank indicates the Default view.

    glide.ui.text_search.match_view

    Default value is blank.
    List and form view to use for Global Text Search results. Blank means default view.

    glide.ui.text_search.view

    Default value is the text_search view. If you do not have a text_search view, you can create it.
    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

    Default value is Simple query.
    Maximum number of results that will be returned during a text index search. This limits the number of records that are extracted from the text index and appear.

    glide.lucene.base_result_max

    Default value is 100. This property is not supported by the Simple query method and is ignored.
    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 you can indicate that more results exists for any given table that are going to appear.

    glide.lucene.base_hits_max

    Default value is 500. This property is not supported by the Simple query method and is ignored.
    Number of simultaneous processes (1 to 16) used when searching though multiple groups in a global search.

    glide.ts.global_search.parallelism

    Default value is 4. Each search group uses one thread to render results.

    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.

  3. Click Save..
    The business rule Text Search Property Change Rationally validates the new values and aborts the update if they are outside its acceptable ranges.
  4. Open the System Property table and search for the property glide.ts.max_wildcard_expansion.
    Table 2. UI properties for global text search
    Field Description
    Name glide.ts.max_wildcard_expansion
    Description Maximum number of matches for a wildcard term that are allowed as unambiguous.
    Type Integer
    Value 500
  5. Edit the Value.
    If a wildcard search matches more words than this value, the system displays a message asking the user to refine the search.
  6. Click Update.
  7. To set the text search stemming language, install an internationalization (i18n) plugin.
  8. Navigate to System Properties > System Localization.
  9. Set this property.
    Table 3. Text stemming property
    Field Description

    Text Search stemming language

    glide.ts.stemming_language

    Default value is English. The system supports stemming in English, German, and French.
Feedback