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

Question 1

The above Jelly script is used to generate a UI Page. When rendered, the 'cmdb_ci' field does not appear. What is the most likely cause?

Accepted Answer

The containing 'cmdb_ci' is improperly nested inside another . When a is nested inside another , the inner element is ignored by the Jelly UI framework. The proper structure requires that be placed directly within a or , not inside another . This nesting issue causes the 'cmdb_ci' field not to render. Option A is incorrect because the namespace is correctly declared if other fields render. Option B is incorrect because a does not need to be inside a ; it can be directly in a . Option D is incorrect because a mandatory attribute does not prevent a field from appearing; it only affects submission behavior.

Answer

The Jelly namespace declaration for 'g2' is missing, causing the field to be ignored

Answer

The element must be inside a rather than

Answer

The 'cmdb_ci' field has a mandatory attribute that conflicts with the UI policy

Question 2

A large enterprise uses ServiceNow for IT Service Management. They have a custom Service Portal for end-users to submit catalog requests. Recently, mobile users reported that the portal is extremely slow on their devices, while desktop users experience no issues. The portal theme uses many custom CSS animations and high-resolution images. Additionally, the widget client scripts are complex and make multiple GlideAjax calls on page load. The development team wants to optimize mobile performance without redesigning the entire portal. Evaluate the options and select the best course of action.

Accepted Answer

Consolidate multiple GlideAjax calls into a single server-side script and use mobile-optimized images. It directly addresses the two primary bottlenecks identified for mobile users: excessive GlideAjax calls and high-resolution images. Consolidating multiple GlideAjax calls into a single server-side script reduces the number of round trips to the server, which is critical on high-latency mobile networks. Using mobile-optimized images (e.g., compressed, appropriately sized) reduces bandwidth consumption and rendering time on mobile devices, which have limited processing power and screen sizes. This approach optimizes performance without requiring a full portal redesign, as requested.

Answer

Increase server-side caching for widgets and use a CDN for static assets

Answer

Remove all custom CSS animations and replace high-res images with scalable vector graphics

Answer

Implement lazy loading for images and defer all GlideAjax calls until after page load

Question 3

A developer created a custom form section for the 'change_request' table that contains a reference field to 'cmdb_ci'. The section is visible in the form layout for all change request types. However, when the 'type' field is set to 'Emergency', the section should not be visible. The developer added a UI Policy to hide the entire section when type is 'Emergency'. But the section remains visible. After checking, the UI Policy is active and the condition is set correctly. What is the most likely reason the UI Policy is not working, and what is the best fix?

Accepted Answer

UI Policies cannot hide form sections; they only control field-level visibility. The developer should hide each field in the section individually via UI Policy or use a client script to hide the section div. UI Policies in ServiceNow can only control the visibility of individual fields, not entire form sections. The developer must either hide each field in the section via separate UI Policy conditions or use a client script to hide the section's HTML div element. Option A is incorrect because UI Policies cannot directly target form sections. Option C is incorrect because there is no 'visible' attribute to assign. Option D is incorrect because the issue is not about order or priority.

Answer

The section's 'Visible' checkbox in the form layout must be unchecked and then controlled by the UI Policy

Answer

The UI Policy must be set to 'Run for all users' and the section must be assigned a 'visible' attribute

Answer

The UI Policy order is too low; it should be set to a higher priority number

Question 4

A developer needs to display a warning message to the user when the 'priority' field is changed to '1 - Critical'. Which TWO client-side implementations can achieve this?

Accepted Answer

UI Policy with condition: 'Priority changes' and action script to call g_form.showFieldMsg(). A UI Policy with the condition 'Priority changes' triggers an action script when the priority field is modified, allowing the use of `g_form.showFieldMsg()` to display an inline warning message on the field. Option E is correct because an onChange client script fires when the 'priority' field changes, and within it you can check `newValue` against '1 - Critical' and call `g_form.showFieldMsg()` to show the warning. Both are client-side implementations that respond to field changes without a server round-trip.

Answer

Business Rule with 'when to run' set to 'before' and script to call g_scratchpad.message

Answer

onLoad client script that checks the current value of priority and shows a message

Answer

Data Policy with condition on priority field and message set

Question 5

A developer is building a Catalog Item in Service Catalog. The item contains a variable named 'department' of type Reference, referencing the Department [cmn_department] table. When a user selects a department on the catalog item form, the developer wants the 'cost_center' variable to populate automatically with the corresponding cost center from the selected department record, without any user interaction. The variable 'cost_center' is a Single Line Text variable. Which approach should the developer use to achieve this?

Accepted Answer

