UI Policy not making field visible

[kirkr]

We've recently added a new State value to the Catalog Task table.

Label: On Hold

Value: -5

When selecting this choice, a new field should be shown via UI Policy, On hold reason [u_on_hold_reason]

This worked in our non-production instances, but once pushed to production, the UI Policy isn't making this field visible. I've cloned production to non-production and the issue is reproducible in the non-production instances now. When looking at the form, the field is't visible but if I change this value in the List View, it does appear.

I've used cache.do to clear the cache, but this didn't fix it.

I've put a number of details below, but does anyone know how to resolve this?

Changing Status [state] to On Hold does not display On hold reason.

Changing this value from the List View, does work.

I've enabled UI Policy debugging, and it indicates that is is running and properly changing the visibility

Here is how I've configured the UI Policy

[kristenankeny]

Are there any client scripts also running that might impact the visibility of the field?

[kirkr]

Unfortunately no, I've checked for Client Scripts and other UI Policies.

There had been a Data Policy, but I've disabled that which all it did was enforced the UI policy.

[Jaspal Singh]

Can you try once by changing the value of State On Hold to something else other than -5.

[kirkr · Accepted solution]

As I was doing your suggestion, I figured this out. Apparently I didn't have the On hold reason field added to the Catalog Task form in production which explains the symptoms.

I seem to come up with new ways to surprise myself with with simple mistakes. Sigh