Skip to Content

Changes for page 259 - Improve Infinitely

Last modified by Erik Bakker on 2026/01/15 09:27
From version 253.1
edited by Erik Bakker
on 2025/05/19 15:16
Change comment: There is no comment for this version
To version 298.1
edited by Erik Bakker
on 2025/12/01 09:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -245 - Limited Exposure
1 +258 - Vale Bene
Content
... ... @@ -1,15 +1,17 @@
1 -In the last sprint, we released functionality to increase the stability of Windows runtimes. This means that those runtimes are now better limited in the memory they can utilize to prevent resource limitations on the machine level. Furthermore, we introduced several small improvements on the platform.
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.245 - Limited Exposure.WebHome||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 -====Minor Changes====
5 +==== Minor changes ====
6 6  
7 -* Deploy - General: For current deployed Windows machines, the calculation of the memory limit of containers is updated, which will prevent memory leaks.
8 -* Deploy - Architecture: You can now manually set the memory of your on-premise machine in design architecture. This memory is considered when checking the machine's health in "Deploy architecture."
9 -* Q&A Forum - Moderation: Q&A Forum Moderators can choose to receive notifications by email about newly posted questions on the forum. (#1401)
7 +* Deploy - Architecture: The memory limit for specific failover containers for on-premises Windows machines can be altered by our support department if necessary.
10 10  
11 -====Bug fixes====
9 +==== Bug fixes ====
12 12  
13 -* Create - Flow designer: The help text for the "value expression" field for the "duplicate detector" support object better reflects the purpose of that field while also providing practical examples. (#1376)
14 -* Create - Flow Designer: The help text for the "virtual root "field of the "JSON source factory "support object better reflects the functionality and behavior of the field while also stating that arrays on the root level are not supported. (#1459)
15 -* General - User Access: Users with view rights in Deploy and Manage (but no rights in the other phases) can now see data in Manage grids. (#1525)
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)
17 +