Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 211.1
edited by Carlijn Kokkeler
on 2024/05/22 13:35
Change comment: There is no comment for this version
To version 209.1
edited by Erik Bakker
on 2024/03/12 14:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,11 +2,10 @@
2 2  
3 3  Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]].
4 4  
5 -====New features====
5 +=====New features=====
6 6  * When deploying the on-premise agent for an on-premise machine, users now have the option to select "Multiple environments" when the selected OS type is Windows. This will solve an issue where deploying multiple machines from different environments (machines from Deploy architecture) to the same on-premise machine (the 'physical' machine) running Windows Server 2022 as an operating system was impossible. We have now implemented a fix allowing users to run these multi-environment setups on their Windows Server 2022 machines.
7 -* Deploy - Architecture: Changing the memory of a runtime should now be done via the machine "details" screen. On top of this logic is added to check the overall health of the machine. This check is reevaluated on every change made on runtime level related to memory.
8 8  
9 -====Minor changes====
8 +=====Minor changes=====
10 10  
11 11  * Capture - Generic: When deleting a system, tenant, or integration, more information is provided on what you are deleting (#1174)
12 12  * Create - Transformation: An optional list in JSON will only create a list if there are items for that list. Otherwise, no list will be made by default. (#941)
... ... @@ -16,8 +16,6 @@
16 16  * Deploy - Releases: Some usability improvements were implemented in Deploy > Releases. Users can now select the flow version of the infra flows (for each pattern respectively) by right-clicking the light-green eMagiz platform component (much like in Create). When the infra flow version has been edited in a release, the platform will color light blue to signify this change in the infra version. The context menu containing the versions also shows a caption to show what exact component has been right-clicked and whose flow versions are showing (i.e., entry, exit, onramp, offramp)
17 17  * Deploy - Architecture: When architectural changes are pending in Deploy → Architecture, the screen will not allow edits and show a message that changes are pending. (#1079)
18 18  * Deploy - Architecture: Pending changes will now block continuing after pressing "Apply to environment" instead of when pressing "Apply Changes" in the next screen. (#606)
19 -* Deploy - Architecture: Applying to environment or saving your machine is not possible If there is more memory configured than available. (#1144)
20 -* Deploy - Architecture: Changing the memory of a runtime should now be done via the machine "details" screen. On top of this logic is added to check the overall health of the machine. This check is reevaluated on every change made on runtime level related to memory. (#545)
21 21  * Manage - Monitoring: A progress bar is added when users have long searches on "Log entries". (#1133)
22 22  * Manage - Alerting - Triggers - New: It can now filter across Queues, Topics, Recipients, and Runtimes when adding a new trigger. (#1089)
23 23  * Manage - Alerting - Alerts: It is now possible to filter the alerts based on the status. (#1176)