Home
Reference Guide
This guide describes conceptual information about data design environment components when you want to use the data fabrication feature in HCL OneTest™ Server.
Schema design
A schema is a graphical data dictionary that contains metadata definitions of the structure of a document to generate test data. Schema provides visual cues for understanding the structure and complete definition of an object.
Components
Defining components
Guidelines for defining components

Reference Guide
This guide describes conceptual information about data design environment components when you want to use the data fabrication feature in HCL OneTest™ Server.
- Files
  You add a file to a project to use it as input in the project. You can upload a file from your local file system to a project from the Files tab to generate test data. Alternatively, you can upload it when you define an action.
- Connections
  A connection defines the properties that are required to connect to an external resource. An action uses a connection to provide source data to a project or write data from a source to a target. Multiple actions can use the same connection. You can define both connections and actions at the project level.
- Schema design
  A schema is a graphical data dictionary that contains metadata definitions of the structure of a document to generate test data. Schema provides visual cues for understanding the structure and complete definition of an object.
  - Introduction to schema design
    Use the Schemas tab to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
  - Type properties
    The properties of a type define the characteristics of the data objects of that type.
  - Item restrictions
    Item restrictions are an optional feature you can use to specify valid or invalid data objects for an item type. Item restrictions are grouped into three categories: Value, Character, and Range.
  - Components
  - Partitioning
  - Type inheritance
  - Schema analyzer
  - Distinguishable objects
  - Functions and expressions

Guidelines for defining components

The guidelines below are numbered to allow references to each other. The numbering does not suggest a priority or a sequence to be followed in observing the guidelines.

Categories cannot have components.
A category is only used for organizing your schema and for setting common properties.
A partitioned group cannot have components.
A partitioned group always represents a choice among the subtypes of that group. You never map a partitioned group without its subtree, so it does not need components.
Note: A subtree is a branch of a schema that includes a type and all of the subtypes that stem underneath it.
If a group is not partitioned, it must have at least one component.
Nonpartitioned groups are sequences of data objects rather than choices. A sequence must contain at least one component.
A type and one of its subtypes cannot be in the same component list.
If a type has components, a subtype can inherit any of those components or any type in the subtree of one of those components.
If a type has no components, a subtype can inherit any type that could be in that type's component list.
A type that has an initiator and a terminator can have itself or one of its ancestors as a component.
A type cannot have one of its subtypes as a component.