Hi @Arun_Manoj
Sharing this based on my recent experience—I've just completed the GRC batch, and I'm passing along what I’ve learned.
Triage mainly depends on triage rules and assignment rules. Unfortunately, it didn’t work for me when I raised the issue from ESC, but it did work when I raised it from the Service Portal.
I’d recommend exploring these areas further to identify what might be causing the difference.
You can check the GRC course or now create docs as well.
Hi Arun,
The Issue Triage process (OOTB) will only flow to be a risk event in certain conditions. For example, if the Issue type is an Incident or Loss Event (Attachment 1), the Result field at the bottom will have a new choice to Confirm as a Risk Event (Attachment 2). Note that Risk Events created through this flow will automatically have the associated Issue Triage record populated in the 'Issue Triage' related list of the created Risk Event (Attachment 3).
It is crucial to understand that in Risk Management, Issues and Risk Events are treated differently, hence why there are distinct pathways depending on the 'Issue type'. An issue is typically a deficiency or gap in control, whereas a risk event (or risk incident/exception) is the occurrence of a risk - which can include an actual impact or near-misses. This explains why some of the choices under Issue type will only have results consistent with creating Issues, while only an incident or loss event will allow you to flow into a Risk Event record.
Attachment 1
Attachment 2
Attachment 3
