Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 486.1
edited by Carlijn Kokkeler
on 2024/04/23 15:19
Change comment: There is no comment for this version
To version 487.1
edited by Carlijn Kokkeler
on 2024/04/23 15:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,7 +3,7 @@
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 a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
6 +**Hi there, eMagiz developers!** This release, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, we have improved our functionality to enable users to seamlessly import OpenAPI specifications with URL paths of up to 300 characters in length. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
7 7  
8 8  == **Feedback Items** ==
9 9  
... ... @@ -11,7 +11,7 @@
11 11  We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
12 12  
13 13  //__Improved OpenAPI import__//
14 -The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
14 +The path length that eMagiz supports when importing OpenAPI specifications is now increased to a maximum of 300 characters.
15 15  
16 16  //__Flow test stack trace__//
17 17  If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab.
... ... @@ -24,13 +24,12 @@
24 24  
25 25  In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}}
26 26  
27 -
28 28  == **Bug Fixes** ==
29 29  //__Error handling__//
30 30  When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
31 31  
32 32  //__Volume mapping passwords__//
33 -Passwords for network volumes are hidden on the machine after deployment.
32 +Passwords for network volumes are now securely hidden in the runtime’s machine after deploying a new release.
34 34  
35 35  //__Create integration removal__//
36 36  When removing an integration from Create, the Create phase is now correctly updated.
... ... @@ -39,7 +39,7 @@
39 39  Legacy pages are now correctly hidden when running on the current runtime architecture.
40 40  
41 41  //__Unused properties__//
42 -Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
41 +Users should not be able to edit or delete eMagiz properties, and so these eMagiz properties will now not be shown in the 'Unused property overview' anymore.
43 43  
44 44  //__Enumeration values__//
45 45  Enumeration values for event processors can now be edited in Create.