https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/reference-pages/task/schedul Generate and distribute scheduled reports via email.
A report is a graphical representation of data from one or more tables in ServiceNow. The following are true for reports in ServiceNow:
* Can be a graphical representation of data. This is true because reports can use various chart types, such as pie, bar, line, or gauge, to visualize data in a meaningful way.
* Can be run on demand by authorized users. This is true because reports can be accessed from the Reports menu or the Report Navigator and run by users who have the appropriate roles and permissions to view the data.
* Can be scheduled to be run and distributed by email. This is true because reports can be configured to run at a specific time and frequency and send the results to one or more email recipients.
The following are not true for reports in ServiceNow:
* Any user can see any report shared with them. This is false because users can only see reports that are shared with them if they also have access to the data source of the report. For example, a user who does not have the itil role cannot see a report based on the incident table, even if the report is shared with them.
* All users can generate reports on any table. This is false because users can only generate reports on
* tables that they have access to and that are enabled for reporting. For example, a user who does not have the admin role cannot generate reports on the sys_user table, which is the table for user records.
References: Reports, Report Security

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

When creating a table, the Create module field allows you to automatically create a module for the table in the application menu. The default behavior of the new module is to display a list of all records from the table. This can be changed later by editing the module properties and specifying a different link type, such as form, URL, or script.
References:
Create a table
Module properties

https://developer.servicenow.com/dev.do#!/learn/learning-plans/rome/new_to_servicenow/app_store_learnv2_sc The following are debugging strategies for client-side scripts, which run in the web browser and manipulate the user interface:
* g_form.addInfoMessage(). This is a client-side API that displays an information message at the top of the form.
* Field Watcher. This is a debugging tool that displays the current and previous values of one or more fields on a form.
* jslog(). This is a client-side API that writes a message to the browser console.
The following is not a debugging strategy for client-side scripts, but for server-side scripts, which run on the ServiceNow platform and manipulate the database:
* gs.log(). This is a server-side API that writes a message to the system log. References: Client-Side Scripting APIs, Debugging Client Scripts

The source control operation used to store local changes on an instance for later application is called a stash. A stash is a temporary storage area for uncommitted changes that are not ready to be pushed to a remote repository. Developers can use stashes to save their work in progress without committing it to the local repository or discarding it. Stashes can be applied later to restore the changes to the working directory, or dropped if they are no longer needed. Reference: [ServiceNow Docs - Stash local changes], [ServiceNow Docs - Source control]