Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

UI Policy is not working

beycos
Tera Contributor

Hi everyone,

I’m working on a form that has a choice field with 4 different options. Each option should display a different set of fields. To achieve this, I created 4 separate UI Policies, one for each option.

However, I’m running into a problem:

  • Some fields are included in more than one UI Policy Action

  • When I change the option, the fields from the previous UI Policy remain visible

  • Even if I disable Reverse if false, the issue continues

  • It looks like the UI Policies are overriding each other and not resetting the form correctly

My question: What is the correct way to handle this scenario when the same field appears in multiple UI Policies? Should each field only be controlled by a single UI Policy, and if so, what is the recommended structure for 4-option logic?

Any guidance or best practices would be greatly appreciated.

Thanks!

2 ACCEPTED SOLUTIONS

AndersBGS
Tera Patron

Hi @beycos 

 

You're correct - when multiple UI policies are created for the same field(s), the behavior can be of unexpected result. You should instead just have 1 UI policy pr. field and define the rule set.

 

If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.

Best regards
Anders

Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/

View solution in original post

ServiceNow Use6
Tera Guru

I will tell you the logical way to do UI Policies.

check which are the fields are common among certain conditions, make it separate UI Policy. For all unique fields create a separate UI Policy with that condition.

Regards

Suman P.

View solution in original post

2 REPLIES 2

AndersBGS
Tera Patron

Hi @beycos 

 

You're correct - when multiple UI policies are created for the same field(s), the behavior can be of unexpected result. You should instead just have 1 UI policy pr. field and define the rule set.

 

If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.

Best regards
Anders

Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/

ServiceNow Use6
Tera Guru

I will tell you the logical way to do UI Policies.

check which are the fields are common among certain conditions, make it separate UI Policy. For all unique fields create a separate UI Policy with that condition.

Regards

Suman P.