Source string Read only

type: Content of: <section><section><section><para><example><para><itemizedlist><listitem><para><informaltable><tbody><tr><td>
Context English State
You can also search for "DynamicField" in the search box above or the "sysconfig" key directly if you already know it.
Locate the setting sub-group for the screen that you are looking for and click on it. For example "Frontend::Agent::Ticket::ViewPhoneNew".
Search for the setting that ends with "###DynamicField". For example "Ticket::Frontend::AgentTicketPhone###DynamicField".
If the setting is empty or does not have the required dynamic field name, click on the "+" button to add a new entry. For example Key: Field1, Content: 1.
If the setting already has the dynamic field name listed be sure that is set to "1" to display the field or to "2" to display it as mandatory.
Save the configuration by clicking on the "Update" button at the bottom of the screen and navigate to the screen where you want the field to be displayed.
Show Examples
The following are "sysconfig" configurations examples to show or hide dynamic fields on different screens.
Activate Field1 in New Phone Ticket Screen.
<emphasis>Group:</emphasis> Ticket
<emphasis>Sub-group:</emphasis> Frontend::Agent::Ticket::ViewPhoneNew
<emphasis>Setting:</emphasis> Ticket::Frontend::AgentTicketPhone###DynamicField
Field1 in New Phone Ticket Screen
<graphic fileref="screenshots/administration/dynamicfields/dynamicfields-agentticketphone-field1.png" scalefit="1" width="100%" contentdepth="100%"></graphic>
Activate Field1 in New Phone Ticket Screen as mandatory.
Field1 in New Phone Ticket Screen as mandatory
<graphic fileref="screenshots/administration/dynamicfields/dynamicfields-agentticketphone-field1-mandatory.png" scalefit="1" width="100%" contentdepth="100%"></graphic>
Activate several fields in New Phone Ticket Screen.
Several fields in New Phone Ticket Screen as mandatory
<graphic fileref="screenshots/administration/dynamicfields/dynamicfields-agentticketphone-allfields.png" scalefit="1" width="100%" contentdepth="100%"></graphic>


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



English English
No related strings found in the glossary.

Source information

Source string comment
type: Content of: <section><section><section><para><example><para><itemizedlist><listitem><para><informaltable><tbody><tr><td>
Source string location
en/content/administration/dynamicfields-configuration.xml:779 en/content/administration/dynamicfields-configuration.xml:835 en/content/administration/dynamicfields-configuration.xml:891 en/content/administration/dynamicfields-configuration.xml:971 en/content/administration/dynamicfields-configuration.xml:1051 en/content/administration/dynamicfields-configuration.xml:1107
String age
a year ago
Source string age
a year ago
Translation file
i18n/doc-admin.pot, string 2185