Create a Catalog Client Script with an onChange handler on the 'department' variable that uses a GlideAjax call to a Script Include to retrieve the cost center and set the 'cost_center' variable value.. To automatically populate a variable based on another variable's selection, a Catalog Client Script with an onChange handler is the appropriate choice. The onChange event triggers when the referenced department variable changes. Using GlideAjax to call a Script Include allows server-side retrieval of the department's cost center, which is then set on the cost_center variable. This ensures the value updates dynamically without user intervention, leveraging client-server communication.

Answer

Create a Data Lookup variable that references the Department table and maps the cost center field to the 'cost_center' variable.

Answer

Create a Business Rule on the Department [cmn_department] table that updates the 'cost_center' variable on the catalog item form.

Answer

Create a Catalog UI Policy that runs on the 'department' variable and sets the 'cost_center' variable value using a script.

Question 6

A developer needs to make the 'assigned_to' field on the incident form mandatory only when the 'priority' field is set to '1 - Critical'. The requirement must be enforced on both the desktop UI and ServiceNow Agent workspace. Which approach should the developer use?

Accepted Answer

Create a UI Policy that sets the 'assigned_to' field to mandatory when 'priority' is '1 - Critical'.. UI Policies are the correct declarative mechanism to conditionally set a field to mandatory based on another field's value. They can be configured to run on both the client and server, ensuring enforcement in the desktop UI and Agent workspace. This eliminates the need for custom scripts and provides a consistent user experience across interfaces.

Answer

Add a UI Action button that validates the 'assigned_to' field when priority is '1 - Critical'.

Answer

Create a Data Policy that sets the 'assigned_to' field to mandatory when 'priority' is '1 - Critical'.

Answer

Write an onLoad client script that checks the priority value and makes the 'assigned_to' field mandatory.

Question 7

A developer needs to display a read-only, live-rendered list of the current user's open change requests inside a custom Service Portal page. The list must update automatically whenever the underlying change_request records are modified, without a full page reload. Which Service Portal component should be used to meet these requirements with the least custom code?

Accepted Answer

Add an instance of the 'Data Table' widget and set its table, filter, and columns via widget options.. The Data Table widget is the standard Service Portal component for displaying a configurable, filterable list of records from a table such as change_request. It handles server-side data retrieval and rendering within the AngularJS portal framework and refreshes appropriately when records change, making it the correct choice for a live, read-only list with minimal custom code.

Answer

Create a UI Macro that queries change_request with GlideRecord and render it with Jelly inside the page.

Answer

Add an instance of the 'Simple List' widget to the page and configure its data table and filter options.

Answer

Embed a report on the change_request table using the Report widget and set the report to run on demand.

Question 8

A developer is customizing a Service Portal page and needs to add a new widget that displays a chart of incident counts by category. The widget should fetch data dynamically from the server. Which TWO steps are required to make the widget's server script return data to the client? (Choose two.)

Accepted Answer

Define the data object in the server script and populate it with the desired data.. To return data from a widget's server script to the client, the server script must define and populate a data object. The client controller then accesses this data via 'c.data'. These two steps are fundamental for dynamic data exchange in Service Portal widgets. Other methods like 'c.server.update()' are for refreshing data, not initial retrieval.

Answer

Set the 'data' object in the server script to an array of records.

Answer

Use the 'c.server.update()' method in the client controller to trigger the server script.

Answer

Add the 'server' attribute to the widget's HTML template.

Question 9

A developer is creating a UI Page that uses Jelly to display a list of users from the sys_user table. The developer wants to ensure that only active users are shown. Which Jelly tag should be used to conditionally filter the records?

Accepted Answer

j:glideRecord. The j:glideRecord tag is used in Jelly to query a table and iterate over the results. By including a query condition like 'active=true', only active users are retrieved. This is more efficient than retrieving all records and filtering them in the Jelly code. The other tags do not provide database-level filtering for GlideRecord queries.

Answer

j:if

Answer

j:set

Answer

j:while

Question 10

A developer is building a custom Service Portal widget that must display a count of active incidents for the logged-in user's assignment group. The count must be computed on the server and returned to the client controller for display without a full page reload. Which approach correctly retrieves the count from the server?

Accepted Answer

Call a Scripted REST API from the client controller and have the API return the count as JSON.. The server script of a Service Portal widget already executes on the server and can use GlideAggregate or GlideRecord to compute the count. To return that value to the client controller without a page reload, the widget's server script should populate the data object, and the client controller reads it from the c.data object. A Scripted REST API is also a valid server-side mechanism, but the most direct and idiomatic portal approach is to compute the count in the widget server script and expose it via c.data.

