Home
Design Server
The documentation provided here describes how to use the Design Server.
Schema designer
Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
Type properties
XML properties in the schema
Identity constraints

Design Server
The documentation provided here describes how to use the Design Server.
- Projects
  This documentation describes Design Server projects.
- Schemas
- Maps
- Flows
  A flow node invokes a sub flow within a flow. Sub-flows need not be wired to other nodes; it is valid to have a flow that is comprised of multiple sub-flows that each have listeners.
- Using Design Server
  How to use the HCL Link Design Server.
- Flows
  This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
- Schema designer
  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

Identity constraints

The XML parser in Link enforces declared identity constraints. The XML Schema Importer sets these properties based on the XML Schema. In general, the identity constraint definition serves in one of the roles listed below:

Identity Constraint: Description
Unique: Enforces that a value (or combination of values) is unique within a given scope. For example, all product numbers must be unique within a catalogue.
Key: Enforces uniqueness and requires that all values be present. For example, every product must have a number and it must be unique within the catalogue.
Key References: Enforces that a value (or combination of values) corresponds to a value represented by a key or uniqueness constraint. For example, for every product number that is displayed as an item in a purchase order there must be a corresponding product number in the product description section.