Wiki source code of 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}(((
3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
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. 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
7 {{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
8
9 == **State Generation~*~*** ==
10
11 //__New components__//
12 The following components have been added:
13 * Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
14 * Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
15 * Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
16 * 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.
17 * Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
18
19 //__SpEL functions & JSON__//
20 Added SpEL functions for:
21 * Encoding & decoding Base64, Hex and hmac.
22 * Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
23 * Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
24
25 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`.
26
27 Added support for `#JsonPath` usage in SpEL expressions. With this functionality, you can access your JSON payloads in a similar way as you would access XML payloads using [[xPath>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Create your transformations.advanced-create-your-transformations-xpath-advanced||target="blank"]].
28
29 {{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}}
30
31 {{warning}}The library used for Code Mappings has been changed. Any customer with next generation architecture runtimes and code mappings is required to reset their container infra flows prior to deploying on image 2.0.0. This has no consequences on a functional level. {{/warning}}
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 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.
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 )))
42
43 == **Feedback Items** ==
44
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.
47
48 //__Save and cancel buttons placement__//
49 The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
50
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.
53
54 //__Cancel and next buttons order__//
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.
56
57 //__Data sink page__//
58 The data sink page has been moved to the “Explore” tab.
59
60 //__Unused images removal__//
61 When a release is removed, the related unused images in the on-premises machines will be removed as well.
62
63 //__Flow Designer performance__//
64 Performance improvements for the Flow Designer have been implemented.
65
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.
68
69 //__Hidden flow fragements__//
70 When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
71
72 //__Resources disappearances__//
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
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. 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.
77
78 //__Highlighting resources__//
79 The performance of highlighting resources of selected components is improved in Read only mode.
80
81 == **Bug Fixes** ==
82
83 //__Topic and event-processor names__//
84 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.
85
86 //__System alignment__//
87 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. This will be done for existing systems as well.
88
89 //__Error alerting__//
90 The error trigger is now configured to check if an error message contains a certain term, besides checking the error header.
91
92 //__Alerting__//
93 For the next generation architecture models, several adaptations to triggers have been made.
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.
97
98 //__Unused containers__//
99 Containers are set inactive when they are unused and removed in Design.
100
101 //__Error popups when promoting a release version__//
102 We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
103
104 {{warning}}There is a new eMagiz Mendix connector available because a memory leak was found, only affecting Mendix connectors that have been migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture. {{/warning}}
105
106 == **Fancy Forum Answers** ==
107
108 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:
109
110 * [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
111 * [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
112 * [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
113 * [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
114
115
116 == **Key Takeaways** ==
117
118 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:
119
120 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
121 * If you have feedback or ideas for us, talk to the Platypus
122 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
123 * Clear your browser cache (Ctrl + Shift + Del)
124 * Check out the release notes [[here>>doc:Main.Release Information.Portal.207 - Aligned State.WebHome||target="blank"]]
125 * Start thinking about how the license tracker can aid your development
126 * Start thinking about major, minor, and patch
127 * Upgrade to the latest build number
128 * Keep making great integrations
129
130 Let's stay in touch and till next time!
131
132 {{info}}
133 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
134
135 ~*~* Indicates a next-generation-architecture only feature.
136 {{/info}})))((({{toc/}}))){{/container}}
137 {{/container}}