Starting the Profile Client with Configuration

The startActivity intent starts the Profile Client with configuration. Sending this intent overwrites the Profile Client existing configuration with the parameters in the new configuration. Valid configuration parameters are defined in Profile Client Configuration.

Use one of the following two methods to configure the Profile Client. Both methods support the same parameters.

Configuration via a JSON File

Load the configuration file, using the

profile_uri

defined in the table below. The file must be located on the device and the path/name specified in the intent, unless using the following default file path/name:

/enterprise/device/settings/WFCDFSConfig.json for WPC Version 2.0.21201 and above.

/sdcard/WFCDFSConfig.json for all other versions.

Configuration via a JSON structure

To send the configuration information, use the

config_profile

defined in the table below.

Prerequisites

When configuring through a file, ensure that the JSON file is downloaded to the device.

The minimum required Profile Client Android version is 2.0. 19234.

When configuring through a JSON structure, the minimum required Profile Client Android version is 2.0.20205.

Intent Definition

Name	Description
Action	com.zebra.dfs.ACTION_NEW_CONFIG
Intent Type	startActivity
Extra 0	This extra specifies the name of a configuration file. Either Extra 1 or Extra 0 must be present, but not both.
Type	String
Name	profile_uri
Value	Path/name of the configuration file.
Extra 1	This extra specifies a set of configuration parameters. Either Extra 1 or Extra 0 must be present, but not both.
Type	String
Name	config_profile
Value	JSON string

ADB Examples

Starting and configuring the client using the default file path/name:

adb shell am start -a com.zebra.dfs.ACTION_NEW_CONFIG

Starting and configuring the client using a different file path/name:

adb shell am start -a com.zebra.dfs.ACTION_NEW_CONFIG --es profile_uri/enterprise/device/settings/Store1105.json

When a configuration file is used, once the file is successfully ingested, the JSON file is deleted from the folder.

If the client is running, the user is logged out of the PTT-Pro and Voice applications returned to the PFM Sign-in screen and the Profile Client restarts.