Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 84.1
edited by Erik Bakker
on 2023/05/26 08:40
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 -198 - Great Migration
1 +206 - Wrap Up
Content
... ... @@ -1,23 +1,15 @@
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.
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.198 - Great Migration.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 -* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
8 -* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
9 -* 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.
10 -* 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.
11 -* 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.
12 -* Deploy - Architecture: When pressing "Apply to Environment" in Deploy -> Architecture there is no hard dependencies anymore on the (active) release when running in the next generation architecture. This makes it more clear and tangible what function is necessary for what goal.
13 -* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14 -* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
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.
15 15  
16 -====Bug fixes====
12 +=====Infra and image changes=====
17 17  
18 -* 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.
19 -* 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.
20 -
21 -====Remarks====
22 -
23 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
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.