Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 594.1
edited by CarlijnKokkeler
on 2024/07/16 12:01
Change comment: There is no comment for this version
To version 148.1
edited by Erik Bakker
on 2023/08/15 13:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - TBD
1 +203 - Fast Paced
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,54 +1,49 @@
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!**
5 +**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
7 7  
7 +== **Release Properties - Early Feedback** ==
8 +The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
8 8  
9 9  == **Feedback Items** ==
10 -//__Alerting notification settings__//
11 -The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
12 +//__"All entries" are now cleaned up as part of the migration__//
13 +To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
14 14  
15 -//__Process containers__//
16 -If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
15 +//__Trigger ID added to our alerting on the next-generation architecture__//
16 +We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
17 17  
18 -//__Design settings__//
19 -When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
18 +//__Improved performance Manage Dashboards__//
19 +We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture.
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
22 -
23 -//__Untested images__//
24 - A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.
25 -
26 -PICTURE
27 -
28 -
29 29  == **Bug Fixes** ==
30 30  
23 +//__Ensure no flow can be in a release twice__//
24 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
31 31  
26 +//__Sped up adding a new operation to the API Gateway solution__//
27 +We have fixed a bug that slowed down the addition of new operations to the API Gateway solution.
32 32  
33 -
34 -
35 35  == **Fancy Forum Answers** ==
36 36  
37 37  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:
38 38  
39 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
33 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
40 40  
41 -== **Key Takeaways** ==
35 +== **Key takeaways** ==
42 42  
43 -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:
37 +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:
44 44  
45 45  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
46 46  * If you have feedback or ideas for us, talk to the Platypus
47 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
41 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
48 48  * Clear your browser cache (Ctrl + Shift + Del)
49 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
43 +* Check out the release notes [here]
50 50  * Start thinking about how the license tracker can aid your development
51 51  * Start thinking about major, minor, and patch
46 +* Upgrade to the latest build number
52 52  * Keep making great integrations
53 53  
54 54  Let's stay in touch and till next time!
... ... @@ -56,11 +56,6 @@
56 56  {{info}}
57 57  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
58 58  
59 -{{/info}}
60 -)))
61 -
62 -(((
63 -{{toc/}}
64 -)))
54 +~*~* Indicates a next-generation-architecture only feature.
55 +{{/info}})))((({{toc/}}))){{/container}}
65 65  {{/container}}
66 -{{/container}}