30th June 2021 (China 1)

MindSphere is now available in Simplified Chinese in region China 1 hosted by infrastructure provider Alibaba Cloud in the data center Shanghai, China.

These release notes are relevant for MindSphere Release in June. 2021 with version "V1903.CL.CN1.N0630“

We recommend that you read the following release notes carefully. These notes contain important information for installation and use.

The following apps and services are currently not available in region China 1:

• Integrated Data Lake

• Semantic Data Interconnect

• Mendix Integration

• Close Loop Foundation and Application

• Start for Free

You can find more information about region variations and deviations in the MindSphere regions documentation.

For region China 1, MindSphere supports all the latest features except the points listed in the respective Plans.

Applicable for:

• MindAccess IoT Value Plan Subscribers

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

Known issues

• Fleet Manager navigation is not working correctly if you have to re-login as query parameters are lost. Please try again by clicking the Fleet Manager navigation button.

• If you are using app specific roles you need to assign plugin roles as well. This is up to now only possible for MindConnect LIB plugin.

Applicable for:

• MindAccess IoT Value Plan Subscribers

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

Known issues

• High Value Asset Monitoring

  • Application matches only the text version of the value of the variable to the user supplied text, but the configuration label reads "Variable value:" giving incomplete information to the user. Label should read "Variable value text:".

• Multi-site monitoring

  • Application does not sort list of most frequently occurring events at site upon loading the site dashboard.

  • Removal of site without the removal of site configuration may result in failure if site has rules.

• Event Management

  • Application may not correctly sort events if timestamp of events in day contain both am and pm.

• KPI Calculations

  • Variable of any type can be selected for the KPI calculation configuration leading to inconclusive output if unsupported variable type is selected (requires positive float number).

Applicable for:

• MindAccess IoT Value Plan Subscribers

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

Known issues

• Only single asset sharing is available in the first release

• Sharing of assets derived from basicAgent and their corresponding plugins is not yet supported

• Tenant assets can not be moved under collaborators root asset or shared assets

• Revoking of sharing offers on sharer side is not yet possible

• Terminating the collaboration will not remove active sharings and shared assets on the receiver side in the first release

• In some cases, the German translation of the Asset Manager UI  may hold English text elements.

• The location of an asset will not be shared with the receiver

Applicable for:

• MindAccess Developer Plan Subscribers

Known issues

• Application versions that contain a "#" character cannot be deployed in the Operator Cockpit. We advise to not use "#" in production version strings.

• Applications cannot be deleted after being transferred to the production system.

• The application upload size is limited to 100 MB.

• Sporadically application roles are not deleted from the User Management when deleting an application

• Layout issues in Internet Explorer 11 in combination with high resolution displays and 125% font scaling.

Additional Information:

We are going to remove the ability of assigning mdsp:core:developer and mdsp:core:developeradmin roles to subtenant users.

Applicable for:

• MindAccess IoT Value Plan Subscribers

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

Known issues

• The event time stamp in the Event extension shows only in format of UTC even if user chooses "Browser (+08:00)" (China for example) from the time zone drop-down.

Applicable for:

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

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.

• After deleting an asset, associated files might still be accessible for up to 30 minutes as this data is deleted asynchronously.

• Multi-part uploading or completing may failed with “500 Internal Server Error”. To avoid such failure, please make sure some interval (e.g 3s, must be greater than 1s) between each part uploading request or before completing the multi-part uploading.

Applicable for:

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

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 using “select” parameter in GET method of Time Series API, the response might not always contain all the data in the below scenario:

  There are 3002 time series data in the given time range of GET method, the earliest time values "_time1" and the latest value is "_time3002". There are only 3 "var2" as in below table. When "var2" is considered by “select” parameter, only "var2" from "_time1" would be returned.

  _time1	va1	var2
  _time2	va1	var2
  _time3	va1	var2
  …	…
  …	…
  _time3000	va1	var2
  _time3001	va1	var2
  _time3002	va1	var2

Applicable for:

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

What's new

• Java SDK 2.3.7

  • add client support of iotbulk

  • add client support of mindconnect

• Python SDK 1.0.4

  • add client support of iotbulk client

  • add client support of mindconnect client

Known Issues

