Skip to main content

ProGlove Documentation

Install INSIGHT Mobile

Important

If an INSIGHT Mobile Beta version (lower than v1.0) is installed on your device, please uninstall it before installing a stable release.

Prerequisite: INSIGHT webportal account activated.

  1. Select Resources → Downloads from the top menu.

  2. In the INSIGHT Mobile (Android) section, check the box to accept the End-user license agreement.

    The Download button becomes available.

  3. Click Download.

    The .apk file downloads to your desktop device.

  4. Transfer the .apk file to the Android/data/de.proglove.connect folder on your Android device via USB cable.

  5. Open the .apk file on your Android device.

    INSIGHT Mobile installs automatically.

Important

Due to limitations of Android 11, you can no longer copy files to the Android/data/de.proglove.connect folder using the Android device only or via MDM. For earlier Android versions, downloading the .apk directly to the Android device still works. On Android 11, you can still use the adb push command to push or pull files or folders to Android/data/de.proglove.connect.

InsightMobileDownload.png

Important

Permissions for installing third party applications (unknown sources) must be granted on your Android device.

After the installation, you can set the necessary Android device permissions manually in the app or set them automatically using your MDM System.

Android 11 limitations

Android 11 redefined the following storage-related permissions: READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, and MANAGE_EXTERNAL_STORAGE (for more information, see Scoped Storage.) Currently, this prevents the user to:

  • Copy-paste the files to the Android/data/de.proglove.connect folder using the Android device only

  • Delete the files from the Android/data/de.proglove.connect folder using the Android device only

  • Implement apps that push / change / delete these files

  • Get to the log files and share them using the Android device only or via MDM

  • Push the files to the Android/data/de.proglove.connect folder using an MDM

  • Access the Android/data/de.proglove.connect folder and its content using a PC (by connecting the device via USB) if the app is installed on a work (managed) profile.

MDMs with Android Enterprise or managed Google Play

If you are using an MDM with the Android Enterprise support or a company managed Google Play, you can use the Managed configurations (previously known as AppRestrictions) to configure the device using the solution below that is running on the work profile.

To make the INSIGHT Mobile app available via your managed Google Play account you need to:

  • Create a managed Google Play account (to learn more, see Android Enterprise)

  • Bind the managed Google Play account to the MDM system

  • Get the organization ID from this page

  • Provide the organization ID to your ProGlove representative and ask for it to be added to the supported list

When this is completed, you can use the ProGlove configuration file content (Base64 encoded) as the available key in your MDM. The string is parsed inside the app and stored as a file identically to scanning the configuration barcode. The propagation is done every time the app is started or the configuration content is updated.

Note

  • In case of invalid Base64 content, the file content will be neglected

  • In case of an empty string, the file content will be neglected

  • IGNORE (not case sensitive) - this string will ignore the file content key so that the integrator can add the configuration file a different integration method

  • REMOVE (not case sensitive) - this string will remove the file content previously loaded and set the default one (the same as a freshly installed application)

Set a custom device name

Using Intent API key broadcast, you can set a device name to match with a third-party system or simply identify a device better, since there are built-in Android 10+ limitations when it comes to sharing device details. This allows you to add a custom value, i.e. customer_custom_identifier, to the staging file within your MDM that will be visible to your workforce in the INSIGHT Mobile (Android) app, and is sent along with the data to INSIGHT Analytics for reporting purposes.

For more details on reporting, see export data.

Note

We recommend setting up the Intent key and value prior to starting the application and work processes.

Figure 1. Example created in a test mobile MDM environment:
Example created in a test mobile MDM environment:


Once the value is set, you can see it displayed as an additional field in the INSIGHT connectivity widget within INSIGHT Mobile, as shown in the image below. That value will also be shared with INSIGHT webportal with every event.

Example_Value_for_customer_custom_identifier.png

You can change the value by broadcasting a different message, bypass (ignore) it to use alternative integration methods, or remove it when needed. Sending the IGNORE value will simply ignore the entered information and allow the integrator to set the value in a different way (using adb or other API methods). Sending REMOVE as a value will remove the entered information, as well as the customer_custom_identifier field from the INSIGHT Mobile (Android) app.

Table 9. Managed configurations

File

Key

Valid values

Supported options

ProGlove.proconfig

configuration_content_android_enterprise_key

Only valid base 64 encoded config files

SET, IGNORE, REMOVE

levelname_provisioning_package.fleet

fleet_provision_content_android_enterprise_key

Only valid base 64 encoded fleet files

SET, IGNORE

customer_custom_identifier

customer_custom_identifier_content_android_enterprise_key

Any string containing 1 - 256 characters

SET, IGNORE, REMOVE



To learn more, see Android developer's page, Admin's perspective, and Samsung KNOX page.

In this section: