In ServiceNow, when importing data from external sources, the platform utilizes Import Sets to stage the data before transforming it into target tables. The mechanism that defines how data from the Import Set fields map to the fields in an existing ServiceNow table is called a Transform Map.
* Transform Map: A Transform Map is a set of field mappings that determine the relationships between fields in an Import Set and fields in an existing ServiceNow table. It allows administrators to define how data should be transformed and inserted into the target table.
servicenow.com
* Business Service Management Map: This is not related to data import processes. It pertains to visual representations of business services and their dependencies.
* Schema Map Relationship Builder: The Schema Map provides a graphical representation of tables and their relationships within the database schema but does not handle data import mappings.
* Data Sources: Data Sources define the origin of the data being imported (e.g., files, JDBC connections) but do not determine the field mappings between Import Sets and target tables.

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]

Catalog Client Scripts and Catalog UI Policies are the client-side scripts that apply to Record Producers. Catalog Client Scripts allow you to add or modify functionality on a catalog item or record producer form. Catalog UI Policies dynamically change information on a catalog item or record producer form. UI Scripts, UI Actions, Client Scripts, and UI Policies do not apply to Record Producers. Reference: Catalog client scripts, Catalog UI policies

Checkbox tooltip: "Show this module when the user has the specified roles. Otherwise the user must have the roles specified by both the application menu and the module." The following is true for the Override application menu roles configuration option when configuring a module:
Users with the module role but without access to the application menu access the module. This is true because the Override application menu roles option allows users to bypass the application menu role requirement and access the module directly if they have the module role. For example, if a module has the itil role and the Override application menu roles option enabled, and the application menu has the admin role, then a user who has the itil role but not the admin role can still access the module.
The following are not true for the Override application menu roles configuration option when configuring a module:
Self-Service users can access the module even though they do not have roles. This is false because the Override application menu roles option does not grant access to the module to users who do not have any roles. Self-Service users are users who do not have any roles assigned to them and can only access the Self-Service portal and the Knowledge Base. To access the module, users need to have at least the module role.
Admin is given access to the module even if Access Controls would ordinarily prevent access. This is false because the Override application menu roles option does not override the Access Control (ACL) rules that apply to the module. Access Control rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user's roles and conditions. Admin is a role

The Field Watcher is a debugging tool that allows you to monitor the values of fields on a form as they change due to scripts or other actions. It can be used to debug Business Rules, Client Scripts, and Access Controls, but not Script Includes. Script Includes are server-side scripts that define reusable functions and classes. They are not associated with any specific field or form, and therefore cannot be watched by the Field Watcher.
Reference:
Field Watcher
Script Includes