Using QR Codes and variables in a Response

Jens Bothe08. Jun 2011 | AdministrationBest PracticesConsulting

Disclaimer:

The practical examples presented in our technical blog (blog.otrs.com) and now in the expert category in our FAQ blog section serve as a source of ideas and documentation to show what is theoretically possible with OTRS in concrete scenarios or sometimes even for more exotic configurations. All configurations presented here were developed under laboratory conditions as a proof of concept. 

We can only guarantee testing and implementation of these concepts to be error-free and productive if implemented in a workshop with one of our OTRS consultants. Without this, the responsibility lies with the customer himself. Please note that configurations from older OTRS versions may not work in the newer ones.

Recently a customer had a very interesting issue which he needed to be solved. For external visitors they provide a free WIFI protected by an WPA key. They created some scripts to generate the key and distribute it to the access points.

Internal customers can order access for their guests at the IT guys. As OTRS now is used for tracking all kind of requests they decided to send out the confirmation mail including the key via OTRS. As a “geek goody” they also wanted to create a QR Code for the WIFI data, which looks like this:
QR Code

We created the following items to make this happen:
– a shell script for generation of an OTRS config file which gets the key as parameter
– a default response using the variable stored in the config file. This variable is called notification tag in OTRS.

The shell script:

#!/bin/sh
Key="$1";
echo "\$Self->{'WEPKey'} = '$Key';" > /otrs/Kernel/Config/Files/WIFI.pm;
echo "1;" >> /otrs/Kernel/Config/Files/WIFI.pm;

The notification tag for this in OTRS is: <OTRS_CONFIG_WEPKey>

 

The content of the response (you need to type in the data as HTML Source!)

Writing the answer to the customer will look like this:

 

Some more informations:

 

 

Your email address will not be published.