Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 780.1
edited by Carlijn Kokkeler
on 2024/11/06 14:05
Change comment: There is no comment for this version
To version 824.1
edited by Carlijn Kokkeler
on 2024/12/02 10:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -233 - Policy Polish
1 +235 - Last Log
Content
... ... @@ -3,52 +3,37 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release, we have done several improvements for our Failover functionality and added two configuration options for our SMB session factory support objects. We have also updated our password policy, so from now on you are required to have a password with a minimum length of 14 characters! Apart from these improvements, we have done several bug fixes. Please find out all below!
6 +**Hi there, eMagiz developers!**
7 7  
8 +{{info}}Please note that this is our last release of the year. Our next release will be on the 16th of January!{{/info}}
9 +
8 8  == **Feedback Items** ==
9 -//__Password policy__//
10 -Our password policy has been updated such that the minimum length is 14 characters, other requirements have remained the same. All users will be required to update their password when logging in. You will not be able to close this popup until your password has been updated successfully.
11 +//__Log alerting__//
12 +We have added log message alert triggers to our new alerting stack for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well.
11 11  
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]]
14 +{{info}}
15 +* **Please take into consideration the following migration actions**:
16 +* All existing log 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., "Log Trigger 1").
22 +** **Users are advised to review and update these names to appropriately reflect each trigger's purpose.**
23 +* A new filter for ‘Log level’ has also been added to the new Log alert triggers, which will be configured such that your existing triggers will generate an alert for **all** log types.
24 +* The new feature introduces duplicate detection when saving an individual log trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate log alerts.
25 +{{/info}}
19 19  
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 +{{warning}}Please check out our **LINK** for an elaborate explanation of our new error alerting. {{/warning}}
23 23  
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.
28 -
29 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.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@release-233-support-object-alert.png]]
34 34  
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.
37 -
38 -//__Queue browser__//
39 -When clicking the queue browser button, the user will not be redirected to the home page anymore.
40 -
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 -
47 47  == **Fancy Forum Answers** ==
48 48  
49 49  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:
50 50  
51 -* [[JSON-TO-JSON java.lang.NumberFormatException in string field>>https://my.emagiz.com/p/question/172825635703991104||target="blank"]]
36 +* [[H2 database following a queue channel without message store>>https://my.emagiz.com/p/question/172825635704003822||target="blank"]]
52 52  
53 53  == **Key Takeaways** ==
54 54  
... ... @@ -58,7 +58,7 @@
58 58  * If you have feedback or ideas for us, talk to the Platypus
59 59  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
60 60  * Clear your browser cache (Ctrl + Shift + Del)
61 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.233 - Policy Polish.WebHome||target="blank"]]
46 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.234 - Alert Adventures.WebHome||target="blank"]]
62 62  * Start thinking about how the license tracker can aid your development
63 63  * Start thinking about major, minor, and patch
64 64  * Keep making great integrations