Esper’s latest release is about giving our customers greater control and efficiency. It includes controls for end user experience, tools for even more streamlined Android provisioning, and improved access to contextual help in the flow of work:
- Configurable User and Admin mode in Esper Settings app via Console
- Use Preloaded/ In-built Apps as “Kiosk Mode Application”
- Contextual Help added to the Apps Section
- Added Enable/Disable Power Button for Knox-Enabled Samsung Android via Device SDK
- Updated Default Install Action for Google Play Apps
1] Configurable User and Admin Mode in Esper Settings App via Console
Please note: This feature update will be applicable only if your devices are on the latest DPC version.
We recently added the ability to customize the custom Esper Settings app using JSON settings. We’ve now implemented configuring Esper Settings using the Console’s GUI in the Provisioning Template and a Compliance Policy to change Esper Settings for deployed devices.
Now, Esper Settings can be configured to include both a user role and a password protected admin:
- User Mode: No Password Required to Access Settings
- Admin Mode: Password Required
Customers can now select which settings actions are exposed to device users and admins. For example, you could choose to let users add new Wi-Fi access points while making Factory Reset available to only admins.
This feature update is visible to customers in Esper’s cloud console viaProvisioning Templates > Compliance Policy.
If you’ve previously created a custom Esper Settings app without a password, the on-device experience will be unchanged until you’ve pushed out an updated Compliance Policy with the new desired Esper Settings configuration. Otherwise there will be no impact to your current device fleet.
2] Use Preloaded/ In-Built Apps as “Kiosk Mode Application”
Customers can now set one of the preloaded or in-built apps to single-app Android kiosk mode. The provisioning template has been updated to include this option. To do so, you’ll need the preloaded app package name when creating or modifying a provisioning template.
If the app isn’t preloaded to a device using the same provisioning template, the device will successfully provision in multi-app mode.
3] Contextual Help Added to the Android Apps Section
We’ve expanded the contextual help available within Esper’s Apps section to showcase best practices in the flow of work.
Just look for the question mark next to any area where contextual help is available.Over the next few releases, we’ll be expanding and adding more contextual help to other parts of the Esper console.
4] New Enable/Disable Power Button Support
Esper has exposed a new function in our Device SDK for Knox-enabled Samsung Android devices. Now, you can use the Esper Device SDKto call the Knox API to enable or disable the device power button.
If you want this enabled in your fleet, submit a ticket.
5] Updated Default Install Action for Google Play Apps
The default install action for Google Play apps in the Esper device provisioning template is now set to “Post Provisioning”. Previously our customers found that some Google Play Store apps were slow to install, freezing the provisioning process while customers waited for the install to complete.
Now, the default is to complete provisioning and then install any and all Google Play Store apps. You can of course change this behavior by selecting “During Provisioning” in your Provisioning Template Apps section if you wish to have the install occur during provisioning.
Bug Fixes and Improvements
- The “Take screenshot” option is now disabled for offline devices.
- An improved option to quickly rename devices or add device tags can be accessed through the Actions column of the Devices & Groups section.
And, that’s it for DevRel 48. We’ll be delivering another round of new features and fixes in DevRel 49. Our next release is currently scheduled for the first week of December 2020.
Also, please share your feedback on how we can improve Esper in DevRel 49, 50, and beyond.