Changes for page 271 - Secure Ship

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

From version 103.1
edited by Erik Bakker
on 2023/08/29 11:07
Change comment: There is no comment for this version
To version 342.1
edited by Erik Bakker
on 2026/06/29 09:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -204 - Found It
1 +271 - Secure Ship
Content
... ... @@ -1,18 +1,22 @@
1 -In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact.
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.204 - Found It.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 - Containers: Removed generation of unnecessary properties from the 3rd generation event streaming containers.
8 +==== Minor Changes ====
8 8  
9 -====Bug fixes====
10 +* 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. (#)
11 +* Create - Flow Designer: Selecting a parameter when configuring the XSLT parameters of the XSLT transformer can be done with a dropdown. (#1026)
12 +* 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 according to our best practices. (#1768)
10 10  
11 -* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970)
12 -* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
13 -* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release.
14 -* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
15 15  
16 -=====Infra and image changes=====
15 +==== Bug fixes ====
17 17  
18 -* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.
17 +* Create - Add Integrations: A more informative message is shown to the user if and when an automated flow configuration has failed. Additionally, the SOAP integrations can be recreated and edited. (#1377)
18 +* Create - Add Integrations: Fixed a specific case where changing a system to be a Mendix connector in the design phase did not correctly influence the deploy phase.
19 +* Create - Overview: We allow users to open (and reset) connector infra flows for on-premises API systems via the context menu. This makes the navigation to these connector infra flows consistent across patterns. (#1297)
20 +* Create - Flow Designer: A JMS outbound channel adapter can be saved without getting an alert when using a destination expression.
21 +* Create - Flow testing: XML test messages created based on a message definition will now contain randomized data.
22 +* Deploy - Releases (Swagger UI): Ensure that when you click the “Swagger UI” button in Deploy Releases, you are always redirected to the corresponding Swagger UI page, not the home page of our platform. (#1797)