Custom fields allow you to extend the standard ticket, account, and custom object information with additional data specific to your business needs. This guide explains how custom fields work and how to use them effectively.

These fields provide flexibility to capture and manage specialized information beyond standard fields. They can be added to tickets, accounts and custom objects, enabling you to:

  • Collect specific business information
  • Standardize data collection
  • Enable advanced reporting
  • Automate workflows based on field values

​
Field sources

Custom fields can be associated with different sources:

Ticket fields

Fields that appear on tickets for tracking specific ticket-related information

Account fields

Fields that store account-specific information and appear on account records

Custom object fields

Fields that extend custom objects with additional attributes and data points

​
Field configuration

Each custom field can be configured with various properties:

​
Field types

The Thena platform supports a wide range of field types to capture different kinds of data. Each type has specific properties and validation rules.

​
Text fields

​
Numeric fields

​
Date and time fields

​
Choice fields

​
Specialized fields

​
Advanced fields

​
Validation

Field validation ensures data quality and consistency across tickets, accounts, and custom objects.

​
Validation types

​
Advanced validation

​
Error handling

​
Best practices

Field design

• Use clear, descriptive names
• Choose appropriate field types
• Set helpful default values
• Add descriptive hints
• Consider source-specific needs

Field management

• Review field usage regularly
• Archive unused fields
• Document field purposes
• Maintain consistent naming
• Monitor cross-source relationships

Validation design

• Keep rules simple and clear
• Provide helpful error messages
• Use appropriate validation types
• Test edge cases
• Consider source-specific needs

Error handling

• Show errors immediately
• Provide clear guidance
• Offer error resolution
• Log validation issues
• Handle cross-source validation

​
API reference

​
Create custom field

{
  "name": "device_type",
  "displayName": "Device Type",
  "description": "Type of device the customer is using",
  "type": "SELECT",
  "isRequired": false,
  "isActive": true,
  "options": [
    {
      "label": "Mobile",
      "value": "mobile"
    },
    {
      "label": "Desktop",
      "value": "desktop"
    },
    {
      "label": "Tablet",
      "value": "tablet"
    }
  ],
  "defaultValue": "desktop",
  "validation": {
    "pattern": null,
    "min": null,
    "max": null
  }
}

​
Available operations

The structure and available options for custom fields depend on the field type selected. The example above shows a SELECT type field with predefined options.

Each field type has its own specific configuration options and validation rules.