Skip to Content

Changes for page 247.1 - Help Out

Last modified by Erik Bakker on 2025/06/25 19:51
From version 262.1
edited by Erik Bakker
on 2025/06/17 09:07
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 -247 - Help Out
1 +237 - Fabulous Flow
Content
... ... @@ -1,12 +1,23 @@
1 -This release focuses on helping our community by improving various aspects of our platform in anticipation of some of the larger features that are just around the corner. So, without further ado, let's take a look at what's on the menu today!
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>>Main.Release Information.Release Blogs.247 - Help Out.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 - Architecture: The "Design architecture" is not updated based on message type changes in the Capture phase. (#1614)
8 -* Create - Flow designer: New help text is generated for the “SOAP entry connector” check box. The check box is present in the "Design phase" while editing the system. (#1413)
9 -* Create - Flow designer: On the "File item reader message source," various help texts have been added to give additional clarity on what the component does. (#1463)
10 -* Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow is corrected so that the flow is deployed with the correct flow version and component list. (#1618)
11 -* Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture. It shows the topic retention bytes, as users are only allowed to modify this variable. (#1358)
12 -* Manage - Explore (Queue Browser): The bug is fixed so that all the options within the explore section of the Manage phase are responsive at all times. (#1524)
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 +
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.