The new release of Bosch IoT Rollouts comes with the following new features:
User Consent Flow
The new user consent flow feature supports rolling out software updates to managed devices in compliance with the European Directive concerning contracts for the supply of digital content and digital services. In particular, it stipulates that the end user needs to be asked for consent for each software update sent to his or her device.
By default, when a distribution set is assigned to a target, Bosch IoT Rollouts directly exposes the artifacts to the respective targets via APIs. The devices then freely download these artifacts and flash themselves to complete the update.
In contrast, when the new user consent flow feature is enabled for the particular tenant, Bosch IoT Rollouts introduces an interim step where the consent of the end user of the device is requested for a pending software update. Only after such consent is granted can the devices proceed with downloading the artifacts and completing the update.
Once enabled, the user consent flow offers two scenarios – confirmation required (on assignment/rollout level) and auto-confirmation (on target level). The feature can be enabled and disabled at any time via both the Bosch IoT Rollouts UI and Management API on tenant level, but before you do that please check the Things to consider before enabling this feature.
Learn how to apply the user consent flow via the Management UI at:
Learn how to apply the user consent flow via the Bosch IoT Rollouts APIs at:
- Management API
- Device Management Federation API
- Direct Device Integration API
- Service Integration Event API
Service plan quotas via Management API
So far, it was possible to view metrics on the used and remaining service quotas, such as number of targets, software module types, target filters, rollouts, etc. only via the Bosch IoT Rollouts UI.
As of this release, you can already view the same service plan related quotas via the Management API as well. For that, you need to have
Find more information on the related methods at Tenant – system configuration – HTTP API.
- [MECS-18229] – Add missing triggerNextGroup API doc
- [MECS-17921] – Configure SuiteAuth and still enable CIAM access for AWS US1
- [MECS-18167] – Stabilize XMPP adapter in case of unhealthy host
- [MECS-18235] – Expose last action status code via Management REST API
- [MECS-18242] – New Management API endpoint for retrieving single action
- [MECS-18256] – Search Software Modules and Distribution sets by arbitrary substrings in Management UI.