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.
In the RITM record, the REQ value is being cleared upon loading - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • In the RITM record, the REQ value is being cleared upon loading
KB0817744

In the RITM record, the REQ value is being cleared upon loading


610 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

If you look at a RITM record, when you open it, the REQ value is being cleared upon loading.

Resolution

The issue occurs due to custom Ui policy on that specific catalog item.
g_form.clearValue('request') was used.
As per "applies to" in the UI policy record the details will be listed as per the below documentation.

Create a UI policy for catalog items


Applies to : Select the type of item this UI policy applies to:
A Catalog Item: enables the Catalog item field.
A Variable Set: enables the Variable set field.
Catalog Item or Variable Set Select the catalog item or a variable set this UI policy applies to. The field name and options available depend on the Applies to selection.
Now, in this case, an advanced script was used in which it is pointing to the name "request" which is the same name as of field and variable, which is not recommended.
Fields name should not be used for creating the variable.


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.