Skip to Content

Changes for page 263 - User Update

Last modified by Erik Bakker on 2026/03/10 12:40
From version 321.1
edited by Erik Bakker
on 2026/03/10 12:40
Change comment: There is no comment for this version
To version 165.1
edited by CarlijnKokkeler
on 2023/12/04 15:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -263 - User Update
1 +210 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,19 +1,28 @@
1 -This release includes many user-driven updates to our platform to enhance your everyday work.
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.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.263 - User Update.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.210 - Deployment Delights||target="blank"]].
4 4  
5 -==== Minor changes ====
5 +=====New features=====
6 6  
7 -* Create - Flow Designer: Improved the help text of the advanced ‘Match value’ attribute of the XPath filter, so it is clear how this option of the XPath filter can be used. (#1542)
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.
8 8  
9 -==== Bug fixes ====
11 +=====Minor changes=====
10 10  
11 -* Deploy - Deployment plan execution: The failure message shown during release preparation has been improved to be more descriptive. (#1568)
12 -* Deploy - Releases: We fixed an issue where the UI of the Create phase and Deploy phase were not aligned since the Releases screen did not show the new additions, but you can find them in the Release details popup. (#1675)
13 -* Manage - Explore - Topic browser: We fixed two problems with the topic browser.
14 -** When navigating to the last page of messages on a topic’s partition, the amount of messages shown in the paging will now correspond to the number of messages on that partition (#1714)
15 -** The first page of messages on a topic’s partition will now include the last message, with offset 1 below the ‘last offset’.
16 -* Manage - Export - Data sink: When opening this page on an empty data sink bucket, there will be a warning on top of the page (“no results found”). (#1096)
17 -==== Remarks ====
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.
18 18  
19 -* General - Portal: We have removed part of our platform's functionality as it was not used anymore.
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 +