Every organization is different and has different data to store. That’s why most entities in Group-Office can be extended with custom fields.
Custom fields show in the:
- Edit dialogs
- Detail views
- Grid columns
- Advanced search and filters
You can create custom fields via System settings at:
- Address book
- … and many more!
The above list depends on the modules installed. You may have less or more options.
Creating and editing fields¶
Navigate to System settings -> Custom fields. You’ll see a list of customizable entities and their corresponding modules.
Click on the pencil icon in the right column to manage custom fields for a certain object. For an non-customized object, the resulting window wll look like below:
Click the + icon to add a field set first. A field set is a group of fields that has a title and an optional description that will be shown on the form. You can also hide field set in some cases. This depends on the module. In the address book you can only show it on certain address books for example.
When you’ve created a field set you can add a field via the ‘+’ button on the field set row:
The image below shows the custom field types you can add.
The types of custom fields that you can add depend on the modules you have installed.
Depending on the type of custom field, you have a plethora of options for your customization. For instance, you can conditionally require and/or hide a field:
The custom field will show in the:
Aside from displaying and storing data, it is a breeze to filter items by custom field values. In the left column, near the Filters header, click on the + and select Filter:
Conditionally required fields¶
It’s possible to make fields required based on a simple condition. You can also hide the field if the condition does not match.
For example you could create a checkbox called “provideDetails” and create a text field “details” with a condition ‘provideDetails = true’. The result will be that when you check the box the provideDetails field will be shown and made required.
The condition syntax is very simple:
<fieldName> <operator> <value>
- fieldName can be any property or custom field
- operator can be: =, !=, >, >=, <, <=
- value is a string without quotes. For checkboxes you can use 0,1 or true or false.
The fieldName, operator and value must be separated by spaces.