Free Practice Questions for ServiceNow CAD Exam

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

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_SelectAnAppFromTheAppPicker.html

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.

g_scratchpad is a server-to-client data transfer object used primarily in the classic web UI rendering pipeline. A common, documented pattern is to populate g_scratchpad in a Display Business Rule (server-side) and then read those values in client-side scripts (such as Client Scripts or UI Scripts) while the form is being rendered in the browser. This avoids extra server calls when you need a small set of precomputed values or flags, such as whether the current user meets a condition, whether a related record exists, or which UI behavior should be enabled. It is not used to “populate properties for a Display Business Rule” as an end in itself; rather, the Display Business Rule is the place where developers often set g_scratchpad. It is also not a concept for defining constructors/destructors for table classes. While similar patterns can exist across experiences, g_scratchpad is specifically recognized as a web client bridging mechanism tied to server-side display processing, which matches option B.

An Access Control list (ACL) defines what data users can access and how they can access it in ServiceNow tables1. The ACL evaluates the user roles and the conditions defined in the ACL rules to determine the user’s access level2. In this case, the ACL rules for the table are as follows:

table.None read Access Control for users with the admin and itil roles: This means that users with the admin or itil roles cannot read any field in the table unless there is a more specific rule that grants them access3.

table. * read Access Control for users with the admin role: This means that users with the admin role can read all fields in the table.

table. field3 read Access Control for users with the itil role: This means that users with the itil role can read only the field3 in the table.

Therefore, a user with the itil role can read only the field3 in the table, and not the other fields.

References = 1: Access Control Lists - ServiceNow Docs 2: How ACL Rules Are Evaluated - ServiceNow Docs 3: Access Control List Rules - ServiceNow Docs : Wildcard in ACL Rules - ServiceNow Docs : Field-Level ACL Rules - ServiceNow Docs

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.

Debugging client-side scripts in ServiceNow involves utilizing tools and methods that operate within the user ' s browser environment, as client-side scripts execute there.

A. gs.addErrorMessage(): This function is used in server-side scripts to add error messages to the session and is not applicable for client-side debugging.

B. g_form.addInfoMessage(): This client-side function displays informational messages to the user on the form. While primarily used for user communication, it can aid in debugging by confirming the execution of certain script sections.

C. jslog(): This function logs messages to the JavaScript log, which can be viewed using browser developer tools. It ' s a valuable tool for debugging client-side scripts by providing runtime information.

servicenow.com

D. gs.log(): This function logs messages on the server side and is not available in client-side scripting.

Additionally, developers can use the debugger; statement within their client-side scripts. When the browser ' s developer tools are open, encountering this statement will pause script execution, allowing for step-by-step inspection.

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