Reference Field Type:

The Reference field type is used to create a relationship between two tables. It allows you to select

and display records from another table directly on a form.

For example, adding a "Caller" field to an Incident form enables you to query and select records from

the sys_user table.

Why Other Options Are Incorrect:

Option B (Phone Number field type): This is used for storing phone numbers, not for querying

records from another table.

Option C (String field type): While this stores plain text, it does not allow querying or establishing

relationships with other tables.

Option D (Date field type): This is used for date or time values, not for referencing another table.

Reference:

ServiceNow Developer Documentation on Field Types .

A transform map determines the relationships between fields in an import set table and fields in an

existing ServiceNow table. It also specifies how to transform the imported data before mapping it to

the target table.

Reference:

1. What Exactly is an Import Set? - ServiceNow Developers

Import set table - ServiceNow Application Development [Book]

Extending an existing table such as the Task table when creating a new application has several

benefits, such as:

You can repurpose existing fields by simply changing the label. For example, you can change the

Short description field to Summary or Title for your new table.

You can use existing fields with no modifications. For example, you can use the Assigned to, Priority,

and State fields for your new table without changing anything.

Existing logic from the parent table will be automatically applied to the new table. For example, you

can inherit the Business Rules, Client Scripts, and UI Policies from the Task table for your new table.

The only option that is not true is d) All of the parent table records are copied to the new table.

Extending a table does not copy any records from the parent table to the new table. It only creates a

new table that inherits the fields and logic from the parent table.

Reference:

[Extend a table]

[Task table]

Reference: https://docs.servicenow.com/bundle/geneva-servicenow-platform/page/administer/

navigation_and_ui/reference/r_ModuleLinkTypes.html

A module is a navigation item that provides access to a feature or functionality in ServiceNow.

Modules must have a link type, which determines how the module behaves when clicked. The

following is a list of link types:

Assessment. This is a link type that opens an assessment, which is a survey or questionnaire that

measures the effectiveness of a process or service.

List of Records. This is a link type that opens a list of records from a table or a saved filter.

Separator. This is a link type that creates a horizontal line to separate modules in the application

menu.

Timeline Page. This is a link type that opens a timeline page, which is a graphical representation of

the duration and sequence of events or tasks.

The following are not link types, but other module attributes or field types:

List of Records, Separator, Catalog Type, Roles. These are not link types, but a combination of a link

type (List of Records), a module attribute (Separator), a field type (Catalog Type), and a user attribute

(Roles).

List of Records, Content Page, Order, URL (from arguments:). These are not link types, but a

combination of a link type (List of Records), a module attribute (Content Page), a field name (Order),

and a link type argument (URL).

Assessment, List of Records, Content Page, Roles. These are not link types, but a combination of a

link type (Assessment), a link type (List of Records), a module attribute (Content Page), and a user

attribute (Roles). Reference: Modules, Create a Module

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-appcreator/concept/guided-app-creator.html

The source control operation used to store local changes on an instance for later application is called

a stash. A stash is a temporary storage area for uncommitted changes that are not ready to be

pushed to a remote repository. Developers can use stashes to save their work in progress without

committing it to the local repository or discarding it. Stashes can be applied later to restore the

changes to the working directory, or dropped if they are no longer needed. Reference: [ServiceNow

Docs - Stash local changes], [ServiceNow Docs - Source control]

Reference: https://docs.servicenow.com/bundle/orlando-applicationdevelopment/page/build/applications/task/ t_StashLocalChanges.html

https://docs.servicenow.com/bundle/tokyo-servicenowplatform/page/administer/notification/task/t_CreateANotification.html

https://developer.servicenow.com/dev.do#!/learn/learningplans/quebec/new_to_servicenow/app_store_learnv2_automatingapps_quebec_when_to_send

The Weight field in an Email Notification determines which notification is sent when multiple

notifications are triggered for the same record and recipients. Only the notification with the highest

weight is sent. A weight value of zero means the notification is always sent when the notification’s

When to send criteria is met. A weight value of -1 means that no email should be sent3.

Reference: Email Notification Weight

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

lists and form"

Understanding Scoped Applications:

Scoped applications in ServiceNow are designed to isolate and protect application-specific code and

data. Server-side scripts within scoped applications can use the gs (GlideSystem) object for logging

and debugging purposes. However, not all gs methods are appropriate or valid for scoped

applications.

Valid Logging Methods in Scoped Applications:

gs.info():

This method logs informational messages to the system log. It is commonly used for general-purpose

logging when developers need to track execution flow or display debug data. Example:

gs.info('This is an informational log message.');

gs.error():

This method logs error messages to the system log. It is used to indicate problems or issues

encountered during script execution. Example:

gs.error('An error occurred during script execution.');

Incorrect Options Explained:

gs.debug() (Option B): This method is not valid in scoped applications. It is a legacy logging method

available in the global scope but restricted in scoped applications.

gs.iog() (Option C): This is a typographical error and not a valid gs method in ServiceNow.

gs.logError() (Option E): This is not a recognized ServiceNow API method. To log errors, gs.error() is

used instead.

Best Practices for Logging:

Logging should be meaningful and avoid unnecessary entries to keep logs clean and manageable.

Avoid excessive use of logging in production environments, as it can clutter the system logs and

potentially degrade performance.

Reference:

ServiceNow Developer Documentation on GlideSystem (gs) .

SN Pro Tips on debugging and logging practices in scoped applications .

: