Upload App versions

As soon as an App is registered, it is possible to upload an App version via the App details page (by clicking the magnifier glass, see here). 

To open the detailed version page, click the 'Create ETS App version' button from the ETS App versions section.

By doing so, the detailed version page opens. This page consists out of the following sections:

• Project file
• Billing information
• License agreement
• Release notes

Project file

In this section, an App developer can:

• Upload an App binary file (.etsapp) for validation, by dragging and dropping the file, or by clicking the upload area and selecting the file.
• Define the App's binary version, by entering it in the corresponding field.

This version number is used by ETS in order to check for updates of this ETS App, it is therefore highly recommended to use the same version as indicated in the binary file.

If there is already an App version listed, then the following options are additionally shown in the 'Project file' section:

• This version includes new features: By checking this, the App developer declares that this version is an 'Upgrade version' and consequently its validation will result in an 'Upgrade validation' with the respective fee.
• This version includes bug fixes: By only checking this option, the App developer declares that this version is an 'Update version' and consequently its validation will result in an 'Update validation' with the respective fee.

In case both options are checked; the App developer declares the version as an 'Upgrade version' which also fixes bugs.

Billing information

In this section, App developers can select the invoice contact in order to regulate the payable App fees. The invoice contacts shown in the 'Select invoice information' dropdown are derived from the Professional account to which the App developer account is linked to.

License agreement

In this section, an App developer can:

• Upload a license agreement file for a specific App version, by dragging and dropping the file, or by clicking the upload area and selecting the file.
  

  The preferred format is PDF, file types like as doc, docx, odt are also accepted.

• Select from the dropdown menu the language of the uploaded license agreement file.
  

  The supported languages for the license agreements are limited to those offered in MyKNX and can be found via the language picker of MyKNX.

• Download or delete the current license agreement, by clicking the download or the delete icon respectively.

Note: the License Agreement file requested here is a document which stipulates the legal framework between the App developer and the End User (EULA), so nothing with KNX Association as a party. The license agreement is shown to customers (End Users) purchasing the App via MyKNX and shall be (read and) accepted in order to complete the order.

Release notes

In this section, an App developer can:

• Upload a release notes file for a specific App version, by dragging and dropping the file, or by clicking the upload area and selecting the file.
  

  The preferred format is PDF, file types like as doc, docx, odt are also accepted.

• Select from the dropdown menu the language of the uploaded license agreement file.
  

  The supported languages for the license agreements are limited to those offered in MyKNX and can be found via the language picker of MyKNX.

• Download or delete the current release notes, by clicking the download or the delete icon respectively.

Note: This file serves the purpose of keep the history of the ETSApp modifications, being them bugfix or new features. It is also used from the KNX Support Team as a reference for problems that might arise between the ETS (in a specific version) and the ETSApp (in a specific version). The format could be, .txt, .pdf, .doc but the content must be: