Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-207 - Aligned State
	1	+222 - Flee Frustration

Content

...	...	@@ -1,77 +1,50 @@
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!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes!
6	6
7		-== **State Generation** ==
	8	+== **Feedback Items** ==
	9	+//__Cron triggers__//
	10	+Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
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	+[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
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	+//__Design changes__//
	15	+If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
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`.
	17	+[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
24	24
25		-Added support for `#JsonPath` usage in SpEL expressions.
	19	+== **Bug Fixes** ==
	20	+//__Trigger activation__//
	21	+Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
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	+//__Multiple users deploying__//
	24	+Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
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.
	26	+[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.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.
	28	+//__Invalid memory configurations__//
	29	+We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
35	35
36		-[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
	31	+//__Property value synchronization__//
	32	+Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
37	37
38		-== **Feedback Items** ==
	34	+//__JMS number__//
	35	+The number on the JMS container correctly displays the amount of queues present in Design.
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.
	37	+[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
42	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		-== **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.
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"]]
	43	+* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
	44	+* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
71	71
	46	+== **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]]
...	...	@@ -78,10 +78,9 @@
78	78	* If you have feedback or ideas for us, talk to the Platypus
79	79	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80	80	* Clear your browser cache (Ctrl + Shift + Del)
81		-* Check out the release notes [here]
	54	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
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}}
	64	+{{/info}}
	65	+)))
	66	+
	67	+(((
	68	+{{toc/}}
	69	+)))
94	94	{{/container}}
	71	+{{/container}}