Wiki source code of 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/05/22 13:36
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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 | |||
| 3 | Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]]. | ||
| 4 | |||
| 5 | ====New features==== | ||
| 6 | |||
| 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 | ====Bug fixes==== | ||
| 12 | |||
| 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. |