Catalog UI Policy Execution Order

[Kohei4]

Hi,

I have faced an issue that catalog UI policies do not work as expected.

In my understanding, catalog UI policies execute from lower order to higher and if there is any conflict action the highest catalog UI policy should be prioritized.

However, there is a suspecious issue.

There is three catalog UI policies which control visibility of a field
A: Order 100, make invisible (using script)

B: Order 150, make invisible (using script)
C: Order 300, make visible (using script)

In this case, the field should be visible.
The field is visible on the portal as expected but in the legacy view the field is invisible
I have not found any other catalog client scripts or catalog ui policies to control the field yet.
Do you have any idea to troubleshoot? or do you have any experience to have same issue?

[Shubham Kumbhar]

Hello Kohei4,

A: Order 100, make invisible (using script)

B: Order 150, make invisible (using script)
C: Order 300, make visible (using a script)

-Add some InfoMessage in each script using method g_form.addInfoMessage()

-You will able to see the execution order properly on the form 

-Accordingly, you can change things as per need

Mark helpful based on impact.

Thank You

[Kohei4]

Thanks for your advice.
I have added g_form.addInfoMessage and confirmed that the 300 order UI Policy (make visible) is executed finaly both on legacy view and portal.

Umm...Why the field is invisible only on legacy view....

[Saurav11]

Hello,

Can you paste the screenshot of your script. It would be easier to assist you

[Kohei4]

This is the script of UI Policy C.

[kamlesh kjmar]

Hi @Kohei4 ,

Could you please confirm  Run script in UI type value, possibility is if, it is  Mobile/service Portal then it will be applicable on portal only.

I hope this help.

Please mark this helpful if this helps and Accept the solution if this solves your issue.

Regards,

Kamlesh