Source string Read only

5/100
Context English State
For detailed instructions on how to write Template Toolkit code, refer to the `Template Toolkit User Manual <http://www.template-toolkit.org/docs/manual/index.html>`__.
Debugging Templates
Writing Template Toolkit code is not too difficult compared to other languages. Nevertheless errors can occur as we are all just humans. To validate your template, open the ticket create or answer screen, where you have your templates configured to be used and choose a template.
If you have mistakes in your Template Toolkit syntax, choosing a template will bring up an error screen that tell you about what went wrong and where to find the error.
Error Reason in Error Screen
In this example the **OTRS** system informed us, that there was an unexpected token ``[`` in the line ``[% IF Data.OTRSTagData.TypeID == 1 [% %]``. A second opening bracket was entered inside the same Template Toolkit tag, which for sure is forbidden.
To fix the error:
Go back to the template editing screen.
Edit the template and save it.
Start debugging the template again by creating or answering a ticket, till no more errors are found and your template comes up as desired.
This package has no agent interface.
Advanced Escalations
This feature add-on makes your escalation management more flexible and adjusts it according to your customers or to different service level agreements. Escalation types defined in **OTRS**, such as *First Response Time*, *Update Time*, and *Solution Time*, can be enhanced by creating new types and defining your own names and properties.
The *Ticket Escalation Types* option in the administrator interface enables you to define when escalations should:
start,
stop,
be suspended,
be resumed
and be restarted.
Ticket attributes, like its status or certain events like creating or answering a ticket, can be used as a trigger. For example, an escalation can start when a ticket is created, but the escalation can stop when the ticket is answered by the agent. If the status of a ticket is changed to *Pending Reminder*, the escalation is suspended, but if the status is changed back to *Open*, the escalation resumes. An up-to-date display of the escalation time left makes accurate service time management possible.
In the ticket view, the new widget *Escalation Information* appears. This shows through the use of different colors and numerical values whether or not:
the escalation time is still within the original timeframe (green),
the escalation time will run out soon (yellow),
the escalation is suspended (brown),
the escalation time has been reached, i.e. the ticket has escalated (red) or
escalation has been suspended or the ticket has been stopped (the window is no longer visible).
The *Ticket Escalation Type Bundle* option enables you to assign newly created escalation types to different customers or service level agreements.
The following scenarios can now be handled more flexibly with *Advanced Escalations*:
A customer requests a rework of a solution – the escalation must be adjusted.
To present a solution, more information is required from the customer – the escalation must be suspended.
A service technician can’t get into the building or has no free access to the machine that needs to be fixed – the escalation must be suspended.

Loading…

User avatar None

New source string

OTRS 7 / Feature Add-ons ManualEnglish

New source string a year ago
Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Flags
read-only
Source string location
../../content/advanced-escalations.rst:9
String age
a year ago
Source string age
a year ago
Translation file
locale/content.pot, string 114