Custom Fields are a Tractian platform feature that allows your company to add extra fields to standard forms, such as Requests, Work Orders, Assets, and others. With them, you can adapt forms to the specific needs of your operation, creating custom fields to store information that is important to your process.
Now, let’s see how to configure them on the Tractian platform.
Access
Access Settings;
Click on "Company";
Select "Custom Fields".
How to create a custom field
Choose the module where you want to add the field;
Click on "Add Field" within the desired section;
Fill in the field information:
Field name: Choose a clear and objective name to make it easy for users to understand. The name must be unique and cannot be repeated among custom fields.
Field type: Select the type of data you want to collect (see details below).
Configure additional options:
Set as required or optional.
Set as read-only (useful for fields automatically populated via integration).
Enable the field filter for use on the platform.
Click "Save".
The field will be included in the corresponding form and will be ready for use.
Available field types
Below is the full list of field types that can be created and configured:
Text: Allows free text entry. Can be configured as single-line text (with character limit) or multi-line text.
Selector: Field with a predefined list of options. Allows selecting one or multiple options. Options can be manually ordered and sub-options can be created within each item, allowing hierarchical lists.
Checklist: Predefined list of items to check. Can require selection of all items or allow partial selection.
User: Allows selecting users and/or teams registered in the company. Can be configured for single or multiple selection.
Value: Numeric field formatted as currency, respecting the company’s currency settings.
Number: Simple numeric field, with possible validation (only positive numbers, negative numbers, or both) and suffix addition.
Signature: Allows manual or digital signatures, restricted to specific users and/or teams.
Yes or No: Simple boolean field for binary responses.
Asset: Allows selecting assets and/or locations from the company.
Attachment: Field to attach files (e.g., images, documents).
Duration: Allows recording a period, configurable as time (hours/minutes) or a date range.
Date: Field for recording dates.
Audio: Allows recording and attaching audio files.
General field settings
Regardless of the type, custom fields have settings that define their behavior on the platform:
Required: Defines that the field must be filled before saving the form.
Active/Inactive: Inactive fields remain visible in historical records but cannot be used in new forms.
Read-only: The field is displayed on the form but cannot be edited. Commonly used for fields automatically populated via integration.
Filter enabled: Allows the field to be used as a filter.
Important information
Fields like Text, Number, and Value offer basic filters (filled/not filled).
Fields like Selector, Checklist, User, and Asset allow advanced filters based on specific options.
Internal name: The field’s original name is maintained even if the displayed title is edited or changed later.
Record counter: Displays how many current records use that field, helping to identify the impact before editing or deleting.
Permissions
Only administrators can create, edit, deactivate, or delete custom fields.
All users can view and fill in fields on forms as configured.
Important information
Creation of custom fields in Requests and Work Orders
When you create a custom field in Requests, it will automatically be replicated in Work Orders. This replication ensures data continuity, allowing values entered in the request to be transferred to the corresponding work order when it is approved.
However, replication occurs only from Requests to Work Orders. Creating fields directly in Work Orders does not replicate them to Requests.
Although creation is automatic in this flow, field deletion is independent: deleting a field in Requests will not remove it from Work Orders, and vice versa.
Disabled or deleted fields
Inactive fields remain visible in historical records, allowing consultation of previously registered information. However, inactive fields cannot be used in new records.
Deleting a field results in the permanent removal of both the structure and all associated data, including in historical records.