Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-203 - Fast Paced
	1	+212 - Failover Fiesta

Author

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

Content

...	...	@@ -1,46 +1,55 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** In the last few weeks, we have processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
	6	+**Hi there, eMagiz developers!** This release...
6	6
7		-== **Release Properties - Early Feedback** ==
8		-The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
9		-
10	10	== **Feedback Items** ==
11	11
12		-//__"All entries" are now cleaned up as part of the migration__//
13		-To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
	10	+//__Failover setup__//
	11	+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"]]
14	14
15		-//__Trigger ID added to our alerting on the next-generation architecture__//
16		-We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
17	17
	15	+//__External recipients emailaddress__//
	16	+The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
	17	+
	18	+//__Broker queue metrics dashboards__//
	19	+It is now possible to select the MQTT broker in the queue metrics dashboards.
	20	+
	21	+//__Runtime image version__//
	22	+The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
	23	+
	24	+
18	18	== **Bug Fixes** ==
19	19
20		-//__Ensure no flow can be in a release twice__//
21		-We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
	27	+//__Message throughput__//
	28	+The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
22	22
23		-//__Ensure no flow can be in a release twice__//
24		-We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
	30	+//__Cloud template upgrade incorrect rollback__//
	31	+An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
25	25
	33	+//__Next generation block__//
	34	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
	35	+
26	26	== **Fancy Forum Answers** ==
27	27
28	28	As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
29	29
30		-* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
	40	+* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
31	31
32	32	== **Key takeaways** ==
33	33
34		-Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	44	+Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
35	35
36	36	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
37	37	* If you have feedback or ideas for us, talk to the Platypus
38		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	48	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
39	39	* Clear your browser cache (Ctrl + Shift + Del)
40	40	* Check out the release notes [here]
41	41	* Start thinking about how the license tracker can aid your development
42	42	* Start thinking about major, minor, and patch
43		-* Upgrade to the latest build number
44	44	* Keep making great integrations
45	45
46	46	Let's stay in touch and till next time!
...	...	@@ -48,6 +48,11 @@
48	48	{{info}}
49	49	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
50	50
51		-~*~* Indicates a next-generation-architecture only feature.
52		-{{/info}})))((({{toc/}}))){{/container}}
	60	+{{/info}}
	61	+)))
	62	+
	63	+(((
	64	+{{toc/}}
	65	+)))
53	53	{{/container}}
	67	+{{/container}}