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

The server-side API debug log method available for scoped applications is gs.info(). This method logs informational messages that describe the progress of the application. Older methods such as gs.print() and gs.
log() are not available in scoped applications. The gs.debuglog() method does not exist. The gs.info(), gs.
warn(), gs.error(), and gs.debug() methods work in both scoped applications and global, and are therefore more versatile going forward in future versions. Reference: Debugging best practices

A Display Business Rule has access to the current, g_scratchpad, and GlideSystem objects, but not the previous object. The previous object is only available to Before Business Rules4. References: Business Rule API
https://docs.servicenow.com/bundle/tokyo-application-development/page/script/business-rules/concept/c_Busine

https://developer.servicenow.com/dev.do#!/learn/courses/sandiego/app_store_learnv2_learnmore_sandiego_learn_more/app_store_learnv2_learnmore_sandiego_form_and_list_layouts/app_store_learnv2_learnmore_sandiego_what_is_form_designer The Form Designer is a tool that allows you to create and customize forms on the ServiceNow platform. The Form Designer has four main components:
Form layout: The form layout shows the preview of the form and allows you to drag and drop fields, sections, and related lists onto the form. You can also resize, reorder, and delete the elements on the form layout.
Page header: The page header shows the name of the table and the form that you are editing. You can also access the form properties, save the form, and switch to the form view from the page header.
Field navigator: The field navigator shows the list of available fields for the table and allows you to search, filter, and add fields to the form. You can also create new fields and edit existing fields from the field navigator.
Schema map: The schema map is not part of the Form Designer. The schema map is a separate tool that shows the relationships between tables and fields on the platform. You can access the schema map from the System Definition > Tables module or from the context menu of a table.
Reference:
[Form Designer]
[Schema map]

A transform map determines the relationships between fields displaying in an Import Set table and fields in an existing ServiceNow table, such as the Incidents or Users table.
Reference:
The following platform feature can be used to determine the relationships between fields in an Import Set table to fields in an existing ServiceNow table:
Transform Map. This is a feature that defines the mapping between the fields of an Import Set table and the fields of a target table, such as incident, problem, or user. A transform map also specifies the logic and rules for transforming the imported data, such as coalescing, scripting, or applying data policies.
The following platform features are not used to determine the relationships between fields in an Import Set table to fields in an existing ServiceNow table:
Business Service Management Map. This is a feature that provides a graphical representation of the configuration items (CIs) and their relationships in the Configuration Management Database (CMDB). A Business Service Management Map can be used to visualize the impact of incidents, changes, or problems on the CIs and the services they support.
Data Sources. This is a feature that defines the connection and authentication information for an external data source, such as a file, a JDBC database, or a web service. A data source is used to import data from the external source into an Import Set table.
CI Relationship Builder. This is a feature that creates relationships between CIs in the CMDB based on predefined or custom rules. A CI Relationship Builder can be used to populate the CMDB with the dependencies and connections between the CIs. References: Transform Maps, Business Service Management Map, Data Sources, CI Relationship Builder