MX 10 Features
MX 10 Features
MX 10 Features
0 Beta 1
We no longer support using DB2 as the database for applications.
We added a new way to convert between microflows and nanoflows by right-clicking
the microflow or nanoflow in the App Explorer. For more information, see the
alternative option specified in the Converting a Microflow to a Nanoflow section
in Microflows and in the Converting a Nanoflow to a Microflow section in Nanoflows.
We updated the login image shown on startup.
We included dark-mode support for the login dialog box shown on startup.
We updated the colors of the microflow editor.
We updated the style for controls residing in a toolbar.
We updated the style for button controls.
We updated the style for the breadcrumb, loading bar, scrollbar, and tooltip UI
components.
We added highlighting for when you hover over tree control rows.
For pluggable widgets with a system property Label, Show label is now set to Yes by
default.
We added a button to the toolbar of the workflow editor that enables the export of a
workflow to an image.
We added a button to filter MxAssist Performance Bot best practices to documents that
are not yet committed to version control.
We updated the MxAssist Performance Bot Best practice MXP011 to group
recommendations together. There is one group for each stack of deeply nested views.
We updated the MxAssist Logic Bot for when a Boolean decision is chosen (at the top
level or in a loop) and both the true and false flows are created.
We added {F1} help support to the MLKit document and fixed an issue with
its Properties pane.
Previously, a single XPath query could result in multiple SQL queries to the database,
and if an XPath query was run outside of a transaction (meaning, not in a microflow,
but in a data grid, for example), these SQL queries were executed concurrently. This is
no longer the case. This simplifies debugging, logging, and tracing.
We added default values for
the ProcessedTasksCleanupAge and ScheduledEventsCleanupAge Mendix Runtime
settings. The default value is now 365 days for existing apps with data and 7 days for
new apps or apps with an empty database. Previously, the default values were empty
and required an explicit Mendix Runtime setting configuration in order to perform
cleanup.
We improved the naming generation in the JSON structure.
In OQL, Attribute = $Parameter where the parameter is a collection containing only
a null now checks that the attribute is empty. This now also works with the parameter
on the left side.