Skip to Content

Changes for page 256 - Power Up

Last modified by Erik Bakker on 2025/11/04 12: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 266.1
edited by Erik Bakker
on 2025/06/17 09:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -255 - Fine Form
1 +247 - Help Out
Content
... ... @@ -1,21 +1,12 @@
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 focuses on helping our community by improving various aspects of our platform in anticipation of some of the larger features that are just around the corner. So, without further ado, let's take a look at what's on the menu today!
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>>Main.Release Information.Release Blogs.247 - Help Out.WebHome||target="blank"]].
4 4  
5 -==== Minor changes ====
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)
12 -
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
20 -
21 -
7 +* Design - Architecture: A change is made to ensure that the "Design architecture" is correctly updated based on message type changes in the Capture phase. (#1614)
8 +* Design - System: New help text is generated for the “SOAP entry connector” check box. The check box is present in the "Design phase" while editing the system. (#1413)
9 +* Create - Flow designer: On the "File item reader message source," various help texts have been added to give additional clarity on what the component does. (#1463)
10 +* Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow are corrected so that the flow is deployed with the correct flow version and component list. (#1618)
11 +* Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture. It shows the topic retention bytes, as users are only allowed to modify this variable. (#1358)
12 +* Manage - Explore: The bug is fixed so that all the options within the explore section of the Manage phase are responsive at all times. (#1524)