Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 195.1
edited by Carlijn Kokkeler
on 2024/02/13 10:33
Change comment: There is no comment for this version
To version 252.1
edited by Carlijn Kokkeler
on 2024/05/21 12:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -214 - System Symphony
1 +221 - Swift Shift
Content
... ... @@ -1,21 +1,17 @@
1 -In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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.214 - System Symphony||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.221 - Swift Shift||target="blank"]].
4 4  
5 -=====New features=====
5 +====New features====
6 +* Design - CDM/System message: A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. (#151)
7 +* Design - System message: Moving an attribute in the datamodel is now directly shown in the tree structure as well. (#151)
8 +* Design - CDM/API Data model/ES data model and system message: The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. (#151)
9 +* Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group.
10 +* Deploy - Architecture: When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
11 +* Q & A: Search results are now persisted when pressing the back button after opening a question in the community Q & A. (#1324)
12 +* Catalog: For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
6 6  
7 -* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once.
8 -* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
9 -
10 -=====Minor changes=====
11 -
12 -* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore.
13 -* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days. To utilize this, a new runtime image, [[V.2.1.1>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.1/||target="blank"]], is needed. (1141)
14 -
15 15  ====Bug fixes====
16 -
17 -* Create - Flow Designer: The help text of the Group attribute has been improved.
18 -* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802)
19 -* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen.
20 -
21 -
15 +* Design - System messages: When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. (#140)
16 +* Deploy - Containers: The delete behaviour of containers in the container overview has been improved. (#1053)
17 +* Deploy - API Gateway: We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.