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] Displaying and hiding menu entries in the ticket view
by Martin Haubold
In a standard configuration, many buttons are enabled in the ticket processing form. If you notice, over the course of time, that you do not need some of them, you can disable the buttons in ((OTRS)) Community Edition Sysconfig.
Figure 1: There are four buttons available for selection in the "Communication" field
To access the configuration item, open Sysconfig ("Admin" -> "Sysconfig") and select the "Ticket" configuration group. Now select the "Frontend::Agent::Ticket::MenuModule" item.
Figure 2: Selecting the entry in Sysconfig
A list with all the available buttons appears.
In our example, we want to hide the items "Outgoing/Incoming phone call" and "Outgoing E-Mail". We will be disabling the corresponding checkboxes to do this.
Figure 3: Disabling the desired menu items
Figure 4: After the change, only "Note" is available.
The settings are saved by clicking on "Update" at the bottom of this page. From now on, the selected items will not be displayed in the Ticket view.
If you do not wish to include all Active Directory users in i-doit, you can restrict said users via filters. Previously, the configuration of the LDAP filter could only be achieved by using the Filter Builder.
Starting from i-doit Version 31, the filter string can be edited directly.
Additional placeholders for the path to plugins ($USERXXX$) can be integrated very easily in SNAG-View. The following steps are necessary for this:
A new <item> entry must be created in the "resource_cfg.xml".
Note: Be careful not to change or delete existing <item> entries.
Example:
We currently ship two predefined macros: "$USER1$ and $USER2$". After the change, the macro $USER3$ is available for the path /var/lib/nagios/libexec-customer2.
The script "/usr/bin/createNagiosCfg.sh" is then executed, so that the configuration is saved and saved in the resource.cfg.
