Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-207 - Aligned State
	1	+217 - Template Tango

Content

...	...	@@ -1,77 +1,53 @@
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!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection. State generation functionality is only accessible for models with an add-on state generation license. Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
	6	+**Hi there, eMagiz developers!** In this release, new cloud templates for docker single and docker double lane are introduced. These templates enable the ability to clean H2 databases from the portal. Next to this, it is now possible to edit the trigger "More than 100 messages on queue over 10 minutes". Moroever, serveral copy to clipboard buttons have been added. Lastly, the runtime overview has been improved with respect to checks on the runtime version.
6	6
7		-== **State Generation** ==
	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>>doc:Main.Release Information.Cloud Templates.R12 Docker - Single Lane.WebHome||target="blank"]].
8	8
9		-//__New components__//
10		-The following components have been added:
11		-* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
12		-* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
13		-* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
14		-* Duplicate detector: support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded.
15		-* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
	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>>doc:Main.Release Information.Cloud Templates.R14 Docker - Double Lane.WebHome||target="blank"]].
16	16
17		-//__SpEL functions & JSON__//
18		-Added SpEL functions for:
19		-* Encoding & decoding Base64, Hex and hmac.
20		-* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
21		-* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
	14	+== **Feedback Items** ==
	15	+//__Dynamic trigger__//
	16	+The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
22	22
23		-Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.
	18	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
24	24
25		-Added support for `#JsonPath` usage in SpEL expressions.
	20	+//__Copy to clipboard buttons__//
	21	+Copy to clipboard buttons have been added to various pages:
26	26
27		-//__New image version 2.0.0__//
28		-The above functionalities are features of the new image version 2.0.0. Important to note is that the library used for Code Mappings has been changed. Changed the library used for Code Mappings. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0.
	23	+ * Deploy agent pop-up
	24	+ * Create - Flow designer: Properties
	25	+ * Deploy - Property releases: Property details
29	29
30		-//__Component pages__//
31		-Pages to add the new components have been created. Forms have been created nicely with proper help texts. The EHCache cache manager has been removed.
	27	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
32	32
33		-== **Metrics Storage Duration** ==
34		-We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively.
	29	+//__Reset H2 database__//
	30	+For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following:
35	35
36		-[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
	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.
37	37
38		-== **Feedback Items** ==
	36	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
39	39
40		-//__Import from store__//
41		-The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened.
42		-
43		-//__Save and cancel buttons placement__//
44		-The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
45		-
46		-//__User session times__//
47		-The user session times for 3rd generation runtime dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour.
48		-
49		-//__Cancel and next buttons order//
50		-The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
51		-
52		-
53	53	== **Bug Fixes** ==
54		-//__Topic and event-processor names__//
55		-The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
	39	+//__Runtime overview improvements__//
	40	+The runtime overview has been improved regarding checks on the runtime version.
56	56
57		-//__System alignment__//
58		-The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases.
59		-
60		-
61		-
62	62	== **Fancy Forum Answers** ==
63	63
64	64	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:
65	65
66		-* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
67		-* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
68		-* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
69		-* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
70		-* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||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"]]
71	71
	49	+== **Key Takeaways** ==
72	72
73		-== **Key takeaways** ==
74		-
75	75	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:
76	76
77	77	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
...	...	@@ -81,7 +81,6 @@
81	81	* Check out the release notes [here]
82	82	* Start thinking about how the license tracker can aid your development
83	83	* Start thinking about major, minor, and patch
84		-* Upgrade to the latest build number
85	85	* Keep making great integrations
86	86
87	87	Let's stay in touch and till next time!
...	...	@@ -89,6 +89,11 @@
89	89	{{info}}
90	90	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91	91
92		-~*~* Indicates a next-generation-architecture only feature.
93		-{{/info}})))((({{toc/}}))){{/container}}
	67	+{{/info}}
	68	+)))
	69	+
	70	+(((
	71	+{{toc/}}
	72	+)))
94	94	{{/container}}
	74	+{{/container}}