Skip to Content

Changes for page 252 - Frostline

Last modified by Erik Bakker on 2025/09/10 21:11
From version 275.3
edited by Maria
on 2025/09/10 15:18
Change comment: There is no comment for this version
To version 164.1
edited by CarlijnKokkeler
on 2023/11/23 08:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -252 - FrostLine
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.maria
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,16 +1,28 @@
1 -This release features numerous updates to our platform, with a user-centric focus. This release, we once again embarked on our traditional Hackathon journey, focused on making the lives of our day-to-day platform users easier.
1 +In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.252 - Frostline 2.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]].
4 4  
5 -==== New features ====
5 +=====New features=====
6 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. *
7 +* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
8 +* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 +* All - The next generation architecture is the default now. New models will use this generation as default.
8 8  
9 -==== Minor changes ====
11 +=====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.
13 +* Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
14 +* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
15 +* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
12 12  
13 -==== Bug fixes ====
17 +====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)
19 +* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
20 +* Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.
21 +* Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
22 +
23 +
24 +
25 +
26 +
27 +
28 +