Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 113.1
edited by Carlijn Kokkeler
on 2023/09/29 14:39
Change comment: There is no comment for this version
To version 82.1
edited by Erik Bakker
on 2023/05/22 15:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Wrap Up
1 +198 - Great Migration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,15 +1,27 @@
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.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Wrap Up.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
4 4  
5 +=====New features=====
6 +
7 +
5 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.
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.
11 11  
12 -=====Infra and image changes=====
20 +====Bug fixes====
13 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.
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.