MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

NOTE

The following Release Notes are valid only for region China 1.

Cloud Foundry

What's new?

  • Cloud Foundry version has been updated to v1.15.0 with regarding all related services,

  • Updated following buildpacks:

Buildpack

Version

dotnet-core-buildpack

2.2.12

go-buildpack

1.8.42

java-buildpack

4.21

nodejs-buildpack

1.6.52

php-buildpack

4.3.78

python-buildpack

1.6.36

ruby-buildpack

1.7.42

staticfile-buildpack

1.4.43

mendix-buildpack

3.6.0

binary-buildpack

1.0.33

Known issues

  • Applications using the Mendix buildpack are currently not supported for MindAccess Operator

  • When deploying an application to MindSphere, the app name has to be compliant with the MindSphere naming conventions.

  • Binary File Storage: MindSphere does not currently have a compatible file service available to its Cloud Foundry stack. Therefore, you cannot use any Mendix features which rely on having a file service.

  • At present, MindSphere only supports two roles. This should be taken into account when designing security within your Mendix app.

  • It is recommended that you create two scopes for your MindSphere app, user and admin which will map to identically-named user roles in your Mendix app.

IoT and Storage Services: File Service

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 must not 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 asynchrounously.

  • Multi-part uploading or completing may failed with “500 Internal Server Error”. To avoid such failure, please make sure some interval (e.g 3s, must be greater than 1s) between each part uploading request or before completing the multi-part uploading.

IoT and Storage Services: Time Series Service

What's new

  • New API to support data ingestion for Multiple Assets and Aspects in a single request. - PUT /timeseries.

  • Time series API currently returns latest record, we have extended it to return the latest value which are not frequently sent to MindSphere up to 1 month.

    New parameter: latestValue, in API: GET /timeseries/{entityId}/{propertySetName} - Default value : false

    latestValue: If true, only the latest value of each property is returned. Latest values must be at least two hours old and at maximum 30 days old, in order to be considered. The returned values might be co-located or spread over multiple timestamps. Each property appears at max once in the response. The select parameter can be used to limit the properties to be considered. Parameters from, to, and limit must not be used in conjunction with latest.

  • Pre-Aggregate is now available for performance entity

  • Standard Deviation is now included in Time Series Aggregates for performance assets.

  • Time series Bulk Import Service now supports LIMITED Bulk data upload capabilities for performance assets. The pre-calculated aggregation of uploaded raw Time Series data will be available in upcoming sprints.

  • Throttling for Timeseries aggregate: limit the number of on-the-fly and pre-calculated request per entity per minute,  Code 429: too many requests would be displayed, specifically:

    • 60 pre-calculated requests per minute per entity

    • 15 on-the-fly calculation per minute per entity

    • 600 records per second per entity

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 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 getting the job status of a bulk import job, the response might not always contain detailed information on errors that occurred.

  • Standard Deviation(SD) feature is not yet supported for data ingested via Bulk Import API.

Currently not available in China 1

  • Standard Deviation for Bulk Service

Usage Transparency Service

What's new?

  • New metrics for "Time Series Storage" is now supported on Customer Dashboard.

Mendix

Currently not available in China 1

  • Mendix Platform License is not available to operate Apps consistently.