Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 247.1
edited by Erik Bakker
on 2025/04/22 14:01
Change comment: There is no comment for this version
To version 319.1
edited by Erik Bakker
on 2026/02/23 08:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -243 - Migration Magic
1 +262 - Good News
Content
... ... @@ -1,30 +1,28 @@
1 -In the last sprint, we released our migration wizard for the new eMagiz connector. This wizard will guide you through the process of migrating the existing eMagiz connector within Mendix to our latest version, which is packed with improvements. Furthermore, we will release a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] that corrects some changes and improves the UI/UX of loads of data grids across the platform. In addition, we have various smaller changes and bug fixes for you to enjoy.
1 +This release includes many updates to our platform. We are releasing some beta features for customers using our latest version of the API Gateway, allowing them to use multiple authentication methods. On top of that, we have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers. Furthermore, we have a series of smaller improvements to enhance your everyday work.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.243 - Migration Magic.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.262 - Good News.WebHome||target="blank"]].
4 4  
5 -====New Features====
5 +==== Minor changes ====
6 6  
7 -* eMagiz Connector - Migration: We have implemented a migration wizard that allows you to migrate to the new eMagiz Connector. You can start this wizard via Deploy -> Mendix connectors on a system-by-system basis.
8 -** Migrating eMagiz connector flows to the new version will remove the history of the old versions from the history tab. Make sure you copy this information if you want to archive it. After migrating your flows, this will no longer be visible.
7 +* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers is available.
8 +* Create - Flow Designer: The help text for the Result Type attribute of the JSON to XML transformer has been improved. (#1553)
9 +* Create - Flow Designer: Unused support objects can be deleted with a single button. (#794)
10 +* Deploy - Releases: The on‑hover text for a release also displays the most recent date and time the release was edited. (#341)
11 +* Deploy - User Management: For models that have been migrated to our latest functionality for both our event streaming and API offering, changes to users in the Deploy phase will be applied immediately for both manually created users and system users.
12 +* Deploy - Architecture: The Apply to Environment pop-up has been updated to reflect progressive changes made to specific objects. Any pending changes on Container, Router, Certificate, Instance, and AWS resources are now stacked and displayed to the user. The list is ordered from the earliest change at the top to the most recent at the bottom, allowing users to clearly see all modifications made to a specific object until the Apply to Environment button is clicked. These changes will remain active for future operations. (#1537)
13 +* Deploy - Architecture - Routes: The View and Edit pages for Routers have been updated to remove the Endpoint DNS Name and Flow Symbolic Name fields. (#1537)
14 +* Manage - Alerting: For Log and Error triggers, a custom subject can now be specified under ‘notifications’. This enables you to sort incoming alerts in your mailbox more easily.
15 +* Manage - Alerting: We have tightened the allowed characters for the triggers to reduce further the likelihood of HTML injection into the bodies of alerting emails sent by eMagiz.
16 +** Note: if you already have existing alert rules that contain characters that are now considered illegal, you will need to change them when you make any change to that trigger.
9 9  
10 -====Minor Changes====
18 +==== Bug fixes ====
11 11  
12 -* General - Event Streaming: We have updated our event streaming infrastructure.
13 -* General - Datagrids: We have updated a lot of our data grids to reflect the latest changes available
14 -** ‘Double click’ action on data grid rows is introduced to the newer datagrid format and, where possible, configured as such. Since older grids will be gradually replaced, this update allows for the maintainability of the behavior you are used to.
15 -** Unfortunately, The above change resulted in a behavior shift when selecting one or multiple rows in a grid (for example, in the trigger overview). Previously, clicking on the whole row resulted in the selection of the row. Now only checking the checkbox results in a row selection.
16 -* Create - Transformation: In the Transformation tab of the Create phase, conditional operators can be added for transformations that have multiple attributes as a source. (#1272)
17 -* Deploy - Machine: We have updated the default network deployment strategy for Windows machines, which might affect your machines. When you access the Deploy phase, you will see the list of machines required for redeployment. Redeploying your machine will ensure you benefit from these enhanced network capabilities.
18 -* Deploy - History: Deploy releases history tab better renders the information on the screen.
19 -** Additionally, we have updated the "Export to Excel" button to reflect the latest functionality. As a result, there is no longer a limit to how many rows can be exported. (#1601)
20 -* Deploy - General: We have implemented performance improvements to the Deploy phase. The larger the model, the more notable the improvements.
21 -* eMagiz Connector - General: We released a new patch version of the eMagizConnector in the Mendix marketplace. It includes some small changes to the naming conventions to remove the ACR violations.
20 +* Design - Catalog: Help texts related to “content”, “Json format”, and “Gateway message definition” are updated. (#1082)
21 +* Create - Untransfer integration: We fixed an issue where you could not remove an integration of the Mendix connector system, which was migrated from the Legacy eMagiz Mendix Connector to the current eMagiz Mendix Connector in Create.
22 +* Create - Flow Designer: When using DSH support objects, the required admin-only fields are automatically filled in. (#1755)
23 +* Create - Store: When importing a store component with properties, validation feedback will now be provided if the property value does not align with the expected type. (#1276)
24 +* Manage - Explore: Error message is much more descriptive when the container is not running (#1321)
22 22  
23 -====Bug fixes====
26 +==== Remarks ====
24 24  
25 -* Design - System Message: Using the "save and create new attribute" button in the system message tab of the design phase will not open a "new attribute" window until the previous attribute’s details are properly entered and saved. (#1650)
26 -* Create - Transformation: Help text appears for relevant attributes when creating a new transformer in the transformation tab of the create phase. (#1352)
27 -* Catalog - General: The content inside the “used by integrations” table for the topic catalog is properly rendered to be more readable for systems with longer names. The title represents the content of the table. (#1224)
28 -* Create - Transformation: Date/time transformer pop-ups in the Transformation tab of the Create phase are rendered in a format that allows editing when in edit mode. (#1642)
29 -* Infra - Runtime Image: Support for the ‘NTCredentials’ authentication method in a custom HttpComponentsMessageSender support object has been reintroduced.
30 -* Infra - Runtime Image: In some edge cases, log messages produced with the Logging channel adapter component did not end up in the Manage phase. This issue is now resolved.
28 +* General - Infrastructure: We updated our image builder for Windows images to use the latest Java versions for images. Effectively, this means that any image built for Windows from this release onwards that uses a base image //3.4.0// or above, will use Java 21.0.10 as baseline. Images below version //3.4.0// will now use Java 17.0.18. Therefore, new (property) releases that use the same eMagiz base image, will still use a different Java version, and may therefore have some changed behavior. Normally that would not be noticable, but since these Java version increases drops support for some weak cipher suites, connectivity may be affected. For more information, please refer to the release notes of image 3.5.1.