Changes for page 270 - Round Round
Last modified by Erik Bakker on 2026/06/15 10:37
From version 72.1
edited by Erik Bakker
on 2023/04/28 08:08
on 2023/04/28 08:08
Change comment:
There is no comment for this version
To version 340.1
edited by Erik Bakker
on 2026/06/15 10:00
on 2026/06/15 10:00
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 - 196-TheLast Post1 +270 - Round Round - Content
-
... ... @@ -1,38 +1,21 @@ 1 - Here's our firstreleaseofthisquarter.We havedeliveredadditional small(bug)fixes in thisrelease and released theLiveFlowtestingfeature.Thelastisa realimprovementduringthedevelopmentprocessofaflow.Furthermore,you willfindseveralimprovementsintheway of workfornextGen environments.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. 196-TheLast Post.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 -==== =Newfeatures=====5 +==== Minor Changes ==== 6 6 7 -* Create - Flow Testing: so far, the Flow Testing allows test eMagiz flows by defining the testing point on the starts and the end points and comparing the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with real endpoint. That means that an “http output gateway” can be marked in “Live Mode”, if so, the http output gateway will send its http request to the real endpoint and received the result so we can go further with testing. 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) 8 8 9 -==== =Minorchanges=====19 +==== Bug fixes ==== 10 10 11 -* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’) 12 -* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can not change CDM message definition, Gateway message definition, even Event streaming message definition without the proper right. 13 -* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran. 14 -* Administration-User management: Company contact can edit permissions of models that fall under child companies 15 -* Administration: Contracts page removed 16 -* Create-Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter. 17 -* Deploy - Releases: We reduced the time it takes to prepare a release, before it can be deployed. The process of building runtime images has been optimized. 18 -* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible. 19 -* Design - Store: You are able to see some warning messages when you import a transformation from store. Because your imported transformation is required some information from the related store fragment. You should include that store fragment to avoid a breaking transformation in Create phase after importing. Afterward, we will update your existing flow component transformer to make it work correctly. 20 -* Design - Store: We updated importing to help you avoiding an error during importing store item that will break your message definition in some special cases. 21 -* Create - Store: We excluded automatically resources that are not good enough from the exporting wizard. Then you will easy to recognize a problem and avoid creating unusable store item. 22 -* Flow Designer: Resources in "Unused resources" section can be marked as used for the case that the resources are referred by components through property placeholders or in custom spel expressions. 23 -* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests, if that parameter was not supplied. Please reset your entry flow to apply the fix. 24 -* Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401, if no API-Key was supplied. Please reset your entry flow to apply the fix. 25 -* Design - Store: We fixed an issue that you import the message definition(s) and a specialized DataType of imported message definition(s) are not matched with the exported message definition(s). Now, they are matched and your transformation won't get issues. 26 -* Create-Resources: When viewing a resource, its full name will be shown, removing the need to download the resource in order to obtain its name 27 -* Create - Flow designer: Improve responsiveness of resources tab at right panel 28 -* Manage - Explore: New button to delete queue is added and only visible for Expert Service (Admin) 29 - 30 -====Bug fixes==== 31 - 32 -* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They now better explain what you need them for and mention important security considerations. 33 -* Create - Flow designer: Various small (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages. 34 -* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs. 35 -* Deploy - Releases: We fixed an issue, where after removing containers from a machine, during execution of the deployment plan, the removed containers are not recognized as change, causing the ‘Deploy machine’ step to be skipped. 36 - 37 -====Remarks==== 38 - 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)