Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 252.1
edited by Carlijn Kokkeler
on 2023/11/21 11:58
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 -209 - Max Verstappen
1 +219 - Creation Carousel
Content
... ... @@ -1,74 +1,60 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have done .....
6 +**Hi there, eMagiz developers!**
6 6  
7 -{{warning}}Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC. {{/warning}}
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"]].
8 8  
9 -== **Quicker Deployment Plan** ==
10 -We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now!
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"]].
11 11  
12 -== **Next Generation Architecture Default** ==
13 -With this release, the next generation architecture will become the default. New models will use this generation as default.
14 -
15 -[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
16 -
17 -== **Cloud Template R11 Docker - Single Lane** ==
18 -This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
19 -
20 -== **Cloud Template R13 Docker - Double Lane** ==
21 -This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
22 -
23 23  == **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.
24 24  
25 -//__Unused properties overview__//
26 -In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
27 -* Not used by any runtime that is in the Create phase release.
28 -* Not required by a flow that is in the Create phase release.
29 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
18 +//__eMagiz Mendix connector__//
19 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
30 30  
31 -//__Send build requests asynchronously__//
32 -The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
21 +//__Improved OpenAPI import__//
22 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
33 33  
34 -//__Queue explorer milliseconds__//
35 -The queue browser now displays milliseconds in the timestamps.
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.
36 36  
37 -//__Cancel and next buttons order__//
38 -The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
28 +//__Volume mapping passwords__//
29 +Passwords for network volumes are hidden on the machine after deployment.
39 39  
40 -//__Unused images__//
41 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
31 +//__Create integration removal__//
32 +When removing an integration from Create, the Create phase is correctly updated as well.
42 42  
43 -//__Carwash logging__//
44 -A new logging feature enabling us to make better choices in encryption standards will be released.
34 +//__Legacy statistics__//
35 +Legacy pages are now correctly hidden when running on the current runtime architecture.
45 45  
46 -//__Static alerts queue consumers__//
47 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
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.
48 48  
49 -== **Bug Fixes** ==
40 +//__Enumeration values__//
41 +Enumeration values for event processors can now be edited in Create.
50 50  
51 -//__Flow Designer connection line__//
52 -In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
43 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
53 53  
54 -//__Portal for migrated models__//
55 -We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
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.
56 56  
57 -//__Error channel inbounds__//
58 -We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
59 -
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  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:
63 63  
64 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
65 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
66 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
67 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||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"]]
68 68  
56 +== **Key Takeaways** ==
69 69  
70 -== **Key takeaways** ==
71 -
72 72  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:
73 73  
74 74  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -75,10 +75,9 @@
75 75  * If you have feedback or ideas for us, talk to the Platypus
76 76  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
77 77  * Clear your browser cache (Ctrl + Shift + Del)
78 -* Check out the release notes [here]
64 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
79 79  * Start thinking about how the license tracker can aid your development
80 80  * Start thinking about major, minor, and patch
81 -* Upgrade to the latest build number
82 82  * Keep making great integrations
83 83  
84 84  Let's stay in touch and till next time!
... ... @@ -86,6 +86,11 @@
86 86  {{info}}
87 87  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
88 88  
89 -~*~* Indicates a next-generation-architecture only feature.
90 -{{/info}})))((({{toc/}}))){{/container}}
74 +{{/info}}
75 +)))
76 +
77 +(((
78 +{{toc/}}
79 +)))
91 91  {{/container}}
81 +{{/container}}