Service Portal and client scripts
Summarize
Summary of Service Portal and client scripts
ServiceNow customers can utilize client scripts and catalog client scripts within the Service Portal when the UI Type is set to Mobile / Service Portal or All. These scripts are designed for use with the Form widget and SC Catalog Item widget, requiring advanced coding knowledge and an understanding of Service Portal APIs.
Show less
Key Features
- Runtime Compatibility: To ensure scripts work across both mobile and desktop environments, use conditional checks on the window object.
- Unsupported Globals: Certain globals like $ and jQuery are unavailable in Service Portal client scripts, but widget client controllers can utilize Angular and jQuery.
- Embedded Widgets: You can embed widgets in catalog item forms using specific variable types and interact with gform instances.
- API Availability: Utilize glist for Glide list elements and gservicecatalog for service catalog item scripts, ensuring compatibility with Service Portal functionality.
Key Outcomes
By leveraging the guidelines for client scripts in the Service Portal, customers can enhance their catalog items with dynamic behaviors tailored for mobile and desktop users. Understanding the limitations and specific APIs available will streamline development and improve the user experience in the ServiceNow environment.
You can use client scripts and catalog client scripts in the Service Portal if the UI Type is set to Mobile / Service Portal or All. Client scripts and catalog client scripts are used with the Form widget and SC Catalog Item widget, as opposed to a widget client controller.
Before flagging a script as Mobile/Service Portal or All, make sure that you are only using the mobile APIs. Setting a client script to Mobile does not ensure that it will work, it simply flags that the script should be attempted by the mobile app or the Service Portal. Many of your existing client scripts can be set to All as long as the API calls are supported by the mobile client scripting environment.
The topics in this section require advanced coding knowledge and an understanding of Service Portal APIs.
Checking desktop vs mobile runtime
if (window === null)
// Write your mobile compatible code here
else
// Write your desktop compatible code hereUnsupported client scripting globals
The following globals and APIs are unavailable in client scripts and catalog client scripts used in the Service Portal:
- $
- $$
- $j
- angular
- control
- document
- jQuery
- window
Embedded widgets & g_form
When using the Service Catalog variable type Macro and Macro with Label, you can pick a widget to embed in a catalog item form. Within the client controller for the embedded widget you can access the field object and catalog item g_form instance using:
$scope.page.field$scope.page.g_form()
Client scripts used with Service Portal
function onLoad() {
var myListCollector = g_list.get("my_list_collector");
myListCollector.reset();
myListCollector.setQuery("active=true^category=8c7b22230b402200b0b02c6317673a62");
myListCollector.addItem('3a700d39af5f4fc0aab978df90f4c692', 'Power Supply');
myListCollector.addItem('1cb93419a3a248318da8f814140b42f6', 'Backpack');
}function onLoad() {
if (window) // if CMS, don't run this
return;
// g_service_catalog api for Service Portal and Mobile
var isOrderGuide = g_service_catalog.isOrderGuide();
g_form.setValue("is_order_guide", isOrderGuide ? "Yes!" : "Nope :(");
}