UI Policy not triggering when the field is cleared by another Client script

[kailashthiyagar]

I have field A and when I select the value of 'Yes', it will make another field B as Editable else the field B will be disabled. It works fine through UI policy.

Now I have field C and on changing value in Field C, Field A will be cleared. If suppose the previously selected value in Field A is 'Yes', then Field B also will be editable. On clearing the value in Field A, the expected behavior is, UI policy should be executed so that field B will be disabled. But now field B will remain editable

Should I be writing logic again my Field C client script to take care of the original logic? I can do it but field C already have 3 choices and have plenty of logic in it. Including this as well over there will make things complicated.

[Rajesh Mushke]

Hey Kailash,

For testing: can you un check the Reverse if fasle field in your UI Policy and try again let me know.

[kailashthiyagar]

It doesnt work. Its making the UI policy fails when i change the value to "No"

[Rajesh Mushke]

then we have only two solutions here, either you need fulfill your requirement with client script or ui pocy

1). why don't you add your script in ui policy

2)make mandatory using client script, i mean everything with client script

[ursnani]

I think I have faced the same kind of situation with Dropdown values.

I have used the Client script to Achieve this, So my sugestion is to write a Client script on Field C and Clear Field A, So when you clear Field A it will automaticlaly trigger the UI policy and it works as you expected.

UI Policy:

When Field A is YES Field B is Editable.

OnChange Client Script on Field C:

When There is change on Field C Clear the Value of Field A and It will Automatically the UI Policy.

Please mark it as helpful and correct answer if this Helps.