Changes for page 257 - Changing Chameleon

Last modified by Erik Bakker on 2025/11/20 16:12

From version 280.2
edited by Erik Bakker
on 2025/09/21 21:19
Change comment: Update document after refactoring.
To version 286.1
edited by Erik Bakker
on 2025/10/21 10:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -253 - Rince Repeat
1 +255 - Fine Form
Content
... ... @@ -1,16 +1,21 @@
1 -This release features numerous updates to our platform, with a user-centric focus. This release, we focused on adding functionality to our new event streaming offering, on which we will share more in the next release blog.
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.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.252 - Frostline.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 -==== New features ====
6 -
7 -* We have introduced the ability to move flows to another container, and be able to move their respective properties along side with them. *
8 -
9 9  ==== Minor changes ====
10 10  
11 -* Create - Transformation: Option to convert a string value to an enumeration by setting value mapping rules inside the “From string transformer“ attribute operation.
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 +* 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.
9 +** 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.
10 +* 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)
11 +* General: The user can now see the names of deactived users again across the platform (i.e. flow history, Q&A). (#1163)
12 12  
13 13  ==== Bug fixes ====
14 14  
15 -* Users belonging to Mendix systems will no longer be shown in Deploy > User management. All required information for these Mendix systems can be found in Deploy > Mendix connectors.
16 -* Create - Transfer Integration: in case an integration is not a part of any release, it is possible to removed it from Create phase. (#800)
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 +