Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:49
From version 11.1
edited by Erik Bakker
on 2022/08/30 09:51
Change comment: There is no comment for this version
To version 9.1
edited by Erik Bakker
on 2022/08/30 09:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,16 +14,15 @@
14 14  
15 15  === 3.1 Scenario's when to cleanup the Alerting phase ===
16 16  
17 -* A user is no longer active on the integration model.
18 - ** The user may still be referenced in the notification settings and should be removed
17 +* A user is no longer active on the integration model. The use may still be referenced in the notification settings and should be removed
19 19  * A specific runtime is removed from the integration model that is referenced in the Alerting
20 20  * A flow or integration is removed from the integration model that is reference in the Alerting
21 21  
22 22  === 3.1 Steps to clean ===
23 23  
24 -Once you have opened your model you should navigate to the Manage environment. From here you should open the Alerting section under Manage and select Triggers. Here you can change the relevant triggers.
23 +Navigate to the Triggers first.
25 25  
26 -**Queue specific**
25 +**Locate Queue specific**
27 27  
28 28  If you have configured the alerting following the best practice outlined in the user guide for Alerting, the following triggers (at least!!!) need to be changed. For your specific situation more triggers could be relevant
29 29  
... ... @@ -30,7 +30,7 @@
30 30  * Standard – Queue consumers too high
31 31  * Standard – Queue consumers too low
32 32  
33 -**Runtime specific**
32 +**Locate Runtime specific**
34 34  
35 35  If you are removing the last flow belonging to a system and you have followed the best practice outlined here the following triggers (at least!!!) need to be changed. For your specific situation more triggers could be relevant
36 36