Why is my OnLoad UI Policy not being respected?

[bcronrath]

Greetings, I have a UI Policy set as follows:

Business Services Affected is just a List Reference field to the Business Service field.   What's happening is that onLoad it is not hiding the region field, even though business services should be empty since nothing has been filled out yet.   I've also tried the reverse of saying "Business Services Affected is empty" and then setting visible to false on u_regions but again it doesn't seem to be respected.   Is there something I am missing here?  

Best regards,

Brian

[gemini17]

Hey Brian:

I do not see any conditions in your screen shot.   If it is service catalog item UI policy, your policy condition should be against what variable you are applying the UI policy.   Say if you have a variable type Yes or No, then your condition type should be, from the drop down select the variable and apply yes or no condition per your requirement.   You UI policy action should be whatever variable/field you want to show or hide depending on your policy condition.

Hope this is helpful.

P.S. Hit it Correct, if it works.

Thanks

Danny Raj

[bcronrath]

Hello Danny,

The condition should be there in the screenshot:   "Business Services Affected is not empty"

[gemini17]

Hey Brian:

Sorry I do see you have a condition.   In this case, I would check, if there are any client scripts that are conflicting or other UI policies.

P.S. Hit it helpful or correct as you see the impact.

Kind regards

Danny Raj

[bcronrath · Accepted solution]

Ok I guess I figured it out, basically it's because the field is mandatory in its dictionary entry that this was not working.   I had to change the field such that it is not mandatory, and then make the UI policy action also control the mandatory flag as well as the visible flag in order for this to work.   I suppose this makes sense in order to prevent required fields from being hidden on a form, although it was a bit confusing to me trying to hunt this down as it really isn't (as far as I can tell) stated in the docs anywhere that this is how it behaves.   Oh well, regardless it should be resolved now.