View Details action fails for approvals on sc_task and other tables in Now Assist VA Actionable NotificationsSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The VA Actionable Notifications approval topic (_view_approval_details_LLM_) determines which fields to display in the View Details card by calling ApprovalsVAUtil.getApprovalRecordFields(tableName). This method uses a naming convention to look for a table-specific method — for sc_task it looks for getScTaskFields(), for cmdb_ci_win_server it looks for getCmdbCiWinServerFields(), and so on. If a matching method exists, its field list is used. If not, a default field list is returned.Out of the box, explicit field methods exist for sc_request, sc_req_item, change_request, and kb_knowledge. For any other table, the framework provides a customization hook — the sn_now_teams.ApprovalsVAUtil script include (sys_id: 6ff5d486c34402104a10a78e8740dd0b) — where customers can add their own table-specific field methods following the same naming convention.For example when user clicks on View tables for approval records on SC_TASK, the flow routes to the "other task approvals" branch correctly. However, since no getScTaskFields() method exists, the framework falls back to the default field list which includes sysapproval.requested_for and sysapproval.price. These fields are resolved by dot-walking from the sysapproval_approver record through the sysapproval reference to the target record. Since sc_task (and its parent task) does not have requested_for or price fields, the dot-walk returns null, and the subsequent .getLabel() call on null produces the error:TypeError: Cannot find function getLabel in object null (sys_script_include.ad7694c6c34402104a10a78e8740ddc5.script; line 125) To fix this, Open the script include sn_now_teams.ApprovalsVAUtil (sys_id: 6ff5d486c34402104a10a78e8740dd0b). Add a getScTaskFields method with fields valid on task/sc_task:var ApprovalsVAUtil = Class.create();ApprovalsVAUtil.prototype = Object.extendsObject(sn_now_teams.ApprovalsVAUtilSNC, {initialize: function() {ApprovalsVAUtilSNC.prototype.initialize.apply(this);},getScTaskFields: function() {return {"fields": ["sysapproval.number","sysapproval.short_description","sysapproval.assigned_to","sysapproval.priority","state"]};},type: 'ApprovalsVAUtil'});Fields prefixed with sysapproval. are dot-walked from the approval record through to the target sc_task record. state (no prefix) reads directly from the sysapproval_approver record.--------------------------------------------------------------------------------------------------------------------------------------------------------------------Similar use case be achieved for CMDB tables (Which are non Task tables)Step 1 — Verify approval record data. On the sysapproval_approver record for the cmdb_ci_win_server approval, confirm that source_table = cmdb_ci_win_server (For example) and document_id = the target CI's sys_id. If these are empty, the approval creation mechanism must be updated to populate them.Step 2 — Add the field method. In the same ApprovalsVAUtil script include, add a getCmdbCiWinServerFields method. Since the non-task branch queries the target table directly (not via dot-walk), fields should be direct field names without the sysapproval. prefix:getCmdbCiWinServerFields: function() {return {"fields": ["name","os","ip_address","serial_number","sys_class_name"]};},The same pattern applies to any future table requiring View Details support.The customer can adjust these to any valid oob or custom fields and tables on business requirement.