MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

Asset Management Service

Fixed issues

  • The user can delete core.basicenterprise type assets if it does not represent a tenant, but will get an appropriate error response if it is a tenant.

  • Appropriate error message is returned when moving a tenant.

Cloud Foundry

What's new?

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

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

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

Container Registry Lite

What's new?

MindSphere Container Registry Lite is a service supporting container based applications and can be accessed in the course of a MindAccess Developer Plan and MindAccess Operator Plan.

  • It can be used by its respective API and GUI.

  • Container Registry Litec provides the following Docker API V2 based services:, (parts available via Harbor GUI also)

    • Login

    • Generate User (robot account) for CI/CD pipeline

    • Image Push

    • Image Pull

    • Image Delete

    • Image Tagging

  • Respective Service can be accessed using an appropriate client, e.g. Docker CLI which has to be downloaded and installed on your system before. 

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 has to 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

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.