Home
Projects
A project is a container for HCL Link artifacts.
Maps
Maps define input and output specifications and mapping rules for data transformation.
Map audit overview
Audit log contents
Data content information in the audit log

Projects
A project is a container for HCL Link artifacts.
- Flows
  This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
- Maps
  Maps define input and output specifications and mapping rules for data transformation.
  - Using Maps
  - Create maps to specify sources and targets
  - Maps and map source files
    Basic tasks involved in creating and managing maps.
  - Input and output cards
  - Card settings
  - Map rules
  - Formulating map rules
  - Functional map basics
  - Map settings
  - Configuring bursts
  - Building maps
  - Running a map
  - Managing invalid data
  - Map audit overview
    - Audit log contents
      - Controlling audit log content
        The map settings that control the map audit. You can also specify audit options from the command line. See Execution Commands documentation for command options. The audit log can be stored in a file or returned in memory if you use the RUN function or an API.
      - Execution summary in the audit log
      - Elapsed execution time in the audit log
      - Source data report by card
      - Target data report by card
      - BurstAudit Data in the audit log
      - Data content information in the audit log
    - Data settings in the audit log
    - Map settings in the audit log
    - Mapping from the audit log
  - Troubleshooting
  - Error and warning messages
- Schemas
  Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
- Connections and Actions
  This documentation describes connections and actions.
- Files
  Files are used in various places within HCL Link. HCL Link allows files to be uploaded to the HCL Linkserver.

Data content information in the audit log

You can audit input and output data. The data audit settings determine what information about the data is written to the audit log.

Auditing data keeps track of specified objects in the input(s) and/or output(s) of a map. The burst audit data information in the audit log can track every occurrence of a record in a file and record the total count of records.

In the resulting audit log, the <DataLog> section follows the </Burst> tag. Within <DataLog>, there is an entry for the first input card. Within the input entry, there is an entry for each occurrence of the object.

If item data is specified in an audit setting, and the item is to be interpreted as binary, the line following the object line has the start tag <Hex> and the data is presented as pairs of hex digits for each byte.

In the audit log, the <DataLog> section follows the </Burst> tag. Within <DataLog>, there is an entry for the first input card. Within the input entry, there is an entry for each occurrence of the object.

If item data is specified in an audit setting, and the item is to be interpreted as binary, the line following the object line has the start tag <Hex> and the data is presented as pairs of hex digits for each byte.