Translation

type: Content of: <section><section><title>
Reference
6/100
Context English Russian State
$Self->{TicketAcl}->{'102-Second-Example-ACL'} = {
# match properties
Properties => {
# current ticket match properties
Ticket => {
Queue => ['Raw'],
}
},
# return possible options (white list)
Possible => {
# possible ticket options (white list)
Ticket => {
State => ['new', 'open', 'pending reminder'],
},
},
# return also not possible options (black list)
PossibleNot => {
# not possible action options
Action => [ 'AgentTicketClose' ],
},
};
$Self->{TicketAcl}->{'102-Second-Example-ACL'} = {
# match properties
Properties => {
# current ticket match properties
Ticket => {
Queue => ['Raw'],
}
},
# return possible options (white list)
Possible => {
# possible ticket options (white list)
Ticket => {
State => ['new', 'open', 'pending reminder'],
},
},
# return also not possible options (black list)
PossibleNot => {
# not possible action options
Action => [ 'AgentTicketClose' ],
},
};
ACL removing always state closed successful. ACL удаляет навсегда возможность установить состояние "closed successful".
This example shows how it is possible to define negative filters (the state "closed successful" will be removed). You can also see that not defining match properties for a ticket will match any ticket, i. e. the ACL will always be applied. This may be useful if you want to hide certain values by default, and only enable them in special circumstances (e. g. if the agent is in a specific group). Этот пример показывает как можно использовать "негативные" фильтры (состояние "closed successful" будет удалено из списков выбора). Вы также можете видеть, что не заданные условия для "properties" для заявки будет означать, что оно верно для всех заявок, т.е. ACL применяется всегда. Это может быть полезно, если вы желаете скрыть определенные значения по умолчанию и допустить ввод других значений только в заданных обстоятельствах (например, если агент принадлежит определенной группе).
ACL 103-Third-ACL-Example ACL 103-Third-ACL-Example
<graphic fileref="screenshots/customization/acl-state.png" scalefit="1" width="100%" contentdepth="100%"></graphic> <graphic fileref="screenshots/customization/acl-state.png" scalefit="1" width="100%" contentdepth="100%"></graphic>
$Self->{TicketAcl}->{'103-Third-ACL-Example'} = {
# match properties
Properties => {
# current ticket match properties (match always)
},
# return possible options
PossibleNot => {
# possible ticket options
Ticket => {
State => ['closed successful'],
},
},
};
$Self->{TicketAcl}->{'103-Third-ACL-Example'} = {
# match properties
Properties => {
# current ticket match properties (match always)
},
# return possible options
PossibleNot => {
# possible ticket options
Ticket => {
State => ['closed successful'],
},
},
};
ACL only showing Hardware services for tickets that are created in queues that start with &quot;HW&quot;. ACL только отображает Hardware-сервисы для заявок, которые были созданы в очередях, начинающихся с &quot;HW&quot;.
This example also shows you how you can use regular expressions for matching tickets and for filtering the available options. Этот пример также показывает как можно использовать регулярные выражения для сопоставления заявок и фильтрации доступных опций.
ACL 104-Only-Hardware-Services-for-HW-Queues-ACL ACL 104-Only-Hardware-Services-for-HW-Queues-ACL
<graphic fileref="screenshots/customization/acl-new-ticket-service.png" scalefit="1" width="100%" contentdepth="100%"></graphic> <graphic fileref="screenshots/customization/acl-new-ticket-service.png" scalefit="1" width="100%" contentdepth="100%"></graphic>
$Self->{TicketAcl}->{'104-Only-Hardware-Services-for-HW-Queues-ACL'} = {
# match properties
# note we don't have "Ticket => {" because there's no ticket yet
Properties => {
Queue => {
Name => ['[RegExp]^HW'],
}
},
# return possible options
Possible => {
# possible ticket options
Ticket => {
Service => ['[regexp]Hardware'],
},
},
};
$Self->{TicketAcl}->{'104-Only-Hardware-Services-for-HW-Queues-ACL'} = {
# match properties
# note we don't have "Ticket => {" because there's no ticket yet
Properties => {
Queue => {
Name => ['[RegExp]HW'],
}
},
# return possible options
Possible => {
# possible ticket options
Ticket => {
Service => ['[RegExp]^(Hardware)'],
},
},
};
ACL to restrict a Process in the customer frontend using the CustomerID. ACL для ограничения доступа к Процессу в интерфейсе клиента по CustomerID.
ACL 105-Disallow-Process-For-CustomerID ACL 105-Disallow-Process-For-CustomerID - Запретить Процессы для этого CustomerID
<graphic fileref="screenshots/customization/acl-disallow-process-for-customerid.png" scalefit="1" width="100%" contentdepth="100%"></graphic> <graphic fileref="screenshots/customization/acl-disallow-process-for-customerid.png" scalefit="1" width="100%" contentdepth="100%"></graphic>
$Self->{TicketAcl}->{"105-Disallow-Process-For-CustomerID"} = {
'Possible' => {},
'PossibleNot' => {
'Process' => [
'P14'
]
},
'Properties' => {
'CustomerUser' => {
'UserCustomerID' => [
'CustomerID'
]
}
},
'PropertiesDatabase' => {},
'StopAfterMatch' => 0
};
$Self->{TicketAcl}->{"105-Disallow-Process-For-CustomerID"} = {
'Possible' => {},
'PossibleNot' => {
'Process' => [
'P14'
]
},
'Properties' => {
'CustomerUser' => {
'UserCustomerID' => [
'CustomerID'
]
}
},
'PropertiesDatabase' => {},
'StopAfterMatch' => 0
};
Reference Ссылка
In the example below there is a list of all parameters which can be used for ACLs. В нижеприведенном Сценарии представлен список всех параметров, которые могут быть использованы для списка прав доступа (ACLs).
Please see the <link linkend="process-management-acl">section on ACLs</link> in the <link linkend="process-management">ProcessManagement</link> documentation for a detailed description of how to use ACLs for process tickets. Смотрите <link linkend="process-management-acl">секция ACL</link> в <link linkend="process-management">ProcessManagement</link> документации для детального рассмотрения использования ACL для процессных заявок.
Reference showing all possible important ACL settings. Ссылка отображает все возможные важные настройки ACL
# ticket acl
$Self->{TicketAcl}->{'200-ACL-Reference'} = {
# match properties (current values from the form)
Properties => {

# the used frontend module
Frontend => {
Action => ['AgentTicketPhone', 'AgentTicketEmail'],
},

# the logged in agent
User => {
UserLogin => ['some login'],
Group_rw => [
'hotline',
],
Role => [
'admin',
],
# ...
},

# the logged in customer
CustomerUser => {
UserLogin => ['some login'],
UserCustomerID => ['some customer id'],
Group_rw => [
'hotline',
],
# ...
},

# process properties
Process => {
ProcessEntityID => ['Process-9c378d7cc59f0fce4cee7bb9995ee3eb'], # the Process that the current ticket is part of
ActivityEntityID => ['Activity-f8b2fdebe54eeb7b147a5f8e1da5e35c'], # the current Activity of the ticket
ActivityDialogEntityID => ['ActivityDialog-aff0ae05fe6803f38de8fff6cf33b7ce'], # the current ActivityDialog that the Agent/Customer is using
},

# ticket properties
Queue => {
Name => ['Raw'],
QueueID => ['some id'],
GroupID => ['some id'],
Email => ['some email'],
RealName => ['OTRS System'],
# ...
},
Service => {
ServiceID => ['some id'],
Name => ['some name'],
ParentID => ['some id'],
# ...
},
Type => {
ID => ['some id'],
Name => ['some name'],
# ...
},
Priority = {
ID => ['some id'],
Name => ['some name'],
# ...
},
SLA = {
SLAID => ['some id'],
Name => ['some name'],
Calendar => ['some calendar'],
# ...
},
State = {
ID => ['some id'],
Name => ['some name'],
TypeName => ['some state type name'],,
TypeID => ['some state type id'],
# ...
},
Owner => {
UserLogin => ['some login'],
Group_rw => [
'some group',
],
Role => [
'admin',
],
# ...
},
Responsible => {
UserLogin => ['some login'],
Group_rw => [
'some group',
],
Role => [
'admin',
],
# ...
},
DynamicField => {
# Names must be in DynamicField_&lt;field_name&gt; format.
# Values in [ ... ] must always be the untranslated internal data keys
# specified in the dynamic field definition and
# not the data values shown to the user.
DynamicField_Field1 => ['some value'],
DynamicField_OtherField => ['some value'],
DynamicField_TicketFreeText2 => ['some value'],
# ...
},
# alternatively, ticket properties can be specified in the ticket hash
Ticket => {
Queue => ['Raw'],
State => ['new', 'open'],
Priority => ['some priority'],
Lock => ['lock'],
CustomerID => ['some id'],
CustomerUserID => ['some id'],
Owner => ['some owner'],
DynamicField_Field1 => ['some value'],
DynamicField_MyField => ['some value'],
# ...
},
},

# match properties (existing values from the database)
PropertiesDatabase => {
# See section "Properties", the same config can be used here.
# ...
}

# reset possible options (white list)
Possible => {
# possible ticket options (white list)
Ticket => {
Queue => ['Hotline', 'Coordination'],
State => ['some state'],
Priority => ['5 very high'],
DynamicField_Field1 => ['some value'],
DynamicField_MyField => ['some value'],
# ...
NewOwner => ['some owner'],
OldOwner => ['some owner'],
# ...
},

# Limit the number of possible ActivityDialogs the Agent/Customer
# can use in a process ticket.
ActivityDialog => ['AD1', 'AD3'],

# Limit the number of possible Processes that can be started
Process => ['Process-9c378d7cc59f0fce4cee7bb9995ee3eb', 'Process-12345678901234567890123456789012'],

# possible action options (white list)
Action => [
'AgentTicketBounce',
'AgentTicketPhone'. # only used to show/hide the Split action
'AgentLinkObject', # only used to show/hide the Link action
# ...
],
},
# add options (white list)
PossibleAdd => {
# See section "Possible"
# ...
},
# remove options (black list)
PossibleNot => {
# See section "Possible"
# ...
},
};
While matching ACLs if CustomerUserID parameter sent, the ACL mechanism will compare the defined ACLs using the supplied CustomerUserID to gather the CustomerUser details to fill the CustomerUser hash and it also overrides the Customer information in the Ticket hash for the Properties match. On the other hand this calculations are also made for the PropertiesDatabase part, but using the Ticket Customer as the basis to gather the data. При проверке ACLs, если CustomerUserID параметр отправлен, механизм ACL сравнивает заданный ACL используя представленный CustomerUserID для сбора данных CustomerUser для заполнения CustomerUser hash, а также перекрывает информацию о клиенте в hash заявки для проверки в Properties. С другой стороны эти вычисления также используются в PropertiesDatabase разделе, но с использованием клиента заявки как основу для сбора данных.
Notice that in Customer Interface, the CustomerUserID is always sent with the current logged Customer User. Обратите внимание, что в Пользовательском Интерфейсе, CustomerUserID всегда отправляется с залогиненым Клиентом.
Be aware that in ticket search screens (AgentTicketSearch and CustomerTicketSearch) the only affected attributes by ACLs are the Dynamic Fields. This means that this screens you can not restrict any other attribute like ticket type, state, queue, etc. Помните, что на экранах поиска (AgentTicketSearch и CustomerTicketSearch) - единственно доступные атрибуты для ACL это динамические поля. Это означает, что для этих экранов вы не можете ограничить любые другие атрибуты, такие как Тип заявки, Состояние, Очередь и т.д.
From OTRS 4 the 'Action' parameter is not longer a hash but an array reference and it can be used in any of the Change sections using any of the Modifiers. Начиная с OTRS 3.4.x, параметр 'Action' теперь является не hash, а ссылкой на массив и может быть использован в любой секции Изменения, используя различные модификаторы/Modifiers.
Performance Tuning Настройка Производительности
Presented below is a list of performance enhancing techniques for your OTRS installation, including configuration, coding, memory use, and more. Ниже представлен перечень различных техник, которые можно использовать для получения максимально возможной производительности системы OTRS: настройка, кодирование, использование памяти и многое другое.
OTRS OTRS
There are several options for improving OTRS performance. Есть несколько возможных вариантов улучшения производительности OTRS.
TicketIndexModule TicketIndexModule
There are two backend modules for the index for the ticket queue view: Есть два типа модулей для индексирования заявок в обзоре очередей:
<literal>Kernel::System::Ticket::IndexAccelerator::RuntimeDB</literal>
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

Reference
Сссылка
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><title>
Source string location
en/content/customization/acl.xml:402
String age
a year ago
Source string age
a year ago
Translation file
i18n/doc-admin.ru.po, string 832