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 inheritance
Inheritance of category properties and components
When not to use categories

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
    - Inheritance of item properties and restrictions
    - Inheritance of category properties and components
    - Propagation of type properties
      Creation time is not the only time type properties can be passed from a type to its subtypes. You can use propagation to pass along certain type properties.
  - Error detection
  - Error recovery
  - Schema analyzer
  - Distinguishable objects
  - Return codes and error messages

When not to use categories

It is best not to use a category type when the subtypes will specifically be item types or specifically be group types.

For example, you have a type named Field for which the only subtypes will be items. If you make Field a category type, each time you create a subtype, the new type will also be a category type by default. You will have to change the Class property from Category to Item for each subtype that you create. Instead, make Field an item type so that the Class property for any subtypes you create will automatically be defined as item types.