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.
[i-doit] Übersichtlichkeit im CMDB Explorer herstellen
CMDB Explorer is your first port of call when it comes to taking a bird's eye view; starting from the selected object, all relationships to other objects are displayed. But it can of course happen that not all information listed there is of interested, and you need a more limited view. i-doit offers you the option of masking object types, relationships, etc. which you do not need with profiles and filters and storing a profile to help you do so.
A simple example: When you open a building, all the objects within this building are called up.
However, you only want a view of the locations that exist within the building. To do this, you create a new filter which only displays "location" objects. Then you create a new CMDB Explorer profile (it makes sense to copy and edit the default profile). In the profile, you set the filter you just created as the filter under "Defaults". In addition, you add the fields to be displayed in the "Object Information" tab.
After selecting the profile, Explorer displays the restricted view and hides the superfluous objects, for the time being
This is a simple example of how you can customise the view in i-doit to suit your needs. In the filter definition, you can add further restrictions for relationship types and weightings, the depth in terms of levels or the CMDB status. Try it out and see for yourself.
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.
With the help of the postmaster filters incoming e-mails can be processed specifically in ((OTRS)) Community Edition. One use case is ignoring automatic replies or absence notes.
In the following example configuration, the content of an automatic reply is not processed and discarded as an article.
The configuration of the postmaster filters can be found in the e-mail settings in the admin area. A new filter can be created via "Add filter".
