As deployments scale, managing store config files for handheld devices without cameras becomes tedious and challenging. Please implement a way to read VLink configuration via managed configurations.
https://developer.android.com/work/managed-configurations
Guest
For example, to associate an Android device with a specific V:Cloud store, a config file needs to be generated for each separate store and then deployed to the devices. This is a lot of manual effort and is prone to errors.
If the store ID and API key could be supplied via the customer's MDM, they could use existing automations and metadata to define the store configuration dynamically. It is likely that the store number is already associated to the handheld in the MDM, so it is also likely that can be easily set as a variable in a ManagedConfiguration.
Dear customer,
Could you please provide more information for this request?
1/ How will this idea help you ?
2/ Who will benefit ?
3/ Any relevant information that you can add to help us
Best,
Olivier
Dear customer,
Thank you for your idea.
I will check feasibility and efforts with the technical team and come back to you.
Best,
Emmanuelle