A transform map determines the relationships between fields in an import set table and fields in an existing ServiceNow table. It also specifies how to transform the imported data before mapping it to the target table.
References:
* 1. What Exactly is an Import Set? - ServiceNow Developers
* Import set table - ServiceNow Application Development [Book]

https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference
/GlideQuery/concept/GlideQueryGlobalAPI.html#GlideQueryAPI
https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference
/glideRecordScoped/concept/c_GlideRecordScopedAPI.html

Flow Designer is a graphical tool that allows users to automate processes in ServiceNow without coding. The following are supported by Flow Designer:
Call a subflow from a flow. This is a feature that allows users to invoke a subflow, which is a reusable unit of logic, from a flow. This can help simplify complex flows and avoid duplication of logic.
Use Delegated Developer. This is a feature that allows administrators to delegate the development and maintenance of flows and actions to users who are not administrators. This can help distribute the workload and empower non-admin users to create automations.
Run a flow from a MetricBase Trigger. This is a feature that allows users to trigger a flow based on a MetricBase query, which is a way of analyzing time-series data in ServiceNow. This can help automate actions based on data trends and patterns.
The following is not supported by Flow Designer:
Test a flow with rollback. This is not a feature of Flow Designer, but of Automated Test Framework (ATF), which is a tool that allows users to create and run automated tests on ServiceNow applications and features. ATF supports testing flows with rollback, which means reverting any changes made by the flow during the test execution. References: Flow Designer, Automated Test Framework

In ServiceNow, when developing within a privately-scoped application, certain logging methods are recommended for use in server-side scripts to ensure proper logging and debugging. The GlideSystem (gs) object provides several methods for this purpose:
* gs.debug():
* Description: Logs messages at the "Debug" level.
* Usage: gs.debug('Debug message here');
* Purpose: Useful for logging detailed information during development and troubleshooting.
These messages are typically only visible when the system's logging level is set to "Debug."
* gs.error():
* Description: Logs messages at the "Error" level.
* Usage: gs.error('Error message here');
* Purpose: Used to log error messages that indicate a problem that might still allow the application to continue running.
* gs.warn():
* Description: Logs messages at the "Warning" level.
* Usage: gs.warn('Warning message here');
* Purpose: Used to log potentially harmful situations that are not necessarily errors but may require attention.
* gs.info():
* Description: Logs messages at the "Information" level.
* Usage: gs.info('Information message here');
* Purpose: Used to log informational messages that highlight the progress of the application at a coarse-grained level.
Deprecated or Unsupported Methods in Scoped Applications:
* gs.log():
* Description: This method is not supported in scoped applications. It is restricted to the global scope and is not accessible from a private scope. Therefore, it should be avoided in privately- scoped applications.