Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 200.1
edited by Carlijn Kokkeler
on 2023/10/24 09:06
Change comment: There is no comment for this version
To version 149.1
edited by Erik Bakker
on 2023/08/29 10:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +204 - Found It
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,110 +2,36 @@
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. 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.
5 +**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
6 6  
7 -== **State Generation** ==
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.
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).
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`.
24 -
25 -Added support for `#JsonPath` usage in SpEL expressions.
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.
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.
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.
35 -
36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
37 -
38 38  == **Feedback Items** ==
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.
9 +//__Improved check on nested property placeholders__//
10 +To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
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.
12 +//__Removed outdated properties when deploying on the new generation architecture stack__//
13 +We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before connecting to a Kafka cluster but have become obsolete once you migrate.
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.
15 +{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
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.
17 +//__Improved performance Manage Dashboards__//
18 +We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
51 51  
52 -//__Data sink page__//
53 -The data sink page has been moved to the “Explore” tab.
54 -
55 -//__Unused images removal__//
56 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
57 -
58 -//__Flow Designer performance__//
59 -Performance improvements for the Flow Designer have been implemented.
60 -
61 -//__Properties with special characters__//
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.
63 -
64 -//__Hidden flow fragements__//
65 -When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
66 -
67 -//__Resources disappearances__//
68 -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.
69 -
70 -//__Error channel for all inbounds__//
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.
72 -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.
73 -
74 -//__Highlighting resources__//
75 -The performance of highlighting resources of selected components is improved in Read only mode.
76 -
77 77  == **Bug Fixes** ==
78 78  
79 -//__Topic and event-processor names__//
80 -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.
22 +//__Errors with long stack traces or long message histories will now also show in eMagiz__//
23 +We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
81 81  
82 -//__System alignment__//
83 -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.
25 +//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
26 +We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
84 84  
85 -//__Error checking__//
86 -Besides checking error header, the error trigger is now configured to check if an error message contains a term.
87 -
88 -//__Alerting__//
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.
92 -
93 -//__Unused containers__//
94 -Containers are set inactive when they are unused and removed in Design.
95 -
96 -//__Error popups when promoting a release version__//
97 -We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
98 -
99 99  == **Fancy Forum Answers** ==
100 100  
101 101  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:
102 102  
103 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
104 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
105 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
106 -* [[3rd generation runtime with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
32 +* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
33 +* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
107 107  
108 -
109 109  == **Key takeaways** ==
110 110  
111 111  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:
... ... @@ -112,7 +112,7 @@
112 112  
113 113  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
114 114  * If you have feedback or ideas for us, talk to the Platypus
115 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
41 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
116 116  * Clear your browser cache (Ctrl + Shift + Del)
117 117  * Check out the release notes [here]
118 118  * Start thinking about how the license tracker can aid your development