ServiceNow CAD Exam Questions

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

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

Comprehensive and Detailed In-Depth

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.

Comprehensive and Detailed In-Depth

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.

In ServiceNow, UI Actions are elements such as buttons, links, and context menu items that allow users to perform actions on records or lists. The three valid UI Action types are:

1. List Banner Button (Option A)

Description: A button that appears in the list view header, allowing users to trigger an action affecting multiple records at once.

Example: A 'Bulk Approve' button that processes selected records.

2. Form Button (Option B)

Description: A button that appears on a form, allowing users to trigger actions related to the current record.

Example: A 'Submit for Approval' button on an incident form.

3. Record Navigation Button (Option D)

Description: A button that helps users navigate between related records.

Example: A 'Go to Parent Record' button that redirects users to a linked record.

Incorrect Options:

Form Choice (Option C):

Not a UI Action type. Choices are typically used in choice fields (dropdowns) rather than UI actions.

List Choice (Option E):

Not a valid UI Action type. Similar to 'Form Choice,' it pertains to field options rather than UI elements.

Workflow Action (Option F):

Workflows are process automation tools, not UI Actions. They are not directly related to buttons or links that users interact with.

For more details, see the official ServiceNow documentation on UI Actions.