Skip to Content

Changes for page 259 - Improve Infinitely

Last modified by Erik Bakker on 2026/01/15 09:27
From version 166.1
edited by CarlijnKokkeler
on 2023/12/04 15:52
Change comment: There is no comment for this version
To version 297.1
edited by Erik Bakker
on 2025/12/01 09:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -210 - Deployment Delights
1 +258 - Vale Bene
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,24 +1,17 @@
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 features various updates to our platform, just before the holiday season. This will be our last release of the year. We will be back releasing more on **January 15th**. With this release, you can enjoy an improved user experience in specific sections of the platform.
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>>doc:Main.Release Information.Release Blogs.258 - Vale Bene.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +==== Minor changes ====
6 6  
7 -* Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
7 +* Deploy - Architecture: The memory limit for specific failover containers for on-premises Windows machines can be altered by our support department if necessary.
8 8  
9 -=====Minor changes=====
9 +==== Bug fixes ====
10 10  
11 -* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
12 -* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images.
11 +* Design - Data Model (Message Format): Viewing and editing permissions for the message format of different message types are fixed. The checks are corrected for all message types. (#1050)
12 +* Create - Add Integrations: Assigning a target namespace to messages based on the system being identified as a "SOAP entry connector" is corrected. Event processors no longer get the target namespace. (#1183)
13 +* Create - System Message / Data Model Message: The UI is updated immediately after removing restrictions for an attribute without the need to refresh the page. (#1707)
14 +* Create - Add Resource (Multiple places): Fixed a bug where when uploading a new (flow) resource in Create, one could select the eMagiz-generated “message definition” & “message transformation”. These, along with two deprecated resource file types, have been removed from the selectable types.
15 +* Create - Help Texts: We have fixed a bug in our help texts where the text would not show for specific input fields.
16 +* Manage - Queue dashboard: Updated message throughput panel to sometimes filter out spikey first and last observations (#1589)
13 13  
14 -====Bug fixes====
15 -
16 -* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
17 -* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
18 -* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
19 -* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
20 -* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
21 -* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
22 -* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
23 -
24 -