Skip to Content

Wiki source code of 209 - Max Verstappen

Version 243.1 by Carlijn Kokkeler on 2023/11/21 11:31
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}(((
3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4
5 **Hi there, eMagiz developers!** We have done .....
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
8 6:00 AM UTC instead 5:00 AM UTC. {{/warning}}
9
10 == **Next Generation Architecture Default** ==
11 With this release, the next generation architecture will become the default. New models will use this generation as default.
12
13 [[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
14
15 == **Cloud Template R11 - Single Lane** ==
16 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
17
18 == **Cloud Template R13 - Double Lane** ==
19
20
21 == **Feedback Items** ==
22
23 //__Unused properties overview__//
24 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:
25 * Not used by any runtime that is in the Create phase release.
26 * Not required by a flow that is in the Create phase release.
27 * If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
28
29 //__Send build requests asynchronously__//
30 The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
31
32 //__Queue explorer milliseconds__//
33 The queue browser now displays milliseconds in the timestamps.
34
35 //__Cancel and next buttons order__//
36 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.
37
38 //__Unused images__//
39 When a release is removed, the related unused images in the on-premises machines will be removed as well.
40
41 //__Carwash logging__//
42 A new logging feature enabling us to make better choices in encryption standards will be released.
43
44 //__Static alerts queue consumers__//
45 Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
46
47 == **Bug Fixes** ==
48
49 //__Images rebuild__//
50 We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped.
51
52 //__Flow Designer connection line__//
53 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.
54
55 //__Portal for migrated models__//
56 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.
57
58 //__Error channel inbounds__//
59 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.
60
61 == **Fancy Forum Answers** ==
62
63 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:
64
65 * [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
66 * [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
67 * [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
68 * [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
69
70
71 == **Key takeaways** ==
72
73 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:
74
75 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76 * If you have feedback or ideas for us, talk to the Platypus
77 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
78 * Clear your browser cache (Ctrl + Shift + Del)
79 * Check out the release notes [here]
80 * Start thinking about how the license tracker can aid your development
81 * Start thinking about major, minor, and patch
82 * Upgrade to the latest build number
83 * Keep making great integrations
84
85 Let's stay in touch and till next time!
86
87 {{info}}
88 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
89
90 ~*~* Indicates a next-generation-architecture only feature.
91 {{/info}})))((({{toc/}}))){{/container}}
92 {{/container}}