MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

Fixed issues

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

What's new?

• As a MindAccess DevOps Plan subscriber, we need to inform you about the deprecation of the Cloud Foundry stack cflinuxfs2 in favor of the newcflinuxfs3 stack. Stacks are prebuilt root file systems that support specific operating systems. These stacks are used for running applications deployed in Cloud Foundry. More details about stacks can be found in the official Cloud Foundry documentation.

  While we do not anticipate any issues with the new cflinuxfs3 stack, we suggest deploying a separate instantiation of your application using the new stack to evaluate if there is any impact to your application. This can be done by pushing your existing application to a new name with a separate route. Once you have verified that your application has not been impacted, redeploy the app using the new cflinuxfs3 stack. Note that once an application has been deployed using the cflinuxfs3 stack, future pushes will remember the stack selection.

  You need to verify if your deployed apps are using buildpacks based on the deprecated cflinuxfs2 stack. In case your apps are using such buildpacks, you need to migrate your apps to the new cflinuxfs3 stack. We have prepared an article that covers the migration of applications from the cflinuxfs2 stack to the cflinuxfs3 in our PLM-Community. Additional information can be found in the MindSphere Developer Documentation.

• Improved handling of Backing Service Upgrades and downgrade. Cloud Foundry Org quotas are now correctly and transparently set for each tenant.

• Applications built using Mendix can be transferred from Developer to Operator and made available to MindAccess IoT Value Plan.

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.

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.

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.

What's new? 

• The Time Series Bulk Import Service now supports calculation of pre-calculated aggregates for 10 milliseconds, 1 millisecond and 1 second.

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.

What's new?: 

• Customer Dashboard:

  • Introduction of a quick search feature within history tab.

  • Introduction of two more metrics: Asset instances and asset types.

Known Issues

• Customer Dashboard doesn't distinguish between the core asset and customized assets and therefore it shows one asset more than configured and shown at the Asset Manager.