Source string Read only

SysConfig
1204/12040
Context English State
Defines inline editing configuration for the dynamic field ticket properties. Please provide a separate configuration item in the array for each dynamic field you would like to configure. In case the specific dynamic field is missing from the configuration, inline editing feature will ultimately not be available for it. “DynamicFieldName” key must be used to specify the dynamic field in question. “PermissionType” key defines the necessary permission level user must have for the ticket in order to edit the property (i.e. “ro” or “rw”). “RequiredLock” can be used for specifying the ticket lock requirement for the inline editing (if checked, the ticket must be locked, otherwise ticket does not have to be locked).
Defines inline editing configuration for the lock ticket property.
Defines inline editing configuration for the owner ticket property.
Defines inline editing configuration for the priority ticket property.
Defines inline editing configuration for the queue ticket property.
Defines inline editing configuration for the responsible ticket property.
Defines inline editing configuration for the service/SLA ticket properties.
Defines inline editing configuration for the state ticket property.
Defines inline editing configuration for the type ticket property.
Defines inline editing configuration for the watch ticket property.
Defines internal communication channel.
Defines list of agent logins (UserLogin) that will be excepted from requiring to setup at least one two-factor authentication method.
Defines list of customer user logins (UserLogin) that will be excepted from requiring to setup at least one two-factor authentication method.
Defines maximum delay in milliseconds when trying to re-establish a WebSocket connection in the frontend applications.
Defines maximum number of attempts before giving up trying to re-establish a WebSocket connection in the frontend applications.
Defines menu items for the main menu. Additional menu items are defined by adding new items and specifying their parameters. The “Group” and “GroupRo” arrays can be used to limit access of the menu item to members of certain groups with RW and RO permissions respectively. You can use the “Name” and “Description” keys to change the user-facing text of the menu item. The “Link” key must contain either the path to the application route or an external URL. Each menu item must belong to an existing “MenuGroup” in order to get displayed. Using the “AccessModule” you can limit the display of the menu item based on more complex conditions, the value should be the package name of the relevant module. Via the “AccessKey” you can define a keyboard shortcut to activate the menu item, even if the menu is not expanded. The “Target” key influences how the menu item will be opened (you can use “_blank” value to open the menu item in new window). The “Prio” key can be used to change the sorting order of the item in respect to its siblings, menu items with higher value will sink to the bottom. The “Active” key determines if the menu item is considered by the configuration (value 1) or ignored (value 0).
Defines menu items for the new action menu. Additional menu items are defined by adding new items and specifying their parameters. The “Group” and “GroupRo” arrays can be used to limit access of the menu item to members of certain groups with RW and RO permissions respectively. You can use the “Name” and “Description” keys to change the user-facing text of the menu item. The “Link” key must contain either the path to the application route or an external URL. Each menu item must belong to an existing “MenuGroup” in order to get displayed. Using the “AccessModule” you can limit the display of the menu item based on more complex conditions, the value should be the package name of the relevant module. Via the “AccessKey” you can define a keyboard shortcut to activate the menu item, even if the menu is not expanded. The “Target” key influences how the menu item will be opened (you can use “_blank” value to open the menu item in new window). The “Prio” key can be used to change the sorting order of the item in respect to its siblings, menu items with higher value will sink to the bottom. The “Active” key determines if the menu item is considered by the configuration (value 1) or ignored (value 0).
Defines optional quick access menu items to be shown in the top bar menu. Additional menu items are defined by adding new items and specifying their parameters. The “Group” and “GroupRo” arrays can be used to limit access of the menu item to members of certain groups with RW and RO permissions respectively. The “Name” key is used as an identifier for the menu item, and must be unique. You can use the “Description” key to change the user-facing text of the menu item. The “Link” key must contain either the path to the application route or an external URL. Each menu item must have the “Icon” key defined, which refers to the type of the common icon which is rendered for it. Using the “AccessModule” you can limit the display of the menu item based on more complex conditions, the value should be the package name of the relevant module. Via the “AccessKey” you can define a keyboard shortcut to activate the menu item. The “Target” key influences how the menu item will be opened (you can use “_blank” value to open the menu item in new window). The “Prio” key can be used to change the sorting order of the item in respect to its siblings, menu items with higher value will sink to the bottom. The “Active” key determines if the menu item is considered by the configuration (value 1) or ignored (value 0).
Defines out of office message template. Two string parameters (%s) available: end date and number of days left.
Defines phone communication channel.
Defines privacy notice configuration for the external interface. The notice will be shown to all users until they accept the privacy policy. To deactivate the notice completely, simply disable this setting.
Defines queue name map for external interface.
Defines state name map for external interface.
Defines that a “FAQ” object can be linked with other “FAQ” objects using the “Normal” link type.
Defines that a “FAQ” object can be linked with other “FAQ” objects using the “ParentChild” link type.
Defines that a “FAQ” object can be linked with other “Ticket” objects using the “Normal” link type.
Defines that a “FAQ” object can be linked with other “Ticket” objects using the “ParentChild” link type.
Defines the (agent) user identifier for actions triggered by customers.
Defines the IP regular expression for accessing the local repository. You need to enable this to have access to your local repository and the Package::RepositoryList is required on the remote host.
Defines the PostMaster header to be used on the filter for keeping the current state of the ticket.
Defines the URL rich text editor path.

Loading…

User avatar None

New source string

OTRS 8 / OTRSEnglish

New source string 11 months ago
Browse all component changes

Things to check

Long untranslated

The string has not been translated for a long time

Reset

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
SysConfig
Flags
read-only
String age
11 months ago
Source string age
11 months ago
Translation file
i18n/otrs/otrs.pot, string 6327