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.
Knowledge Search box results in page not found when using it from a CMS page attached to the non oob ess site. - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Knowledge Search box results in page not found when using it from a CMS page attached to the non oob ess site.
KB0542558

Knowledge Search box results in page not found when using it from a CMS page attached to the non oob ess site.


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

Description

When implementing a custom site and modifying any of the pages that use the com.glideapp.servicecatalog_category_view UI page to display the search box when the iframe does not have a header, the search box does not work and fails to land on a result page.

This is expected behavior and only happens after enabling the UI page to display the search box while in a headless object by using the sysparm_headless url argument.

To enable a catalog in a new CMS site, a matching Catalog Site record needs to be created in the [sc_catalog_site] table. This specifies the pages that Service Catalog needs to retrieve in order to work properly. For more information, see Upgrade to Multiple Service Catalogs in the product documentation.

The resulting value of the form search action can display .do instead of the expected (base system) catalog_find.do. This value is populated in the com.glideapp.servicecatalog_category_search template, with the result of the join between the [sc_catalog_site] and the [sc_catalog] tables.

Workaround

There is no workaround for this Known Error at this time.
 

Related Problem: PRB603692

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.