Dynamic Fields

General Dynamic Field Settings

These settings are the same for all types of dynamic fields.

Name *

The name of this resource. Any type of characters can be entered to this field including uppercase letters and spaces. The name will be displayed in the overview table.

Label *

This is the name to be shown on the screens where the field is active.

See also

It is possible to add translations for a dynamic field label. Label translations have to be added manually to language translation files.

Field order *

This is the order in which the field is displayed on the screens where it is active.

Note

The configured value for the field order is considered in the following screens:

• all screens in the administrator interface

• all screens in the external interface

• Business Process Information widget in the agent interface

In other screens the order can be configured in other ways, e.g. via a specific order of fields in the form configuration.

Validity *

Set the validity of this resource. Each resource can be used in OTRS only, if this field is set to valid. Setting this field to invalid or invalid-temporarily will disable the use of the resource.

Field type

This type have been selected in the previous page and can not be changed here anymore. This is a read-only field.

Object type

This type have been selected in the previous page and can not be changed here anymore. This is a read-only field.

Note

The object type determines where the dynamic field can be used. For example dynamic field with object type Ticket can be used only in tickets, and can not be used in articles.

The following settings are relevant only for the particular type of dynamic fields.

Calculation Dynamic Field Settings

Note

To be able to use dynamic field calculation in OTRS, you have to enable it first.

Calculation dynamic field is used to perform simple mathematical operations.

Calculation formula

This setting is used to add a calculation formula. Simple mathematical operations are possible. The default value is zero.

Numbers in the formula should have dot as decimal separator and should be used without thousands separator like 123456.78.

Checkbox Dynamic Field Settings

Checkbox dynamic field is used to store true or false value.

Default value *

The default value for the checkbox.

Checked

The checkbox is checked by default.

Unchecked

The checkbox is unchecked by default.

Contact With Data Dynamic Field Settings

This dynamic field allows to add contacts with data to tickets.

Name Field *

The attribute Name is always mandatory and it is not automatically added, so for each new data source this attribute must be added manually. Within the data source definition (or dynamic field configuration) this must be represented by the key Name and the value could be Name for example.

ValidID Field *

The attribute ValidID is always mandatory and it is not automatically added, so for each new data source this attribute must be added manually. Within the data source definition (or dynamic field configuration) this must be represented by the key ValidID and the value could be Validity for example.

Other Fields

These are the possible data attributes for contacts. Clicking on the ⊞ button of the Add Fields will add two new fields, where a Key (internal value) and a Value (displayed value) can be set. With the button you can add multiple key-value pairs.

Warning

The keys Name and ValidID are already used by Name Field and ValidID Field. Do not use these keys again!

Add Fields

Use this button to add more fields to dynamic field.

Mandatory fields

Comma separated list of mandatory keys.

Note

Keys Name and ValidID are always mandatory and doesn’t have to be listed here.

Sorted fields

Comma separated list of keys in sort order. Keys listed here come first, all remaining fields afterwards and sorted alphabetically.

Searchable fields

Comma separated list of searchable keys.

Note

Key Name is always searchable and doesn’t have to be listed here.

When the dynamic field was saved, click on the name of the newly created dynamic field in the overview table. The Edit Dynamic Field screen will open. There is a button Add or edit contacts, that points to Tickets → Edit contacts with data to add some data.

To add a new contact with data:

1. Select a dynamic field from the drop-down list in Actions widget of the left sidebar.

2. Click on the Add contact with data button in the left sidebar.

3. Fill in the required fields.

4. Click on the Save button.

To edit a contact with data:

1. Click on a contact with data in the list of contact with data entries.

2. Modify the fields.

3. Click on the Save or Save and finish button.

The usage of this type of dynamic field is more complex then the others. An exemplary usage of contacts with data is as follows:

1. Create a new dynamic field of type contact with data.

2. Set the possible contact attributes (possible values).

   • Type Name into Name Field.

   • Type Validity into ValidID Field.

   • Add any other attribute with Add Fields button such as Telephone attribute (key: Telephone, value: Phone).

3. Add the list of mandatory attribute keys comma separated (Name and ValidID are not needed).

4. Set the attribute key order list comma separated as: Name,Telephone,ValidID.

