Welcome
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.
Native JSON schema support
This documentation describes the Native JSON schema support.
Special JSON literals

Introduction
Congratulations on your selection of HCL Link as your data integration solution!
What's new
Learn about the new and changed functions and features in HCL Link version 1.3.2.0.
Release notes
Read the latest release specific information for HCL Link version 1.3.2.0.
System requirements
A complete desciption of the hardware and software requirements for both Windows and Linux systems.
Installation
Everything you need to know to install HCL Link.
Administration
Here you will find the tasks that are required for administration of your HCL Link product.
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
  - Native XML schema support
    HCL Link provides Native XML schema support.
  - Native JSON schema support
    This documentation describes the Native JSON schema support.
    - Importing JSON documents
      A JSON document can be used to define a schema. This process is known as importing a JSON document. Schemas defined in this way are called native JSON schemas.
    - The representation of JSON types in Link schemas
      A JSON object is represented as a group type in a native JSON schema. The components of the group type correspond to the properties of the JSON object. The name of a component, which is the name of the type of the component, corresponds to the name of the property of the JSON object.
    - Using native JSON schemas in a map
      A native JSON schema can be used in an input card or an output card.
    - Special JSON literals
  - 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.
Services
Service definitions define REST services and the endpoints of a service. This guide provides step-by-step instructions for creating, importing, and managing services using the system interface, following Microsoft standards.
Connectors
This documentation describes the connectors and how they are used.
Packages
Servers
This documentation contains a description of the server groups and servers.
Variables
The variables described here include Configuration variables, flow variables, and cache variables.
Dashboards
A description of HCL Link dashboards, including the Server dashboard and the Kibana dashboard.
Runtimes
Descriptions of Link runtime services.
Resource Adapters
About the HCL Link Resource Adapters, and how to use them.
Cloud Native Link
Cloud Native Link refers to the HCL Link product installation on a Kubernetes cluster.
Reference
This documentation provides HCL Link reference information.
Notices

Special JSON literals

These are used to produce special JSON unquoted output.

Literal

<JSONNULL> - Will produce "anyfield" : null

<JSONTRUE> - Will produce "anyfield" : true

<JSONFLSE> - Will produce "anyfield" : false

For example: assigning ="<JSONNULL>" to a field called "name" will produce "name" : null

Note:

These literals must be only used with native JSON type trees and must be the only data passed to that field (results are unpredictable for other uses).