Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-196 - The Last Post
	1	+210 - Deployment Delights

Author

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

Content

...	...	@@ -1,76 +1,64 @@
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 work hard on improving our next generation architecture and introduced the "live" mode within our flow testing functionality. Furthermore there are loads of smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
	6	+**Hi there, eMagiz developers!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several for the Store. Lastly, we made some changes to the alerts that you may be receiving.
6	6
7		-== **"Live" mode on flow testing** ==
	8	+== **Alerts** ==
8	8
9		-With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch between "live" and "mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all external communication is mocked by the system and only the functional process can be tested.
	10	+//__Topic approaching max size alert__//
	11	+The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
10	10
11		-By switching to "live" mode you can not only test the functional process but also the communication to the external system. You can do so by entering the "edit" mode of the flow test and toggle between "mock" and "live" mode. When doing so eMagiz will show you the following pop-up stressing the consequences of your actions.
	13	+//__Missing metrics alert__//
	14	+We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
	16	+== **Feedback Items** ==
14	14
15		-Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
	18	+//__Container version overview__//
	19	+In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]]
	21	+[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
18	18
19		-{{info}}* The following restrictions apply for this functionality
20		- ** "Live" mode can only be activated on HTTP outbound gateway components
21		- ** "Live" mode can **not** be active when you want to use the flow test as an "automated" test{{/info}}
	23	+//__Unchanged containers__//
	24	+When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
22	22
23		-== **3rd generation improvements** ==
	26	+//__Rebuilding of images__//
	27	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
24	24
25		-//__Event Streaming statistics completion__//
26		-In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
	29	+== **Bug Fixes** ==
27	27
28		-//__Deployments on next generation architecture__//
29		-This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
	31	+//__Runtime metrics processing__//
	32	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
30	30
31		-//__Clean queues option__//
32		-This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
	34	+//__Deployment plan__//
	35	+We solved a bug where a deployment step in the deployment plan could randomly get stuck.
33	33
34		-== **Feedback items ** ==
	37	+//__Store message merging__//
	38	+The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
35	35
36		-//__On-premise containers are started upon slot wakeup__//
37		-With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
	40	+//__View all store items__//
	41	+An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
38	38
39		-//__Resource path is shown to the user__//
40		-You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
	43	+//__Out of memory behavior__//
	44	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
41	41
42		-//__Flow designer improvements__//
43		-With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
	46	+//__Max fetch size__//
	47	+We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
44	44
45		-//__Improved capabilities of a company contact__//
46		-With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
47		-
48		-== **Bug fixes ** ==
49		-
50		-//__Optional API parameters are handled correctly__//
51		-Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
52		-
53		-//__Without CDM rights nothing related to any data model can be edited anymore__//
54		-With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
55		-
56		-//__Improved sorting of Design and Deploy archticture__//
57		-With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
58		-
59	59	== **Fancy Forum Answers** ==
60	60
61	61	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:
62	62
63		-* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
64		-* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
65		-* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
	53	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
66	66
67	67	== **Key takeaways** ==
68	68
69		-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:
	57	+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:
70	70
71	71	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
72	72	* If you have feedback or ideas for us, talk to the Platypus
73		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	61	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
74	74	* Clear your browser cache (Ctrl + Shift + Del)
75	75	* Check out the release notes [here]
76	76	* Start thinking about how the license tracker can aid your development
...	...	@@ -83,6 +83,12 @@
83	83	{{info}}
84	84	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
85	85
86		-~*~* Indicates a GEN3-only feature.
87		-{{/info}})))((({{toc/}}))){{/container}}
	74	+~*~* Indicates a next-generation-architecture only feature.
	75	+{{/info}}
	76	+)))
	77	+
	78	+(((
	79	+{{toc/}}
	80	+)))
88	88	{{/container}}
	82	+{{/container}}