Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 630.1
edited by CarlijnKokkeler
on 2024/07/29 12:34
Change comment: There is no comment for this version
To version 534.1
edited by CarlijnKokkeler
on 2024/05/29 10:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -226 - Alerting Alchemy
1 +221 - Swift Shift
Content
... ... @@ -3,41 +3,53 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release,
6 +**Hi there, eMagiz developers!** In this release, we improved the user interface for managing your failover and grouping configurations and improved the method for adding new attributes to data models. Next to this, we have improved the Event Catalog overview for Catalog users. Using the back button on the eMagiz Q&A now also brings you back to where you were with your search query. We also fixed some previous bugs, resulting in improved delete behavior for containers and correctly generated scope properties. Lastly, there will not be a warning message anymore when importing an XSD if there is no selected request or response message definition.
7 7  
8 8  == **Feedback Items** ==
9 -//__Queue alerting__//
10 -Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, which includes the following improvements:
11 -* New UI that shows all queues and the alerting that is active on them.
12 -* Every queue in the model will be automatically added to the list of queues in Manage - Alerting.
13 -* Triggers of a queue will be automatically enabled or disabled based on whether that queue is included in the release.
14 -* Added 2 new trigger types "inactivity check" and "periodic activity check" that replace the "queue throughput" alert.
15 -** These checks can now run for a (very) long time, whereas the "queue throughput" was limited by 1 hour.
16 -* The alert generation has been solidified to reduce the likelihood that your alerting is affected with false positives or false negatives during eMagiz maintenance.
17 -* When the same check of multiple queues trigger at the same time, the alerts will be aggregated into a single summarized email instead of a single email per alert.
9 +//__Q&A search__//
10 +Search results are now persisted when pressing the back button after opening a question in the community Q & A.
18 18  
19 -If your model is running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, you will be migrated on the day of release. eMagiz will transfer the queue alerts that you have currently configured to the closest match in the new alerting stack. Models that are in the process of migrating to the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture during the time of the release of this feature will be able to pre-configure their new queue alert triggers, but will not be able to make active use of them until the runtime migration has finished.
12 +//__Event catalog__//
13 +For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
20 20  
21 -{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
15 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
22 22  
23 -//__Tenant technical name__//
24 - The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
17 +//__Attribute placements__//
18 +Some improvements regarding the placement of attributes have been done:
19 +* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute.
20 +* For system message definition, moving an attribute in the data model is now directly reflected in the tree structure as well. However for CDM, API Gateway, and EVS Data Model, moving an attribute will not be directly reflected in the tree structure. A pop-up confirmation, as shown below, will appear with respect to the type of message definition (i.e., system message or CDM) that the user is working with.
21 +* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype.
25 25  
26 -//__Tenant transfer__//
27 -A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
23 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
28 28  
29 -//__Property placeholder__//
30 -A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
25 +//__Failover & grouping__//
26 +Some improvements regarding the widgets for failover and grouping have been done:
27 +* When executing a start/stop action on a group, the description of the step now contains the name of the group.
28 +* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
31 31  
30 +[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
31 +
32 +[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
33 +
32 32  == **Bug Fixes** ==
35 +//__XSD import__//
36 +When importing an XSD to a new or empty response or request message, you will not receive a warning message anymore to avoid confusion.
33 33  
38 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
39 +
40 +//__Container deletion__//
41 +The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
42 +
43 +//__Scope properties__//
44 +We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.
45 +
34 34  == **Fancy Forum Answers** ==
35 35  
36 36  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:
37 37  
38 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
39 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
40 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
50 +* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
51 +* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
52 +* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
41 41  
42 42  == **Key Takeaways** ==
43 43  
... ... @@ -47,7 +47,7 @@
47 47  * If you have feedback or ideas for us, talk to the Platypus
48 48  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49 49  * Clear your browser cache (Ctrl + Shift + Del)
50 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
51 51  * Start thinking about how the license tracker can aid your development
52 52  * Start thinking about major, minor, and patch
53 53  * Keep making great integrations