Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 291.1
edited by Carlijn Kokkeler
on 2023/12/06 14:25
Change comment: There is no comment for this version
To version 471.1
edited by Carlijn Kokkeler
on 2024/04/23 12:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -210 - Deployment Delights
1 +219 - Creation Carousel
Content
... ... @@ -3,62 +3,58 @@
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 have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
6 +**Hi there, eMagiz developers!**
7 7  
8 -== **Alerts** ==
8 +== **Environment Template R13 Docker - Single Lane** ==
9 +This release introduces a new non-service affecting environment template for all our customers running in a single-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Single Lane.WebHome||target="blank"]].
9 9  
10 -//__Topic approaching max size alert__//
11 -The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
11 +== **Environment Template R15 Docker - Double Lane** ==
12 +This release introduces a new non-service affecting environment template for all our customers running in a double-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R15 Docker - Double Lane.WebHome||target="blank"]].
12 12  
13 -//__Missing metrics alert__//
14 -We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
15 -
16 16  == **Feedback Items** ==
15 +//__Machine agents__//
16 +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.
17 17  
18 -//__Improved release build process__//
19 -When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
18 +//__eMagiz Mendix connector__//
19 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
20 20  
21 -//__Container version overview__//
22 -Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
21 +//__Improved OpenAPI import__//
22 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
23 23  
24 -[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
24 +== **Bug Fixes** ==
25 +//__Error handling__//
26 +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.
25 25  
26 -//__Improved deployment process__//
27 -The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
28 +//__Volume mapping passwords__//
29 +Passwords for network volumes are hidden on the machine after deployment.
28 28  
29 -//__Rebuilding of images__//
30 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
31 +//__Create integration removal__//
32 +When removing an integration from Create, the Create phase is correctly updated as well.
31 31  
32 -== **Bug Fixes** ==
34 +//__Legacy statistics__//
35 +Legacy pages are now correctly hidden when running on the current runtime architecture.
33 33  
34 -//__Runtime metrics processing__//
35 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
37 +//__Unused properties__//
38 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
36 36  
37 -//__Deployment plan__//
38 -We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
40 +//__Enumeration values__//
41 +Enumeration values for event processors can now be edited in Create.
39 39  
40 -//__View all store items__//
41 -An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
43 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
42 42  
43 -//__Out of memory behavior__//
44 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
45 +//__SFTP sessions__//
46 +SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. Please find out more HERE.
45 45  
46 -//__Max fetch size__//
47 -In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
48 -
49 49  == **Fancy Forum Answers** ==
50 50  
51 51  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:
52 52  
53 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
52 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
53 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
54 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
58 58  
56 +== **Key Takeaways** ==
59 59  
60 -== **Key takeaways** ==
61 -
62 62  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
63 63  
64 64  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -65,10 +65,9 @@
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 66  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 -* Check out the release notes [here]
64 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
69 69  * Start thinking about how the license tracker can aid your development
70 70  * Start thinking about major, minor, and patch
71 -* Upgrade to the latest build number
72 72  * Keep making great integrations
73 73  
74 74  Let's stay in touch and till next time!
... ... @@ -76,7 +76,6 @@
76 76  {{info}}
77 77  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  
79 -~*~* Indicates a next-generation-architecture only feature.
80 80  {{/info}}
81 81  )))
82 82