MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

Analytics Services

What's new?

  • Within this release, the Trend Prediction returns the accuracy of the regression during the training phase based on the root mean squared error method (RMSE), lower values indicating better fit). This allows to decide if the training is valid for use and avoids overfitting.

Cloud Foundry

What's new?

  • Available and Updated buildpacks:

Buildpack

Version

Details

dotnet-core-buildpack

2.3.19

https://github.com/cloudfoundry/dotnet-core-buildpack/releases/tag/v2.3.19

go-buildpack

1.9.23

https://github.com/cloudfoundry/go-buildpack/releases/tag/v1.9.23

java-buildpack

4.35

https://github.com/cloudfoundry/java-buildpack/releases/tag/v4.35

nodejs-buildpack

1.7.37

https://github.com/cloudfoundry/nodejs-buildpack/releases/tag/v1.7.37

php-buildpack

4.4.27

https://github.com/cloudfoundry/php-buildpack/releases/tag/v4.4.27

python-buildpack

1.7.26

https://github.com/cloudfoundry/python-buildpack/releases/tag/v1.7.26

ruby-buildpack

1.8.27

https://github.com/cloudfoundry/ruby-buildpack/releases/tag/v1.8.27

staticfile-buildpack

1.5.14

https://github.com/cloudfoundry/staticfile-buildpack/releases/tag/v1.5.14

mendix-buildpack

4.13.5

https://github.com/mendix/cf-mendix-buildpack/releases/tag/v4.13.5

binary-buildpack

1.0.36

https://github.com/cloudfoundry/binary-buildpack/tree/v1.0.36

Additional Info:

  • Change in Cloud Foundry gorouter may require customer action. For more information, refer Change in Cloud Foundry Gorouter.

  • PostgreSQL11 Migration Assist is available. It is recommended to migrate your a9s PostgreSQL 9.4. The version 9.4 is deprecated and will be removed in the future.https://developer.mindsphere.io/paas/a9s-postgresql/using.html#migrate-the-service-instance-to-another-postgresql-version-into-new-postgresql-instance

  • Please note that redis32 and rabbitmq36 are going to be deprecated and might be removed in the future.

  • A new Backing Service Dashboard API (https://developer.mindsphere.io/paas/paas-cloudfoundry-backingservices.html#backing-service-dashboard-api) will be provided effective March 2021.
    The current Backing Service Dashboard API will be switched off in one of the next releases. 

  • LogMe Kibana dashboard URL has changed. Follow https://developer.mindsphere.io/paas/a9s-logme/using.html#see-your-applications-logs to find the new URL.

  • The way of sharing MindSphere Cloud Foundry Backing Service instances with new created CF Orgs or CF Spaces will be changed in one of the next releases.

    • Sharing via User-Provided-Service (as described here https://developer.mindsphere.io/paas/howtos/howtos-service-instances.html#create-a-user-provided-service) will not longer be possible.You can use "cf share-service" command instead (described here https://developer.mindsphere.io/paas/paas-cloudfoundry-backingservices.html#sharing-service-instances and here https://developer.mindsphere.io/paas/howtos/howtos-service-instances.html#enable-sharing-of-a-service-instance).

    • This change does not effect shares to existing CF Spaces.

Identity and Access Management

Known issues

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

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

IoT and Storage Services: Time Series Service

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.