XML provisioning can collect custom attributes based on your Android device details. You can use custom attributes for advanced assignment criteria for product provisioning, as lookup values, and for automatically moving devices to organization groups based on these attribute values.
- Simple XML File Push (Tags) – You push an XML file with a pre-defined attribute value and the Workspace ONE Intelligent Hub reports it back to the console, functioning like a device tag. You can build these tags into products. While performing other actions, the product then adds an attribute that tells the console that those actions have been taken. You can then use these values for product assignment, OG assignment, and lookup values.
- Hub Directory Save – You can code an internally-developed application that saves an XML file with the attribute values to the Workspace ONE Intelligent Hub directory. The Hub then reports these values back to the console. The benefit of this scenario over the first scenario (Tags) is that, because you are using the Workspace ONE Intelligent Hub, which collects information from other apps, you have access to information you would not ordinarily have.
- Navigate to Android as your platform. and select
- Create an XML provisioning file.
See Create an XML Provisioning File, Android, Win7, WinRugg. The manifest must include an action to download the XML file to the Zebra device location /enterprise/usr/attributes.
For non-Zebra Android devices, the XML file location is /sdcard/Android/data/com.airwatch.androidagent/files/attributes/.
Upon receiving the XML file, the Workspace ONE Intelligent Hub for Android creates a custom attributes output file.
During the next check-in with AirWatch, the Workspace ONE Intelligent Hub sends the output file to the Workspace ONE UEM console.
Once the XML file installs, the custom attributes requested in the file exported to the console. These values display in the console in the Device Details page under custom attributes. The Device Details page enables you to view the name of the attribute and the values returned from each device. These values can be used to create product assignment rules using the Custom Rules system.
<?xml version="1.0"?> <attributes> <attribute name="attribute 1" value="value 1"/> <attribute name="attribute 2" value="value 2"/> <attribute name="attribute 3" value="value 3"/> </attributes>