Skip to Content

Changes for page 259 - Improve Infinitely

Last modified by Erik Bakker on 2026/01/15 09:27
From version 292.1
edited by Erik Bakker
on 2025/11/04 12:44
Change comment: There is no comment for this version
To version 223.1
edited by Erik Bakker
on 2025/01/31 11:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -256 - Power Up
1 +237 - Fabulous Flow
Content
... ... @@ -1,15 +1,23 @@
1 -This release features various updates to our platform, with a user-centric focus, as we work on improved functionality for our new event streaming broker and API Gateway. All those improvements will be shared in the future once everything is ready. Additionally, we want to raise awareness that several new **[[environment templates>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]** have been released that need to be updated before **December, 14th**. So if you have yet to update please take the necessary actions.
1 +In the last sprint, we focused on improving the flow back and forth between the various phases in eMagiz by solving several feedback items related to Design, Create, and Deploy and the interaction between these three phases. We have also improved the memory calculation for all runtimes running on a Windows machine. Moreover, we have updated the styling of our graphs in the Manage phase.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.256 - Power Up.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.237 - Fabulous Flow||target="blank"]].
4 4  
5 -==== Bug fixes ====
5 +====Minor Changes====
6 6  
7 -* Design - System Message: Improved performance of saving entities whith a large number of attributes. (#1731)
8 -* Design - Store: Two fixes on importing store items for synchronous messages. (#1579)
9 -** From store functionality for API Gateway is restored.
10 -** Additionally, users can import store item to synchronous system message - response message.
11 -* Design - Create - System Message (API integrations) - The request system message correctly displays the message definition (#1713)
12 -* Create - Add Integrations: We have fixed a bug where some Mendix systems could face an error when trying to add an event streaming integration in Create.
13 -* Deploy - Containers: Debug icon has on hover text (#1725)
14 -* Manage - Alerting: Partial words from an alert's description can be searched and still return accurate results. (#1726)
7 +* Create - Flow Designer: Validation feedback and help text updates for the following components: SMB outbound gateway, SMB session factory, and SMB composite list filter. (#1461)
8 +* Create - Flow Designer: Styling of the following components has been updated. (#1544)
9 +** XML to EDI transformer
10 +** EDI to XML transformer
11 +** XML to UN/EDIFACT transformer
12 +** UN/EDIFACT to XML transformer
13 +* Deploy - Architecture: To prevent out-of-memory events, the calculation of each runtime's memory limit is updated for all runtimes deployed on a Windows machine.
14 +* Manage - Statistics: We have updated our monitoring graph technology, including minor styling updates across the different current-generation monitoring dashboards.
15 15  
16 +====Bug fixes====
17 +
18 +* Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456)
19 +* Create - Add Integrations: When removing the last integration from a system in create, the container infra flows are also removed from the create phase release. (#1559)
20 +* Create - Flow Testing: Users can navigate to all pages for the logs in their flow test. (#1532)
21 +* Deploy - Releases: The flow version for the Create release on the Deploy phase is synced for that specific flow automatically when the user resets the flow in the Create phase. (#1523)
22 +* Deploy - Architecture: Searching in the start/stop flows overview, and the queue browser can now be done from any page in the overviews. (#1511)
23 +* Manage - Alerting: If the message in a log or error contained a Windows line break (\r\n), and a log or error alert was configured that matched it, an alert would be generated, but no email would be sent out.