Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 1.1
edited by eMagiz
on 2022/10/14 13:36
Change comment: There is no comment for this version
To version 256.1
edited by Carlijn Kokkeler
on 2024/06/03 15:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - Get Ready
1 +222 - Flee Frustration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,18 +1,10 @@
1 -Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
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.184 - New Beginnings.WebHome||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 -* Create - new flow designer has been introduced for all users in the Create phase
7 - ** Right hand panel that displays alerts, properties, support objects and resources
8 - ** Objects can now be put on the canvas without a full configuration
9 - ** Alerts are generated to display incorrect or incomplete configuration
10 - ** Flow versions can be pushed to Deploy only when there are no remaining alerts
5 +====New features====
11 11  
12 12  
13 -=====Minor changes=====
14 -* Deploy - Copy property page changed to have a orientation on the runtime. Includes update to that popup for the field runtime
15 15  
16 -
17 17  ====Bug fixes====
18 -* Feedback widget - introduced new version and fixed the interaction
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.