Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-213 - Joyful Journeys
	1	+207 - Aligned State

Content

...	...	@@ -1,85 +1,77 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** This release ....
	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.
7	7
8		-== **Pop-up Improvements** ==
9		-//__Property releases__//
10		-When a new property release is created, this property release can now be viewed and deleted.
	7	+== **State Generation** ==
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
	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.
13	13
14		-//__Runtime deletion__//
15		-When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
	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).
16	16
17		-//__Wiretap & debug error messages__//
18		-The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
	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`.
19	19
20		-//__Action messages__//
21		-The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
	25	+Added support for `#JsonPath` usage in SpEL expressions.
22	22
23		-== **Formatting & Alignments** ==
	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.
24	24
25		-//__Input fields__//
26		-Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
	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	27
28		-//__UI improvements__//
29		-UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
	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.
30	30
31		-//__Runtime overview image versions__//
32		-Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
	36	+[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
33	33
34		-//__Component changes reversion__//
35		-In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
36		-
37		-//__State generation statistics__//
38		-The state generation graphs will now show the correct number of cache hits and misses.
39		-
40		-//__Queue browser timestamps__//
41		-All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
42		-
43		-//__Addition and deletion of internal recipients__//
44		-Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
45		-
46	46	== **Feedback Items** ==
47	47
48		-//__Update flows__//
49		-In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
	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.
50	50
51		-//__Q&A forum search__//
52		-The option to search by pressing the Enter key has been added to the Q&A forum.
	43	+//__Save and cancel buttons placement__//
	44	+The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
53	53
54		-//__Memory settings__//
55		-It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
	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.
56	56
57		-//__Runtime validation__//
58		-Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
	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	+
59	59
60		-
61	61	== **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.
62	62
63		-//__Removal of onramp__//
64		-We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
	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.
65	65
66		-//__Runtime statistics details__//
67		-We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
68		-
69		-//__Deployment prechecks__//
70		-During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
71		-
72		-
	60	+
	61	+
73	73	== **Fancy Forum Answers** ==
74	74
75	75	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:
76	76
77		-* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
78		-* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
79		-* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
	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"]]
80	80
81		-== **Key Takeaways** ==
82	82
	73	+== **Key takeaways** ==
	74	+
83	83	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:
84	84
85	85	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
...	...	@@ -89,6 +89,7 @@
89	89	* Check out the release notes [here]
90	90	* Start thinking about how the license tracker can aid your development
91	91	* Start thinking about major, minor, and patch
	84	+* Upgrade to the latest build number
92	92	* Keep making great integrations
93	93
94	94	Let's stay in touch and till next time!
...	...	@@ -96,11 +96,6 @@
96	96	{{info}}
97	97	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
98	98
99		-{{/info}}
100		-)))
101		-
102		-(((
103		-{{toc/}}
104		-)))
	92	+~*~* Indicates a next-generation-architecture only feature.
	93	+{{/info}})))((({{toc/}}))){{/container}}
105	105	{{/container}}
106		-{{/container}}