Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33

From version 85.1
edited by Erik Bakker
on 2023/06/05 16:03
Change comment: There is no comment for this version
To version 241.1
edited by Erik Bakker
on 2025/04/07 14:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +242 - Stability Score
Content
... ... @@ -1,20 +1,20 @@
1 -In the last sprint cycle we have focused on improving various aspects of the portal functionality. Among others we focused on the next-generation architecture, the store, security and certificate management.
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.199 - Home Improvements.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 -* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately 3 months before the expiration dates of event streaming users' access certificates.
8 -* Deploy - Release: After successful machine deployments, unused runtime images will be automatically removed. This can be disabled by changing the machine step in your deployment plan.
9 -* Manage - Monitoring: HTTP statistics page now displays all of the resources.
10 -* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it.
11 -* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower.
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"]].
12 12  
13 -====Bug fixes====
9 +====Minor Changes====
14 14  
15 -* Create - Store: Spring Reserved words that contain * are not incorrectly replaced with the prefix of the flow.
16 -* Manage - Monitoring: When an application failed to start, not all log messages were visible in the manage phase.
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.
17 17  
18 -====Remarks====
15 +====Bug fixes====
19 19  
20 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
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’s fields for our current generation of alerts. This is to prevent potential malicious code from ending up in emails sent to customers.
20 +