Custom fields are used to extend forms for individual record types with additional, user-definable data. They allow you to customize forms to specific processes, service types, or organizational needs without requiring any programming changes to the application.
To enable custom fields to be reused across different forms and data types, they are designed as universal and configurable elements. This is reflected in their multi-level structure, which separates the field’s display from its data type and value sources. Understanding this structure is a prerequisite for correctly configuring your own forms.
The structure consists of 3 parts:
- Custom field – represents a “container” with a name that appears on the left side of the input field in the form. If the custom field does not contain any basic properties, only its name will be displayed in the form, without the option to enter a value. Based on the configuration of custom fields, we distinguish between:
- Simple custom field – a custom field that contains only one basic property
- Composite custom field – a custom field that contains more than one basic property.
- Basic property – the elementary building block of a custom field. It determines the data type of the entered value, such as text, number, date, custom dropdown, etc.
- Custom dropdown – a user-defined list of values that can be used as a data source for a basic property. The dropdown’s content is managed manually and allows you to restrict value entry to predefined options.
The following documentation articles provide detailed information on the individual sections of the user fields.