Source string Read only

15/150
Context English State
Click on the *Overwrite existing ACLs?* checkbox, if you would like to overwrite the existing ACLs.
Click on the *Import ACL configuration(s)* button.
Deploy the imported ACLs with *Deploy ACLs* button.
If several ACLs are added to the system, use the filter box to find a particular ACL by just typing the name to filter.
Changing the name of this object should be done with care, the check only provides verification for certain settings and ignores things where the name can't be verified. Some examples are dashboard filters, access control lists (ACLs), and processes (sequence flow actions) to name a few. Documentation of your setup is key to surviving a name change.
ACL Settings
Like comment, but longer text can be added here.
Stop after match
ACLs are evaluated in alphabetical order. This setting disables the evaluation of the subsequent ACLs.
Edit ACL Structure
The ACL definition can be split into two big parts, *Match settings* and *Change settings*. In the matching sections the ACLs contain attributes that has to be met in order to use the ACL. If the attributes defined in the ACL do not match with the attributes that are sent, then the ACL does not take any affect, but any other match ACL will. The change sections contain the rules to reduce the possible options for a ticket.
Match settings
This section contains matching options that can be changed on the fly. For example on a ticket creation time the data of the ticket changes dynamically as the agent sets the information. If an ACL is set to match a ticket attribute then only when the matching attribute is selected the ACL will be active and might reduce other ticket attributes, but as soon as another value is selected the ACL will not take any affect.
``PropertiesDatabase``
This section is similar to ``Properties`` but does not take changes in ticket attributes that are not saved into the database, this means that changing an attribute without submit will not make any effect. This section is not use for ticket creation screens (as tickets are not yet created in the database).
Change settings
``Possible``
This section is used to reset the data to be reduce to only the elements that are set in this section.
``PossibleAdd``
This section is used to add missing elements that were reduced in other ACLs. This section is only used in together with other ACLs that have ``Possible`` or ``PossibleNot`` sections.
``PossibleNot``
This section is used to remove specific elements from the current data. It could be used stand alone or together with other ACLs with a ``Possible`` or ``PossibleAdd`` sections.
Modifiers
In order to make the development of ACLs easier and more powerful there is a set of so called modifiers for the attributes on each section. This modifiers are explained below:
``[Not]``
This modifier is used to negate a value, for example ``[Not]2 low``. Talking about priorities will be the same as to have: *1 very low*, *3 normal*, *4 high*, *5 very high*.
``[RegExp]``
It is used to define a regular expression for matching several values, for example ``[RegExp]low``. In this case talking about priorities is the same as *1 very low*, *2 low*.
``[regexp]``
It is very similar to ``[RegExp]`` but it is case insensitive.
``[NotRegExp]``
ComponentTranslation
This translation Translated OTRS 8/Administration Manual Change settings
The following string has the same context and source.
Translated OTRS 8/OTRS Change settings

Loading…

User avatar None

New source string

OTRS 8 / Administration ManualEnglish

New source string 11 months ago
Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Flags
read-only
Source string location
../../content/processes-automation/access-control-lists.rst:132
String age
11 months ago
Source string age
11 months ago
Translation file
locale/content.pot, string 2594