Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 112.1
edited by Erik Bakker
on 2023/05/09 12:45
Change comment: There is no comment for this version
To version 543.1
edited by CarlijnKokkeler
on 2024/06/03 13:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +222 - Flee Frustration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,83 +1,59 @@
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 work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
6 +**Hi there, eMagiz developers!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to read about the details and the rest of our bug fixes!
6 6  
7 -== **Event streaming alerting** ==
8 +== **Feedback Items** ==
9 +//__Cron triggers__//
10 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
8 8  
9 -With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it.
12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.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 whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication that messages might be deleted before consumer groups had the option to consume the messages.
14 +//__Design changes__//
15 +If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
12 12  
13 -The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
19 +== **Bug Fixes** ==
20 +//__Trigger activation__//
21 +Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
16 16  
17 -The first new "dynamic" alert allows you to raise an alert once the total 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 message placed on a topic called "Exception" is less than 15 messages within 5 minutes.
23 +//__Multiple users deploying__//
24 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
20 20  
21 -The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
28 +//__Invalid memory configurations__//
29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
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"]].
31 +//__Property value synchronization__//
32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
24 24  
25 -== **3rd generation improvements** ==
34 +//__JMS number__//
35 +The number on the JMS container correctly displays the amount of queues present in Design.
26 26  
27 -//__Event Streaming statistics completion__//
28 -In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
29 29  
30 -//__Deployments on next generation architecture__//
31 -This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
32 -
33 -//__Clean queues option__//
34 -This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
35 -
36 -== **Feedback items ** ==
37 -
38 -//__On-premise containers are started upon slot wakeup__//
39 -With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
40 -
41 -//__Resource path is shown to the user__//
42 -You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
43 -
44 -//__Flow designer improvements__//
45 -With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
46 -
47 -//__Improved capabilities of a company contact__//
48 -With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
49 -
50 -== **Bug fixes ** ==
51 -
52 -//__Optional API parameters are handled correctly__//
53 -Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
54 -
55 -//__Without CDM rights nothing related to any data model can be edited anymore__//
56 -With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
57 -
58 -//__Improved sorting of Design and Deploy archticture__//
59 -With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
60 -
61 61  == **Fancy Forum Answers** ==
62 62  
63 63  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:
64 64  
65 -* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
66 -* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
67 -* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
43 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
68 68  
69 -== **Key takeaways** ==
46 +== **Key Takeaways** ==
70 70  
71 -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:
48 +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:
72 72  
73 73  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74 74  * If you have feedback or ideas for us, talk to the Platypus
75 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
52 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76 76  * Clear your browser cache (Ctrl + Shift + Del)
77 -* Check out the release notes [here]
54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
78 78  * Start thinking about how the license tracker can aid your development
79 79  * Start thinking about major, minor, and patch
80 -* Upgrade to the latest build number
81 81  * Keep making great integrations
82 82  
83 83  Let's stay in touch and till next time!
... ... @@ -85,6 +85,11 @@
85 85  {{info}}
86 86  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
87 87  
88 -~*~* Indicates a GEN3-only feature.
89 -{{/info}})))((({{toc/}}))){{/container}}
64 +{{/info}}
65 +)))
66 +
67 +(((
68 +{{toc/}}
69 +)))
90 90  {{/container}}
71 +{{/container}}