MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

Currently not available in Europe 2:

• Anomaly Detection in Batch Mode

Fixed issues

• Asset Management API responds with an appropriate error when the maximum size of an aspect is exceeded.

What's new?

• General usability and security enhancements.

• Apps need to be updated to library Spring Boot 2.x in case they using versions prior to 2.0.0. 
  Reason: Version 1.x is end-of-life since beginning of this month (https://spring.io/blog/2018/07/30/spring-boot-1-x-eol-aug-1st-2019).
  Upgrade: Please read this migration guide: https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.0-Migration-Guide.

• Updated buildpacks

Fixed Issues

• Fixed an issue that caused rarely 404 errors while accessing of applications.

• Fixed an issue that caused errors during service unbinding.

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

  • MindSphere currently does not support mobile applications built using Mendix

  • 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

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

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

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.

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.

• When creating or updating aspects on an asset, it might take some time (up to 30 minutes) until this aspect or respective changes are available on the Time Series Service. The service returns a 404 (Not Found) as long as the changes are not completely propagated.

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

What's new?

Mendix offering now available - Mendix Platform License now available to operate apps consistently.

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.