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

Question 1

A Service Portal widget uses AngularJS. The developer needs to share data between the client script and the HTML template. What is the correct approach?

Accepted Answer

Use the 'c' object (c.data) provided by the widget framework.. In ServiceNow portal widgets, the 'c' object serves as the client-side controller context, and data stored in c.data is accessible in both the client script and the HTML template. This is the recommended approach for sharing data within a widget. Option A is wrong because $rootScope makes data global and can lead to unintended side effects. Option B is wrong because $scope is not directly used in the widget framework; instead, the 'c' object provides the scoped context. Option D is wrong because AngularJS factories are meant for reusable services, not for widget-specific data binding.

Answer

Use $rootScope to make data globally available.

Answer

Use $scope to store data in the client controller.

Answer

Create a custom AngularJS factory to manage data.

Question 2

Which record type should be used to customize the look and feel of the UI16 interface?

Accepted Answer

UI Theme (sys_ui_theme). UI Theme (sys_ui_theme). In ServiceNow, the UI16 interface's look and feel is customized using UI Themes, which are stored in the 'sys_ui_theme' table. Option A (UI Script) is incorrect because UI Scripts are used for client-side JavaScript functions, not for theming. Option B (Portal Theme) is meant for Service Portal configurations, not the UI16 interface. Option D (Branding) handles logos, colors, and fonts but does not provide the full theme customization capabilities of UI Themes.

Answer

UI Script (sys_ui_script)

Answer

Portal Theme (sp_theme)

Answer

Branding (sys_brand)

Question 3

A business rule updates a field on the incident table after submission. However, the updated value is not displayed on the form when the record is opened again. What is the most likely cause?

Accepted Answer

A client script (onLoad) is setting the field back to its original value.. A client script (onLoad) can run after the record is opened and set the field back to its original value, overriding the value updated by the business rule. Option A is incorrect because the form does refresh when the record is opened, so the issue is not a lack of refresh. Option B is incorrect: asynchronous business rules still save their updates to the database; the timing of execution does not affect whether the value persists on the form. Option D is incorrect because hiding a field via UI Policy does not change its value; the value would still be stored.

Answer

The form is not refreshing after submission.

Answer

The business rule is set to run asynchronously.

Answer

A UI Policy is hiding the field.

Question 4

A UI Macro that displays a custom header is not appearing on the form. The macro is referenced in a UI16 theme. What is the first troubleshooting step?

Accepted Answer

Examine the UI Macro record for syntax errors in the HTML or Jelly script.. The first troubleshooting step is to examine the UI Macro record for syntax errors in the HTML or Jelly script (Option D). Syntax errors are the most common cause of a macro not rendering. Checking the browser's HTML source (A) is possible but not the first step. Ensuring the UI Macro is in global scope (B) is less likely the issue, as macros are typically accessible within the theme. Verifying UI Scripts (C) is unrelated because UI Scripts are separate client-side resources, not the macro's own code.

Answer

Check the browser's HTML source for the macro's placeholder.

Answer

Ensure the UI Macro is in the global scope.

Answer

Verify that all referenced UI Scripts are loaded.

Question 5

The client script above runs on a text field's onChange event. When the user changes the field, the 'short_description' field is not updated. What is the most likely reason?

Accepted Answer

The 'short_description' field is defined as read-only on the form.. G_form.setValue() cannot update a read-only field. If 'short_description' is defined as read-only on the form, the script will fail to change its value. Option A is incorrect because a missing semicolon would not prevent the field update; JavaScript allows optional semicolons. Option C is incorrect because g_form is available in onChange client scripts. Option D is incorrect because the onChange event fires after the new value is assigned to the field, so the script runs with the updated value.

Answer

The script is missing a semicolon after the setValue statement.

Answer

g_form is not available in the onChange client script.

Answer

The script runs before the new value is assigned to the field.

Question 6

A developer sees the above error in the browser console when an incident form loads. What is the most likely cause?

Accepted Answer

