Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40

From version 144.1
edited by Erik Bakker
on 2023/08/15 10:23
Change comment: There is no comment for this version
To version 592.1
edited by CarlijnKokkeler
on 2024/07/16 11:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -203 - Fast Paced
1 +225 - TBD
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,46 +1,43 @@
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 processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **Release Properties - Early Feedback** ==
8 -The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
9 9  
10 10  == **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.
11 11  
12 -//__"All entries" are now cleaned up as part of the migration__//
13 -To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
13 +[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
14 14  
15 -//__Trigger ID added to our alerting on the next-generation architecture__//
16 -We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
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.
17 17  
18 18  == **Bug Fixes** ==
19 19  
20 -//__Ensure no flow can be in a release twice__//
21 -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.
22 22  
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.
25 25  
22 +
23 +
26 26  == **Fancy Forum Answers** ==
27 27  
28 28  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:
29 29  
30 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
28 +* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
31 31  
32 -== **Key takeaways** ==
30 +== **Key Takeaways** ==
33 33  
34 -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:
32 +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:
35 35  
36 36  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
37 37  * If you have feedback or ideas for us, talk to the Platypus
38 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
36 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
39 39  * Clear your browser cache (Ctrl + Shift + Del)
40 -* Check out the release notes [here]
38 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
41 41  * Start thinking about how the license tracker can aid your development
42 42  * Start thinking about major, minor, and patch
43 -* Upgrade to the latest build number
44 44  * Keep making great integrations
45 45  
46 46  Let's stay in touch and till next time!
... ... @@ -48,6 +48,11 @@
48 48  {{info}}
49 49  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
50 50  
51 -~*~* Indicates a next-generation-architecture only feature.
52 -{{/info}})))((({{toc/}}))){{/container}}
48 +{{/info}}
49 +)))
50 +
51 +(((
52 +{{toc/}}
53 +)))
53 53  {{/container}}
55 +{{/container}}