Answer

Use g_form.getValue('assignment_group') in the client controller to read the group, then query the incident table client-side.

Answer

Embed a UI Page that runs a GlideAggregate on the incident table and include it in the widget's HTML template.

Answer

Use GlideAjax with a client-callable script include that returns the count from a GlideAggregate.

Question 11

A developer is creating a new UI Action on the Incident form. The UI Action should be visible only to users with the 'itil' role and should only appear when the incident state is 'In Progress'. The developer writes a condition script that checks the user's roles and the state. However, the button appears for all users regardless of role. What is the most likely cause?

Accepted Answer

The UI Action's 'Client' checkbox is selected, causing the condition script to be evaluated on the client side where g_user.hasRole is not available.. When a UI Action has the 'Client' checkbox enabled, its condition is evaluated in the browser using client-side APIs. The g_user object on the client does not support the hasRole method; that method is available only in server-side scripts. Using it in a client-side condition will either throw an error or not work as expected, often resulting in the condition being ignored or returning true, thus showing the button to all users.

Answer

The UI Action is not associated with the correct table, so it appears on all forms.

Answer

The UI Action's 'Condition' field contains a script that returns true for all users, or the 'Visible' checkbox is not checked.

Answer

The UI Action's 'Condition' field is empty, and the script is placed in the 'Script' field instead.

Question 12

A developer creates a UI Page that uses Jelly to render a form-like interface. The developer wants a field named 'cmdb_ci' to appear on the page, but when the page is rendered, the field does not appear. The Jelly script includes a <g:ui_reference> tag for the field. What is the most likely cause?

Accepted Answer

The tag requires a 'name' attribute that matches the field name, and it is missing or incorrect.. The Jelly tag renders a reference field and requires a 'name' attribute that matches the field name on the table. If that attribute is missing, misspelled, or does not correspond to an actual field such as cmdb_ci, the tag will not render the field. This is the most common cause of a field not appearing in a Jelly-rendered UI Page.

Answer

The 'cmdb_ci' field is not present on the form layout used by the UI Page.

Answer

The 'cmdb_ci' field is read-only on the table, so Jelly cannot render it.

Answer

The UI Page lacks a 'client script' that populates the field value before rendering.

Question 13

A developer is asked to add a custom button to the Service Portal form for the 'incident' table. The button should trigger a client script that displays a confirmation dialog before submitting the form. Which approach should the developer use?

Accepted Answer

Create a UI Action on the incident table with a client script and set the 'Show insert' condition.. UI Actions in Service Portal are the standard mechanism for adding custom buttons to forms. By creating a UI Action on the incident table with a client script, the developer can add a button that triggers a confirmation dialog before form submission. UI Policies only control field attributes (e.g., visibility, mandatory) and cannot create new UI elements like buttons.

Answer

Create a UI Policy on the incident table with a client script that shows the button conditionally.

Answer

Create an Access Control Rule (ACL) on the incident table and attach a client script.

Answer

Create a Business Rule on the incident table that injects a button via server-side code.

Question 14

A Service Portal widget is failing to update a reference field on a form after a user selects a value from a reference picker. The developer reviews the widget's client controller and sees the following code snippet: $scope.c.data.selectedItem = value; The server script expects 'selectedItem' to be a sys_id string, but it is receiving an object. What is the most likely cause?

Accepted Answer

The reference field returns an object with 'value' and 'display' properties; the code should extract the sys_id.. When a reference picker returns a value in Service Portal, it typically provides an object containing both the display value and the sys_id (e.g., {value: 'sys_id', display: 'name'}). The client controller code assigns this entire object to $scope.c.data.selectedItem, but the server script expects a plain sys_id string. The developer must extract the sys_id property (e.g., value.sys_id or value.value) before assigning it to the scope variable.

Answer

The server script expects the parameter in a different scope variable, like $scope.c.data.item.

Answer

The $scope.c.data assignment is incorrect; it should be $scope.data.

Answer

The client controller is not allowed to set $scope.c variables.

Question 15

When configuring a Service Portal page, a developer wants to ensure that a specific widget appears only to users with the 'itil' role. Which approach should be used?

Accepted Answer

Set the 'Roles' property on the widget instance within the page designer.. The 'Roles' property on a widget instance within the Service Portal page designer directly controls which roles can view that specific widget. This is the intended declarative approach for role-based visibility at the widget instance level, without requiring custom scripting or ACLs.

Answer

Pass a role check from the server script to the client controller via widget options.

Answer

Write an Access Control Rule (ACL) on the widget's table to restrict access.

Answer

Create a UI Policy on the portal table that hides the widget based on user roles.