CAD Certified Application Developer - ServiceNow Questions and Answers

https://developer.servicenow.com/dev.do#!/learn/courses/sandiego/app_store_learnv2_learnmore_sandiego_learn_more/app_store_learnv2_learnmore_sandiego_form_and_list_layouts/app_store_learnv2_learnmore_sandiego_what_is_form_designer

The Form Designer is a tool that allows you to create and customize forms on the ServiceNow platform. The Form Designer has four main components:

Form layout: The form layout shows the preview of the form and allows you to drag and drop fields, sections, and related lists onto the form. You can also resize, reorder, and delete the elements on the form layout.

Page header: The page header shows the name of the table and the form that you are editing. You can also access the form properties, save the form, and switch to the form view from the page header.

Field navigator: The field navigator shows the list of available fields for the table and allows you to search, filter, and add fields to the form. You can also create new fields and edit existing fields from the field navigator.

Schema map: The schema map is not part of the Form Designer. The schema map is a separate tool that shows the relationships between tables and fields on the platform. You can access the schema map from the System Definition > Tables module or from the context menu of a table.

https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ApplicationScope.html

The correct statement regarding Application Scope is that applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts. Application Scope is a feature that identifies and isolates applications and their related artifacts from other applications. Each scoped application has a unique namespace identifier that consists of a prefix and a scope name. This prevents cross-application name collisions and ensures that only authorized scripts can access or modify data in a scoped application. References: [Product Documentation | ServiceNow], [How To Create a Scoped App in ServiceNow - YouTube]

 The application development plan is a document that outlines the scope, objectives, deliverables, and timeline of a software project1. It should include the following business requirements and processes:

Data input/output: This describes what data is needed for the application to function, how the data is collected, stored, processed, and displayed, and what outputs are generated by the application2.

Business problem: This defines the problem or opportunity that the application aims to address, the current situation, the desired outcome, and the benefits of the solution3.

Process steps: This details the steps involved in the application development lifecycle, such as planning, designing, testing, deploying, and maintaining the application4.

Users/stakeholders: This identifies the people who will use, benefit from, or influence the application, their roles, responsibilities, and expectations, and how they will be involved in the project5.

References = 1: Application Development Lifecycle: Phases, Steps and Process3 2: Tips for Writing Business Requirements Documents2 3: Business Requirements Document Template: 7 Components1 4: Requirements Development Steps4 5: What is Business Process Documentation?: 10 Easy Steps to5

In ServiceNow, when importing data from external sources, the platform utilizes Import Sets to stage the data before transforming it into target tables. The mechanism that defines how data from the Import Set fields map to the fields in an existing ServiceNow table is called a Transform Map.

Transform Map: A Transform Map is a set of field mappings that determine the relationships between fields in an Import Set and fields in an existing ServiceNow table. It allows administrators to define how data should be transformed and inserted into the target table.

servicenow.com

Business Service Management Map: This is not related to data import processes. It pertains to visual representations of business services and their dependencies.

Schema Map Relationship Builder: The Schema Map provides a graphical representation of tables and their relationships within the database schema but does not handle data import mappings.

Data Sources: Data Sources define the origin of the data being imported (e.g., files, JDBC connections) but do not determine the field mappings between Import Sets and target tables.

Enabling “Allow access to this table via web services” allows authenticated users with proper roles to access this table via REST/SOAP APIs.

From Development Handbook 4.0.4, p. 191:

" This setting allows web service access to a table, but still requires that users have appropriate roles and permissions through ACLs. "

Thus, access isn’t automatic — proper access controls still apply.

Roles are used to control access to applications and modules in the application navigator. Each application menu or module has a role field that specifies which role is required to view it. Users who do not have the specified role or a role that contains it will not see the application menu or module. Roles can also be used to control access to other features and capabilities in ServiceNow, such as tables, fields, scripts, and workflows.

References = Enable or disable an application menu or module, Grant a role access to applications and modules, Controlling access to applications and modules.

In ServiceNow, to create a module that directs users to a Record Producer (a simplified form for creating records), you should use the " URL (from Arguments) " Link Type. This configuration allows you to specify a direct link to the Record Producer.

Steps to Configure:

Navigate to Module Creation:

Go to the Application Menu where you want to add the module.

Click on " Edit Application Menu " and then " New Module. "

Set Link Type:

In the module ' s configuration, set the Link Type to " URL (from Arguments). "

Define the URL:

In the Arguments field, provide the URL to the Record Producer. The URL typically follows this pattern:

arduino

CopyEdit

servicenow_instance_url/com.glideapp.servicecatalog_cat_item_view.do?sysparm_id=record_producer_sys_id

Replace servicenow_instance_url with your instance ' s URL and record_producer_sys_id with the sys_id of the Record Producer.

Explanation of Other Options:

