- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2019 09:37 PM
I have a simple Catalog UI Policy (fields are hidden if a particular value is selected in a dropdown box) that is not working on the Service Portal. When the Requested Item is created the Catalog UI Policy works properly if an ITIL user triggers it. Is this common behaviour?
Solved! Go to Solution.
- Labels:
-
Service Catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2019 09:38 PM
you should check to make sure that the script or UI policy is set to run in both UI types via the dropdown on the policy/script.
Regards,
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2019 09:42 PM
I have it applying on Catalog Item view, Catalog Tasks and Requested Items. If I tick the Run Scripts checkbox on the Script tab the Run Scripts in UI Type is set to All.
Is that what you are referring to or am I missing another setting?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2019 09:56 PM
Yes, i was referring to UI type. You are good on this part if UI type is set to ALL.
Do you see any errors in console with regards to this UI policy?
did you try to convert this UI policy into onload client script to verify results?
Regards,
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2019 10:04 PM
In the browser console I can see the fields showing up as being hidden but they are still showing.
The Catalog UI Policy works if fulfillers trigger it on the back end so I'm fairly confident that the trigger/actions are correct. Will changing it to an onload client script show anything that would explain why it doesn't work on the Service Portal?
