Esper has been updated to DevRel 22.
- Pipeline– The new Esper Pipeline feature enables users to ensure smooth deployment of actions (including app installation) on large fleets of remote devices by defining stages constituting of operations, installations, tests, and wait time that are executed when a defined trigger occurs, such as when a new version of the app is uploaded. Only after succeeding in the above stages on test devices will the action get applied on production devices, hence ensuring a smooth deployment via a pipeline of stages. The initial version of the Esper Pipeline supports only the app installation operation and requires a 5 second or more break between the deletion of stages.
- List View in Devices– When the number of devices in a fleet crosses over into the 100s it is hard to view or sort them in the device tile view. With the new ‘List View‘ users can easily see a list of all devices available on the dashboard along with device information columns including online/offline status, serial number, group name, Android version, and andy tags.
Search by device name can be used without having to enter into the device details page to get detailed information about each device. Let us know what additional features you’d like to see us implement in this area by leaving a comment below.
- WiFi SSID in QR Code– In order to make the 6-tap provisioning process easier, we are introducing the capability to include the required WiFi credentials in the QR code generated via a Device Template. After reading the QR code, the device automatically connects to the WiFi access point using the SSID and password entered for the template.
Below is the template section where the WiFi access point login information can be preset. The bottom section is where you can see the heading “Ability to add wifi credentials to the QR code”
User may enter wifi SSID, password and choose the security type in the dropdown shown as below:
Upon reading the QR code, the device will automatically connect to the WiFi access point if it is available.
- Description Box added to Template and Policy– Dashboard users and admins create policies and templates in a context. For example, creating a template to define the device behavior for a set of devices deployed in Burbank warehouse, or a compliance policy for any device operating at retail outlets in Texas. The Description Box enables the context to be associated and saved with Compliance Policies and Templates.