Changes for page 277 - First Farewell

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-277 - First Farewell
	1	+212 - Failover Fiesta

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,26 +1,16 @@
1		-This release includes many smaller improvements across the platform's various phases. It also introduces a **new** runtime image in response to several CVE reports. Furthermore, it marks the **end of support** for our Event Streaming-related alerting for models still running on our old infrastructure (Aiven).
	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>>doc:Main.Release Information.Release Blogs.277 - First Farewell.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4	4
5		-==== Major Changes ====
	5	+=====New features=====
6	6
7		-* General - API MAM Migration: Topic alerting for the legacy Aiven-based Kafka topics has been marked as **End of Support**. This means the functionality will keep running as-is, but we will no longer provide support, bug fixes, or updates for this feature. This only affects customers who have not yet migrated to our new event streaming broker.
	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		-* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V360.WebHome||target="blank"]] for **all** customers is available.
12		-* General - UI/UX: Some UI elements have been replaced with newer versions, which should improve User experience.
13		-* Design - System Message: OpenAPI import functionality from the system message of an API integration is revised and improved. The functionality lets you select the desired path and operation to import from the selected OpenAPI file. Also, it imports both the request and response messages for the selected operation and sets them as root. (#1421)
14		-* Design - CDM: We improved the loading of data model-related information. This improves performance when interacting with larger data models.
	13	+* Design - Message Mapping: The message merging tool has been fixed to allow merging a store item message model into your own message models.
	14	+* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements.
15	15
16		-===== Bug Fixes ====
17	17
18		-* Design - Solution Design: Event Streaming processors with errors in their message mapping are also displayed when the Design phase “Only errors” switch is enabled. (#1422)
19		-* Design - Solution Design: Sorting of the tenants on a multi-tenant system is aligned between Capture and Design. (#1736)
20		-* Design - System message: Fixed two typos found when attempting to delete and edit annotations. (#1813)
21		-* Design - Event Streaming: The prompt for entering edit mode correctly references event streaming when the integration type is event streaming. (#1780)
22		-* Create - Flow designer: We fixed an issue regarding the HTTP security support object that prevented the underlying flow from working even though the security was disabled.
23		-* Create - Properties tab: Improved the logic for property highlighting when selecting a component for properties with similar names. (#1774)
24		-* Deploy - Releases: We fixed a minor typo when a step is determined not to be relevant in the deployment plan. (#1781)
25		-* Deploy - Missing flows for runtimes: The pop-up also includes the display name of the system in Design. (#1812)
26		-* Manage - Flows With Error Messages: Filter option on the "flow with error messages" page to be carried over to the pop-up when opening the overview of a specific flow containing errors (#1766)