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.
Components
Defining components
Guidelines for defining components

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.

Guidelines for defining components

The guidelines below are numbered to allow references to each other. The numbering does not suggest a priority or a sequence to be followed in observing the guidelines.

Categories cannot have components.
A category is only used for organizing your schema and for setting common properties.
A partitioned group cannot have components.
A partitioned group always represents a choice among the subtypes of that group. You never map a partitioned group without its subtree, so it does not need components.
Note: A subtree is a branch of a schema that includes a type and all of the subtypes that stem underneath it.
If a group is not partitioned, it must have at least one component.
Nonpartitioned groups are sequences of data objects rather than choices. A sequence must contain at least one component.
A type and one of its subtypes cannot be in the same component list.
If a type has components, a subtype can inherit any of those components or any type in the subtree of one of those components.
If a type has no components, a subtype can inherit any type that could be in that type's component list.
A type that has an initiator and a terminator can have itself or one of its ancestors as a component.
A type cannot have one of its subtypes as a component.