The onLoad client script uses GlideRecord, which is not available client-side.. The onLoad client script runs on the client side, where GlideRecord is not available. Using it directly in a client script causes the 'gliderecord is not defined' error. Option A is wrong because server-side scripts can use GlideRecord without error. Option C is wrong because 'GlideRecord' is spelled correctly. Option D is wrong because GlideRecord is not deprecated.

Answer

The onLoad client script is running on the server instead of the client.

Answer

The script uses a typo: 'GlideRecord' should be 'GlideRecord'.

Answer

GlideRecord has been deprecated and replaced by a newer API.

Question 7

A UI Policy with the above condition script never evaluates to true. What is the issue?

Accepted Answer

The script should not be wrapped in a function; it should directly be the condition expression.. UI Policy condition scripts are evaluated as expressions; they should directly return the condition result without being wrapped in a function. The script must be a single expression that evaluates to true or false. Option A is incorrect because UI16 does not require AngularJS for UI Policy conditions; UI Policy conditions are still evaluated as standard scripts. Option B is incorrect because there is no evidence of a misspelling, and property names can contain dots. Option C is incorrect because gs.getProperty() is permitted and commonly used in UI Policy scripts.

Answer

The condition must be written in AngularJS to work in UI16.

Answer

The property name is misspelled as 'my.property' but should be 'my_property'.

Answer

gs.getProperty() is not permitted in UI Policy scripts.

Question 8

Which TWO of the following are valid ways to create a UI Action?

Accepted Answer

Duplicate an existing UI Action from the list view.. Options A and B are correct. UI Actions can be created by duplicating an existing UI Action from the list view (Option A) or by creating a new UI Action record directly from the UI Actions module (Option B). Option C is wrong because Script Includes are separate server-side scripts and cannot be configured directly as UI Actions (they might be used in UI Action scripts, but not a direct creation method). Option D is wrong because the Form Design interface is used for layout customization, not for creating UI Actions. Option E is wrong because the Business Rules module is for business rules, a different record type.

Answer

Write a Script Include and configure it as a UI Action.

Answer

Create a UI Action from the Form Design interface.

Answer

Create a UI Action from the Business Rules module.

Question 9

Which TWO client-side APIs are available in a Service Portal widget to interact with form fields?

Accepted Answer

c.data (to bind data to the template). The correct answers are B and C. In a Service Portal widget, `c.data` is the primary mechanism for data binding between the server and client. `g_form.setValue()` is available when the widget includes a form (e.g., using the Form widget or a custom form). Option A is incorrect because `spUtil.setValue()` does not exist; `spUtil` has methods like `update` and `addInfoMessage`. Option D is wrong because `g_list.setValue()` is for list views, not standard forms. Option E is incorrect because `$scope` is AngularJS's scope but the recommended pattern in Service Portal is to use `c.data` for data binding.

Answer

spUtil.setValue()

Answer

g_list.setValue() (to set a value in a list)

Answer

$scope (to set values in the controller)

Question 10

Which THREE factors can negatively impact the performance of a ServiceNow form?

Accepted Answer

Large client script files (e.g., 100KB+).. Options A, B, and C are correct. Multiple UI Policies increase server load and client-side processing. Synchronous Ajax calls block the UI until they complete. Large client script files increase download time and parsing. Option D is wrong because the number of tabs does not significantly impact performance. Option E is wrong because AngularJS directives, when used properly, are not a performance issue.

Answer

Many tabs (sections) on the form.

Answer

Use of AngularJS directives in the form.

Question 11

A ServiceNow developer has created a custom UI page using the 'UI Page' module. The page is accessible via a direct URL, but when the user navigates to it, the page appears blank with no errors in the browser console. What is the most likely cause?

Accepted Answer

