Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Service Catalog release notes

Log in to subscribe to topics and get notified when content changes.

Service Catalog release notes

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

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

London upgrade information

Before upgrading, you should be aware of changes made to the underlying Service Catalog data model. These changes affect the way that 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.

New in the London release

Multi-row variable set
Use a multi-row variable set to capture variable data in a table layout while submitting a catalog item request for a group of entities.
Note: This variable set is also available in Service Portal.
Automated test framework for Service Catalog in Service Portal
Write automated end-to-end tests for requester flows to validate catalog items in Service Portal. When you upgrade or modify an instance, run these tests to confirm that the instance still works as designed. The following test step configurations are available in the Automated Test Framework (ATF) for Service Catalog in Service Portal:
  • Open a Catalog Item (SP)
  • Open a Record Producer (SP)
  • Set Variable Values (SP)
  • Set Catalog Item Quantity (SP)
  • Validate Variable Values (SP)
  • Variable State Validation (SP)
  • Validate Price and Recurring Price (SP)
  • Add Item to Shopping Cart (SP)
  • Order Catalog Item (SP)
  • Submit Record Producer (SP)
Note: ATF for Service Catalog in Service Portal is not supported for order guides and multiple items in the cart.
Checkout Shopping Cart ATF test step configuration
Use the Checkout Shopping Cart server test step configuration to test the submission of a shopping cart in the Now Platform and Service Portal.
Assert type for the Search for a Catalog Item ATF test step configuration
Use the Assert Type field in the Search for a Catalog Item test step configuration to specify the condition for the success of the test step.
Create Request UI action
Create a catalog request from other flows to join the Service Catalog flow. By default, this UI action is available from the incident flow, where you can create a request, and associate the request with the incident. You cannot add items to the wish list or save a record producer in these flows.
When you create a request from an incident, the caller of the incident is automatically set as the Requested For user for both the one-step and two-step checkout. If the two-step checkout is enabled, the fulfiller can change the Requested For user.
Note: The Best Practice - Incident Resolution Workflow plugin (com.snc.bestpractice.incident) should be active for creating a request from an incident.

Associate a record producer request with the parent table record by retrieving the sysparm_parent_sys_id and sysparm_parent_table parameters from the URL using the RP.getParameterValue() method in the Script field of the record producer.

Request Parent Mapping submodule
Use the Request Parent Mapping submodule to add the mapping configuration for associating a request with any parent table record. Only the admin and catalog_admin roles have access to this submodule.

By default, the request mapping configuration is available for the Incident [incident] table.

Service Catalog parameters
Use the following Service Catalog parameters to link the parent record to the child record when using the catalog experience, that is, when a catalog is launched from a parent record (for example, incident).
  • sysparm_parent_sys_id
  • sysparm_parent_table
  • sysparm_view
Variable SQL Debugger
Use the Variable SQL Debugger to analyze the impact of the variable setup of a catalog item on its runtime performance, and identify the issues, if any. You can review the processing time of the catalog item and its variables based on the triggered SQL queries.
Permission tab for a variable
Use the Permission tab while creating a variable to specify the read, write, and create roles of the variable.

If no role is specified in this tab for the read, write, or create actions, all users who can access the catalog item can perform these actions irrespective of their role. For example, if no role is specified for the Write roles field, all users who can access the catalog item can edit the variable value in the variable editor.

If you are upgrading to London and the catalog item form has been customized, the Permission tab is not visible until you revert the customization.

Decryption support for a masked variable
Decrypt and encrypt the values of a masked variable using the Show and Hide buttons. These buttons are not available for a fulfiller (itil) without the catalog_view_masked role. However, the requester always has access to these buttons and the variable value on records submitted by the requester. The decryption support is also applicable in Service Portal.
Order for a catalog UI policy action
Use the Order field for a catalog UI policy action to specify the sequence in which the UI policy action is evaluated. The order is evaluated from the lowest value to the highest value. This order is also applicable in Service Portal.
Post-processing script for a record producer
Use the Post insert script field on a record producer form to include scripts that operate on the submitted record, after the record is inserted in the associated table.
Note: Post insert script overrides the target record values and record producer template values.
Clear a variable value using a catalog UI policy action
Select the Clear the variable value check box on a catalog UI policy action to clear the variable value. The selection is also applicable in Service Portal.
Auto-population of names for variables and variable sets
The Internal name field for a variable set is auto-populated based on the Title field for all variable types except break, container split, and container end.

