Reassign Approvals for Risk Assessments

Jan_07
Tera Contributor

3 weeks ago

Hi there,

I want to try to reassign the approval for a risk assessment when submitted in case the current approver leaves the organization. However, I am getting the error "inline editing disabled", I created a write ACL on the sysapproval_approver table and checked access analyzer which said the user should be able to write to the approver field. However, I am still getting the same issue in both the workspace and in classic view of not being able to edit.

 

1. Do write ACLs take affect on the approver field in sysapproval_approver?

2. Why wouldn't the user be able to edit despite access analyzer saying Write access is granted in classic view?

3. Do I need to look into the workspace to enable line edit? If so, where do I look?

 

Preview file
99 KB
0 Helpfuls
  • 676 Views
3 REPLIES 3

Vishal Jaswal
Tera Sage

3 weeks ago

Hello @Jan_07 

System Property "glide.lists.inline_editing_enabled" set to false disable inline editing globally (for all record types).

FYI: When you try the same via related list in workspace, then this is an expected behavior: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2770684 


0 Helpfuls

Jan_07
Tera Contributor
In response to Vishal Jaswal

3 weeks ago

That property is set to true and I am still facing the same issue

0 Helpfuls

TroyP0581187515
ServiceNow Employee

3 weeks ago

@Jan_07  Run the Security Debugger on the impersonated user and check the logs. Access Analyzer only checks ACLs, so a UI policy, dictionary read-only flag, or workspace form layout could still be blocking inline edits. Could you also share more about the use case? Are you expecting an admin to change approvals for someone who has left? Ideally, nobody should be able to change the approver on a pending approval, so it’s worth confirming whether that’s the real requirement.

Until that’s resolved, these workarounds avoid editing the approver field directly:
Method 1: Add a replacement approver

  1. Open the record (Request, Change, or Incident) with the pending approval.
  2. In the Approvers related list, add the new approver.
  3. Open the new approval and set its state from Not Yet Requested to Requested to trigger the notification.
  4. Open the departed approver’s record and set its state from Requested to No Longer Required.
  5. Keep the old record so the audit trail stays intact.

Method 2: Delegation rules

  • For future departures, set up a business rule or flow on sys_user that creates a sys_user_delegate record when active changes to false.
  • Users can also set delegates in advance under their profile, but that depends on them doing it before they leave.

Method 3: Custom UI Action

  • Build a “Reassign Approval” UI Action on the approval form that lets admins pick a replacement and updates the approver through a controlled background script. This is the cleanest long-term option if approvals need reassigning regularly.
0 Helpfuls