Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 98.1
edited by Erik Bakker
on 2023/07/17 21:28
Change comment: There is no comment for this version
To version 83.1
edited by Erik Bakker
on 2023/05/22 15:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -201 - Be Informed
1 +198 - Great Migration
Content
... ... @@ -1,30 +1,24 @@
1 -In the last sprint cycle, we focused on planning the upcoming quarter, finishing up, and working on the Hackathon to fix several smaller items.
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.201 - Be Informed.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 5  =====Minor changes=====
6 6  
7 -* Portal - Menu: The back button is changed to have text on it to make the navigation much clearer. (#949)
8 -* Design-Architecture: Topic Storage detail page contains help text. (#994)
9 -* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832)
10 -* Design - API Gateway: Small styling improvement on the "Edit integration page." (#954)
11 -* Create - Flow Designer: When deleting one or multiple components, you cannot change the selection before confirming or canceling the delete action. (#969)
12 -* Create - Migrate to 3rd Generation: If one or more flows break during migration, a popup will inform the flows containing errors after the migration. (#983)
13 -* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979)
14 -* Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown. All changes made in the portal that will affect your running environment are listed here. These changes can be applied to the environment or reverted. (#828)
15 -** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release.
16 -** Changes with a direct effect will not be listed (for example, restarting a machine).
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.
17 17  
18 18  ====Bug fixes====
19 19  
20 -* Design - Solutions: We fixed an issue that displayed a message mapping error despite having a passthrough API gateway. (#935)
21 -* Design - Settings: The full length of the contract number can now be registered. (#958)
22 -* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982)
23 -* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990)
24 -* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972)
25 -* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
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.
26 26  
27 -=====Infra and image changes=====
22 +====Remarks====
28 28  
29 -* Changed the endpoint for sending error messages to the eMagiz Control Tower.
30 -* Updated the Spring version of the gateway supporting deploy and manage phase operations.
24 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.