MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

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.

Known issues

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

• 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 to create 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:

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

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

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.

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.

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.

Known Issue

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