Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 562.1
edited by CarlijnKokkeler
on 2024/06/18 11:40
Change comment: There is no comment for this version
To version 47.1
edited by Erik Bakker
on 2022/11/21 13:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -223 - TBD
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,68 +1,91 @@
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!**
7 -
8 -== **Feedback Items** ==
9 -//__SwaggerUI default__//
10 -Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown.
5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
7 +== **3rd generation runtime bolstering** ==
13 13  
14 -//__Deprecated warnings__//
15 -We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10.
9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
16 16  
17 -//__Used message types__//
18 -It is now possible to filter the message types in Capture on whether they are used.
11 +//__Migration of JMS backup configuration improved__//
12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
19 19  
20 -[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]]
21 -
22 -//__Debugger duration__//
23 -Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be reset (or updated) in order to also store the messages for 10 minutes instead of 5. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
24 24  
25 -== **Bug Fixes** ==
26 -//__SFTP sessions__//
27 -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.
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
20 +//__Code mapping functionality available on 3rd generation runtime__//
21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
30 30  
23 +//__Improved the performance when activating a release__//
24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
26 +//__Failing runtimes won't be restarted indefinitely anymore__//
27 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
33 33  
34 -//__SFTP sessions__//
35 -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 +== **Exportable Release Audit** ~* ==
36 36  
37 -//__TaskScheduler__//
38 -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.
31 +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.
39 39  
40 -//__View XSLT__//
41 -We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
33 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
42 42  
43 -//__Multipart/form-data HTTP request__//
44 -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.
35 +{{warning}}Note that the following restrictions apply when exporting an audit document:
36 + * Changes made on definition and transformation level are **not** restored
37 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022
38 + * 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
39 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
45 45  
41 +== **Feedback items ** ==
42 +
43 +We have also solved other feedback items besides the flow designer's critical updates.
44 +
45 +//__Data Sink Refactor__//
46 +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 you separately.
47 +
48 +//__Improved naming convention on Store related pages__//
49 +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.
50 +
51 +//__Press "Enter" to search on multiple pages__//
52 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
53 +
54 +* Deploy → Deployment Plan
55 +* Deploy → Properties → History
56 +* Deploy → User Management → Roles
57 +* Manage → Error Messages → Error Messages
58 +* Manage → Error Messages → Flows with Error Messages
59 +* Manage → Error Messages → Exceptions of Error Messages
60 +* Manage → Log Entries
61 +* Manage → Alerts
62 +* Manage → Triggers
63 +* Manage → Tags – Cant find (only Gen2)
64 +* Manage → Notifications
65 +* Manage → Notification Settings
66 +* Manage → Data Usage → History
67 +* Manage → Code mappings → All tabs
68 +
46 46  == **Fancy Forum Answers** ==
47 47  
48 48  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:
49 49  
50 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
51 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
52 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
53 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
73 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
74 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
75 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
54 54  
55 -== **Key Takeaways** ==
77 +== **Key takeaways** ==
56 56  
57 -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:
79 +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:
58 58  
59 59  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
60 60  * If you have feedback or ideas for us, talk to the Platypus
61 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
83 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
62 62  * Clear your browser cache (Ctrl + Shift + Del)
63 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
85 +* Check out the release notes [here]
64 64  * Start thinking about how the license tracker can aid your development
65 65  * Start thinking about major, minor, and patch
88 +* Upgrade to the latest build number
66 66  * Keep making great integrations
67 67  
68 68  Let's stay in touch and till next time!
... ... @@ -70,11 +70,6 @@
70 70  {{info}}
71 71  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
72 72  
73 -{{/info}}
74 -)))
75 -
76 -(((
77 -{{toc/}}
78 -)))
96 +~*~* Indicates a GEN3-only feature.
97 +{{/info}})))((({{toc/}}))){{/container}}
79 79  {{/container}}
80 -{{/container}}