UI Policy based on Assignment Group

[mauricio23]

Goal: The goal is to have different UI views based on Assignment Group.

I have two UI Policies on the Incident Table. Both are very similar with one minor difference:

• The CCS Billing Assignment group:
  • Has one field that is not required and non-visible.

The problem I am facing is I can't get the CCS Billing ( 2nd UI Policy ) rule to fire off. It seems that the First UI Policy (order=100) over rides the Second UI Policy (order=110).

===

First UI Policy - All Fields Required ( Assignment Group is NOT Billing )

Second UI Policy - All Fields Required ( Assignment Group is Billing )

[mauricio23]

Hi Pradeep

UI Policy - Assignment Group "Not Billing" :

• Has fields A, B, C, D.
• All required. All Visible.

UI Policy - Assignment Group: "Billing"

• Has fields A, B, C, D.
• D is not required and not visible.

When I have "Reverse if False" check on both UI Policies:

• UI Policy "Not Billing"   - A, B, C, D are not showing up as required

When I have "Reverse if False" unchecked on "Billing":

• UI Policy "Not Billing" - Field D does not display

[Pradeep Sharma]

Hi Mauricio,

Have a UI policy for the first case when the assignment group is "Not billing" and uncheck reverse if false.

For the other case just have a client script on change for assignment group i.e when assignment group is billing make field D as not visible.

[mauricio23]

Looks like I figured it out.

For the "Billing" UI Policy, I just removed fields   (A,B,C) from the definition. Leaving only field D. Seems to work so far. If it doesn't for some reason, I'll look into your second approach of using client scripts.

Thanks!