Release Notes

Version 2.35 (2018-12-11)

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 API (Beta release - minor updates and additions should be expected)

We now release GraphQL (beta) as a new Cloud API to interact with MIC. GraphQL is a query and manipulation language for API data. It provides a powerful and flexible approach to building web clients and applications. Included in the beta release is graphiql which is an in-browser IDE for exploring all available queries and mutations. To read more about GraphQL and get an intro to queries and mutations: https://graphql.org/learn/queries/

Note that changes to the API can be expected and end-points will be added. Please email developersupport for questions or feedback. First version of documentation is available on http://docs.telenorconnexion.com/mic/

GraphQL and REST API will exist side by side.

NOTE! One GraphQL query may correspond to multiple requests (Cloud API Requests, which is a pricing component of MIC). Details can be found in the online documentation.

Advanced Permissions (under development, minor API changes and additions should be expected)

Minor updates in the Permission API

• Changed method from PUT to PATCH for roles endpoint
• Changed method from PUT to PATCH for privileges endpoint

Please see the online documentation for further details about the Permission API.

Minor improvements and corrections

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

• Improved identification of Things in the NB-IoT integration by ensuring the MIC ThingID is present in the NB-IoT integration server
• Fixed issue with URL in the set password email - the token in the URL is now URL-encoded
• For Resource settings fields for dropdown (in Thing Type management in App Board) we have optimized validation to enable setting any values for the resource
• Fixed issue with set resource in Rules with Observation timestamp in the condition

Version 2.34 (2018-11-20)

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

User API can return the current logged in user

We have added an endpoint WHOAMI for getting user information about the currently logged in user, e.g. user name, the users role and domain. No input is needed, else but the already known user session credentials.

Advanced Permissions (under development, minor API changes and additions should be expected)

New permission objects

• Permission object for the Observations API, currently implementing the Read permission for secondary domains.
• Permission object for the Thing Management API, currently implementing the Read permission for secondary domains.

New end points in the permission API

• Added end point for GET_ROLE.

Please see the documentation for further details about the new API endpoints and permission objects.

Minor improvements and corrections

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

• A new validation to prevent dash ("-") in thing names has been introduced.
• Added functionality to allow setting nested resources from App Board.
• Added functionality to allow using nested resource in the set resource rule action.

Version 2.33 (2018-10-30)

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

Integration with Telenor’s NB-IoT Network in Norway

