Home
Projects
A project is a container for HCL Link artifacts.
Maps
Maps define input and output specifications and mapping rules for data transformation.
Input and output cards

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 overview
      Each map can contain none or more input cards and none or more output cards.
    - Static input cards
      You can reduce the processing overhead of a map that runs repeatedly by including static input files in the map.
  - 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
  - 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.

Input and output cards

A map defines how to generate data objects of a certain type. A map contains input and output cards that transform data content from source formats to target formats. This data transformation occurs according to mapping rules on the data objects in the output card in the map.

Input and output cards represent data objects. Each card represents one data object, which is defined as a particular type. There are two types of map cards: input cards and output cards.

An input card contains the complete definition of an input for the map including information such as source identification, retrieval specifics, and the behavior that should occur during processing.
An output card contains the complete definition of an output for the map including information such as target identification, destination specifics, and the behavior that should occur during processing.

Each input of data and each output of data requires content definition settings. The content of each card is specified as a type in a schema.