Dot Walking in a Catalog Item UI Policy not working

[kevinray]

I have a reference field in my catalog item that looks up servers in our cmdb_ci_hardware table.

I have two other questions that I want to ask based on the class of the server they select

I created a UI Policy and dotwalk to the class field

The issue is that as soon as a populate the build type with "Copy of an Existing Server" the Storage size windows field shows up on the form.

It doesn't even wait for me to select the server to know what the cpr_server_name.Class even is.

[sethivarun]

Hi Kevin,

What is the other OR condition in this UI policy.

Also, the storage size , is it being used in any other ui policy action?

[kevinray]

Varun. Thanks for the inquiry. The other OR wasn't applicable so I didn't include it.

It states:

An no, I have confirmed that the cpr_storage_size_windows variable is not used in any other UI Policy.

[sethivarun · Accepted solution]

Hi Kevin,

Apparently UI policy doesn't work with dot walking

Conditions

The conditions which, if fulfilled, cause the UI policy to be applied. Conditions are built with the condition builder. To set conditions using a script, use a client script instead. Conditions are only rechecked if a user manually changes a field on a form. If the change is made by a UI action, context menu action, or through the list editor, it is not evaluated. In UI11, the field must be on the form to be checked by a UI policy. To test the value of a field but hide it from users, add the field to the form and use UI policies to hide it. This requirement also prevents dot-walked fields from being used as conditions.

HEre is the link Create a UI policy

Please mark the answer has helpful or correct based on the impact on the question

[kevinray]

Well that's a great big huge bummer.

I guess i'll have to figure out how to do it using Glide on a Client Script.

Thanks for the info Varun.