Catalog UI Policy and/or Catalog Client Script not showing all variables to monitor for change

[William Hadley]

I have been beating my head on the wall with this one. I'm working in a Washington DC PDI that is brand new with demo data. I'm trying to run either a Catalog UI Policy or Catalog Client Script that triggers on State change. I have come across extensive documentation indicating to set them to trigger on State change from the condition selector (UI Policy) or changed variable (UI Script); however, I only have access to custom variables on the Catalog Item via these methods (no option to select any default variables/fields like State). There is no option to monitor the state in either scenario.

Why is it that I cannot see anything else in the condition/variable selectors for the Catalog Item I'm working with when I see everyone else's examples with screenshots showings it's possible? Is there a configuration setting I'm missing that is limiting what I can see on which to base my policy and scripts?

[James Chun · Accepted solution]

Hi @William Hadley,

What you are doing there is adding a UI Policy/Client script on the Catalog Item, hence it's called the Catalog UI Policy/Catalog Client Script. These dictate the behavior of the 'form' - i.e. the form users use to submit a request. So from here, you only have access to the variables of the catalog item and 'state' is not part of it.

Instead, what you should be doing is creating a UI policy on the Requested Item [sc_req_item] record.

Hope it helps, thanks

[James Chun · Accepted solution]

Hi @William Hadley,

What you are doing there is adding a UI Policy/Client script on the Catalog Item, hence it's called the Catalog UI Policy/Catalog Client Script. These dictate the behavior of the 'form' - i.e. the form users use to submit a request. So from here, you only have access to the variables of the catalog item and 'state' is not part of it.

Instead, what you should be doing is creating a UI policy on the Requested Item [sc_req_item] record.

Hope it helps, thanks

[SunilKumar_P · Accepted solution]

Hi @William Hadley, Catalog UI Policies / Catalog Client Scripts are specfic to the catalog item and this deals with variables only. The 'state' field you are talking about belongs to the table (Ex - sc_req_item or sc_task) and the tables fields are not accessible to the catalog ui policies. Hence, you can try the table level UI Policies.

Regards,
Sunil

[sunwin93]

Hi @William Hadley ,

I hope you are doing good.

Please check below points to tackle the issue you are facing.

1. We can apply ui policy or client script on the variables of catalog item/record producer only . We can not access the fields of any table when we write ui policy/client script for catalog item/ record producer.

2. You can not apply policy/script on dot walking also.

3. Please check application.

Please mark my response helpful if you find it so.

Thank you

Sanjeet

[William Hadley]

I can't believe I was so caught up in tunnel vision that I wasn't even thinking about the table on which the policies were looking. It makes total sense that the state is of course not on the catalog item but on the sc_req_item and sc_task tables. I appreciate the answers!