Skip to Content

Changes for page 271 - Secure Ship

Last modified by Erik Bakker on 2026/06/29 09:20
From version 342.1
edited by Erik Bakker
on 2026/06/29 09:03
Change comment: There is no comment for this version
To version 267.1
edited by Erik Bakker
on 2025/06/24 09:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -271 - Secure Ship
1 +2471 - Help Out
Content
... ... @@ -1,22 +1,11 @@
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.
1 +This release introduces the ability for beta models to run on our new event broker. With this critical step being reached, we can migrate the first set of beta customers to the new event broker while simultaneously further developing this proposition.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.271 - Secure Ship.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2471 - Help Out.WebHome||target="blank"]].
4 4  
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)
5 +==== New features ====
7 7  
8 -==== Minor Changes ====
7 +* General - Event Streaming: Run your event streaming solution on our new event broker at DSH. Please note that we will initially release this functionality as a **beta** feature. This means it is currently only available to a select number of models. Once this functionality is more developed, we will share more information on this.
9 9  
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)
9 +==== Minor changes ====
13 13  
14 -
15 -==== Bug fixes ====
16 -
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)
11 +* Deploy - User Management: Updated the UI/UX for this overview to provide more context to our users regarding their connected system users, their roles, and their rights.