207 - Aligned State

Version 196.1 by Carlijn Kokkeler on 2023/10/23 15:25

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.

State Generation

New components
The following components have been added:

Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
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.
Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.

SpEL functions & JSON
Added SpEL functions for:

Encoding & decoding Base64, Hex and hmac.
Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).

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`.

Added support for `#JsonPath` usage in SpEL expressions.

New image version 2.0.0
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.

Component pages
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.

Metrics Storage Duration

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.

Feedback Items

Import from store
The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened.

Save and cancel buttons placement
The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.

User session times
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.

Cancel and next buttons order
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.

Bug Fixes

Topic and event-processor names
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.

System alignment
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.

Fancy Forum Answers

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:

Key takeaways

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:

If you have questions surrounding our Program Increment Planning, please get in touch with productmanagement@emagiz.com
If you have feedback or ideas for us, talk to the Platypus
Please inform us of new additions to the store (productmanagement@emagiz.com) so we can all benefit from these.
Clear your browser cache (Ctrl + Shift + Del)
Check out the release notes [here]
Start thinking about how the license tracker can aid your development
Start thinking about major, minor, and patch
Upgrade to the latest build number
Keep making great integrations

Let's stay in touch and till next time!

* Indicates a Beta feature. If you would like to get access to this beta feature, please contact productmanagement@emagiz.com

** Indicates a next-generation-architecture only feature.