Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 782.1
edited by Carlijn Kokkeler
on 2024/11/18 10:46
Change comment: There is no comment for this version
To version 848.1
edited by Erik Bakker
on 2025/01/27 13:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -234 - Alert Adventures
1 +237 - Fabulous Flow
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.Release Information.Release Blogs.WebHome
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -3,52 +3,66 @@
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!** In this release, we focused on improving the flow back and forth between the various phases in eMagiz by solving several feedback items related to Design, Create, and Design and the interaction between these three phases. We have also improved the memory calculation for all runtimes running on a Windows machine. Moreover, we have updated the styling of our graphs in the Manage phase.
7 7  
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.
8 +== **Runtime Memory Update (Windows Machines Only)** ==
9 +
10 +As part of this release, we will update the underlying memory calculations for all runtimes running on a Windows machine. Consequently, these runtimes will have a slightly increased memory footprint on your machine.
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]]
12 +{{info}}
13 +* **Please take into consideration the following**:
14 +* The new memory settings will take effect on the **first** deployment you will execute after **this** release.
15 +** When executing this deployment, you will see a pop-up notifying you of the **new** used memory. Here, you can also see whether the new **used** memory exceeds the available memory.
16 +* Should the **used** memory increase the available memory (as determined by eMagiz), you can manually override this setting in Design -> Architecture under the "Edit machine" option by filling in the memory field.
17 +[[image:Main.Images.Release Blog.WebHome@release-237-manual-override-memory-on-prem.png]]
18 +* Should you encounter any problems, please get in touch with our [[support department>>mailto:support@emagiz.com]]!
19 +{{/info}}
20 +
21 +== **Certificate Update** ==
22 +
23 +As announced on our [[status page>>https://status.emagiz.com/incidents/4wb8tt5x9v95||target="blank"]], we will update our emagizcloud certificate as part of this release. Should you encounter any problems, please get in touch with our [[support department>>mailto:support@emagiz.com]]!
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]]
25 +== **Minor changes** ==
26 +//__SMB component improvements__//
27 +Validation feedback and help text updates for the following components: SMB outbound gateway, SMB session factory, and SMB composite list filter.
28 +
29 +//__EDI Components - Styling Update__//
30 +The styling of the following components has been updated.
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.
32 +* XML to EDI transformer
33 +* EDI to XML transformer
34 +* XML to UN/EDIFACT transformer
35 +* UN/EDIFACT to XML transformer
36 +
37 +//__Manage Statistics UI Update__//
38 +We have updated our monitoring graph technology, including minor styling updates across the different current-generation monitoring dashboards.
28 28  
40 +[[image:Main.Images.Release Blog.WebHome@release-237-ui-changes-manage-statistics.png]]
41 +
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.
43 +//__Import from Store - Design__//
44 +The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. This is to avoid broken transformations within the Create phase of eMagiz.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@release-233-support-object-alert.png]]
46 +//__Removing integrations from Create__//
47 +When the last integration is removed from a system in create, the container infra flows are also removed from the create phase release.
48 +
49 +//__Flow Test Logging - Navigation__//
50 +We have improved the navigation of the logging shown on the flow test level in Create.
51 +
52 +//__Create Phase - Synchronization process updated__//
53 +The flow version for the Create release on the Deploy phase is synced for that specific flow automatically when the user resets the flow in the Create phase.
54 +
55 +//__Update on search functionality in "Start/Stop flows" overview__//
56 +Searching in the start/stop flows overview and the queue browser can now be done from any page in the overviews.
57 +
58 +//__Windows line break fix__//
59 +If the message in a log or error contained a Windows line break (\r\n), and a log or error alert was configured that matched it, an alert would be generated, but no email would be sent out.
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"]]
65 +* [[Issue with importing XSD into eMagiz, replacing '=ref' references>>https://my.emagiz.com/p/question/172825635704054981||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"]]
75 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.237 - Fabulous Flow.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