Changes for page 259 - Improve Infinitely
Last modified by Erik Bakker on 2026/01/15 09:27
From version 298.1
edited by Erik Bakker
on 2025/12/01 09:20
on 2025/12/01 09:20
Change comment:
There is no comment for this version
To version 300.1
edited by Erik Bakker
on 2026/01/15 09:20
on 2026/01/15 09:20
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -25 8-ValeBene1 +259 - Improve Infinitely - Content
-
... ... @@ -1,17 +1,21 @@ 1 -This release features various updates to our platform, just before the holiday season.This will be our last releaseofthe year. We will be back releasingmoreon**January15th**. With thisrelease,youcanenjoyanimproveduserexperiencein specificsectionsoftheplatform.1 +This release features various updates to our platform, just after the holiday season. Apart from various more minor improvements, we have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V350.WebHome||target="blank"]] for **all** customers. 2 2 3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.25 8-ValeBene.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.259 - Improve Infinitely.WebHome||target="blank"]]. 4 4 5 +==== New features ==== 6 + 7 +* General - Runtime Image: Maintenance update where we primarily updated Spring Boot from version 3.4.1 to 3.5.8 and ensured all our external libraries are up-to-date. 8 + 5 5 ==== Minor changes ==== 6 6 7 -* Deploy - Architecture: The memory limit for specific failover containers for on-premises Windows machines can be altered by our support department if necessary. 11 +* Create - Flow Designer: Selector expression is added on the channel interceptors page. (#1738) 12 +* Manage - Error Messages: Search by complete flow name functionality is added to the flows with error messages page. Additionally, the grid is updated to improve the page's appearance. (#1738) 8 8 9 9 ==== Bug fixes ==== 10 10 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) 16 +* Create - Transformation: The content section of the XSLT snippet is converted to an XML editor to beautify the field. (#1739) 17 +* Create - Transformation: Validation feedback is visualised on the flat file field right before the save action to provide clarity to the user. (#891) 18 +* Create - Transformation: The same display name was being used for two similar support objects, which caused confusion. The incorrectly labeled object has now been renamed. The second "Byte array length header (de)serializer" has been renamed to "ByteArrayRawSerializer". (#1751) 19 +* Deploy - Known Hosts String: When you create a new property and select the drop-down called “Data type”, choose the option called “Known hosting string”. Behind the “Value” field, a cog wheel appears. It leads you to a pop-up. In this pop-up, the Host and Port fields have been swapped. We did it because this ordering aligns with the common defaults used across IT systems. (#1749) 20 +* Monitoring - Runtimes: two graphs, namely “Problematic runtimes memory usage” and “Max memory usage”, are fixed and show correct information. (#1654) 17 17