When configuring a REST Message, the Endpoint is:
* The URI of the data to be accessed, queried, or modified. This is the correct answer because the Endpoint is the part of the REST Message that specifies the location and the resource of the REST provider. The Endpoint is composed of the base URL and the resource path, which can include query parameters or variables. For example, the Endpoint for a REST Message that retrieves the weather information for a city from a web service could be https://api.openweathermap.org/data/2.5/weather?
q=London.
The following are not correct definitions of the Endpoint when configuring a REST Message:
* The commands to the REST script to stop execution. This is not correct because the commands to the REST script to stop execution are not part of the REST Message, but of the Scripted REST API, which is a feature that allows users to create custom REST endpoints on the ServiceNow platform. The commands to the REST script to stop execution are methods of the RESTAPIResponse object, such as setStatusCode, setError, or complete.
* Information about the format of the returned data. This is not correct because the information about the format of the returned data is not part of the Endpoint, but of the HTTP headers or the Accept field of the REST Message. The HTTP headers or the Accept field can be used to specify the content type of the response, such as JSON, XML, or HTML.
* The response from the provider indicating there is no data to send back. This is not correct because the response from the provider indicating there is no data to send back is not part of the Endpoint, but of the HTTP status code or the response body of the REST Message. The HTTP status code or the response body can be used to indicate the result of the REST request, such as 200 OK, 404 Not Found, or 500 Internal Server Error. References: REST Messages, Scripted REST APIs Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/integrate/outbound- rest/reference/r_RESTMessageElements.html

It is possible to change an application's scope in ServiceNow, either from global to private or from private to global. However, changing the scope of an application may affect its functionality and compatibility with other applications. Therefore, it is recommended to test the application thoroughly before and after changing its scope.
Reference:
How To Change Application Scope In ServiceNow - YouTube
How to move Custom Scoped Applications bettween instances - ServiceNow
Steps to switch a scoped application from your company's application repository to update sets - ServiceNow How to change the application (scope) of a SLA Definition without needing to recreate the SLA Definition - ServiceNow Advantages of Scoped Applications in ServiceNow - QualityClouds

In ServiceNow, Modules are navigation elements that provide access to various parts of the platform, such as forms, lists, reports, or other application components. They are organized within Application Menus to create a structured and intuitive navigation hierarchy.
Key characteristics of Modules:
* Part of Application Menus: Every module is contained within an application menu. This organization helps users navigate to different areas of the platform efficiently. For instance, the "Incident" application menu may contain modules like "Create New" or "All Incidents."
* Functionality: Modules can open various elements, including forms, lists, reports, or URLs. This flexibility allows modules to direct users to specific records, filtered lists, or external resources.
* Association with Tables: While many modules are associated with specific tables (e.g., a module that displays a list of incidents is associated with the "Incident" table), it's not a strict requirement. Some modules may link to external URLs or perform actions not directly tied to a table.
* Access Control: Access to modules is controlled through roles. Administrators can define which user roles have visibility and access to specific modules, ensuring that users only see modules relevant to their responsibilities.
For example, a module named "Active Incidents" under the "Incident" application menu might display a list of all active incident records. Access to this module can be restricted to users with the "itil" role, ensuring that only authorized personnel can view active incidents.
Reference: For more detailed information, please refer to the official ServiceNow documentation on Application Menus and Modules.

Explanation/Reference: https://community.servicenow.com/community?
id=community_question&sys_id=7ddc4462dbe2b3840be6a345ca9619af

https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/task/t_CreateANotification.html Reference:
An Email Notification is a record that defines the content and conditions for sending an email message from the ServiceNow platform. The following are configured in an Email Notification:
Who will receive the notification. This is specified by the Recipients related list, which can include users, groups, email addresses, or scripts that return email addresses.
What content will be in the notification. This is specified by the Subject and Message HTML fields, which can include variables, scripts, or templates to dynamically generate the email content.
When to send the notification. This is specified by the When to send tab, which defines the conditions and events that trigger the email notification.
The following is not configured in an Email Notification:
How to send the notification. This is not a configuration option for an Email Notification. The platform uses the SMTP protocol to send email messages, and the email properties control the email server settings and behavior. References: Email Notifications, Get Started with Notifications