The 'Requires role' ACL restricts the page content from rendering for the user. A blank UI page without console errors often indicates that the page’s content is suppressed by a security restriction, such as a required role ACL that the user does not have. Since there are no errors, the page is being reached but the content is not rendered. Option A is incorrect because an undeployed client script would cause a client-side script error, not a completely blank page with no console errors. Option C is incorrect because if the page were not set as ‘Published,’ it would typically show an authorization error rather than a blank page. Option D is incorrect because the processing type (direct vs. producer) affects how the page is called but does not cause a blank page when the page is accessed directly.

Answer

The page references an undeployed client script that fails silently

Answer

The page is not set as 'Published' in the UI Page configuration

Answer

The page is using the 'direct' processing type instead of 'producer'

Question 12

Which of the following is the best practice for referencing a field value in a client script on a ServiceNow form?

Accepted Answer

Using g_form.getValue('field_name'). The correct answer because g_form.getValue('field_name') is the standard client-side API to retrieve the value of a field on a ServiceNow form. Option A is incorrect because g_l.get() is used for GlideAjax calls, not for direct field access. Option B is incorrect because g_form.getValue() does not take a DOM element as an argument; it expects a field name string. Option D is incorrect because GlideRecord.get() is a server-side method and cannot be used directly in a client script.

Answer

Using g_l.get('field_name')

Answer

Using g_form.getValue(document.getElementById('field_name'))

Answer

Using GlideRecord.get() to query the field value

Question 13

A Service Portal widget is not rendering on the page, and the browser console shows: 'Uncaught ReferenceError: sp is not defined'. The widget's client script uses 'sp.get()'. What is the cause?

Accepted Answer

The widget's client controller does not include 'sp' in the dependency list. The user sees an error 'sp is not defined' because the client script uses 'sp.get()' but 'sp' is not available. In Service Portal, the 'sp' API must be explicitly injected into the widget's client controller. If it is not listed in the dependencies of the client controller function, the script will not have access to 'sp'. Therefore, Option B is correct. Option A is incorrect because the order of widgets on the page does not affect dependency injection for individual widgets. Option C is incorrect because 'angular' is not required for 'sp'; it is the Service Portal API that needs to be injected. Option D is incorrect because there is no race condition; the server script runs first and does not affect the client-side dependency injection.

Answer

The widget is placed before the 'sp' provider widget on the page

Answer

The widget is missing a dependency on 'angular'

Answer

The server script runs after the client script, causing a race condition

Question 14

A developer wants to customize the appearance of a Service Portal theme. Which approach is recommended to ensure maintainability and scalability?

Accepted Answer

Define CSS custom properties in the theme's stylesheet and use them throughout widgets. The recommended approach because CSS custom properties (CSS variables) allow centralized theme management in the theme's stylesheet, making them reusable across all widgets without duplication. This ensures maintainability and scalability. Option A is incorrect because LESS variables defined in widget styles are scoped to that widget and not shared globally, leading to duplication. Option B is incorrect because editing the default theme record directly can be overwritten during upgrades, causing maintenance issues. Option D is incorrect because inline styles are not scalable, hard to maintain, and cannot be overridden systematically.

Answer

Use LESS variables inside each widget's widget styles

Answer

Edit the default theme record to change primary colors

Answer

Apply inline styles directly in widget templates for fine-grained control

Question 15

A UI Macro on a form is causing slow load times. The macro uses multiple GlideRecord queries in its server-side script. The developer wants to optimize performance without altering functionality. Which action is most effective?

Accepted Answer

Replace GlideRecord queries with GlideAggregate and cache the results. Replacing multiple GlideRecord queries with a single GlideAggregate query reduces the number of database calls, improving performance. Caching the results further avoids redundant queries. Option A is incorrect because asynchronous loading does not reduce the total server processing. Option B is incorrect because moving queries to a client script via GlideAjax only shifts the load but still requires server-side processing. Option C is incorrect because g_form.addOption() is for adding options to a select field, which does not address the macro's performance issue.

Answer

Load the macro asynchronously using UI Macro configuration

Answer

Move the queries to a client script using GlideAjax to reduce server load

Answer

Use g_form.addOption() to populate a reference field instead of building the macro