Table of Contents

Search

  1. Preface
  2. Introduction to Data Transformation
  3. Data Processor Transformation
  4. Wizard Input and Output Formats
  5. Relational Input and Output
  6. Using the IntelliScript Editor
  7. XMap
  8. Libraries
  9. Schema Object
  10. Command Line Interface
  11. Scripts
  12. Parsers
  13. Script Ports
  14. Document Processors
  15. Formats
  16. Data Holders
  17. Anchors
  18. Transformers
  19. Actions
  20. Serializers
  21. Mappers
  22. Locators, Keys, and Indexing
  23. Streamers
  24. Validators, Notifications, and Failure Handling
  25. Validation Rules
  26. Custom Script Components

Data Transformation User Guide

Data Transformation User Guide

Design-Time Event Log

Design-Time Event Log

The design-time event log contains the events that occur when you run the Data Processor transformation from the
Data Viewer
in the Developer tool.
When you run a Data Processor transformation from the
Data Viewer
view, the design-time event log appears in the
Data Processor Events
view. By default, the design-time event log contains notifications, warnings, and failures. In the transformation settings, you can configure the Data Processor transformation to exclude one or more event types from the log.
When you save the input documents with the log, you can click an event in the
Data Processor Events
view to find the location in the input document that generated the event. When you configure the Data Processor transformation settings, you can choose to save the input files for every run or only on failure.
The design-time event log is named
events.cme
. You can find the design-time event log for the last run of the Data Processor transformation in the following directory:
C:\<Installation_directory>\clients\DT\CMReports\Init\events.cme
The Data Processor transformation overwrites the design-time event log every time you run the transformation in the
Data Viewer
. Rename the design-time event log if you want to view it after a later run of the transformation,or if you want to compare the logs of different runs. When you close the Developer tool, the Developer does not save any files in the