Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 141.1
edited by Carlijn Kokkeler
on 2023/10/23 16:54
Change comment: There is no comment for this version
To version 29.1
edited by Erik Bakker
on 2022/11/24 11:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,29 +1,22 @@
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 did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
1 +The release brings several improvements to our 3rd generation runtime and its interaction with the portal. On top of that, we have several feedback items and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]].
4 4  
5 5  =====Minor changes=====
6 6  
7 -* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 -* Design - Performance: Performance improvements for the Flow Designer have been implemented.
9 -* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
10 -* 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 5, 7 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)
11 -* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
12 -* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
13 -* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946)
14 -* 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%.
15 -For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
16 -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.
17 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
18 -* 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)
7 +* General: Code mapping is now available for models migrating to the 3rd generation runtime.
8 +* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785)
9 +* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
10 +* Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems. This means that when a runtime is being deployed, which is constantly crashing and thereby causing problems, the restart of the runtime is limited to just five times. (#720)
11 +** After five times, the runtime will remain in the stopped state.
19 19  
20 20  ====Bug fixes====
14 +* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717)
15 +* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
16 +* Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly. With this fix we ensured the widget will always load correctly. (#362)
17 +* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
18 +* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
19 +* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture.
21 21  
22 -* 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)
23 -* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
24 -
25 -
26 -
27 -=====Infra and image changes=====
28 -
29 -* 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.
21 +====Remarks====
22 +* Mendix Runtime has been upgraded to Mendix 9.19.0.