With the Mobile Ticket application, customers can request tickets from their mobile device, via a web page/web application, using a direct URL, or for example a QR code to determine their 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:
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.
• 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 “Configuration for 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 is tested and supported on the following browsers:
• Safari
• Chrome
• Opera
If you use a browser that is not supported, you will be notified about that.
Distributed Operations
Distributed Operations, allowing you to configure and manage your customer journey platform centrally, while the workload is distributed among all your branches, is supported.
• Orchestra Orchestra 6.1, Hotfix 4 or later is required.
• 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.
• We have received reports on problems starting Mobile Ticket on Linux. If you get an error related to helmet, install the latest version of helmet by npm i -s helmet and it should work.
Note that Mobile Ticket has not been tested on Linux.
Upgrade
Please note that upgrade, in the proper sense of the word, is not supported for Mobile Ticket. 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.
Cookies
In Mobile Ticket, the following three types of information are temporarily saved in cookies for session management purposes:
• Selected branch
• Selected service
• Visit information
After 12 hours, these data will expire. No other cookie data is saved.
Note that there is an option to enable Google Analytics. If so, it might be required to customize Mobile Ticket in order for follow local regulations related to GDPR.
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:
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” .
Distributed Operations requires stable connectivity.