Seeking Thoughts on Making Scan UpdateSet Feature Mandatory in ServiceNow

[itsRakesh]

Hello ServiceNow Community,

I hope you're all doing well. Today, I'm reaching out to gather your insights and opinions on a crucial process change we're considering in our ServiceNow environment.

Background:
Recently, we encountered a significant issue where a developer moved an update set containing an Inbound Action without the necessary "When to Run" conditions. This oversight led to operational challenges. To mitigate such issues, we implemented a check under the Instance Scan -> Checks module, which proved effective initially. It flagged errors whenever an Update Set contained Inbound Actions missing the "When to Run" condition.

The Challenge:
Despite this solution, a new team member, unaware of this protocol, repeated the mistake, bypassing the scan and moving an incomplete Update Set into production. This incident highlighted a gap in our process adherence.

Proposed Solution:
I'm considering making the Update Scan feature mandatory in lower instances. The idea is to abort the completion of an Update Set if:
1. The Update Set hasn't undergone a scan.
2. There's a relevant record in the table pointing to the unscanned Update Set.
3. The scan flags Priority 1 issues.

I believe this change could significantly enhance our operational integrity, but I'm keen to understand your perspectives. Have you implemented similar controls in your environments? What challenges did you face, and how did you address them? Are there better alternatives or additional precautions we should consider?

Your experience and insights are precious, and I look forward to your thoughts on this matter.