MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers


The following Release Notes are valid only for region Europe 2. You can find more information about regions in the MindSphere regions document.

Analytics Services

What's new?

  • Improved the following in Trend Prediction and KPI Calculation methods with regards to input parameters and empty data in the request body:

    • Trend Prediction endpoint "get/models" now has improved paging and size parameters when retrieving the trained models list

    • Trend Prediction now provides an improved Error message when time series are not being provided by the customer for training the model

    • KPI Calculation endpoint "calculateKPIstatesdirect" now has an improved error handling in case the TimeSeries data is empty for the given range

Currently not available in Europe 2:

  • Anomaly Detection in Batch Mode.

Cloud Foundry

What's new?

  • Cloud Foundry Backing Service supports a 'pay per hour' billing model of utilized Backing Services. At the end of month, billing will occur based on started hours per backing service instance.

  • The usage of CF RAM due to running applications will be shown in UTS on a daily basis.

The following updated buildpacks are now available:


































Additional Info:

  • PostgreSQL11 Migration Assist is available. It is recommended to migrate your a9s PostgreSQL 9.4. The version 9.4 is deprecated an 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

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

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

  • Reminder: Backing Service MongoDB will be removed from Cloud Foundry after 31.10.2020

  • The way of sharing MindSphere Cloud Foundry Backing Service instances with new created CF Orgs or CF Spaces will be changed effective end of January 2021.

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

Fixed Issues

  • Cloud Foundry PostgreSQL Backing Service randomly loses CREATEROLE privilege.

Identity and Access Management

Known Issues

  • After modifying the authorization of a user via Identity Management Service, the change is not immediately visible. The user must then close the browser and login again.

  • In the current version the logout with Internet Explorer 11 might not work. In this case please close the browser directly.

Integrated Data Lake Service

What's new?

  • It is now possible to use the user interface of Integrated Data Lake to create, modify, list and delete event subscriptions.

IoT and Storage Services: File Service

What's new?

  • With this release, the contractual limits of IoT File Service on File Storage will be enforced with one of the upcoming next releases. If you are about to exceed a respective limit, you will receive a descriptive response and no new files will be uploaded. If you have already exceeded your allowed quota on File Storage, these will not be influenced but will no longer be able to create upload new files. You can increase the amount of allowed quota on File Storage via our sales channels or directly via the Upgrade application.

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

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.

  • When creating, updating or deleting aspects on an asset in Asset Manager, it might take some time (up to 30 minutes) until this aspect or respective changes are available on the Time Series Service and available for visualization in Fleet Manager.

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

Notification Service

What's new?

  • It is now possible for the developers and operators to use the Email Notification APIs in order to communicate with the users via email. In addition, the commercial upgrade package(s) for email notification is also provided.

Usage Transparency Service

What's new?

  • With this release, the following additional metrics will be shown on the Customer Dashboard:

    • Cloud Foundry RAM size

    • Number of API calls per month to Token Manager Service

  • With this release, hourly granularity will be added to metric "Time series data ingest rate" on the Customer Dashboard history tab.

  • With this release, asset name will be added to metric "Time series data ingest rate per asset" on Customer Dashboard.

  • Overview on Pay-per-use offerings will be provided on Customer Dashboard. Additional metrics will be shown on Customer Dashboard: Cloud Foundry Backing Services - subscription and Pay-per-use services

Known issues

  • All usages generated within a Cloud Foundry Environment cannot be collected by Usage Transparency Services. All usages from and to a Cloud Foundry Environment e.g. requests to APIs still will be collected.