Skip to Content

Changes for page 277 - First Farewell

Last modified by Erik Bakker on 2026/09/23 16:09
From version 245.1
edited by Erik Bakker
on 2025/04/22 10:58
Change comment: There is no comment for this version
To version 355.1
edited by Erik Bakker
on 2026/09/10 08:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -243 - Migration Magic
1 +276 - API, API
Content
... ... @@ -1,30 +1,20 @@
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 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 various smaller improvements throughout the various phases of the platform. On top of that, it introduces a structured and simple way to navigate to our API MAM functionality for all models using the API Pattern in combination with the API Key security option.
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.276 - API, API.WebHome||target="blank"]].
4 4  
5 -====New Features====
5 +==== New Features ====
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 - API MAM Migration: Migration wizard for API MAM for API Key API gateway models. This migration wizard enables you to transform your API gateway environment to support multiple authentication methods (OAuth, API key, and basic auth).
9 9  
10 -====Minor Changes====
9 +==== Minor Changes ====
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.
11 +* General - Platform: Replaced several older widgets with newer equivalents. As a result, the look and feel of various parts of the platform have changed.
22 22  
23 -====Bug fixes====
13 +===== Bug Fixes ====
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.
15 +* Flow Designer - Save and Create New Version: We fixed a bug that prevented users from transferring their flows to Deploy when their initial action was to create an “Autosaved version” of the flow. (#1816)
16 +* Deploy - Release: We improved the release activation logic to prevent some uncertainty issues during the deployment of the release in the Deploy phase.
17 +
18 +==== Remarks ====
19 +
20 +* Updated our //__emagiz.com__// certificate.