Changes for page 271 - Secure Ship

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-210 - Deployment Delights
	1	+271 - Secure Ship

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -1,28 +1,24 @@
1		-In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
	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.210 - Deployment Delights||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		-=====New features=====
	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 - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
8		-* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9		-* All - The next generation architecture is the default now. New models will use this generation as default.
	8	+==== Minor Changes ====
10	10
11		-=====Minor changes=====
	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)
12	12
13		-* Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
14		-* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
15		-* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
16	16
17		-====Bug fixes====
	16	+==== Bug fixes ====
18	18
19		-* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
20		-* Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.
21		-* Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
	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.
22	22
	22	+==== Remarks ====
23	23
24		-
25		-
26		-
27		-
28		-
	24	+* Support employees can trigger a rollback on the intermediate certificate on the customer authorization server.