General

In general, all individual fields can be displayed as normal fields. However, there are special features that are explained below. With the "model", care must be taken that the prefix is always "entity.IndividualFields." followed by the field name in lower case. To use field components that work with a datasource URL or similar, an individual API endpoint is needed. You can find out how to create an individual API endpoint here. With the name of the API or with the ID of the API, you can retrieve the required data. To do this, assign the following URL to the property "dataSourceURL":

Statistic/api/dynamicapi/<ID der API>/GetData

or

Statistic/api/dynamicapi/<Namen der API>/GetDataByServiceName

Creating individual fields

Individual fields can be created via the options tool using the menu item "System -> Individual tables -> Create tables".

The names of the individual fields must be unique throughout the system.
Data types and translations can be defined in the following menu items.

Categories for individual fields

If individual fields are to be grouped into categories, this option must first be activated. To do this, an entry with Gruppe = 1005 and Zaehler = 2 (and LangIdx = 0 and Beschreibung = “1”) must be entered in the FELDINHALT table.

Do not forget to log in again, as this setting is only checked when the session is started and is not read out again afterwards.

Create new category

All categories are listed in the INDKAT table. If you want to create a new category, you must create a new entry in the INDKAT table. The fields must be set as follows:

Name	Description
ID	A unique Id of the category.
TABELLE	The name of the table containing the individual fields to be categorised.
KATNAME	The desired name of the category.
POS	Used to specify the order in which the categories are listed.

Once a category has been created in INDKAT, the desired individual fields must be assigned to this category.

This setting is made in the table INDKATFELDER.

The meaning of the fields are:

Name	Description
ID	Unique Id of the record.
KAT	The Id of the Category.
FELD	The field name of the individual field to be added to this category.
VISIBLE	Specifies whether this field should be visible to internal users.
READONLY	Specifies whether the values for the individual field may be changed by internal users.
VISIBLE_EXTERN	Visibility setting for external users.
READONLY_EXTERN	Sets whether external users are allowed to change values for this individual field.
SEARCHABLE	Indicates whether the field can be used in the search mask (currently not supported).
POS	Specifies the position of the field for sorting.

If categories are used, only those individual fields are displayed that are listed in the INDKATFELDER table and set to "Visible" for the respective user group.
If there is no entry for an individual field in the INDKATFELDER table, this is equivalent to "Visible = false".

Translations for categories

At present, it is not possible to manage translations for categories directly via the software (e.g. OptionsTool).
The translations can currently only be entered via the database. In the FSM, the categories of the individual fields are then displayed in the set language.

Sprachunabhängige Übersetzung oder Umbenennung

If you want to rename a category independently of the language, you need an entry in the PLTRANSLATE table.
The fields must contain the following values:

Name	Description
TABELLE	The name of the table containing the field to be renamed. For categories, the value here must be 'INDKAT'.
FELD	The name of the field to be renamed. For categories, the category ID must be entered here.
BEZEICHNUNG	The value of renaming.

If there is no language-specific renaming/translation for a category, the language-independent translation is used.

Language-specific translation of a category

If a translation for a target language is to be created for a category, the table PLTRANSLATELANG is used.
PLTRANSLATELANG is structured similarly to PLTRANSLATE, except that a language key must also be maintained.
For example, if you want to translate a category into English, the following entry must be created in the table:

SPRACH=1;TABELLE=INDKAT;FELD=KategorieID;BEZEICHNUNG=Übersetzung

PLTRANSLATE is normally used for a fallback translation if no translation is available in PLTRANSALTELANG for a given language.

Linking an individual field to a table

Instead of an API endpoint, a field can also be linked to another table. For this, the following entries must be set in the PLSTEUER table.

Name	Description
Bezeichnung	Name of the field from the corresponding individual table.
Tabelle	Enter the name of the look-up table here.
Auswahltyp	Here you specify the component in which the value is to be entered. In this case, if you want to link the individual field with a table, you must enter the value 0 here.
Pflichtfeld	Enter the value "1" here if the field is to be a mandatory field. Otherwise enter the value "0".
OrderByFeld	This field records the sort order in the selection table, the entry is made without SQL.

The Component "individualData"

With the component "individualData", fields from the corresponding individual table are displayed. There is also a "mixed mode". If certain individual fields are already present in the mask, they are not displayed a second time in the component.

"title": "{{{WebSMS.Additional.NData}}}",
"visible": "!entity.IsNew",
"moduleName": "app/core/components/individualNData",
"iconName": "table",
"helpUrl": "{{helpBaseUrl}}/inscd/{{helpVersion}}/{{helpLanguage}}/pflegen-von-stammdaten/verwalten-von-adressdaten",
"props": {
	"type": "Address"
}

Tabular individual data

The tabular individual data can be displayed with the component "individualNData".

{
"title": "{{{WebSMS.Additional.NData}}}",
"visible": "!entity.IsNew",
"moduleName": "app/core/components/individualNData",
"iconName": "table",
"helpUrl": "{{helpBaseUrl}}/inscd/{{helpVersion}}/{{helpLanguage}}/pflegen-von-stammdaten/verwalten-von-adressdaten",
"props": {
	"type": "Address"
 }