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

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

Error detection

During map execution, the input data is compared to the data definition in the schema. If the data does not match the definition, it is invalid or "in error".

To validate a data object as belonging to a certain type, the data must be matched to its type definition. For data to be valid, the following must be true:

The data must have the properties that were defined for the type.
If the type is an item that has restrictions, the data object must match one of the restrictions.
If the type is a group, the components of the data object must match those defined in the group view, and each component rule must evaluate to "true" at map execution time.

Ultimately, all data objects, no matter how complex, consist of items because items represent the smallest unit of data. When all of the items that collectively comprise a component are found, the component has been "found."

When executing a map, invalid data is recorded in the trace file. You can decide what you want the system to do when errors are encountered: you can map the errors to an output and also have the system ignore invalid data. For methods on ignoring invalid data, see "Restart attribute" .