Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 384.1
edited by Carlijn Kokkeler
on 2024/02/12 16:54
Change comment: There is no comment for this version
To version 464.1
edited by Carlijn Kokkeler
on 2024/04/23 10:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -214 - System Symphony
1 +219 - Creation Carousel
Content
... ... @@ -3,48 +3,43 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release contains multiple bug fixes, as well as some other improvements. The monitoring graphs have been improved, such that they can now show data up to the last thirty days. Moreover, we can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.
6 +**Hi there, eMagiz developers!**
7 7  
8 +
8 8  == **Feedback Items** ==
10 +//__Machine agents__//
11 +We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more here.
9 9  
10 -//__On premise Windows machines__//
11 -We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
13 +//__Custom webhook__//
14 +We removed a deprecated functionality that sends a custom webhook when upgrading the environment. Please find out more here.
12 12  
13 -[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
16 +//__eMagiz Mendix connector__//
17 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.4
14 14  
15 -//__Adding multiple attributes__//
16 -It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity. To utilize this, a new runtime image, [V.2.1.1>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.1/||target="blank"]], is needed.
19 +//__Improved OpenAPI import__//
20 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
17 17  
18 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
19 -
20 -//__Monitoring graphs__//
21 -The monitoring graphs can now show data up to the last thirty days.
22 -
23 23  == **Bug Fixes** ==
24 -//__Image versions__//
25 -The deletion of releases with deployed container versions will not be blocked anymore. Automated release clean up behaviour will also not exclude these releases from deletion. Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases.
23 +//__Error handling__//
24 +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.
26 26  
27 -//__Failover group helptext__//
28 -The helptext of the Group attribute has been improved.
26 +//__Volume mapping passwords__//
27 +Passwords for network volumes are hidden on the machine after deployment.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
29 +//__Create integration removal__//
30 +When removing an integration from Create, the Create phase is correctly updated as well.
31 31  
32 -//__Failover group refresh__//
33 -A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in Group tab of "Start/Stop Flows" screen.
32 +//__Legacy statistics__//
33 +Legacy pages are now correctly hidden when running on the current runtime architecture.
34 34  
35 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
36 -
37 -//__Resource paths__//
38 -After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
39 -
40 40  == **Fancy Forum Answers** ==
41 41  
42 42  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:
43 43  
44 -* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
45 -* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
46 -* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
47 -* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]]
39 +* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
40 +* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
41 +* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
42 +* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
48 48  
49 49  == **Key Takeaways** ==
50 50  
... ... @@ -54,7 +54,7 @@
54 54  * If you have feedback or ideas for us, talk to the Platypus
55 55  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
56 56  * Clear your browser cache (Ctrl + Shift + Del)
57 -* Check out the release notes [here]
52 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
58 58  * Start thinking about how the license tracker can aid your development
59 59  * Start thinking about major, minor, and patch
60 60  * Keep making great integrations