Changes for page 237.1 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 120.1
edited by Erik Bakker
on 2025/01/31 11:52
on 2025/01/31 11:52
Change comment:
There is no comment for this version
To version 112.1
edited by Erik Bakker
on 2023/09/27 18:53
on 2023/09/27 18:53
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 37.1-FabulousFlow1 +206 - Wrap Up - Content
-
... ... @@ -1,6 +1,15 @@ 1 -This release signifies our efforts to stabilizecontainers running on-premiseon Windows as part of our[[announced hotfix>>https://status.emagiz.com/incidents/h3kftq4wpg3n||target="blank"]]. It consists ofa revertof our announced functionalityregardingWindowsmemorylimits.1 +This release signifies our efforts to wrap up our quarter. It consists of several must-needed functionalities for specific use cases regarding the next-generation architecture. 2 2 3 - ====Reverts====3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Wrap Up.WebHome||target="blank"]]. 4 4 5 - * Deploy - Architecture: To preventout-of-memoryevents, thecalculation of eachruntime's memory limit is updated for all runtimesdeployed on a Windows machine.5 +=====Minor changes===== 6 6 7 +* Deploy - Releases: The related unused images in the on-premises machines will also be removed when the release is removed. 8 +* Create - Transfer settings from Design: Added a migration step. If the custom error handling is set to false, we set the error channel to “errorChannel” for all inbounds in a flow. 9 +* Create - Transfer settings from Design: Added a check in the migration that validates whether every targetNamespace is filled in when a SOAP web service is migrated and split as part of the migration to the next-generation architecture. 10 +* Create - Transfer settings from Design: Added a check in the migration that validates whether a specific old component, the Jetty server support object, remains in a flow after the migration. If so, the user is notified that they need to take action on this. 11 + 12 +=====Infra and image changes===== 13 + 14 +* New logging feature enabling us to make better choices in deprecating old encryption standards. 15 +* Carwash change to enable our direct connect offering for customers on the next-generation architecture.