Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 781.1
edited by Carlijn Kokkeler
on 2024/11/06 14:06
Change comment: There is no comment for this version
To version 725.1
edited by Carlijn Kokkeler
on 2024/09/27 09:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -233 - Policy Polish
1 +230 - Petite Peaks
Content
... ... @@ -3,52 +3,33 @@
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!** In this release, we have some small improvements and bug fixes. First of all, the pop-up when adding an integration to an existing API in Design has been improved. Secondly, queues with illegal characters will not cause errors anymore. Thirdly, an issue has been fixed where a deployment step would get blocked. Please find out all below!
7 7  
8 +{{info}}Please note that during this deployment, Kafka metrics will be unavailable and lost for the duration of the deployment. After the deployment is complete, Kafka metrics will resume and be reflected in the monitoring graphs, but no metrics will be present corresponding to the deployment period.{{/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 +//__Add integration__//
12 +When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
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 +[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
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]]
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 -
16 +//__Failover__//
17 +We have introduced a new failover feature, allowing you to enable failover on messaging flows with minimal setup required. Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]].
18 +
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.
20 +//__Queues with illegal characters__//
21 +Existing queues with illegal characters will not generate errors anymore. They can now be searched, deleted, explored, wiretapped, etc. in Manage -> Explore.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@release-233-support-object-alert.png]]
23 +//__Blocked deployment step__//
24 +We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
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"]]
30 +* [[Error being stamped on the wrong "last flow">>https://my.emagiz.com/p/question/172825635703952578||target="blank"]]
31 +* [[AMQP broker hostname for JMS-host instead of IP>>https://my.emagiz.com/p/question/172825635703965465||target="blank"]]
32 +* [[Calling a soap webservice that is secured with a client certificate>>https://my.emagiz.com/p/question/172825635703965402||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"]]
42 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.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