Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Deployment Delights
	1	+217 - Template Tango

Content

...	...	@@ -3,58 +3,50 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** We have...
	6	+**Hi there, eMagiz developers!**
7	7
8		-== **Alerts** ==
	8	+== **Cloud Template R12 Docker - Single Lane** ==
	9	+This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here.
9	9
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.
	11	+== **Cloud Template R14 Docker - Double Lane** ==
	12	+This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here.
12	12
13		-//__Missing metrics alert__//
14		-We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
15		-
16	16	== **Feedback Items** ==
	15	+//__Custom trigger__//
	16	+The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger.
17	17
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.
	18	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
20	20
21		-[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
	20	+//__Copy to clipboard buttons__//
	21	+Copy to clipboard buttons have been added to various pages:
22	22
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.
	23	+ * Deploy agent pop-up
	24	+ * Create - Flow designer: Properties
	25	+ * Deploy - Property releases: Property details
25	25
26		-//__Rebuilding of images__//
27		-Changing the list of flows that should run on a container will now trigger the rebuilding of images.
	27	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
28	28
	29	+//__Reset H2 database__//
	30	+For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following:
29	29
30		-== **Bug Fixes** ==
	32	+* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
	33	+* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
	34	+* For on-premise runtimes, only a reset of the runtime is needed.
31	31
32		-//__Runtime metrics processing__//
33		-The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
	36	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
34	34
35		-//__Deployment plan__//
36		-We solved a bug where a deployment step in the deployment plan could randomly get stuck.
	38	+== **Bug Fixes** ==
	39	+//__Runtime overview improvements__//
	40	+The runtime overview has been improved regarding checks on the runtime version.
37	37
38		-//__Store message merging__//
39		-The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
40		-
41		-//__View all store items__//
42		-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.
43		-
44		-//__Out of memory behavior__//
45		-We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
46		-
47		-//__Max fetch size__//
48		-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.
49		-
50		-
51	51	== **Fancy Forum Answers** ==
52	52
53	53	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:
54	54
55		-* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	46	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
	47	+* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
56	56
57		-== **Key takeaways** ==
	49	+== **Key Takeaways** ==
58	58
59	59	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:
60	60
...	...	@@ -65,7 +65,6 @@
65	65	* Check out the release notes [here]
66	66	* Start thinking about how the license tracker can aid your development
67	67	* Start thinking about major, minor, and patch
68		-* Upgrade to the latest build number
69	69	* Keep making great integrations
70	70
71	71	Let's stay in touch and till next time!
...	...	@@ -73,7 +73,6 @@
73	73	{{info}}
74	74	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75	75
76		-~*~* Indicates a next-generation-architecture only feature.
77	77	{{/info}}
78	78	)))
79	79