HealthScan definitions updates: November 2024 release
Some HealthScan definitions are deprecated or updated between releases.
Deprecated definitions
The following definitions have been deprecated for the November 2024 release.
| Number | Short description | Rating | Related portfolio | Category | Reason for deprecation |
|---|---|---|---|---|---|
| HSD0004695 | Ensure gamification ranges do not overlap and have a unique start value. | Recommend | Configuration Review for CSM | Manageability | Merged with HSD0004987 |
Updated definitions
The following definitions have been updated for the November release to improve performance, reduce false positives, and meet the latest coding practices. Some of these definitions will have a positive or negative impact on your customer instance scores.
Due to process and technical constraints, a comprehensive impact analysis for the overall score impact could not be fully conducted for customer instances. As a result, there may be potential impact score drops that have not been identified or addressed.
| Number | Short description | Rating | Category | Update description |
|---|---|---|---|---|
| HSD0001041 | Customer accounts without primary contact | Discuss | Manageability | - Improved code to follow HealthScan definition guidelines - Documentation link update |
| HSD0001058 | Scoped app uses logging utils or deprecated methods for logging rather than the verbosity method | Act | Manageability | - Improved performance with more reliance on the database to filter records - Accurate line numbers - Reduced number of false positives |
| HSD0001128 | Client-side code should not use synchronous AJAX methods | Recommend | Performance | - Added query for catalog and client scripts: type!=onSubmit - Implemented updated line numbering and comment handling - Added try/catch to ensure better stability |
| HSD0001193 | Use the condition field in Business Rules | Discuss | Manageability | Modified the initial query to include "Script not empty" and "when" conditions and removed it from the detailed analysis part of the HSD code |
| HSD0001459 | Missing key contact details - Email or Account | Discuss | Manageability | - Improved code to follow HealthScan definition guidelines - Valid documentation link update |
| HSD0001475 | Entitlements without duration \(start and end date\) | Discuss | Manageability | - Improved code to follow HealthScan definition guidelines - Valid documentation link update |
| HSD0001484 | Missing Asset Information - Primary Contact or Location | Discuss | Manageability | - Improved code to follow HealthScan definition guidelines - Valid documentation link update |
| HSD0001507 | A dedicated integration user runs actions in place of the default admin user | Act | Security | - Corrected typo leading all queries on this to fail and return all records - Filtered out tables that don't have a user field available on the form view - Filtered out baseline records - Added query to return the jobs running as admin \(without a user value\) - Added display on Findings to make this distinction clear - Added 1k Findings limit |
| HSD0001533 | The default "system" user preference for "rows per page" should be set to 50 or less | Recommend | Performance | - Replaced documentation URL - Always creates a statistic - Added defensive scripting |
| HSD0001623 | Read ACLs \(Security rules\) should not have GlideRecord, GlideAggregate, or GlideRecordSecure in script | Act | Performance | - Improved code - Avoided use of ScriptUtils performMatch and search override - Fixed incorrect line numbering - Resolved multiple inquiries - Considered GlideRecordSecure in the findings along with GlideRecord and GlideAggregate |
| HSD0001627 | Do not query audit log in custom integrations and code | Recommend | Performance | - Improved performance with more reliance on the database to filter records - Accurate line numbers - Reduced number of false positives |
| HSD0001662 | Differs from baseline: Business Rules | Recommend | Upgradeability | - Excludes custom applications - Queries for customized business rules from store apps - Resolved multiple inquiries - Improved accuracy and performance - Increased the number of findings - Added findings limit and defensive scripting |
| HSD0001664 | Differs from baseline: Script Includes | Recommend | Upgradeability | - Excludes custom applications - Improved performance by not checking twice for baseline |
| HSD0001665 | Differs from baseline: Client Scripts \(and UI Scripts\) | Recommend | Upgradeability | - Excludes custom applications - Queries for customized client scripts from store apps - Resolved multiple inquiries - Improved accuracy and performance - Increased the number of findings - Added findings limit and defensive scripting |
| HSD0001877 | Customer Contact should not have the snc\_internal role | Act | Manageability | Improved code to follow HealthScan definition guidelines |
| HSD0002056 | Knowledge articles older than 12 months may be unduly aging | Recommend | Manageability | - Added logic to not create the single Finding on zero results - Added try/catch logic - Added Statistical score for visibility on zero |
| HSD0002295 | Service Contracts without duration \(Start and End Date\) | Recommend | Manageability | Improved code to follow HealthScan definition guidelines |
| HSD0002299 | Feature adoption: Automated Case Assignment | Recommend | Manageability | Improved code to follow HealthScan definition guidelines |
| HSD0002300 | CSM Demo Data Plugin Installation | Discuss | Manageability | Improved code to follow HealthScan definition guidelines |
| HSD0002371 | Product Adoption: Use CSM to streamline your Customer Service operations | Discuss | Manageability | - Improved code to follow HealthScan definition guidelines - Changed execution type from Statistical to Automated |
| HSD0002372 | Feature Adoption: Self-registration for customer contacts | Discuss | Manageability | Improved code to follow HealthScan definition guidelines |
| HSD0002437 | Check whether strict mode for GlideRecord queries is active | Recommend | Manageability | Added defensive scripting by means of try/catch/finally structure to ensure a statistic |
| HSD0002534 | Duplicate Cases created with the same number | Discuss | User Experience | - Improved code to follow HealthScan definition guidelines - Restricted Max finding to 75 |
| HSD0002828 | All events should have the "fired by" field populated | Recommend | Manageability | - Returns multiple findings up to a maximum of 1000 - Each finding groups flagged events by application and displays the event count per app - Each finding links to a list page of flagged events for the same application - Returns custom \(rather than OOTB\) events - Defensive scripting in case of table accessibility issues - Statistic is always returned - Statistic represents the cumulative count |
| HSD0003784 | Check for unhandled duplicate CI tasks | Discuss | User Experience | - Added defensive scripting by means of try/catch/finally structure to ensure a statistic - Added check for short\_description field exists - Migrated to GlideAggregrate for overall count - Added 30 days filter to Findings - Added 1000 Findings limit |
| HSD0004419 | Deactivate stale user accounts | Recommend | Manageability | - Returns finding if 1 or more inactive users are found - Always returns statistic - Filters out users created less than 1 month ago - Defensive scripting in case of issues with tables |
| HSD0004672 | Every Knowledge Base should have Knowledge Manager populated | Recommend | User Experience | - Improved code to follow HealthScan definition guidelines - Fixed spelling errors |
| HSD0004689 | Enables session caching. | Recommend | User Experience | Improved code to follow HealthScan definition guidelines |
| HSD0004690 | Enables the user-mentions functionality in Communities content. | Recommend | User Experience | Improved code to follow HealthScan definition guidelines |
| HSD0004692 | Enables Google re-CAPTCHA on the self-registration page with Communities | Recommend | Security | Improved code to follow HealthScan definition guidelines |
| HSD0004693 | Enable Gamification on Community | Recommend | User Experience | Improved code to follow HealthScan definition guidelines |
| HSD0004974 | Check if system property sn\_customerservice.consumer\_max\_new\_cases\_daily has been modified for consumer Cases per day | Recommend | Manageability | Improved code to follow HealthScan definition guidelines |
| HSD0004987 | Ensure gamification has a unique level range name, that gamification ranges do not overlap, and have a unique start value. | Recommend | Manageability | Improved code to follow HealthScan definition guidelines |
| HSD0005255 | Regression testing for ATF Quick Start Test "Major Issue Management" | Recommend | Upgradeability | Improved code to follow HealthScan definition guidelines |
| HSD0006666 | Check if current.update\(\) is used in a business rule | Act | Performance | - Improved code to follow HealthScan definition guidelines - Resolved multiple inquiries - Rectified incorrect line numbering |
| HSD0011774 | Hardware Models should have Manufacturer and Model Number | Recommend | Manageability | Added a check: If there are 0 models, do not create a finding |
| HSD0012251 | Hardware Asset Tags are unique | Discuss | Manageability | - Updated documentation URL to the latest playbook - Removed finding when there are 0 duplicate asset tags |
| HSD0014977 | GlideRecord.insert\(\) method should check for Null | Recommend | Manageability | - Updated definition with latest comment handling - Added try/catch - Many performance improvements |
Parent Topic:HealthScan definitions