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 190.1
edited by CarlijnKokkeler
on 2024/01/17 08:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -271 - Secure Ship
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,24 +1,16 @@
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 providing new cloud templates that improve auto-healibng. Moreover, components and deployment steps have been created to support a failover setup. Lastly, bug fixes regarding message mapping and topic data models 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.212 - Failover Fiesta||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 +* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
8 +* Create - Flow Designer: New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
9 +* Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
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)
11 +====Bug fixes====
14 14  
13 +* Design - Message Mapping: We have improved our merging functionality within our Store offering to avoid unexpected results after merging.
14 +* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements.
15 15  
16 -==== 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.
21 -
22 -==== Remarks ====
23 -
24 -* Support employees can trigger a rollback on the intermediate certificate on the customer authorization server.