Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 785.1
edited by Carlijn Kokkeler
on 2024/11/18 11:56
Change comment: There is no comment for this version
To version 779.1
edited by Carlijn Kokkeler
on 2024/11/05 16:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -234 - Alert Adventures
1 +233 - Policy Polish
Content
... ... @@ -3,22 +3,44 @@
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!** 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!
7 7  
8 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.
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 11  
12 -{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}
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]]
13 13  
14 -{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/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]]
15 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}}
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.
17 17  
18 -
19 19  == **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.
20 20  
33 +[[image:Main.Images.Release Blog.WebHome@release-233-support-object-alert.png]]
21 21  
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 +
22 22  == **Fancy Forum Answers** ==
23 23  
24 24  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: