- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2016 11:57 AM
I have a UI Policy on our Intranet form that basically makes several fields read-only when the Incident State field is "Closed." It works great on the Default View of the Incident Form, but doesn't work at all on other views.
I tried creating a different UI Policy in our Dev instance and having just the "Incident State" field in case it wasn't working because I had fields listed that weren't on the view. That did not work.
I tried unchecking Global and adding two view names in, that did not work for either of them (and broke that it was working for the "Default_View").
I tried moving the Global Field from the "When to Apply" section to the "Default" section of the UI Policy form. That didn't work either.
Any thoughts on what would keep it from working on certain views if Global is checked?
Here's how it looks right now:
Thanks,
Richelle
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2016 12:01 PM
In order for the UI policy to work, the fields involved Active, and Incident state MUST be available on all views.
Also, no other view specific UI policies should be working on those field conditions as well..
Reference:
Creating a UI Policy - ServiceNow Wiki

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2016 12:00 PM
Hi Richelle,
Can you uncheck global field once and make sure view field is empty?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2016 12:03 PM
Also make sure there are no client script or UI policies conflicting with the one you have created.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2016 12:06 PM
Thank you Pradeep,
There were no views in the View field, and I did check for conflicts. Good advice for all problem solving cases!
Happy Friday,
Richelle

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2016 12:08 PM
Thanks Richelle for the update.
FYI : All fields are evaluated by a UI policy condition even if they are not visible on the form (in UI16 and UI15 only). This removes the requirement that a field must be on a form for it to be evaluated. In UI11, a UI policy condition only evaluates fields that are present on a form; fields that are not present are not evaluated. For UI11, ensure that any field called by a UI policy exists on the form.