Skip to Content

Changes for page 202 - New Equilibrium

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 61.1
edited by Erik Bakker
on 2023/03/17 08:32
Change comment: There is no comment for this version
To version 3.1
edited by Erik Bakker
on 2022/10/14 13:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Giant Leap
1 +185 - Get Ready
Content
... ... @@ -1,34 +1,23 @@
1 -The release introduces improvements to our 3rd generation runtime architecture and other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
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.194 - Giant Leap.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 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.
6 6  
7 -* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]].
8 -* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers, and waking up a cloud slot will start those containers. (#889)
9 -
10 10  =====Minor changes=====
11 11  
12 -* Design - Architecture: New calculation for topic size is applied and the feedback on topic retentions bytes has more information.
13 -* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you use custom error handling on your event processors.
14 -* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
15 -* Deploy - User Management: Roles are sorted alphabetically. (#806)
16 -* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date.
17 -* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and chart, and made minor visual improvements.
18 -* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
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 +* Create - Flow Designer: small bugs ( copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
19 19  
20 20  ====Bug fixes====
21 -
22 -* Generic: We fixed an issue in that you may see a screen with a broken styling when switching among phases.
23 -* Create - Flow Designer: Removed the option to create a new resource on the resource selection popup of a simple XSD schema support object.
24 -* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902)
25 -* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filenames (>100 characters).
26 -* Deploy - Releases: You need edit rights in the test environment of the deploy phase to execute the “Update flows to latest versions” action.
27 -* Manage - Dashboard: We update the view to visualize the split entries after you migrate combined entries.
28 -* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet it occurred (#825)
29 -* Manage - Logging: Reduced the occurrence of 'Failed to send to Elastic' log messages which trigger alerts. (#898)
30 -* Manage - Alerting: Editable column shows the correct value.
31 -
32 -====Remarks====
33 -
34 -* Create - Flow designer: After the deployment, the ‘Version Compare' and 'Version Restore’ features will be unavailable for a few hours because of data migration. You will get an error stating that the version is incompatible with the selected feature until the migration is finished.
19 +* Deploy - Deployment plan. Performance of page to deploy a release increases significantly
20 +* Store - Import resources was incorrectly done in specific cases, which is now fixed
21 +* Store - Target namespace will be imported when imported XML Message Definition
22 +* Store - When exporting components, if property values contains bus name, they will be updated automatically with new bus name when importing into a new bus.
23 +* Store: Importing items from the store sometimes resulted in invalid JMS connection factories.