Release Notes

Managed IoT Cloud is usually released every three weeks and in this section you can find the release notes for all releases.


Version 2.40 (2019-04-16)

Important notices

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/

Features

New View Mode picker

The View Mode picker have been upgraded with new design and functionality to support all View Mode categories: Root, Domain and Personal.

Advanced permissions (beta)

Continued work with advanced permissions APIs. In release 2.40, new privileges for Domains and User Management have been added. For details, please see the documentation at https://docs.telenorconnexion.com/mic/rest-api/permissions/

Minor improvements and corrections

Numerous minor enhancements and bug fixes are delivered by the new release, including:

  • Improved performance of rule engine
  • Improved filtering on resources in All Things List
  • Improved validation of data in the user API
  • In GraphQL we now allow sending resource data type to ensure filtering on the right data type
  • Fixed issue with republishing of data when data was reported as an array.
  • Fixed issue with App Board Gauge widget showing multiple colors
  • Fixed issue with Thing creation in Thing batch create in case the Thing ID already was taken
  • Fixed issue in App Board Thing batch create where double clicking created two batches accidentally

Version 2.39 (2019-03-26)

Important notices

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/

Features

GraphQL general available – Conclusion of beta period

We now conclude our GraphQL beta period and make it general available. The development of the GraphQL API have been ongoing during several releases, and the API has been open for exploration in the beta state during this period. Several Customers and Partners have kindly tried out the APIs and contributed much appreciated feedback that has been incorporated in the API design with this release. Thanks!

During the beta period, we have gradually started using the new APIs for our own App Board and validated that the API is useful and stable. In 2.39 we are therefore releasing the GraphQL APIs for production use. New endpoints and additions will be added as we continue to evolve the MIC product.

Please note that certain endpoints are intended for App Board only. These APIs should not be used for other purposes by external developers, as they may be locked down in the future.

The release includes a few minor updates, wherof the most important is added support for externalId as identification parameter in thing and allThings queries.

Once again, thanks to all of you who have contributed valuable feedback during the beta stage!

App Board View Modes - second generation

In this release we introduce a whole new generation of View Mode. We will improve the functionality over a few releases with the goal to make View Modes at the same more flexible and easier to use.

Functionality introduced in version 2.39

  • Personal View Modes - a user can now create personal View Modes, not visible to other users
  • Domain specific View Modes
  • Default View Mode - you can now specify which View Mode shall be default for all users who not have done an active choise
  • A new buttom to create a new View Mode “+ VIEW MODE”
  • Editing the View Mode is split into two separate actions. The existing “pen” symbol is now used to save the View Mode and edit the View Mode meta-data. A new symbol is introduced to arrange the dashboard and its widgets (this used to be under the pen symbol too) and saving the current View Mode under the same name. To save the View Mode under a new name, the “pen” has to be used.

From before we have support for General View Modes. They are connected to the Thing Type and available to all users with access to the specific Thing Type. With the 2nd generation of View Modes any View Mode saved on the Thing Type domain level will be a General View Mode.

The Thing Type API have been updated and View Modes are not available in this API anymore. The corresponding documentation have been updated.

Improved webhook retry functionality

We have improved the webhook retry functionality to enable both better scale and usability. For a webhook you can now specify whether to activate retry or not. When activating, you specify these parameters

  • Interval (sec) - The time before the first retry attempt (1 to 600 sec)
  • Backoff rate - A multiplier (1-4) by which the retry interval increases on each attempt
  • Max attempts - The maximum number of retry attempts (1 to 5)

Webhook retry is available in both the API and App Board. A supporting time scale GUI has been added in App Board to visualize the retries and simplify configuration.

Minor improvements and corrections

Numerous minor enhancements and bug fixes are delivered by the new release, including:

  • Improved user experience in App Board when setting a value for a Thing resource. The arrow indicating setting is in progress will be shown until the Thing confirms the set resource command by setting desired state to “null”. A tooltip for the arrow will say “Waiting for Thing to mark setting as accepted”.
  • Fixed App Board issue with capital letters in Thing Types search function under Settings / Thing Types.
  • Fixed App Board issue with deleting a Thing image.
  • Fixed App Board issue with sorting of in resources dropdown selection in Rule create/edit.
  • Fixed App Board issue with domains dropdown in filter being misplaced during half a second.
  • Fixed issue with tcxn convention resources of the old format not being supported in some areas.

Version 2.38 (2019-03-12)

Important notices

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/

Features

Conditional coloring of Gauge widget in App Board

With the new release, it is possible to control the color of the Gauge widget using a banded-criteria, e.g. 0-33=Green, 33-66=Yellow, and 66-100=Red.

