Changes for page 243 - Migration Magic

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-242 - Stability Score
	1	+212 - Failover Fiesta

Author

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

Content

...	...	@@ -1,20 +1,16 @@
1		-In the last sprint, we released several items to improve the platform's stability across the various ILM phases. Our biggest change is a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] that allows models running on our current-generation architecture to better utilize their CPU within the cloud models. In addition, we have released various improvements to the platform regarding clarity and stability.
	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.242 - Stability Score.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		-====New Features====
	5	+=====New features=====
6	6
7		-* Cloud - Templates: We have implemented a feature for Cloud models to consume an unlimited amount of CPU burst on their production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
	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====
10		-
11		-* Design - Message Definition: When editing a system, CDM, or Gateway message, you can now add and remove attributes to an entity in the message model using an improved version of the ‘Add attribute(s)’ popup in the message designer.
12		-* Store - Overview: The statistics tab in Store item details shows the number of imports and the models where a store item has been imported to, which is only visible to store admins. (#799)
13		-* eMagiz Connector - Softcrow: Softcrow restoration has been added to the eMagiz Connector.
14		-
15	15	====Bug fixes====
16	16
17		-* Create - Transformation: In the Transformation tab of the Create phase. Newly created attribute operations of type aggregator can freely switch positions with a destination filter using the move left or right buttons. (#1307)
18		-* Create - Flow Designer: Updated help texts and documentation references that pointed to Joda time with the relevant Java DateTimeFormatter options to reflect the current state of libraries supported in the runtime images.
19		-* Manage - Triggers: You can no longer add HTML in the trigger’s fields for our current generation of alerts. This is to prevent potential malicious code from ending up in emails sent to customers.
	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.
20	20
	16	+