Skip to content

Commit 80b57ff

Browse files
authored
Empty recipients for active notification (#96)
* Update README.md Manageability: active notification without any recipients * Active notification without any class of recipients There is an issue when active notifications with some condition doesn't specify any recipients class: Users | recipient_users Users/Groups in fields | recipient_fields Groups | recipient_groups
1 parent 5c254d3 commit 80b57ff

File tree

2 files changed

+48
-0
lines changed

2 files changed

+48
-0
lines changed

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -127,6 +127,14 @@ Finds integration users that have assigned admin role - there are two types:
127127
Already completed Update Set shouldn't be set back to In Pogress
128128
There is risk that even for a moment completed update set were retrieved to higher environment and won't be retrieved once again after more modifications are done on lower environment
129129

130+
### Active notifications with empty any recipients class
131+
For notification records there are condition to be met, active flag - they indicates that some notificaton should reach recipients
132+
It happens from time to time that after development or conifguration all the three classes of recpients can be empty:
133+
- Users | recipient_users
134+
- Users/Groups in fields | recipient_fields
135+
- Groups | recipient_groups
136+
It can cause except issue with manageability also some performance impact - to verify active notification against some conditions and at the end no notification produced
137+
130138
## Category: Upgradability
131139

132140
### Call GlideRecord using new
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<unload unload_date="2023-10-18 10:10:47">
3+
<scan_table_check action="INSERT_OR_UPDATE">
4+
<active>true</active>
5+
<advanced>false</advanced>
6+
<category>manageability</category>
7+
<conditions table="sysevent_email_action">active=true^recipient_usersISEMPTY^recipient_fieldsISEMPTY^recipient_groupsISEMPTY^EQ<item goto="false" or="false" field="active" endquery="false" value="true" operator="=" newquery="false"/>
8+
<item goto="false" or="false" field="recipient_users" endquery="false" value="" operator="ISEMPTY" newquery="false"/>
9+
<item goto="false" or="false" field="recipient_fields" endquery="false" value="" operator="ISEMPTY" newquery="false"/>
10+
<item goto="false" or="false" field="recipient_groups" endquery="false" value="" operator="ISEMPTY" newquery="false"/>
11+
<item goto="false" or="false" field="" endquery="true" value="" operator="=" newquery="false"/>
12+
</conditions>
13+
<description/>
14+
<documentation_url/>
15+
<finding_type>scan_finding</finding_type>
16+
<name>Active notification without any recipients</name>
17+
<priority>3</priority>
18+
<resolution_details/>
19+
<run_condition/>
20+
<score_max>100</score_max>
21+
<score_min>0</score_min>
22+
<score_scale>1</score_scale>
23+
<script/>
24+
<short_description>Neither of recipients class is specified</short_description>
25+
<sys_class_name>scan_table_check</sys_class_name>
26+
<sys_created_by>admin</sys_created_by>
27+
<sys_created_on>2023-10-18 10:09:08</sys_created_on>
28+
<sys_id>dcc8978c2f4a7110b0b62d5df699b603</sys_id>
29+
<sys_mod_count>1</sys_mod_count>
30+
<sys_name>Active notification without any recipients</sys_name>
31+
<sys_package display_value="Global" source="global">global</sys_package>
32+
<sys_policy/>
33+
<sys_scope display_value="Global">global</sys_scope>
34+
<sys_update_name>scan_table_check_dcc8978c2f4a7110b0b62d5df699b603</sys_update_name>
35+
<sys_updated_by>admin</sys_updated_by>
36+
<sys_updated_on>2023-10-18 10:09:26</sys_updated_on>
37+
<table>sysevent_email_action</table>
38+
<use_manifest>false</use_manifest>
39+
</scan_table_check>
40+
</unload>

0 commit comments

Comments
 (0)