Results

MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

Analytics Services

What‘s new?

  • With this release we introduce the direct interactive mode for KPI Calculation API. With the direct interactive mode it is now possible to let the API fetch the asset's time series data from IoT directly instead of providing the IoT timeseries data as input in the HTTP header. This is done by directly integrating with Time Series service inside the API backend execution.

  • We're introducing the direct interactive mode for Anomaly Detection API. With the direct interactive mode it is now possible to let the API fetch the asset's time series data from IoT directly instead of providing the IoT timeseries data as input in the HTTP header. This is done by directly integrating with Time Series service inside the API backend execution. In this release, we also change the input variable names to asset and aspect. 

  • We're also introducing the direct interactive mode for Signal Validation API. With the direct interactive mode it is now possible to let the API fetch the asset's time series data from IoT directly instead of providing the IoT timeseries data as input in the HTTP header. This is done by directly integrating with Time Series service inside the API backend execution.

Cloud Foundry

Known issues

  • Upgrading single Logme, MongoDB 3.2 and PostgreSQL 9.4 Backing Services instances to clustered instances is not possible.

Additional Information

  • CF Stack

    • CFlinuxFS2 Stack is deprecated and planned to be removed from cloud Foundry at end of May 2020. Apps running on cflinuxfs2 stack will not run anymore.

    • DotNet BuildpackNext DotNet buildpack update will not support DotNet 3.0 anymore.

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

What‘s new?

  • Starting with this release, we are introducing enforcements on user limits in MindSphere. The user limit depends on the tenant type and purchased upgrades. New users cannot be created if this limit is exceeded. The upgrade can be purchased by using the Settings application.

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.

Integrated Data Lake Service

What‘s new?

It is now possible to ingest data in bulk/batch into Integrated Data Lake.

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

  • After deleting a file, it will take some time (up to 60 seconds) to create the file with the same name again.

  • After creating or deleting the file, it will take some time (up to 3 seconds) to get the file in "search file" API. 

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.

IoT and Storage Services: Aggregates Service

What's new?

  • Within this release we introduce the new version of Time Series Aggregate API with enhanced usability features like optional query parameters, auto calculation of intervalUnit and intervalValue and support for non aligned times. It also supports ISO date formats.

  • With the upcoming releases we will discontinue support of trailing “/” after {aspectName} while calling Timeseries APIs. The API will continue working without trailing “/” as shown in examples below.

    Example:

    For Timeseries Aggregates Services API:

    • The following call will work: https://gateway.{region}-{environment}.{mindsphere-domain}/api/iottsaggregates/v3/aggregates/{assetId}/{aspectName}

    • The following call will not work: https://gateway.{region}-{environment}.{mindsphere-domain}/api/iottsaggregates/v3/aggregates/{assetId}/{aspectName}/

    For Timeseries Services API:

    • The following call will work: https://gateway.{region}-{environment}.{mindsphere-domain}/api/iottsaggregates/v3/aggregates/{assetId}/{aspectName}

    • The following call will not work: https://gateway.{region}-{environment}.{mindsphere-domain}/api/iottsaggregates/v3/aggregates/{assetId}/{aspectName}/

OPC UA Pub Sub

What‘s new?

  • It is now possible to write the unit of a variable to the proper field so that it can be interpreted by all the applications. This will significantly enhance the user experience in all applications showing assets onboarded via OPC UA Pub/Sub.

Chap. 2.30.3