8.1

Last update: Edit

8.1.1

Release date: September 10th, 2019

Download

Fix

  • We fixed the issue where Studio Pro leaked memory. (Tickets 88045, 88075, 88100, 88142)

Known Issues

  • MySQL 8.0 cannot be used with the default authentication plugin as of this moment. Mendix uses the open-source MariaDB driver to connect, which has not yet added support. We will include the updated driver as soon as it is released. To resolve this issue, you may consider using the previous default plugin until the driver has been updated.
  • It is possible to connect to SQL Server 2014 databases, although Mendix no longer supports that version.
  • The first deployment of an app project with a native mobile profile takes up to approximately one minute longer than usual, as it needs to build up a cache. On consecutive deployments, this time is reduced.
  • In native mobile apps, the back button text changes to Back in case of longer page titles. This is currently not translatable.

8.1.0

Release date: September 2nd, 2019

Download

New Features

Pluggable Widget Capabilities

With this release, we are extending the capabilities of pluggable widgets. These widgets can now be made conditionally visible in the same way as all core Mendix widgets. As a widget developer, you can control how the Visible setting is presented to an end-user with the help of the new Visibility system property.

In addition, pluggable widgets can now have an editable configuration, similar to that of core input widgets. When a widget is marked as read-only or conditionally editable with the condition being false, then all the EditableValue it receives will be readOnly. To opt in for this feature, the pluggable widget can use the new Editability system property.

We also improved the documentation shipped with our npm package so that you can have better inline documentation in your IDE.

More Flexible App Modeling

The data view is a powerful widget. However, building a UI can become more complex when multiple data views are needed. So, we improved one modeling scenario where data views were required. You can now make an input widget (for example, a text box or radio button) showing an attribute over an association editable without introducing an intermediate data view over the association. This will make building pages easier and faster.

When you introduce a nested data view, there will now be less of a “hard border” on your page. That means you can use objects of all the surrounding data view widgets in your visibility, editability, and validation expressions (and not only the enclosing data view). You can do this by referring to the data view name as a variable.

The above features can be used by pluggable widgets as well, which is one more reason to build one!

New mx Command-Line Tool

We added the mx command-line tool. This is a Windows and Linux command-line tool that can be used to convert the inputted app projects(s) to the version of Studio Pro with which the tool is bundled.

Improvements

  • We improved the Studio Pro installation experience by changing the installer and Version Selector technology. This improves progress reporting and dependency installation. Also, if you choose to run Studio Pro at the end of the installer, it will no longer run in elevated mode.
  • In native mobile apps, page titles and bottom bar captions are now translatable.
  • For native mobile apps, anonymous users are now localized using the user’s OS language instead of the app project’s default language. If the user’s OS language is not recognized or not configured in the Project Settings, the project’s default language will be used.
  • The navigation mechanism of native mobile apps is now based on React Navigation instead of React Native Navigation.
  • For number operations with native pluggable widgets, you can now use the big.js library.
  • Specifying isList or entityProperty on the return type of an expression property in a pluggable widget will now cause a validation error when loading the widget package.
  • Mendix Assist now helps you with assigning condition values on the flows of a microflow.
  • You can now configure error handling via the Properties pane in your microflow.
  • In published OData services, it is now possible to filter data using functions such as substringof, startswith, and endswith on attributes of associated entities.
  • You can now configure the shared access signature and the blob endpoint for connecting to the Azure Storage service.
  • We added a consistency check for XML export mappings. Using an attribute and a child element that have the same name is not supported.
  • We improved support for calling services that require an Expect: 100-continue HTTP header.
  • We changed the behavior of OPTIONS requests to published REST services. Authentication is no longer required when you define an OPTIONS microflow. In addition, when CORS is checked, you no longer need an OPTIONS microflows; the service will respond to OPTIONS requests with CORS headers. (Ticket 85462)
  • You can now use the copy-paste command in the Project Explorer to move most items.
  • The nanoflow editor now supports extracting sub-nanoflows!

Fixes

  • We created a solution for Native Builder v1 being incompatible with Mendix 8.1. To use the Native Builder with Mendix 8.1, download and use Native Builder v2.
  • We fixed an issue that prevented connections to Azure SQL Databases by downgrading the minimum required engine version for SQL Server. (Ticket 87014)
  • We fixed an issue where incorrect results were returned for XPath queries when the same entity member (either an attribute or an association) was compared against different values.
  • We fixed an issue where the needsEntityContext attribute was required for a pluggable widget, but it had no effect. Now you can safely skip that attribute.
  • You might have noticed that even if you disabled Mendix Assist, some requests were still sent to the service, though no suggestions were shown in the microflow. Such requests are no longer sent.
  • We fixed an issue where Mendix Assist was sending too many requests when recovering from connectivity issues.
  • We fixed an issue where a variable containing NULL or empty caused an error when used in the string comparison functions of XPath expressions. (Ticket 78645)
  • We fixed an issue where a query for a specialized entity containing a predicate with a path over an association of its generalization returned another instance of that generalization.
  • We fixed an issue that prevented database migration in cases where the source database had a longer enumeration value than the column length generated on the current database based on the application domain model. (Ticket 65327)
  • We fixed an issue in Studio Pro where a missing log message showed an exception pop-up window.
  • We fixed an issue in Studio Pro where the metadata URL of a published OData service displayed a double slash where it should have been a single slash.
  • We fixed an issue in the web service call action so that when the result is empty, it now results in an empty value instead of going to the error handler.
  • We fixed an issue where Studio Pro installation failed if AdoptOpenJDK had been installed manually.
  • We upgraded the internal browser technology for more stability and security
  • We fixed an issue in the Studio Pro App Store where clicking Request info for an App Store item led to an error message.
  • We fixed an issue where a home page microflow with a return value resulted in a JVM exception. (Ticket 86303)
  • We fixed a bug where an error occurred when deploying a native app.
  • We fixed an issue that prevented sessions from staying alive when using optimistic locking. (Ticket 85222)
  • We fixed an issue that prevented some users from merging specific revisions from another branch. (Ticket 85619)
  • We solved an issue in which the retrieve action wrongly added the prefix New to the object. (Ticket 85939)
  • We fixed some error messages that had been truncated (with error codes CE0529, CE0569, and CE6554), and we fixed an incorrect error code prefix (to use CE1155, not CI1155).

Known Issues

  • In some situations, after opening an app project in Studio Pro, Studio Pro starts leaking memory over time.
  • MySQL 8.0 cannot be used with the default authentication plugin as of this moment. Mendix uses the open-source MariaDB driver to connect, which has not yet added support. We will include the updated driver as soon as it is released. To resolve this issue, you may consider using the previous default plugin until the driver has been updated.
  • It is possible to connect to SQL Server 2014 databases, although Mendix no longer supports that version.
  • The first deployment of an app project with a native mobile profile takes up to approximately one minute longer than usual, as it needs to build up a cache. On consecutive deployments, this time is reduced.
  • In native mobile apps, the back button text changes to Back in case of longer page titles. This is currently not translatable.