Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 26.1
edited by Erik Bakker
on 2022/11/21 13:25
Change comment: There is no comment for this version
To version 242.1
edited by Erik Bakker
on 2025/04/08 16:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +242 - Stability Score
Content
... ... @@ -1,21 +1,20 @@
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.
1 +In the last sprint, we released several items to improve the platform's stability across the various ILM phases. Our biggest change is a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] that allows models running on our current-generation architecture to better utilize their CPU within the cloud models. In addition, we have released various improvements to the platform regarding clarity and stability.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.242 - Stability Score.WebHome||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +====New Features====
6 6  
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.
9 -* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
10 -* Deploy - Deployment plan: 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.
11 -** After five times, the runtime will remain in the stopped state.
12 -* Deploy - Releases: The activate release functionality performance for models that use the 3rd generation runtime is improved.
7 +* Cloud - Templates: We have implemented a feature for Cloud models to improve resource management control within your production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
13 13  
9 +====Minor Changes====
10 +
11 +* Design - Message Definition: When editing a system, CDM, or Gateway message, you can now add and remove attributes to an entity in the message model using an improved version of the ‘Add attribute(s)’ popup in the message designer.
12 +* Store - Overview: The statistics tab in Store item details shows the number of imports and the models where a store item has been imported to, which is only visible to store admins. (#799)
13 +* eMagiz Connector - Softcrow: Softcrow restoration has been added to the eMagiz Connector.
14 +
14 14  ====Bug fixes====
15 -* Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
16 -* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
17 -* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
18 -* 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.
19 19  
20 -====Remarks====
21 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
17 +* Create - Transformation: In the Transformation tab of the Create phase. Newly created attribute operations of type aggregator can freely switch positions with a destination filter using the move left or right buttons. (#1307)
18 +* Create - Flow Designer: Updated help texts and documentation references that pointed to Joda time with the relevant Java DateTimeFormatter options to reflect the current state of libraries supported in the runtime images.
19 +* Manage - Triggers: You can no longer add HTML in the trigger fields for our current generation of alerts. This is to prevent potential malicious code from ending up in emails sent to customers.
20 +