Skip to Content

Changes for page 270 - Round Round

Last modified by Erik Bakker on 2026/06/15 10:37
From version 341.1
edited by Erik Bakker
on 2026/06/15 10:37
Change comment: There is no comment for this version
To version 96.1
edited by Erik Bakker
on 2023/06/22 13:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -270 - Round Round
1 +200 - Uncharted Territories
Content
... ... @@ -1,20 +1,27 @@
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 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.
1 +In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture and others.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.270 - Round Round.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.200 - Uncharted Territories.WebHome||target= "blank"]].
4 4  
5 -==== Minor Changes ====
5 +=====Minor changes=====
6 6  
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)
7 +* Create - Flow Designer: it is possible to select multiple components by area selection on the area with a scrollbar.
8 +* Create - Flow designer: The new best practices have updated Kafka components' default values. Updated values are:
9 +** For Kafka templates:
10 +*** Batch size: 200000
11 +*** Linger: 300
12 +** For Kafka message listener containers
13 +*** Fetch min. amount: 100000
12 12  
13 -==== Bug fixes ====
15 +{{warning}}The existing Kafka components in your flows will automatically be updated with the new best practice values. To make deploying these changes more effortless for you, we will create a new version of your flows after updating the values (versions will be created in the name of model contacts) and transfer them to the Deploy phase. You can then create and deploy a new release with updated flow versions.{{/warning}}
14 14  
15 -* 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)
16 -* 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.
17 -* 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)
18 -* Create - Flow Designer: A JMS outbound channel adapter can be saved without getting an alert when using a destination expression.
19 -* Create - Flow testing: XML test messages created based on a message definition will now contain randomized data.
20 -* 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)
17 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
18 +* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture.
19 +* Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs regarding your deployment. By default, we only show some necessary logs, such as error logs, warning logs, and started runtime information logs. You can use the filter logs icons at the top of the list to show more information.
20 +* Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser. Furthermore, there is no deployment step configuration to "enable" triggers anymore.
21 +
22 +====Bug fixes====
23 +
24 +* Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957)
25 +* Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet.
26 +* Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases. Note that this functionality requires a newly deployed release. (#956)
27 +* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)