5. Add the list of searchable attribute keys comma separated (Name is not needed).

6. Populate the data source by adding at least one contact in the newly created data source by using Manage Contacts with Data screen from the main menu of the agent interface.

7. Add the new dynamic field to the screen’s configuration where it should be shown. For example in New Phone Ticket screen by updating the system configuration setting Forms###AgentFrontend::TicketCreate::Phone::CreateProperties and do the same for AgentFrontend::TicketDetailView::WidgetType###Properties.

   See also

   See Display Dynamic Fields on Screens for more information.

8. Go to New Phone Ticket screen, and notice that the new field is there. Add all needed information to the ticket.

9. Select an existing contact using autocomplete and choosing a contact.

10. Click on the Create button to create the ticket and go to the ticket detail view.

11. Open the widget configuration of the Properties widget in the ticket detail view, and enable the dynamic field in the Hide/Show Properties list.

12. The assigned contact and its attributes will be shown in the ticket detail view.

13. It is possible to update the attributes of the contact by clicking the Edit contact button that appears in the right side of dynamic field property card (if the current user is a member of the groups defined in system configuration setting Frontend::Module###AdminDynamicFieldContactWithData).

14. If is necessary to change the contact for this ticket, it can be done via any other ticket action where the dynamic field is configured for display.

Customer Dynamic Field Settings

Customer dynamic field is used to store customer data from integrated external customer databases as contacts in a ticket.

Input type *

Defines whether the dynamic field should be able to store a Single contact or Multiple contacts.

Navigation on external interface *

Defines whether or not a new navigation entry in the external interface should be shown. This navigation entry will only be shown to customer users that are stored in one of the Customer fields. The label of this entry can be defined in the setting Navigation label if this setting is saved with yes.

Navigation label

This configuration makes it possible to define a custom label for the navigation entry displayed in the external interface. If no value is configured, a default combination of the field label and Tickets will be used, for example Contacts Tickets.

Use for communication *

If customer users stored in a dynamic field of type Customer should get used for communication, this configuration has to be used. It is possible to use customer users for the To, Cc and Bcc field. If this configuration is active, the customer user will be added to the configured field. If the field is already containing the address of the customer user, it will not get added a second time. The agent still has the opportunity to remove the address from the field when composing a new message.

Use for notification *

If customer users stored in a dynamic field of type Customer should get used for notification, this configuration has to be used. It is possible to use customer users for the To, Cc and Bcc recipient. If this configuration is active, the dynamic field will be shown in the recipient block of the ticket notifications.

Note

If the configuration option UserForNotification is not set in the dynamic field table, the fallback recipient will be used. The fallback recipient is the To recipient.

Filter contact by *

In some scenarios it is necessary to filter possible contacts by their attributes. A filter for example could be the customer number, the city or a custom attribute. To activate the filter functionality, select the needed attribute from the drop-down list. If the customer number is selected, the contact will be filtered by the customer number of the customer of the ticket. For each other attribute the filter can be defined as a text value. After selecting the filter attribute from the drop-down list, a second input field will be displayed where the filter can be defined.

Filter criteria *

In this field the filter of the attributes for the customer result is defined. For example, if only customer users with the first name Theo should be selectable, the filter Fistname from the Filter contact by has to be selected. After that the Filter criteria field will be displayed. Now we can insert Theo into the filter field. Currently it is not possible to define a regular expression or a placeholder for filtering customer users.

After the dynamic field of the type Customer was configured and added to the different views, the functionality can get used. The contact fields will be displayed below the recipients for new tickets or otherwise in the dynamic fields block of the page. The exact position and label of the field depends on the field configuration.

If a customer number filter was configured the dynamic field will be locked and unchangeable as long as no customer is added to the ticket.

After inserting at least one character into the text field of the dynamic field a search over the configured customer databases starts. At this point the configured filter takes it place and removes unmatched customer users from the result set. To start a search for all available customer users for this field you can use the * wildcard.

If a field has been configured to use the contacts for communication and the Reply via Email or Reply to All via Email actions are used in the ticket detail view, all customer users stored in the respective field will be added to the configured recipient list (to, cc or bcc) unless they exist as a recipient already.

To allow searching of the Customer dynamic field values after the data was stored to the ticket the search view has to be configured accordingly.

The search works equals to the search for regular customer users. The login name of the customer user has to be used as search criteria.

Database Dynamic Field Settings

Database dynamic field is used to store data from external databases in tickets.

Before an external database can be searched and the results be saved at the ticket through the dynamic field, the credentials have to be stored in the configuration of the dynamic field.

Possible values

The possible values will fill up the Identifier field below automatically, which defines the value that will be stored in the dynamic field. Possible values can be created as much as needed (or at least as many table columns as the database table has). The possible values defines the database columns to search in. It is possible to set the column name, a description (label) the field should have, the needed data type and if the field should be a search or list field.

Name *

The exact name of the database column which will be requested through the database queries.

Label *

The label of the field which will be displayed in the detailed search.

Datatype *

The data type which will be stored in the dynamic field. Possible values: Date, Integer or Text.

Filter

With the filter field, it is possible to choose a ticket attribute or a dynamic field as a filter for the related column. If the dynamic field is bound to a related ticket, the attributes will be used for the filter mechanism, otherwise the filters will be ignored. If the filter will be configured to a table column, only search results matching to the search term and the related ticket attribute on exactly the configured column will be displayed.

Searchfield

Indicates if a field should be included in the search requests.

Listfield

Indicates if a field should be displayed in the results.

Add value

Click on the + icon to add a new section to Possible values.

Show link

Here you can specify an optional HTTP link for the field value displayed in overviews and detail views. Examples:

• The value of dynamic field named Field1 is part of the link:

  https://some.example.com/handle?query=[% Data.Field1 | uri %]
  

• The value of dynamic field named Field1 is the complete link with and without protocol:

  [% Data.Field1 %]
  https://[% Data.Field1 %]
  

• The value of dynamic field named 100Field needs special handling, because the name of the dynamic field starts with a number:

  https://some.example.com/handle?query=[% Data.item("100Field") | uri %]
  

If special characters (&, @, :, /, etc.) should not be encoded, use url instead of uri filter.

Link for preview

If filled in, this URL will be used for a preview which is shown when this link is hovered in ticket detail view. Please note that for this to work, the regular URL field above needs to be filled in, too.

Type *

The type of the desired database can be selected here. The following database types are supported: MySQL, Oracle, PostgreSQL or MSSQL.

SID

This option is only available for Oracle connections and will be shown or hidden automatically. Within this option you have to enter the SID of your Oracle connection.

Driver

This option is only available for ODBC connections and will be shown or hidden automatically. Within this option you have to enter in the host system previously configured ODBC driver to connect to the desired MSSQL database.

Server *

The database host (host name or IP address).

Port

The port of the database server.

Database *

Defines the desired target database of the DBMS. This database will be used for queries.

Table/View *

This table or view will be used for the queries.

User *

The username for the database connection.

Password *

The user password for the database connection.

Identifier *

This select box will be automatically filled through Possible values. This field represents the value which will be stored in the dynamic field. Must be unique column from the table entered in Table/View.

Multiselect

If this field is selected, it will be possible to store more than one value to the dynamic field. Those values will be stored comma separated.

Cache TTL

This value defines the period of validity of the database cache in seconds. Equal queries to the database will be answered through the cache (local file system) within this period instead of asking the database again.

Search Prefix

This value will be put in the front of every search term while using the auto-completion to search the database. Wildcard characters are supported as well. The search prefix will be ignored during the detailed search, but it is still possible to use wildcard characters in those masks.

Search Suffix

This value will be put in the end of every search term while using the auto-completion to search the database. Wildcard characters are supported as well. The search suffix will be ignored during the detailed search, but it is still possible to use wildcard characters in those masks.

Result Limit

The entered integer value defines the maximum amount of allowed results during a database search. This includes the auto-completion search as well as the detailed search.

Case Sensitive

If this field is selected, case-sensitivity will take effect on searches.

Date Dynamic Field Settings

Date dynamic field is used to store a date value.

Default date difference

The difference from now (in seconds) to calculate the field default value (e.g. 3600 or -60).

Define years period

Activate this feature to define a fixed range of years (in the future and in the past) to be displayed on the year part of the field. If set to Yes the following options will be available:

Years in the past

Define the number of years in the past from the current day to display in the year selection for this dynamic field in edit screens.

Years in the future

Define the number of years in the future from the current day to display in the year selection for this dynamic field in edit screens.

Note

If no years period is specified, the system uses the default value for the period: 10 years (5 years in the past and 5 years in the future).

Show link

Here you can specify an optional HTTP link for the field value displayed in overviews and detail views. Examples:

• The value of dynamic field named Field1 is part of the link:

  https://some.example.com/handle?query=[% Data.Field1 | uri %]
  

• The value of dynamic field named Field1 is the complete link with and without protocol:

  [% Data.Field1 | uri %]
  https://[% Data.Field1 | uri %]
  

• The value of dynamic field named 100Field needs special handling, because the name of the dynamic field starts with a number:

  https://some.example.com/handle?query=[% Data.item("100Field") | uri %]
  

• The value of dynamic field named Field1 contains the link, the value of dynamic field named Field2 contains an important value for a parameter:

  https://[% Data.Field1 | uri %]?query=[% Data.DynamicField_Field2 | uri %]
  

If special characters (&, @, :, /, etc.) should not be encoded, use url instead of uri filter.

Link for preview

If filled in, this URL will be used for a preview which is shown when this link is hovered in ticket detail view. Please note that for this to work, the regular URL field above needs to be filled in, too.

See also

The URL has to be added to the allowed origins. Read the External Link Previews chapter for more information.

Restrict entering of dates

Here you can restrict the entering of dates of tickets.

Prevent entry of dates in the future

Selecting this option will prevent entering a date that is after the current date.

Prevent entry of dates in the past

Selecting this option will prevent entering a date that is before the current date.

Date / Time Dynamic Field Settings

Date / time dynamic field is used to store a date time value.

The settings for this type of dynamic field is the same as for date dynamic field.

Dropdown Dynamic Field Settings

Drop-down dynamic field is used to store a single value, from a closed list.

Possible values

These are the possible data attributes for contacts. Clicking on the ⊞ button will add two new fields, where a key (internal value) and a value (displayed value) can be set. With the button you can add multiple key-value pairs.

Warning

The maximum number of 100 values should not be exceeded. Exceeding this limit may affect the system performance.

Default value

This is the default value for this field and this will be shown on the edit screens.

Add empty value

If this option is activated an extra value is defined to show as a – in the list of possible values. This special value is empty internally.

Tree View

Activate this option to display values as a tree. If you use a sub-value, specify it as Parent::Sub.

Translatable values

If you activate this option the values will be translated to the user defined language.

Note

You need to add the translations manually into the language translation files.

Show link

Here you can specify an optional HTTP link for the field value displayed in overviews and detail views. Examples:

• The value of dynamic field named Field1 is part of the link:

  https://some.example.com/handle?query=[% Data.Field1 | uri %]
  

• The value of dynamic field named Field1 is the complete link with and without protocol:

  [% Data.Field1 | uri %]
  https://[% Data.Field1 | uri %]
  

• The value of dynamic field named 100Field needs special handling, because the name of the dynamic field starts with a number:

  https://some.example.com/handle?query=[% Data.item("100Field") | uri %]
  

• The value of dynamic field named Field1 contains the link, the value of dynamic field named Field2 contains an important value for a parameter:

  https://[% Data.Field1 | uri %]?query=[% Data.DynamicField_Field2 | uri %]
  

If special characters (&, @, :, /, etc.) should not be encoded, use url instead of uri filter.

Link for preview

If filled in, this URL will be used for a preview which is shown when this link is hovered in ticket detail view. Please note that for this to work, the regular URL field above needs to be filled in, too.

See also

The URL has to be added to the allowed origins. Read the External Link Previews chapter for more information.

Multiselect Dynamic Field Settings

Possible values

These are the possible data attributes for contacts. Clicking on the ⊞ button will add two new fields, where a key (internal value) and a value (displayed value) can be set. With the button you can add multiple key-value pairs.

Warning

The maximum number of 100 values should not be exceeded. Exceeding this limit may affect the system performance.

Default value

This is the default value for this field and this will be shown on the edit screens.

Add empty value

If this option is activated an extra value is defined to show as a – in the list of possible values. This special value is empty internally.

Tree View

Activate this option to display values as a tree. If you use a sub-value, specify it as Parent::Sub.

Translatable values

If you activate this option the values will be translated to the user defined language.

Note

You need to add the translations manually into the language translation files.

Number Dynamic Field Settings

Dynamic fields of type number are used to store integers and floating point numbers (float).

Type

Select the type of the number. Possible values: Float or Integer.

Decimal places

Determines the amount of digits to be shown after the decimal separator.

This setting is only available if Float is selected in the Type field.

Step by *

Determines the step value which is used in increase or decrease.

Default value

This is the default value for this field and this will be shown on the edit screens.

Show link

Here you can specify an optional HTTP link for the field value displayed in overviews and detail views. Examples:

• The value of dynamic field named Field1 is part of the link:

  https://some.example.com/handle?query=[% Data.Field1 | uri %]
  

• The value of dynamic field named Field1 is the complete link with and without protocol:

  [% Data.Field1 | uri %]
  https://[% Data.Field1 | uri %]
  

• The value of dynamic field named 100Field needs special handling, because the name of the dynamic field starts with a number:

  https://some.example.com/handle?query=[% Data.item("100Field") | uri %]
  

• The value of dynamic field named Field1 contains the link, the value of dynamic field named Field2 contains an important value for a parameter:

  https://[% Data.Field1 | uri %]?query=[% Data.DynamicField_Field2 | uri %]
  

If special characters (&, @, :, /, etc.) should not be encoded, use url instead of uri filter.

Link for preview

If filled in, this URL will be used for a preview which is shown when this link is hovered in ticket detail view. Please note that for this to work, the regular URL field above needs to be filled in, too.

See also

The URL has to be added to the allowed origins. Read the External Link Previews chapter for more information.

Text Dynamic Field Settings

Text dynamic field is used to store a single line string.

Default value

This is the default value for this field and this will be shown on the edit screens.

Show link

Here you can specify an optional HTTP link for the field value displayed in overviews and detail views. Examples:

• The value of dynamic field named Field1 is part of the link:

  https://some.example.com/handle?query=[% Data.Field1 | uri %]
  

• The value of dynamic field named Field1 is the complete link with and without protocol:

  [% Data.Field1 | uri %]
  https://[% Data.Field1 | uri %]
  

• The value of dynamic field named 100Field needs special handling, because the name of the dynamic field starts with a number:

  https://some.example.com/handle?query=[% Data.item("100Field") | uri %]
  

• The value of dynamic field named Field1 contains the link, the value of dynamic field named Field2 contains an important value for a parameter:

  https://[% Data.Field1 | uri %]?query=[% Data.DynamicField_Field2 | uri %]
  

If special characters (&, @, :, /, etc.) should not be encoded, use url instead of uri filter.

Link for preview

If filled in, this URL will be used for a preview which is shown when this link is hovered in ticket detail view. Please note that for this to work, the regular URL field above needs to be filled in, too.

See also

The URL has to be added to the allowed origins. Read the External Link Previews chapter for more information.

Check RegEx

Here you can specify a regular expression to check the value. The regex will be executed with the modifiers xms. Example:

^[0-9]$

Add RegEx

Clicking on the ⊞ button will add two new fields, where a regular expression and an error message can be added.

Textarea Dynamic Field Settings

Textarea dynamic field is used to store a multiple line string.

Number of rows

The height (in lines) for this field in the edit mode.

Number of cols

The width (in characters) for this field in the edit mode.

Default value

This is the default value for this field and this will be shown on the edit screens.

Check RegEx

Here you can specify a regular expression to check the value. The regex will be executed with the modifiers xms. Example:

^[0-9]$

Add RegEx

Clicking on the ⊞ button will add two new fields, where a regular expression and an error message can be added.

Web Service Dynamic Field Settings

Dynamic field of type web service is used to store data from external systems for tickets.

It is necessary to have an already working web service before creating a new dynamic field. The dynamic field gathers its selectable options from an external system using a web service.

The response from the external system defines the possible options to be displayed, and they could vary depending on the data that is sent in the request. Normally when a field is changed in a screen (e. g. the ticket priority in the New Phone Ticket screen) the values of other fields could be updated. That is the case with this type of dynamic fields, as they could also include all screen field values in the request and the remote server could potentially return completely different values depending on input.

Additionally if the dynamic field source object already exists (e. g. a ticket, and the field is set in the Change Free Fields action), the details of the already created ticket are also included in the request.

Web service *

The configured web service whose invokers will be to triggered when a dynamic field is displayed.

Invoker *

The invoker that is used to send requests to external systems. Within this field, just invokers of type Generic::PassThrough will be displayed.

Multiselect

A drop-down menu to determine if the displayed dynamic field should act as a multiselect field instead of a drop-down field.

Cache TTL

A cache time to live value, that contains a value (in minutes). If the value is 0 or empty, no caching will be active. This cache is to prevent unnecessary requests to the remote server using the same values.

Add empty value

Defines if it is possible to save an empty value in the field.

Tree View

This option activates the tree view of possible values, if they are supplied in the correct format.

Translatable values

If you activate this option the values will be translated to the user defined language.

Note

You need to add the translations manually into the language translation files.

Show link

Here you can specify an optional HTTP link for the field value displayed in overviews and detail views. Optional HTTP link works only for single-select fields. Examples:

• The value of dynamic field named Field1 is part of the link:

  https://some.example.com/handle?query=[% Data.Field1 | uri %]
  

• The value of dynamic field named Field1 is the complete link with and without protocol:

  [% Data.Field1 %]
  https://[% Data.Field1 %]
  

• The value of dynamic field named 100Field needs special handling, because the name of the dynamic field starts with a number:

  https://some.example.com/handle?query=[% Data.item("100Field") | uri %]
  

If special characters (&, @, :, /, etc.) should not be encoded, use url instead of uri filter.

Link for preview

If filled in, this URL will be used for a preview which is shown when this link is hovered in ticket detail view. Please note that for this to work, the regular URL field above needs to be filled in, too.

Dynamic Field in Business Object Detail View

Dynamic fields can be added to any widget of the business object detail view. The following examples show the possibilities.

To add a ticket dynamic field to the Properties widget:

1. Go to the System Configuration screen.

2. Search for the setting AgentFrontend::TicketDetailView::WidgetType###Properties.

3. Add the ticket dynamic field to the Properties section of the YAML configuration.

   Properties:
   - Name: DynamicField_Test1
     IsVisible: 1
   

   

   See also

   Detailed information about the configuration of the property card and possible keys can be found under the reference.

4. Deploy the modified system configuration.

5. Go to the ticket detail view screen in the agent interface.

6. Find the Properties widget and open its configuration via the gear icon. Identify the Test1 dynamic field property in the Hide/Show Properties list. Activate it by clicking on the checkbox. Click on the Save button to apply the change and close the widget configuration.

   

If defined, the ticket dynamic field value will then be displayed as a separate property card.

To add an article dynamic field to the Communication Stream widget:

1. Go to the System Configuration screen.

2. Search for the setting AgentFrontend::TicketDetailView::WidgetType###CommunicationStream.

3. Add the article dynamic field name to the ArticleDynamicFields array of the YAML configuration.

   ArticleDynamicFields:
   - Test1
   

   

4. Deploy the modified system configuration.

If defined, the article dynamic field value will then be displayed as a separate line in the article header in the Communication Stream widget. If not visible, make sure the header is expanded by clicking on it.

To add a ticket dynamic field to the Business Process Information widget:

1. Go to the System Configuration screen.

2. Search for the setting AgentFrontend::TicketDetailView::Widget::BusinessProcessInformation###DynamicField.

3. Add the dynamic field to the list and enabled it.

   

4. Deploy the modified system configuration.

If defined, the ticket dynamic field value will then be displayed as a separate property card in the Business Process Information widget of a process ticket.

Dynamic Field in Ticket and Article Action

The following example shows how to add a dynamic field to the Close Ticket action. The steps are identical for other actions, only the system configuration keys are different for each form.

To add a ticket or an article dynamic field to the Close Ticket form:

1. Go to the System Configuration screen.

2. Search for the setting Forms###AgentFrontend::Ticket::Action::Close.

3. Add the dynamic field to the Fields section of the YAML configuration.

   Fields:
   - Name: DynamicField_Test1
   

   

4. Deploy the modified system configuration.

The ticket dynamic field will be displayed in the relevant ticket or article action as a form field.

Dynamic Field in Business Object List

The following examples show how to add a dynamic field as a column or as a filter to the organizer item type Ticket List. This affects all organizer items of the type Ticket List. If only a specific organizer item needs to be affected, then please modify the system configuration key of the relevant organizer item.

To add a ticket dynamic field as a list column:

1. Go to the System Configuration screen.

2. Search for the setting Agent::Organizer::ItemType###TicketList.

3. Add the ticket dynamic field to the Columns section of the YAML configuration.

   Columns:
     DynamicField_Test1:
       IsVisible: 2
   

   

   See also

   For detailed information about the column configuration and possible keys, please check the reference.

4. Deploy the modified system configuration.

If defined, the ticket dynamic field value will then be displayed in a column cell, for any of the organizer items of the ticket list type.

To add a ticket dynamic field as a list filter:

1. Go to the System Configuration screen.

2. Search for the setting Agent::Organizer::ItemType###TicketList.

3. Add the ticket dynamic field name to the AvailableDynamicFieldFilters array of the YAML configuration.

   AvailableDynamicFieldFilters:
   - Test1
   

   

4. Deploy the modified system configuration.

The ticket dynamic field can now be used as a filter in the business object list.

Dynamic Field in Ticket Create Screen

To add a ticket or an article dynamic field to New Email Ticket screen:

1. Go to the System Configuration screen.

2. Search for the setting Forms###AgentFrontend::TicketCreate::Email::CreateProperties.

3. Add the ticket dynamic field to the Fields section of the YAML configuration.

   Fields:
   - Name: DynamicField_Test1
   

   

   See also

   For more information about form fields and groups, please consult the Forms chapter.

4. Deploy the modified system configuration.

The ticket or article dynamic field can now be used as part of the New Email Ticket screen.

Dynamic Field in Ticket Bulk Action

To add a ticket or an article dynamic field to a ticket bulk action:

1. Go to the System Configuration screen.

2. Search for the setting AgentFrontend::Ticket::BulkFeature::Attributes###DynamicField.

3. Add the dynamic field to the list and enabled it.

   

4. Deploy the modified system configuration.

The ticket or article dynamic field is now displayed in the Properties section in the action form of the bulk action.

Dynamic Field in the Print Output

To add a ticket or an article dynamic field to the print output:

1. Go to the System Configuration screen.

2. Search for the setting AgentFrontend::Ticket::Print###DynamicField.

3. Add the dynamic field to the list and enabled it.

   

4. Deploy the modified system configuration.

The ticket or article dynamic field is now displayed in the printed output of the ticket.

Dynamic Field in External Interface

To add a dynamic field to the external interface:

1. Go to System Configuration screen.

2. Navigate to Frontend → External → View in the navigation tree.

3. Select the screen where the dynamic field should be displayed.

4. Search for the dynamic field setting of the screen and click on the Edit this setting button.

   The following settings are relevant to adding dynamic fields:

   - ExternalFrontend::KnowledgeBaseDetailView###DynamicField
   - ExternalFrontend::TicketCreate###DynamicField
   - ExternalFrontend::TicketDetailView###DynamicField
   - ExternalFrontend::TicketDetailView###FollowUpDynamicField
   - ExternalFrontend::TicketOverview###DynamicField
   

5. Click on the + button to add the dynamic field. The key is the name of the dynamic field, the value is 1 – Enabled. This setting is used to display the content of dynamic field in the selected screen.

6. Search for setting ExternalFrontend::TicketDetailView###FollowUpDynamicField and click on the Edit this setting button.

7. Click on the + button to add the dynamic field. The key is the name of the dynamic field, the value is 1 – Enabled. This setting is used to configure dynamic fields in the answer part of customers detail view.

8. Repeat the steps for other views, if needed.

9. Deploy the modified settings.