Andrey,
Most of the SDML are designed for Windows type of devices. You may try <<user.client.LocaleID>> or you may try <<user.deviceid>>.
I am not really sure if the <<user.deviceid>> was fully integrated as the documentation on this is lacking in SAP.
Starting from Agentry 6.0.32 see reference: Agentry Patch Notes 6.0.32 - SAP Mobility - SCN Wiki
AG-24058 - Change Android client to default to using server-generated device IDs
This feature may or may not be related to the SDML <<user.deviceid>> as it is purely used inside the Agentry core libraries called deviceID(). I am not sure if this is part of the openUI control where the deviceID() may be exposed. You may need to research the openUI section.
I believe this piece of code was replicated into Agentry 6.0, 6.1 and 7.0 (In theory copied into SMP 3.0).
The main comment of this is:
~~~~~~~~~~~~Start here~~~~~~~~~~~~~~~
- The device ID is now generated by the server, and stored on the client.
- Reseting the client using "Reset Everything" retains the device ID assigned by the server.
- Clearing the data from Android's --> Settings --> Apps will lose the server assigned device ID.
- Uninstalling the client will also lose the server assigned device ID.
- Losing connection during a transmit will still retain the device ID assigned by the server.
- Changing users will still retain the device ID assigned by the server.
This was tested with multiple transmits from multiple devices and the server's device logs show the same number of device IDs (updating the user information of the device ID when a user is changed on a device)
~~~~~~~~~~~~end~~~~~~~~~~~~~~~~~~~~
I have not really played with this but you may try it out (<<user.deviceID>>). Worst comes to worst it may not be supported as it is not part of any of our documentation in SMP 3.0 SDML document. It could only be a control inside the Agentry core libraries wherein when they use the deviceID() function it returns the Android device id. Again this may be openUI.
Hopefully somebody in the Agentry core of designers may expand on this subject matter. With respect to support, if it is not documented it is not supported. I gave my best shot at this question by providing the Agentry key bug number listed above from the release notes.
Hopefully somebody who is within the inner circle of development may shine in.
Best Regards,
Mark Pe
SAP Platinum Support Engineer