Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 103.1
edited by Erik Bakker
on 2023/08/29 11:07
Change comment: There is no comment for this version
To version 112.1
edited by Erik Bakker
on 2023/09/27 18:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -204 - Found It
1 +206 - Wrap Up
Content
... ... @@ -1,18 +1,15 @@
1 -In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact.
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 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.204 - Found It.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Wrap Up.WebHome||target="blank"]].
4 4  
5 5  =====Minor changes=====
6 6  
7 -* Deploy - Containers: Removed generation of unnecessary properties from the 3rd generation event streaming containers.
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.
8 8  
9 -====Bug fixes====
10 -
11 -* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970)
12 -* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
13 -* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release.
14 -* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
15 -
16 16  =====Infra and image changes=====
17 17  
18 -* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.
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.