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
on 2026/06/15 10:37
Change comment:
There is no comment for this version
To version 289.1
edited by Erik Bakker
on 2025/10/21 11:03
on 2025/10/21 11:03
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 70-RoundRound1 +255 - Fine Form - Content
-
... ... @@ -1,20 +1,21 @@ 1 -This release includesimprovements to ourcertificaterotationmechanismthataffectallcustomersusingour event streaming offering.Ontopof that, new **[[environmenttemplates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]**arereleased.Furthermore,additionalaccelerantsforall integrationdevelopersarehere.This includesimprovementsinhowweassist users inCapture, Design,and Createatthesystemlevel. Subsequently, weintroduceda fix to improvethestabilityof interacting with Create via theflowdesigner and when adding and removingintegrations.Enjoyreadingourlatestupdatesonthe platform.1 +This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. Additionally, we will release a new **[[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]]** for selected customers and on our flow testing engine. On top of that, we will release new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** to allow specific customers to run on our MAM functionality. 2 2 3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.2 70-RoundRound.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.255 - Fine Form.WebHome||target="blank"]]. 4 4 5 -==== Minor Changes ====5 +==== Minor changes ==== 6 6 7 -* General - Environment Templates:New**[[environmenttemplates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]**arereleased.Makesuretoupdate before**August 15th, 2026**.8 -* General - EventStreaming:Managingtherotation of customer intermediatecertificatesbeforetheyexpiretokeeptheenvironmentoperational.9 -* De sign-System:OnAPI-relatedsystems,we stopactivating the“OpenAPI”checkboxbydefault,asitwasnotusedoften enoughto warrantthedefault behavior.(#1794)10 -* Design- System:Whenactivatingthe“OpenAPI”optionandneglectingto supplyanyoperation,youare confrontedwith amessagespecifying whatyouforgot whenpressingSave.(#1794)11 -* Design-System:Fixedaninconsistencyin EventStreamingsystems regardingtheselecteddefault messageformat.Asaresult,we willno longeralter thedefaultmessageformatwhensaving thecorrespondingsystem inCapture. (#1794)7 +* General - Runtime: A new [[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]], for selected customers, and our flow testing will be made available. 8 +* General: The user can now see the names of deactived users again across the platform (i.e. flow history, Q&A). (#1163) 9 +* Deploy - Releases: We have updated the editing release behaviour for the Event streaming pattern. You now have more flexibility for you to add or remove either Event streaming processor flow(s) or Event streaming Mendix connector flow(s) in the release. 10 +** Additionally, we have also fixed the issue where adding or removing event streaming flow(s) resulted in incorrect flow(s) being included or excluded. This update ensures that the correct Event streaming flow(s) are now properly managed during release editing. 11 +* Create - Add Integrations: Users can un-transfer event streaming integrations that have the default message type messaging by using the ‘Create/Settings/Transfer settings from design/ES Integrations’. (#1485) 12 12 13 13 ==== Bug fixes ==== 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) 15 +* Design - Model Designer: Changed “align top“ and “align left“ to “align horizontally“ and “align vertically“ to be consistent with similar functionality in the Flow Designer. (#1611) 16 +* Create - Settings: The SOAP settings tab allows syncing the SOAP settings of systems in Design and Create. (#1569) 17 +* Create - Transformation: Updated the pattern used in dateTime transformations for the +HH:mm format. These used to fall back to +HHmm instead (dropping the ':'), this has now been resolved. (#1368) 18 +** Existing transformations are not automatically updated, but if you are using a custom XPath to do the transformation right now, you can now use the default functionality again. 19 +** The updated pattern (using XXX instead of ZZ) does not work on the previous generation runtime. If you are still using the previous generation runtime, and you have edited the specific part of the transformation, you can instead use the custom XPath where you use the pattern that is composed when using the dropdown menus, and replacing the XXX at the end with ZZ 20 + 21 +