Version 2.27 (2018-05-22)
Managed IoT Cloud has now been adapted to drive compliance with GDPR (EU’s General Data Protection Regulation) which will enter into force on 25 May 2018.
In addition, functionality simplifying for our customers to fulfill the GDPR requirements has been added, including
- Storage retention settings (v 2.25)
- Generic mechanism for user consent or agreement acceptance for new users (v2.26)
Technical documentation available online
All technical documentation for Managed IoT Cloud, including API specifications, Release notes and Getting Started Guides, are available online: https://docs.telenorconnexion.com/mic/
Full App Board support for the File API, including New File Browser
The new File Browser replaces the old Things file browser. Here all files in MIC can be uploaded, viewed and deleted. It uses the new capabilities in the File API released in v 2.26. This includes the following four different file buckets
- Public – for files that should be publicly available.
- Root – for files that are relevant at the MIC instance-level.
- Thing Name – for files related to a specific Thing.
- Thing Type – for files related to a specific Thing Type.
In addition, App Board has been upgraded to fully support the enhanced File API
- Files widget (update and delete file will be enabled in coming version)
- Image files in Process widget
- Image files in Thing Summary
- The logo file in Branding
Existing files will be migrated in relation to the release roll-out
App Board support for storage retention time
In System Management menu (under Settings top menu) storage retention can now be specified in number of months. Retention can be specified separately for Raw Observation Retention (the S3 data lake) and Indexed Observation Retention (the Elasticsearch Observation index) in order to differentiate long term storage and observation indexed for fast search and analyses. Retention for the indexed data cannot be set to less than retention for the raw data.
Changes to storage retention can only be made by root users with full system access and the user needs to provide the user password to proceed with the changes. As default, retention is not enabled (i.e. by default, no data is deleted automatically).
IMPORTANT NOTE: Retention shall be used with great care - data older than the retention policy will actually be deleted and cannot be recovered.
Minor improvements and corrections
Numerous minor enhancements and bug fixes are delivered by the new release, including:
- Updated and improved documentation on Elasticsearch 5
- Added support for more status codes (successful status) in webhooks
- Fixed issue with response message from API GW when calling replace certificate
- Fixed issue to ensure all resources are deleted when a Thing Type is deleted
- The API for Storage Retention has be updated to one endpoint instead of two separate for raw data and indexed data