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

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

XML properties in the schema

When you open a schema in the schema designer after you imported it from a DTD or XML Schema, the XML-specific properties are displayed as read-only fields.

For each type in the resulting schema, the Intent property is either General (indicating non-XML) or XML. All category types that are created during the import process are considered non-XML properties. All group and item types that are created during the import process are considered XML properties.

Any types that you manually add to the XML schema are considered non-XML and have General intent. In such a case where there are both XML and non-XML types present (such as EDI data), the appropriate method of validation is determined automatically.

See Utilities for XML for information about tools that can assist you with upgrading your XML schemas and maps to this version of HCL Link.