Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 853.1
edited by Erik Bakker
on 2025/02/10 09:27
Change comment: There is no comment for this version
To version 852.2
edited by Erik Bakker
on 2025/02/10 09:16
Change comment: Update document after refactoring.

Summary

Details

Page properties
Content
... ... @@ -3,24 +3,63 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we focused on finishing the first iteration of our new eMagiz Mendix Connector and the first iteration of our new base image. We will first utilize the new eMagiz Mendix Connector to get an even better feeling of its performance, but you will notice a UI change straightaway. Once we have passed that hurdle, we will share more information about it and release it to a broader range of customers. Regarding the base image, we will now introduce this to our flow testing offering to see if anything unexpected happens. This is an additional safety measure we have put in place to reduce the chance of something breaking in your model once the new base image is released. On top of that, we have some minor updates to improve the quality of the platform.
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 Deploy 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 -== **Updated Base Image** - Flow Testing Only ==
8 +== **Runtime Memory Update (Windows Machines Only)** - Reverted ==
9 9  
10 -With this release we introduce the new [[runtime image>>Main.Release Information.Runtime Images||target="blank"]] to our flow testing functionality. This means that as of that moment your flow tests will run against the latest runtime image. We do this to decrease the likelihood of unexpected things happening on your actual environments once we release the image to the community.
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 12  {{info}}
13 13  * **Please take into consideration the following**:
14 -* This means that the flow testing results could differ from the results you get once you have deployed your functionality to an environment. If something like that happens please contact us via our [[support department>>mailto:support@emagiz.com]].
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 +
18 +[[image:Main.Images.Release Blog.WebHome@release-237-manual-override-memory-on-prem.png]]
19 +
20 +* Should you encounter any problems, please get in touch with our [[support department>>mailto:support@emagiz.com]]!
15 15  {{/info}}
16 16  
17 -== **New eMagiz Mendix Connector**~* ==
23 +== **Certificate Update** ==
18 18  
19 -The new eMagiz Mendix Connector is ready and will be first implemented in our own infrastructure to further assess the quality and stability of the new connector. Once this is done we will share more information to the community about the changes related to the new eMagiz Mendix Connector and make it available for a broader audience. In the mean time you will already notice a UI change that identifies Mendix systems by showing the Mendix icon on these systems.
25 +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]]!
20 20  
27 +== **Minor changes** ==
28 +//__SMB component improvements__//
29 +Validation feedback and help text updates for the following components: SMB outbound gateway, SMB session factory, and SMB composite list filter.
30 +
31 +//__EDI Components - Styling Update__//
32 +The styling of the following components has been updated.
33 +
34 +* XML to EDI transformer
35 +* EDI to XML transformer
36 +* XML to UN/EDIFACT transformer
37 +* UN/EDIFACT to XML transformer
38 +
39 +//__Manage Statistics UI Update__//
40 +We have updated our monitoring graph technology, including minor styling updates across the different current-generation monitoring dashboards.
41 +
42 +[[image:Main.Images.Release Blog.WebHome@release-237-ui-changes-manage-statistics.png]]
43 +
21 21  == **Bug Fixes** ==
45 +//__Import from Store - Design__//
46 +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.
47 +
22 22  //__Removing integrations from Create__//
23 -When removing an exit/entry connector linked to a system and using the same message type can now be removed from eMagiz without problems.
49 +When the last integration is removed from a system in create, the container infra flows are also removed from the create phase release.
50 +
51 +//__Flow Test Logging - Navigation__//
52 +We have improved the navigation of the logging shown on the flow test level in Create.
53 +
54 +//__Create Phase - Synchronization process updated__//
55 +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.
56 +
57 +//__Update on search functionality in "Start/Stop flows" overview__//
58 +Searching in the start/stop flows overview and the queue browser can now be done from any page in the overviews.
59 +
60 +//__Windows line break fix__//
61 +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.
62 +
24 24  == **Fancy Forum Answers** ==
25 25  
26 26  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:
... ... @@ -35,7 +35,7 @@
35 35  * If you have feedback or ideas for us, talk to the Platypus
36 36  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
37 37  * Clear your browser cache (Ctrl + Shift + Del)
38 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.238 - Preparation Paradise.WebHome||target="blank"]]
77 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.237 - Fabulous Flow.WebHome||target="blank"]]
39 39  * Start thinking about how the license tracker can aid your development
40 40  * Start thinking about major, minor, and patch
41 41  * Keep making great integrations