Skip to Content

Changes for page 217 - Template Tango

Last modified by CarlijnKokkeler on 2024/04/23 12:06
From version 114.1
edited by Erik Bakker
on 2023/05/09 13:41
Change comment: There is no comment for this version
To version 411.1
edited by CarlijnKokkeler
on 2024/03/25 10:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +217 - Template Tango
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,68 +1,56 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
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.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **Event streaming alerting** ==
8 +== **Cloud Template R12 Docker - Single Lane** ==
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 +== **Cloud Template R14 Docker - Double Lane** ==
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 +== **Feedback Items** ==
13 +//__Improved event streaming graph__//
14 +The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic.
12 12  
13 -The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
16 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-topics-2.png]]
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
18 +//__Flow versions auto deletion__//
19 +Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available.
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.
21 +== **Bug Fixes** ==
22 +//__Queue name validation__//
23 +The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
25 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
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.
27 +//__Removal of onramp__//
28 +An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
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"]].
30 +//__eMagiz login__//
31 +In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field.
24 24  
25 -== **3rd generation improvements** ==
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.
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.
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.
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.
38 -
39 -== **Feedback items ** ==
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.
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.
46 -
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"]]
37 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
38 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
39 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
40 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
41 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
53 53  
54 -== **Key takeaways** ==
43 +== **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:
45 +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.
49 +* 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
64 64  * Start thinking about major, minor, and patch
65 -* Upgrade to the latest build number
66 66  * Keep making great integrations
67 67  
68 68  Let's stay in touch and till next time!
... ... @@ -70,6 +70,11 @@
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.
74 -{{/info}})))((({{toc/}}))){{/container}}
61 +{{/info}}
62 +)))
63 +
64 +(((
65 +{{toc/}}
66 +)))
75 75  {{/container}}
68 +{{/container}}