UI policy is not working

ANWAR BASHA · ‎04-03-2023

Hi All,

i create one UI policy in that i added some filter conditions like.

State is one of high, critical,

And

Assignment group. name does not contains HIK

And

caller is not Sam

or

caller is not RIck.

caller field is reference field from sys_user table.

order of the UI policy also correct.

i using the above conditions but UI policy is not working can any one help on this how to archive this.

Thanks,

Weird · ‎04-03-2023

Your conditions must always be AND if you don't want either user to match.
So, change the OR between the callers to AND.

Now you're saying OR so if you select Rick, then caller is not Sam and it evaluates to true.
If you change it to AND caller is not Rick, then it checks that Caller is Rick, but not Sam, but since AND requires both to be true, the condition will fail.

View solution in original post

Sagar Pagar · ‎04-03-2023

Hi @ANWAR BASHA,

Make sure there are no other UI policies/Client scripts conflicting with the same fields.

Thanks,

Sagar Pagar

The world works with ServiceNow

ANWAR BASHA · ‎04-03-2023

Hi Sagar ,

No UI policy and client scripts are not conflicting to that field.

Ankur Bawiskar · ‎04-03-2023

@ANWAR BASHA

so did you check for which condition it's failing

Regards,
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

ANWAR BASHA · ‎04-03-2023

yes @Ankur Bawiskar caller condtion only