Mobile Ticket : General Information
  

General Information

With this application, an end-customer can request a ticket from his mobile device, via a web page/web application, using a direct URL, or for example a QR code on his/her physical ticket to determine his/her position in the Queue.
The picture below illustrates the architecture of the Mobile Ticket application as well as how the different parts communicate with each other:
 

Deliverables

The software is available on github.com/qmatic/mobile-ticket as well as on Qmatic World.
Please read the README.md file for more information.
The following table describes the contents of the Mobile Ticket package, on a high level:
 
File / folder
Sub folder
Contents Description
sslcert
 
This folder contains a script called create_cert.sh. This folder is also where you should place your certificate, if your server is supporting SSL. This is defined in the proxy-config.json file.
node_modules
iconv-lite
These sub folders contain parsers, http-proxy, readme-files etc.
express
express-http-proxy
raw-body
unpipe
proxy-config.json
 
This is where you specify the API Gateway Host address, local webserver port, etc. For more information, see “Installation and Basic Configuration - Node.js / Mobile Ticket” .
server.js
 
Main script file to start the solution.
src
app
This folder contains the following sub folders:
• config - This folder contains the config.json file, where you specify the branch radius, where you find the current version number of Mobile Ticket, and so on. For more information, see “Basic Configuration - Mobile Ticket Web Application” .
• locale - This folder from start only contains the file en.json and this is where you place your translated language files, if applicable. For more information, see Localization.
• resources - In this folder, you find graphical resources used, such as fonts, images, and buttons. A few of these are then pointed out from the theme-styles.css file. Here, you can also find the sound file notification.mp3, which is pointed out from the config.json file.
• theme - This folder contains the file theme-styles.css, a Cascading Style Sheet file defining for example font color, accent color, and logotype.
zip
This folder contains the files bundle.min.css.gz and bundle.min.js.gz.
The files favicon.ico and index.html

Supported Browsers

Mobile Ticket has been tested on (and is therefore supported on) the following browsers:
• Safari
• Chrome
• Opera
If you use a browser that is not supported, you will be notified about that.

Limitations

The following limitations exist:
• superadmin User may not be used.
• Currently, creation of Multi-Service Visits online is not supported. However, it is possible to for example create a Multi-Service Visit in a kiosk, get a paper ticket with a QR code on it and then scan that QR code, to follow the Visit online.
• Appointment Queues are not supported.
• If you are running http, location detection is not possible, for this HTTPS is needed.

Upgrade

Please note that upgrade, in the proper sense of the word, is not supported by Qmatic. The upgrade procedure actually consists of installing a newer version of the software.
 
Any configuration and customization performed in the previous version must most likely be performed manually again, in a later version of Mobile Ticket.
Also, we do not guarantee that functionality that was available in the previous version will remain unchanged in a later version.

Document Structure

This manual is meant to be seen as a Getting Started Guide. The goal of it is that you should get the Mobile Ticket solution up and running in a few steps:
1. “Installation and Basic Configuration - Orchestra” .
2. “Installation and Basic Configuration - API Gateway” .
3. “Installation and Basic Configuration - Node.js / Mobile Ticket” .
Once those steps are performed, Mobile Ticket should be up and running with basic functionality, suitable for demo purposes. However, for production environments, you may need to go on with Advanced Configuration, see “Advanced Configuration” .
If you are experiencing any problems, please see “Troubleshooting Guide” .
When you are ready to start using Mobile Ticket, you should check out “Common Use Cases” .