Skip to Content

Changes for page 271 - Secure Ship

Last modified by Erik Bakker on 2026/06/29 09:20
From version 344.1
edited by Erik Bakker
on 2026/06/29 09:20
Change comment: There is no comment for this version
To version 199.1
edited by Erik Bakker
on 2024/02/13 15:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -271 - Secure Ship
1 +214 - System Symphony
Content
... ... @@ -1,24 +1,21 @@
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 +In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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.214 - System Symphony||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 +* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once. (#1141)
8 +* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
9 9  
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)
10 +=====Minor changes=====
14 14  
12 +* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore. (#1216)
13 +* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed.
15 15  
16 -==== Bug fixes ====
15 +====Bug fixes====
17 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.
17 +* Create - Flow Designer: The help text of the Group attribute has been improved.
18 +* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802)
19 +* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen.
21 21  
22 -==== Remarks ====
23 23  
24 -* Support employees can trigger a rollback on the intermediate certificate on the customer authorization server.