Skip to Content

Changes for page 271 - Secure Ship

Last modified by Erik Bakker on 2026/06/29 09:20
From version 343.1
edited by Erik Bakker
on 2026/06/29 09:20
Change comment: There is no comment for this version
To version 264.1
edited by Erik Bakker
on 2025/06/17 09:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -271 - Secure Ship
1 +247 - Help Out
Content
... ... @@ -1,23 +1,12 @@
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 focuses on helping our community by improving various aspects of our platform in anticipation of some of the larger features that are just around the corner. So, without further ado, let's take a look at what's on the menu today!
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.247 - 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)
7 -
8 -==== Minor Changes ====
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. (#1792)
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 in line with our best practices. (#1768)
13 -
14 -
15 15  ==== Bug fixes ====
16 16  
17 -* Capture - Delete System: When being prevented from deleting a system by eMagiz, you no longer are confronted with an everlasting platypus. (#1771)
18 -* 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.
19 -* Deploy - User Management: We fixed inconsistent errors in Deploy - User Management overview, making it more reliable to manage users and their credentials.
20 -
21 -==== Remarks ====
22 -
23 -* Support employees can trigger a rollback on the intermediate certificate on the customer authorization server.
7 +* Design - Architecture: A change is made to ensure that the "Design architecture" is correctly updated based on message type changes in the Capture phase. (#1614)
8 +* Design - System: New help text is generated for the “SOAP entry connector” check box. The check box is present in the "Design phase" while editing the system. (#1413)
9 +* Create - Flow designer: On the "File item reader message source," various help texts have been added to give additional clarity on what the component does. (#1463)
10 +* Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow is corrected so that the flow is deployed with the correct flow version and component list. (#1618)
11 +* Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture. It shows the topic retention bytes, as users are only allowed to modify this variable. (#1358)
12 +* Manage - Explore (Queue Browser): The bug is fixed so that all the options within the explore section of the Manage phase are responsive at all times. (#1524)