MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

Analytics Services

Fixed issues

  • Internal refactoring of Signal Validation, Anomaly Detection, KPI Calculation for fixing pipeline issues, internal access layer and SecurityLib usage.

  • Adaptions to enable subtenant awareness in Anomaly Detection.

  • Adaptions to enable subtenant awareness in Trend Prediction (Model storage delegated to Model Management instead of internal storage).

Cloud Foundry

What's new?

  • Updated Buildpacks for "cflinuxfs2" and "cflinuxfs3" stacks.





















  • "cflinuxfs3" stack is the new default root filesystem. Please refer to the developer documentation to learn more about stacks and how to upgrade existing applications. We heavily recommend to use the latest stack as "cflinuxfs2" stack is going to be deprecated soon.

  • Security enhancements.

  • Support for Multi Line Output for LogMe Backing Service.

Fixed issues

  • Fixed an occasionally occurring error that caused a failure during unbinding of Backing Service instances.

Known issues

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

  • In rare situations the creation of a Backing Service instances takes longer than 30 minutes and might fail. In those cases please try later again to create the service.

  • Mendix:

    • The Mendix buildpack is currently only available on MindSphere running on region Europe 1.

    • MindSphere currently does not support mobile native apps.

    • If the user logs out from MindSphere, the application built using Mendix will not delete the session cookie. In some circumstances, this could lead to another user using the same app on the same browser on the same computer, picking up the session from the previous user if the cookie has not yet expired.

Additional Information

  • Cloud Foundry allows the creation of more Backing Services instances than included in the individual plans. A fix for this behavior is going to be implemented with the next release.

  • Mendix:

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

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

Identity and Access Management

Known issues

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

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

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

IoT and Storage Services: Time Series Service

What's new?

  • Stability and performance updates for storage of time series data.

  • The Time Series Bulk Import Service now supports multiple jobs to be submitted for the same hour while uploading bulk simulation data via this service.

Fixed issues

  • An issue has been fixed that prevented clients from getting the latest value of an aspect when using the Time Series API GET endpoint without parameters.

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.

  • Some users observe delay or timeout  in reading the raw time series data for assets with more variables of type BIG_STRING.

Usage Transparency Service

What's new?: 

Under the resource Tab Assets there are 2 new data points (columns) available now.

  • Asset ID Unique identification ID of the asset.

  • Asset Name Unique name of the asset.

    This column value is empty if "Asset Name" is not mentioned for an associated "Asset ID" in the Entity Master Data Service (EMDS).

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.