• Auto-deployment does NOT support 1) applications using binary buildpack, 2) appliations that has "buildpacks" attribute in manifest.

• Application upload artifact with Chinese filename will fail to check.

Applicable for:

• MindAccess IoT Value Plan Subscribers

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

Known issues

• Note: A full configured monitoring of the Analyzing Packages Vibration Characteristic Values and Vibration Frequency Spectra with all channels of one SM1281 can exceed the CPU performance of the MCN. Also in other scenarios dependent of tasks running in parallel on the MCN, CPU load can get to high. The recommendation is to use only two full configured Vibration Frequency Spectra Analyzing Packages in parallel.

• Note: A compatibility check, whether the Edge Analytics Engine Version on the target MCN supports all possible types of Analyzing Packages, which are offered by EAM, is not yet done. Therefore it has to be made sure that the newest Firmware Version is installed on the MCN when using the new Analyzing Package Vibration Frequency Spectra, otherwise the Edge Analytics Engine will suspend.

Applicable for:

• MindAccess Developer Plan Subscribers

Known issues

• Currently only email text is checked, other contents like image, audio, video, URL are not in the validation scope.

Applicable for:

• MindAccess Operator Plan Subscribers

Known issues

• If you download application binaries during manual deployment the progress bar of the download progress of the Operator Cockpit is temporary disabled. The download will be executed but without a feedback of the progress in the Operator Cockpit. Look into your download folder to find the application binaries.

• Limitations for applications that use "Technical Token Manager API"

  • You cannot use zero downtime upgrade for applications that use "Technical Token Manager API", if the previous version of this application did not use "Technical Token Manager API".

• Limitations for update of Cloud Foundry applications:

  • The service instance names for each service should be same in the current and new version of the application. If the service instance names are different in the new version and the existing version of an application, then the existing service instances will not be readily available even after zero-downtime version upgrade.

  • During manual deployment of a new version of an application, do not use the same component names as available in the existing version. This might create name conflicts and usability issues. In order to avoid such conflicts, while deploying a new version of an application, append green at the end of the component name.

• For every individual (single) application, one Cloud Foundry space must be deployed.

• After modifying the authorization of a user via the Operator Cockpit user interface, the change is not immediately visible. The user has to close the browser and login again.

• After deployment of an app there is a security feature in place validating if the app is known to MindSphere or the app got somehow modified. Sometimes issues occur with regards to name changes or deploying from various folders. The apps need to be deployed as they are assigned from the developer.

Applicable for:

• MindAccess IoT Value Plan Subscribers

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

Known issues

• Applications can use the subtenant functionality via the provided APIs. Tenant administrators should pay attention when assigning such apps to subtenant users as subtenant isolation cannot be ensured by the platform. The app might expose data to the user that is not intended to be seen.

• When moving an asset from a parent tenant to a subtenant, there might be a delay of up to 30 minutes until a subtenant user will be able to see data related to that asset.

• Please be aware, if you provide a user (even subtenant user) the role "mdsp:core:TenantAdmin", this user is then able to get access to all kinds of tenant data.

Applicable for:

• MindAccess IoT Value Plan Subscribers

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

Known issues

• Time used for usage information storage and displayed on UTS UI is only using UTC time zone, not depending on the time zone of the region.

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

• Usage Transparency Service reports are only available after a 1-hour delay for developers.

• Customer Dashboard does not cover all metrics and upgrades that UTS measures for a tenant. We are continuously working on introducing more metrics and upgrades.

Applicable for:

• MindAccess IoT Value Plan Subscribers

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

Known issues

• Any request within Visual Explorer is limited to an execution time of 60 sec.

• The "share via link" functionality works unreliable.

• Support time series data types “LONG” with values for safe integer ->(2^53-1) to (2^53-1).

• If the value is e.g. 2⁶³ the value will be reset to safe integer ->2^53-1.

• Alerts can only be set up by clicking on a continuous axis.

Applicable for:

• MindAccess IoT Value Plan Subscribers

• MindAccess Developer Plan Subscribers

• MindAccess Operator Plan Subscribers

Known issues

• HTTP-in/response other user cannot access 'AllUsers' endpoint

• Subtenant users cannot use the time series subscription node.