How petroskyluke/servicenow-health-check works
This repository provides two ServiceNow health-check workflows: a configurable scan of customized application code, and a separate ATF test for VIT risk-score and rating data. The scan selects application records, filters them using customer-update evidence, checks for configured code patterns and scheduled-job risks, and prints prioritized findings. The ATF steps validate configuration and then check population, values, consistency, and distribution through a shared read-only helper. The scan’s implementation is sampled only in excerpts; its documented capabilities are retained, but uncertain internal wiring is omitted.
Main entry points: USEM_HC_ApplicationHealthScan.js Scope scan · VRRiskDataHealth.js Risk health helper · steps Five check steps
Components 12
Application scan
- Scope scan
Scripts/USEM_HC_ApplicationHealthScan.js - Prioritized findings
Scripts/USEM_HC_ApplicationHealthScan.js
VIT risk checks
- Five check steps
Scripts/ATF/steps - Risk health helper
Scripts/ATF/VRRiskDataHealth.js - Check results
Scripts/ATF/VRRiskDataHealth.js
ServiceNow platform
- Application records
- Customer updates
- Version metadata
- User records
- VIT records
Other components
- Administrator
- ATF runner
Connections 11
- Administrator → Scope scan: runs
- Scope scan → Application records: queries scopes and code
- Scope scan → Customer updates: checks customer changes
- Scope scan → Version metadata: classifies origin
- Scope scan → User records: checks run-as users
- Scope scan → Prioritized findings: prints report
- ATF runner → Five check steps: executes
- Five check steps → Risk health helper: runs check
- Risk health helper → VIT records: aggregates read-only
- Risk health helper → Check results: returns pass or fail
- Check results → Five check steps: supplies result