Here you will find our monthly tips to improve your OTRS, i-doit, SNAG-View and NeDi configuration. If you need support in setting up your systems or need special adaptations, then simply contact us at +49 441 390 10 10 40 or send us an e-mail, we will be happy to advise you.
More than 100 customers from all areas of business and public administration trust our software solutions and services.
[((OTRS)) Community Edition] Using the FAQ
For useful tips or frequently occurring problems it can be helpful to create a FAQ entry in ((OTRS)) Community Edition. This means that all agents have access to the knowledge and can process tickets more quickly.
FAQ articles can (and should) be divided into categories. These can be mapped in a parent-child structure. You can define which agent groups are allowed to access articles within categories. The configuration can be found under "FAQ -> Categories - Administration":
A new article is created under "FAQ -> New". A title and the corresponding category must be entered. In addition, keywords can be assigned to the article in order to find this entry more quickly later. Under "Status" you can define who is allowed to read this article. A distinction is made between three access authorizations:
Internal (Agent): Only logged in agents can see the entry External (customer): Registered customers in the customer portal can also see the article Public (All): The article is visible for everyone without registration (<OTRS-URL>/public.pl)
Symptom", "Problem", "Solution" and "Comment" can be entered in the text boxes. The boxes support the well-known editor functions (e.g. coloring, embedding images, links):
After creation, the article is available to other agents or customers. This entry can now be used for ticket processing.
Below is a short example for "Outgoing e-mail". Under "Options" you can select FAQ articles. A mask with the existing FAQ categories and the corresponding articles opens. With a large FAQ, the search can be used to find the desired article more quickly. A click on the desired result opens the corresponding article and you can choose whether the entire article, the public link or both should be inserted into the reply mask. The prefabricated answer can then be edited further.
A well-structured FAQ can speed up the processing process for the agents. When the customer portal is used, the customers also benefit and in the best case a ticket is not even opened.
The full text search in ((OTRS)) Community Edition offers a very good possibility to quickly find the relevant tickets. Modern browsers are delivered with predefined search engines, but can be extended with your own searches. The examples of Google Chrome and Mozilla Firefox show how the ((OTRS)) Community Edition full text search can be integrated into the browser.
For useful tips or frequently occurring problems it can be helpful to create a FAQ entry in ((OTRS)) Community Edition. In this way all agents can access the knowledge and thus the tickets can be processed faster.
If configuration changes are made in ((OTRS)) Community Edition, the system may not behave "normally" for a short time. To inform other ((OTRS)) Community Edition agents that a change is being imported into the system, a system maintenance can be entered. To do this, select System Maintenance in the admin area and plan a new system maintenance:
Upgrading to the version will cause many invisible changes to the StatusTray.
These changes ensure a faster start-up and better handling of system resources. In addition, we are laying the first stone for further features of the application, e.g. full integration into the taskbar of the operating systems. This creates a seamless integration of the application into everyday life and thus allows the head to be free for the essentials.
The free "Device Exchange" add-on module offers a fast and convenient approach to replacing devices. Imagine the following scenario: A switch which is in use and well-documented fails; it needs to be replaced by another switch. The second switch also exists in the CMDB and is documented as completely as possible (model, accounting, location, status).
Every user in i-doit has the ability to configure their own dashboard. To allow this to happen, a number of pre-configured widgets are provided. Among other things, the "Report" widget can be displayed. This example embeds a report that provides information on the objects associated with the user ("Contact assignment" category), and which were last edited by another user.