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?

[Saurav11]

Hello,

1) Is the UI type selected as All in all the Catalog UI policies?

2) Are any of the UI policy part of any varibale set?

3) Does all of them contain the field as UI policy action or in the script?

Please let me know the above it would be easier to assist you

[Kohei4]

Hi,

Thank you for your reply.

1) Yes, All is selected in UI Type

2) No, they are not in any variable set, they are directly configured in the record producer

3) All of them are included in the script

[Saurav11]

In all the script can you all g_form.addInfoMessage('somemessage');

and then see in what order the info message appeared on the form and is it as per the execution order

[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...