UI Policy not working when moved from DEV to TEST

cgreen2
Tera Contributor

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

7 REPLIES 7

Mark Roethof
Tera Patron
Tera Patron

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

LinkedIn

Arav
Tera Guru
Tera Guru

Hi,

Have you captured UI policy actions (if any) that are linked to the UI policies in the update set ?

Thanks,

Arav

Ankur Bawiskar
Tera Patron
Tera Patron

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

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader

cgreen2
Tera Contributor

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

find_real_file.png