Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55

From version 248.1
edited by Carlijn Kokkeler
on 2024/05/21 12:12
Change comment: There is no comment for this version
To version 82.1
edited by Erik Bakker
on 2023/05/22 15:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +198 - Great Migration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,18 +1,27 @@
1 -In the last sprint cycle, we have worked on .
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.221 - Swift Shift||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  =====New features=====
6 6  
7 -* Q & A: Search results are now persisted when pressing the back button after opening a question in the community Q & A. (#1324)
8 -* Catalog: We have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
9 -* Design - CDM/System message: A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. (#151)
10 -* Design - System message: Moving an attribute in the datamodel is now directly shown in the tree structure as well. (#151)
11 -* Design - CDM/API Data model/ES data model and system message: The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. (#151)
12 -* Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group.
13 -* Deploy - Architecture: When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
14 14  
15 -=====Bug fixes=====
16 -* Design - System messages: When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. (#140)
17 -* Deploy - Containers: The delete behaviour of containers in the container overview has been improved. (#1053)
18 -* Deploy - API Gateway: We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.
8 +=====Minor changes=====
9 +
10 +* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
11 +* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
12 +* 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.
13 +* 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.
14 +* 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.
15 +* Deploy - Architecture: You can apply your changes to environment without having an active release.
16 +* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
17 +(control tower, so Gen3 only)
18 +* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
19 +
20 +====Bug fixes====
21 +
22 +* 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.
23 +* 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.
24 +
25 +====Remarks====
26 +
27 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.