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?

[Kohei4]

UI Type is All as you can see in the screenshot

[kamlesh kjmar]

Hi @Kohei4 ,

To know why this is happening, first you need to know which UI Policy/Client script is exactly responsible for this. And for this you need to do debugging. Below is the link which can help you debug (there example is on RITM, you can try same on legacy view of your item) and find exactly who is responsible and then you can further analyze things :

https://www.servicenow.com/community/developer-forum/unable-to-view-value-in-form/m-p/2365857#M92594...

Once you know how to debug, you need to look for something like below in your debug console

:

Let me know if you find any difficulty in debugging.

I hope this help.

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

Regards,

Kamlesh