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
Mapping from a floating component type

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
    - 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.

Mapping from a floating component type

About this task

If an input card data object is a group that has a floating component type, you can map from the floating component type. A floating component must be distinguishable from every component of the group it is assigned to. On input, a floating component can appear after the initiator and after each component. If a floating component is associated with an input data object, it can appear as the first component.

If a type object has content, a floating component is built as the specified literal after the initiator and after each component. If this feature is used, it is up to the user to include a literal that will validate as an object of the type of the floating component.

You cannot map to a floating component in the output. If you have a floating component in the output data to which you want to map, you must define them as components of the output.