Pass the ServiceNow Certified Application Developer CAD Questions and answers with ExamsMirror

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

In ServiceNow, UI Actions are elements that facilitate user interaction within the platform, enabling users to perform specific actions such as form submissions, record updates, or triggering workflows. The valid types of UI Actions include:

Form Button: A button displayed on a form that, when clicked, executes a defined action.

Form Context Menu: An option added to the context menu of a form, providing additional actions related to the form's record.

Form Link: A hyperlink on a form that directs users to another page or executes a script.

List Banner Button: A button displayed in the banner area of a list, allowing actions to be performed on multiple records simultaneously.

List Choice: An option added to the list context menu for individual records, enabling actions on a selected record.

List Link: A hyperlink in a list that directs users to another page or executes a script.

Record Navigation Button: Buttons that facilitate navigation between records, such as Next and Previous buttons.

Options like "Workflow action" and "Form choice" are not recognized as standard UI Action types in ServiceNow.

For comprehensive details, refer to the official ServiceNow documentation on UI Actions.

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​.

 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

The Bar Chart and Pie Chart report types can be created by right-clicking on a column header in a table’s list. These report types show how individual pieces of data relate to the whole using proportional bars or slices. You can also choose different aggregation methods such as count, sum, average, min, max, or percent. Reference: [Create reports from lists]

To link a ServiceNow application to a Git repository, you need to provide the user name, URL, and password of the Git account that hosts the repository12. The URL is the address of the Git repository that you want to link to the application. The user name and password are the credentials that you use to access the Git account. Alternatively, you can use a personal access token instead of a password for increased security3.

References = 1: Link an application to source control - ServiceNow Docs 2: Publish an application to the application repository - ServiceNow 3: Linking an application to Git using a personal access token instead of a password - ServiceNow

Ensuring that users receive email notifications in ServiceNow requires verifying specific attributes on the user record:

A. The Email field must have a valid value: This is correct. The Email field should contain a valid email address, as notifications are sent to the address specified in this field.

B. The user must not be locked out: While it's important for user access, being locked out does not directly impact the sending of email notifications.

C. The First name and Last name fields must have values: These fields are for identification purposes and do not affect email notification delivery.

D. Active must be true: This is correct. Only active users are eligible to receive email notifications. If a user is marked as inactive, notifications will not be sent to them.

E. Delegation must be enabled: Delegation pertains to assigning responsibilities to another user and does not influence the receipt of email notifications.

For effective email notification delivery, always ensure that the user's Email field contains a valid address and that the Active field is set to true.

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.