Skip to Content

Changes for page 195 - Easter Party

Last modified by Carlijn Kokkeler on 2024/05/22 13:41
From version 42.1
edited by Erik Bakker
on 2023/01/18 11:32
Change comment: There is no comment for this version
To version 10.1
edited by Erik Bakker
on 2022/10/14 13:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +185 - Get Ready
Content
... ... @@ -1,32 +1,25 @@
1 -The release finishes up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs and some minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
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.190 - Fast Forward.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.185 - Get ready.WebHome||target="blank"]].
4 4  
5 5  =====New features=====
6 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
7 -* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your jms-server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
6 +* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
8 8  
9 -=====Major changes=====
10 -
11 -* Manage - Redelivery: You are able to explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Beside that, you are also able to redeliver the message(s) in this page.
12 -
13 13  =====Minor changes=====
14 14  
15 -* Design - System message: 'Request' and 'Response' entities are generated and set as root entities automatically for new SOAP web service integrations in 3rd generation runtimes.
16 -* Create - Flow designer: sensitive information stored in property values is masked. (#790)
17 -* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so user can use it to compare with the previous versions.
18 -* Create - Flow Designer: when importing store item from another partner, a error popup will be shown instead of default error message.
19 -* Deploy - Releases: The activate release functionality gained a performance improvement for gen 3 models.
20 -* Deploy - Architecture: Before apply to environment, we require a confirmation from you if those are some breaking changes that may cause issues in AWS. (#828)
21 -* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
22 -* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings", where you can enable/disable both HTTP and control bus per runtime.
23 -* Deploy - Releases - When activating a release you will be reminded of empty runtimes. Empty runtimes are runtimes without flows in the release. These runtimes should be removed from your architecture.
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
24 24  
25 25  ====Bug fixes====
26 -* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
27 -* Create - Flow Designer: When copy and paste, support objects such as "property placeholder", "support.bus-connection-caching" and "support.bus-connection-plain" are not duplicated (#793)
28 -* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in setup step.
29 -* Deploy - Containers: We fix an issue that the container overview does not show the entry flows which should run on that container. (#863)
30 -* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
31 -* Deploy - Architecture: The deploy runtimes option is only visible for admin. New menu item "Deploy agent" is added and visible for all users to show the command which can be uses to deploy agent on premises machine.
32 -
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.