The new release of Bosch IoT Manager comes with the following improvements:
Added cleanup of all data related to a service instance
Upon request, Bosch IoT Manager now deletes all existing database data regarding a particular service tenant. In addition, it also makes sure that no more such database data is added in the future due to delayed processing – for example from queues, further confirmations from devices, etc.
Added new scripting APIs
The following scripting APIs have been introduced in Bosch IoT Manager:
- Execution context API: provides methods for accessing rule/task attributes of the current execution and controlling the rule/task execution,
- Async HTTP Client API: provides methods for device management scripting, which can be used with REST calls.
All scripting APIs are available in the Groovy documentation.
Added action execution result dialogue in UI
Once an action called on individual devices has been executed, there will be a pop-up in the Bosch IoT Manager console showing the execution state and further details, if available.
Find out more in Device Information and Management.
- Fixed the bug causing some tasks and rules to fail to receive subscribed session events
Within the same service instance, tasks and rules may be created and may subscribe for events through different OAuth2 client access tokens. However, even though tasks and rules were visible through all OAuth2 clients in the scope of the same service instance, the task/rule events were not delivered if the respective task/rule was created with a different OAuth2 client than the client listening for those events. As a result of the fix, all events are now properly received.