Show TOC

Procedure documentationDeveloping Core Data Types Locate this document in the navigation structure

Prerequisites

Before you begin to develop new core data types in the ES Repository, check whether any already exist in the ES Repository that you could use. Ideally there would be a unification and standardization process (governance) in your company to avoid any double developments. Additionally, (depending on the representation term) you must reference existing core data types.

The procedure below does not provide any design guidelines, and mainly describes how to use the data type editor.

Procedure

  1. Create a data type of classification Core Data Type in the ES Builder (more information: Creating Objects) and specify the appropriate Representation Term.

    Caution Caution

    According to CCTS, the name of the core data type depends on the representation term (the representation term is the last part of the core data type name). More information: Core Data Types and Aggregated Data Types

    End of the caution.
  2. Choose the Type Definition tab page. The type and properties of the element depend on the selected representation term. The attributes are also defined by the representation term.

    More information: XSD Editor (Core Data Types and Aggregated Data Types).

  3. Specify a built-in XSD type for the element. Alternatively, for some representation terms you can refer to a core data type, but only when you do not define any attributes for the core data types.

    Note Note

    You can only specify fixed values for core data types with the Code representation term. More information: Defining Fixed Values.

    End of the note.
  4. To add attributes for the core data type element, choose Add/Remove Attribute (Add/Remove Attribute). The function is only active when the the representation term allows attributes for the element.

  5. Assign a type to each attribute. The representation term determines from which components you can reference a built-in XSD type or another core data type.

  6. If required, add further restrictions to the element or to the attribute in the Details column.

  7. Save your changes.