SNOW-CAD User Interface Development — 10 Questions

Question 1

Which TWO of the following are valid ways to customize the Service Portal login page?

Accepted Answer

Override the 'Login' page in the portal record by creating a new page and setting it as the login page.. Option B is correct because in Service Portal you can replace the default login page by creating a new page and assigning it as the login page in the portal record's Login page field, which is a supported customization approach. Option D is correct because the portal theme's SCSS uses CSS variables (e.g., $brand-primary, $body-bg) that cascade to login page elements, allowing styling changes without altering the login widget itself. Option A is not valid because the 'loginpage' widget slot is not a supported extension point for adding widget instances to the login page. Option C is not valid because the login widget does not expose a widget option for injecting custom CSS. Option E is not valid because there is no 'login.css' system property in sys_properties for pointing to a custom stylesheet URL.

Answer

Create a new widget instance on the 'loginpage' widget slot.

Answer

Add a widget option to the login widget to inject custom CSS.

Answer

Set the 'login.css' property in sys_properties to a custom stylesheet URL.

Question 2

This client script is attached to the 'category' field on the incident form. When the user changes the category to 'Network', what happens to the short_description field?

Accepted Answer

The short_description is set to 'Category changed to Network'.. The client script checks if the newValue of the 'category' field is not empty and equals 'Network'. When the user changes the category to 'Network', newValue is 'Network', which passes the empty check (newValue !== ''), and then the condition newValue === 'Network' is true. The script then executes g_form.setValue('short_description', 'Category changed to Network'), which sets the short_description field to that string.

Answer

Nothing happens because newValue equals 'Network' which passes the empty check.

Answer

An error occurs because setValue cannot be called with a string.

Answer

The short_description is cleared.

Question 3

A company has a Service Portal that includes a custom widget for submitting hardware requests. The widget has a client controller that calls a server script to create a new record in the 'hardware_request' table. Recently, users have reported that when they click the 'Submit' button, the widget sometimes does not show a success message, and the record is not created. The developer reviews the server script, which uses gs.log to log errors, and sees no errors in the logs. The client controller uses $scope.server.get() to call the server. The widget template uses ng-show='data.success' to display a success message. Based on this scenario, what is the most likely cause of the intermittent issue?

Accepted Answer

The client controller does not handle the asynchronous response properly; the success message depends on the promise resolving before the user might navigate away or click again.. The client controller uses $scope.server.get() to make an asynchronous call to the server script. If the user clicks 'Submit' and then navigates away or clicks again before the promise resolves, the success message (ng-show='data.success') may never display because the $scope.data object is not updated in time. The server script logs no errors because it executes correctly, but the client-side asynchronous handling fails to capture the response, leading to the intermittent issue.

Answer

The server script fails due to a mandatory field not being provided, but the error is not logged.

Answer

The server script uses data.success = true; but the client controller does not read it.

Answer

The widget has a Client Script that conflicts with the server script.

Question 4

A company wants to hide a field on a catalog item form when a specific variable is selected. What is the most appropriate way to achieve this?

Accepted Answer

Create a UI Policy that hides the field when the condition is met.. UI Policies are the standard declarative way to control field visibility, read-only, and mandatory states on ServiceNow catalog item forms based on conditions. Option B is incorrect because modifying the form layout only changes the initial arrangement and does not dynamically hide fields. Option C is incorrect because a catalog client script can be used but is less standard and efficient than a UI Policy for visibility control. Option D is incorrect because a client script setting the display property is not the recommended approach; UI Policy is specifically designed for such conditional logic.

Answer

Modify the form layout to remove the field.

Answer

Use a catalog client script to hide the field.

Answer

Write a client script to set the field's display property to false on load.

Question 5

A service portal widget is supposed to load data from a table and display it in a list. The widget renders but shows no data. Which is the most likely cause?

Accepted Answer

An error in the widget's server script prevents data from being queried.. If the widget renders but shows no data, the most likely cause is that the server script—which executes the GlideRecord query—encountered an error, preventing data from being fetched. A syntax error in the client script would typically break rendering or produce a JavaScript error, but the widget still renders.

Answer

The table's ACL denies read access to the user.

Answer

The widget's client script has a syntax error.

Answer

The portal page is not configured to include the widget.

Question 6

A form has a UI Policy that conditionally makes a field mandatory. The UI Policy works on the server side but the mandatory validation is not enforced on the client side before submission. What is the most likely reason?

Accepted Answer

The UI Policy is set to run only on the server and not on the client.. UI Policies have a 'Run scripts' or execution scope setting that determines whether the policy executes on the client (browser), the server, or both. If the policy is configured to run only on the server, the mandatory field validation is applied when the record is submitted to the server but is not enforced in the browser before submission, which matches the described symptom. Setting the policy to run on both client and server restores the client-side mandatory enforcement.

Answer

The field's ACL does not allow the user to see it.

Answer

The form is in a different ordering of UI Policies.

Answer

A client script is overriding the mandatory property.

Question 7

A reference field on a form shows a list of records, but the user cannot see any results when typing. The reference qualifier is set to 'active=true'. What is the most likely cause?

Accepted Answer

There are no records that satisfy the reference qualifier condition.. If the reference qualifier condition 'active=true' filters out all records (e.g., all records are inactive), no results appear. Option A is incorrect: lack of read access would prevent the user from seeing any records at all, but the user can see the field and type. Option C is incorrect: a read-only field prevents editing but does not affect searching for new records. Option D is incorrect: if no reference table were specified, the field would not function; the problem is the qualifier filtering.

Answer

The user does not have read access to the referenced table.

Answer

The field is read-only and prevents searching.

Answer

The field's dictionary entry does not have a reference table specified.

Question 8

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.. The onChange client script uses g_form.setValue to update 'short_description', but if that field is configured as read-only on the form, the setValue call will be silently ignored. ServiceNow enforces read-only at the UI level, preventing any client-side modification to the field's value. Thus, even though the script executes correctly, the field remains unchanged. This is the most likely reason because other options involve syntax or timing issues that would typically cause script errors or partial failures, not a silent no-op.

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 9

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 10

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.