External Configuration Support
This Support Application feature enables loading configurations from Play Store Managed Configurations and Intent Actions.
Overview
Support Application typically gets its configuration from the BlueFletch Launcher or from configuration files loaded onto the device via an MDM. In version 5.13.8, the Support Application now provides two additional methods for loading configurations: Play Store Managed Configurations and Intent Actions. With External Configuration Support, Support Application can store configurations within application data storage.
User Guide
To use Play Store Managed Configurations, you need to add the following fields to the application's Play Store listing:
configUrl: A URL referencing the desired configuration.
configChecksum: A configuration file checksum. This field is optional.
To use Intent Actions, you need to create an Intent Action with the action name com.bluefletch.support.config.ACTION_LOAD_CONFIG. The Intent Action should have the following extras:
url: A URL referencing the desired configuration. This is required.
org_id: The organization ID as found in the BlueFletch Portal. This is required.
Feature Configuration
To set up External Configuration Support for a particular device profile or device group, please follow the steps below:
Configuring with ADB Command
To enable Support Application to download the configuration file from the specified URL, you need to specify the intent action, the package name, and extra strings that will be passed to the intent. In the example below, com.bluefletch.ems.support.ACTION_DOWNLOAD_CONFIG is the intent action and com.bluefletch.ems.support is the package name.
Configuring with AirWatch Command
Use the example below to configure with AirWatch Command.
Configuring with SOTI Command
Use the example below to configure with SOTI Command.
Last updated