MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

Asset Management Service

What's new?

  • Customers can now share selected single assets with another tenant of their choosing.

Known issues

  • When using asset-sharing, the following things should be avoided

    • sharing of agent assets

    • deleting or changing core.sharerenterprise typed asset

Analytics Services

Fixed issues

  • Security fixes for Spectrum Analysis API, Event Analytics API Top Events and Pattern Matching

  • Infrastructure improvements for Anomaly Detection API, KPI Calculation API and Signal Validation API

  • Trend Prediction API now stores models in Model Management. This allows customers to download or change the metadata of a stored model via Model Management API separately, thus giving more flexibility.

Cloud Foundry

What's new?

  • General usability and security enhancements

  • Updated buildpacks:































Fixed issues

  • Fixed an issue that caused rare 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:

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

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

What's new?

  • Time series API currently returns latest record, we have extended it to return the latest value which are not frequently sent to MindSphere up to 1 month.

  • Standard Deviation are now included in Time Series Aggregates for performance assets.

  • Time series PUT API now supports data ingestion for Multiple Assets and Aspects in a single request.

  • Time series Bulk Import Service now supports LIMITED Bulk data upload capabilities for performance assets. The pre-calculated aggregation of uploaded raw Time Series data will be available in upcoming sprints.  

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.

Usage Transparency Service

What's new?

  • Additional metrics will be shown at the Customer Dashboard: Asset instances and Asset types.