Changes for page 243 - Migration Magic
Last modified by Erik Bakker on 2025/06/02 09:33
From version 240.1
edited by Erik Bakker
on 2025/04/07 10:06
on 2025/04/07 10:06
Change comment:
There is no comment for this version
To version 140.1
edited by Carlijn Kokkeler
on 2023/10/23 16:48
on 2023/10/23 16:48
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 42-StabilityScore1 +207 - Aligned State - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,18 +1,23 @@ 1 -In the last sprint, we releasedseveraltems to improvethe platform'sstability across thevarious ILM phases. Our biggest changeisaew[[cloud template>>doc:Main.ReleaseInformation.Cloud Templates.WebHome||target="blank"]]thatallowsmodelsrunning on our current-generationarchitecture tobetter utilizetheirCPU within thecloudmodels.Inaddition,wehaveeleasedvarious improvementstotheplatformregardingclarityandstability.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. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 42-StabilityScore.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 -==== NewFeatures====5 +=====Minor changes===== 6 6 7 -* Cloud - Templates: We have implemented a feature for Cloud models to consume an unlimited amount of CPU burst on their production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]. 7 +* 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. 8 +* Design - Message Mapping: The button 'Import from Store' will directly open the store. 9 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. 10 +* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards. 11 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched. 8 8 9 -====Minor Changes==== 10 10 11 -* 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) 12 -* eMagiz Connector - Softcrow: Softcrow restoration has been added to the eMagiz Connector. 13 13 14 14 ====Bug fixes==== 15 15 16 -* 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) 17 -* 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. 17 +* 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. 18 18 19 + 20 + 21 +=====Infra and image changes===== 22 + 23 +* 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.