With the latest release, Managed IoT Cloud offers integration with Telenor Norway’s nationwide NB-IoT network (https://www.telenor.com/media/announcement/telenor-launches-nationwide-iot-network-over-4g).

Things attached to the NB-IoT network can be configured to communicate securely (both uplink and downlink, including optional payload transform functions when relevant) with Managed IoT Cloud using an intuitive graphical user interface. This allow users to capture, explore and build applications based on their IoT data with minimal efforts and short time to market.

Advanced Permissions (under development, minor API changes and additions should be expected)

Several new endpoints have been added to the Permissions API.

• CREATE_ROLE
• GET_ROLE
• LIST_ROLES
• UPDATE_ROLE
• GET_METADATA

The following endpoints have been renamed.

• CREATE -> CREATE_PRIVILEGE
• UPDATE -> UPDATE_PRIVILEGE
• READ -> GET_PRIVILEGE
• LIST -> LIST_ROLE_PRIVILEGES

In addition, the concept of roleDomains has been added to the Permission API and functionality. The roleDomain parameter allows a role to exist in a particular domain and its sub domains only.

Please see the documentation for further details about the new API endpoints and the roleDomain concept.

Minor improvements and corrections

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

• Enable Domain settings to be set to “null” to clear the settings for a specific domain
• Fixed issue with Thingtype meta data editor
• Added limitation to only list the first 100 search results in the Domain drop down in the App Board user management interface.

Version 2.32 (2018-10-09)

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

Set limitations per domain - API only

This API enables an administrator with root access to set limitations per domain in terms of

• Number of Thing Types for a domain
• Number of Things for a domain
• Number of Users for a domain

When adding, updating or moving an item, a check will be done to ensure no limit is exceeded. This includes checking the domain tree upwards to the root domain.

This enables control of resources and costs for each domain level and can be used e.g. in packaging various end customer offerings.

Advanced Permission - Allow /deny access to App Board - Beta release API endpoint

We now introduce a feature to toggle the access to App Board. It is part of the new Advanced Permission structure, meaning you define a role with deny App Board access and give this role to the users that not shall have App Board access. This can be used e.g. when a custom application is developed for end users and you want to deny access to App Board and direct the users to the custom app only. A user trying to login to App Board will get a message that the user is not allowed to use this application (App Board).

The Beta release means you can start piloting this functionality, but there may be changes/updates to the API before it is fully launched.

Additional IoT end-point

Google, Apple and Mozilla have announced that, starting October 2018, they will deprecate trust in all Symantec root certificate authorities (CAs), including the VeriSign Class 3 Public Primary G5 root CA used to sign AWS IoT Core server certificates.

The decision to no longer include these CA certificates will disrupt mobile and web applications that rely on the certificate trust stores provided by their mobile operating systems or browsers.

AWS IoT now provides an additional AWS IoT end-point that present Amazon Trust Services (ATS) signed server certificates. In order to use the new ATS CA you will have to change the IoT end-point url in your mobile or web application to point to the new ATS url.

The Manifest will contain two URLs: IotEndpoint and IotEndpointATS. The current endpoint called IoTEndpoint in the manifest can still be used by Things though AWS will keep the current IoT endpoint serving VeriSign CA until further notice.

Minor improvements and corrections

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

• Enhanced sorting on virtual resources in the Things list in All Things Dashboard. If no data exists for the resource, sorting will be disabled for that resource.
• Fixed issue in Analyze export function causing repeated data in the export file when exporting non-aggregated data.
• Fixed issue with new resources not being identified under certain circumstances.
• Fixed issue in file browser when searching and no Thing was found.

Version 2.31 (2018-09-18)

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

Domain Level Branding

In the branding configuration of the App Board, a domain selector has been added to allow configuration of domain specific branding. For a logged in user that belong to a domain with specific branding, the logo and color is affected. For subdomains without branding specified, the nearest parent domain with branding configured will be used. Please note that the root level branding will always be used on the login screen.

As before, root level access with read/write permission is needed to configure branding settings.

Different graphical marker for last received coordinate when the map widget is used in “historical trace”-mode

A different graphical marker for the last received position is now used when the map widget is viewed in “historical trace”-mode, to make it easier to distinguish the last known position from the historical data.

Configurable interval for aggregates

In widgets displaying aggregated data (e.g. time series widgets in Thing and Thing Type dashboards), the aggregation interval can now be configured. The default aggregation interval is 3 hours, but this can be adjusted to suit the characteristics of the specific resource and the intended usage of the widget. This settings is useful for scenarios where the frequency of the data is known and can be taken into consideration – i.e. using a 24h aggregation for cyclical data with the period of 24 h will result in a loss of potentially valuable information.

Status endpoint in the API for the TCP Proxy over MQTT

A new API endpoint for querying the status of a proxy connection based on thing name has been added. The information returned by the status call includes bytes read/written, the ip-address of the connected device, and the used port.

Logging of observations with unexpected data type

If a thing sends an observation using the wrong data type (the data type for observation differ from the resource’s configuration in MIC), that data is not indexed. With the new release, such errors are published on the Event API, and can be browsed using the Event user interface in App Board.

Minor improvements and corrections

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

• Added “de-bounce” delay in the thing search field in the file browser (to avoid triggering a new search for each key-press).
• Fixed issue with rule descriptions sometimes not being properly indexed.
• Added optional query scope parameter “thingTypes” to the Observation Find API, to allow limiting the query to a specific Thing Type and its underlying index.
• Removed now obsolete “password” parameter from documentation for User API Create.