Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 108.1
edited by Carlijn Kokkeler
on 2023/09/18 13:12
Change comment: There is no comment for this version
To version 43.1
edited by Erik Bakker
on 2023/01/18 11:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -204 - Found It
1 +190 - Fast Forward
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,21 +1,32 @@
1 -In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact.
1 +The release finished many new improvements to our 3rd generation runtime offering and fixed various annoying bugs and minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.204 - Found It.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
4 4  
5 -=====Minor changes=====
6 -* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change and can be multiply selected.
7 -* Deploy-Architecture: The container calculations are improved. For event streaming containers these show the amount of topic proccessers deployed. For gateway containers these represent the amount of operations deployed on a container. For JMS containers these represent the amount of message queues deployed. The other types of containers display the amount of intergrations deployed.
8 -* Create - 3rd Generation runtime migration: Your containers will be validated for 3rd Generation runtimes first before you approve the migration.
9 -* Deploy-Architecture: Users with edit rights in deploy can edit certificates.
10 -* Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
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.
11 11  
12 -====Bug fixes====
9 +=====Major changes=====
13 13  
14 -* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970)
15 -* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
16 -* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release.
17 -* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
11 +* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
18 18  
19 -=====Infra and image changes=====
13 +=====Minor changes=====
20 20  
21 -* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.
15 +* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities 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 the user can use it to compare the previous versions.
18 +* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
19 +* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
20 +* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact 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 - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
24 +
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 copying and pasting, 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 the setup step.
29 +* Deploy - Containers: We fixed 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. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
32 +