SNOW-CAD User Interface Development Practice Test 4 — 15 Questions

Question 1

Which THREE factors contribute to poor UI performance in ServiceNow forms and portals? (Choose three.)

Accepted Answer

Large number of catalog client scripts in a variable set. Option B is correct because each catalog client script in a variable set executes in the browser whenever its condition is met, and a large number of them multiplies JavaScript execution, DOM manipulation, and re-render cycles on the catalog form, degrading UI responsiveness. Option C is correct because multiple client scripts bound to the 'load' event all run synchronously during form initialization, blocking the form from rendering until every script finishes, which directly delays time-to-interactive. Option E is correct because UI Macro server scripts that issue unindexed GlideRecord queries force full table scans on the database, and since macros render inline during page generation, those slow queries stall the server response and thus the UI. Option A is not a problem: simple conditions in UI Policies are lightweight and evaluated efficiently, so they do not contribute to poor performance. Option D is not a problem: CSS custom properties are natively supported by browsers and are a performant styling mechanism, not a cause of UI slowdown.

Answer

Using simple conditions in UI Policies

Answer

Use of CSS custom properties

Question 2

Which TWO of the following are valid types of client scripts in ServiceNow? (Choose two.)

Accepted Answer

onSubmit. B. onSubmit is a valid client script type in ServiceNow: it runs on the client when a form is submitted, before the record is sent to the server, and is commonly used for client-side validation (returning false aborts submission). C. onChange is also a valid client script type: it fires when the value of a specified field changes on a form, enabling dynamic UI behavior such as showing/hiding fields or setting other field values. The other options are not client script types: onDelete and onUpdate are server-side business rule timings (before/after delete and update), while onClick is not a ServiceNow client script type (UI Actions handle click behavior). Therefore only onSubmit and onChange belong to the list of valid client script types.

Answer

onDelete

Answer

onClick

Answer

onUpdate

Question 3

A Service Portal widget displays a list of open incidents. The data is updated via a GlideAjax call in the client controller. Users report that the list does not refresh automatically when a new incident is created. The developer wants to implement auto-refresh without manual page reload. The widget is used on a dashboard that does not require real-time updates every second. Which approach is most efficient?

Accepted Answer

Use Angular $interval to call the GlideAjax every 30 seconds in the client controller. Using a polling interval (e.g., 30 seconds) strikes a balance between data freshness and server load. Option B is unnecessary since real-time updates are not required. Option C is inefficient due to full page reload. Option D misses updates when the user is not interacting.

Answer

Set up a real-time data channel using WebSocket and push updates from server

Answer

Use the 'spNavigation' API to reload the entire page every 30 seconds

Answer

Trigger the GlideAjax call on mouseover and focus events

Question 4

Refer to the exhibit. A developer wrote this client script to hide a field when another field changes to '1'. However, the script throws a JavaScript error. What is the most likely cause?

Accepted Answer

hideField is not a valid method; the correct method is setDisplay or setVisible.. `hideField` is not a valid client-side method in ServiceNow. The correct methods to control field visibility in client scripts are `setDisplay` (to show/hide a field) or `setVisible` (to show/hide a field and its label). Using an undefined method like `hideField` will throw a JavaScript error because the GlideForm (g_form) API does not include it.

Answer

hideField is a server-side method and cannot be used in client scripts.

Answer

The developer should use showFieldMsg to hide the field.

Answer

The function signature is incorrect for an onChange client script.

Question 5

A ServiceNow developer is tasked with improving the performance of a custom incident form in the classic UI. The form includes a 'category' field that, when changed, triggers an onChange client script. This script uses a GlideRecord query to fetch related data from a large 'cmdb_ci' table (over 100,000 records) and populates a dependent field called 'subcategory' with relevant options. Users report that after selecting a category, the form freezes for 10-15 seconds before the subcategory field updates. The developer needs to maintain real-time updates based on the category selection. What is the best approach to resolve this performance issue while keeping the functionality?

Accepted Answer

Replace the client script with a Scripted REST API that returns subcategory options, and make an asynchronous AJAX call from the client script to populate the field.. It offloads the heavy GlideRecord query from the client to the server via a Scripted REST API, while using an asynchronous AJAX call (e.g., GlideAjax) to avoid blocking the UI thread. This eliminates the 10-15 second freeze by preventing synchronous server-side processing on the client, maintaining real-time updates without freezing the form.

