Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 165.1
edited by Carlijn Kokkeler
on 2023/12/04 15:30
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 -210 - Deployment Delights
1 +221 - Swift Shift
Content
... ... @@ -1,28 +1,18 @@
1 -In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
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.210 - Deployment Delights||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 - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
8 -* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 -* All - The next generation architecture is the default now. New models will use this generation as default.
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".
10 10  
11 -=====Minor changes=====
12 -
13 -* Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
14 -* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
15 -* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
16 -
17 -====Bug fixes====
18 -
19 -* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
20 -* Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.
21 -* Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
22 -
23 -
24 -
25 -
26 -
27 -
28 -
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.