TypeError thrown by addSystemEncodedQuery when invoked from AIA tools on Yokohama with Now Assist for Security Incident Response 4.2.1 - Known Error

TypeError thrown by addSystemEncodedQuery when invoked from AIA tools on Yokohama with Now Assist for Security Incident Response 4.2.1 Description On ServiceNow Yokohama instances running Now Assist for Security Incident Response 4.2.1, customers using AI Agent (AIA) tools that internally call GlideRecord.addSystemEncodedQuery() or GlideRecord.addUserEncodedQuery() see the agentic workflow fail at runtime. The pre-processor / tool execution surfaces a JavaScript TypeError indicating the function is not available on the GlideRecord object. As a result, agentic flows that depend on these queries (for example, the Shift Handover agentic workflow) cannot complete and the user receives a generic tool-failure response.

Steps to Reproduce

Log in to a Yokohama instance with Now Assist for Security Incident Response 4.2.1 installed. Trigger an agentic workflow that invokes a tool which calls addSystemEncodedQuery() or addUserEncodedQuery() (for example, the Shift Handover agentic workflow). Observe the pre-processor step (e.g., "pre-processor for shift handover" calling getActiveShiftHandover in the AIAShiftHandoverTools script include). Workflow fails; logs show TypeError on the addSystemEncodedQuery / addUserEncodedQuery call.

Root cause:

addSystemEncodedQuery() and addUserEncodedQuery() were introduced in the Zurich release and have not been backported to Yokohama. Any script include or AIA tool that calls these methods on a Yokohama instance will throw a TypeError because the methods do not exist on the GlideRecord prototype in that release.

Workaround Replace calls to the unavailable methods with the addEncodedQuery(query, enforceSecurity) overload, explicitly passing the enforceSecurity boolean to preserve the original ACL-enforcement intent: - addUserEncodedQuery(q) -> addEncodedQuery(q, true) - addSystemEncodedQuery(q) -> addEncodedQuery(q, false)

A targeted update set has been published for customers on Yokohama with Now Assist for Security Incident Response 4.2.1 that applies this substitution at all known call sites. After applying the update set, re-run the affected agentic workflow to confirm the TypeError no longer occurs. No change is required on Zurich or later releases, where the original methods remain available.