Changes for page 271 - Secure Ship

Last modified by Erik Bakker on 2026/06/29 09:20

From version 255.1
edited by Erik Bakker
on 2025/05/21 09:01
Change comment: There is no comment for this version
To version 344.1
edited by Erik Bakker
on 2026/06/29 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 +271 - Secure Ship
Content
... ... @@ -1,17 +1,24 @@
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 includes improvements to our certificate rotation mechanism that affect all customers using our event streaming offering. On top of that, new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** are released. Furthermore, additional accelerants for all integration developers are here. This includes improvements in how we assist users in Design, Create, and Deploy.
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.271 - Secure Ship.WebHome||target="blank"]].
4 4  
5 -====Minor Changes====
5 +==== New Features ====
6 +* Create - Flow Designer: When copy-pasting flow components with support objects, if a similar support object exists in the target flow, you can choose whether to copy the support object or re-use the existing one. (#978)
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)
10 -* General - eMagiz Connector: The new version is available in the Mendix Marketplace.
11 -** The "eMagiz Connector" Mendix module has been updated in preparation for event streaming support.
8 +==== Minor Changes ====
12 12  
13 -====Bug fixes====
10 +* General - Environment Templates: New **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** are released. Make sure to update before **August 29th, 2026**.
11 +* Design - API Catalog: Removed the “Server” button from this overview, along with all unique configuration related to it, as the button no longer served a function. (#1792)
12 +* Create - Flow Designer: Selecting a parameter when configuring the XSLT parameters of the XSLT transformer can be done with a dropdown. (#1026)
13 +* Deploy - Containers: The “flows that should run on” overview has been restructured to display the main information by default, with an option to show additional information if needed. Furthermore, updated the styling in line with our best practices. (#1768)
14 14  
15 -* 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)
16 -* 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)
17 -* 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)
15 +
16 +==== Bug fixes ====
17 +
18 +* Capture - Delete System: When being prevented from deleting a system by eMagiz, you no longer are confronted with an everlasting platypus. (#1771)
19 +* Deploy - System: We fixed an issue that, on some occasions, the wrong file location is set for the H2 database if the runtime runs on an on-premises machine.
20 +* Deploy - User Management: We fixed inconsistent errors in Deploy - User Management overview, making it more reliable to manage users and their credentials.
21 +
22 +==== Remarks ====
23 +
24 +* Support employees can trigger a rollback on the intermediate certificate on the customer authorization server.