Skip to Content

Changes for page 270 - Round Round

Last modified by Erik Bakker on 2026/06/15 10:37
From version 160.1
edited by CarlijnKokkeler
on 2023/11/22 14:57
Change comment: There is no comment for this version
To version 339.1
edited by Erik Bakker
on 2026/06/01 09:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +269 - Additional Acceleration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,33 +1,12 @@
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 +This release includes additional accelerants for all integration developers out there. This includes improvements in the flow designer navigation and the missing properties functionality. Subsequently, we introduced a fix to improve the stability of our flow designer. Enjoy reading our latest updates on the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.269 - Additional Acceleration.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +==== Minor Changes ====
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 +* Create - Flow Designer: When part of an integration is opened for the first time, the entire flow is generated as an initial version so that the user can navigate to the previous and next flow using the inbound and outbound components. (#1660)
8 +* Deploy - Release - Missing Properties: To improve overall performance, we update the missing properties list in such a way that we do not need to recalculate the full list every time a user makes a change in the list. Furthermore, various UI/UX improvements have been made throughout the process to optimize the user experience. (#1796)
10 10  
11 -=====Minor changes=====
10 +==== Bug fixes ====
12 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 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
15 -* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
16 -* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
17 -
18 -====Bug fixes====
19 -
20 -* Create - Flow Designer: An issue has been fixed in the flow designer where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
21 -* Create - Flow Designer: We added a migration step to set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
22 -* 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.
23 -* Manage - Monitoring - We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that has just migrated to the next generation architecture.
24 -
25 -====Infra and image changes====
26 -
27 -* Infra: New logging feature enabling us to make better choices in encryption standards.
28 -
29 -
30 -
31 -
32 -
33 -
12 +* Create - Flow Designer: A fix has been implemented to resolve an issue where an error popup would occasionally appear when opening the Flow Designer. (#1644)