You are configuring security and you do not want the risks to go through the review and approve process each time they are updated. How will you meet this requirement?

The approval workflow in Oracle Risk Management is triggered by the assignment of specific duty roles, namely the Risk Reviewer and Risk Approver roles. If no users are assigned to job roles that contain these duty roles, the system has no one to route the approval task to. Consequently, the workflow is bypassed, and the risk is automatically set to an active or approved status upon creation or modification. This is the standard mechanism for disabling the formal review and approval process for an object.

A. Assigning the reviewer role to the creator does not bypass the workflow; it simply makes the creator the reviewer, which may not be allowed depending on setup.
B. Using only the approver role would still initiate a workflow, sending the risk directly for approval rather than bypassing the process entirely.
C. Restricting the reviewer role to upper management limits who can review but does not eliminate the review step itself from the workflow.

1. Oracle Fusion Cloud Risk Management and Compliance, Implementing Risk Management, 23D, Chapter 4: Financial Reporting Compliance, Section: "Manage Objects". The documentation on object workflows explains that workflows are contingent on role assignments. If approver/reviewer roles are not provisioned, the workflow does not initiate.

2. Oracle Fusion Cloud Applications, Securing ERP, 23D, Chapter: Role and User Management, Section: "Security Reference for Financials". This guide details the privileges associated with duty roles like Risk Reviewer, implying their necessity for the review process.