Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 854.1
edited by Erik Bakker
on 2025/02/10 09:30
Change comment: There is no comment for this version
To version 815.1
edited by Carlijn Kokkeler
on 2024/12/02 09:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -238 - Preparation Paraside
1 +235 - TBD
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -3,30 +3,59 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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.
6 +**Hi there, eMagiz developers!**
7 7  
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 your flow tests will run against the latest runtime image as of that moment. We do this to decrease the likelihood of unexpected things happening in your actual environments once we release the image to the community.
8 +{{info}}Please note that this is our last release of the year. Our next release will be on the 19th of January!{{/info}}
11 11  
10 +== **Feedback Items** ==
11 +//__Error alerting__//
12 +Error alerting 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"]] several 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.
13 +
12 12  {{info}}
13 -* **Please take into consideration the following**:
14 -* This means the flow testing results could differ from those 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}}
15 +Please take into consideration the following migration actions:
16 +* All existing error message alert triggers from the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture models will be automatically migrated to the new alerting feature.
17 +* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
18 +** The 'Description' field has been replaced by the new 'Instructions' field (note: the 'Description' field no longer exists).
19 +** The values of the old description field will be transferred into the instructions field
20 +* Additionally, a new field, 'Name', has been introduced for identification purposes. The 'Name' field will be included in email notifications when a trigger is activated.
21 +** This field will be automatically populated with a default name (e.g., "Error Trigger 1").
22 +** **Users are advised to review and update these names to appropriately reflect each trigger's purpose**.
23 +* If an error message alert trigger has the following specific configuration, its trigger conditions will be migrated such that alerts are triggered for **all** incoming error messages:
24 +** "Check header" is disabled.
25 +** "Check error message" is enabled.
26 +** The "Error message contains" field includes only a single character.
27 +* The new feature introduces duplicate detection when saving an individual error trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate error alerts.{{/info}}
16 16  
17 -== **New eMagiz Mendix Connector**~* ==
29 +{{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}}
30 +
31 +{{warning}}Please check out our [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-error-alerting.WebHome||target="blank"]] for an elaborate explanation of our new error alerting. {{/warning}}
32 +
33 +//__Attribute selection__//
34 +When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted.
35 +
36 +[[image:Main.Images.Release Blog.WebHome@release-234-cdm.png]]
18 18  
19 -The new eMagiz Mendix Connector is ready and will be first implemented in our infrastructure further to assess the quality and stability of the new connector. Once this is done, we will share more information with the community about the new eMagiz Mendix Connector changes and make it available to a broader audience. In the meantime, you will already notice a UI change that identifies Mendix systems by showing the Mendix icon on these systems.
38 +//__Runtime image__//
39 +We have removed some deprecated components from our runtime image.
40 +* TCP support object 'Byte array text length header (de)serializer'
41 +* Mikrotik service activator
20 20  
43 +Please find out more [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]].
44 +
45 +{{warning}}We recommend evaluating custom groovy scripts and SpEL expressions to ensure that they do not rely on functionality that may have been removed due to one of the library removals.
46 +* Calls to com.emagiz.util.Assert can be replaced with org.springframework.util.Assert
47 +* Calls to com.emagiz.util.StringUtils can be replaced with org.springframework.util.StringUtils
48 +* Calls to com.emagiz.util.CollectionUtils can be replaced with org.springframework.util.CollectionUtils{{/warning}}
49 +
21 21  == **Bug Fixes** ==
22 -//__Removing integrations from Create__//
23 -Removing an exit/entry connector linked to a system and using the same message type can now be removed from eMagiz without problems.
51 +//__Failover container__//
52 +The failover container will now be shown correctly.
24 24  
25 25  == **Fancy Forum Answers** ==
26 26  
27 27  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:
28 28  
29 -* [[Spaces handled differently in folder name after using SMB components for file connectivity>>https://my.emagiz.com/p/question/172825635703940018||target="blank"]]
58 +* [[H2 database following a queue channel without message store>>https://my.emagiz.com/p/question/172825635704003822||target="blank"]]
30 30  
31 31  == **Key Takeaways** ==
32 32  
... ... @@ -36,7 +36,7 @@
36 36  * If you have feedback or ideas for us, talk to the Platypus
37 37  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
38 38  * Clear your browser cache (Ctrl + Shift + Del)
39 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.238 - Preparation Paradise.WebHome||target="blank"]]
68 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.234 - Alert Adventures.WebHome||target="blank"]]
40 40  * Start thinking about how the license tracker can aid your development
41 41  * Start thinking about major, minor, and patch
42 42  * Keep making great integrations