Skip to Content

Changes for page 240 - Spring Cleaning

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

Summary

Details

Page properties
Content
... ... @@ -3,56 +3,52 @@
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>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-error-alerting.WebHome||target="blank"]]. Moreover, a new runtime image is available, check it out [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]]. Lastly, we have improved the selection visibility in data models, and have fixed a bug regarding failover containers.
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, .
7 7  
8 8  == **Feedback Items** ==
9 9  //__Error alerting__//
10 -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 +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.
11 11  
12 -{{info}}Please take into consideration the following migration actions:
13 -* 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.
14 -* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
15 -** The 'Description' field has been replaced by the new 'Instructions' field (note: the 'Description' field no longer exists).
16 -** The values of the old description field will be transferred into the instructions field
17 -* 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.
18 -** This field will be automatically populated with a default name (e.g., "Error Trigger 1").
19 -** **Users are advised to review and update these names to appropriately reflect each trigger's purpose**.
20 -* 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:
21 -** "Check header" is disabled.
22 -** "Check error message" is enabled.
23 -** The "Error message contains" field includes only a single character.
24 -* 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}}
12 +//__Failover__//
13 +Several improvements for our failover functionality have been done:
14 +* We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.
15 + [[image:Main.Images.Release Blog.WebHome@release-233-balance-failover.png]]
16 +* We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment. This action can be found in Deploy Architecture, when right clicking on the white canvas.
17 +* We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture. Besides that, you will also see this shown in the pending changes list when you apply your changes to the environment.
18 + [[image:Main.Images.Release Blog.WebHome@release-233-failover-system.png]]
25 25  
26 -{{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}}
20 +//__Empty status__//
21 +The status of error messages can now be reset to empty.
22 +[[image:Main.Images.Release Blog.WebHome@release-233-reset-status.png]]
27 27  
28 -{{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}}
24 +//__SMB session factory__//
25 +We have added two additional configuration options to the SMB session factory support object.
26 +* Connect as guest: We have added the option to toggle whether the session factory should attempt to connect as a guest if the login attempt with the provided username and password is rejected.
27 +* Force SMB version 2: We have added the option to enforce the usage of SMB version 2. This effectively disables backwards-compatible version negotiation.
29 29  
30 -//__Attribute selection__//
31 -When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted.
32 -
33 -[[image:Main.Images.Release Blog.WebHome@release-234-cdm.png]]
34 -
35 -//__Runtime image__//
36 -We have removed some deprecated components from our runtime image.
37 -* TCP support object 'Byte array text length header (de)serializer'
38 -* Mikrotik service activator
29 +== **Bug Fixes** ==
30 +//__Support object alert__//
31 +If a component misses a support object, an alert is now shown in the Flow Designer, displaying which support object is missing.
39 39  
40 -Please find out more [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]].
33 +[[image:Main.Images.Release Blog.WebHome@release-233-support-object-alert.png]]
41 41  
42 -{{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.
43 -* Calls to com.emagiz.util.Assert can be replaced with org.springframework.util.Assert
44 -* Calls to com.emagiz.util.StringUtils can be replaced with org.springframework.util.StringUtils
45 -* Calls to com.emagiz.util.CollectionUtils can be replaced with org.springframework.util.CollectionUtils{{/warning}}
35 +//__XML to flat file__//
36 +The XML to flat file and flat file to XML transformers have been restyled, such that they are similar to all other components.
46 46  
47 -== **Bug Fixes** ==
48 -//__Failover container__//
49 -The failover container will now be shown correctly.
38 +//__Queue browser__//
39 +When clicking the queue browser button, the user will not be redirected to the home page anymore.
50 50  
41 +//__Edit freeze__//
42 +We fixed an issue where the browser page would get frozen when editing a flow component.
43 +
44 +//__Release version__//
45 +The version number of releases that have been activated, cannot be reused anymore for new releases. Note that this check only applies to release version numbers that are activated since this Release 233.
46 +
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[H2 database following a queue channel without message store>>https://my.emagiz.com/p/question/172825635704003822||target="blank"]]
51 +* [[JSON-TO-JSON java.lang.NumberFormatException in string field>>https://my.emagiz.com/p/question/172825635703991104||target="blank"]]
56 56  
57 57  == **Key Takeaways** ==
58 58  
... ... @@ -62,7 +62,7 @@
62 62  * If you have feedback or ideas for us, talk to the Platypus
63 63  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64 64  * Clear your browser cache (Ctrl + Shift + Del)
65 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.234 - Alert Adventures.WebHome||target="blank"]]
61 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.233 - Policy Polish.WebHome||target="blank"]]
66 66  * Start thinking about how the license tracker can aid your development
67 67  * Start thinking about major, minor, and patch
68 68  * Keep making great integrations