The configuration is accessed in the settings dialogue for any Gauge widget.

Advanced permissions (beta)

Continued work with advanced permissions, including user interfaces and APIs. For details, please see the documentation at https://docs.telenorconnexion.com/mic/rest-api/permissions/

In release 2.38, new privileges for Permissions, Thing Types, Thing Groups, and Thing Jobs has been added.

GraphQL (beta) – New endpoints and conclusion of beta period

GraphQL endpoints for System Management and Users has been added, please see the GraphQL documentation for details.

With this, the beta period for the GraphQL API is soon to be concluded, and the first production release is planned after next sprint.

Several Customers and Partners have kindly tried out the APIs and contributed much appreciated feedback that has been incorporated in the API design with this release. Thanks!

Minor improvements and corrections

  • Serialization of outbound SMS messages to make it possible to send large volumes of rule-based SMS messages even if the SMSC limits concurrency.
  • Harmonized validation in App Board and platform with regards to preventing domain names including slashes (“/”).
  • Updated documentation to reflect proper terminology for Nested Payloads and Nested Resources
  • New backend data structures for the App Boards view modes have been implemented, resulting in performance gains in this release, and setting the scene for functional additions in future releases.
  • Fixed issue that disabled rules where only visible to root-level users.
  • Fixed issue with the parameter “Protocol” not being properly reflecting the Thing edit dialogue in App Board.
  • Fixed issue with time zone support for timestamps in the GraphQL API and in App Board.
  • The parameter “IdentityId” is no longer required as an authorization header, and if used, it will not have any effect.

Version 2.37 (2019-02-12)

Important notices

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/

Features

Additional system information displayed in App Board About-page and in Manifest

In release 2.32, new AWS IoT end-points using the Amazon Trust Services (ATS) signed server certificates was introduced. This end-point is listed in the Managed IoT Cloud Manifest file and in relevant documentation (e.g. https://docs.telenorconnexion.com/mic/thing-api/).

Additionally, the system information displayed in the App Board About page has been expanded to include API end-point urls and other useful information.

API parameter to lock data types in Thing Type data model

The data model for a Thing Type in Managed IoT Cloud is automatically generated based on the observations sent from the Things. Every month, a new index holding the observation data is created. This sometimes had unwanted effects, i.e. if the first observation for a new month had a different data type compared to the data type recorded for the resource in the previous month.

To allow control of this, a new property, “lockMappings”, has been added to the Thing Type API. When this parameter is set to true, the data type mappings for the Thing Type is maintained over time, regardless of the data type used for the first observation of a specific month. If on the other hand, this property is set to false, the data type mappings of a resource could change for future indices, if the first observation in a new month is of a different type than what was used in the previous month.

Rules Event action now optional in App Board rule configuration

When configuring rules in the App Board, the “Event” action was previously attached to each rule by default, and not possible to remove.

With the new release, the event action is optional, and handled just like the other rule actions, that can be optionally added for a rule.

Please not that each rule need at least one action to be valid, and that rules with “trigger once” need to have an event with the “need acknowledgement” flag set.

Advanced permissions (beta)

Continued work with advanced permissions, including user interfaces and APIs. For details, please see the documentation at https://docs.telenorconnexion.com/mic/rest-api/permissions/

GraphQL (beta)

The GraphQL API is currently in beta, undergoing testing and validation in parallel with work to migrate the App Board to the GraphQL APIs. Customer feedback on the beta is of course welcome!

Minor improvements and corrections

  • The REST API documentation has been reviewed and updated with a number of minor corrections and clarifications.

Version 2.36 (2019-01-29)

Important notices

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/

Features

Advanced permissions (beta)

Continued work with advanced permissions, including user interfaces and APIs. For details, please see the documentation at https://docs.telenorconnexion.com/mic/rest-api/permissions/

GraphQL (beta)

The GraphQL API was released as beta in the previous release, and is currently undergoing testing and validation, and customer feedback on the beta is welcome. Please see the release notes for 2.35 (https://docs.telenorconnexion.com/mic/release-notes/2_35/) for further details.

In 2.36, an enhanced mechanism for refresh of the auth-token in the front-end client have been implemented.

Minor improvements and corrections

  • Fixed padding issue in set password text.
  • Review of API documentation.
  • Fixed validation of nested resources in rule action in app board.
  • Fixed re-rendering of Map widget in historical trace mode at change of the period picker.
  • Optimized performance of filter components for large sets of data.
  • Fixed memory issue that occurred when using analyser for data sets with incoming MQTT messages.