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.
Homepages - Hiding a content block with conditions also hides all Homepage Widgets below it - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Homepages - Hiding a content block with conditions also hides all Homepage Widgets below it
KB0598070

Homepages - Hiding a content block with conditions also hides all Homepage Widgets below it


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

Description

Hiding a content block by using a script in the Condition field will also hide any blocks placed below it.

 

Steps to Reproduce

  1. Create a new content_block_static record with the following information (also shown in the attachment):

    • Category: General
    • Conditional: Checked
    • Condition: gs.getSession().hasRole('admin');
  2. Add this this block to the ITIL Homepage so that it has content blocks above and below it.

  3. View the homepage while logged in as the System Administrator.

    Note that the block shows as expected.

  4. Impersonate an ITIL user that does not have the admin role.

  5. View the ITIL Homepage again.

    The content block is not visible and all elements below the block are also hidden.

Workaround

This is expected behaviour. The condition field of a CMS content block is meant to work on CMS pages, not Home pages. While some CMS widgets may run on Home pages be aware they were not developed for Home pages but for CMS pages.

Content Blocks were designed for Content Pages (CMS), not for Home Pages. Although they might work on home pages, it is recommended not to use them on Home Pages, as this is not supported.

Since Helsinki, Responsive Dashboards can be used. Like Home Pages, these do not support some Content Blocks features, and we do not plan on supporting them, as Dashboards are not CMS Content Pages.

It is not recommended to rely on the content block condition field, because it will make difficult migrating to Dashboards, which rely on proper ACLs to grant access to content instead of condition expressions.


Related Problem: PRB648998

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.