UI Policies not working for non-admin role
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2025 12:54 AM - edited 06-19-2025 01:00 AM
I had created an ui policy to make configuration item field on sc_task table as mandatory for particular catalog items .But for admin users it's working as expected as it is being mandatory, for non-admin users that field is read only and non-mandatory.
Those users can see cmdb_ci table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2025 03:59 AM
Hi @Sahil_kashyap,
You need to check for RITM ACLs since it is dot walked field. Also there is an alternative way, where you can add Resolver variables which will only appear on sc_task for those particular items and set the Catalog UI Policies appropriately.
Regards,
Ehab Pilloor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2025 05:42 AM
Hi @Sahil_kashyap ,
You can make a field both Read-Only and Mandatory, but Read-Only takes priority. This means that even if the field is empty, the form can still be submitted because the user can’t edit the field. It’s similar to how Mandatory takes priority over Visible.
In your case, the field is being made Read-Only by an ACL or a script, which is why the Mandatory rule isn’t working.
If my response helped, please mark it as the accepted solution ✅ and give a thumbs up👍.
Thanks,
Anand