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.
Mandatory asterisk not correct when a field is set to read-only by a client script or ui policy (UI14) - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Mandatory asterisk not correct when a field is set to read-only by a client script or ui policy (UI14)
KB0547058

Mandatory asterisk not correct when a field is set to read-only by a client script or ui policy (UI14)


3065 Views Last updated : Jan 19, 2024 public Copy Permalink
KB Summary by Now Assist

Description

Mandatory asterisk is showing as bright red even when value is selected. The issue happens if you use a UI policy or client script (g_form.setReadOnly) to make the field read-only.

Note: the issue does not occur if you make the field read-only using the dictionary.

Steps to Reproduce

  1. Log on to a demo instance in Eureka.
  2. On the incident form, personalize the field contact_type to be Mandatory.
  3. Create an onLoad UI policy to make this field read-only.
  4. Open an existing incident form.
    Note that the asterisk is shown as bright red. The 
    field has a default value of phone, so the mandatory asterisk should be gray in color.

 

Workaround

After carefully considering the severity and frequency of the issue, as well as the the cost and risk of attempting a fix, a decision has been made not to address this issue in any current or future releases. We do not make this decision lightly and we apologize for any inconvenience. If you have any questions regarding this problem or incident, please contact Customer Support.


Related Problem: PRB618808

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.