UI Policy conflict behavior when switching field values without saving the record

[themadhankumar]

Hi Team,

I am facing a doubt related to UI Policy behavior and I would like some clarification.

I have created two UI Policies on the Incident table:

1. UI Policy 1

   • Condition: Category = Hardware

   • Action: Subcategory = Mandatory

2. UI Policy 2

   • Condition: Category = Network

   • Action: Subcategory = Visible = false

Scenario I am observing:

• I create a new Incident record

• First, I select Category = Hardware
  → Subcategory becomes mandatory (this works as expected)

• Without saving the record, I change Category = Network
  → Subcategory is still visible (UI Policy 2 does not apply)

• If I change back to Hardware, Subcategory again becomes mandatory

Now, if I create another new Incident:

• First, I select Category = Network
  → Subcategory becomes not visible (this works)

• Then without saving, I change Category = Hardware
  → Subcategory becomes mandatory

• After that, if I switch back to Network, the Subcategory visibility does not change as per UI Policy

So the UI Policy seems to work correctly only the first time, based on which category is selected first, and then it does not always revert correctly when switching values without saving.

My doubt:

• Is this expected behavior of UI Policies?

• Do UI Policies evaluate only once per form load?

• Is this because the record is not saved?

• Do I need to use Reverse if false, order, or Client Scripts to handle this?

Please let me know the correct approach to handle this scenario.

Thanks in advance.

[Najmuddin Mohd]

Hello @themadhankumar ,

I have seen this type of issue when the action is written on the same field in two different UI Policies.
So, I try to use the action in the same UI Policy and try to build conditions using OR condition. 
However, I believe the requirement here cannot be build within the same UI Policy.

Can you check by using Reverse if false condition. If this does not work, try with Client Scripts.


If the above information helps you, Kindly mark this as Helpful and Accept the solution.
Regards,
Najmuddin

[WillieW]

As Mohd indicated a Single Client Script defined on the category field can achieve both goals.