UI Policy not working

[MStritt]

Hello,

I've created several UI Policies for a field on our Problem form. Depending on the value in that field, depends on what other field shows below it. I have one UI Policy that isn't working. The default value of this field is -- None --. I've created a UI Policy that says when the value is -- None --, then don't show these other fields. However, it's not working. The other UI Policies I've created for the other values in this field, are working properly. The default value of the field is -- None --. So, when a Problem is created, this is the default value. See a short video below.

https://www.screencast.com/t/d6BtTzqaeSk

UI Policy for -- None --

I've created UI Policies for each value in the 'Survey Classification' field. Whenever one of these values is selected, only the field pertaining to that value appears (correctly).

[Ankur Bawiskar]

Hi,

Is the UI policy flag for onLoad set to true?

Does it work when form loads?

Does it work when someone changes value from xyz to None? 

Mark ✅ Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur

[MStritt]

Hi Ankur,

Is the UI policy flag for onLoad set to true?

Yes

Does it work when form loads?

No

Does it work when someone changes value from xyz to None? 

No. You can see in my video, when I click back to -- None --, all the fields appear again.

[Allen Andreas]

Hello,

Without seeing your actual form and your other UI policies, we can only help but so much.

Obviously...UI policies work, when set correctly. So it boils down to an issue with what you have setup. If you have conflicting UI policies, it'll cause undesired behavior. In all of the UI policies following this one, that affect these same fields, you should also have a condition to those that the Survey Classification IS NOT none. So you may have 2 conditions for those other UI policies, for example:

This is about the escalation classification

-Survey Classification IS NOT none

-Escalation Classification is 'x'

So then show fields A, B, C.

So that's my first suggestion for a fix.

Secondly, are any of these fields set as MANDATORY on the field level? Meaning, when you created these variables or fields...is the core setting for that to be mandatory? If so....mandatory fields will ignore UI policies and still show anyway.

You would need to turn off the core field setting of it being mandatory and only trigger it being mandatory through the UI Policy when it's supposed to be mandatory (meaning after so and so fills in 'x' field or when field 'y' doesn't equal 'z').

Please mark reply as Helpful/Correct, if applicable. Thanks!

[MStritt]

Hi Allen,

Thanks for the response. I have a UI Policy for each value in the 'Survey Classification' field. Below is the UI Policy for the Escalation value. I've created the same for each of the other values.

None of the fields are mandatory.

If I add the additional Condition (IS NOT -- None --), would it be an OR or AND condition? Would I keep the UI Policy I currently have for -- None --?