Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 118.1
edited by Erik Bakker
on 2023/10/10 10:06
Change comment: There is no comment for this version
To version 114.1
edited by Erik Bakker
on 2023/10/06 13:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205.1 - World Explorers
1 +205.2 - World Explorers
Content
... ... @@ -1,9 +1,15 @@
1 -This release signifies our efforts to stabilize the management of our customer models from Manage even better. It consists of several much-needed functionalities for specific use cases regarding the next-generation architecture.
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.206 - Wrap Up.WebHome||target="blank"]].
4 +
3 3  =====Minor changes=====
4 4  
5 -* Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80%
6 -* Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (Gen3 only)
7 -* Manage - Queue statistics: They are now all visible for models with a vast number of queues. This used to be cut off. (Gen3 only)
8 -* Manage - Monitoring: Removed time filter options for time windows longer than the last seven days in 3rd generation runtime statistics dashboards.
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.
9 9  
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.