Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 196.1
edited by CarlijnKokkeler
on 2023/10/23 15:25
Change comment: There is no comment for this version
To version 574.18
edited by dfirdausy
on 2024/07/01 15:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +224 - Summer Sonata
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.dfirdausy
Content
... ... @@ -1,77 +1,51 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
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.
6 +**Hi there, eMagiz developers!** Over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor.
6 6  
7 -== **State Generation** ==
8 +== **Feedback Items** ==
9 +//__Retention duration and bytes in Capture__//
10 +The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes.
8 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.
12 +//__Help text in Capture__//
13 +Collapsing the help text of this pop-up page by clicking the "?" icon on the top right corner of the pop-up page will now correctly hide the help text pane.
14 +
15 +//__Property value page__//
16 +Pop-up pages with non-editable input fields containing long text are now displaying the entire content without any text being cut off at the edge of the page.
16 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).
18 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
22 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`.
20 +== **Bug Fixes** ==
21 +//__Adding tags in Capture__//
22 +In the Capture phase, clicking to add or remove a tag in the pop-up page for specifying integration requirements no longer displays a 'blocked' icon.
24 24  
25 -Added support for `#JsonPath` usage in SpEL expressions.
24 +[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
26 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.
26 +//__SMB outbound gateway__//
27 +The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
29 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.
29 +//__TaskScheduler__//
30 +In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
32 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.
32 +//__View XSLT__//
33 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
35 35  
36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
35 +//__Multipart/form-data HTTP request__//
36 +The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available.
37 37  
38 -== **Feedback Items** ==
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.
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.
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.
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.
51 -
52 -
53 -== **Bug Fixes** ==
54 -//__Topic and event-processor names__//
55 -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.
56 -
57 -//__System alignment__//
58 -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.
59 -
60 -
61 -
62 62  == **Fancy Forum Answers** ==
63 63  
64 64  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:
65 65  
66 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
67 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
68 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
69 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
70 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
42 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
43 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
44 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
45 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
71 71  
47 +== **Key Takeaways** ==
72 72  
73 -== **Key takeaways** ==
74 -
75 75  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:
76 76  
77 77  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -78,10 +78,9 @@
78 78  * If you have feedback or ideas for us, talk to the Platypus
79 79  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 80  * Clear your browser cache (Ctrl + Shift + Del)
81 -* Check out the release notes [here]
55 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
82 82  * Start thinking about how the license tracker can aid your development
83 83  * Start thinking about major, minor, and patch
84 -* Upgrade to the latest build number
85 85  * Keep making great integrations
86 86  
87 87  Let's stay in touch and till next time!
... ... @@ -89,6 +89,11 @@
89 89  {{info}}
90 90  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91 91  
92 -~*~* Indicates a next-generation-architecture only feature.
93 -{{/info}})))((({{toc/}}))){{/container}}
65 +{{/info}}
66 +)))
67 +
68 +(((
69 +{{toc/}}
70 +)))
94 94  {{/container}}
72 +{{/container}}