RCA Error on Record Forms due to AI Agent Modified Fields APIDescriptionWhen opening a record form for a table where Restricted Caller Access (RCA) is enabled, an RCA error message is displayed. This occurs because the AI Agent Modified Fields API invocation is blocked under RCA constraints, preventing it from retrieving AI activity data required for the form, which results in the error being surfaced to the userSteps to Reproduce Navigate to a record form for a table where AI Agent functionality and Restricted Caller Access (RCA) are enabled.Load the form.Observe that a Restricted Caller Access (RCA) error message is displayed on the form.Open browser developer tools or relevant system logs.Inspect the network/API calls triggered during form loadWorkaroundNavigate to sys_ws_definition_list.Filter for AI Agent.Open the relevant record.Under Related Lists, select Modified Fields.Open the corresponding Scripted REST API Operation.Update the script with the required code fix. Note: This workaround is not effective in Zurich. Code: (function process(request, response) { function execute(params) { const recordTable = params.recordTable || request.queryParams.sysparm_recordTable; const recordSysId = params.recordSysId || request.queryParams.sysparm_recordSysId; if (!recordTable || !recordSysId) { response.setStatus(400); response.setBody({ error: 'Missing recordTable or recordSysId' }); return; } const fetcher = new AiRecordActivityFetcher(); const aiActivity = fetcher.fetch(recordSysId); response.setStatus(200); response.setBody({ isAiCreated: aiActivity.isAiCreated, fields: aiActivity.fields }); } execute((request.body && request.body.data) || {}); })(request, response); For Yokohama and Australia versions, the issue can be mitigated by updating the Scripted REST API: Note: This workaround is not effective in Zurich.Related Problem: PRB1993929