Translation

type: Content of: <section><section><section><title>
Configuration
12/130
Context English Russian State
All OTRS configuration files are stored in the directory <filename>Kernel</filename> and in its subdirectories. There is no need to manually change any other file than <filename>Kernel/Config.pm</filename>, because the rest of the files will be changed when the system gets updated. Just copy the configuration parameters from other files into <filename>Kernel/Config.pm</filename> and change them as per your needs. This file will never be touched during the update process, so your manual changes are safe.
The configuration can be rebuilt either manually by executing <literal>perl bin/otrs.Console.pl Maint::Config::Rebuild</literal> or automatically by the installer, package operations (install, update, reinstall and uninstall), etc. All <filename>.xml</filename> files located in <filename>Kernel/Config/Files/XML/</filename> are parsed and their content is transferred to the OTRS database. Most of the <filename>.xml</filename> files which are part of this directory by default belong to OTRS Free, but OTRS Free Features such as FAQ or Survey (or any other OTRS extension) will add their own configuration files to this directory as well.
To apply any sort of changes to the configuration, it is necessary to deploy them. The deployment process will extract all settings and the according values from the OTRS database, convert them to a format that OTRS can understand naturally and put them into <filename>Kernel/Config/Files/ZZZAAuto.pm</filename>.
If the OTRS web interface is accessed, the settings contained in the files <filename>Kernel/Config/Files/ZZZAAuto.pm</filename>, <filename>Kernel/Config/Files/ZZZACL.pm</filename> (if existing), <filename>Kernel/Config/Files/ZZZProcessManagement.pm</filename> (if existing) and any other custom <filename>.pm</filename> file will be evaluated alphabetically. These files are used by the graphical user interface for caching purposes and should never be changed manually. Lastly, the file <filename>Kernel/Config.pm</filename> that contains your individual settings and manually changed configuration parameters will be parsed. Reading the configuration files in this order makes sure that your specific configuration settings are considered correctly by the system.
Configuring the System Through the Web Interface
The graphical interface for system configuration Графический интерфейс для настройки системы
OTRS Free currently brings more than 1700 configuration settings, and there are different ways to quickly access a specific one. With the full text search, all configuration settings can be scanned for one or more keywords. The full text search not only searches through the names of the configuration settings, but also the descriptions and values. This allows an element to be found easily even if its name is unknown.
Furthermore, each configuration setting is classified by a category and a navigation group. Navigation groups are individual elements in the main navigation tree. By selecting one of these navigation entries, all settings assigned to the selected group will be shown. As long as no extensions are installed, the category selection is automatically hidden, but as soon as a package is installed which brings its own configuration settings (such as FAQ or Survey), the category selection will be revealed. Selecting a category makes the main navigation tree show only the navigation groups belonging to the selected category.
All configuration settings are shown as read only by default. To edit a setting, click the <emphasis>Edit this setting</emphasis> button that appears on hovering your mouse cursor over a setting. Once edit mode has been entered, changes made to the fields from within the setting can be saved by clicking the <emphasis>Save</emphasis> button on the right (or by hitting the <emphasis>Enter</emphasis> key on your keyboard). If a setting is currently edited by another administrator, it is not possible to get access to the edit mode for that setting until the other administrator finished their work. Editing can be cancelled by clicking the <emphasis>Cancel</emphasis> button on the right or hitting the <emphasis>Escape</emphasis> key on your keyboard. When editing is cancelled, all changes made during the current editing session are discarded.
Clicking the setting name or the menu icon on the top right of each setting will reveal a menu with some more options (e.g. enable/disable a setting, reset a setting values to their defaults, copy a direct link to a setting or add a setting to a list of favorites for quick access).
To bring changes into effect, a deployment has to be started. The system configuration deployment screen shows a list of the settings which are to be deployed. Clicking the arrow icon on the top left of each setting or in the outer <emphasis>Changes Overview</emphasis> box will show a one to one comparison between the settings current state (which is about to be deployed) and the previous (or default) state.
System configuration deployment
<graphic fileref="screenshots/administration/adminarea/admin-systemconfigurationdeployment.png" scalefit="1" width="100%" contentdepth="100%"></graphic>
If you would like to save all the changes you made to your system configuration (for example to quickly set up a new instance) you can use the <emphasis>Export settings</emphasis> button, which will provide a <filename>.yml</filename> file for downloading. To restore your own settings, use <emphasis>Import settings</emphasis> and select the <filename>.yml</filename> file you have created before.
For security reasons, the configuration settings for the database connection cannot be changed in the graphical user interface of the system configuration. These have to be set manually in <filename>Kernel/Config.pm</filename>.
Configuration Конфигурация
By default, a clean installation of OTRS comes with two pre-installed internal dynamic fields, which cannot be removed. If you plan to use such fields in tickets, articles, customer users or customer companies you need to create new, custom dynamic fields.
Please note that dynamic fields for customer users and companies need to be configured accordingly in the CustomerUser and CustomerCompany mapping, usually to find in <filename>Kernel/Config.pm</filename> of your OTRS installation. Examples for configuring them can be found in <filename>Kernel/Config/Defaults.pm</filename>.
The configuration of a dynamic field is split in two parts, to add a new dynamic field or manage an existing one you need to navigate into the "Admin" panel in the "Dynamic Fields" link. To show, show as mandatory or hide a dynamic field in one screen you need to change the OTRS settings in the "SysConfig" screen. Настройка динамических полей разделена на две части. Для создания новых или управления ранее созданными полями перейдите по ссылке "Динамические поля" в Панели Администратора. Для управления показом, обязательностью показа или скрытием полей на конкретных экранах используйте настройки Конфигурации системы/SysConfig для этих экранов.
Adding a Dynamic Field Добавление Динамического Поля
Click on the "Admin" button located in the navigation bar, then click on the "Dynamic Fields" link inside "Ticket Settings" box located in the lower center of the screen. The dynamic fields overview will display as follows:
Dynamic fields overview screen.
<graphic fileref="screenshots/administration/dynamicfields/dynamicfields-overview-empty.png" scalefit="1" width="100%" contentdepth="100%"></graphic> <graphic fileref="screenshots/administration/dynamicfields/dynamicfields-overview-empty.png" scalefit="1" width="100%" contentdepth="100%"></graphic>
Notice that this screen will change as you add more dynamic fields to list all created dynamic fields. This screen might already have some fields if the installation was updated from an older version of OTRS. Обратите внимание, что вид экрана изменится при добавлении динамических полей. Он также может уже иметь несколько полей, если вы провели обновление со старых версий OTRS, в которых динамические поля еще не использовались. Они теперь заменили понятие Свободные/Дополнительные поля/FreeText fields.
The Actions in the side bar at the left of the screen describes four possibilities: Article, Ticket, CustomerUser and CustomerCompany, each one has its own dropdown selection of dynamic fields.
The installation of an OTRS package could add more objects to the Action side bar. Установка некоторых дополнительных пакетов OTRS может привести к добавлению типов объектов в разделе "Действия".
The general procedure to create a dynamic field is: Общая процедура для создания динамического поля:
Click on the desired dynamic field object dropdown in the Actions side bar.
Click on the dynamic field type that you want to add from the list. Выберите в списке и нажмите на тип динамического поля, которое вы хотите добавить.
Fill the configuration. Настройка
Save. Сохранить.
ComponentTranslation
This translation Translated OTRS 6/Administration Manual Конфигурация
The following string has the same context and source.
Translated OTRS 6/((OTRS)) Community Edition Конфигурация

Loading…

User avatar ymyasoedov

Translation changed

OTRS 6 / Administration ManualRussian

Configuration
Настройка СистемыКонфигурация
a year ago
Browse all component changes

Glossary

English Russian
No related strings found in the glossary.

Source information

Source string comment
type: Content of: <section><section><section><title>
Source string location
en/content/administration/dynamicfields-configuration.xml:5 en/content/administration/stats.xml:79
String age
a year ago
Source string age
a year ago
Translation file
i18n/doc-admin.ru.po, string 2038