Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/04/22 14:08
From version 218.1
edited by Erik Bakker
on 2025/01/13 09:30
Change comment: There is no comment for this version
To version 244.1
edited by Erik Bakker
on 2025/04/10 08:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -236 - Another Agent
1 +242 - Stability Score
Content
... ... @@ -1,20 +1,20 @@
1 -In the last sprint cycle, we focused on delivering new [[cloud templates>>Main.Release Information.Cloud Templates||target="blank"]] for docker single and docker double lane. Moreover, we have addressed several key feedback points within our platform.
1 +In the last sprint, we released several items to improve the platform's stability across the various ILM phases. Our most significant 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 control their resource management within the cloud models. In addition, we released various improvements in the platform regarding clarity and stability.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.236 - Another Agent||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 -====Major Changes====
5 +====New Features====
6 6  
7 -* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
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"]].
8 8  
9 9  ====Minor Changes====
10 10  
11 -* Create - Flow Designer: Improved help texts for the FTP & SFTP local filter options.
12 -* Deploy - Overview: Spring6 pop-up has been removed.
13 -* Manage - Alerting: The recipients tab for the new Alerting triggers has seen a small update in regards of UX: You will get an explanation when you are trying to enable notifications when no recipients are selected yet.
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. (#1605)
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  
15 15  ====Bug fixes====
16 16  
17 -* Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456)
18 -* Create - Transfer Settings: You can now increase and decrease the number of runtimes for existing Systems. And transfer them from Design Architecture to Deploy Architecture. This can be done in “Create – Settings - Transfer Settings from Design”. (#1543)
19 -* Manage - Alerting: Inactive users in your model are removed from the list of selectable recipients.
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 20