PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Enabling the telemetry
  • Creating the executable
  • Configuring the telemetry
  • Installing the application
  • Installing an application that support the telemetry
  • Installing an application that support the telemetry
  • Overview
  • Enabling the telemetry
  • Enabling the telemetry in the project description
  • Enabling the telemetry in the description of a configuration
  • Enabling the telemetry when creating the executable
  • Installing the application
  • Installing an application that support the telemetry
  • Installing an application that support the telemetry
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
To use the telemetry in a WINDEV or WINDEV Mobile application, you must:
  1. Enable the telemetry in the application. This activation can be done:
    • WINDEV when creating the executable.
    • in the platform description.
  2. Deploy the application:
Note: The telemetry data is anonymous data.Note: The telemetry data is anonymous data by default. You have the ability to identify the user by using TelemetryIdentifyUser.
Versions 22 and later
Universal Windows 10 App The telemetry is now available in the applications in Universal Windows 10 App mode.
iPhone/iPad The telemetry is now available in the iPhone/iPad applications.
Android The telemetry is now available in the Android applications.
New in version 22
Universal Windows 10 App The telemetry is now available in the applications in Universal Windows 10 App mode.
iPhone/iPad The telemetry is now available in the iPhone/iPad applications.
Android The telemetry is now available in the Android applications.
Universal Windows 10 App The telemetry is now available in the applications in Universal Windows 10 App mode.
iPhone/iPad The telemetry is now available in the iPhone/iPad applications.
Android The telemetry is now available in the Android applications.
Enabling the telemetry
WINDEV

Creating the executable

To enable the telemetry, all you have to do is create the executable: on the "Project" pane, in the "Generation" group, click "Generate".
The "Telemetry" step is used to fill the telemetry options:
  1. Check "Enable the telemetry for this application".
  2. Specify the location of telemetry server:
    • Local, network or Internet network: In this case, you have the ability to specify the protocol used: HTPP or HTTPS.
      Note: For an HTTPS protocol, a certificate must be installed on your Web server (IIS or Apache).
    • CLOUD platform. In this case, all you have to do is specify the CLOUD account to use.
      Note: A Telemetry platform is required.
  3. Specify the address of the telemetry server to use:
  4. Check the connection to the telemetry server to make sure that the data is correct.
Follow the different wizard steps to create your executable.
Note: The telemetry data sent to the server is processed every two hours. Therefore, it will not be immediately visible in the telemetry dashboard.

Configuring the telemetry

To configure the telemetry for the current configuration:
  1. On the "Project" pane, in the "Project configuration" group, click "Current configuration".
  2. Select the "Telemetry" tab to configure the telemetry:
  3. Check "Enable the telemetry for this configuration".
  4. Specify the location of telemetry server:
    • Local, network or Internet network: In this case, you have the ability to specify the protocol used: HTPP or HTTPS.
      Note: For an HTTPS protocol, a certificate must be installed on your Web server (IIS or Apache).
    • CLOUD platform. In this case, all you have to do is specify the CLOUD account to use.
  5. Specify the address of the telemetry server to use:
  6. Check the connection to the telemetry server to make sure that the data is correct.
  7. The option "Telemetry of the application" is used to configure:
    • The application name. This name will be proposed in the telemetry dashboard.
    • The mode for enabling the telemetry. The telemetry is automatically enabled by default but it can be enabled by programming with TelemetryEnable. The mode for triggering the collection of information. The data collection is automatically enabled by default but it can be enabled by programming with TelemetryEnable.
Installing the application
WINDEV

Installing an application that support the telemetry

