Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 112.1
edited by Carlijn Kokkeler
on 2023/10/11 12:53
Change comment: There is no comment for this version
To version 248.1
edited by Carlijn Kokkeler
on 2024/05/21 12:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +221 - Swift Shift
Content
... ... @@ -1,26 +1,18 @@
1 -In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
1 +In the last sprint cycle, we have worked on .
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.221 - Swift Shift||target="blank"]].
4 4  
5 5  =====New features=====
6 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>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
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".
8 8  
9 -=====Minor changes=====
10 -
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)
14 -
15 -
16 -====Bug fixes====
17 -
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.
22 -
23 -
24 -=====Infra and image changes=====
25 -
26 -* No infra and/or image changes is this release.
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.