Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 115.1
edited by Erik Bakker
on 2023/05/09 13:42
Change comment: There is no comment for this version
To version 242.1
edited by Carlijn Kokkeler
on 2023/11/21 11:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,62 +2,76 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving our next-generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore, several smaller feedback items and bugs have been resolved with this release. So without further ado, let us dive into all we have to offer.
5 +**Hi there, eMagiz developers!** We have done .....
6 6  
7 -== **Event streaming alerting** ==
7 +== **Next Generation Architecture Default** ==
8 +With this release, the next generation architecture will become the default. New models will use this generation as default.
8 8  
9 -This release expands our alerting functionality into the event streaming pattern. As of now, one new "static" alert has been introduced for all clients (using event streaming), and two "dynamic" alerts have been introduced that you can configure yourself if there is a need for it.
10 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
10 10  
11 -The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights into whether messages on it are deleted due to a size or time constraint. In cases where data is deleted, the topic was too full way before the messages should have been removed due to the retention hours constraint. This alert can indicate that messages might be deleted before consumer groups had the option to consume the messages.
12 +== **Cloud Template R11 - Single Lane** ==
13 +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
12 12  
13 -The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
15 +== **Cloud Template R13 - Double Lane** ==
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
16 16  
17 -The first new "dynamic" alert allows you to raise an alert once the number of messages on one (or more topics) is less than a certain number per defined time unit. So, for example, you can configure an alert once the number of messages placed on a topic called "Exception" is less than 15 messages within 5 minutes.
18 +== **Feedback Items** ==
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
20 +//__Unused properties overview__//
21 +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:
22 +* Not used by any runtime that is in the Create phase release.
23 +* Not required by a flow that is in the Create phase release.
24 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
20 20  
21 -The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups are more than X messages behind on one or more topics. The configuration of this is comparable to what we saw before.
26 +//__Send build requests asynchronously__//
27 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
22 22  
23 -For more information on the generic way of working surrounding alerting, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
29 +//__Queue explorer milliseconds__//
30 +The queue browser now displays milliseconds in the timestamps.
24 24  
25 -== **3rd generation improvements** ==
32 +//__Cancel and next buttons order__//
33 +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.
26 26  
27 -//__Increased grace period for shutdown__//
28 -In this release, we have increased a container's grace period to shut down before it is forcefully shut down. This should reduce the chance of unwanted failover behavior within your model.
35 +//__Unused images__//
36 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
29 29  
30 -//__Update at once or not__//
31 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
38 +//__Carwash logging__//
39 +A new logging feature enabling us to make better choices in encryption standards will be released.
32 32  
33 -//__Improved user feedback while executing a deployment plan__//
34 -This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information about why this cannot be executed is shown to the user. This way, they can take this information and act upon it instead of assuming everything went well.
41 +//__Static alerts queue consumers__//
42 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
35 35  
36 -//__Improved auto-healing when running in a hybrid situation__//
37 -In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
44 +== **Bug Fixes** ==
38 38  
39 -== **Feedback items ** ==
46 +//__Images rebuild__//
47 +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.
40 40  
41 -//__Make sure the message format can be viewed without "Start editing"__//
42 -With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
49 +//__Flow Designer connection line__//
50 +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 43  
44 -//__Various styling improvements in the flow testing functionality__//
45 -Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
52 +//__Portal for migrated models__//
53 +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.
46 46  
55 +//__Error channel inbounds__//
56 +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.
57 +
47 47  == **Fancy Forum Answers** ==
48 48  
49 49  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:
50 50  
51 -* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
52 -* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
62 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
63 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
64 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
65 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
53 53  
67 +
54 54  == **Key takeaways** ==
55 55  
56 -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:
70 +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:
57 57  
58 58  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
59 59  * If you have feedback or ideas for us, talk to the Platypus
60 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
74 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
61 61  * Clear your browser cache (Ctrl + Shift + Del)
62 62  * Check out the release notes [here]
63 63  * Start thinking about how the license tracker can aid your development
... ... @@ -70,6 +70,6 @@
70 70  {{info}}
71 71  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
72 72  
73 -~*~* Indicates a GEN3-only feature.
87 +~*~* Indicates a next-generation-architecture only feature.
74 74  {{/info}})))((({{toc/}}))){{/container}}
75 75  {{/container}}