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.
Changes to UI scripts not applied to users until they manually clear their cache - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Changes to UI scripts not applied to users until they manually clear their cache
KB0539441

Changes to UI scripts not applied to users until they manually clear their cache


1593 Views Last updated : Oct 17, 2023 public Copy Permalink
KB Summary by Now Assist

Description

If a system administrator makes a change to a UI script, any user who has already looked at a page using that script will not get the updates.

This is likely the same issue as PRB584873, but more detailed steps to reproduce are included here.

Steps to Reproduce

  1. Log into an instance as admin or maint running one of the affected builds.
  2. Navigate to Incidents > All.
  3. Open an incident.
  4. Click the book icon to the right of the Short Description field.
  5. Open one of the KB articles that appear in the popup window.
  6. Click the Attach to Incident button.
  7. Navigate to System UI > UI Scripts.
  8. Open the KnowledgeScripts UI script.
  9. Add the following line of code below line number 149:
    var myTitle = document.getElementById("u_my_title").value;
  10. Repeat steps 2 through 6.
  11. Note that everything still works fine.
  12. Now repeat steps 2 through 5, but before clicking the Attach to Incident button, clear your browser cache, reload the page (easily done in Chrome by pressing CMD+SHFT+R), and then click the button.
  13. Note that now the functionality breaks.
  14. Also note that if you inspect the resource names in the browser, the name will not have changed. For example, if the resource name was https://<instancename>.service-now.com/KnowledgeFunctions.jsdbx?v=10-22-2013_2330 before step #1, it will still be https://<instancename>.service-now.com/KnowledgeFunctions.jsdbx?v=10-22-2013_2330.

 

Workaround

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

Related Problem: PRB592625

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.