Service Catalog release notes

ServiceNow® Service Catalog product enhancements and updates in the Jakarta release.

Service Catalog provides a customer-facing view of available service and product offerings provided by departments within the organization.

Jakarta upgrade information

Before upgrading, you should be aware of changes made to the underlying service catalog data model. These changes affect that way you implement multiple service catalogs. For details, see Upgrade to multiple service catalogs.

If you are upgrading from a version prior to the Fuji release, see Migrate cart layouts.

Activation information

Service Catalog is active by default.

New in the Jakarta release

Debug UI Customization
Debug UI Customization, a new submodule introduced under the Catalog Administration module, enables catalog administrators to perform a health check of Service Catalog pages. The corresponding UI indicates UI macros that have been customized and skipped during an upgrade, enabling catalog administrators to pinpoint the issue and self-heal. It helps you identify the source of broken functionality due to customized UI macros in Service Catalog when you upgrade to a new release. Use the Disable UI Customization Debug module submodule under the Catalog Administration module to turn off the debugger.
Variable Watcher
The Variable Watcher tab is available for Service Catalog variables. A catalog administrator can monitor individual variables for changes in their state and value due to Catalog Client Scripts, Catalog UI Policies, and Catalog Data Lookups.
Variable Action Logger
For a full analysis of all the client-side actions affecting the state and values of every variable on a catalog form, use the Variable Action Logger window. Use the new submodule, Enable Variable Action Logger, under the Catalog Administration module to enable this feature. This feature is available only for catalog administrators. Once enabled, you can track the full chronology of actions that happen on all variables of a catalog form. These actions happen due to Catalog Client Scripts, Catalog UI Policies, and Catalog Data Lookups.
Full feature support for variable editors on records created via record producers
The Applies on Target Record check box available in the Catalog UI Policies and Catalog Client Scripts submodules ensures that they are applicable on the default variable editors. Catalog UI Policies, Catalog Client Scripts, Catalog Data Lookups, Reference Qualifiers, and dependent reference fields are supported on the default variable editor used for records created via record producers. This support is applicable only for records created for task-extended tables via record producers.
Enhancements to variables
The following variables are introduced:
  • IP Address: Use this variable type to capture the IPv4 and IPv6 data for a catalog item. Under the Validation Scripts submodule, a validation script type associated with this variable is available.
  • Duration: Use this variable type to capture the duration-related data for a catalog item.
The following enhancements are made to existing variables:
  • Apart from the Macro, Macro with label, and UI page variable types, Service Portal supports all types of variables.
    Note: Convert the UI Macro variable to portal widget and associate with the same widget.
  • Service Portal supports two-column layouts only for the top-level containers.
  • You can specify example text as a hint for a variable before you enter a value.
Variable set extension
When you apply Catalog UI policy Actions and GlideForm APIs (setReadOnly, setMandatory setDisplay) on a variable set, the actions are applied on every variable within the variable set. You can make variables read-only and mandatory, or change the display of variables by performing these actions on the corresponding variable set. The same feature is available for containers as well.
Note: This feature is not supported on Service Portal.
Catalog UI Policy condition builder
Variables associated with a variable set have the variable set name associated with them in the Catalog UI Policy condition builder as well as in the Catalog UI Policy Actions list.
Automated Test Framework for Service Catalog
Catalog administrators can write automated tests to validate their catalog items because Service Catalog is supported in the Automated Test Framework (ATF). You can write end-to-end tests for both the requester and fulfiller flows. You can perform the following functions as part of the ATF for Service Catalog:
  • Search for a catalog item or record producer
  • Open a specific catalog item or record producer
  • Set variable values
  • Set item quantity
  • Validate variable values
  • Validate variable states
  • Validate price and recurring price
  • Add items to the shopping cart
  • Order a catalog item
  • Submit a record producer
Note: Only catalog items and record producers are supported for Service Catalog in the ATF. Order guides are not supported in this release. ATF is not supported for Portal flows.
Record producer redirection settings
You can configure the redirect behavior of a record producer after its generation in the UI.

Changed in this release

  • Copy behavior of a catalog item : When you perform the Copy UI action on a catalog item, all the associated variables, Catalog UI Policies, Catalog Client Scripts, and Catalog Data Lookups are copied along with the catalog item.

    When using the Language Internationalization plugins, if you perform the copy action in English, a copy of the catalog item is made for English. If you perform the copy action in a language other than English, a copy of the catalog item is made for that language and for English.

    Previously, when you copied a catalog item, any other records in the platform that had a reference to the catalog item were also copied. For example, when you copied a catalog item, any product model associated with the catalog item was also copied.

    In Jakarta, such platform associations are not copied along with a catalog item unless specified. Under the Service Catalog properties, use the Relationship tables which should be part of Copy Item action. Table Name should be comma separated. property to specify the table names of associations that should be copied. Use a comma-separated list with no spaces between the values.

  • Behavior of the g_form.clearValue() API: If the g_form.clearValue() API changes a variable value in the Catalog form, this API invokes the onChange scripts for that variable. For example, if the g_form.clearValue(‘text1’) clears the value of a Single Line Text variable, text1, then this API invokes the onChange scripts for text1 to change the value from ‘abc’ to ‘’. The g_form.clearValue() API also works on variable editors.
  • Service Catalog is 508 and WCAG A compliant.

Removed in this release

  • All fields except the variable fields have been removed from the Catalog UI Policy condition builder to avoid any confusion when creating Catalog UI policies.
  • The Description field has been removed from the Question tab on the Variable form.