HTML (from Arguments): Used to display custom HTML content. Not suitable for linking directly to Record Producers.

Content Page: Used to display predefined content pages within ServiceNow. Not applicable for direct Record Producer links.

Script (from Arguments): Allows execution of a script to determine the module ' s behavior. This is more complex and unnecessary for simply linking to a Record Producer.

To see what scripts, reports, and other application artifacts will be in a published application, the best option is to examine the Application Files Related List in the application to be published. This will show all the application files that belong to the application, grouped by file type and scope. You can also filter, sort, or search the list to find specific files.

The following options are not the best ways to see what application artifacts will be in a published application:

Enter the name of the Application in the Global search field. This will perform a global text search on the instance and return any records that match the application name, which may include irrelevant or incomplete results.

Open the list of Update Sets for the instance. This will show all the update sets that have been created or imported on the instance, but not necessarily the ones that belong to the application to be published. Update sets are used to move customizations between instances, not to publish applications to the ServiceNow Store or Share.

Open the artifact records individually to verify the value in the Application field. This will require opening each record that may be part of the application and checking the Application field, which is tedious and error-prone. References: Publish an Application, Application Files

ServiceNow provides several methods for developers to publish and share applications once they are ready for distribution. The supported methods include:

Publish to an application repository: This method allows developers to publish their applications to a centralized repository, enabling easy distribution and installation across multiple ServiceNow instances. The application repository serves as a hub where applications can be stored and accessed by other instances.

snowunderground.com

Publish to the ServiceNow Store: Developers can submit their applications to the ServiceNow Store, a marketplace where applications are reviewed, certified, and made available to all ServiceNow customers. Publishing to the Store involves a certification process to ensure the application meets ServiceNow ' s standards.

support.servicenow.com

Publish to an update set: An update set is a container for capturing configuration changes in ServiceNow. Developers can publish applications to an update set, which can then be moved between instances, allowing for the transfer of application configurations and customizations.

servicenow.com

Options A (Publish to a spreadsheet), D (Publish to a local USB device), and F (Publish to a local drive) are not supported methods for publishing applications in ServiceNow. These options do not align with the platform ' s mechanisms for application distribution and deployment.

Access Control scripts are server-side scripts that run when an Access Control rule is evaluated. They can use the gs and current objects to access the GlideSystem and GlideRecord methods, respectively. Some of the useful methods in Access Control scripts are:

gs.hasRole() - This method checks if the current user has a specified role. It returns true if the user has the role, and false otherwise. For example, gs.hasRole(‘admin’) will return true if the user is an administrator, and false otherwise.

current.isNewRecord() - This method checks if the current record is a new record that has not been inserted into the database yet. It returns true if the record is new, and false otherwise. For example, current.isNewRecord() will return true if the record is being created, and false if the record is being updated or deleted.

The methods g_user.hasRole() and current.isNew() are not part of the server-side scripting API. They are part of the client-side scripting API, which is used in Client Scripts and UI Policies. They cannot be used in Access Control scripts.

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.

ServiceNow Developer Documentation on GlideSystem (gs)​.

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

Application scope is a foundational concept in ServiceNow application development. ServiceNow documentation describes application scoping as a protection mechanism that identifies and restricts access to an application’s files and data. In practice, scope defines an isolation boundary around an application’s artifacts, such as tables, scripts, UI components, and other resources. This boundary helps prevent unintended interference between applications and reduces the risk of naming collisions or cross-application impacts. The scope model also works together with Application Access settings, which allow administrators to specify what parts of an application are accessible to other applications. By default, scoped applications are designed to keep resources private unless explicitly shared through access settings or cross-scope privileges. Because of this, the primary purpose of scope is not backups or UI design control, and it is explicitly not meant to enable unrestricted updates across applications. Instead, scope exists to define and enforce boundaries so that an application’s resources remain isolated and protected unless intentionally exposed.

Application Access settings on a table control which operations external applications (in other scopes) can perform. The main controllable operations are:

Can create

Can read (query)

Can update

Can delete

From Development Handbook 4.0.4, p. 192:

“Application access settings determine whether another scope can read, write, create, or delete records from this table... Execute is not a valid database operation — it pertains to script includes or other executable logic.”

The ServiceNow REST API is a web service that allows you to interact with the ServiceNow platform using HTTP requests and responses. The ServiceNow REST API supports the following methods:

POST: This method allows you to create a new record or execute an action on the ServiceNow platform. For example, you can use the POST method to create an incident or run a script.

GET: This method allows you to retrieve information from the ServiceNow platform. For example, you can use the GET method to get the details of a user or a table.

DELETE: This method allows you to delete a record or a resource from the ServiceNow platform. For example, you can use the DELETE method to delete an attachment or a workflow context.

PUT: This method allows you to update a record or a resource on the ServiceNow platform. For example, you can use the PUT method to update the state of a task or the value of a system property.

