Option | Description |
|---|---|
Log file name | Click Browse and specify the log file name where the log messages must be stored. By default, the log file name is same as the artifact name. Note: No log file is created if the specified log file path is incorrect or left blank. |
Run options | Select one or both the following: • Clear log file before each run - Clears the contents of the log file before executing the map. • Flush log to disk after each message - Sends the contents of the log file to a file on the disk after each message. |
Error types to log | Select one or more of the following types of errors that must be logged in the log file: • Errors: Logs errors that may cause a map or process execution to stop. • Warnings: Logs messages about data truncation in a field, field name changes, loss of precision, or other issues. • Information Messages: Logs messages such as "Execution initialization...", "Execution successful", number of records converted, deleted, updated, or inserted, time to convert, and whether the map execution was stopped. • Debug Messages: All messages generated as a result of a TraceOn action and some other messages are logged at this level. In this case, the record number, first five fields of each record, and all the events are recorded. The messages are logged up to the selected log type including the previous log types in the order of precedence. For example, if Warnings is selected, then the log file includes both Errors and Warnings messages. Similarly, if Debug Messages is selected, then the log file includes Errors, Warnings, Informative Messages, and Debug Messages. Note: In case of v9 compatible artifacts, only the selected type of error message is included in the log file. |