There is no direct relationship between Problem/Incident and IRM Risk Registry items. The "Accept Risk" button on Problems is part of the risk assessment workflow but doesn't create a linked record in the IRM Risk Registry (sn_risk_risk).
Recommended approach to achieve this linkage:
1. Use a Related List with a custom M2M table Create a many-to-many (M2M) relationship table between problem (or task) and sn_risk_risk (Risk table in IRM). This gives you a Related List on both the Problem/Incident form and the Risk Registry item, letting users explicitly link them. This is the cleanest, most maintainable approach.
2. Add a Reference field (simpler but limited) Add a reference field on the Problem/Incident form pointing to sn_risk_risk. Quick to implement but only supports a one-to-one link per record.
3. Automate with a Business Rule or Flow When "Accept Risk" is clicked on a Problem, trigger a Business Rule or Flow Designer flow that automatically creates or links a corresponding Risk Registry item in IRM, pre-populating fields like risk description, category, and source record.
4. Leverage the CMDB/CI relationship If your risks in IRM are already tied to CIs/services, you can use the shared CI as the connecting thread — query risks by the same CI affected in the incident/problem. This gives indirect but meaningful traceability.
Best practice combination: Use option 1 (M2M table) for explicit manual linking plus option 3 (automation) to auto-suggest or auto-create risk links when problems are promoted from incidents. Add a reporting dashboard using Performance Analytics to track problems grouped by linked risk statements.
