MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

Analytics Services

What‘s new?

  • Event Analytics Duplicate Event removal: Allows you to remove identical event messages in a given time frame, in order to remove noisy status or error messages from your event stream.

  • Event Analytics Event Filter: Allows you to remove certain events in the input data you provided that match your filter text. With this, one can remove commonly known status messages from devices that spam your event stream.

  • Event Analytics Event Count: Returns the number of events that occurred in your input data binned into the timeframe of your desire.

Cloud Foundry

What‘s new?

Updated the following Cloud Foundry component versions:

Component

Version

binary-buildpack

1.0.21

staticfile-buildpack

1.4.29

python-buildpack

1.6.18

nodejs-buildpack

1.6.28

capi

1.62.0

ruby-buildpack

1.7.21

go-buildpack

1.8.21

dotnet-core-buildpack

2.1.3

java-buildpack

4.13.1

php-buildpack

4.3.57

uaa

60.2

loggregator

103.0

Known issues

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

Additional Information

Identity and Access Management

Fixed issues

  • Logout behavior was improved.

Known issues

  • After modifying the authorization of an 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.