control adding not wokring in risk record

[rinathombar]

On a Risk Record, we are unable to add relationships to existing Controls using the OOB functionality.
On the Controls related list, when you click "Add," the associated controls appear in the dialog box; however, when you select the Control(s) and click "Add Relationship," nothing occurs.
I was able to create a new Control from the same related list successfully.

what is issue anyone idea

[Naveen20]

The "Add Relationship" button silently failing typically points to one of a few root causes. Here's how to troubleshoot:

1. Check the browser console first

Open DevTools (F12) → Console tab, then reproduce the issue. Look for any JavaScript errors when you click "Add Relationship." This is the fastest way to narrow it down — often there's a client-side error being swallowed silently.

2. ACL on the M2M table

The relationship is created on the many-to-many table — likely sn_risk_m2m_risk_control (or sn_grc_m2m_risk_control depending on your version/plugin). Verify the user's role has create access on that M2M table. The fact that "New" works but "Add" doesn't is a strong hint — "New" creates the control record itself, while "Add" inserts into the M2M table, which may have different ACLs.

3. Business Rule or Before Insert logic

Check for any Business Rules (including scoped app BRs) on the M2M table that might be calling current.setAbortAction(true) or otherwise blocking the insert silently. Filter Business Rules on that table and look at before insert rules.

4. Domain separation

If domain separation is active, confirm that both the Risk record and the Control(s) you're trying to associate belong to the same domain (or global). Cross-domain M2M inserts can fail silently.

5. Known defect

This has been a reported defect in certain ServiceNow releases. Check the Known Error portal (HI) for entries related to "Add Relationship" on Risk Controls related list — there have been patches/hotfixes for this in past family releases. Worth checking which version and patch level you're on.

Quickest diagnostic path: Browser console errors → then check sn_risk_m2m_risk_control ACLs → then check BRs on that table. That sequence usually surfaces the culprit.

[Obed3]

Hi @rinathombar.

We also faced this issue due to a recent update - exactly the same problems as you have encountered where 'New' works, but 'Add' doesn't. As @Naveen20 had noted above, the culprit was likely in an ACL. Indeed if:

• New action works = not a problem with a Create ACL
• Add action does not work = likely problem with a Write ACL (as we are writing to the sn_risk_m2m_risk_control table)

Upon investigation, I found that there was a Write ACL that only allows 'nobody' to Write to that table. Put simply, this means that no one can add controls to risks, and vice-versa. What's interesting though is that this ACL does not appear to have been modified or created recently - suggesting it has been there all along. Perhaps this is something a ServiceNow technical team member can help explain. What new workflow or script modification was introduced that is now causing this conflict?

A simple deactivation to that ACL worked for us.

Result

Note that you should probably scrutinise the logic - who should be able to add to this m2m table? I suspect replicating the approach as in the Create ACL would be prudent. This means that only Compliance Managers, Risk Managers, Risk Implementation Managers and Compliance Control Framework Managers should be able to.