Skip to Content

Changes for page 256 - Power Up

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -237 - Fabulous Flow
1 +253 - Rince Repeat
Content
... ... @@ -1,23 +1,22 @@
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.
1 +This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.237 - Fabulous Flow||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]].
4 4  
5 -====Minor Changes====
5 +==== Major Changes ====
6 6  
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.
7 +* Deploy -> Containers: The user can now easily see the containers a flow should run on in Deploy → Containers via the button in the flow grid. Furthermore, we have overhauled the user experience on this overview to align with recent improvements to other parts of Deploy. (#976)
15 15  
16 -====Bug fixes====
9 +==== Minor changes ====
17 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.
11 +
12 +* Manage - Alerting - Triggers: Removed the deprecated, eMagiz-defined log trigger specified under the ‘other’ tab for Log entries. This trigger would generate an alert in the event of a runtime crash due to memory issues or failure to deliver a message.
13 +** Since the release of our new log alerting, it is possible to specify this alert rule yourself under the ‘logs’ tab if you still wish to receive these alerts. To do so, create four new log triggers as shown in our [[release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]]
14 +* Manage - Alerting - Triggers: Introduced a new ‘Quotas’ tab, where the quota limits for metrics, log, and error messages can be viewed per environment.
15 +
16 +==== Bug fixes ====
17 +
18 +* Create - Flow Testing: Validation message is changed to make it more transparent to the user why they could not set the desired name for the flow test message. (#1702)
19 +* Create - Flow designer: You can no longer view the save button on a standard aggregator component while not in “Start Editing“ mode (#1703)
20 +* Deploy - Releases: Height of the release details pop-up is fixed to keep it consistent between all releases, including the Create Phase Release. (#1706)
21 +* API Management - Swagger (UI): NonEmptyString is now correctly represented in the swagger resource in Create, and therefore the Swagger UI that API users can check for details. (#1652)
22 +** When the user wants to use the Swagger resource with the correct information, one of the API flows in Create requires a flow version push.