Changes for page 270 - Round Round

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+270 - Round Round

Author

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

Content

...	...	@@ -1,45 +1,21 @@
1		-In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
	1	+This release includes improvements to our certificate rotation mechanism, which are relevant to 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 Capture, Design, and Create at the system level. Subsequently, we introduced a fix to improve the stability of interacting with Create via the flow designer and when adding and removing integrations. Enjoy reading our latest updates on the platform.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.270 - Round Round.WebHome||target="blank"]].
4	4
	5	+==== Minor Changes ====
5	5
6		-=====Minor changes=====
	7	+* General - Environment Templates: New **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** are released. Make sure to update before **August 15th, 2026**.
	8	+* General - Event Streaming: Managing the rotation of customer intermediate certificates before they expire to keep the environment operational.
	9	+* Design - System: On API-related systems, we stop activating the “OpenAPI” checkbox by default, as it was not used often enough to warrant the default behavior. (#1794)
	10	+* Design - System: When activating the “OpenAPI” option and neglecting to supply any operation, you are confronted with a message specifying what you forgot when pressing Save. (#1794)
	11	+* Design - System: Fixed an inconsistency in Event Streaming systems regarding the selected default message format. As a result, we will no longer alter the default message format when saving the corresponding system in Capture. (#1794)
	12	+* 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)
	13	+* 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.
	14	+* 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)
	15	+* Create - Flow Designer: A JMS outbound channel adapter can be saved without getting an alert when using a destination expression.
	16	+* Create - Flow testing: XML test messages created based on a message definition will now contain randomized data.
	17	+* 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)
7	7
8		-* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
9		-* Create - SSL: Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
10		-* Create - Framework: The framework used in the flow designer has been updated to the latest version.
11		-* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
12		-* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
13		-* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
14		-* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
15		-* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
16		-* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
17		-* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
18		-* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
19		-* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
20		-* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
21		-* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
22		-* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
23		-* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
24		-* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
25		-* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
	19	+==== Bug fixes ====
26	26
27		-
28		-
29		-====Bug fixes====
30		-
31		-* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
32		-* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
33		-* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
34		-* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
35		-* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
36		-* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
37		-* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
38		-* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
39		-* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
40		-
41		-
42		-
43		-=====Infra and image changes=====
44		-
45		-* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.
	21	+* Create - Flow Designer: A fix has been implemented to resolve an issue where an error popup would occasionally appear when opening the Flow Designer. (#1644)