PATCH: This method allows you to update a record or a resource on the ServiceNow platform by sending only the changes. For example, you can use the PATCH method to update the short description of an incident or the order of a module.

The method COPY is not part of the ServiceNow REST API. There is no COPY method in the HTTP protocol. To copy a record or a resource on the ServiceNow platform, you need to use the POST method with the clone action.

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.

" A table that extends another table is called a child class, and the table it extends is the parent class " - this is about halfway down in this link below: https://docs.servicenow.com/en-US/bundle/tokyo-platform-administration/page/administer/table-administration/concept/table-extension-and-classes.html

In ServiceNow, GlideForm is the client-side API used to interact with and manipulate a record form, including reading and writing field values, controlling visibility/mandatory/read-only behavior, and displaying messages to the user. The platform exposes GlideForm methods through a single global client-side object named g_form. ServiceNow documentation explicitly states that there is no constructor for the GlideForm class and that developers access GlideForm methods using the g_form global object available in client-side contexts such as Client Scripts and UI Policies. This makes g_form the correct and standard way to call GlideForm functions (for example, g_form.getValue(), g_form.setValue(), g_form.setDisplay(), etc.). The other options listed are not the documented GlideForm global object for standard client scripting in ServiceNow.

" Add instructional text and other design elements to your forms by using form annotations in Form Builder. " https://docs.servicenow.com/bundle/sandiego-application-development/page/administer/form-builder/task/create-form-annotations.html

The method call that returns true only if the currently logged in user has the catalog_admin role and in no other case is g_user.hasRoleExactly(‘catalog_admin’). This method checks if the user has exactly one role, and returns true if it matches the argument. The other methods return true if the user has one or more roles, or if the user has any role from a list of arguments. References: [ServiceNow Docs - GlideUser API], [ServiceNow Community - Difference between hasRole() and hasRoleExactly()]

 It is best practice to define the business requirements and the process(es) an application will manage as part of the application development plan. The following are some of the considerations to document as part of the business process:

Business problem. This is the description of the problem or opportunity that the application is intended to address or exploit. It should include the background, context, scope, and objectives of the problem or opportunity.

Data input/output. This is the specification of the data that the application will need to collect, store, manipulate, and display. It should include the data sources, formats, validations, transformations, and integrations of the data.

Users/stakeholders. This is the identification of the users and stakeholders who will be involved in or affected by the application. It should include the roles, responsibilities, expectations, and needs of the users and stakeholders.

Process steps. This is the definition of the steps and activities that the application will perform or support. It should include the inputs, outputs, triggers, conditions, and outcomes of each step or activity.

The following are not some of the considerations to document as part of the business process:

Project schedule. This is the estimation of the time and resources required to complete the application development project. It should include the milestones, deliverables, dependencies, and risks of the project. This is not part of the business process, but part of the project management plan.

Database capacity. This is the measurement of the amount of data that the application will generate and store in the database. It should include the data volume, growth rate, retention policy, and backup strategy of the data. This is not part of the business process, but part of the technical design and architecture of the application.

Available licenses. This is the number and type of licenses that the application will consume or require from the ServiceNow platform. It should include the license model, cost, and allocation of the licenses. This is not part of the business process, but part of the financial and legal aspects of the application. References: Application Development Process, Business Process Analysis

When creating a table in a privately-scoped application, four Access Controls are automatically created for the table. These Access Controls define the permissions for the four basic operations on the table: Create, Delete, Read, and Write. The Create operation allows the user to create new records on the table. The Delete operation allows the user to delete existing records on the table. The Read operation allows the user to view the records on the table. The Write operation allows the user to modify the records on the table. By default, these Access Controls grant access to the admin role and the application scope. You can modify or delete these Access Controls as needed.

The other options are not valid Access Controls for a table. Insert, Query, and Update are not operations, but methods of the GlideRecord class that are used to manipulate records on the server-side. They are not part of the Access Control rules.

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

In ServiceNow, a Record Producer allows users to create records in a specific table through the Service Catalog. After a user submits a Record Producer, developers may want to redirect the user to a specific page. This can be achieved by setting the producer.redirect property within the Script field of the Record Producer.

For example:

javascript

CopyEdit

producer.redirect = ' incident.do?sys_id= ' + current.sys_id;

This script redirects the user to the newly created incident record after submission.

Option A is incorrect because configuring the module that opens the Record Producer does not control the post-submission behavior.

Option C is unnecessary for simple redirection purposes; creating an application property to store the URL adds unnecessary complexity.

Option D is incorrect because using window.redirect in a Business Rule is not appropriate; Business Rules run on the server side and do not have access to the client-side

Scheduled Script Executions (formerly known as Scheduled Jobs) are used to run server-side logic at specific intervals, such as querying or updating records automatically. Option B describes a valid server-side scheduled use case.

