Skip to content

DynamicFieldDatabaseExtensions

Compatibility OTOBO ≥ 11.0.x, Znuny ≥ 7.0.x

Overview

With the DynamicFieldDatabaseExtensions plugin, you can structure the display of values for dynamic fields of type "Database" in OTOBO more clearly. It adds a dropdown menu in the admin area that allows you to group values by self-defined headers.

Installation

  1. Via Package Manager
  • Navigate to Administration → Package Management in the OTOBO admin area.
  • Search for "DynamicFieldDatabaseExtensions" and install the add-on.
  1. Manual Installation
  • Unpack the plugin archive into the Kernel/Config/Files/ directory.
  • In the admin area under Administration → Update → Reload file system, activate the new files.

Configuration (SysConfig)

Enabling Extended Structure

  • DynamicFieldDB::ExtendedValueStructure Enables or disables the extended display structure for database fields.

Defining Headers

  • DynamicFieldDB::DisplayFieldHeaders Define a list of grouping headers. These will appear as options in the dropdown of the admin dynamic fields.

  • The header General is automatically added, even if it is not included in the list.

Module Registrations

Add the following keys in SysConfig to enable the frontend module:

SysConfig PathPurpose
Frontend::Agent::ModuleRegistration::Loader::Loader::Module::AgentTicketZoom###003-DynamicFieldDatabaseExtensionsDisplays extension in Agent Ticket Zoom
Frontend::Customer::ModuleRegistration::Loader::Loader::Module::CustomerTicketZoom###003-DynamicFieldDatabaseExtensionsDisplays extension in Customer Ticket Zoom

Usage

  1. Admin → Settings → Dynamic Fields → Edit Database Field
  • In the editing dialog, a "Display Header" dropdown is now available.
  1. Select Value Groups
  • Choose the appropriate header from the dropdown to logically group entries.
  1. Display in Agent and Customer Interface
  • The headers will be inserted into the ticket widgets, clearly grouping the displayed values.

Limitations

  • The function only accesses fields of type Database (DB).
  • A subsequent change to header pairings does not automatically affect existing values.

Support & Further Information