Skip to main content

ProGlove documentation

Provisioning

Provisioning establishes a connection between the Standalone SDK and INSIGHT webportal.Once provisioned, the SDK is linked to the Insight backend and can transmit operational data for monitoring, analytics, and diagnostics.

Provisioning is performed using a .fleet file generated and downloaded from the ProGlove Insight Webportal and imported into the SDK.

What provisioning enables

After successful provisioning, the SDK automatically forwards events to the INSIGHT webportal. The following event types are collected and transmitted:

  • Scanning events.

  • Worker feedback events.

  • Telemetry events.

  • Display change events.

  • Connection events.

This allows administrators and operators to gain visibility into device usage and workflow execution.

Provisioning via the SDK

To provision the SDK, convert the downloaded .fleetfile into a ByteArray and pass it to the provision() method on the PgManager.

Example:

PgManager.provision(ByteArray, object : IProvisioningStatusCallback {
    override fun provisioningDone(isSuccess: Boolean) {
        // isSuccess == true if provisioning was successful
    }
})

Where:

  • fleetByteArray is the .fleet file converted into a ByteArray.

  • IProvisioningStatusCallback returns the provisioning result.

If provisioning completes successfully, the Devices: Standalone SDK is immediately connected to the INSIGHT webportal.

Checking provisioning status

You can check whether the SDK is already provisioned by calling isProvisioned() on the PgManager.

Example:

PgManager.isProvisioned(object : IIsProvisionedCallback {
    override fun isProvisioned() {
        // SDK is provisioned
    }
})

Important

Important notes:

  • isProvisioned() is asynchronous.

  • If the SDK is provisioned, the isProvisioned() callback will be invoked.

  • If the SDK is not provisioned, no callback is returned.

This behavior is intentional and should be handled accordingly in your integration logic.

In this section: