Server-Side JavaScript Sandbox - Dispositioning OOTB incompatible Guarded Scripts

[Jeff Boltz1]

Hello Community,

We're reviewing incompatible Guarded Script findings associated with ServiceNow's Server-Side JavaScript Sandbox Replacement and have found that occurrence volume can be somewhat misleading.

In our environment, thousands of occurrences reduce to only a small number of distinct recurring script patterns.

ServiceNow Support has since confirmed that several of our highest-volume patterns are known product issues:

- VisualizationFiltersParser.getCreatedByMe()
- VisualizationFiltersParser.getSharedWithMe()
- VisualizationFiltersParser.getBookmarked()

These are being tracked by ServiceNow as a product issue, with customer-side remediation not expected.

We've also confirmed that:

- sn_flow.AssociatedFlows.getFlows() is associated with a separate known ServiceNow product issue.
- One remaining pattern involving sn_hr_agent_ws.hr_DelegationHelper.getDelegatedTasks() is still under investigation and currently has no identified PRB.

This leaves us with a more interesting engineering/governance question than simply counting incompatible-script occurrences.

For customers or developers who have worked through Sandbox / Guarded Script compatibility:

1. Are you dispositioning findings by unique script pattern rather than occurrence volume?

2. How are you handling findings confirmed to originate from out-of-box ServiceNow code?

3. Are you retaining known product-issue findings for validation after the applicable patch/release, or creating exemptions in the interim?

4. When an application-provided/OOTB pattern has no known PRB, how are you determining whether it requires customer action versus vendor investigation?

5. What criteria are you using to determine when your incompatible Guarded Script assessment is sufficiently complete for future enforcement decisions?

I'm particularly interested in practical engineering approaches for separating customer-owned remediation from ServiceNow/platform-owned findings.

Thanks,
Jeff