Answer

Convert the onChange script to a UI Policy with a condition on category and a script action to perform the query.

Answer

Use a calculated field on the subcategory field that derives its value from a database view.

Answer

Move the query to a Business Rule that runs on 'before' and updates the subcategory field using setValue.

Question 6

A developer needs to display a read-only summary of an incident's short description and priority on a Service Portal page. The summary must update dynamically when the user selects a different incident from a list. The developer wants to avoid full page reloads. Which Service Portal feature should be used to build this component?

Accepted Answer

A Service Portal widget. Service Portal widgets are the building blocks of portal pages. They combine server-side data retrieval with client-side AngularJS logic, enabling dynamic updates without full page reloads. A widget can listen for selection changes and refresh its data via its server script, making it the appropriate choice for a dynamic incident summary.

Answer

A UI Page with a Processing Script

Answer

A UI Macro

Answer

A Client Script of type onLoad

Question 7

A developer is creating a Service Portal page and needs to display a dynamic list of records from the 'incident' table. The list should support sorting, filtering, and pagination without writing custom client-side code. Which Service Portal widget should be used?

Accepted Answer

List. The List widget is a standard Service Portal component that renders a list of records with full interactivity, including sorting, filtering, and pagination. It is pre-built to handle these features, so no custom client-side scripting is needed. Other widgets like Simple List or Data Table lack these built-in capabilities, making them unsuitable for this scenario.

Answer

Form

Answer

Data Table

Answer

Simple List

Question 8

A developer is creating a new Service Portal page and wants to add a widget that displays a list of the current user's open incidents. The widget must be reusable across multiple pages. Where should the developer create the widget record?

Accepted Answer

In the Service Portal > Widgets module. Service Portal widgets are stored in the sp_widget table and are created via the Service Portal > Widgets module. This allows them to be defined once and reused across multiple pages, either directly or as embedded widgets. Creating a widget in this module ensures it is available for reuse.

Answer

In the sys_ui_page table via a UI Page record

Answer

In the UI Builder under the Components section

Answer

In the Widgets related list on the Service Portal page record

Question 9

A developer needs to add a custom UI action button to the 'incident' form that is only visible to users with the 'itil' role and only when the incident state is 'In Progress'. Which configuration should be used?

Accepted Answer

Create a UI Action with the 'Form button' checkbox selected, set the condition to 'gs.hasRole("itil") && current.state == 2', and add the 'itil' role to the 'Roles' field.. To add a custom button to a form, a UI Action must have the 'Form button' checkbox selected. The condition script should check both the user's role and the record's state to control visibility. Adding the 'itil' role in the 'Roles' field provides an additional layer of security. The other options either use the wrong UI Action type or omit state checking.

Answer

Create a UI Action with the 'Form button' checkbox selected, set the condition to 'gs.hasRole("itil")', and leave the 'Roles' field empty.

Answer

Create a UI Action with the 'List choice' checkbox selected, set the condition to 'gs.hasRole("itil") && current.state == 2', and add the 'itil' role to the 'Roles' field.

Answer

Create a UI Action with the 'Form link' checkbox selected, set the condition to 'current.state == 2', and add the 'itil' role to the 'Roles' field.

Question 10

A developer is building a custom Service Portal widget that includes a form. The form must validate that a user-entered email address is unique across the sys_user table before allowing submission. The validation must occur without a full page reload and must provide immediate feedback. Which approach should the developer use?

Accepted Answer

Use a GlideAjax call in the widget's client script to invoke a script include that checks the sys_user table.. GlideAjax is the correct mechanism for asynchronous server-side validation from a Service Portal widget. It allows the client to call a Script Include that can query the sys_user table and return the result. This provides immediate feedback without a full page reload, meeting both requirements.

Answer

Use a UI Policy with a script condition on the sys_user table to validate the email field.

Answer

Use a client-side script with a synchronous GlideRecord query to check the sys_user table.

Answer

Use an onBefore business rule on the sys_user table to validate the email and return an error message to the widget.

Question 11

A developer is building a custom Service Portal widget that includes a form for creating new incident records. The form should validate that the 'short_description' field is not empty before submission. Where should the validation logic be implemented?

Accepted Answer

