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.
UI Policies are not working on Catalog components in Mobile - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • UI Policies are not working on Catalog components in Mobile
KB0623526

UI Policies are not working on Catalog components in Mobile


1954 Views Last updated : Nov 25, 2024 public Copy Permalink
KB Summary by Now Assist

Description

UI Policies and UI Policy Actions are not working as expected on Catalog components in Mobile App or Mobile View.

For example:

  • Variables set as read-only on Requested item or Catalog Task forms remain editable on the mobile application, while the same variables are read-only on the Desktop UI.
  • UI Policies that are hiding fields are working on the Desktop UI, but in Mobile, everything is visible.

Steps to Reproduce

 

  1. Login as administrator in an OOB instance (Enterprise or Express) in Native UI
  2. Select a Catalog Item Record Producer available to Desktop and Mobile
  3. Create a Catalog UI Policy to a Variable, or Variable Set, or field in the catalog item to make it read only
  4. Observe that it works fine on the std desktop UI
  5. Switch to /$m.do or access the instance via mobile app
  6. Observe the same variable or field is not read-only and still editable
 
 

Workaround

After carefully considering the severity and frequency of the issue and the risk of attempting a fix, it has been decided to not address this issue in any current or future releases. We do not make this decision lightly, and we apologize for any inconvenience.

To receive notifications in case of a future product enhancement on this, please subscribe to this article by clicking the Subscribe button at the top right of the page.


Related Problem: PRB745444

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.