Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 222.1
edited by Carlijn Kokkeler
on 2023/10/24 11:41
Change comment: There is no comment for this version
To version 199.1
edited by Carlijn Kokkeler
on 2023/10/23 16:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,14 +2,10 @@
2 2  {{container layoutStyle="columns"}}(((
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.
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 6  
7 -{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
7 +== **State Generation** ==
8 8  
9 -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.
10 -
11 -== **State Generation~*~*** ==
12 -
13 13  //__New components__//
14 14  The following components have been added:
15 15  * Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
... ... @@ -28,28 +28,27 @@
28 28  
29 29  Added support for `#JsonPath` usage in SpEL expressions.
30 30  
31 -{{info}}The components are all configurable from the Flow Designer in Create and are accompanied by a help text explaining the use cases and the various technical configurations. Note that to make the components work in your model, a new release containing the latest image (2.0.0) needs to be deployed.{{/info}}
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.
32 32  
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.
32 +
33 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 7, 14 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.
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.
35 35  
36 -((((% border="3" cellpadding="10" cellspacing="10" style="width:400px" %)
37 -|=(% style="width: 120px;" %)Future|=(% style="width: 180px;" %)Minute level|=(% style="width: 180px;" %)Hour level
38 -|(% style="width:120px" %) Production|(% style="width:180px" %) 30 days|(% style="width:180px" %) 1 year
39 -|(% style="width:120px" %) Acceptance|(% style="width:180px" %) 14 days|(% style="width:180px" %) 6 months
40 -|(% style="width:120px" %) Test|(% style="width:180px" %) 7 days|(% style="width:180px" %) 3 months
41 -)))
36 +[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
42 42  
43 43  == **Feedback Items** ==
44 44  
45 45  //__Import from store__//
46 -The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
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.
47 47  
48 48  //__Save and cancel buttons placement__//
49 49  The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
50 50  
51 51  //__User session times__//
52 -The user session times for next generation architecture 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.
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.
53 53  
54 54  //__Cancel and next buttons order__//
55 55  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.
... ... @@ -64,7 +64,7 @@
64 64  Performance improvements for the Flow Designer have been implemented.
65 65  
66 66  //__Properties with special characters__//
67 -When a user would migrate to the next generation architecture and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
62 +When a user would migrate to gen3 and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
68 68  
69 69  //__Hidden flow fragements__//
70 70  When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
... ... @@ -73,7 +73,7 @@
73 73  Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components.
74 74  
75 75  //__Error channel for all inbounds__//
76 -If there is no custom error handling, next generation migration would set the error channel to “errorChannel” only for the first inbound in an entry flow.
71 +If there is no custom error handling, Gen3 migration would set the error channel to “errorChannel” only for the first inbound in an entry flow.
77 77  We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
78 78  
79 79  //__Highlighting resources__//
... ... @@ -91,9 +91,9 @@
91 91  Besides checking error header, the error trigger is now configured to check if an error message contains a term.
92 92  
93 93  //__Alerting__//
94 -For the next generation architecture models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
95 -For the next generation architecture models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
96 -The next generation architecture configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
89 +For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
90 +For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
91 +The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
97 97  
98 98  //__Unused containers__//
99 99  Containers are set inactive when they are unused and removed in Design.
... ... @@ -101,6 +101,9 @@
101 101  //__Error popups when promoting a release version__//
102 102  We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
103 103  
99 +//__Memory leak__//
100 +A memory leak when using gen 3 metrics has been fixed.
101 +
104 104  == **Fancy Forum Answers** ==
105 105  
106 106  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:
... ... @@ -108,7 +108,7 @@
108 108  * [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
109 109  * [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
110 110  * [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
111 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
109 +* [[3rd generation runtime with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
112 112  
113 113  
114 114  == **Key takeaways** ==