CAD Exam Dumps - ServiceNow Certified Application Developer Questions and Answers

In ServiceNow, the admin role includes all other roles implicitly. So if a user has admin, g_user.hasRole('any_role') returns true.

From ServiceNow Docs – g_user API:

“The hasRole() method returns true if the user has the specified role or is an admin.”

g_user is a global object available only in the client-side environment (Client Scripts, UI Policies, UI Actions).

From Development Handbook 4.0.4, p. 204:

“g_user is only available client-side. It returns session-specific info like roles and user ID. Not usable in Business Rules or Script Includes.”

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

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.

https://developer.servicenow.com/dev.do#!/learn/learning-plans/tokyo/new_to_servicenow/app_store_learnv2_automatingapps_tokyo_use_application_properties

A possible reason to build a custom app is to fulfill a specific use case on internal processes. For example, you may want to digitize a manual process that is not covered by an existing ServiceNow solution, such as managing inventory, tracking expenses, or scheduling events. Building a custom app on the Now Platform can help you automate workflows, improve data quality, and provide better user experiences. The other options are not valid reasons to build a custom app. To avoid using a code repository like GitHub or GitLab is not a reason to build a custom app, as you can still use source control integration with your custom app development. To create a custom integration for a 3rd party system is not a reason to build a custom app, as you can use integration tools such as IntegrationHub or REST APIs to connect with external systems without creating an app. To replace ServiceNow base tables is not a reason to build a custom app, as it is not recommended to modify or delete base tables that are essential for ServiceNow functionality. Reference: Build Custom Apps in ServiceNow – eBook

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.

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.

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