|
3 | 3 | <active>true</active>
|
4 | 4 | <advanced>true</advanced>
|
5 | 5 | <category>manageability</category>
|
6 |
| - <conditions table="incident">active=true^EQ<item endquery="false" field="active" goto="false" newquery="false" operator="=" or="false" value="true"/> |
| 6 | + <conditions table="incident">active=true^assignment_group=^EQ<item endquery="false" field="active" goto="false" newquery="false" operator="=" or="false" value="true"/> |
| 7 | + <item endquery="false" field="assignment_group" goto="false" newquery="false" operator="=" or="false" value=""/> |
7 | 8 | <item endquery="true" field="" goto="false" newquery="false" operator="=" or="false" value=""/>
|
8 | 9 | </conditions>
|
9 | 10 | <description>Tickets from tables such as Incident, Change Request, Problem, and other task-related tables should always have an Assignment Group specified. These tickets represent issues or requests that require attention and action. Leaving the Assignment Group field empty can result in unresolved issues or delays in implementing fixes, as no team will be accountable for the resolution. Since the Assignment Group is meant to designate the responsible team for managing these tickets, it should never be left blank.</description>
|
|
17 | 18 | <score_min>0</score_min>
|
18 | 19 | <score_scale>1</score_scale>
|
19 | 20 | <script><![CDATA[(function(finding, current) {
|
20 |
| - var IncID = current.getValue('sys_id'); |
21 |
| - var inc = new GlideRecord('incident'); |
22 |
| - inc.addQuery('sys_id', IncID); |
23 |
| - inc.addEncodedQuery("assignment_group!=null"); |
24 |
| - if (!inc.hasNext()) { |
25 |
| - finding.increment(); |
26 |
| - } |
| 21 | + //var IncID = current.getValue('sys_id'); |
| 22 | + // var inc = new GlideRecord('incident'); |
| 23 | + // inc.addQuery('sys_id', IncID); |
| 24 | + // inc.addEncodedQuery("assignment_group!=null"); |
| 25 | + // if (!inc.hasNext()) { |
| 26 | + // finding.increment(); |
| 27 | + // } |
| 28 | + //if(current.assignment_group!=null){ |
| 29 | + finding.increment(); |
| 30 | + //} |
27 | 31 | })(finding, current);]]></script>
|
28 | 32 | <short_description>Tickets from Incident table should have assignment group specified.</short_description>
|
29 | 33 | <sys_class_name>scan_table_check</sys_class_name>
|
30 | 34 | <sys_created_by>admin</sys_created_by>
|
31 | 35 | <sys_created_on>2024-10-07 18:22:05</sys_created_on>
|
32 | 36 | <sys_id>7334dda283455210ae0854b6feaad378</sys_id>
|
33 |
| - <sys_mod_count>9</sys_mod_count> |
| 37 | + <sys_mod_count>12</sys_mod_count> |
34 | 38 | <sys_name>Check for Orphaned tickets</sys_name>
|
35 | 39 | <sys_package display_value="Example Instance Checks" source="x_appe_exa_checks">ca8467c41b9abc10ce0f62c3b24bcbaa</sys_package>
|
36 | 40 | <sys_policy/>
|
37 | 41 | <sys_scope display_value="Example Instance Checks">ca8467c41b9abc10ce0f62c3b24bcbaa</sys_scope>
|
38 | 42 | <sys_update_name>scan_table_check_7334dda283455210ae0854b6feaad378</sys_update_name>
|
39 | 43 | <sys_updated_by>admin</sys_updated_by>
|
40 |
| - <sys_updated_on>2024-10-07 18:33:38</sys_updated_on> |
| 44 | + <sys_updated_on>2024-10-09 06:30:13</sys_updated_on> |
41 | 45 | <table>incident</table>
|
42 | 46 | <use_manifest>false</use_manifest>
|
43 | 47 | </scan_table_check>
|
|
0 commit comments