Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 298.1
edited by Carlijn Kokkeler
on 2023/12/18 12:51
Change comment: There is no comment for this version
To version 265.1
edited by Carlijn Kokkeler
on 2023/11/22 15:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +209 - Max Verstappen
Content
... ... @@ -3,47 +3,70 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
7 7  
8 -== **TBD** ==
8 +{{warning}}
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.
10 +{{/warning}}
9 9  
12 +== **Quicker Deployment Plan Execution** ==
10 10  
14 +We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. So, the deployment plan will be finished much quicker now!
11 11  
16 +== **Next Generation Architecture Default** ==
17 +
18 +With this release, the next generation architecture will become the default. From now on, new models will then use this generation as the default architecture.
19 +
20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
21 +
22 +== **Cloud Template R11 Docker - Single Lane** ==
23 +
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"]].
25 +
26 +== **Cloud Template R13 Docker - Double Lane** ==
27 +
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"]].
29 +
12 12  == **Feedback Items** ==
13 13  
14 -//__Missing properties overview__//
15 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
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:
16 16  
17 -ADD FIGURE
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.
18 18  
19 -//__Broker queue metrics dashboards__//
20 -It is now possible to select the MQTT broker in the queue metrics dashboards.
39 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-unused-properties-overview.png]]
21 21  
22 -== **Bug Fixes** ==
41 +//__Queue explorer milliseconds__//
42 +The queue browser now displays milliseconds in the timestamps.
23 23  
24 -//__Deployment execution error message__//
25 -In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup.
44 +//__Unused images__//
45 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
26 26  
27 -//__Cloud template upgrade unjust rollback__//
28 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
47 +//__Carwash logging__//
48 +A new logging feature enabling us to make better choices in encryption standards will be released.
29 29  
30 -//__Missing log entries__//
31 -We improved crash handling so that log messages clearly show when and why a container failed to start.
50 +//__Static alerts queue consumers__//
51 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
32 32  
33 -//__Runtime logging__//
34 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
53 +== **Bug Fixes** ==
35 35  
55 +//__Flow Designer connection line__//
56 +In the Flow Designer an issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
57 +
58 +//__Portal for migrated models__//
59 +We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
60 +
61 +//__Error channel inbounds__//
62 +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.
63 +
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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:
39 39  
40 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
41 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
42 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
43 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
44 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
68 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
45 45  
46 -
47 47  == **Key takeaways** ==
48 48  
49 49  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: