Each class or subtype has a number of attributes that describe this type in more detail. The Data Dictionary contains a list of attributes for each class. If no attributes are specified in the Data Dictionary for a subtype, the subtype inherits all attributes from the corresponding class. If no attributes are specified for a class in the Data Dictionary, this class has all fields from the corresponding table or feature class as attributes.
Each attribute has a logical name as a key. For an object of a class, the respective attribute value can be accessed via this name.
Properties |
Description |
||||||
|---|---|---|---|---|---|---|---|
Display name |
Each attribute has a display name. In attribute data forms and attribute dialogs this display name is used as identifier for the attribute. The display name is localizable and can be adapted to different languages. |
||||||
Column name |
The column name is used to associate the attribute with a specific field from the corresponding table or feature class. |
||||||
Database type |
The specification of the database type determines the form in which the attribute value is stored in the database. |
||||||
Property type |
The specification of the property type determines how the attribute value is handled in the application. For example, for a text field that is stored as a string in the database, the property type Url or Uri can be defined. This indicates that this string is an URL. During configuration, you must ensure that the database type and property type can correspond. For example, the configuration of a property type String in combination with a database type Integer can cause problems if the text entered by the user cannot be interpreted as a numerical value. |
||||||
Category |
Each attribute has a category. By specifying a category, attributes can be summarized and grouped. In attribute data forms and attribute dialogs, attributes of a category are displayed as belonging together and can thus be shown or hidden automatically and together. Using a category is optional. If no category is specified for an attribute, an implicit classification in the category Miscellaneous is performed. |
||||||
Help text |
Each attribute can be provided with a description. In attribute data forms and attribute dialogs, this description is displayed as quick info or in supporting text elements. |
||||||
Base unit |
Attributes can have a physical base unit. If an attribute refers to a base unit, this information is placed after the attribute value. |
||||||
Editor |
For each attribute it can be defined which editor is to be used in attribute data forms and attribute dialogs. Following editors can be used:
|
||||||
Activation |
Each attribute can be activated or deactivated. A deactivated attribute cannot be edited in the interface. Nevertheless, a value can be set for this attribute programmatically or as part of user functionality. |
||||||
Mandatory field |
If an attribute has been declared as a mandatory field, a value must be specified for the associated field when an object is entered. |
||||||
Read only |
If an attribute is configured as Read only, no value can be entered for this field. The attribute cannot be edited in the user interface either. |
||||||
Visibility |
Visibility can be set for attributes. Attributes that have been configured as invisible are not displayed in the interface. |
||||||
Formatting |
A formatting can be set for each attribute. Formatting can be assigned for numeric or date attributes.
|
||||||
Focus traversal |
For each attribute the position in the focus traversal can be specified. |
