Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 783.1
edited by Carlijn Kokkeler
on 2024/11/18 11:12
Change comment: There is no comment for this version
To version 853.1
edited by Erik Bakker
on 2025/02/10 09:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -234 - Alert Adventures
1 +238 - Preparation Paraside
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -3,26 +3,29 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, our new error alerting will be available! Please find out more about it here (LINK). Apart from this, .
6 +**Hi there, eMagiz developers!** In this release, we focused on finishing the first iteration of our new eMagiz Mendix Connector and the first iteration of our new base image. We will first utilize the new eMagiz Mendix Connector to get an even better feeling of its performance, but you will notice a UI change straightaway. Once we have passed that hurdle, we will share more information about it and release it to a broader range of customers. Regarding the base image, we will now introduce this to our flow testing offering to see if anything unexpected happens. This is an additional safety measure we have put in place to reduce the chance of something breaking in your model once the new base image is released. On top of that, we have some minor updates to improve the quality of the platform.
7 7  
8 -== **Feedback Items** ==
9 -//__Error alerting__//
10 -Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, following our queue alerting design that has been [[released>>doc:Main.Release Information.Release Blogs.226 - Alerting Alchemy.WebHome||target="blank"]] a couple of months ago. The new error alerting feature allows you to trigger an alert on all incoming errors, or choose to trigger when specific filters on the error’s headers, message or class have been met. Furthermore, you can select the specific runtime the error originated from as one of the filters as well.
8 +== **Updated Base Image** - Flow Testing Only ==
9 +
10 +With this release we introduce the new [[runtime image>>Main.Release Information.Runtime Images||target="blank"]] to our flow testing functionality. This means that as of that moment your flow tests will run against the latest runtime image. We do this to decrease the likelihood of unexpected things happening on your actual environments once we release the image to the community.
11 11  
12 -{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}
12 +{{info}}
13 +* **Please take into consideration the following**:
14 +* This means that the flow testing results could differ from the results you get once you have deployed your functionality to an environment. If something like that happens please contact us via our [[support department>>mailto:support@emagiz.com]].
15 +{{/info}}
13 13  
14 -{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}
15 -
16 -{{warning}}To keep a better overview, we recommend you to remove your old dynamic triggers after the new error triggers are activated, these have already been disabled by our migration process. The same applies for your queue-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page. {{/warning}}
17 +== **New eMagiz Mendix Connector**~* ==
17 17  
18 -== **Bug Fixes** ==
19 +The new eMagiz Mendix Connector is ready and will be first implemented in our own infrastructure to further assess the quality and stability of the new connector. Once this is done we will share more information to the community about the changes related to the new eMagiz Mendix Connector and make it available for a broader audience. In the mean time you will already notice a UI change that identifies Mendix systems by showing the Mendix icon on these systems.
19 19  
20 -
21 +== **Bug Fixes** ==
22 +//__Removing integrations from Create__//
23 +When removing an exit/entry connector linked to a system and using the same message type can now be removed from eMagiz without problems.
21 21  == **Fancy Forum Answers** ==
22 22  
23 23  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:
24 24  
25 -* [[JSON-TO-JSON java.lang.NumberFormatException in string field>>https://my.emagiz.com/p/question/172825635703991104||target="blank"]]
28 +* [[Issue with importing XSD into eMagiz, replacing '=ref' references>>https://my.emagiz.com/p/question/172825635704054981||target="blank"]]
26 26  
27 27  == **Key Takeaways** ==
28 28  
... ... @@ -32,7 +32,7 @@
32 32  * If you have feedback or ideas for us, talk to the Platypus
33 33  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
34 34  * Clear your browser cache (Ctrl + Shift + Del)
35 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.233 - Policy Polish.WebHome||target="blank"]]
38 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.238 - Preparation Paradise.WebHome||target="blank"]]
36 36  * Start thinking about how the license tracker can aid your development
37 37  * Start thinking about major, minor, and patch
38 38  * Keep making great integrations