To display only the features present on a particular device, select one or more filters from the SmartDocs bar below.
Input fields accept ENGLISH ONLY.
Queries from MX are not supported on Zebra devices running Android 11 or later. See alternative method.
The "SmartDocs" bar can customize this page to show only the features present on a particular Zebra device.
OSX, MX and Android version information for a device can be found in the Android Settings panel or by querying the device through ADB, EMDK or the MX CSP. More info.
The DataWedge Manager (DataWedgeMgr) enables control of the Zebra DataWedge data acquisition service for Android devices programmatically or through an Enteprise Mobility Management system. DataWedge allows any application on the device to acquire data from any of a device's input sources, including barcode scanners and MSR and RFID readers, and to manipulate the data as needed based on simple options or complex rules.
NOTE: This CSP is supported only on devices with DataWedge 7.6 or later.
Controls whether the device user has access to the DataWedge user interface and can change configuration settings on the device.
Note: Supported only on devices with DataWedge 7.6 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: ManualConfiguration
Controls whether DataWedge intent APIs are accessible by apps. Selecting this option can either prevent API access by all apps or permit access only by apps included in the device's "whitelist" as configured in AccessMgr. Learn more about Secure APIs.
Note: Supported only on devices with DataWedge 8.1 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: ControllingAPIs
Controls access to intent APIs relating to DataWedge device configuration settings such as the Get_Config
and Set_Config
APIs. See Access Manager for information about whitelisting. Learn more about Secure APIs.
Note: Supported only on devices with DataWedge 8.1 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: ConfigAPIs
Controls access to intent APIs relating to DataWedge notification settings on the device such as those for displaying scanner status and Profile information. See Access Manager for information about whitelisting. Learn more about Secure APIs.
Note: Supported only on devices with DataWedge 8.1 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: NotificationAPIs
Controls access to intent APIs relating to DataWedge queries such as those for retrieving scanner information and the DataWedge version on the device. See Access Manager for information about whitelisting. Learn more about Secure APIs.
Note: Supported only on devices with DataWedge 8.1 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: QueryAPIs
Controls access to intent APIs relating to DataWedge device runtime settings such as Switch_Scanner
and Switch_Scanner_Params
APIs. See Access Manager for information about whitelisting. Learn more about Secure APIs.
Note: Supported only on devices with DataWedge 8.1 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: RuntimeAPIs
This is the On/Off switch for automatic importation of DataWedge configuration files when they're pushed to the /enterprise/device/settings/datawedge/autoimport
folder on the device. When enabled (option 1), settings contained in a Configuration file take effect as soon as the file is pushed to the device if DataWedge is running when the file is received. If DataWedge is not running when a config file is pushed, settings take effect the next time DataWedge is launched.
SECURITY WARNING: Automatic importation of configuration settings can cause unwanted changes to device settings that result from pushing an unauthorized file to the device. Select "Turn Off" (option 0) to prevent unauthorized changes to the DataWedge configuration.
Android 11 Note: Due to Android Scoped Storage Restrictions, files CANNOT be deployed using an EMM system to the internal (/enterprise/device/settings/datawedge/autoimport
) folder or to removable device media.
Zebra recommends using/enterprise/device/settings/datawedge
OR/data/tmp/public
device folders and updating deployment paths accordingly.
Note: Supported only on devices with DataWedge 7.6 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: AutoImporting
Controls whether Configuration files can be delivered to DataWedge by other apps on the device using intents.
Note: Supported only on devices with DataWedge 7.6 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: ApiImport
Used to enter the name of a file on the device containing configuration settings to import into DataWedge.
Input value rules:
DataWedge supports the importation of Config files (datawedge.db
) and Profiles (dwprofile_profilename.db
) to devices delivered through commercially available Enterprise Mobility Management (EMM) systems.
Zebra recommends using FileMgr to download or copy data configuration file(s) to the
/enterprise/device/settings/datawedge/autoimport
or/storage/emulated/0/Download
folder prior to calling DataWedgeMgr.
IMPORTANT: Turn off the Auto-importing option if file(s) are to be copied to/enterprise/device/settings/datawedge/autoimport
.
RECOMMENDATIONS:
.db
files so that DataWedge file procedures are not impeded./enterprise/device/settings/datawedge/autoimport
folder; access to the /enterprise
folder and its subfolders will be restricted on devices running Android 13 and later. Note: Supported only on devices with DataWedge 7.6 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: ConfigurationFile
Requires:
- MX: 9.2+
Controls whether the NextGen SimulScan template file entered in the NextGen SimulScan Templates parameter is imported to the device. WARNING: If a template is imported with a name matching a file already the device, the existing file is replaced.
Note: Supported only on devices with DataWedge 8.0 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: NGSimulScanTemplates
Used to enter the full path and name of a NextGen SimulScan template file on the device to import into DataWedge.
Input value rules:
Note: Supported only on devices with DataWedge 8.0 or later.
Status: On devices running Android 13 and later, this feature is accessible only through non-XML barcodes or .bin files generated by StageNow.
Parm Name: NGSimulScanTemplateFile
Requires:
- MX: 10.0+