CAD Exam Dumps - ServiceNow Certified Application Developer Questions and Answers

User-defined non-inherited fields can be deleted from a table in ServiceNow. These are fields that are created by users on a specific table and are not inherited from a parent table. Inherited fields cannot be deleted from a table, as they are defined on a parent table and shared by all child tables. Any field on a table cannot be deleted, as some fields are system-defined and essential for the table functionality. Table records are not deleted when a field is deleted, as the field deletion only affects the table structure and not the data. Reference: Delete fields

gs.print() and gs.log() are older and not available in scoped applications, whereas gs.debug(), gs.info(), gs.warn(), gs.error() work in both scoped applications and global are therefore are more versatile going forward in future versions.

The following is true for GlideUser (g_user) methods:

Can be used in Client Scripts, UI Policies, and UI Actions. This is true because GlideUser (g_user) methods are part of the client-side scripting APIs that provide information about the current user and the user’s preferences. Client Scripts, UI Policies, and UI Actions are all types of client-side scripts that run in the web browser and manipulate the user interface.

The following are not true for GlideUser (g_user) methods:

Can be used in Client Scripts and UI Policies only. This is false because GlideUser (g_user) methods can also be used in UI Actions, which are another type of client-side scripts that can be triggered by a user’s click on a button, link, or choice.

Can be used in Business Rules only. This is false because GlideUser (g_user) methods cannot be used in Business Rules, which are server-side scripts that run on the ServiceNow platform and manipulate the database. Business Rules use a different API to access the current user information, which is GlideSystem (gs).

Can be used in Business Rules, and Scripts Includes. This is false because GlideUser (g_user) methods cannot be used in Business Rules or Script Includes, which are both server-side scripts. Script Includes are reusable units of code that can be called from any server-side script. Script Includes also use GlideSystem (gs) to access the current user information. References: Client-Side Scripting APIs, GlideUser, Business Rules, Script Includes

In ServiceNow, Modules are navigation elements that provide access to various parts of the platform, such as forms, lists, reports, or other application components. They are organized within Application Menus to create a structured and intuitive navigation hierarchy.

Key characteristics of Modules:

Part of Application Menus: Every module is contained within an application menu. This organization helps users navigate to different areas of the platform efficiently. For instance, the "Incident" application menu may contain modules like "Create New" or "All Incidents."

Functionality: Modules can open various elements, including forms, lists, reports, or URLs. This flexibility allows modules to direct users to specific records, filtered lists, or external resources.

Association with Tables: While many modules are associated with specific tables (e.g., a module that displays a list of incidents is associated with the "Incident" table), it's not a strict requirement. Some modules may link to external URLs or perform actions not directly tied to a table.

Access Control: Access to modules is controlled through roles. Administrators can define which user roles have visibility and access to specific modules, ensuring that users only see modules relevant to their responsibilities.

For example, a module named "Active Incidents" under the "Incident" application menu might display a list of all active incident records. Access to this module can be restricted to users with the "itil" role, ensuring that only authorized personnel can view active incidents.

The application name is not required to link a ServiceNow application to a Git repository. You only need to provide the URL, user name, and password of the Git repository, as well as the branch name and the authentication type. The application name is automatically generated based on the scope name of your application. Reference: [Link an application to a Git repository]

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.