Changes for page 234 - Alert Adventures
Last modified by Carlijn Kokkeler on 2024/11/18 15:29
From version 238.1
edited by Carlijn Kokkeler
on 2024/04/25 15:58
on 2024/04/25 15:58
Change comment:
There is no comment for this version
To version 257.1
edited by Carlijn Kokkeler
on 2024/06/03 16:06
on 2024/06/03 16:06
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 19-CreationCarousel1 +222 - Flee Frustration - Content
-
... ... @@ -1,18 +1,17 @@ 1 -In the last sprint cycle, we have workeda new[[runtime image>>doc:Main.ReleaseInformation.RuntimeImages.V304.WebHome||target="blank"]]thatcontainsafixfor anissue regardingSFTP sessions. Furthermore,we developed a new versionof oureMagiz Mendix connectortosupport Mendix version10and higher. Lastly, we didseveral bug fixes.1 +In the last sprint cycle, we done several improvements for the Design and Deploy phases. Moreover, we have improved the Event Catalog overview for Catalog users. Our bug fixes concern the import of xsds, the deletion behaviour of containerse, and the generation of scope properties. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 19-CreationCarousel||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.222 - Flee Frustration||target="blank"]]. 4 4 5 -=====New features===== 6 -* Design - API Gateway: The path length in OpenAPI specification that can be imported is now increased to a maximum of 300 characters. 7 -* eMagiz Mendix Connector: We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 8 -* Deploy - Architecture: We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents on the current generation architecture from the portal. With future releases of environment templates, your on-premise agents may also be updated. 5 +====New features==== 6 +* Design - Architecture: If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture. 7 +* Create - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05. 9 9 10 -==== =Bug fixes=====11 -* Create- Addintegrations:WhenremovinganintegrationfromCreate,theCreate phase isnowcorrectly updated. (#1053)12 -* Create - Flow Designer: Enumerationvaluesforeventprocessorscannowbe editedin Create.13 -* Create-FlowDesigner:Defaulterrorhandling isnowmigrated correctlywhenmovingtothecurrentruntimearchitecture. (#1266)14 -* Create-Flow Designer:Ifaflow testcreatesaloglinewithlevel ‘Warning’or ‘Error’ andtheresastacktracecreated,thenwe showthestack trace insidethelogmessage on a separate tab.15 -* Deploy - Architecture:SFTPsessionfactoriesdid not close theirconnectionafterit was complete.This couldcauseconnectionstarvationontheSFTPserver,and wasespeciallynoticablewhenusingtheSFTPSessionFactorywithout caching,asthatfactory opens a new connectionforevery call. A new runtimeimage containing a fix is available, please check it out [[here>>doc:Main.ReleaseInformation.RuntimeImages.V304.WebHome||target="blank"]].16 - * Deploy - Architecture: Passwords for network volumes are now hidden on the machine after deployment. (#984)17 - * Deploy - Unused properties: eMagiz properties, which cannot be edited or removed by a user, are not shown in the unused properties overview anymore. (#1267)18 - * All: Legacy pages are now hidden correctly for models running on the current runtime architecture. (#1068)9 +====Bug fixes==== 10 +* Design - Architecture: The number on the JMS container correctly displays the amount of queues present in Design. (#1284) 11 +* Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053) 12 +* Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282) 13 +* Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293) 14 +* Deploy - Releases: Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. (#1293) 15 + 16 + 17 +