Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 258.1
edited by Carlijn Kokkeler
on 2024/06/03 16:07
on 2024/06/03 16:07
Change comment:
There is no comment for this version
To version 207.1
edited by Carlijn Kokkeler
on 2024/03/25 12:15
on 2024/03/25 12:15
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 22-FleeFrustration1 +217 - Template Tango - Content
-
... ... @@ -1,17 +1,14 @@ 1 -In the last sprint cycle, we have workedtoallow crontrigggers for hours, days andmonthsprependedbya0. Moreover,changesin Design that will createordeleteruntimes,orimpactyourmodelarchitecture, will triggerawarningbeforebeing put intoeffectinDesignArchitecture.Wehave alsodoneseveralbug fixes, for example,users are notloggedoutfromtheportalanymorewhiledeploying.Furthermore,usersarenow blockedfromdeployingatthesame timeon the sameenvironment.Findoutabout therestbelow!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.2 22-FleeFrustration||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.217 - Template Tango||target="blank"]]. 4 4 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. 5 +=====Minor changes===== 8 8 7 +* Manage - Monitoring: The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic. (#951) 8 +* Deploy - Releases: Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available. (#1137) 9 + 9 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 15 16 - 17 - 12 +* Generic - Login: In the login screen, users can now press "enter" to log in when the username field is selected. 13 +* Create - Flow Designer: The validation regarding undesired spaces for components that use a queue name has been improved. (#1012) 14 +* Create - Flow Designer: An issue has been fixed where removing an onramp linked to a combined entry was impossible. (#1021)