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.
Type properties
Item properties
Number item subclass properties
Pad
Padded to > SizedAs

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

Padded to > SizedAs

Use the Padded to > SizedAs property to specify that padding is measured in either bytes or characters. The default setting is Bytes.

Trace file and audit log lengths are always reported in bytes.

Table 1. Pad implementation example (bytes compared to characters)
Scenario for empty field:	Result:
Data language is UTF-8 Pad > Value = `À` (hexadecimal representation = `0xC3 0x80`) Pad > Padded to = Fixed Size Padded to > Length = 5 Padded to > SizedAs = Bytes	Two `À` pad characters using 4 bytes.
Data language is UTF-8 Pad > Value = `À` (hexadecimal representation = `0xC3 0x80`) Pad > Padded to = Fixed Size Padded to > Length = 5 Padded to > SizedAs = Characters	Five `À` pad characters totaling 10 UTF-8 bytes.