Changes for page 217 - Template Tango

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+217 - Template Tango

Content

...	...	@@ -1,79 +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 done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
	6	+**Hi there, eMagiz developers!**
6	6
7		-== **Deployment Plan** ==
	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.
8	8
9		-//__Improved deployment plan to make the process better and more predictable__//
10		-The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
	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.
11	11
12		-//__Editing release properties__//
13		-With this release, it will be possible to change the description of a property by editing the property.
14		-
15		-//__JMS memory setting check__//
16		-A change in memory settings triggers redeployment of the container now.
17		-
18		-//__Properties tab__//
19		-We have removed the deprecated tab Properties in the Deploy phase.
20		-
21		-//__Cleanup old images__//
22		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
23		-
24		-//__Performance improvements for loading releases__//
25		-Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
26		-
27		-== **Store Improvements** ==
28		-
29		-//__Message definition elements order__//
30		-We fixed an issue that the orders of message definition’s elements were changed after they were imported.
31		-
32		-//__Message definition elements order__//
33		-We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
34		-
35	35	== **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.
36	36
37		-//__Alerting manual pause__//
38		-A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
	18	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
39	39
40		-//__Ordering of graphs in Manage__//
41		-The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
	20	+//__Copy to clipboard buttons__//
	21	+Copy to clipboard buttons have been added to various pages:
42	42
43		-//__UTC times in Grafana panels__//
44		-All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
	23	+ * Deploy agent pop-up
	24	+ * Create - Flow designer: Properties
	25	+ * Deploy - Property releases: Property details
45	45
46		-//__Update flow designer version__//
47		-The framework used in the flow designer has been updated to the latest version.
	27	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
48	48
49		-//__Carwash track TLS versions in logging__//
50		-A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
	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:
51	51
52		-//__Moving channels in the flow designer__//
53		-Moving already attached channels in the flow designer has been made sligthly easier.
	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.
54	54
55		-//__Topic sizes description change__//
56		-In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
	36	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
57	57
58		-//__Password change notification__//
59		-When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
60		-
61		-//__Password comparison__//
62		-When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
63		-
64		-
65	65	== **Bug Fixes** ==
	39	+//__Runtime overview improvements__//
	40	+The runtime overview has been improved regarding checks on the runtime version.
66	66
67		-//__Flow designer styling__//
68		-The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
69		-
70	70	== **Fancy Forum Answers** ==
71	71
72	72	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:
73	73
74		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	46	+* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
	47	+* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
	48	+* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
	49	+* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
	50	+* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
75	75
76		-== **Key takeaways** ==
	52	+== **Key Takeaways** ==
77	77
78	78	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:
79	79
...	...	@@ -84,7 +84,6 @@
84	84	* Check out the release notes [here]
85	85	* Start thinking about how the license tracker can aid your development
86	86	* Start thinking about major, minor, and patch
87		-* Upgrade to the latest build number
88	88	* Keep making great integrations
89	89
90	90	Let's stay in touch and till next time!
...	...	@@ -92,6 +92,11 @@
92	92	{{info}}
93	93	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
94	94
95		-~*~* Indicates a next-generation-architecture only feature.
96		-{{/info}})))((({{toc/}}))){{/container}}
	70	+{{/info}}
	71	+)))
	72	+
	73	+(((
	74	+{{toc/}}
	75	+)))
97	97	{{/container}}
	77	+{{/container}}