Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 233.1
edited by Carlijn Kokkeler
on 2024/04/23 13:14
Change comment: There is no comment for this version
To version 210.1
edited by Carlijn Kokkeler
on 2024/03/25 12:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -219 - Creation Carousel
1 +217 - Template Tango
Content
... ... @@ -1,17 +1,17 @@
1 -In the last sprint cycle, we focused on releasing new [[environment templates>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for docker single and double lane. Moreover, we have worked on a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] that contains a fix regarding SFTP sessions. Furthermore, we developed a new version of our eMagiz Mendix connector to support Mendix version 10 and higher. Lastly, we did several bug fixes.
1 +In the last sprint cycle, we focused on improving the event streaming graph. Moreover, we have done some bug fixes. First of all, the validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.219 - Creation Carousel||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.217 - Template Tango||target="blank"]].
4 4  
5 5  =====New features=====
6 -* Design - API Gateway: The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
7 -* Deploy - Architecture: We have released new environment templates, that ensures that on-premise machine agents are updated. Please check out the [[environment template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
8 -* eMagiz Mendix Connector: We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
9 9  
7 +* Create - Flow Designer & Deploy: Copy to clipboard buttons have been added to various pages.
8 +* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce the ability to clean H2 databases from the portal. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 +* Manage - Alerting: The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger.
10 +
10 10  =====Minor changes=====
11 -* Create - Add integrations: When removing an integration from Create, the Create phase is now correctly updated.
12 -* Create - Flow Designer: Enumeration values for event processors can now be edited in Create.
13 -* Create - Flow Designer: Default error handling is now migrated correctly when moving to the current runtime architecture.
14 -* Deploy - Architecture: SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. A new runtime image containing a fix is available, please check it out [[here>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]].
15 -* Deploy - Architecture: Passwords for network volumes are now hidden on the machine after deployment.
16 -* Deploy - Unused properties: eMagiz properties, which cannot be edited or removed by a user, are not shown in the unused properties overview anymore.
17 -* All: Legacy pages are now hidden correctly for models running on the current runtime architecture.
12 +
13 +* Deploy - Architecture: For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note that only H2 databases that are registered under the standard eMagiz data folder will be removed. Moreover, it is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. Lastly, for on-premise runtimes, only a reset of the runtime is needed.
14 +
15 +====Bug fixes====
16 +
17 +* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)