- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2015 08:15 AM
Hello Community,
I have just found a problem throughout my instance where my UI Policies are not setting fields to be Read Only on the RITM level. I have a UI Policy for every catalog item that I have that is set to run only on the Requested Item level and the Task level. It sets every field on the form to Read Only. I have just noticed that none of these are working. My first thought is that it has something to do with the view..maybe something has changed that I'm not aware of. Any ideas here? I'm starting to feel like i'm chasing a ghost.
Solved! Go to Solution.
- Labels:
-
User Interface (UI)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2015 02:10 PM
So I have found the problem. There was a field removed from the form. Just so happens its the field that maintains the relationship between the catalog item and the UI policies. Added the field back and all is well again. Thanks for the assistance everyone!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2015 08:36 AM
I would also check for javascript errors on the page thrown by a client script or something that might keep the ui policy from evaluating. You can use the chrome dev console or an equivalent to check that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2015 08:42 AM
I viewed that already. There was an error due to bad code in a UI Action but even after fixing that problem, the UI Policies still don't function.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2015 09:04 AM
Try to stop all UI Policies/ Client script to run except for the Read only UI policy and see if it fixes the issue. Then you can know its one of the Client Script/ UI policy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2015 10:12 AM
I have done this for this particular item and found nothing. Keep in mind, this is for every catalog item that I have in my instance so I feel like I'm aiming a bit too low. I'm thinking more globally but I only have 1 UI Script running globally and I've turned that off with no change. I'm trying to find something that would be all inclusive so to speak.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2015 02:10 PM
So I have found the problem. There was a field removed from the form. Just so happens its the field that maintains the relationship between the catalog item and the UI policies. Added the field back and all is well again. Thanks for the assistance everyone!