CAD Exam Dumps - Certified Application Developer - ServiceNow

"By default, all application scope scripts can read the table's records but cannot perform any other database operations." https://developer.servicenow.com/dev.do#!/learn/learning-plans/tokyo/servicenow_administrator/app_store_learnv2_securingapps_tokyo_application_access_database_settings

The Guided Application Creator in ServiceNow provides several methods for creating tables within a new application:

B. Create a table from scratch: This option allows developers to define a new table with custom fields and configurations tailored to the application's specific requirements.

C. Extend a table: Developers can create a new table that extends an existing ServiceNow table. This means the new table inherits all fields and behaviors of the parent table, allowing for customization and additional fields as needed.

D. Upload a spreadsheet: This feature enables developers to upload data from a spreadsheet, which ServiceNow then uses to create a new table. The system automatically defines the table structure based on the spreadsheet's contents.

The other options listed are not standard methods provided by the Guided Application Creator:

A. Use API calls: Creating tables via API calls is not a feature of the Guided Application Creator.

E. Create a table from a template: While templates can be used in other contexts, the Guided Application Creator does not offer a direct option to create tables from templates.

F. Link to external tables: Linking to external tables is not a standard feature within the Guided Application Creator.

G. Run import jobs: Running import jobs pertains to data import processes and is not a method for creating tables within the Guided Application Creator.

For more detailed information, refer to the official ServiceNow documentation on the Guided Application Creator.

In ServiceNow, when configuring a REST Message, the Endpoint specifies the URI (Uniform Resource Identifier) where the REST request is sent. This URI points to the resource on the external system that the REST message will interact with, whether it's to retrieve, update, create, or delete data.

Key Points:

Endpoint Definition: The Endpoint is a complete URL that includes the protocol (e.g., HTTP or HTTPS), the domain or IP address of the external server, and the specific path to the resource. For example: https://api.example.com/v1/resources.

Dynamic Endpoints: ServiceNow allows the use of variables within the Endpoint URL, enabling dynamic substitution at runtime. This is useful when the exact resource path or parameters need to be determined during execution.

Configuration in ServiceNow:

Navigate to "System Web Services" > "Outbound" > "REST Message."

Create a new REST Message or select an existing one.

In the REST Message record, define the Endpoint URL in the "Endpoint" field.

Example Scenario:

If you are integrating ServiceNow with an external ticketing system to retrieve incident data, the Endpoint might be something like https://api.ticketingsystem.com/incidents/{incident_id}, where {incident_id} is a placeholder that gets replaced with the actual incident ID at runtime.

https://docs.servicenow.com/bundle/tokyo-application-development/page/script/server-scripting/concept/c_ServerScripting.html

https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ApplicationScope.html

The correct statement regarding Application Scope is that applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts. Application Scope is a feature that identifies and isolates applications and their related artifacts from other applications. Each scoped application has a unique namespace identifier that consists of a prefix and a scope name. This prevents cross-application name collisions and ensures that only authorized scripts can access or modify data in a scoped application. References: [Product Documentation | ServiceNow], [How To Create a Scoped App in ServiceNow - YouTube]

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.