The Name field for a variable is auto-populated based on the Question field for all variable types except break, container split, and container end.

Server-side scripting support for variables of a variable set
Use the Internal Name field of a variable set to access its variables that are set on the target record. You can access the variable value of the target record in a script using:
gr.variables.variable_set_name.variable_name
For example, consider a variable set with the internal name vset and the variable single. Access the variable value of the target record in a script using:
gr.variables.vset.single
Ability to access variables for task records
Use scripts to access variables of task records using the following access points:
  • gr.variables: Gets GlideElementVariable of variables and variable sets associated with a GlideRecord.
  • gr.variables.getVariableValues(): Gets the name value pair of variables associated with a GlideRecord.
  • gr.variables.getElements(): Gets GlideElementVariable for variables within a GlideRecord.
  • gr.variables.<var_name>.getQuestion(): Returns the Question object of each GlideElementVariable.
Support for a record producer variable mapped to an encrypted field
If the record producer variable is mapped to an encrypted field of a target table, then this variable value is not stored in Question Answer [question_answer] table. So, this variable value is also not available in the variable editor of the target record.
If the record producer variable is masked and encrypted, and mapped to an encrypted field of a target table:
  • The variable value is not stored in Question Answer [question_answer] table.
  • The decrypted value of the variable is copied to the encrypted field of the target record.
UserCriteriaLoader API
Use the UserCriteriaLoader API to get the user criteria associated with a specific user, or a user associated with a specific linkTable. To use this class in a scoped application, use the sn_uc namespace identifier.
New method for the Service Catalog REST API
Use the following method to get the display value of the specified variable.
POST /sn/sc/servicecatalog/variables/{sys_id}/display_value

Changed in this release

Category change for the Search for a Catalog Item ATF test step configuration
Moved the Search for a Catalog Item test step configuration from the Service Catalog category to the Server category.
Choice direction of a variable question in Service Portal
The Choice direction field value of a Lookup multiple choice variable question is applicable in Service Portal.
Default quantity choice
The default quantity choices are 1–10. These values are configured under System Definition > Choice Lists for the Item [sc_cart_item] table and the quantity element.
My Request Filter condition
The default filter condition is updated to display the active requests opened by or requested for the current user by navigating to Self-Service > My Requests.
Modifications to a variable set
  • Variable set is elevated as a first-class citizen in Service Catalog. Like variables, a variable set has read, write, and create roles. If roles are provided for a variable set, the roles are applicable for the variables within the set. Roles of an individual variable are overridden by the roles of the variable set.
  • The Name field of a variable set is deprecated and replaced with the Title field.
  • Variable sets within a catalog item cannot have the same internal name.
  • The name of a variable and the internal name of a variable set cannot be the same within a catalog item.
    Note: This condition is also applicable even if a variable is not part of the variable set.
  • Any catalog client script or catalog UI policy script should refer to the internal name of a variable set instead of its name or title.
    Note: This condition is not applicable for a variable set used in a catalog UI policy action.
Preview of a catalog item or category
If the glide.sc.cat_view_use_popup_for_details property is set to true, the preview pop-up window for a catalog item or category is available when you click the info icon next to the item or category.

Details of the preview pop-up window opens the item or the category view in the Service Catalog application. This functionality is also applicable for requested items (RITM).

Prior to the London release, if the glide.sc.cat_view_use_popup_for_details property was set to true, the preview pop-up window for a catalog item or category was available when you point to the item or category.

Modifications to the Service Portal API
The result for $sp.getCatalogItem() API has changed to:

 { 
            .. 
            _fields: { 
                name:'<name>' 
                variable_name:'IO:<sys_id>' 
            } 
        } 
Prior to the London release, the result was as follows:
{ 
            .. 
            _fields: { 
                name:'IO:<sys_id>' 
                variable_name:'<name>' 
            } 
        } 
 

Removed in this release

  • Removed sc_cat_item_producer from the exclusion list of the glide.sc.item.order_guide_exclusion property.

Activation information

Active by default.

Feedback