The procedure for creating the setup of an application that supports the telemetry is identical to the procedure for creating a standard setup, with an additional step.
  1. Start the setup procedure of the application: on the "Project" pane, in the "Generation" group, click "Setup procedure".
  2. Create the executable if necessary.
  3. In the left section of the wizard, select "Skin template of installer".
  4. Follow the different wizard steps until you reach the "Enabling the telemetry" step.
    In this screen, you can:
    • Display (or not) an information message. This information message informs the end user that the telemetry will be used on his application.
      Important note: Regardless this message is displayed or not, the telemetry will be enabled in the application.
      If TelemetryIdentifyUser was used in the application code, the default message does not specify that the transmitted data is anonymous data.
    • Allowing the end user disable the telemetry.
      In this case, the end user can check (or not) the option "I accept to contribute to the improvement of XXXX". No data will be collected if the end user refuses.
      Note: If the option "These parameters will replace the parameters previously entered in deployment" is checked, the question will be asked again to the end user whenever an update is performed. Note: If the option "During an update, the telemetry will be automatically proposed to the user even if it was disabled" is checked, the question will be asked to the end user whenever a new update is performed.
Then, the procedure for setup creation is the standard one.
Reminder: This setup program is supplied in English and in French. To translate the setup program into other languages, a setup custom program must be created.
When the application is installed, the data is regularly sent to the server:
  • every hour. This frequency can be modified by TelemetryConfigure.
  • when closing the application.
WINDEV Mobile

Installing an application that support the telemetry

The procedure for creating the setup of an application that supports the telemetry is identical to the procedure for creating a standard setup.
The telemetry is automatically enabled when starting the application (or via TelemetryEnable).
The telemetry data is sent whenever possible:
  • when the starting application,
  • when closing the application,
  • every hour,
  • when going into background.
Notes:
  • In order for the telemetry data to be sent, a connection to the telemetry server is required.
  • Using the telemetry in the mobile application does not consume a lot of data.
  • The frequency for collecting information can be defined by TelemetryConfigure. Indeed, the default frequency set to one hour can be reduced in a mobile application.
Overview
To use the telemetry in a WINDEV or WINDEV Mobile application, you must:
  1. Enable the telemetry in the application. This activation can be done:
    • Versions 22 and later
      in the project description. In this case, this activation is performed for all the existing project configurations.
      New in version 22
      in the project description. In this case, this activation is performed for all the existing project configurations.
      in the project description. In this case, this activation is performed for all the existing project configurations.
    • in the platform description.
    • WINDEV when creating the executable.
  2. Deploy the application:
Note: The telemetry data is anonymous data by default. You have the ability to identify the user by using TelemetryIdentifyUser.
Versions 22 and later
Universal Windows 10 App The telemetry is now available in the applications in Universal Windows 10 App mode.
iPhone/iPad The telemetry is now available in the iPhone/iPad applications.
Android The telemetry is now available in the Android applications.
New in version 22
Universal Windows 10 App The telemetry is now available in the applications in Universal Windows 10 App mode.
iPhone/iPad The telemetry is now available in the iPhone/iPad applications.
Android The telemetry is now available in the Android applications.
Universal Windows 10 App The telemetry is now available in the applications in Universal Windows 10 App mode.
iPhone/iPad The telemetry is now available in the iPhone/iPad applications.
Android The telemetry is now available in the Android applications.
Enabling the telemetry
The telemetry can be enabled:
  • Versions 22 and later
    in the project description. In this case, this activation is performed for all the existing project configurations.
    New in version 22
    in the project description. In this case, this activation is performed for all the existing project configurations.
    in the project description. In this case, this activation is performed for all the existing project configurations.
  • in the platform description.
  • WINDEV when creating the executable.
Versions 22 and later

Enabling the telemetry in the project description

To enable the telemetry in the project description:
  1. Display the description window of project: on the "Project" pane, in the "Project" group, click "Description".
  2. In the window that is displayed, select the "Telemetry" tab.
  3. Check "Enable the telemetry for the project" and specify the requested parameters:
    Project description,
    • Server location:
      • Local, network or Internet network: In this case, you have the ability to specify the protocol used: HTPP or HTTPS.
        Note: For an HTTPS protocol, a certificate must be installed on your Web server (IIS or Apache).
      • CLOUD platform. In this case, all you have to do is specify the CLOUD account to use.
        Note: A Telemetry platform is required.
    • Address:
      • Address of server or address of PCCloud platform.
      • User name and associated password. This data was given at the end of setup of telemetry server.
      Check the connection to the telemetry server to make sure that the data is correct.
    • Telemetry of application:
      • Name of application. This name will be proposed in the telemetry dashboard.
      • The mode for triggering the collection of information. The data collection is automatically enabled by default but it can be enabled by programming with TelemetryEnable.
  4. Validate.
