Transformation script variables
-
- UpdatedAug 1, 2024
- 2 minutes to read
- Xanadu
- Data Management
Multiple variables can be used to define explicit mapping relationships in a transform map script.
- Variable name: source
Type:GlideRecord object
Description: Contains the import source record currently being transformed. Specify a specific field from the source record as an object property.
Example:- Variable name: target
Type:GlideRecord object
Description: Contains the import target record currently being inserted. Specify a specific field from the target record as an object property.
Example:- Variable name: map
Type:GlideRecord object
Description: Contains the transformation map record currently being used for the transformation process. Specify a specific field from the transform map record with one of these properties.- name
- sys_id
- source_table
- target_table
- order
Example:- Variable name: log
Type: Function
Description: Log information about the current import process. Each log level has its own method.
Example:- Variable name: action
Type: Function
Description: Specify the transformation action occurring on the target record. This value can be either "insert" or "update".
Example:- Variable name: ignore
Type: Boolean
Description: When set to true, skips or aborts the current import action. In onStart scripts, this variable aborts the entire transformation process. In onBefore scripts, this variable only skips the current row being transformed.
Example:- Variable name: error
Type: Boolean
Description: When set to true, aborts the current import action and logs an error message in the Import Set Log.
Example:- Variable name: error_message
Type: String (output message)
Description: When an error occurs, adds the specified error message to SOAP response.
Example:- Variable name: status_message
Type: String (output message)
Description: Adds the specified status message to SOAP response.
Example: