Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 110.1
edited by Carlijn Kokkeler
on 2023/09/18 11:21
Change comment: There is no comment for this version
To version 114.2
edited by Erik Bakker
on 2023/10/06 13:09
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +2052 - World Explorers
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,26 +1,15 @@
1 -In the last sprint cycle, we focused on what we show in Manage concerning the next-generation architecture. Furthermore, we will release a new cloud template. 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 much-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.205 - World Explorers.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 -=====New features=====
6 -
7 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template release notes for more information.
8 -
9 9  =====Minor changes=====
10 10  
11 -* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
12 -* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
13 -* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052)
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.
14 14  
15 -
16 -====Bug fixes====
17 -
18 -* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
19 -* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
20 -* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
21 -* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
22 -
23 -
24 24  =====Infra and image changes=====
25 25  
26 -* No infra and/or image changes is this release.
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.