Wiki source code of 209 - Max Verstappen

Version 255.1 by CarlijnKokkeler on 2023/11/21 12:05

Hide last authors
eMagiz 1.1 1 {{container}}
CarlijnKokkeler 254.1 2 {{container layoutStyle="columns"}}
3 (((
eMagiz 1.1 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5
CarlijnKokkeler 242.1 6 **Hi there, eMagiz developers!** We have done .....
CarlijnKokkeler 206.1 7
CarlijnKokkeler 254.1 8 {{warning}}
CarlijnKokkeler 255.1 9 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.
CarlijnKokkeler 254.1 10 {{/warning}}
CarlijnKokkeler 243.1 11
CarlijnKokkeler 247.1 12 == **Quicker Deployment Plan** ==
CarlijnKokkeler 254.1 13
CarlijnKokkeler 246.1 14 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!
15
CarlijnKokkeler 242.1 16 == **Next Generation Architecture Default** ==
CarlijnKokkeler 254.1 17
CarlijnKokkeler 242.1 18 With this release, the next generation architecture will become the default. New models will use this generation as default.
CarlijnKokkeler 206.1 19
CarlijnKokkeler 254.1 20 [[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
CarlijnKokkeler 172.1 21
CarlijnKokkeler 249.1 22 == **Cloud Template R11 Docker - Single Lane** ==
CarlijnKokkeler 254.1 23
CarlijnKokkeler 251.1 24 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"]].
CarlijnKokkeler 227.1 25
CarlijnKokkeler 249.1 26 == **Cloud Template R13 Docker - Double Lane** ==
CarlijnKokkeler 254.1 27
CarlijnKokkeler 252.1 28 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"]].
CarlijnKokkeler 187.1 29
CarlijnKokkeler 154.1 30 == **Feedback Items** ==
Erik Bakker 149.1 31
CarlijnKokkeler 242.1 32 //__Unused properties overview__//
33 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:
CarlijnKokkeler 254.1 34
CarlijnKokkeler 242.1 35 * Not used by any runtime that is in the Create phase release.
36 * Not required by a flow that is in the Create phase release.
37 * If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
Erik Bakker 151.1 38
CarlijnKokkeler 242.1 39 //__Send build requests asynchronously__//
40 The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
Erik Bakker 151.1 41
CarlijnKokkeler 242.1 42 //__Queue explorer milliseconds__//
43 The queue browser now displays milliseconds in the timestamps.
Erik Bakker 151.1 44
CarlijnKokkeler 198.1 45 //__Cancel and next buttons order__//
CarlijnKokkeler 196.1 46 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.
CarlijnKokkeler 155.1 47
CarlijnKokkeler 242.1 48 //__Unused images__//
CarlijnKokkeler 197.1 49 When a release is removed, the related unused images in the on-premises machines will be removed as well.
50
CarlijnKokkeler 242.1 51 //__Carwash logging__//
52 A new logging feature enabling us to make better choices in encryption standards will be released.
CarlijnKokkeler 197.1 53
CarlijnKokkeler 242.1 54 //__Static alerts queue consumers__//
55 Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
CarlijnKokkeler 197.1 56
Erik Bakker 124.1 57 == **Bug Fixes** ==
CarlijnKokkeler 197.1 58
CarlijnKokkeler 242.1 59 //__Flow Designer connection line__//
60 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.
Erik Bakker 148.1 61
CarlijnKokkeler 242.1 62 //__Portal for migrated models__//
63 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.
CarlijnKokkeler 197.1 64
CarlijnKokkeler 242.1 65 //__Error channel inbounds__//
66 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.
CarlijnKokkeler 197.1 67
eMagiz 1.1 68 == **Fancy Forum Answers** ==
69
Erik Bakker 30.1 70 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:
eMagiz 1.1 71
CarlijnKokkeler 253.1 72 * [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
eMagiz 1.1 73
74 == **Key takeaways** ==
75
Erik Bakker 149.1 76 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:
eMagiz 1.1 77
Erik Bakker 30.1 78 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
eMagiz 1.1 79 * If you have feedback or ideas for us, talk to the Platypus
Erik Bakker 151.1 80 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
eMagiz 1.1 81 * Clear your browser cache (Ctrl + Shift + Del)
82 * Check out the release notes [here]
83 * Start thinking about how the license tracker can aid your development
84 * Start thinking about major, minor, and patch
85 * Upgrade to the latest build number
86 * Keep making great integrations
87
88 Let's stay in touch and till next time!
89
90 {{info}}
Erik Bakker 30.1 91 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
eMagiz 1.1 92
Erik Bakker 141.1 93 ~*~* Indicates a next-generation-architecture only feature.
CarlijnKokkeler 254.1 94 {{/info}}
95 )))
96
97 (((
98 {{toc/}}
99 )))
eMagiz 1.1 100 {{/container}}
CarlijnKokkeler 254.1 101 {{/container}}