Service Portal and client scripts
Summarize
Summary of Service Portal and Client Scripts
The Service Portal supports client scripts and catalog client scripts when the UI Type is set to Mobile / Service Portal or All. These scripts are used with the Form widget and SC Catalog Item widget, and they must utilize mobile APIs to function correctly in the Service Portal or mobile app. Compatibility with both environments can be achieved by checking the runtime.
Show less
Key Features
- Runtime Compatibility: Use a conditional check to write code that behaves differently on mobile and desktop environments.
- Unsupported Globals: Certain globals and APIs like $ and $$ are not available in Service Portal client scripts, but widgets can still use Angular and jQuery.
- Embedded Widgets: You can embed widgets in catalog item forms and interact with them via the client controller.
- glist and gservicecatalog APIs: Use these APIs for managing lists and determining if a script is part of an order guide in the Service Portal.
Key Outcomes
By utilizing client scripts effectively in the Service Portal, customers can enhance user interactions, manage catalog items dynamically, and ensure that their scripts function seamlessly across desktop and mobile platforms. Understanding the limitations and supported APIs will enable customers to implement robust solutions tailored to their organization's needs.
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 :(");
}