MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

NOTE

The following Release Notes are valid only for region Europe 2.

Analytics Services

Currently not available in Europe 2:

  • Anomaly Detection in Batch Mode

Asset Management Service

Fixed issues

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

Cloud Foundry

Known Issues

  • Upgrading single Backing Services instances to clustered instances is currently not possible.

Identity and Access Management

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.

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.

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

Usage Transparency Service

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.