Android Smart Device Custom Properties

Version 3

    Verified Product Versions

    Avalanche 6.1Avalanche 6.2

    This Document is designed to walk you through creating an Android Custom Property Payload and how to edit a device’s individual custom properties.


    Known limitations:

    Custom Properties only work with enablers that are and newer enablers communicating to Avalanche 6.2 Premise and Avalanche AOD after the 2016 Q3 patch.

    If you have a Custom Properties payload that is applied to a device and you manually edit the property within the device view, the device will sync and replace the manually edited property with the custom property within the payload.



    First we will begin by creating a new Payload and selecting Android from the platform section. You will see Custom Properties as a selectable payload type. Click Custom Properties



    A new window will be displayed. As all other payloads you are required to provide a unique name. Next you will click on the + icon.



    A new window will be displayed. You will be given the option to edit the Property’s Group, Name and Value. The Group name is optional and is provided for those who wish to creature further structure in their property identification.



    Any of these fields can use any character that is alphanumeric. No special characters. In this instance we will be creating a location identification property with the name being the state and value being the city. By default the create property action is selected. Leave it and press save.



    As you will see an error will pop up if you use special characters or spaces.. We will change South Jordan to SouthJordan. And hit save.



    Once saved we are returned to the previous screen and we can see that our new custom property has been added to the list. The process for creating a delete record is very similar. Press the plus sign again.



    In this example we will create a delete property record to ensure that any other locations would be removed from a device in case a device moves. Fill out the location information again and select the Delete Property Action. Then hit save



    We will now see two entries within the payload. One to create a property a second to delete a property.



    We will now create a Smart Device profile as normal. Provide name and select the Custom Properties Payload. A new Section for Custom Properties has been added to this list.




    Once you have saved the Profile run a deployment and let it complete. Once the device has finished syncing you will be able to go to the Inventory and select your device. Within the Device View of the inventory, move to the Properties section. You can filter the columns by Data Type to see all configurable properties. Before a device has finished syncing you will be able to see the pending values.



    Any Device that has an enabler older than will not be able to receive customer properties. Any Devices will just show values in the pending column.


    If you find that you need to update a specific device’s customer property select the check box to the left of the Property Group. Then click on the pencil icon



    You will be shown the old applied value and can then add a new value.



    The Console will then show the new value within the Pending Value column until the device has synced and downloaded the files.



    Once the device has synchronized the enabler drops a customproperties file into Enterprise/usr/persist (for zebra devices). This file is similar to rugged devices with the files.