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:


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).