Thing pricing with limited period

It is now possible to allow customers to try a service level for a limited period, such as 30 days, instead of activating a subscription of a year or more. This new pricing model may have an activation fee, and at the end of the period, the product is set back to the previous service level.

User information provided during activation

You can mark user properties as mandatory during user activation. This way, when creating a new user, you can avoid providing all the information, even if it is mandatory, and let it be filled in by the newly created user when the account is activated.

Added support to the HTTPS/2 protocol

The DPS application is now also reachable with the HTTP/2 protocol, increasing performance in downloading resources and API requests.

You won't have to do anything; the browser will use the new protocol automatically.

New cloud-to-cloud IoT Connector management

The main IoT Connector, which was designed to be used only for a cloud-to-cloud integration, is now configurable only within the Console (Integrations / IoT Connector) and no longer in the DPS (Administration / Security / Connections). In addition, at each level (Customer, Location, Thing), unless explicitly overwritten, you can keep using the main IoT Connector, but without access to its configuration properties (e.g. username, password, certificates), which, for security reasons, are obfuscated.

Bug fixes (DPS)

• The default sidebar menu icons were using incorrect caching options, causing unexpected displays.
• Some delete buttons used the CSS class btn-primary instead of btn-danger which sets a red background color.
• The new Map widget was crashing during loading if an invalid page variable name was set for the query.

Bug fixes (Console)

• In the console, the API keys page loaded all API Keys, even if they were associated with a specific customer or partner (API Keys as-a-service).