UI Policy not working when moved from DEV to TEST
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2022 11:44 PM
Hi,
I've created a UI Policy on a catalog item however when i've moved the update set from Dev to Test the UI policy has been created (looks identical) but isn't working.
I've created a new update set in Dev - updated the Active / De Active / Active flag to see if that would work it when i moved it to Test but it's still not working.
Any suggestions / ideas please.
Thanks
- Labels:
-
Service Catalog

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2022 11:46 PM
Hi there,
Can you share details about your UI Policy?
Have you also debugged that the UI Policy itself is triggered at all?
Maybe there's something in the condition, referencing a record, while that specific record is not on your test environment (or under a different sys_id)?
If my answer helped you in any way, please then mark it as helpful.
Kind regards,
Mark
2020-2022 ServiceNow Community MVP
2020-2022 ServiceNow Developer MVP
---
LinkedIn
Community article, blog, video list
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2022 11:48 PM
Hi,
Have you captured UI policy actions (if any) that are linked to the UI policies in the update set ?
Thanks,
Arav
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2022 11:49 PM
Hi,
are you sure everything was captured fine in update set?
Are you sure no other script is conflicting your UI policy in the Test instance?
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2022 11:50 PM
Thanks Mark, it's really simple..all it's designed to do is show the Data Breach field on the Incident form (in the portal) when you select the Service Component ( i know it's odd that the condition is set to 'is not' but that's how they have all been build historically.
Everything else in the update set has come across okay