In the DiliTrust Entities Module, you can create new data types to model complex relationships in your data.
This feature is called Custom Fields.
Only users with admin privileges can set up and configure Custom Fields.
To Access the functionality, open the platform under:
How to Access
Navigate to:
Configuration > Data Customization

In this section, you can review, filter, and create Custom Fields.

Click “Create a Field” to open a popup where you can configure your new field.


The following fields are mandatory:
Field Title: The name of the Custom Field (e.g., “Example #1”), with support for multi-language input in multinational instances.
Entity: The entity type the Custom Field is linked to. Options include:
Task
Events
Documents
Bank Accounts
Shareholders
Shares
Companies
Costs
Individuals
Mandates
Representatives
Faculties
Delegations
Contracts
Litigations
Type: Defines the data format. Types are grouped into three main categories:
Standard Types
Content (used to link another entity)
Reference List (not covered in this section)
If Content is selected, you can specify the entity type that the Custom Field should link to.
Optionally, each Custom field can be made:
- Historizable: to track changes in the value of the fields itself.
- Mandatory: to oblige each new entity instance to specify a value for that Custom Field.
Optional Settings
Each Custom Field can also be configured to be:
Historizable: Enables tracking of value changes over time.
Mandatory: Requires users to provide a value when creating or editing an entity.
Conditional (Reference list only): whether we want to activate conditional fields that depends on the choice form the list.
Multiple (Reference list only): if we want to give the possibility to attach multiple values from the list to our custom field
Grouping by Category
For Custom Fields linked to Companies, Individuals, Contracts, or Litigations, you can define a Category to group related fields.
For example, you might create categories based on departments, such as:
HR (Human Resources)
Operations

Field Usage
Once the Custom Field is configured, it will appear under the Extra Information section when creating or editing the corresponding entity.
N.B. In the case in which the Custom Field is set to be Mandatory, all future editing of the Entities linked with the Field will have to insert a value for this field, even though the custom field was not existent when the record was created.
Mandatory Historization on Fields
We’ve introduced a new enhancement that allows administrators to make historization mandatory on both standard and custom fields for Companies and Individuals. This ensures that every change to sensitive fields is always recorded in history, without relying on manual user action. ✅
What’s New ❓
- A new “Mandatory” option is available for all historizable fields.
- Applies to:
- Standard fields (e.g. Company Name)
- Custom fields for Companies and Individuals
- Mandatory historization can be enabled or disabled at any time, even after the field has been created and used.
How It Works ⚙️
When a field is configured as historization mandatory:
- The Historization checkbox is:
- Automatically checked
- Disabled (cannot be unticked)
- A default date (today)is applied to the history entry
- The date can still be edited if needed
- Every value change creates a history record
Where This Applies ?
Mandatory historization works consistently across all editing experiences:
- Edit modal → Information
- Edit modal → Extra Information
- Extra Information tab on entity detail pages
- Inline edit in the Tabular view
Important Behavior Notes ⚠️
- If a value is set back to its default state (e.g. empty value), no historization entry is created.
- Only actual value changes generate a history record.
- No additional permissions are required — existing access rules apply.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article