These parameters are defined for the current project and for all its configurations. The telemetry can be customized or disabled for each project configuration.
New in version 22

Enabling the telemetry in the project description

To enable the telemetry in the project description:
  1. Display the description window of project: on the "Project" pane, in the "Project" group, click "Description".
  2. In the window that is displayed, select the "Telemetry" tab.
  3. Check "Enable the telemetry for the project" and specify the requested parameters:
    Project description,
    • Server location:
      • Local, network or Internet network: In this case, you have the ability to specify the protocol used: HTPP or HTTPS.
        Note: For an HTTPS protocol, a certificate must be installed on your Web server (IIS or Apache).
      • CLOUD platform. In this case, all you have to do is specify the CLOUD account to use.
        Note: A Telemetry platform is required.
    • Address:
      • Address of server or address of PCCloud platform.
      • User name and associated password. This data was given at the end of setup of telemetry server.
      Check the connection to the telemetry server to make sure that the data is correct.
    • Telemetry of application:
      • Name of application. This name will be proposed in the telemetry dashboard.
      • The mode for triggering the collection of information. The data collection is automatically enabled by default but it can be enabled by programming with TelemetryEnable.
  4. Validate.
These parameters are defined for the current project and for all its configurations. The telemetry can be customized or disabled for each project configuration.

Enabling the telemetry in the project description

To enable the telemetry in the project description:
  1. Display the description window of project: on the "Project" pane, in the "Project" group, click "Description".
  2. In the window that is displayed, select the "Telemetry" tab.
  3. Check "Enable the telemetry for the project" and specify the requested parameters:
    Project description,
    • Server location:
      • Local, network or Internet network: In this case, you have the ability to specify the protocol used: HTPP or HTTPS.
        Note: For an HTTPS protocol, a certificate must be installed on your Web server (IIS or Apache).
      • CLOUD platform. In this case, all you have to do is specify the CLOUD account to use.
        Note: A Telemetry platform is required.
    • Address:
      • Address of server or address of PCCloud platform.
      • User name and associated password. This data was given at the end of setup of telemetry server.
      Check the connection to the telemetry server to make sure that the data is correct.
    • Telemetry of application:
      • Name of application. This name will be proposed in the telemetry dashboard.
      • The mode for triggering the collection of information. The data collection is automatically enabled by default but it can be enabled by programming with TelemetryEnable.
  4. Validate.
These parameters are defined for the current project and for all its configurations. The telemetry can be customized or disabled for each project configuration.

Enabling the telemetry in the description of a configuration

To configure the telemetry for the current configuration:
  1. On the "Project" pane, in the "Project configuration" group, click "Current configuration".
  2. Select the "Telemetry" tab to configure the telemetry.
  3. Versions 22 and later
    Several options are available:
    Available options
    • Use the telemetry parameters of project: This option allows you to use the telemetry parameters specified in the project description.
      Caution: If the telemetry is not enabled in the project, the current configuration will not use the telemetry.
    • Use specific telemetry parameters: This option is used to define specific telemetry parameters for the current configuration. You can for example disable the telemetry on the project and enable it on a configuration only. You also have the ability to use specific parameters for a type of configuration (for example, the Windows and mobile configurations do not use the same server).
    • Disable the telemetry for this configuration: This option allows you to disable the telemetry for the current configuration.
    New in version 22
    Several options are available:
    Available options
    • Use the telemetry parameters of project: This option allows you to use the telemetry parameters specified in the project description.
      Caution: If the telemetry is not enabled in the project, the current configuration will not use the telemetry.
    • Use specific telemetry parameters: This option is used to define specific telemetry parameters for the current configuration. You can for example disable the telemetry on the project and enable it on a configuration only. You also have the ability to use specific parameters for a type of configuration (for example, the Windows and mobile configurations do not use the same server).
    • Disable the telemetry for this configuration: This option allows you to disable the telemetry for the current configuration.
    Several options are available:
    Available options
    • Use the telemetry parameters of project: This option allows you to use the telemetry parameters specified in the project description.
      Caution: If the telemetry is not enabled in the project, the current configuration will not use the telemetry.
    • Use specific telemetry parameters: This option is used to define specific telemetry parameters for the current configuration. You can for example disable the telemetry on the project and enable it on a configuration only. You also have the ability to use specific parameters for a type of configuration (for example, the Windows and mobile configurations do not use the same server).
    • Disable the telemetry for this configuration: This option allows you to disable the telemetry for the current configuration.
