0
2.0.3
Australia, Zurich Patch 3, Yokohama Patch 8
Standalone Application
The Scan Engine is a ServiceNow application designed to automate recommended practice enforcement, manage technical debt, and optimize workflows across ServiceNow environments. It enables administrators and developers to proactively identify, remediate, and track issues through real‑time, on‑demand, and scheduled scans, ensuring continuous improvement in platform health and compliance. Integrated directly into the development lifecycle, it provides real‑time checks within App Engine Studio and script editors to prevent non‑compliant changes before they reach production, while offering intelligent fix suggestions to accelerate resolution.
- Real-Time Compliance: Embedded validations in App Engine Studio and script editors to prevent non-compliant changes during development.
- Expanded Scan Types:
- Instance Scan (Scheduled/On-Demand)
- Full Scan
- Delta Scan
- Update Set Scan
- Application Scan
- Instance Scan (Scheduled/On-Demand)
- Governance Workflows: Exception handling and approval processes for flagged findings.
- Third-Party Integrations: Jira, Azure DevOps & other integration for remediation tracking.
- Role-Based Access Control: Three roles -
- Scan Admin: Full configuration and management
- Scan User: Initiate scans and view results
- Scan Read User: Read-only access
- Domain Separation Support: Ensures data isolation and flexible external integrations per domain.
New
- Run scans directly from the Scan Results list view using UI actions. You can now trigger delta scans using Initiate Scan and start a full scan using Force Full Scan (including cancelling an in-progress delta scan to immediately begin a full scan).
- Scan Engine will now perform a Live Scan on any Record (sys_metadata) during load of Form View. This means that Findings are immediately created in real-time. This “Passive Enforcement” mode allows the Real-Time Validation to be set to False so that Developers are not interrupted on Insert / Update of records, but when the Form View loads, a Scan is performed and Findings are generated.
- Creates exception reasons directly from findings (without needing to navigate to the underlying scanned record).
Changed
- Improved scan initiation behavior and visibility for scan UI actions. Updated behavior around when scan buttons appear and how scan initiation messaging behaves on the Scan Results page.
- Out-of-box (OOTB) scanning is no longer customer-configurable. This change prevents Scan Engine from scanning partner/store application records and surfacing findings that customers can’t act on.
- Additional logging information has been added to the Scan Status page. This provides additional feedback to indicate where the current scan is within the process of loading application files.
Fixed
- Resolved issues where story/task details and links from a source instance were not fully syncing to the target (production) instance.
- Fixed cases where newly created Jira stories/tasks could have a blank short description.
- Corrected Exclude Approved Exception counts so governance totals reflect expected values.
- Fixed discrepancies in exception views where definitions and line numbers were incorrect.
- Ensured exceptions created during remediation are reliably linked to their originating findings for accurate governance and reporting.
Removed
- Removed the property that allowed enabling out-of-box scanning.
- The related setting is set to false (off) for any customer instances where it had previously been enabled.
N/A