Release Notes

Version 2.45 (2019-09-17)

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

App Board support for including all event data when using webhook

An option to forward “all event data” for a triggered rule using the webhook action has been added to the rule configuration view in App Board.

This function was previously available only when using the API.

Default limit for the number of coordinates in a geofence rule

When configuring geofence rules, two modes are available: 1) Point of interest (a circle defined by a center coordinate and a radius) and 2) Perimeter (a closed polygon defined by a number of coordinate points).

With the new release, the maximum number of coordinates that can be used in the latter mode has been limited to 25, to cap the computational complexity of rule evaluations. The limitation is highlighted in the App Board user interface.

Furthermore, the concept of a closed polygon implies that the minimum number of coordinates is 4, where the first and last coordinates are equal (i.e. a triangle).

Added REST API header to allow browser caching for certain responses

The Access-Control-Max-Age header have been added to REST API OPTIONS-responses, to allow browser caching of these responses and thereby avoid unnecessary API requests.

Minor improvements and corrections

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

• Fixed issue with the thing simulator where the specified maximum value of a random integer was never (or very rarely) generated.
• Fixed issue with rendering of domain name, description and meta data in widgets.
• Fixed issue in App Board where the “Enable retry” for webhook rules could not be disabled if once enabled.
• The conditional coloring of map markers is now optional (if no configuration is added to a map, the blue default marker will be used).

Version 2.44 (2019-08-27)

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

Thing list made available as a generic widget

In the App Board, a configurable list of the available things is displayed in the all things and thing type views. With the new release, this list view has been made available as a generic widget as well, giving the user the option to combine lists and other widgets such as aggregations and histograms in relevant dashboards.

The tab based navigation to the predefined thing list will remain for the time being, but the longer term intention is to remove the list tab from the user interface.

Color coding of Thing map markers

The Thing Markers in App Board Thing Dashboard and Thing Type Dashboard can now be color coded according to the value of a selected resource. This enables the Thing Type map to show e.g. all lamps that are turned on with yellow Thing markers and all lamps that are turned off with grey Thing markers.

The functionality is enabled in the widget setting by designing a list of criteria and its respective color for the resource selected (also the TCXN convention online status flag can be used).

Improvements and corrections for the new thing simulator

In the user interface for the new thing simulator (the UI that allows you to define your own payload and message frequency, please see the release notes for 2.42 for further details) a more intuitive behavior for the browser back button has been implemented in addition to a back button in the user interface. Moreover, a few minor changes to the user interface for the simulator are included in the new release.

To prevent that the simulator is mistakenly used to create additional resources in the data model for existing, “real-world” thing types, the create resource privilege can be used to lock/unlock the add resources button in the simulator user interface. Please note that this privilege can currently only be accessed using the permissions API. Also note that to a Thing Type only having simulated Things, the add resources button is available.

Clarification of that UTC time zone is used for data exports

In general, time stamps in App Board are rendered using the client’s local time zone. However, in the data export user interface, timestamps are rendered as UTC to make it easier to relate to the timestamps in the exported data. With the new release, the UTC-based timestamps are more clearly highlighted in the user interface and in relevant API documentation.

Early Access Environment

In this release we have enabled an Early Access Environment for MIC, intended to be used by customers and partners for testing and verification of coming features and updates. The environment will typically be updated 3-4 business days before the actual release becomes general available in production environments.

If you would like to have access to this environment, please contact Telenor Connexion SOC (technicalsupport@telenorconnexion.com) with name and contact details (including email) of the person who will be in charge (owner and administrator) of your Early Access Environment and we will set up a domain for you and a admin user. The address of the environment is https://staging.mic.telenorconnexion.com/ and the Early Access Environment is offered at no additional cost to commercial MIC customers in production. Telenor Connexion will have the right to limit use, if the environment is used outside the intended scope, misused or used with excessive workloads.

Rule engine optimizations

An updated queueing mechanism underlying the rule engine has been implemented to safeguard scalability and performance.

Minor improvements and corrections

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

• The counter displaying the number of things included in a data export sometimes displayed the wrong number due to a cache issue, which has now been fixed.
• The GraphQL documentation covering the newly added data export functions has been updated and improved.
• The rendering of labels for nested resources in Analyze has been corrected.
• Fixed issue with listing of rules that were created by subdomain users

