Source string Read only

type: Content of: <section><section><example><para><itemizedlist><listitem><para><informaltable><tbody><tr><td>
26/260
Context English State
Remember, if more settings are added in a new XML each setting name needs to be unique in the system and different than "PreferencesGroups###DynamicField". For example: PreferencesGroups###101-DynamicField-Field1, PreferencesGroups###102-DynamicField-Field2, PreferencesGroups###My-Field1, PreferencesGroups###My-Field2, etc.
Activate Field1 in the User preferences.
<emphasis>Sub-group:</emphasis> Frontend::Agent::Preferences
<emphasis>Setting:</emphasis> PreferencesGroups###101-DynamicField-Field1
<literal>Active</literal>
<literal>Block</literal>
Input
<literal>Column</literal>
Other Settings
<literal>Data</literal>
[% Env("UserDynamicField_Field1") %]
<literal>Key</literal>
<literal>Label</literal>
Default value for: My Field 1
Kernel::Output::HTML::PreferencesGeneric
<literal>PrefKey</literal>
UserDynamicField_Field1
<literal>Prio</literal>
7000
Field1 in User preferences screen
<graphic fileref="screenshots/administration/dynamicfields/dynamicfields-userpreferences.png" scalefit="1" width="100%" contentdepth="100%"></graphic>
A dynamic field is a special kind of field in OTRS, created to extend the information stored on a ticket or article. These fields are not fixed in the system and they can appear only in specific screens, they can be mandatory or not, and their representation in the screens depends on the field type defined at their creation time according to the data to be held by the field. For example, there are fields to hold a text, a date, a selection of items, etc.
Dynamic fields are the evolution of TicketFreeText, TicketFreeKey, TicketFreeTime, ArticleFreeText and ArticleFreeKey fields that where commonly used in OTRS 3.0 and before. The limitation of these "Free Fields" was that they can be defined up to 16 (text or dropdown) fields and 6 time fields for a ticket and 3 (text or dropdown) fields for each article only, not more.
Now with dynamic fields the limitation in the number of fields per ticket or article is removed, you can create as many dynamic fields you like either for ticket or articles. And beyond that, the framework behind the dynamic fields is prepared to handle custom fields for other objects rather than just ticket and articles.
This new framework that handles the dynamic fields is build using a modular approach, where each kind of dynamic field can be seen as a plug-in module for the framework. This means that the variety of dynamic fields can be easily extended by public OTRS modules, OTRS Feature Add-ons, OTRS custom developments, and other custom developments.
The following dynamic field types are included with this release:
Text (one line of text)
Textarea (multiple lines of text)
Dropdown (single choice, multiple values)
Multiselect (multiple choice, multiple values)
Backing Up the System

Loading…

User avatar None

New source string

OTRS 6 / Administration ManualEnglish

New source string a year ago
Browse all component changes

Things to check

Multiple failing checks

The translations in several languages have failing checks

Reset

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
type: Content of: <section><section><example><para><itemizedlist><listitem><para><informaltable><tbody><tr><td>
Flags
read-only
Source string location
en/content/administration/dynamicfields-configuration.xml:1311
String age
a year ago
Source string age
a year ago
Translation file
i18n/doc-admin.pot, string 2247