From ServiceNow Docs (https://developer.servicenow.com/):

“Scheduled Script Executions allow you to define JavaScript logic that runs on a schedule to automate tasks such as checking data integrity, generating reports, or reassigning records.”

Client-side logic like in options A, C, and D must use Client Scripts or UI Policies, not Scheduled Jobs.

Flow Designer variables can store record data and complex data using the following data types:

Integer: A whole number that can be used in mathematical operations.

Array: A collection of items that can be accessed by their index or iterated over using a For each action.

String: Any kind of text, such as email addresses or the text contents of a file.

Define and Use Data Types in a Flow (Flow Designer)

Variable data types - Power Automate | Microsoft Learn

Product Documentation | ServiceNow

The steps to import new data into ServiceNow from a spreadsheet are: Load Data, Create Transform Map, Run Transform. Load Data is the process of uploading the spreadsheet file and creating an Import Set table that contains the data to be imported. Create Transform Map is the process of defining how the fields from the Import Set table map to the fields of the target table in ServiceNow. Run Transform is the process of executing the Transform Map and copying the data from the Import Set table to the target table. Reference: Import sets, Transform maps

In ServiceNow, when a new field is added to an existing table, it is not automatically included in any existing List views. List views are predefined configurations that determine which fields are displayed when viewing records in a list format. To display the new field in a List view, you must manually modify the List layout to include the field.

Steps to Add a New Field to a List View:

Navigate to the List Layout Configuration:

Go to the table ' s list view.

Right-click on the header row (where the column titles are displayed).

Select " Configure " and then " List Layout. "

Add the New Field:

In the List Layout configuration, you ' ll see two columns: " Available " and " Selected. "

Locate your new field in the " Available " column.

Use the arrow buttons to move the new field to the " Selected " column, placing it in the desired order.

Save the Configuration:

Click " Save " or " OK " to apply the changes.

The new field will now appear in the List view as configured.

The fastest way to create and configure a Record Producer is to open the table in the Table records and select the Add to Service Catalog Related Link. This will automatically create a Record Producer with the same fields as the table and add it to the Service Catalog. You can then modify the Record Producer as needed. The other options require more steps and manual configuration. Reference: Create a record producer

This class allows you to create and manipulate dialog windows on the user interface. You can use this class to display messages, forms, or custom HTML content in a modal window.

GuideAjex: This class allows you to make asynchronous calls to the server and process the response. You can use this class to retrieve data, execute scripts, or perform actions on the server without reloading the page.

GuideForm: This class allows you to access and manipulate the fields and values on a form. You can use this class to get or set field values, show or hide fields, add or remove options, or validate field inputs.

The class GuideRecord is not part of the Client side scoped APIs. GuideRecord is part of the Server side scoped APIs, which are a set of classes and methods that allow you to interact with the database and perform server-side logic on the ServiceNow platform. GuideRecord is a class that represents a record in a table and allows you to query, insert, update, or delete records on the server.

In ServiceNow, a workflow context refers to a specific instance of a workflow execution. When a workflow is initiated—whether by inserting or updating a record, triggering an event, or through scripts—the system creates a workflow context. This context is derived from a particular version of the workflow and is responsible for executing the defined activities and following the specified transitions within that workflow.

Key points about workflow context:

Instance of Execution: Each time a workflow runs, a new context is created to manage that specific execution instance. This allows multiple instances of the same workflow to operate independently and simultaneously.

Execution of Activities: The context manages the progression through the workflow ' s activities, ensuring that each step is executed in the defined order and under the specified conditions.

Tracking and Management: Workflow contexts enable administrators to monitor the state and progress of workflow executions. They provide visibility into which activities have been completed, which are pending, and any transitions that have occurred.

For example, if a workflow is designed to handle approval processes, each time an approval is initiated, a new workflow context is created to manage that particular approval instance. This context will track the approval ' s progress, manage notifications, and handle any branching logic defined in the workflow.

Access Controls are rules that define who can access what data and how they can access it. When configuring an Access Control, you can specify the table, operation, and role for the rule. You can also add a condition or a script to further refine the rule. If you do not add a condition or a script, the rule will apply to all records and fields on the table.

The statements A, B, and C are true for Access Controls that have no condition or script. For example:

table.* will grant access to every field in a record. This means that the user can view and edit all the fields on the record, regardless of their role or any other criteria.

table.None will grant access to every record on the table. This means that the user can view and edit all the records on the table, regardless of their role or any other criteria.

table.field will grant access to a specific field in a record. This means that the user can view and edit only that field on the record, regardless of their role or any other criteria.

The statement D is not true for Access Controls that have no condition or script. table.id will not grant access to a specific record on the table. This is because the id is not a field name, but a unique identifier for the record. To grant access to a specific record on the table, you need to add a condition or a script that matches the id of the record.

In ServiceNow, when an event is generated using the gs.eventQueue() method, the system can respond in several ways:

B. Email Notification: Events can trigger email notifications. By associating an event with a notification, the system can send emails to specified recipients when the event occurs.

E. Script Action: Script Actions are server-side scripts that execute in response to events. They allow developers to define custom behaviors that should occur when specific events are fired.

The other options are not appropriate responses to events generated by gs.eventQueue():

A. UI Policy: UI Policies are used to dynamically change the behavior of fields on forms in the user interface and are not triggered by events.

C. Client Script: Client Scripts run on the client side (in the user ' s browser) and are not directly triggered by server-side events.

D. Scheduled Script Execution (Scheduled Job): Scheduled Jobs are scripts that run at specified times or intervals and are not triggered by events.

For more detailed information, refer to the official ServiceNow documentation on Responding to Events.

In ServiceNow, the gs object provides a range of methods for logging messages on the server side. However, the availability of these methods can vary depending on whether the application is global or scoped.

gs.info(): This method is available in scoped applications and is used to log informational messages to the system log. It provides a way to record general information during script execution.

Options A (gs.log()), B (gs.print()), and D (gs.debugLog()) are not available in scoped applications. These methods are either restricted to global applications or do not exist in the ServiceNow API.

For more detailed information, refer to the official ServiceNow documentation on server-side scripting:

Inbound email matching uses Watermarks and Subject lines (with record numbers like INC0010001) to associate emails with existing records.

From Email Handling Docs:

“ServiceNow uses Watermark IDs and subject lines containing record numbers to find the corresponding task or record when processing inbound email.”

Checkbox tooltip: " Show this module when the user has the specified roles. Otherwise the user must have the roles specified by both the application menu and the module. "

The following is true for the Override application menu roles configuration option when configuring a module:

Users with the module role but without access to the application menu access the module. This is true because the Override application menu roles option allows users to bypass the application menu role requirement and access the module directly if they have the module role. For example, if a module has the itil role and the Override application menu roles option enabled, and the application menu has the admin role, then a user who has the itil role but not the admin role can still access the module.

The following are not true for the Override application menu roles configuration option when configuring a module:

Self-Service users can access the module even though they do not have roles. This is false because the Override application menu roles option does not grant access to the module to users who do not have any roles. Self-Service users are users who do not have any roles assigned to them and can only access the Self-Service portal and the Knowledge Base. To access the module, users need to have at least the module role.

Admin is given access to the module even if Access Controls would ordinarily prevent access. This is false because the Override application menu roles option does not override the Access Control (ACL) rules that apply to the module. Access Control rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions. Admin is a role

Catalog Client Scripts and Catalog UI Policies are the client-side scripts that apply to Record Producers. Catalog Client Scripts allow you to add or modify functionality on a catalog item or record producer form. Catalog UI Policies dynamically change information on a catalog item or record producer form. UI Scripts, UI Actions, Client Scripts, and UI Policies do not apply to Record Producers. Reference: Catalog client scripts, Catalog UI policies

https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/glideSystemScoped/concept/c_GlideSystemScopedAPI.html

When a ServiceNow instance requests information from a web service, ServiceNow is the web service consumer. A web service consumer is an application that sends requests to a web service provider and receives responses from it. A web service provider is an application that exposes its functionality as web services. A web service publisher is a person or organization that publishes web services for others to use. A web service specialist is a person who has expertise in developing or using web services. Reference: Web services

When creating a table, the Create module field allows you to automatically create a module for the table in the application menu. The default behavior of the new module is to display a list of all records from the table. This can be changed later by editing the module properties and specifying a different link type, such as form, URL, or script.

When designing and creating a form, you can create sections to organize fields on a form. Sections are containers that group related fields together and provide a label and a description for the group. You can use sections to improve the readability and usability of the form. You can also collapse or expand sections to show or hide the fields within them.

The other options are not valid ways to organize fields on a form. Related lists are not fields, but lists of records that are related to the current record on the form. Tabs are not part of the form, but part of the application menu that allows you to navigate between different modules. Buttons are not fields, but elements that perform actions on the form, such as saving, updating, or deleting the record.

In ServiceNow, Business Rules are server-side scripts that execute whenever a record is inserted, updated, deleted, or queried. However, certain actions can be configured without writing any script, using the Business Rule ' s user interface options.

The primary actions that can be configured without scripting are:

Set field values: This allows administrators to specify new values for fields when the Business Rule conditions are met. This is configured in the " Actions " tab of the Business Rule form, where specific fields and their desired values can be set without any scripting.

Add message: Administrators can configure a message to be displayed to the user when the Business Rule executes. This is done by selecting the " Add message " checkbox and providing the desired message text.

Options C (Set field values and write to the system log) and D (Set field values and generate an event) would require scripting. Writing to the system log involves using server-side APIs like gs.log(), and generating an event requires calling event generation methods—both necessitate scripting.

For more detailed information, refer to the official ServiceNow documentation on Business Rules:

servicenow.com

The Customer Update [sys_update_xml] table stores the individual customization records that make up an update set. The Update Set [sys_update_set] table represents the update set container itself, but the actual tracked configuration changes are represented as customer update records. This distinction is important in CAD because update sets are used to group and migrate configuration changes, not ordinary transactional data. For example, changes to business rules, forms, fields, UI actions, and other configuration records can create Customer Update records. System Properties and Application Registry records serve different purposes and are not the table that stores update set customization details. Therefore, D is the correct answer.

================

An example of when an application might not use a Scheduled Script Execution (Scheduled Job) is when the application needs to run a client-side script at the same time every day. A Scheduled Script Execution is a server-side script that runs on a specified schedule and performs some action on the server or database. A client-side script runs on the user’s browser and cannot be scheduled by ServiceNow. The other options are examples of when an application might use a Scheduled Script Execution, such as sending email reminders, running a clean up script, or querying the database for unassigned records. Reference: Scheduled Script Execution, Client scripts

 When configuring a REST Message, the Endpoint is:

The URI of the data to be accessed, queried, or modified. This is the correct answer because the Endpoint is the part of the REST Message that specifies the location and the resource of the REST provider. The Endpoint is composed of the base URL and the resource path, which can include query parameters or variables. For example, the Endpoint for a REST Message that retrieves the weather information for a city from a web service could be https://api.openweathermap.org/data/2.5/weather?q=London.

The following are not correct definitions of the Endpoint when configuring a REST Message:

The commands to the REST script to stop execution. This is not correct because the commands to the REST script to stop execution are not part of the REST Message, but of the Scripted REST API, which is a feature that allows users to create custom REST endpoints on the ServiceNow platform. The commands to the REST script to stop execution are methods of the RESTAPIResponse object, such as setStatusCode, setError, or complete.

Information about the format of the returned data. This is not correct because the information about the format of the returned data is not part of the Endpoint, but of the HTTP headers or the Accept field of the REST Message. The HTTP headers or the Accept field can be used to specify the content type of the response, such as JSON, XML, or HTML.

The response from the provider indicating there is no data to send back. This is not correct because the response from the provider indicating there is no data to send back is not part of the Endpoint, but of the HTTP status code or the response body of the REST Message. The HTTP status code or the response body can be used to indicate the result of the REST request, such as 200 OK, 404 Not Found, or 500 Internal Server Error. References: REST Messages, Scripted REST APIs

The Event Registry is a table that stores the definitions of all the Events that can be triggered or processed by the ServiceNow system1. The Event Registry allows ServiceNow to react when Events are generated by executing actions such as sending notifications, running scripts, or starting workflows2. The Event Registry also provides information about the Event parameters, description, and source3.

References = 1: Event Registry - ServiceNow Docs 2: Event Management - ServiceNow Docs 3: Event Registry form - ServiceNow Docs

Business Rules run server-side, so the correct APIs come from the GlideSystem object (gs) rather than client-side objects like g_form. In server-side scripting, the platform provides a standard way to retrieve the currently logged-in user’s identity. The method gs.getUserID() returns the sys_id of the user associated with the current session. This is commonly used in Business Rules for auditing logic, conditional processing, field stamping (for example, setting a custom “last processed by” field), or enforcing business rules based on user identity. The g_form object is a client-side API available in Client Scripts and UI Policies, so any option using g_form is invalid in a Business Rule context. Likewise, gs.getUserSysID() is not the documented method name for this purpose. Using the correct server-side API ensures the script executes reliably regardless of UI context (classic UI, workspace, mobile), because it relies on the session and not on the form rendering layer.

https://developer.servicenow.com/dev.do#!/learn/courses/tokyo/app_store_learnv2_flowdesigner_tokyo_flow_designer/app_store_learnv2_flowdesigner_tokyo_notifications_in_flow_designer/app_store_learnv2_flowdesigner_tokyo_inbound_email_and_flows

" By default, the system generates a watermark label at the bottom of each notification email to allow matching incoming email to existing records. " https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/concept/c_WorkingWithWatermarks.html

" If there are no spreadsheets or existing tables to use for your application, you can create and customize a new table. " see this quote in link below:

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/app-engine-studio/task/create-table.html

Also see:

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/task/gac-create-table-from-scratch.html

Also, no search results if search on " Now Experience Table Creator " .

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. References: [ServiceNow Docs - Stash local changes], [ServiceNow Docs - Source control]

To allow a module to open a form for new record insertion, the Link type should be set to “Create new record” or similar.

From Platform App Design Docs:

“Modules control navigation behavior via the Link type setting. To insert records, use the ' Create record ' or ' New record ' link type.”

In ServiceNow, UI Actions are elements that make the user interface more interactive and tailored to user activities. They can appear as buttons, links, or context menu items on forms and lists. The valid types of UI Actions include:

C. Form choice: These are UI Actions that appear as choices in form context menus, allowing users to perform specific actions related to the form.

D. Form button: These are buttons that appear on forms, enabling users to execute defined actions directly from the form view.

E. List banner button: These are buttons that appear in the list view ' s banner, providing actions that can be performed on the list or selected records.

The other options are not standard UI Action types:

A. Workflow action: While workflows can include actions, " Workflow action " is not a defined UI Action type in ServiceNow.

B. Record navigation button: This is not a standard term used for UI Action types in ServiceNow.

Inherited fields in ServiceNow are fields that are part of a parent table and automatically become part of child tables through inheritance. This structure is foundational in the ServiceNow data model, ensuring that child tables maintain a consistent relationship with their parent tables.

Here’s why inherited fields cannot be deleted from a child table:

System Design:ServiceNow employs a table inheritance model where child tables derive fields and properties from parent tables. Deleting inherited fields from a child table would break the integrity of the data model, as those fields are shared across multiple tables.

Impact on Functionality:Many inherited fields, such as sys_created_on or sys_updated_by, are integral to the functionality of the platform. Removing them could disrupt workflows, reporting, and auditing capabilities.

Alternative Approach:If you want to hide or restrict access to inherited fields in a child table, you can use ACLs (Access Control Lists) to prevent users from viewing or modifying these fields. Another option is to use UI Policies or Client Scripts to control their visibility on forms.

Developer Note:Attempting to delete inherited fields violates ServiceNow’s core principles of maintaining a robust and unified data structure. The platform enforces these rules to ensure consistent behavior across all tables in the hierarchy.

ServiceNow Developer Documentation on Table Inheritance​.

Best practices outlined on SN Pro Tips regarding scoped application development and table structures​.

Create table from template is not an option for creating a table through the Guided Application Creator. The other options are available for creating a table in the app. Upload spreadsheet allows you to import data from an Excel file and create a table based on the spreadsheet columns and rows. Extend a table allows you to create a child table that inherits fields and behaviors from a parent table. Create table from scratch allows you to define your own fields and data types for a new table. Reference: Create tables

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

A Display Business Rule has access to the current, g_scratchpad, and GlideSystem objects, but not the previous object. The previous object is only available to Before Business Rules4. References: Business Rule API

https://docs.servicenow.com/bundle/tokyo-application-development/page/script/business-rules/concept/c_BusinessRules.html

https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/servicenow_administrator/app_store_learnv2_automatingapps_quebec_scheduled_script_execution_scripts

The objects that you can use in a Scheduled Script Execution (Scheduled Job) script are GlideSystem and GlideRecord. GlideSystem provides methods for performing system operations, such as logging, running background scripts, or getting system information. GlideRecord provides methods for working with records in the database, such as querying, updating, inserting, or deleting records. The current object is not available in Scheduled Script Execution scripts, as it refers to the current record on a form or list. The GlideUser object is also not available, as it refers to the current user session. Reference: Scheduled Script Execution, GlideSystem, GlideRecord

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

https://developer.servicenow.com/dev.do#!/learn/learning-plans/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. References: Email Notification Weight

A transform map determines the relationships between fields displaying in an Import Set table and fields in an existing ServiceNow table, such as the Incidents or Users table.

ServiceNow Studio code search uses the default code search group to determine which application file types are searchable. To expand the supported file types, an administrator can create a new code search group that includes additional file types. This is cleaner than modifying a default table or changing unrelated metadata synchronization settings. The important CAD concept is that code search is metadata-driven and applies to searchable application file types, generally those extending sys_metadata. Creating a new code search group keeps the configuration controlled and avoids changing baseline behavior unnecessarily. Therefore, option A is the best answer for expanding supported Studio code search file types.

================

In ServiceNow, when importing data from external sources, the data is first loaded into an Import Set table, which acts as a staging area. To move this data into an existing ServiceNow table (known as the target table), a Transform Map is used. A Transform Map is a set of field mappings that define the relationships between fields in the Import Set table and fields in the target table. This mapping ensures that data is accurately transformed and transferred to the correct fields in the target table during the import process. Therefore, the correct answer is C. Transform Map.

The other options are not related to this specific function:

A. Business Service Management Map: This is not a standard term used in the context of data import and transformation in ServiceNow.

B. Data Sources: These define the origin of the data being imported but do not handle the field mapping between Import Set tables and target tables.

D. Schema Map Relationship Builder: This tool visualizes the relationships between tables in the database schema but is not used for mapping fields during data transformation.

For more detailed information, refer to the official ServiceNow documentation on Transform Maps.

ServiceNow is optimized for building applications that manage structured data in tables and provide consistent user experiences through lists and forms. A core reason to develop on the platform is when the solution naturally fits the record-based model: users create, review, and update records through forms, and those records drive reporting, auditing, and process automation. That makes option C a direct match to how ServiceNow applications are designed and delivered. Another primary platform strength is workflow automation, including Flow Designer, approvals, task orchestration, notifications, and integration actions that coordinate work across teams and systems. If the solution requires repeatable, governed process automation, option D aligns with the platform’s purpose and capabilities. In contrast, “multimedia features” is not a platform driver for application development; while media can be displayed, it is not the typical reason to choose ServiceNow. Similarly, requiring low-level programming libraries is generally a mismatch, since ServiceNow development focuses on platform APIs and configuration patterns rather than direct access to low-level system libraries.

In ServiceNow, to include data from another table within a form, the Reference field type is utilized. A Reference field creates a relationship between the current table and another table by storing a reference to a record in the target table. This allows users to select a record from the referenced table and display related information seamlessly within the form.

A. Use the Date field type: This is incorrect. The Date field type is designed to store date values and does not facilitate referencing records from other tables.

B. Use the Phone Number field type: This is incorrect. The Phone Number field type is intended for storing phone number data and does not support referencing other table records.

C. Use the String field type: This is incorrect. The String field type stores text data and does not inherently provide functionality to reference records from other tables.

D. Use the Reference field type: This is correct. The Reference field type is specifically designed to create a link to a record in another table, enabling the incorporation of related data into the form.

For example, in the Incident table, the " Caller " field is a reference to the User [sys_user] table, allowing the selection of a user as the caller for the incident. This setup ensures data consistency and leverages existing records without data duplication.

For more detailed information, refer to the official ServiceNow documentation on Reference Fields.

In ServiceNow, tables can extend other tables, inheriting all fields and functionalities from the parent table. These inherited fields are integral to the structure and behavior of the child table.

A. No, inherited fields cannot be deleted from a child table: This is correct. Inherited fields are part of the child table ' s schema due to its extension of the parent table. Removing these fields would disrupt the inherent structure and relationships defined by the table hierarchy.

B. Yes, but only if they are text fields: This is incorrect. The data type of the field does not permit the deletion of inherited fields.

C. Yes, select the red X in the left-most column in the table definition: This is incorrect. Inherited fields do not have a delete (red X) option in the table definition, as they are not directly created on the child table.

D. Yes, but only if there has never been any saved field data: This is incorrect. The presence or absence of data does not affect the ability to delete inherited fields.

To modify the structure of inherited fields, consider the following approaches:

Field Visibility: Use client scripts or UI policies to hide the inherited fields on forms where they are not needed. This approach maintains data integrity while tailoring the user interface to specific requirements.

Form Layout Configuration: Adjust the form layout to remove inherited fields from specific views, ensuring they are not displayed to users in contexts where they are irrelevant.

These methods allow customization of the user experience without altering the underlying table schema or violating the inheritance principles established in the data model.

Business Rule is server-side, so it uses GlideSystem API. gs.hasRoleExactly doesn ' t exist

In a Business Rule, the following returns true if the currently logged in user has the admin role:

gs.hasRole(‘admin’). This is the correct answer because gs is the GlideSystem object, which provides methods for performing system operations, and hasRole is a method that checks if the current user has the specified role. For example, gs.hasRole(‘admin’) will return true if the current user has the admin role, and false otherwise.

The following do not return true if the currently logged in user has the admin role in a Business Rule:

g_form.hasRoleExactly(‘admin’). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRoleExactly is a method that checks if the current user has exactly the specified role and no other roles. For example, g_form.hasRoleExactly(‘admin’) will return true if the current user has only the admin role, and false if the current user has the admin role and any other role.

g_form.hasRole(‘admin’). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRole is a method that checks if the current user has the specified role or any role that contains the specified role. For example, g_form.hasRole(‘admin’) will return true if the current user has the admin role or any role that contains the admin role, such as admin_ui or admin_script.

gs.hasRoleExactly(‘admin’). This is not correct because gs is the GlideSystem object, which provides methods for performing system operations, and hasRoleExactly is not a valid method of the gs object. There is no method that checks if the current user has exactly the specified role and no other roles in the gs object. References: Business Rules, GlideSystem, GlideForm

Created UI policy on incident form, action set ' s cmdb_ci field as mandatory and script as not. result, field was not mandatory.

A UI Policy’s Actions execute before the UI Policy’s Scripts. Actions are predefined operations that can be applied to fields or sections, such as making them mandatory, read-only, visible, or setting a default value. Scripts are custom JavaScript code that can be used to perform more complex logic or validations. Actions are executed first, and then Scripts are executed if the UI Policy conditions are met. References: [ServiceNow Docs - UI policy actions], [ServiceNow Docs - UI policy scripts]