Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
Change comment: There is no comment for this version
To version 574.12
edited by dfirdausy
on 2024/07/01 14:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +224 - Summer Sonata
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -1,86 +1,61 @@
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!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
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 -== **3rd generation runtime bolstering** ==
8 +== **Feedback Items** ==
9 +//__Integration requirements: retention duration and bytes__//
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 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
12 +//__Integration requirements: help text__//
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 +//__Debugger duration__//
16 +Wiretaps and debugging sessions will now collect messages for ten minutes, this used to be five. Note that the JMS server needs to be updated in order to also store the messages for ten minutes instead of five. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
10 10  
11 -//__Migration of JMS backup configuration improved__//
18 +== **Bug Fixes** ==
19 +//__SFTP sessions__//
20 +Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
12 12  
13 -//__Prechecks on Upgrade option made available for 3rd generation runtime__//
22 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
14 14  
15 -//__Autogenerated exits can be deployed at once__//
16 16  
17 -//__Code mapping functionality available on 3rd generation runtime__//
25 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
18 18  
19 -//__Improved the performance of deploying or activating a release__//
27 +//__SMB outbound gateway__//
28 +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.
20 20  
21 -//__Failing runtimes won't be restarted indefinetly anymore__//
30 +//__TaskScheduler__//
31 +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.
22 22  
23 -== **Exportable Release Audit** ~* ==
33 +//__View XSLT__//
34 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
24 24  
25 -On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
36 +//__Multipart/form-data HTTP request__//
37 +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.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
28 -
29 -{{warning}}Note that the following restrictions apply when exporting an audit document:
30 - * Changes made on definition and transformation level are **not** restored
31 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
32 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
33 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
34 -
35 -== **Feedback items ** ==
36 -
37 -We have also solved other feedback items besides the flow designer's critical updates.
38 -
39 -//__Data Sink Refactor__//
40 -We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
41 -
42 -//__Improved naming convention on Store related pages__//
43 -We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
44 -
45 -//__Press "Enter" to search on multiple pages__//
46 -In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
47 -
48 -* Deploy → Deployment Plan
49 -* Deploy → Properties → History
50 -* Deploy → User Management → Roles
51 -* Manage → Error Messages → Error Messages
52 -* Manage → Error Messages → Flows with Error Messages
53 -* Manage → Error Messages → Exceptions of Error Messages
54 -* Manage → Log Entries
55 -* Manage → Alerts
56 -* Manage → Triggers
57 -* Manage → Tags – Cant find (only Gen2)
58 -* Manage → Notifications
59 -* Manage → Notification Settings
60 -* Manage → Data Usage → History
61 -* Manage → Code mappings → All tabs
62 -
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  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:
66 66  
67 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
68 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
69 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
70 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
43 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
44 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
45 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
46 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
71 71  
72 -== **Key takeaways** ==
48 +== **Key Takeaways** ==
73 73  
74 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
50 +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:
75 75  
76 76  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  * If you have feedback or ideas for us, talk to the Platypus
78 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
54 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79 79  * Clear your browser cache (Ctrl + Shift + Del)
80 -* Check out the release notes [here]
56 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
81 81  * Start thinking about how the license tracker can aid your development
82 82  * Start thinking about major, minor, and patch
83 -* Upgrade to the latest build number
84 84  * Keep making great integrations
85 85  
86 86  Let's stay in touch and till next time!
... ... @@ -88,6 +88,11 @@
88 88  {{info}}
89 89  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
90 90  
91 -~*~* Indicates a GEN3-only feature.
92 -{{/info}})))((({{toc/}}))){{/container}}
66 +{{/info}}
67 +)))
68 +
69 +(((
70 +{{toc/}}
71 +)))
93 93  {{/container}}
73 +{{/container}}