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.
When the conditions of the UI policy is based on Date/Time field, the UI does not trigger when the conditions become false and "Reverse if false: True" is configured - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • When the conditions of the UI policy is based on Date/Time field, the UI does not trigger when the conditions become false and "Reverse if false: True" is configured
KB0727654

When the conditions of the UI policy is based on Date/Time field, the UI does not trigger when the conditions become false and "Reverse if false: True" is configured


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

Description

The UI policy works fine when the condition based on Date variable is True. But when the condition is False, reverse if false is not triggered. The issue is reproducible with OOB date format.

Steps to Reproduce

1) Go to any London instance
2) Open the incident form from native UI and create two fields: one of type Date(test1) and one of type String(test2).
3) Create a UI policy with the following details
Conditions: test1 is not empty
Reverse if false: True
4) Create a UI policy action for the test2 variable. Read-only is true and everything else Leave alone.
5) Test on the incident form that this UI policy is working as expected. Make sure the UI policy triggers when the condition is both true or false(Reverse if false).
6) Now go to Service portal and open an incident form. Test the UI policy
https://<instance>.service-now.com/sp?id=form&table=incident&sys_id=sys_id_of_incident

Notice that the test2 variable becomes read-only when the condition becomes True. Now clear off the value in test1.

Expected result: The variable test2 should be in write based on the UI policy condition.

Actual result: The variable test2 will be in Read-only even though test1 is empty

Workaround

This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix

 


Related Problem: PRB1320823

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.