A Control Manager has changed the status of an issue to “In Remediation” and has submitted it. What will be the state of the Issue if there is no…

The issue workflow in Oracle Risk Management Cloud proceeds through various states. When an issue is in the "In Remediation" state, the control manager works on a remediation plan. Upon submission, the issue enters an approval workflow. If no validator, reviewer, or approver roles are configured for this workflow in BPM Worklist, the system automatically approves the submission. Consequently, the issue's state transitions directly to "Approved," signifying the completion of the remediation and approval cycle.

A. In Review: This state is used only when a reviewer is configured in the workflow. Since none are configured, this step is skipped.

B. Active: This is a general status for an object that is in use, not a specific state in the issue management workflow process.

C. Reported: This is an initial state that occurs before an issue is accepted and moved into remediation. The workflow does not move backward to this state.

E. In Edit: This is not a formal workflow state but describes an action where a user is actively modifying the issue details before submission.

Oracle Fusion Cloud Risk Management and Financial Reporting Compliance, 24B, "Monitor Issues and Remediations": Chapter 6, Section "Issue Remediation". The documentation describes the lifecycle, and standard BPM workflow behavior dictates that a task with no assignees is automatically completed/approved.

Oracle Fusion Cloud Applications, Using Common Features, 24B, "Using Approval Management": Chapter 10, Section "Approval Task". This guide explains that if an approval stage has no participants, the process advances to the next stage, effectively auto-approving the current one.