Skip to Content

Changes for page 230 - Petite Peaks

Last modified by Carlijn Kokkeler on 2024/09/27 09:36
From version 83.1
edited by Erik Bakker
on 2023/05/22 15:20
Change comment: There is no comment for this version
To version 9.1
edited by Erik Bakker
on 2022/10/14 13:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +185 - Get Ready
Content
... ... @@ -1,24 +1,24 @@
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 +Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
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.185 - Get ready.WebHome||target="blank"]].
4 4  
5 +=====New features=====
6 +* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
7 +
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.
10 +* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
11 + ** Datagids, where there is now on hover action for example.
12 + ** Pop ups
13 + ** Context menus, also have on hover action
14 + ** Styling of scrollbars
15 +* Message Redelivery - admin logs improved to better analyze issues when they occur
16 +* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
17 +* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
16 16  
17 17  ====Bug fixes====
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.
21 -
22 -====Remarks====
23 -
24 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
20 +* Deploy - Deployment plan. Performance of page to deploy a release increased significantly
21 +* Store - Import resources was incorrectly done in specific cases, which is now fixed
22 +* Store - Target namespace will be imported when importing an XML Message Definition
23 +* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.
24 +* Store - Importing items from the store sometimes resulted in invalid JMS connection factories.