Results

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. 

Analytics Services

Fixed issues

  • Upgrade of Springboot version for Signal Validation, KPI Calculation and other underlying services.

Cloud Foundry

What's new?

  • General usability and security enhancements.

  • Renew certificates

    • *.cf.eu1.mindsphere.io

    • *.apps.eu1.mindsphere.io

  • Updated buildpacks

    Buildpack

    Version

    Details

    dotnet-core-buildpack

    2.2.12

    https://github.com/cloudfoundry/dotnet-core-buildpack/releases/tag/v2.2.12

    go-buildpack

    1.8.42

    https://github.com/cloudfoundry/go-buildpack/releases/tag/v1.8.42

    java-buildpack

    4.20

    https://github.com/cloudfoundry/java-buildpack/releases/tag/v4.20

    mendix-buildpack

    3.6.0

    https://github.com/mendix/cf-mendix-buildpack/releases/tag/v3.6.0

    nodejs-buildpack

    1.6.52

    https://github.com/cloudfoundry/nodejs-buildpack/releases/tag/v1.6.52

    php-buildpack

    4.3.78

    https://github.com/cloudfoundry/php-buildpack/releases/tag/v4.3.78

    python-buildpack

    1.6.36

    https://github.com/cloudfoundry/python-buildpack/releases/tag/v1.6.36

    ruby-buildpack

    1.7.42

    https://github.com/cloudfoundry/ruby-buildpack/releases/tag/v1.7.42

    staticfile-buildpack

    1.4.43

    https://github.com/cloudfoundry/staticfile-buildpack/releases/tag/v1.4.43

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.

  • Support for Java SDK Version 1 will be stopped from end of October, the following SDK Downloads will not be available anymore:

    • mindsphere-sdk_1.0.0.zip (613,0 KB)

    • mindsphere-sdk_v1.1.0.zip (881,7 KB)

    • mindsphere-sdk_1.2.0.zip (1005,2 KB)

    • mindsphere-sdk_1.2.1.zip (1006,4 KB)

Container Registry Lite

Fixed issues

  • Sporadic login/logout issues fixed.

Data Flow Engine

Known issues

  • Sporadically streams cannot be deleted. Please try again if it was unsuccessful.

  • If an entity is derived from type core.basicdevice only one stream can be deployed.

Identity and Access Management

Known issues

  • If you have problems logging off in Internet Explorer 11, please refer to Overcoming Logout Problems in IE11. 

  • After a user's permissions have been changed using the Identity Management Service, the change is not immediately visible. The user must close the browser and log in 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.

  • Standard Deviation(SD) feature is not yet supported for data ingested via Bulk Import API.

Settings

What's new?

  • Service Credentials

    • Available for Cloud Foundry to create technical users in order to establish e.g. a CI/CD pipeline.

    • Up to 3 credentials can be created with an automatic expiry after 365 days.

Usage Transparency Service

Known issues

  • Customer Dashboard don't distinguished between the Core Asset and Customized Assets and therefore it shows one Asset more than configured and shown at the Asset Manager.  

Chap. 2.9.3