MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

What‘s new?

We have enabled the enforcement of the contractual limit in Agent Management Service of the agent creation quota.

What's new? 

• We have updated the following buildpacks:

Known issues

• Upgrading single Logme, MongoDB 3.2 and PostgreSQL 9.4 Backing Services instances to clustered instances is not possible.

Additional Information

• CF Stack

  • CFlinuxFS2 Stack is deprecated and planned to be removed from cloud Foundry at end of May 2020. Apps running on cflinuxfs2 stack will not run anymore.

  • DotNet BuildpackNext DotNet buildpack update will not support DotNet 3.0 anymore.

Known issues

• Sporadically streams cannot be deleted. Please try again if it was unsuccessful.

• If an entity is derived from type core.basicdevice only one stream can be deployed.

Known issues

• If you have problems logging off in Internet Explorer 11, please refer to Overcoming Logout Problems in IE11. 

• After a user's permissions have been changed using the Identity Management Service, the change is not immediately visible. The user must close the browser and log in again.

Known issues

• For security reasons a strict timeout is enforced. Currently, this leads to the situation that the size of a file which can be uploaded/ downloaded depends on the network bandwidth at client side.

• When uploading files to the File Service, a file name cannot contain blank spaces. Blank spaces in the file name will prevent the file form being stored.

• After deleting an asset, associated files might still be accessible for up to 30 minutes as this data is deleted asynchronously.

• After deleting a file, it will take some time (up to 60 seconds) to create the file with the same name again.

• After creating or deleting the file, it will take some time (up to 3 seconds) to get the file in "search file" API. 

Known issues

• The maximum payload size of a message sent to Time Series Service as part of a PUT request cannot exceed 1 MB.

• The service will never return more than 2000 records in a response.

• After deleting an asset, respective time series data might still be accessible for up to 30 minutes as this data is deleted asynchronously.

• When getting the job status of a bulk import job, the response might not always contain detailed information on errors that occurred.

• When creating or updating an aspect it might take up to 30 minutes until aggregated data can be read for this aspect. Writing data or reading raw data is possible immediately.

• When ingesting time series data for multiple asset and aspects in single request, the combination of records should be unique.

• Get Latest Value with query parameter "latestValue = true" will work with a delay up to 2 hours from the time of ingestion. Refer to developer documentation 'sample' section for more information.

• While using Get Latest Value with query parameter  "latestValue = true", historic/late arriving data may take more than 1 day to reflect in the response.

What's new?

Advance Information: Time series service will soon be upgrading its version of Aggregate API from 3.X to 4.X in coming releases.

We request you to please evaluate the new version and migrate the applications using the older API and use the newer features of the version 4.X. The detailed IoT Aggregate API documentation will be made available in the overview page along with differences between the two API versions. We have included a short summary of the advanced intelligent features for the new API below. The new API will have advanced intelligent features as follows:

• All query parameters are optional.

• If intervalValue and intervalUnit gets calculated automatically using from and to date, if not provided by user.

• Added new parameter count to specify how many aggregates the user wants.

• Asset and Aspect IDs as query parameters.

• Support for ISO date formats.

• Removed limits on records and added limits on duration and number of calls

What‘s new?

• Within this release we introduce the file transfer via HTTPS for OPC UA PS implementation.