Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 82.1
edited by Erik Bakker
on 2023/05/22 15:19
Change comment: There is no comment for this version
To version 120.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 -198 - Great Migration
1 +237.1 - Fabulous Flow
Content
... ... @@ -1,27 +1,6 @@
1 -Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
1 +This release signifies our efforts to stabilize containers running on-premise on Windows as part of our [[announced hotfix>>https://status.emagiz.com/incidents/h3kftq4wpg3n||target="blank"]]. It consists of a revert of our announced functionality regarding Windows memory limits.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
3 +====Reverts====
4 4  
5 -=====New features=====
5 +* 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.
6 6  
7 -
8 -=====Minor changes=====
9 -
10 -* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
11 -* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
12 -* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
13 -* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
14 -* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
15 -* Deploy - Architecture: You can apply your changes to environment without having an active release.
16 -* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
17 -(control tower, so Gen3 only)
18 -* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
19 -
20 -====Bug fixes====
21 -
22 -* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
23 -* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
24 -
25 -====Remarks====
26 -
27 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.