UI Policy conditions are not evaluated correctly when using Variables in the condition builder - Known Error

UI Policy conditions are not evaluated correctly when using Variables in the condition builder Description Conditions are not evaluated as expected when using Variables in the condition builder for SLA Definitions, UI Policies, or other condition builders. The metadata for the variables used in the filter are not parsed correctly, causing an incorrect dot-walked condition.

Steps to Reproduce

Navigate to Service Catalog > Maintain Items . Select Apple iPad 3. Modify the Variables to add a variable as follows: Name : Test Type : Yes/No Click Try It on the Apple Ipad 3 Catalog item. Set Test = Yes. Click Order Now . Go to the requested item for this request. Create a UI Policy for this form. Set the condition to Variables: Apple iPad 3, Test is Yes (to match the condition). Create a UI Policy Action that makes the Configuration Item field set to Visible. Reload the form. The Configuration Item field is no longer visible.

Note : If you use developer tools, you may see debug output like the following example.

GlideFieldPolicy: Running "test variables" UI Policy on "sc_task" table js_includes_doctype.jsx?v=07-30-2014_2110&lp=Tue_Sep_02_09_05_27_PDT_2014&c=2_36:1367 GlideFieldPolicy: >>> evaluating conditions: js_includes_doctype.jsx?v=07-30-2014_2110&lp=Tue_Sep_02_09_05_27_PDT_2014&c=2_36:1367 GlideFieldPolicy: > variables's value of " " with the condition( HASITEMVARIABLE :62d8ec0e3d07a100f3620b4a2089e4d9=Yes) evaluates to FALSE js_includes_doctype.jsx?v=07-30-2014_2110&lp=Tue_Sep_02_09_05_27_PDT_2014&c=2_36:1367 GlideFieldPolicy: GlideFieldPolicy: Setting "visible" to "false" on "assigned_to" field js_includes_doctype.jsx?v=07-30-2014_2110&lp=Tue_Sep_02_09_05_27_PDT_2014&c=2_36:1367

Workaround Use Client Scripts or Business Rules instead of UI Policies to achieve the desired outcome.

To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix.