Skip to Content

Changes for page 273 - Squash Squash

Last modified by Erik Bakker on 2026/07/27 11:44
From version 287.1
edited by Erik Bakker
on 2025/10/21 10:20
Change comment: There is no comment for this version
To version 346.1
edited by Erik Bakker
on 2026/07/27 08:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -255 - Fine Form
1 +273 - Squash Squash
Content
... ... @@ -1,21 +1,20 @@
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.
1 +This release includes various smaller improvements throughout the various phases of the platform. On top of that, we have updated certain parts of our Mendix project to their respective latest version.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.255 - Fine Form.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.273 - Squash Squash.WebHome||target="blank"]].
4 4  
5 -==== Minor changes ====
5 +==== Minor Changes ====
6 6  
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)
7 +* Deploy - History (Releases): Introduced various changes to this overview to make the information we show here more specific. The main changes are that we show a full timestamp in the “When” column instead of the date itself, and the “eye” icon is only present when the registered audit log exceeds a predefined length. (#1779)
8 +* Create - Flow Designer (OAuth Interceptor): Various help texts for this component have been updated to provide additional clarity on its functionality and more advanced configurations. (#1761)
12 12  
10 +
13 13  ==== Bug fixes ====
14 14  
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
13 +* Design - API Catalog (Operation - Response): A user can define an HTTP range as the HTTP Status Code for an operation's response, as suggested by the help text. (#1764)
14 +* Create - Overview: Number of errors in transformation is reflected correctly in offramp flow.
15 +* Create - Flow Designer (SFTP/FTP Outbound Channel Adapters): Ensured that the correct help text is shown for the Temporary remote directory configuration option. (#1754)
16 +* Deploy - Releases (Missing Properties): Nested emagiz properties are removed from the missing properties page. (#1803)
20 20  
18 +==== Remarks ====
21 21  
20 +* Updated various UI related modules within our Mendix project to their respective latest version.