Note: If you select "Use specific telemetry parameters", all the telemetry parameters must be defined.
Customizing the telemetry options
  1. Specify the location of telemetry server:
    • Local, network or Internet network: In this case, you have the ability to specify the protocol used: HTPP or HTTPS.
      Note: For an HTTPS protocol, a certificate must be installed on your Web server (IIS or Apache).
    • CLOUD platform. In this case, all you have to do is specify the CLOUD account to use.
  2. Specify the address of the telemetry server to use:
  3. Check the connection to the telemetry server to make sure that the data is correct.
  4. The option "Telemetry of the application" is used to configure:
    • The application name. This name will be proposed in the telemetry dashboard.
    • The mode for triggering the collection of information. The data collection is automatically enabled by default but it can be enabled by programming with TelemetryEnable.
WINDEV

Enabling the telemetry when creating the executable

When creating a Windows executable, you have the ability to enable and configure the telemetry.
The different steps are as follows:
  1. Select (if necessary) the configuration corresponding to the executable.
  2. Create the executable: on the "Project" pane, in the "Generation" group, click "Generate".
  3. In the different steps regarding the "EXE definition", the "Telemetry" step is used to specity the telemetry options.
  4. Versions 22 and later
    Several options are available:
    Creating the executable: configuring the telemetry
    • Use the telemetry parameters of project: This option allows you to use the telemetry parameters specified in the project description. This option cannot be used if the telemetry is not enabled in the project.
      Creating the executable: telemetry not available in the project
    • Disable the telemetry for this configuration: This option allows you to disable the telemetry for the configuration linked to the executable currently generated.
    • Use specific telemetry parameters: This option allows you to define specific telemetry parameters for the configuration linked to the executable currently created. When this option is selected, all the telemetry parameters must be defined.
      Customizing the telemetry options
      1. Specify the location of telemetry server:
        • Local, network or Internet network: In this case, you have the ability to specify the protocol used: HTPP or HTTPS.
          Note: For an HTTPS protocol, a certificate must be installed on your Web server (IIS or Apache).
        • CLOUD platform. In this case, all you have to do is specify the CLOUD account to use.
      2. Specify the address of the telemetry server to use:
      3. Check the connection to the telemetry server to make sure that the data is correct.
    New in version 22
    Several options are available:
    Creating the executable: configuring the telemetry
    • Use the telemetry parameters of project: This option allows you to use the telemetry parameters specified in the project description. This option cannot be used if the telemetry is not enabled in the project.
      Creating the executable: telemetry not available in the project
    • Disable the telemetry for this configuration: This option allows you to disable the telemetry for the configuration linked to the executable currently generated.
    • Use specific telemetry parameters: This option allows you to define specific telemetry parameters for the configuration linked to the executable currently created. When this option is selected, all the telemetry parameters must be defined.
      Customizing the telemetry options
      1. Specify the location of telemetry server:
        • Local, network or Internet network: In this case, you have the ability to specify the protocol used: HTPP or HTTPS.
          Note: For an HTTPS protocol, a certificate must be installed on your Web server (IIS or Apache).
        • CLOUD platform. In this case, all you have to do is specify the CLOUD account to use.
      2. Specify the address of the telemetry server to use:
      3. Check the connection to the telemetry server to make sure that the data is correct.
    Several options are available:
    Creating the executable: configuring the telemetry
    • Use the telemetry parameters of project: This option allows you to use the telemetry parameters specified in the project description. This option cannot be used if the telemetry is not enabled in the project.
      Creating the executable: telemetry not available in the project
    • Disable the telemetry for this configuration: This option allows you to disable the telemetry for the configuration linked to the executable currently generated.
    • Use specific telemetry parameters: This option allows you to define specific telemetry parameters for the configuration linked to the executable currently created. When this option is selected, all the telemetry parameters must be defined.
      Customizing the telemetry options
      1. Specify the location of telemetry server:
        • Local, network or Internet network: In this case, you have the ability to specify the protocol used: HTPP or HTTPS.
          Note: For an HTTPS protocol, a certificate must be installed on your Web server (IIS or Apache).
        • CLOUD platform. In this case, all you have to do is specify the CLOUD account to use.
      2. Specify the address of the telemetry server to use:
      3. Check the connection to the telemetry server to make sure that the data is correct.
