If base system UI pages (for example, com.glideapp.servicecatalog_cat_item_view) are changed, they do not receive the updated references to style sheets introduced in the Geneva release. The changes in Geneva involve updating references to style sheets using a script include named CatalogCssSelector. This makes future changes to style sheets easier to apply by editing a single point (script include) instead of individual UI pages.

Steps to Reproduce


On a pre-Geneva instance:

  1. Navigate to System UI > UI Pages.
  2. Search and open com.glideapp.servicecatalog_cat_item_view.
  3. Make a change.
  4. Click Save.

In an upgrade Geneva instance:

  1. Navigate to an item with variables.
  2. Note that the components on the page are not laid out correctly.


To manage most of the CSS issues, each customized page must include lines to call the missing scripting files.

  1. Navigate to System UI > UI Pages.
  2. Search for the UI page with CSS issues.
    In the example below, the UI page is named com.glideapp.servicecatalog_cat_item_view.
  3. Include the lines below just after the line <j:jelly trim="false" xmlns:j="jelly:core" xmlns:g="glide" xmlns:j2="null" xmlns:g2="null">.

    <g:requires name="scripts/js_includes_catalog.js" includes="true"/>
    <g:requires name="styles/${new CatalogCssSelector().getVariableCss()}" includes="true"/>
    <g:requires name="styles/${new CatalogCssSelector().getCatalogCss()}" includes="false"/>
    <g:inline template="sc_sanitize.xml"/>

  4. Save the record.
  5. More adjustments may be required, depending on your customizations.

Related Problem: PRB648370

Seen In

Geneva Patch 3 Hot Fix 2

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-07-25 12:34:09