Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 83.1
edited by Erik Bakker
on 2023/05/22 15:20
on 2023/05/22 15:20
Change comment:
There is no comment for this version
To version 109.1
edited by Carlijn Kokkeler
on 2023/09/18 11:21
on 2023/09/18 11:21
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 198-GreatMigration1 +205 - World Explorers - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,24 +1,26 @@ 1 - Anothercouple of weeks have passed, so itistime foranewrelease.Wehavefocusedinthisperiodonimprovingthe migrationprocess towardsthe next-generation architectureaswell ashowthe userexperienceandinteraction with theext-generation architecture works.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. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 198-GreatMigration.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.205 - World Explores.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 + 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: You can apply your changes to environment without having an active release. 13 -* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing. 14 -(control tower, so Gen3 only) 15 -* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments. 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) 16 16 15 + 17 17 ====Bug fixes==== 18 18 19 -* 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. 20 -* 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. 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. 21 21 22 -====Remarks==== 23 23 24 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2. 24 +=====Infra and image changes===== 25 + 26 +* No infra and/or image changes is this release.