Home
Projects
A project is a container for HCL Link artifacts.
Maps
Maps define input and output specifications and mapping rules for data transformation.
Formulating map rules
When input data is missing
When portions of an input series are missing

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
    - When input data is missing
      - When portions of an input series are missing
      - When an output evaluates to NONE
    - Mapping an input item to an output item
    - Mapping a group to a group
    - Outputs with maximum range greater than 1
    - Indexing an output
      When you know the number of objects to generate for each map execution, index the number of occurrences of that output object. To index an output is to generate a specific number of occurrences of that output.
    - Mapping to multiple occurrences of a group
    - Indexing an Input
    - Mapping from a floating component type
  - 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.

When portions of an input series are missing

When portions of an input series are missing, the output to which it is mapped built according to the Track property of the type in the schemas. The Track property indicates whether to only track the components that have content (Track = Content) or all components, including those that do not have content (Track = Places).

If both the input data object and the output data object have the Track = Places property, the place holder is generated on output, even if there is no data. Example output data with a missing third item would be:

YES,YES,,YES

If the input data object has the Track = Content property, the empty occurrences of that data object are not mapped and the empty occurrences are not built. Example output data with a missing third item would be:

YES,YES,YES