CAD Practice Questions

Debugging client-side scripts in ServiceNow involves using methods that provide feedback during

script execution. The following methods are commonly used:

g_form.addInfoMessage():

Description: Displays informational messages to the user within the form interface.

Usage: g_form.addInfoMessage('Your message here');

Purpose: Useful for providing real-time feedback or debugging information directly on the form

during script execution.

jslog():

Description: Logs messages to the browser's console.

Usage: jslog('Your debug message here');

Purpose: Helps developers output debugging information to the browser console, which can be

inspected during development.

Incorrect Options:

gs.addErrorMessage(): This is a server-side method used to display error messages to the user and is

not applicable for client-side debugging.

gs.log(): Another server-side method used to log messages to system logs, not suitable for client-side

script debugging.

Reference: For more detailed information, please refer to the official ServiceNow documentation on

Client-Side Scripting.

"Add instructional text and other design elements to your forms by using form annotations in Form

Builder." https://docs.servicenow.com/bundle/sandiego-applicationdevelopment/page/administer/form-builder/task/create-form-annotations.html

A Record Producer is a type of service catalog item that allows users to create records on a specified

table. A Record Producer has the following characteristics:

Graphics can be included on the user interface: You can add images, icons, or banners to the Record

Producer to make it more appealing and informative for the user. You can also use HTML and CSS to

customize the layout and style of the Record Producer.

You can script behaviors of fields in the user interface: You can use Client Scripts and UI Policies to

control the behavior and appearance of the fields on the Record Producer. For example, you can use

Client Scripts to validate the field inputs, perform calculations, or populate default values. You can

also use UI Policies to show or hide fields, make fields mandatory or read-only, or set field values

based on conditions.

Each field prompts the user with a question rather than a field label: You can use the Variable

Question field to define the question that prompts the user for the field value. The question can be

more descriptive and user-friendly than the field label. For example, you can use the question “What

is the name of the project?” instead of the field label “Name”.

The other statements are not true for Record Producers. Record Producers do not always insert

records into the Requested Item [sc_req_item] table. They can insert records into any table that is

specified in the Record Producer properties. Record Producers also do not have to be scripted. They

can use the default script that maps the variable values to the record fields, or they can use a custom

script that defines the logic for creating the record.

Reference:

[Record Producers]

[Record Producer properties]

[Record Producer scripts]

Application Access is a feature that allows you to control the access level of other application scopes

to your application’s data tables. You can use Application Access to control the following database

operations:

Create: This operation allows the user to create new records on the table. You can enable or disable

this operation by selecting or clearing the Can create option.

Delete: This operation allows the user to delete existing records on the table. You can enable or

disable this operation by selecting or clearing the Can delete option.

Read: This operation allows the user to view the records on the table. You can enable or disable this

operation by selecting or clearing the Can read option.

Write: This operation allows the user to modify the records on the table. You can enable or disable

this operation by selecting or clearing the Can write option.

The one database operation that cannot be controlled with Application Access is Query. Query is not

an operation, but a method of the GlideRecord class that is used to retrieve records from the

database on the server-side. Query is not part of the Application Access rules, but it is affected by the

Access Controls and the user’s roles.

Reference:

Application Access

[GlideRecord methods]

there are only two types of UX options: Mobile and Classic. Classic is defined as "manage records via

lists and form"

In ServiceNow, the Caller Access field is used to define the level of access that external scripts or

applications have to a particular script include or application resource. The valid options for the

Caller Access field are:

None: No special restrictions are applied; the resource is accessible as defined by other security

settings.

Caller Restriction: Limits access to the resource, allowing only specified callers or applications to

invoke it.

Caller Tracking: Enables tracking of which callers are accessing the resource, providing an audit trail

for monitoring purposes.

Options such as "Accessible from," "Allow Configuration," and "Caller Permission" are not valid

selections for the Caller Access field.

For more detailed information, refer to the official ServiceNow documentation on Restricted Caller

Access Privileges.

In ServiceNow, to display data from another table within a form, the Reference field type is used. A

Reference field creates a relationship between the current table and another table by storing a

unique identifier (sys_id) of a record from the referenced table. This allows users to select a record

from the referenced table and access its data within the form. Therefore, the correct answer is B.

The other field types do not provide this functionality:

A . Phone Number: This field type is designed to store phone numbers and does not create

relationships between tables.

C . Date: This field type is used to store date values and does not reference records from other tables.

D . String: This field type stores text strings and does not facilitate querying records from another

table.

For more detailed information, refer to the official ServiceNow documentation on Field Types.

:

The ServiceNow App Repository is a central repository for all scoped applications that are published

by all ServiceNow customers. It enables ServiceNow customers to upload and distribute applications

between their instances. It also provides entitlements and version control for the applications.

Reference:

ServiceNow application repository

Application Development Platform – ServiceNow

App Repo - ServiceNow Developer Blog

A spoke is a scoped application that contains flow actions that can be used in Flow Designer. Spokes

allow developers to create reusable actions that can be shared across applications and instances.

Reference:

Spokes - Product Documentation: San Diego - ServiceNow

Create a spoke - Product Documentation: San Diego - ServiceNow

Flow Designer Spokes - ServiceNow Developers