Introduction



There are two types of updates supported by the TransLution Auto update facility. Both Major (new Version) and minor (intermin release) updates are supported. Both of these are managed from an end user perspective in exactly the same way. The difference is that for major releases, the auto update is required and for minor releases the auto update is optional.



Major Updates


A Major release would be from V7.1 to Version 7.2 or from V7.5 to V8.0. When the first or second digit in the version number changes then an update on the clients is required. In this case TransLution checks for the update by comparing the server version to the version of software running on the client. If the first two digits don't match then a client update is required. This is done by following the steps descrined below.


Minor Updates


The second kind of update is a minor update and this is optional. An example of this is a change from V7.2.03 to 7.2.06. When the third of fourth digit changes this implies a minor bug fix has been done. Under these conditions, you may not wish to update all your clients. Perhaps the bug fix was related to a feature you don't use and you don't need to update any clients or perhaps it related to only Android so there is no need to update your Windows clients. When this happens, you have the option of uploading a new version of the client to the database as described below. 


Every time TransLution runs on a client server, in addition to looking for a major upgrade by checking the server version, it also looks for a minor update by comparing the current client buld number to the latest client build on the server. If you have uploaded a new client build, even if the server build didn't change, TransLution will autoupdate the clients with the latest build. 


The process descrided above means that Site Admin can at any time choose if they would like minor fixes to be distributed to all cients or only Android or Windows clients, simply by managing what they upload for distribution.


Enabling Auto Updates


It is required to upload new client versions to the database so that each client can download the software and perform an update. This is done using the TransLution Client Maintenance Utility. Run this Utility to see the form below.




This allows you to specify the database name and server where the application will be saved. Unless you have changed the common database name, keep the default TRANSLUTION_UTILITY_CONTROL for the database name but of course be sure to select the right database server. Once done you will see the form below. 

 



Form to upload client files

 

Select Upload Installer and then browse to the folder where the EazyTouch exe or the Android APK file can be found. Select to upload the file and once this is complete you will see your recently uploaded files.

 



This is all that is required at this stage. 


The option to Extract Installer provides a way to extract the file that is stored in the database and save it locally. If for example, a new device is being configured and you aren't sure you have access to the correct version of the application, you can download it from the database. All other work is done on the clients and users are only required to click OK when prompted for the update to occur.