Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 267.1
edited by Carlijn Kokkeler
on 2023/11/23 08:57
Change comment: There is no comment for this version
To version 127.1
edited by Samet Kaya
on 2023/06/20 13:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +200 - Uncharted Territories
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.SametKaya
Content
... ... @@ -1,70 +1,61 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on a lot of things that are unfortunately not quite ready to be released. As a result the output of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
7 7  
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}}
7 +== **Next generation improvements and bug fixes** ==
11 11  
12 -== **Quicker Deployment Plan Execution** ==
9 +//__Enhanced right-hand view within Deployment Plan context__//
10 +When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
13 13  
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!
12 +{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
15 15  
16 -== **Next Generation Architecture Default** ==
14 +//__Improved timeout settings when deploying__//
15 +To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
17 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.
17 +{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
19 19  
20 -[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
19 +//__Detailed HTTP Statistics now show user info in specific additional cases__//
20 +To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
21 21  
22 -== **Cloud Template R11 Docker - Single Lane** ==
22 +{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
23 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"]].
24 +//__Improved loading speed of Manage Dashboard__//
25 +This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
25 25  
26 -== **Cloud Template R13 Docker - Double Lane** ==
27 +== **Store Improvements** ==
27 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 +//__Importing in Design is improved__//
30 +We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
29 29  
30 -== **Feedback Items** ==
32 +== **Bug Fixes** ==
31 31  
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:
34 +//__Deprecated reminder pop-up removed__//
35 +We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
34 34  
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.
37 +//__Improved selection area in Flow Designer__//
38 +When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
38 38  
39 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-unused-properties-overview.png]]
40 +//__Improved Kafka settings__//
41 +For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
40 40  
41 -//__Queue explorer milliseconds__//
42 -The queue browser now displays milliseconds in the timestamps.
43 +{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
43 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 -//__Flow Designer connection line__//
50 -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.
51 -
52 -//__Portal for migrated models__//
53 -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.
54 -
55 55  == **Fancy Forum Answers** ==
56 56  
57 57  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:
58 58  
59 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
49 +* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
50 +* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
60 60  
61 61  == **Key takeaways** ==
62 62  
63 -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:
54 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
64 64  
65 65  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66 66  * If you have feedback or ideas for us, talk to the Platypus
67 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
58 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
68 68  * Clear your browser cache (Ctrl + Shift + Del)
69 69  * Check out the release notes [here]
70 70  * Start thinking about how the license tracker can aid your development
... ... @@ -77,12 +77,6 @@
77 77  {{info}}
78 78  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
79 79  
80 -~*~* Indicates a next-generation-architecture only feature.
81 -{{/info}}
82 -)))
83 -
84 -(((
85 -{{toc/}}
86 -)))
71 +~*~* Indicates a GEN3-only feature.
72 +{{/info}})))((({{toc/}}))){{/container}}
87 87  {{/container}}
88 -{{/container}}