You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,7 +100,7 @@ Variables should be used in Catalog Item or a Variable Set. Variables not in us
100
100
### Delete Orphaned Catalog Client Scripts
101
101
Catalog Client Script should be used in either a Catalog Item or a Variable Set. Catalog Client Scripts not in use should be deleted.
102
102
103
-
### Update set description should not be empty
103
+
### Delete Orphaned Catalog UI Policies
104
104
Catalog UI policy should be used in either a Catalog Item or a Variable Set. Catalog UI Policies not in use should be deleted.
105
105
106
106
### Client Script Business rule or Script Include should not have an empty description or be without comments in the script section
@@ -146,6 +146,9 @@ During the time it can be a situation that person is no longer active in the sys
146
146
### Unsupported API GlideLDAP
147
147
GlideLDAP API usage is unsupported by ServiceNow and hence should be avoided, rather use LDAP Server Data Sources to pull data from LDAP via MID Server or directly through an internet facing LDAP.
148
148
149
+
### Check for Orphaned Tickets
150
+
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 not be left blank.
151
+
149
152
150
153
## Category: Upgradability
151
154
@@ -306,6 +309,9 @@ In general, variables in JavaScript should be properly declared (e.g. using “v
306
309
### Don't show unpublished knowledge articles
307
310
Unpublished knowledge articles may contain sensitive information that should not be visible to anyone with read access. By preventing access to unpublished articles, reviewers are given the opportunity to verify the content before it is made accessible. This ensures that only properly reviewed and approved information is available to users with read access.
308
311
312
+
### Scripts in ACLs should be cleared when Advanced is not checked
313
+
Scripts in ACLs ARE executed regardless of whether or not the Advanced checked box is checked off. As such, unnecessary scripts should be cleared from the field OR the Advanced checkbox should be checked in cases where scripts are required to provide better visibility to admins for troubleshooting purposes.
314
+
309
315
## Category: User Experience
310
316
311
317
### Added a Number Prefix which already exists
@@ -325,6 +331,9 @@ It is recommended to use an OOB library for modals in order to improve the user
325
331
### Use "last run datetime" for JDBC data loads
326
332
In your JDBC data load configuration, ensure that the 'last run datetime' option is set to true and configure the target database field to serve as a timestamp, as this best practice enables incremental data loading and improves performance in data integration processes using JDBC.
327
333
334
+
### Use of setWorkflow(false) in business rules will cause unexpected issues
335
+
As setWorkflow(false) method will stop the execution of business rules on that particular GlideRecord object, this will result in unexpected behaviour where the execution of business rules skipped. Maintain caution while using this method and perform regression testing to avoid possible risk. It can have noticeable impact on Audit, Journal fields, notifications, SLA engine, workflow, flow engine etc.,
336
+
328
337
# Additional resources
329
338
330
339
Please check these additional links for more information and details:
<description>The Choice table should not be used as the reference table for a Reference type field. Reference fields store the sys_id of the corresponding record in the reference table and show the specified display value. For example: the caller_id field stores the sys_id of a record from the user table and displays the corresponding name value. This presents a problem when using the sys_choice table, because existing records are deleted and replaced when choices are modified. This causes a new sys_id to be generated for each record in the choice list. So the sys_id stored in the Reference field is no longer a valid value and the reference is broken.</description>
<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>
10
+
<documentation_url/>
11
+
<finding_type>scan_finding</finding_type>
12
+
<name>Check for Orphaned tickets</name>
13
+
<priority>2</priority>
14
+
<resolution_details>Identify the records with emopty assignment group and assign them to respective assignment groups so that they can work on the tickets and to further prevent it try creating assignment lookup rules</resolution_details>
15
+
<run_condition/>
16
+
<score_max>100</score_max>
17
+
<score_min>0</score_min>
18
+
<score_scale>1</score_scale>
19
+
<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
+
}
27
+
})(finding, current);]]></script>
28
+
<short_description>Tickets from Incident table should have assignment group specified.</short_description>
<description>Scripts in ACLs ARE executed regardless of whether or not the Advanced checked box is checked off. As such, unnecessary scripts should be cleared from the field OR the Advanced checkbox should be checked in cases where scripts are required to provide better visibility to admins for troubleshooting purposes.</description>
0 commit comments