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
+19-4
Original file line number
Diff line number
Diff line change
@@ -12,16 +12,25 @@ Open-Sourced community contributed and owned repository for Instance Scan Defini
12
12
13
13
## Category: Manageability
14
14
15
+
### Inactive user check: Approvals
16
+
Check any approvals waiting in inactive users queue
17
+
18
+
### Inactive user check: Catalog task Assigned To
19
+
Check any Catalog Tasks Assigned to Inactive user
20
+
15
21
### Check any assets assigned to inactive user
16
22
Check if any asset is assigned to inactive users.
17
23
18
24
### Check if any incidents are assigned to inactive users.
19
25
Check if any incidents are assigned to inactive user.
20
26
21
-
### Inactive User Check: Catalog Item
27
+
### Inactive User Check: Catalog Item
22
28
We should ensure that inactive users are removed from being assigned as Catalog item owners.
23
29
24
-
###Avoid gs.log()Statement
30
+
### Check problem ticket assigned to inactive user
31
+
Make sure that a problem ticket is not assigned to an inactive user.
32
+
33
+
### Avoid gs.log() Statement
25
34
Use Logging Levels: Instead of gs.log(), consider using more appropriate logging levels, such as:
26
35
gs.info() for informative messages.
27
36
gs.warn() for warnings that don’t break functionality but may need attention.
@@ -173,6 +182,11 @@ Tickets from tables such as Incident, Change Request, Problem, and other task-re
173
182
### Check Inactive Business Rules over 90 days
174
183
Inactive Business Rules which are not updated for more than 90 days and not created by glide.maint and not updated by admin should be identified to remove unnecessary overhead.
175
184
185
+
### Update set In Progress/Completed previously Ignored
186
+
Usually, developers mark an updatesets as Ignore if the work done is not required to be promoted or incorrect or irrelavent or due to any other reasons.
187
+
However, at times, some of the developers may use the ignored set for any active work instead of creating new one by updating the state from Ignore to In-Progress. It is not a good practice to do the same. It may case the deployment issues and also makes the troubleshooting process cumbersome.
188
+
It may also impact the deployment and cause issues in case if the state is changed to In-Progress/Completed for the potential ignored sets.
189
+
176
190
## Category: Upgradability
177
191
178
192
### Call GlideRecord using new
@@ -277,7 +291,8 @@ Select the check box to ignore flushing some server-side caches, thus flushing o
277
291
Avoid using gs.sleep() in any script because it does not release session and will cause delays, and add logs to the script whenever gs.sleep() has to be used.
278
292
279
293
## Category: Security
280
-
##Check Mandatory fields on incident
294
+
295
+
### Check Mandatory fields on incident
281
296
This check is used to find mandatory fields on incident
282
297
283
298
### Avoid using setBasicAuth for REST messages
@@ -346,7 +361,7 @@ Scripts in ACLs ARE executed regardless of whether or not the Advanced checked b
346
361
### Added a Number Prefix which already exists
347
362
Creating new number records does not require uniqueness. Though having duplicate number records causes some ServiceNow core functionality not to behave as expected. For example, the search might return a record from another table the number prefix is also used on.
348
363
349
-
## List Inactive users from active group
364
+
###List Inactive users from active group
350
365
List inactive users that still belongs to activate groups
351
366
352
367
### HTTP connection records not excluded on clones from Prod
<description>Usually, developers mark an updatesets as Ignore if the work done is not required to be promoted or incorrect or irrelavent or due to any other reasons.
11
+
However, at times, some of the developers may use the ignored set for any active work instead of creating new one by updating the state from Ignore to In-Progress. It is not a good practice to do the same. It may case the deployment issues and also makes the troubleshooting process cumbersome.
12
+
It may also impact the deployment and cause issues in case if the state is changed to In-Progress/Completed for the potential ignored sets.</description>
13
+
<documentation_url/>
14
+
<finding_type>scan_finding</finding_type>
15
+
<name>Update set In Progress/Completed previously Ignored</name>
16
+
<priority>3</priority>
17
+
<resolution_details>It is always good and recommended to create a new updateset instead of using already Ignored updatesets by changing the state from Ignore to In-Progress/Completed.</resolution_details>
0 commit comments