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 )

[Pradeep Sharma]

Hi Mauricio,

You can select "Reverse if false" on your first UI policy to reverse the conditions. Why you are having the second UI policy. Also I see that the second UI policy is inactive as per screenshots.

Please let me know if i am missing something here.

[mauricio23]

Ah - you're right about it being inactive. I activated it and running into other problems. Before I start going into the other problems, what is the best way to approach this? Is there a better way than creating a second UI Policy?

[Pradeep Sharma]

Hi Mauricio,

Can you list down me the exact requirement. Is my understanding clear. Please see my first reply.

[Pradeep Sharma]

So suppose your req is assignment group is xyz then show the fields a and b. Here if you apply reverse if false checkbox to true the viceversa case will be handled in the first UI Policy itself.