Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-207 - Aligned State
	1	+225 - Pop-up Party

Author

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

Content

...	...	@@ -1,77 +1,87 @@
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, a new runtime image (LINK) will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below!
6	6
7		-== **State Generation** ==
	8	+== **Feedback Items** ==
	9	+//__Alerting notification settings__//
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	+//__Process containers__//
	12	+If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern.
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 settings__//
	15	+When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
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-225-design-settings.png]]
24	24
25		-Added support for `#JsonPath` usage in SpEL expressions.
	19	+//__Untested images__//
	20	+ A warning will be shown when a release is activated on **Production** with a new runtime image version which has not been tested on acceptance before.
	21	+
	22	+[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
	23	+
	24	+{{warn}}
	25	+The following restrictions apply to this functionality:
	26	+
	27	+- The warning is
	28	+{{/warn}}
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.
	30	+//__Infinispan Cache Manager__//
	31	+We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
	32	+
	33	+//__Infinispan Cache Manager error message__//
	34	+We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available.
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.
	36	+//__Flow bump__//
	37	+When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
	38	+
	39	+[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.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.
	41	+//__Unused support objects__//
	42	+Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
35	35
36		-[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
	44	+[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
	45	+
	46	+//__Deleting routes__//
	47	+For clarity purposes, a confirmation pop-up will be shown when deleting routes.
37	37
38		-== **Feedback Items** ==
	49	+[[image:Main.Images.Release Blog.WebHome@release-225-routes.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.
	51	+//__Debug queue__//
	52	+The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
	53	+
	54	+[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
	55	+
	56	+== **Bug Fixes** ==
	57	+//__Internal server error__//
	58	+The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
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.
	60	+//__Namespace update__//
	61	+Editing a namespace used in a message definition automatically updates the message definition & transformations.
45	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.
	63	+//__Error pop-up__//
	64	+We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
48	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		-
	66	+//__SMB inbound channel adapter__//
	67	+The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new runtime image LINK is available.
52	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.
	69	+//__Heap memory__//
	70	+The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available.
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.
	72	+//__Classpath conflicts__//
	73	+We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
59	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"]]
	79	+* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
	80	+* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
	81	+* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
71	71
	83	+== **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]
	91	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.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}}
	101	+{{/info}}
	102	+)))
	103	+
	104	+(((
	105	+{{toc/}}
	106	+)))
94	94	{{/container}}
	108	+{{/container}}