Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 220.1
edited by Erik Bakker
on 2025/01/27 13:22
Change comment: There is no comment for this version
To version 185.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -237 - Fabulous Flow
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,23 +1,27 @@
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 Design 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 +In the last sprint cycle, we focused on ....
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>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
5 -====Minor Changes====
5 +=====New features=====
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 - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
8 +* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
15 15  
10 +=====Minor changes=====
11 +
12 +* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13 +* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
14 +* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
15 +* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
16 +* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
18 +
16 16  ====Bug fixes====
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.
21 +* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
22 +* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
23 +* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
25 +* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
26 +
27 +