How can you update the look-n-feel of the Service Catalog?

robertlankford
Kilo Expert

Our service catalog has UI elements that just look ... old.  The Item Ordering Widget, for instance, doesn't float correctly and the buttons on it are old/out of date table html elements with images embedded vs modern UI 16 button elements.

Where is this information stored?  How can I begin to figure out what needs updated and then begin the process of updating it?

 

/completely new to ServiceNow, btw, as if you couldn't tell by the question!  🙂

1 ACCEPTED SOLUTION

Ok. It's definitely not the problem I was thinking then. I think you'd better open on Incident in HI so they can log in and see more about how your system is configured. Sorry!


View solution in original post

16 REPLIES 16

ian_cox
ServiceNow Employee
ServiceNow Employee

Thanks for the response.   That didn't really get me going in the right direction, though.   The folks there are still talking at a higher level than I'm able to following along with.   Specifically, I don't know how to find/edit the CSS they keep referencing.   Again, first timer here.



So, more specifically, this what my instance looks like today:


old-widget.png



But a new developer instance looks like this instead:



new-widget.png



How can I update my instance to look like the developer instance?


Back in Fuji we introduced a new UI for Service Catalog. Existing customers did not get it if they had customized any of the files specified in CartLayoutMigration (sys_script_include_1c9c6723eb232100fcfb858ad106fe76.xml) called by a fix script "fix_sc_layout.xml". You can manually set the property to force the new UI by changing the value of the property named, "glide.sc.use_cart_layouts". Maybe this is it. What happens if you change that property in one of your sub-prods?


Thank you for the response.  


Back in Fuji we introduced a new UI for Service Catalog. Existing customers did not get it if they had customized any of the files specified in CartLayoutMigration


This sounds right to me.   I think that this could be the problem. The property that you mentioned was already set to true.  


find_real_file.png


I'm not sure what I need to do to begin to fix the issue though.