Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 261.1
edited by Carlijn Kokkeler
on 2024/06/18 12:21
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 -223 - Idyllic Image
1 +212 - Failover Fiesta
Content
... ... @@ -1,17 +1,16 @@
1 -In the last sprint cycle, we have worked on releasing a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]], which contains several bug fixes, and increases the debugger duration. Moreover, we have worked on our SwaggerUI settings, filtering, and SpEL Expressions. Find out all features and fixes below.
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.223 - Idyllic Image||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 - API management: Model contacts are now able to select a default SwaggerUI environment from the API management settings in Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown. (#438)
7 -* Capture - Settings: It is now possible to filter the message types in Capture on whether they are used. (#1281)
8 -* Manage - Monitoring: Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be reset (or updated) in order to also store the messages for 10 minutes instead of 5.
5 +=====New features=====
9 9  
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 +
10 10  ====Bug fixes====
11 -* Create - Flow Designer: The SMB outbound gateway with the GET command did not work, this has been resolved.
12 -* Create - Flow designer: We fixed a transformation tooling issue where it was not possible to view an XSLT in certain cases.
13 -* Create - Flow Designer: In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue
14 -* Create - Flow Designer: The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. (#1215)
15 -* Create - Properties: Support has been added to provide the SFTP session factories with a known_hosts in string format rather than file format, so it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
16 16  
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.
17 17  
16 +