You can create as many fields as you want for each data type, where each field:
The custom-field data is then available in:
You can change the “weight” of custom-fields, so they show up in the order you define.
||allows to administrate the custom field definitions|
By default, these are assigned to each user with the role
The custom fields will be shown on the “create and edit entity” forms and can have the following types:
|Input field type||Description|
||simple text field|
||number without decimal point|
||number with decimal places|
||enter a duration in various formats|
||dropdown of languages, shown in the user language|
||dropdown of currencies, shown in the user language|
||dropdown of countries, shown in the user language|
||browser specific input element to select a color|
||type a date or select it from the datepicker|
||type a date and time or select it from the picker|
|enter an email address (with basic validation)|
||multi-line text field|
||drop-down with custom entries|
Use the value
1 as default value for a pre-checked box or
0 for an unchecked box.
If a checkbox is marked as mandatory, the user has to check it in order to submit the form.
“Choice-list” is a different word for “Select-box” or “Drop-down”.
You have to add the entries as comma separated list into the default-value field.
For example a list consisting of fruits would look like this:
As the first entry is pre-selected, you can add an empty field to the dropdown by starting the list
with a leading
, like this:
Combined with the mandatory flag, this will force your users to select an entry from the list to be able to submit the form.
Choice list is also capable to configure title and values independently.
Let’s assume you have non-human friendly IDs for the value, but want to show a human friendly text, you can separate
each value from its title by using a pipe
A select box that is useful if you want to generate automatic invoices via command line / cronjobs.
The Kimai command
bin/console kimai:invoice:create supports invoice templates via custom-field (see docs).
The option parameter
--template-meta takes the internal name of the custom field that will identify the invoice template to be used.