Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-207 - Aligned State
	1	+216 - Hack Heaven

Author

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

Content

...	...	@@ -1,70 +1,90 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
	5	+
	6	+**Hi there, eMagiz developers!** As part of our alignment week we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that we launch new functionality that makes it easier to transform to JSON, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes.
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.
	8	+== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
6	6
7		-== **State Generation** ==
	10	+Placeholder for info from Bas
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.
	12	+{{info}}{{/info}}
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	+== **Announcement - Spring 6** ==
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`.
	16	+Placeholder for info from Jelle
24	24
25		-Added support for `#JsonPath` usage in SpEL expressions.
	18	+{{warning}}{{/warning}}
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.
	20	+== ** Updated release functionality - Infra flow selection** ==
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.
	22	+This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level.
32	32
33		-== **Metrics Storage Duration** ==
34		-Manage - Monitoring: 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.
	24	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
35	35
36		-[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
	26	+When you are in edit mode you can select a new version via the right-click option as you were used to for other flows.
37	37
	28	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
	29	+
	30	+On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release.
	31	+
	32	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
	33	+
	34	+== ** Updated deploy functionality on-premise - Multiple environments selection** ==
	35	+
	36	+{{warning}}The following is only applicable under the following conditions:
	37	+ * Windows 2022 server
	38	+ * Atleast one port opened (as a consequence of a hosted web service){{/warning}}
	39	+
	40	+When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine.
	41	+
	42	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
	43	+
38	38	== **Feedback Items** ==
	45	+//__Easier component selection in flow designer__//
	46	+The area selector through which you can select one or more components has improved to allow for an easier selection of said components when they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier.
39	39
40		-//__Import from store__//
41		-Design - Message Mapping: The button 'Import from Store' will directly open the store instead of showing a pop asking whether the store should be opened.
	48	+//__Improved handling of optionality in JSON on lists__//
	49	+Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired.
42	42
43		-//__Save and cancel buttons__//
44		-The Save and Cancel buttons have been placed slightly further apart from each other to avoid misclicking.
	51	+//__Loading bar when searching for log entries__//
	52	+To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search.
45	45
46		-//__User session times__//
47		-Manage - Monitoring: 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.
	54	+//__Improved feedback when deleting elements from Capture__//
	55	+To better specify to the user which integration or system the user intends to delete we have improved the text in the confirmation pop-up. This way we can provide more information to the user to avoid mistakes.
48	48
49		-
	57	+//__Enhanced filter options in Manage__//
	58	+With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
50	50
	60	+//__Copy property names from Create__//
	61	+This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying.
	62	+
	63	+
51	51	== **Bug Fixes** ==
	65	+//__Queue name validation__//
	66	+The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer.
52	52
	68	+[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
53	53
	70	+//__Removal of onramp__//
	71	+An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
54	54
	73	+//__eMagiz login__//
	74	+In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field.
	75	+
55	55	== **Fancy Forum Answers** ==
56	56
57	57	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:
58	58
59		-* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
60		-* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
61		-* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
62		-* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
63		-* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
	80	+* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
	81	+* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
	82	+* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
	83	+* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
	84	+* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
64	64
	86	+== **Key Takeaways** ==
65	65
66		-== **Key takeaways** ==
67		-
68	68	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:
69	69
70	70	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
...	...	@@ -74,7 +74,6 @@
74	74	* Check out the release notes [here]
75	75	* Start thinking about how the license tracker can aid your development
76	76	* Start thinking about major, minor, and patch
77		-* Upgrade to the latest build number
78	78	* Keep making great integrations
79	79
80	80	Let's stay in touch and till next time!
...	...	@@ -82,6 +82,11 @@
82	82	{{info}}
83	83	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
84	84
85		-~*~* Indicates a next-generation-architecture only feature.
86		-{{/info}})))((({{toc/}}))){{/container}}
	104	+{{/info}}
	105	+)))
	106	+
	107	+(((
	108	+{{toc/}}
	109	+)))
87	87	{{/container}}
	111	+{{/container}}