Changes for page 256 - Power Up

Last modified by Erik Bakker on 2025/11/04 12:44

From version 206.1
edited by CarlijnKokkeler
on 2024/02/28 13:20
Change comment: There is no comment for this version
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 -215 - Tiny Tales
1 +255 - Fine Form
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,14 +1,21 @@
1 -In the last sprint cycle, we focused on improving the event streaming graph. Moreover, we have done some bug fixes. First of all, the validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected.
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>>Main.Release Information.Release Blogs.215 - Tiny Tales||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 -=====Minor changes=====
5 +==== Minor changes ====
6 6  
7 -* Manage - Monitoring: The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic. (#951)
8 -* Deploy - Releases: Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available. (#1137)
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)
9 9  
10 -====Bug fixes====
13 +==== Bug fixes ====
11 11  
12 -* Generic - Login: In the login screen, users can now press "enter" to log in when the username field is selected.
13 -* Create - Flow Designer: The validation regarding undesired spaces for components that use a queue name has been improved. (#1012)
14 -* Create - Flow Designer: An issue has been fixed where removing an onramp linked to a combined entry was impossible. (#1021)
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 +