How are task outcomes processed in a BPEL process?

How are task outcomes processed in a BPEL process?

A.
Each path out of the human task activity has a condition in which you specify the outcome that
causes that path to be followed.

B.
With onMessage or pick activities that receive the outcome from the human workflow engine.

C.
With a switch containing a case for each outcome of interest plus an optional otherwise case
after the human task activity.

D.
With a switch containing one case for each possible outcome after the human task.

Explanation:
The Switch activity reflects the possible outcomes, or cases, specified previously,
Approve and Reject. It also has an Otherwise case to represent other outcomes, such as errored,
stale, or expired. Inside each of the cases, you can add activities to complete modeling of the
business process.
Note:
* Human Task editor—A tool that enables you to specify task settings such as task outcome,
payload structure, task participants, assignment and routing policy, expiration and escalation
policy, notification settings, and so on.
* Task outcomes capture the possible outcomes of a task. The Oracle BPEL Worklist Application
displays the outcomes you specify here as the possible actions to perform during run time. You
can specify the following types of task outcomes:
Select a seeded outcome
Enter a custom outcome
* The Outcomes window displays the possible outcomes for tasks. APPROVE and REJECT are
selected by default.