Srey Waghray
Moderator
Moderator

Code quality is the backbone of a stable and reliable platform. When errors slip into production, they disrupt business operations, consume developer resources, and damage trust in the system. That’s why the Yokohama release introduces Proactive Code Check, a tool designed to help users identify best practice violations before promoting code to higher environments. This proactive approach ensures cleaner, more reliable deployments while minimizing risks and reducing frustration. 

 

What is Proactive Code Check? 

 

Proactive Code Check empowers you to scan update sets for best practice violations in a sub-production environment. By catching issues early, this tool ensures that all code complies with best practices before reaching production. The result? Improved code quality, reduced errors, and enhanced system stability. 

 

Why Proactive Detection Matters 

 

Without the right tools in place, code violations can slip through the cracks and create significant challenges for your teams. These unnoticed issues often lead to: 

  • Errors and System Instability: Code that isn’t checked thoroughly can disrupt workflows and user experiences, causing frustration and downtime. 
  • Increased Workload: Fixing problems after deployment is time-consuming and diverts resources from strategic, value-driven tasks. 
  • Inefficiency and Risk: A lack of proactive detection makes it difficult to maintain stability and trust in the platform, leading to delays and unnecessary risks. 
  • Increased Technical Debt: When code issues accumulate unnoticed, they result in a growing backlog of fixes that require more effort and resources to resolve over time.  

Addressing these challenges with a robust tool like Proactive Code Check can change the game. It ensures early identification of issues, streamlines workflows, and keeps teams focused on innovation instead of firefighting. 

 

Why Addressing This Problem Matters 

 

Unchecked code and configuration violations don’t just slow down development; they can significantly impact the entire organization: 

  • Undermined Trust: Errors in production environments can damage user confidence in the platform. 
  • Increased Costs: Debugging and reworking code post-deployment adds to the total cost of ownership. 
  • Delayed Operations: Critical business workflows get interrupted, causing dissatisfaction among end users and stakeholders. 
  • End User Experience: Poorly optimized code and unresolved issues can lead to slow response times, application crashes, and inconsistent functionality.  

 

Key Benefits of Proactive Code Check 

 

  1. Enhance Code Quality: Automatically scans for best practice violations, ensuring cleaner and more reliable updates. 
  1. Increase Confidence and Reduce Technical Debt: Early detection boosts confidence by catching potential issues before they are introduced in Production environments. 
  1. Save Time and Resources: Minimizes the need for rework, allowing teams to focus on high-value tasks. 
  1. Maintain System Stability: Promotes only compliant code, safeguarding platform reliability and ensuring smooth operations. 

 

How It Works 

 

Proactive Code Check integrates seamlessly into subproduction environments, allowing you to: 

  • Run Comprehensive Scans: Identify best practice violations across scripts, configurations, and customizations. 
  • Review Detailed Findings: Access clear reports with actionable recommendations to address issues. 
  • Track and Analyze Technical Debt: Monitor improvement areas and technical debt over time, gaining actionable insights. 

This early-stage validation process reduces risks and elevates the overall quality of the codebase. 

 

 

Real-World Impact 

 

Imagine working on a critical update. Without Proactive Code Check, undetected issues could lead to system instability, requiring hours of debugging and rework. With this tool, violations are flagged and resolved immediately, ensuring a smooth deployment and uninterrupted business operations. 

 

What’s Included in the Yokohama Release 

 

The Yokohama release of Proactive Code Check delivers: 

  • Prevention of Technical Debt: Thorough scans for best practice violations before promotion to production, ensuring compliance. 
  • Comprehensive Tracking and Analytics: Detailed reports on technical debt and prevention metrics to maintain high standards across instances. 

 

The Bottom Line 

Proactive Code Check isn’t just a tool—it’s a step forward in ensuring platform stability and reliability. By addressing code quality issues early, teams can: 

  • Deliver higher-quality updates. 
  • Reduce the time and effort spent on troubleshooting. 
  • Maintain a stable and reliable ServiceNow environment. 

With Proactive Code Check, the Yokohama release empowers you to work more confidently and efficiently, ensuring that every line of code contributes to a stronger, more stable platform. 

 

SreyWaghray_0-1741718090493.png

 

Comments
Juhi Poddar
Kilo Patron

Hello @Srey Waghray 

 

Proactive Code Check sounds like a game-changer for maintaining code quality and reducing technical debt—excited to see it in action!

 

Thank You 

Juhi Poddar 

PrabhakarCh
Tera Contributor

We are upgrading to Y-P1 by end April. Really excited to see this feature beneficial for Dev Community and improving the Platform heath.

 

Best,

PC

arielgritti
Mega Sage

Hi @Srey Waghray 

Thanks for sharing. Can I ask what are the differences between this new capability in Yokohama and the HealthScan / Instance Checks approach?


Ariel

Fitz4
Tera Expert

Very interesting tool - how is it used?  I don't see it in the list of available plugins, nor can I find it in the menus of my YP1 release instance. 

Srey Waghray
Moderator
Moderator

Hi - you can leverage Proactive Code Check if you have Impact

Srey Waghray
Moderator
Moderator

@arielgritti 

 

Healthscan was run off the customer instance and ran full instance scans 
 
Proactive code check is leveraging instance scan as the execution technology on the customer's instance.  It also does an update set scan, not full instance scan. 
JC Moller
Giga Sage

What is the future for the Instance scan if you are an on-prem customer? Hope to see at least some tools survive for the use of on-prem users.

 

- Jan

Lisa71
Tera Contributor

what's the difference between proactive code check and instance scan? which exact feature is only available in one of them and not the other? Thanks. 

JC Moller
Giga Sage

OOB Servicenow Instance scan has no code sanity checks. So if you forget to uncomment log statements in your scripts, then there are no OOB scans that will find them. You will need to add support for everything yourself.

 

Why was code checks / code sanity checks left out from the original product? On-prem customers do not have access to Impact.

 

-Jan

Ken K1
Giga Guru

How does this product compare with Bravium Best Practice Engine?  

Mark Nguyen
Tera Guru

@Srey Waghray what's the difference between proactive code check and instance scan? which exact feature is only available in one of them and not the other? Thanks. 

davidwilhel
Tera Contributor

ServiceNow bought Bravium best practice engine. You can no longer buy it from Bravium.

If memory serves, BPE had a lot more checks than Proactive Check. Hopefully there will be more OOB scans in Yokohama.

Version history
Last update:
2 weeks ago
Updated by: