Changes for page 275 - Summer Sounds
Last modified by Erik Bakker on 2026/08/24 13:37
From version 73.1
edited by Erik Bakker
on 2023/04/28 08:16
on 2023/04/28 08:16
Change comment:
There is no comment for this version
To version 350.1
edited by Erik Bakker
on 2026/08/24 10:14
on 2026/08/24 10:14
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 +275 - Summer Sounds - Content
-
... ... @@ -1,35 +1,31 @@ 1 - Here's our firstreleaseof this quarter.Wehavedeliveredadditional small(bug) fixesin thisreleaseandreleasedtheLive Flow testing feature.The last isa realimprovementduringthedevelopment processofa flow. Furthermore,you will findseveralimprovementsintheway of workfor nextGenenvironments.1 +This release includes several smaller improvements across the platform's phases. We also updated certain parts of our Mendix project to their latest versions. 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.275 - Summer Sounds.WebHome||target="blank"]]. 4 4 5 -==== =Newfeatures=====5 +==== Minor Changes ==== 6 6 7 -* Create - Flow Testing: Till now, the Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), run them and compare the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with an actual "live" endpoint. As a result a “HTTP outbound gateway” can be set in “Live Mode”. When you do this, the HTTP outbound gateway will send its HTTP request to the actual endpoint. Consequently the response will be handled by the flow in the flow test so you can determine whether the actual endpoint behaves as expected. 7 +* General - Platform: As part of our regular system maintenance, we have upgraded the application to the Mendix LTS version 11.12. 8 +** This upgrade improves the platform's overall stability, security, and long-term reliability. This upgrade has no impact on daily operations. 9 +** This update ensures the application remains well-supported and ready for future enhancements. 10 +* General - Legacy Event Streaming Broker: Updated Kafka Broker version from 3.8.1 to 3.9.2. This is a maintenance update and should not affect any functionality. 11 +* General - eMagiz Connector: We will release a new version of the eMagiz Connector (1.2.0) that is compatible with Mendix 11 (11.12.1 and higher). 12 +* Create - Flow designer: Various updates to flow designer components are introduced in preparation for the Spring 7 migration. 13 +** Two support object components are no longer available to create in the current generation. 14 +*** Access decision manager 15 +*** OAuth2 Bearer token authentication filter. 16 +** We updated validation for a few components in preparation for the Spring 7 migration to address missing or incorrect settings after the components are saved. Note that these updated settings can lead to alerts when opening a flow that currently has an incorrect configuration 17 +*** File inbound channel adapter 18 +*** TCP inbound channel adapter 19 +*** JMS outbound gateway 20 +*** Standard content enricher > Property 21 +*** HTTP security 22 +** On top of that, some components are end of support. They are no longer used in any client model and are therefore removed from the list of selectable Flow Designer components. 8 8 9 -===== Minorchanges=====24 +===== Bug Fixes ==== 10 10 11 -* 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. 12 -* 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. 13 -* 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. 14 -* 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. 15 -* 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. 16 -* Create - Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter. 17 -* Create - Flow designer: Improve responsiveness of resources tab at right panel. 18 -* Create - 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. 19 -* 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. 20 -* 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. 21 -* 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 22 -* 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. 23 -* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible. 24 -* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’) 25 -* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran. 26 -* Manage - Explore: A new button to delete queue is added. This button is only visible for authorized personnel. 27 -* Administration -User management: Company contact can edit permissions of models that fall under child companies. 28 -* Administration - Overview: Contracts page removed. 26 +* Design - Architecture: Updated display order calculation for machines when adding or moving them. (#1113) 27 +* Deploy - Swagger UI: Downloaded Swagger documentation has the full correct schema. (#1811) 29 29 30 -==== Bugfixes====29 +==== Remarks ==== 31 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 -* 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. 35 -* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs. 31 +* Updated various UI related modules within our Mendix project to their respective latest version.