The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.
English
Do you really want to delete this key mapping?
Data key regex filters (before mapping)
Data key regex filters (after mapping)
The data structure will be traversed recursively and all configured regexes will be applied to all keys.
Use cases are e.g. removing key prefixes that are undesired or correcting keys that are invalid as XML element names.
Example 3: Search = '^(?<number>\\d+) (?<text>.+?)\\$' / Replace = '_\\$+{text}_\\$+{number}' turns '16 elementname' into '_elementname_16'.
If modifiers are desired they have to be specified within the regexes themselves.
Regular expressions defined here will be applied before the XSLT mapping.
Regular expressions defined here will be applied after the XSLT mapping.
The name is typically used to call up this web service operation from a remote system.
Mapping for incoming request data
The request data will be processed by this mapping, to transform it to the kind of data OTRS expects.
Mapping for outgoing response data
Include ticket data in response.
Define the route that should get mapped to this operation. Variables marked by a ':' will get mapped to the entered name and passed along with the others to the mapping. (e.g. /Ticket/:TicketID).
This field should be an integer number.
Here you can specify the maximum size (in bytes) of REST messages that OTRS will process.
Send Keep-Alive
This configuration defines if incoming connections should get closed or kept alive.
Endpoint