Version 2.43 (2019-06-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

Data Export - Adding jobs detail view

In this release we add a detail view for a job. In App Board under Settings/Data Export, click on the export job name to see the detail view for this job, including the schedule setting, selected Things and resources. In this view, you can also delete the job. Please note that deleting a job will also delete all its associated executions (files), so please make sure to save all files you want to keep before deleting the job.

The App Board supports definition of the most commonly used schedules. More complex scheduling criteria can be defined using the API, and if this option is used, the schedule in the job detail view will be displayed in the API syntax (AWS cron expressions), as explained here https://docs.telenorconnexion.com/mic/rest-api/observation/#create-export-job.

Improved UX in App Board

• The Set resource dialog box now more clearly shows reported value and the desired value you are about to set. The reject set resource dialog box have similar improvements.
• Setting of a resource is now available in the resource overview widget by clicking the Set button to the right in the table. As before, the resource can also be set from the single resource widgets.
• The resource overview widget has also been enriched with +WIDGET buttons to the right in the table in order to speed creation of new widgets for the resources.
• Rules list now have delete buttons to the right instead of checkboxes.

Thing API - Added Identified signed URL call

The GetIdentifiedSignedURL API call is an addition to the existing GetSignedURL. The new call allows you to specify an ID together with your request. This can be used to ensure identity of the signed URL request when making several requests almost simultaneously.

Minor improvements and corrections

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

• Fixed validation issue in the Thing Simulator in App Board
• Improved ordering of very frequent, time stamped, MQTT messages (several messages within 1/10 of a second) containing updates for the same resource.

Version 2.42 (2019-05-28)

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

Thing Simulator in App Board

A new simulator that can generate thing data for e.g. test, piloting and configuration purposes is introduced in the new release. This enables you to design a Thing Type, configure what resources it shall have and instantly start a simulation of a Thing of that Thing Type by generating data for it. The new simulator can be used to generate observations for Things of any Thing Type. However, data cannot be generated for real Things, i.e. being actual physical Things with a certificate.

To use the Simulator, create one new thing (“Create batch” mode turned off) and select the “Allow simulation” option.

When viewing the new thing in the Thing dashboard, a “play” icon will be visible at the top of the dashboard. Clicking this button (right-click if you want to open the simulator in a new tab or window) will bring up a payload editor.

The payload editor will list the current resources for the thing type, if any. Selecting an existing resource with a supported data type will bring up options for how to generate data for that resource.

Additional resources can also be added to the payload. Please note that new resources that are appended to the payload and sent to the platform will permanently be added as resources for the Thing Type, i.e. reflected in the data model for that Thing Type.

The frequency of the messages can be configured at the top of the editor, and the play button will start the generation of simulated data. Generated data will be sent using the selected frequency until the stop button is clicked, or until the browser session is terminated.

Scheduled Data Export (beta)

In the previous release, instant data export was introduced (in beta, pending e.g. a price model). In the new release, a scheduled variant of the data export is added to this beta.

When selecting the export button in a Thing or Thing Type dashboard, a wizard is presented. In the first step, the resources to include in the export are selected. In the second step, the option for scheduled or instant export is introduced. In the scheduled mode, the user gets to define a weekly or a daily schedule for when the job should be executed. Optionally, the user can also configure the relative period for which data should be exported (by default, the reporting frequency will used to derive the period for which data is exported).

Both instant and scheduled jobs can be viewed in the settings -> data export section. The presentation separates “Jobs” (the definition of an export) and “Executions” (the generation of the export file, potentially repeatedly as per the schedule) in two tabs.

Scheduled jobs can be either enabled or disabled, and the current status is represented by a toggle in the App Board user interface.

Advanced permissions (beta)

The advanced permissions beta have been appended with the possibility to address domains recursively – i.e. one domain and all of its subdomains. The option to apply permissions to a domain recursively is available for all permission objects except ThingPubSub, that is always interpreted recursively. Please see the API documentation for details.

Minor improvements and corrections

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

• A batch mode for creation of MIoT things (subject to configured integrations) has been added.
• Improved naming of data export files, as well as other minor adjustments to the data export functionality.
• Update of advanced permissions roles endpoint to allow empty role descriptions.
• Added support for backdated observations (that has been saved at the time of export) in the data export.
• Removed misleading error message when approving new user in the signup flow.

Version 2.41 (2019-05-07)

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

Instant Data Export

With Instant Data Export you can export large amounts of data for treatment and analysis in third party applications and tools, e.g. for business intelligence or machine learning. The export is done as a batch job and can be initiated from either API (REST and GraphQL) or App Board. In App Board there is a new export symbol in top of the Thing Type Dashboard and Thing Dashboard that lets you select what resources to include and the time interval for the data content to export. The batch job creates an export data file in .csv format that can be found and downloaded under Settings / Data Export. Instant Data Export is launched in Beta version, for limited and non-commercial use. There is an additional cost associated with this functionality and the price model will be communicated when Data Export is general available.

Resource overview widget

A new widget is introduced to enable quick listing of all resources of the Thing Type. The list will show Resource name, last reported value, last update, data type, and resource metadata. With this widget you can easy and with almost no configuration, get a full overview of the Thing and status of all its resources.

Domain search improvement

Domain search in App Board now is a wildcard search within the domain patch, meaning it searches on the entire domain path and presents both the domain and the subdomains in the result. E.g. searching for “domainA” will also show “domainA”, “domainA/subdomainAA”, “domainA/subdomainAB”, “domainA/subdomainAA/subdomainAAA”, as these are all the subdomains of domainA in this example. Before this improvement, only the domain itself was presented, not the subdomains.

Minor improvements and corrections

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

• Fixed issue with domain ID containing the space character for some customers, which from now on is prohibited.
• Fixed issue that the view mode edit button was not available under certain circumstances.
• Fixed issue with listing of domains in Advanced Permission
• Fixed issue with color selection in App Board Gauge widget configuration
• The length of signed urls was changed following an upgrade from AWS, which caused problems for certain customers. This issue has now been solved.