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
Card overview
Each map can contain none or more input cards and none or more output cards.
Card specifics

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.
      - Card specifics
    - Native XML schema support
      HCL Link provides Native XML schema support.
    - Native JSON schema support
      HCL Link supports using JSON templates, or JSON schema documents to define the schema of a card.
    - 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.

Card specifics

More than one card in a map can reference the same type but the cards must have different card names.
Each card is assigned a number when it is created. Cards are numbered sequentially, beginning at 1. The card numbers determine the order in which the cards and the data in those cards is evaluated. The card number is important when a map is used as a functional map. To reorder the cards, use the Reorder command on the Card menu.
The structure of the card object appears in the card. An icon represents each component that the entire card data object is composed of. Each icon in the input and output card represents a type that has been defined in the schemas.
The output column in the output card shows the structure and the names of the components of the output data object.
In the case of partitioned groups, the structure shown is the partitioned group and its subtypes. An icon is shown for each component and each partition that compose the entire card object.
Each output name appears in a separate cell in the output card.
The rule column contains a rule cell for each output object. Enter map rules to define how to generate the data object of this card.