Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 469.1
edited by CarlijnKokkeler
on 2024/04/23 11:34
Change comment: There is no comment for this version
To version 195.1
edited by CarlijnKokkeler
on 2023/10/23 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -219 - Creation Carousel
1 +207 - Aligned State
Content
... ... @@ -1,62 +1,70 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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.
7 7  
8 -== **Environment Template R13 Docker - Single Lane** ==
9 -TBD This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R12 Docker - Single Lane.WebHome||target="blank"]].
7 +== **State Generation** ==
10 10  
11 -== **Environment Template R15 Docker - Double Lane** ==
12 -TBD This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R14 Docker - Double Lane.WebHome||target="blank"]].
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.
13 13  
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 14  
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`.
15 15  
16 -== **Feedback Items** ==
17 -//__Machine agents__//
18 -We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more HERE.
25 +Added support for `#JsonPath` usage in SpEL expressions.
19 19  
20 -//__eMagiz Mendix connector__//
21 -We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
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.
22 22  
23 -//__Improved OpenAPI import__//
24 -The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
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.
25 25  
26 -== **Bug Fixes** ==
27 -//__Error handling__//
28 -When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
33 +== **Metrics Storage Duration** ==
34 +Manage - Monitoring: 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.
29 29  
30 -//__Volume mapping passwords__//
31 -Passwords for network volumes are hidden on the machine after deployment.
36 +[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
32 32  
33 -//__Create integration removal__//
34 -When removing an integration from Create, the Create phase is correctly updated as well.
38 +== **Feedback Items** ==
35 35  
36 -//__Legacy statistics__//
37 -Legacy pages are now correctly hidden when running on the current runtime architecture.
40 +//__Import from store__//
41 +Design - Message Mapping: The button 'Import from Store' will directly open the store instead of showing a pop asking whether the store should be opened.
38 38  
39 -//__Unused properties__//
40 -Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
43 +//__Save and cancel buttons__//
44 +The Save and Cancel buttons have been placed slightly further apart from each other to avoid misclicking.
41 41  
42 -//__Enumeration values__//
43 -Enumeration values for event processors can now be edited in Create.
46 +//__User session times__//
47 +Manage - Monitoring: 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.
44 44  
45 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
49 +
46 46  
47 -//__SFTP sessions__//
48 -SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. Please find out more HERE.
51 +== **Bug Fixes** ==
49 49  
53 +
54 +
50 50  == **Fancy Forum Answers** ==
51 51  
52 52  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:
53 53  
54 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
55 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
56 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
59 +* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
60 +* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
61 +* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
62 +* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
63 +* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
57 57  
58 -== **Key Takeaways** ==
59 59  
66 +== **Key takeaways** ==
67 +
60 60  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:
61 61  
62 62  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -63,9 +63,10 @@
63 63  * If you have feedback or ideas for us, talk to the Platypus
64 64  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
65 65  * Clear your browser cache (Ctrl + Shift + Del)
66 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
74 +* Check out the release notes [here]
67 67  * Start thinking about how the license tracker can aid your development
68 68  * Start thinking about major, minor, and patch
77 +* Upgrade to the latest build number
69 69  * Keep making great integrations
70 70  
71 71  Let's stay in touch and till next time!
... ... @@ -73,11 +73,6 @@
73 73  {{info}}
74 74  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75 75  
76 -{{/info}}
77 -)))
78 -
79 -(((
80 -{{toc/}}
81 -)))
85 +~*~* Indicates a next-generation-architecture only feature.
86 +{{/info}})))((({{toc/}}))){{/container}}
82 82  {{/container}}
83 -{{/container}}