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.

g_scratchpad is a server-to-client data transfer object used primarily in the classic web UI rendering pipeline. A common, documented pattern is to populate g_scratchpad in a Display Business Rule (server-side) and then read those values in client-side scripts (such as Client Scripts or UI Scripts) while the form is being rendered in the browser. This avoids extra server calls when you need a small set of precomputed values or flags, such as whether the current user meets a condition, whether a related record exists, or which UI behavior should be enabled. It is not used to “populate properties for a Display Business Rule” as an end in itself; rather, the Display Business Rule is the place where developers often set g_scratchpad. It is also not a concept for defining constructors/destructors for table classes. While similar patterns can exist across experiences, g_scratchpad is specifically recognized as a web client bridging mechanism tied to server-side display processing, which matches option B.

In the SOAP Message feature set, we indicate variables using the following syntax: S{variable_name}. This allows us to pass a variable with the specified name from the SOAP message record to the web service function.

Tutorial: Handling a SOAP Response in ServiceNow | John Andersen

ServiceNow SOAP - Cheat Sheet Cheat Sheet by bibingokuldas - Download …

A Read-only protection policy allows the Script Include logic to be visible but prevents changes to the script on the instance where the application is installed. This is different from “Protected,” which is stronger and is intended to hide the script contents. It is also different from “None,” which allows other application developers to customize the Script Include. The CAD topic here is application file protection and intellectual-property management in distributed applications. Read-only is useful when developers want consumers to inspect the implementation for transparency or troubleshooting but do not want them to modify the script values. Therefore, option C accurately describes Read-only protection behavior.

================

Application Access is a feature that allows you to control the access level of other application scopes to your application’s data tables. By selecting the Allow access to this table via web services option, you can enable other application scopes to access your data tables using web services, such as SOAP or REST. However, the user performing the query via web services must have the correct permissions to access the table’s records. The user must have the appropriate roles and access controls to perform the operations on the table, such as create, read, write, or delete.

The other statements are not true when this option is selected. This option does not restrict the ability to delete records via web services, nor does it allow records to be always read. The access to the records depends on the user’s permissions and the web service method. This option also does not restrict access only to SOAP web services, but applies to both SOAP and REST web services. Finally, this option is not the only way to enable web service access to the table’s records. Even when this option is not selected, users with the correct permissions can use web services to access the table’s records, as long as they specify the application scope in the web service request.

" A table that extends another table is called a child class, and the table it extends is the parent class " - this is about halfway down in this link below: https://docs.servicenow.com/en-US/bundle/tokyo-platform-administration/page/administer/table-administration/concept/table-extension-and-classes.html

The Application Repository is a central location for storing, managing, and distributing custom applications developed on the Now Platform.

From Developer Site > App Repo:

“The ServiceNow Application Repository stores custom applications and enables developers to distribute applications across multiple instances in their organization.”

In ServiceNow, the gs object provides a range of methods for logging messages on the server side. However, the availability of these methods can vary depending on whether the application is global or scoped.

gs.info(): This method is available in scoped applications and is used to log informational messages to the system log. It provides a way to record general information during script execution.

Options A (gs.log()), B (gs.print()), and D (gs.debugLog()) are not available in scoped applications. These methods are either restricted to global applications or do not exist in the ServiceNow API.

For more detailed information, refer to the official ServiceNow documentation on server-side scripting:

A UI Action is a button, link, or choice that can be clicked by a user to perform an action, such as submitting a form or running a script. The following are UI Action types:

List choice. This is a UI Action that appears as a choice list on a list of records. It can be used to perform an action on multiple records at once, such as deleting or updating them.

Form button. This is a UI Action that appears as a button on a form. It can be used to perform an action on the current record, such as saving or approving it.

List banner button. This is a UI Action that appears as a button on the banner of a list of records. It can be used to perform an action on the entire list, such as exporting or printing it.

The following is not a UI Action type:

Form choice. This is not a UI Action type, but a field type. A form choice is a field that displays a choice list on a form. It can be used to select a value from a predefined set of options, such as priority or state. References: UI Actions, Field Types

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

The baseline behavior of a table in a privately-scoped application is that all application scopes can read from the table. A privately-scoped application is an application that restricts write access to its tables and resources to scripts within the same scope. However, read access is allowed by default for all scopes, unless the administrator explicitly denies it using an Access Control rule. This allows for data sharing between different applications while maintaining data integrity and security. References: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]