Skip to Content

Changes for page 240 - Spring Cleaning

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -235 - TBD
1 +240 - Spring Cleaning
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -3,59 +3,33 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!** In this release, we focused on tidying up our house to make it ready for various cool things to come later this year. As a result, we have a set of infastrucutural improvements as well as several UI/UX related improvements and bug fixes for you to enjoy.
7 7  
8 -{{info}}Please note that this is our last release of the year. Our next release will be on the 19th of January!{{/info}}
8 +== **Minor Changes** ==
9 9  
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.
10 +//__Alerts/Notifications improved UI/UX__//
11 +Alerts/Notifications now have an icon before the text to put further emphasis on the meaning. One example of such a change is shown below.
13 13  
14 -{{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}}
13 +[[image:Main.Images.Release Blog.WebHome@release-240-improved-icon-alerts.png]]
28 28  
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}}
15 +//__Badge, Switch, and progess bar have an improved UI/UX__//
16 +We have updated our badge, switch and progress bar components. This to improve the overall quality and consistency of what we show to the user. One example of such a change is shown below.
30 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}}
18 +[[image:Main.Images.Release Blog.WebHome@release-240-improved-badge-alerts.png]]
32 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]]
37 -
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
42 -
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 -
50 50  == **Bug Fixes** ==
51 -//__Failover container__//
52 -The failover container will now be shown correctly.
21 +//__Auto-creation API Operation entry gate__//
22 +We have changed the auto-creation behavior for entry gates. This means that we now avoid creating functionality in these entry gates that is only relevant for flows running inside a Mendix app.
53 53  
24 +//__Infra flow reset Mendix Connector__//
25 +Infra flows for systems labeled as a "Mendix Connector" can no be reset once more under all circumstances, also when your model utilize the code mapping functionality.
26 +
54 54  == **Fancy Forum Answers** ==
55 55  
56 56  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:
57 57  
58 -* [[H2 database following a queue channel without message store>>https://my.emagiz.com/p/question/172825635704003822||target="blank"]]
31 +* [[sum function in xpath concatenates instead of sums>>https://my.emagiz.com/p/question/172825635704067995||target="blank"]]
32 +* [["Failed to list files" error log>>https://my.emagiz.com/p/question/172825635704067900||target="blank"]]
59 59  
60 60  == **Key Takeaways** ==
61 61  
... ... @@ -65,7 +65,7 @@
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 66  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.234 - Alert Adventures.WebHome||target="blank"]]
42 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.240 - Spring Cleaning.WebHome||target="blank"]]
69 69  * Start thinking about how the license tracker can aid your development
70 70  * Start thinking about major, minor, and patch
71 71  * Keep making great integrations