Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 252.1
edited by Carlijn Kokkeler
on 2024/05/21 12:55
Change comment: There is no comment for this version
To version 188.1
edited by Carlijn Kokkeler
on 2024/01/15 14:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +212 - Failover Fiesta
Content
... ... @@ -1,17 +1,19 @@
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.
1 +In the last sprint cycle, we focused on ....
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.221 - Swift Shift||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
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.
5 +=====New features=====
13 13  
7 +* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
8 +* Create - Flow Designer: New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
9 +* Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
10 +
11 +=====Minor changes=====
12 +
13 +
14 14  ====Bug fixes====
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.
15 +
16 +* Design - Message Mapping: The message merging tool has been fixed to allow merging a store item message model into your own message models.
17 +* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements.
18 +
19 +