ThinKnx Configurator: new Deploy menu

The ThinKnx Configurator always evolves to make life easier to installers. In this release ( the Export procedure has been redesigned to make it more straightforward and easy. The operations related to the exportation and deploy of the project are now splitted in two different context menu: Deploy and Export.
The Export menu is reduced and contains all the functions related to a file exportation of the project: Export project (*.erg), Export for Server on File (*.srv), Export for Touch Screen/Windows (*.thw), Export for Android (
In the Deploy menu, all the functions concerning the publishing/deployment of the project are collected and organized in two section, local deploy and cloud deploy. Moreover, a new Help item has been added to clarify the difference between these two modalities.
If the PC running the Configurator is in the same network of ThinKnx server and clients, it is always possible to use the Local deploy, which is the "traditional" procedure to upload the project on server and to start a web server to download the project on clients.

New authentication procedure

The procedure to authenticate client devices always requires the effort of installers to access the server web pages and to manually add the last connected client code to the table of enabled clients. To save time to installers and leave more indipendence to final users, it is now possible to authenticate the client directly from the app through a simple popup.
To use this feature the ThinKnxCloud must be enabled and the users must be configured (each user with its own cloud password) in the project. It is enough to enable the "Automatic authentication" property in the System node and to upload the project to the cloud (if the Automatic server update is disabled, remember to upload it also on the server!). Then, when an unauthenticated client connects to the ThinKnx server, a popups appears in the app asking for credentials. If the credentials provided by the users are correct, a new row will be automatically added in the table of enabled clients in the server web pages.