Changes for page 232 - Bug Busters
Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 327.1
edited by Carlijn Kokkeler
on 2024/10/07 12:01
on 2024/10/07 12:01
Change comment:
There is no comment for this version
To version 255.1
edited by Carlijn Kokkeler
on 2024/06/03 13:33
on 2024/06/03 13:33
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 31-Microscopic Madness1 +222 - Flee Frustration - Content
-
... ... @@ -1,12 +1,10 @@ 1 - Duringour recent sprint cycle, wehave improved thesearch options forflowtestinglogsandmonitoringlogs.Next tothis, wefixed theunusedpropertiesoverview andimproved the deletionfunctionalityofroutercontainers.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 31-Microscopic Madness||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==== 5 5 6 -====Minor changes==== 7 -* Create - Flow Testing: Search options for flow testing logs have been improved. 8 -* Manage - Monitoring: Search options for monitoring logs have been improved. 9 9 8 + 10 10 ====Bug fixes==== 11 -* Deploy - Architecture: Router containers that were deleted from the Deploy Architecture, are now cleaned up completely from the environment. 12 -* Deploy - Releases: We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. (#1442) 10 +* 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.