The UI for the sysapproval_approver form breaks if the Approval Summarizer UI Formatter contains ServiceCatalog variables.

A client side error 'ServiceCatalogForm is not defined' occurs.

Steps to Reproduce

  1. On a demo instance, open a RITM that has some variables.
  2. In the Catalog Tasks related list, open a sc_task record (or create a new one if none exist).
  3. On the sc_task form, scroll down to the Approvers related list and create sysapproval_approver records.
  4. Open the sysapproval_approver record and bring the Approval Summarizer UI Formatter to the form (if it's not already there).
    Note that the form is broken.


  1. Create a new UI macro with the following details:

    Name: approval_summarizer_workaround


    <?xml version="1.0" encoding="utf-8" ?>
    <!-- WORKAROUND FOR PRB632062 -->
    <j:jelly trim="true" xmlns:j="jelly:core" xmlns:g="glide" xmlns:j2="null" xmlns:g2="null">
    <g:requires name="scripts/js_includes_catalog.js"/>
    <g:requires name="styles/expert.css" />
    <g:requires name="styles/sc_cat.css" />
    <g:requires name="styles/sc_cat_only.css" />
    <g:requires name="scripts/expert.js"/>
    <g:requires name="scripts/classes/ServiceCatalogForm.js"/>
    <g:requires name="scripts/catalog.js"/>
    <g:approval_summarizer />
  2. Go to System UI > Formatters and open the record where the name is Approval Summarizer.
  3. Replace approval_summarizer_master.xml in the Formatter field with approval_summarizer_workaround.

Related Problem: PRB632062

Seen In

Fuji Patch 11
Fuji Patch 3
Fuji Patch 7 Hot Fix 5
Helsinki Patch 0 Hot Fix 1

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-12-30 06:09:30