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 component rules
Examples of component rules

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.

Examples of component rules

A component rule can limit the acceptable values of a component as shown in the following example:

Quantity < 10000
Interest Rate > .13 & Interest Rate < .20
WHEN (PurposeCode != "PF", ShipValue = 200|ShipCode < 0)

The following example illustrates how a component rule can make the presence of one component mandatory, if another component is present:

WHEN (PRESENT (Address Field), PRESENT (Qualifier Field))
WHEN (PRESENT (PhoneNumber), PRESENT (AreaCode), ABSENT (AreaCode))

A component rule can compare a component to the result of an arithmetic operation as shown in the following example:

SUM (((QuantityOrdered:Item Record:Detail) = TotalQuantity:Summary Record:Detail
Account Balance = Credits - Debits
Extension = Quantity*Price
#Items Field = COUNT (Item Record IN Invoice)