Form Masks
Configuring form masks is also possible across domains and can be found in a configuration. Translations are also included there for multilingual capability.
Here, it is important to note that the keys in the file are unique. This document will expand on how the keys must be defined to ensure this.
Configuration of the form mask is divided into the following four parts:
Locales
This enables support of multiple languages. To date, English and German are planned as defaults. It would, however, be possible to add other languages.
Content:
Values from choice lists, values from Esri domains, titles from form masks, titles from registers, designations of expressions and designations of field names
CodedValues
In addition to the content of the choice lists, these include the option to also make columns dependent on one another to facilitate multiple languages.
Expressions
Formatting for fields that can be used for several columns in different tables. Several fields can also be summarized in one expression.
Schemas
The actual representation of the form mask is configured under schemas. In addition to the column order or grouping of several columns into one group, it is possible to define areas of visibility and dependencies of columns on one another.
Content:
Title name and placement, write protection, content grouping, group title and what the representation of the group looks like, which columns are to be represented and how. In addition to the column title, settings can also be specified for value slots and dependencies on other fields and their content, plus whether the column should be displayed.
The configuration of an attribute form is organized in 5 parts:
Configuration parts |
Description |
Version of the JSON structure |
|
"locales" |
Definition of the language form for the different texts and data content of an attribute form. Per language, there is a subgroup with language abbreviation: de, fr, etc. Country-specific abbreviations are also possible (de_de, de_ch, de_at). The inv subgroup is taken as the default display if no translation exists for the text in the form for the user’s language. VertiGIS uses English as the default (inv). If no definition exists also, the text as transferred by the service is used. Each entry in locales must be unambiguous within VertiGIS Networks Solution (hence multidisciplinary). The entries are the placeholders that are referenced in the remainder of the file. |
"codedValues" |
Definition of the choice lists and their dependencies. |
"expressions" |
Expressions that can be used to calculate and display values. |
"schemas" |
Definition of the attribute form content for the different feature classes. |
The following chapters describe:
•For what information an entry should be created under locales
•What naming convention should be used to ensure entries are unambiguous for locales, expressions and codedValues.
