Changes for page 259 - Improve Infinitely

Last modified by Erik Bakker on 2026/01/15 09:27

From version 298.1
edited by Erik Bakker
on 2025/12/01 09:20
Change comment: There is no comment for this version
To version 229.1
edited by Erik Bakker
on 2025/02/25 08:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -258 - Vale Bene
1 +239 - Modern Talking
Content
... ... @@ -1,17 +1,17 @@
1 -This release features various updates to our platform, just before the holiday season. This will be our last release of the year. We will be back releasing more on **January 15th**. With this release, you can enjoy an improved user experience in specific sections of the platform.
1 +In the last sprint, we focused on testing the eMagiz Mendix Connector and solving internal feedback on the process and the connector itself. With that behind us we are ready to launch the new eMagiz Mendix Connector to our community. With this release we will make available for all new Mendix systems in models running on the current-generation architecture. Subsequently we will implement a migration wizard aiding a simple and smooth migration to the new eMagiz Mendix Connector. On top of that, we have some minor updates to improve the quality of the platform.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.258 - Vale Bene.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.239 - Modern Talking.WebHome||target="blank"]].
4 4  
5 -==== Minor changes ====
5 +====New Features====
6 6  
7 -* Deploy - Architecture: The memory limit for specific failover containers for on-premises Windows machines can be altered by our support department if necessary.
7 +* New Mendix connector: We will introduce a new eMagiz Mendix connector. This new connector delivers improved stability and a simpler setup process. The new connector is better integrated in your eMagiz models and will receive full support. The connector can be used for new systems and will be enabled by default for new models.
8 +** A migration wizard will be released later which allows you to easily and smoothly migrate your current legacy Mendix connectors to the new Mendix connector.
8 8  
9 -==== Bug fixes ====
10 +====Minor Changes====
10 10  
11 -* Design - Data Model (Message Format): Viewing and editing permissions for the message format of different message types are fixed. The checks are corrected for all message types. (#1050)
12 -* Create - Add Integrations: Assigning a target namespace to messages based on the system being identified as a "SOAP entry connector" is corrected. Event processors no longer get the target namespace. (#1183)
13 -* Create - System Message / Data Model Message: The UI is updated immediately after removing restrictions for an attribute without the need to refresh the page. (#1707)
14 -* Create - Add Resource (Multiple places): Fixed a bug where when uploading a new (flow) resource in Create, one could select the eMagiz-generated “message definition” & “message transformation”. These, along with two deprecated resource file types, have been removed from the selectable types.
15 -* Create - Help Texts: We have fixed a bug in our help texts where the text would not show for specific input fields.
16 -* Manage - Queue dashboard: Updated message throughput panel to sometimes filter out spikey first and last observations (#1589)
12 +* Create - Flow Designer: The view button that can be found by navigating to the right panel of the Flow Designer and choosing the Support Objects tab opens a pop-up that shows a list of all support objects that can be added. This button is accessible only in view mode of the Flow Designer. (#870)
17 17  
14 +====Bug fixes====
15 +
16 +* Create - Flow Creation: Payload root Qname support object for the API gateway infra is not containing duplicates now. (#1517)
17 +* Manage - Dashboard: The manage phase dashboard no longer breaks when an error occurs in a component with an id that does not follow the [id].[system].[flow] convention, or when that value is longer than expected. (#1566)