Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 201.1
edited by Carlijn Kokkeler
on 2024/02/26 10:47
on 2024/02/26 10:47
Change comment:
There is no comment for this version
To version 259.1
edited by Carlijn Kokkeler
on 2024/06/05 09:30
on 2024/06/05 09:30
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 15-Tiny Tales1 +222 - Flee Frustration - Content
-
... ... @@ -1,15 +1,17 @@ 1 -In the last sprint cycle, we focused onimprovingtheeventstreaminggraph. Moreover,wehavedonesomebug fixes.First ofall,thevalidation forqueue nameswithrespecttospaceshasbeen improved.Moreover,itisnowpossibletoremovean onrampthatwaspreviouslylinkedtoan allentry.Lastly,it isnowpossibleto login toeMagizby pressingenterwhenhavingtheusernamefieldselected.1 +In the last sprint cycle, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Find out about the rest below! 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 15-Tiny Tales||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.222 - Flee Frustration||target="blank"]]. 4 4 5 -=====Minor changes===== 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. 6 6 7 -* Manage - Monitoring: The event streaming graph has been improved to better reflect the state of your topics. (#951) 8 - 9 9 ====Bug fixes==== 9 +* Design - Architecture: The number on the JMS container correctly displays the amount of queues present in Design. (#1284) 10 +* Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053) 11 +* Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282)4 12 +* 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) 13 +* Deploy - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05. 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) 10 10 11 -* Login: In the login screen, users now have the ability to press enter to log in when having the username field selected. 12 -* Create - Flow Designer: The validation regarding undesired spaces for components that use a queue name has been improved. (#1012) 13 -* Create - Flow Designer: An issue has been fixed where it was not possible to remove an onramp that was previously linked to a combined entry. (#1021) 14 14 15 15