Home
Projects
A project is a container for HCL Link artifacts.
Schemas
Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
Distinguishable objects
Bound components
Component of an implicit group

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.
- Schemas
  Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
  - About schemas
    A schema defines the contents of at least one input that you intend to map or one output you intend to map.
  - Subtypes
  - Schema hierarchy
  - Defining data
  - Objects, types, and classes
  - Testing part of a schema
    You can test a schema by generating test data for an item or a group. The schema designer creates source and compiled maps that generate and validate the test data. The test-data-generation map automatically runs and produces a text file with the sample data. After that, the test-data-validation map automatically runs on the sample data file.
  - Type properties
  - Item restrictions
  - Components
  - Partitioning
  - Type inheritance
  - Error detection
  - Error recovery
  - Schema analyzer
  - Distinguishable objects
  - Return codes and error messages
- 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.

Component of an implicit group

Condition

Example

Its range is fixed and its type is bound.

The component Inventory Record (3:3) is bound, if the type Inventory Record is bound according to any of the conditions listed under "Bound Types" .

It has a component rule that binds it.

The component PO Record (s) is bound, if it has the following component rule which binds it:

PO# Field:PO Record = PO# Field:PO Record[LAST]

The schema analysis checks only that the component has a rule that refers to the component itself. The analysis does not check that the rule binds the component. You must ensure that the rule is one that binds the component.

It is sized (using the Sized attribute) by the component that precedes it.

The component Name Field (0:2) is bound, if the previous component in the group has the Sized attribute.