Changes for page 243 - Migration Magic

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

From version 241.1
edited by Erik Bakker
on 2025/04/07 14:39
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2022/10/24 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -242 - Stability Score
1 +186 - Daemon Switch
Content
... ... @@ -1,20 +1,25 @@
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.
1 +Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.242 - Stability Score.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.186 - Daemon Switch.WebHome||target="blank"]].
4 4  
5 -====New Features====
5 +=====New features=====
6 +* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
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"]].
8 +=====Minor changes=====
8 8  
9 -====Minor Changes====
10 +* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
11 + ** Datagids, where there is now on hover action for example.
12 + ** Pop ups
13 + ** Context menus, also have on hover action
14 + ** Styling of scrollbars
15 + ** Warning, info and error context labels.
16 +* Message Redelivery - admin logs improved to better analyze issues when they occur
17 +* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
18 +* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
10 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 -
15 15  ====Bug fixes====
16 -
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 -
21 +* Deploy - Deployment plan. Performance of page to deploy a release increased significantly
22 +* Store - Import resources was incorrectly done in specific cases, which is now fixed
23 +* Store - Target namespace will be imported when importing an XML Message Definition
24 +* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.
25 +* Store - Importing items from the store sometimes resulted in invalid JMS connection factories.