UI policies not reversing when false

[TEdwards]

We have a problem with UI policies not reversing when false if the user changes the mind about their answer mid-submission. For example, in one catalog item the user has three options to choose from. If they choose one of two options (New Access or Change existing access) then several variables appear which require answers.

If the user answers Yes to one of these questions, a required text field appears for them to complete.

However, if the user realizes in mid-submission that they should have chosen "Remove access", the text field ("Please indicate the picklist to which the employee should be added") does not disappear.

This happens in other catalog items as well. I was wondering if anyone else had experienced this and what they did to resolve it. A colleague has recommended adding yet another UI policy which makes the text fields not visible under the appropriate conditions to counteract this problem, but this does not seem practical, especially when "Reverse if false" should make the unneeded field(s) not visible.

[TEdwards · Accepted solution]

Actually we believe we have an answer to this. When the user chooses "New Access" or "Change current access" in answer to the question "Please indicate whether this is new access or modification to existing access" our catalog UI policy makes the variable "Does the employee need to be added to a picklist?" visible. Another catalog UI policy makes the text field appear when the user answers "Yes" to this question. When the answer to "Please indicate whether this is new access or modification to existing access" is changed to "Remove access" the policy that makes "Does the employee need to be added to a picklist?" visible is reversed, but since a separate policy makes the text variable appear it does not affect that variable. 

Thanks to all who offered their thoughts regarding this!

[Ankur Bawiskar]

Hi Tricia,

Can you also mark answer as correct and close the thread

Regards

Ankur

[Rohit54]

Hi TEdwards,

How do you finally achieved the goal of removing the field when the field

[TEdwards]

I eventually ended up putting the variables into variable sets, and hiding the variable sets instead of the variables themselves, but we are having much more success subsequently by using catalog client scripts instead of UI policies as our requirements have become more complicated.