Skip to Content
Last modified by Erik Bakker on 2025/02/13 07:36
From version 191.1
edited by Carlijn Kokkeler
on 2024/01/29 15:29
Change comment: There is no comment for this version
To version 190.1
edited by Carlijn Kokkeler
on 2024/01/17 08:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +212 - Failover Fiesta
Content
... ... @@ -1,31 +1,16 @@
1 -In the last sprint cycle, we focused on improving pop-up messages to improve the user experience. Moreover, we did several alignment & formatting improvements. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
1 +In the last sprint cycle, we focused on providing new cloud templates that improve auto-healibng. Moreover, components and deployment steps have been created to support a failover setup. Lastly, bug fixes regarding message mapping and topic data models have been done.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.213 - Joyful Journeys||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
5 5  =====New features=====
6 6  
7 -* Home - Q&A: The option to search by pressing the Enter key has been added.
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"]].
8 8  
9 -=====Minor changes=====
11 +====Bug fixes====
10 10  
11 -* All - Input fields: Multiple input fields have been updated to expand when the amount of characters exceeds the default size. (#822)
12 -* Design - Message: The tooltip for the optional/required toggle has been improved. (#1172)
13 -* Create - Transformation: UI improvements for static input components have been done. (#1172)
14 -* Create - Resources: A button "Update flows" has been added to update versions of all flows in which a resource is used. (#1129)
15 -* Deploy - Releases: When a new property release is created, this property release can now be viewed and deleted. (#1031)
16 -* Deploy - Containers: The error message that is displayed when deleting a runtime is now more descriptive. (#1053)
17 -* Deploy - Runtime overview: Insight into invented and actual deployments has been improved.
18 -* Deploy - Architecture: It is now possible to change the memory settings of a container before pressing "Apply to environment". (#968)
19 -* Deploy - Architecture: Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. (#977)
20 -* Deploy - Architecture: The formatting of action messages regarding changes in retention bytes/hours has been improved.
21 -* Manage - Explore: The error messages that may be displayed when using wiretaps and the debugger have been improved.
13 +* Design - Message Mapping: We have improved our merging functionality within our Store offering to avoid unexpected results after merging.
14 +* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements.
22 22  
23 -====Bug fixes====
24 24  
25 -* Create - Flow Designer: We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). (#1021)
26 -* Create - Flow Designer: A bug has been fixed where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. (#1030)
27 -* Deploy - Architecture: During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
28 -* Manage - Monitoring: The correct number of cache hits and misses are now shown in the state generation statistics. (#1161)
29 -* Manage - Monitoring: We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
30 -* Manage - Explorer: We aligned all timestamp formatting to yyyy-MM-dd HH:mm:ss.SSS.
31 -* Manage - Notification settings: Internal recipients are now added correctly.