Follow the different wizard steps to create your executable.
Note: The telemetry data sent to the server is processed every two hours. Therefore, it will not be immediately visible in the telemetry dashboard.
Installing the application
WINDEV

Installing an application that support the telemetry

The procedure for creating the setup of an application that supports the telemetry is identical to the procedure for creating a standard setup, with an additional step.
  1. Start the setup procedure of the application: on the "Project" pane, in the "Generation" group, click "Setup procedure".
  2. Create the executable if necessary.
  3. In the left section of the wizard, select "Skin template of installer".
  4. Follow the different wizard steps until you reach the "Enabling the telemetry" step.
    In this screen, you can:
    • Display (or not) an information message. This information message informs the end user that the telemetry will be used on his application.
      Important note: Regardless this message is displayed or not, the telemetry will be enabled in the application.
      If TelemetryIdentifyUser was used in the application code, the default message does not specify that the transmitted data is anonymous data.
    • Allowing the end user disable the telemetry.
      In this case, the end user can check (or not) the option "I accept to contribute to the improvement of XXXX". No data will be collected if the end user refuses.
      Note: If the option "These parameters will replace the parameters previously entered in deployment" is checked, the question will be asked again to the end user whenever an update is performed. Note: If the option "During an update, the telemetry will be automatically proposed to the user even if it was disabled" is checked, the question will be asked to the end user whenever a new update is performed.
Then, the procedure for setup creation is the standard one.
Reminder: This setup program is supplied in English and in French. To translate the setup program into other languages, a setup custom program must be created.
When the application is installed, the data is regularly sent to the server:
  • every hour. This frequency can be modified by TelemetryConfigure.
  • when closing the application.
WINDEV Mobile

Installing an application that support the telemetry

The procedure for creating the setup of an application that supports the telemetry is identical to the procedure for creating a standard setup.
The telemetry is automatically enabled when starting the application (or via TelemetryEnable).
The telemetry data is sent whenever possible:
  • when the starting application,
  • when closing the application,
  • every hour,
  • when going into background.
Notes:
  • In order for the telemetry data to be sent, a connection to the telemetry server is required.
  • Using the telemetry in the mobile application does not consume a lot of data.
  • The frequency for collecting information can be defined by TelemetryConfigure. Indeed, the default frequency set to one hour can be reduced in a mobile application.
  • Android The telemetry is available for the devices equipped with an ARM processor. Otherwise, the telemetry is disabled. Android This telemetry is available for the devices equipped with ARM processors or using an ARM emulation. Otherwise, the telemetry is disabled as well as for the Samsung Galaxy Tab 3 tablet.
Minimum required version
  • Version 21
This page is also available for…
Comments
Click [Add] to post a comment