Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Global search in CMS page (directed to search_content.do) has issues dealing with special characters - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Global search in CMS page (directed to search_content.do) has issues dealing with special characters
KB0547143

Global search in CMS page (directed to search_content.do) has issues dealing with special characters


733 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

When trying to search a term that contains the "&" character, using the global search in the ess portal (which uses the search_content.do), returns no results.

Searching for the same term using the global search on the platform (which uses the textsearch.do) finds results.

Steps to Reproduce

  1. Navigate to Knowledge > Create New.
  2. Create a new KB article.
  3. In Short Description type AT&T.
  4. Save the article.
  5. In the global search of the navigation page, search for the term AT&T.
    The article you created appears in the search results.
  6. Open the ESS portal.
  7. In the global search, search for AT&T.
    Note that the record is not found and the text is cut to AT.

Workaround

  1. Edit the ContentSearch Processor by navigating to:

    https://<your_instance_name>.service-now.com/nav_to.do?uri=sys_processor.do?sys_id=b1627a1e0a0a0b12004617aa01ea9392

  2. Change the line:

    g_response.sendRedirect(pl + '?sysparm_search=' + g_request.getParameter('sysparm_search'));

    to:

    g_response.sendRedirect(pl + '?sysparm_search=' + GlideStringUtil.urlEncode(g_request.getParameter('sysparm_search')));

  3. Click Save.
  4. Log out of the current session.
  5. Close the current browser.

Note: Ensure that you revert to the base system version of the ContentSearch Processor before upgrading the instance.


Related Problem: PRB619544

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.