In the widget's HTML template using AngularJS directives like 'ng-required' and 'ng-model'.. Client-side validation in Service Portal widgets is typically handled using AngularJS directives. Directives like 'ng-required' and 'ng-model' allow the form to enforce field requirements and prevent submission until valid. This provides immediate feedback without server round-trips. Server-side validation should still be implemented as a backup, but the primary pre-submission check belongs in the HTML template with AngularJS.

Answer

In the widget's server script using a GlideRecord insert and checking for empty values before insertion.

Answer

In the widget's client controller using the 'c.server.get' method to validate the field asynchronously.

Answer

In a UI Policy on the 'incident' table that makes the field mandatory when the form loads.

Question 12

A developer is creating a new Service Portal widget that displays a list of records from the incident table. The widget must allow users to filter the list by state and priority using dropdowns. The filtering should happen without a full page reload. Which TWO actions must the developer take to implement this functionality? (Choose two.)

Accepted Answer

Use the widget's server script to query the incident table and apply the filter conditions based on the client-side variables.. To implement dynamic filtering in a Service Portal widget, the developer must bind the dropdowns to client-side variables using AngularJS and then use the widget's server script to query the incident table with those filter conditions. The client controller triggers the server script when selections change, updating the list without a page reload.

Answer

Add a GlideAjax call in the client script to directly query the incident table and update the list.

Answer

Create a UI Policy on the incident table to filter records based on the dropdown values.

Answer

Configure the widget's option schema to include the state and priority fields as filter options.

Question 13

A developer creates a Service Portal widget that displays a list of records. The widget's client controller uses an ng-repeat directive to render the records, but the list does not update when the underlying data changes via a background script. The developer confirms the server script returns updated data when the widget is reloaded. What is the most likely cause?

Accepted Answer

The widget does not have a mechanism to automatically refresh when the underlying data changes.. Service Portal widgets are stateless and do not automatically re-render when database records change. The client controller retrieves data once during initialization. To reflect changes made by background scripts, the widget must implement a refresh strategy such as polling, web sockets, or a manual refresh button. Without such a mechanism, the displayed data remains static until the page is reloaded.

Answer

The ng-repeat directive is missing the track by clause, causing AngularJS to not detect changes.

Answer

The widget's client controller is not using $scope.$apply() after updating the data model.

Answer

The widget's server script is not using GlideRecord correctly to fetch the records.

Question 14

A developer needs to add a 'Resolve with Notes' button to the Incident form. When clicked, the button must open a modal dialog that contains a text area and a 'Submit' button. The modal must capture user input and then update the incident record via a GlideAjax call. Which UI mechanism should the developer use to implement this modal dialog?

Accepted Answer

Use the GlideModal class from the client-side API to open a dialog that contains a UI Page or a custom form.. The GlideModal class is the correct client-side API for creating modal dialogs in ServiceNow. It allows a developer to open a dialog containing custom HTML or a UI Page, capture user input, and then process it, for example by calling GlideAjax to update the record. The other options either use deprecated technology, non-existent methods, or misapply UI Policies.

Answer

Create a UI Action that uses the 'gs.submitModal' server-side method to render a modal dialog.

Answer

Create a UI Page with a dialog template and link it to a UI Action using the 'onclick' attribute.

Answer

Add a new section to the form and use a UI Policy to conditionally display it as a modal.

Question 15

A developer is creating a Service Portal widget that displays a list of tasks assigned to the current user. The widget's server script queries the task table and returns an array of task records. The client script uses ng-repeat to render the list. Users report that the list does not update when a new task is assigned to them unless they manually refresh the page. The developer wants the list to update automatically when a new task is assigned. Which approach should the developer take?

Accepted Answer

Add a record watcher in the client script using the spUtil.recordWatch method to listen for changes to the task table.. The spUtil.recordWatch method is designed for real-time updates in Service Portal. It uses the ServiceNow record watcher service to notify the client when records matching a filter change. By using recordWatch, the widget can automatically refresh its data when a new task is assigned, providing a seamless user experience. Polling, event queues, or non-existent properties do not achieve this efficiently.

Answer

Set the widget's 'Live Update' property to true in the widget editor.

Answer

Use a GlideAjax call in the client script to periodically poll the server for new tasks every 30 seconds.

Answer

Configure the widget's server script to use the gs.eventQueue method to push updates to the client.