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 153.1
edited by CarlijnKokkeler
on 2023/10/26 12:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -255 - Fine Form
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,21 +1,37 @@
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 +In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components and we did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
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.207 - Aligned State .WebHome||target="blank"]].
4 4  
5 -==== Minor changes ====
5 +=====Runtime release notes=====
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 +There is a new eMagiz Mendix connector available because a memory leak was found, only affecting Mendix connectors that have been migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture. For specific information, please check out this link to the [[release notes>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime/eMagiz%20Mendix%20Connector%20-%206.0.2/]]
12 12  
13 -==== Bug fixes ====
9 +=====Minor changes=====
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
11 +* Design - Message Mapping: The button 'Import from Store' will directly open the store.
12 +* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
13 +* Create - Flow Designer: When importing items from the store, flow fragments that are hidden in Design will be listed under the versions in Create. (#1044)
14 +* Create - Flow Designer: Resources without names won't trigger error messages when users select components. (#950)
15 +* Create - Flow Designer: A migration step has been added, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
16 +* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read-only mode.
17 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
18 +* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
19 +* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
20 +* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
21 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
22 +* Manage - Data Sink: The data sink page has been moved to the “Explore” tab. (#946)
23 +* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of the configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
24 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
25 +* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
20 20  
27 +====Bug fixes====
21 21  
29 +* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
30 +* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
31 +* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
32 +* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
33 +
34 +
35 +=====Infra and image changes=====
36 +
37 +* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.